Separate tensorflow coverage into multiple pages

The "Tensorflow End to End Coverage" page has grown quite a bit over the past few months, and #3753 exasperated that significantly. This change splits the TensorFlow coverage into four groups:

TensorFlow Base APIs
TensorFlow Keras Layers
Language and Speech Models
Vision Models

and stores them under a parent page like "Getting Started".

New UI:


Convert numeric values to series early

To be merged after #683.
We can also do similar work for comparison operators, effectively removing the need for to_series/to_polars_series in the Explorer.PolarsBackend.Series.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Fix managed cursor acknowledgment state metric names

Documentation
Check the box below or label this PR directly (if you have committer privilege).
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[ ] no-need-doc
(Please explain why)

[X] doc
(If this PR contains doc changes)

Hi @Demogorgon314 can you review this PR from the technical perspective? Thanks


examples/getting_started not found

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I'm trying to build Cilium on docker using https://cilium-genbit.readthedocs.io/en/latest/gettingstarted/docker.html but the example script is not there anymore.
Is it possible to run Cilium directly in docker? Without Kubernettes.
Cilium Version
pull from github
Kernel Version
0
Kubernetes Version
0
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@kasasxav This part of the documentation is indeed severely out of date. :slightly_smiling_face: Thanks for bringing that to our attention. You're mentioning 'building' Cilium on Docker, but I assume you're trying to run an existing Cilium release image on a standalone Docker node, correct?
I'm not aware of anyone running Cilium this way as it would be impractical to say the least. We definitely don't test Cilium in such a configuration. There's always https://netreap.io if you're looking to use Nomad instead of Kubernetes. I'll see if we can get that piece of documentation updated or removed in the meantime.

Hi @ti-mo,
Yes exactly, we have different dockers running on different sites and we would like to use Cilium for the networking between them and adding policies as well. But we don't use Kubernetes, I know before there use to be the cilium-net docker plugin but it seems it's not available anymore.
I will take a look at nomad and netreap.
Best,
Xavier.

Yep, running standalone on Docker hasn't been officially supported for a long time. Someone pointed me to the fact that you're linking to https://cilium-genbit.readthedocs.io, which is a really old fork of a contributor. This page is long gone in the main branch. :wink:
I'll close this out and ask them to take down the outdated copy of the docs. It's still ranking pretty highly when searching for cilium docker getting started, since the official docs no longer explicitly mention this topic. Thanks again for flagging this!


Kohlchan extension

Hello, mishi. Could you make an extension for kohlchan.net? It's one of the boards that Bernd's chosen to post on.  Thanks.

Half a year has passed, but still no support... And it's faster than, like, 90%+ of the supported boards in the list. Please, take notice.

i did an extension months ago

Half a year has passed, but still no support... And it's faster than, like, 90%+ of the supported boards in the list. Please, take notice.

The problem is that making new extensions is very boring, so I don't make them actively anymore. Moreover, last months I'm busy reworking existing extensions, and it's not a fast process as well. https://github.com/Mishiranu/Dashchan-Extensions/pull/26

as i mentioned, active and working:
https://github.com/krautbernd/Dashchan-Extensions-kohlchan
so this issue can be closed 😉


FOX page: fox farming

https://www.figma.com/design/lqcttmmnGtRtbjb8evL6Le/FOX-page?node-id=814-675&node-type=frame&t=g7p4aoeHaEYvZV2s-0

add fox farming section
add feature flag for this section
release

cc @NeOMakinG The chakra UI math for APY on fox farming:

" do trailing three epochs using FOX price and Rune price on day of distribution. Call it "estimated trailing 90 day APY" " @shapeshift/product is aligned with good math.

@twblack88 - #7867 is the rfox guy


Improve header styling in reference docs

Currently we use header 3 for the top-level sections in the reference docs. We should use the top-level headers and then style each header appropriately. Currently we don't have a lot of flexibility in terms of structuring the content.
Related to this, the styling for header 5 looks strange, as it is smaller than the body text.

This is part of what needs to be standardized and enforced using a linter.
In this case, the rule is you can't jump headers. So need to start with title (#), then ##, and so on.


[Slider] Knob does not move along when value is 0

Title.

Haha, I was waiting until someone came across this one 😂
This happens because 0 is a falsy value. value="0" works.
We've rebuilt this Primitive from scratch, so this issue will be gone once we update the dependency.
Thanks for raising and well spotted ;)


[iOS] Review Tiki-Sdk Tests and Documentation

List of test cases:
On TikiSdk:

[x] #286

On Title:

[x] #287
[x] #288
[x] #289

On License:

[x] #290
[x] #291

On Payable:

[x] #292
[x] #293

On Receipt:

[x] #294
[x] #295

On Idp:

[x] #297
[x] #298

On Trail:

[x] #299
[x] #300
[x] #301

List of documentation who needs to be updated or created
On TikiSdk:

[x] #302

On Title:

[x] #303

On Payable:

[x] #304

On Receipt:

[x] #305

On Idp:

[x] #306

@JesseMonteiro please create the missing stories for these

Done


Document extra_css/javascript

This feature was brought up in #202, I just noticed it wasn't documented.

Going to deal with this in #307


Unable to install library @aws-sdk/client-cognito-identity-provider

Environment
System:
OS: macOS 14.4.1
CPU: (8) arm64 Apple M1
Memory: 105.70 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.19.1
path: ~/.nvm/versions/node/v18.19.1/bin/node
Yarn:
version: 1.22.21
path: ~/.nvm/versions/node/v18.19.1/bin/yarn
npm:
version: 10.2.4
path: ~/.nvm/versions/node/v18.19.1/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.15.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.2
- iOS 17.2
- macOS 14.2
- tvOS 17.2
- visionOS 1.0
- watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode:
version: 15.2/15C500b
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.10
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby

Description
I'm receiving an error TypeError: Object.defineProperty() invoked on non-object when I try to install the library @aws-sdk/client-cognito-identity-provider, but other libraries are working correctly.

Reproducible Demo
try to install library on super app @aws-sdk/client-cognito-identity-provider and try running the application you will received the error
CODE
`import { CognitoIdentityProviderClient, InitiateAuthCommand } from '@aws-sdk/client-cognito-identity-provider';
interface loginParams {
username: string;
password: string;
type: string;
mobile_pin: string,
customChallenge: boolean
}
const login = ({username, password,type, mobile_pin, customChallenge} : loginParams): Promise => {
const client = new CognitoIdentityProviderClient({
region: 'YOUR_REGION',
credentials: {
accessKeyId: 'YOUR_ACCESS_KEY',
secretAccessKey: 'ACCESS_KEY',
},
});
const params = {
AuthFlow: 'CUSTOM_AUTH',
ClientId: 'POOL_ID',
AuthParameters: {
USERNAME: username,
PASSWORD: password,
},
};
return new Promise((resolve, reject) => {
// Attempt login
client.send(new InitiateAuthCommand(params))
.then(data => {
console.log('Authentication successful:', data);
})
.catch(err => {
console.error('Authentication failed:', err);
});
});
};
export { login };
`

Hi @jbaldaraje-cg,
I was able to resolve your issue by adding the following dependencies to transpiled node_modules:
diff --git a/packages/host/webpack.config.mjs b/packages/host/webpack.config.mjs
index 8b16341..571f287 100644
--- a/packages/host/webpack.config.mjs
+++ b/packages/host/webpack.config.mjs
@@ -147,7 +147,7 @@ export default env => {
        */
       rules: [
         {
-          test: /\.[jt]sx?$/,
+          test: /\.[cm]?[jt]sx?$/,
           include: [
             /node_modules(.*[/\\])+react/,
             /node_modules(.*[/\\])+@react-native/,
@@ -158,6 +158,10 @@ export default env => {
             /node_modules(.*[/\\])+metro/,
             /node_modules(.*[/\\])+abort-controller/,
             /node_modules(.*[/\\])+@callstack\/repack/,
+            /node_modules(.*[/\\])+@aws-sdk/,
+            /node_modules(.*[/\\])+@aws-crypto/,
+            /node_modules(.*[/\\])+@smithy/,
+            /node_modules(.*[/\\])+fast-xml-parser/,
           ],
           use: 'babel-loader',
         },

You should be able to get rid of the error this way. In Re.Pack 4.0.0 we included we've added greater compat with Metro, but in this case, you would still need to specify those dependencies yourself.
This is something we're planning to address in the next major release and get rid of this problem altogether.

Hi @jbroma
I already added that and get rid the errors but after trying the library. I'm getting this new error

On aws sdk v3 it was written on the documentation that needed to add this 2 imports on index file
import 'react-native-get-random-values';
import 'react-native-url-polyfill/auto';
But still getting the same error. Did you try on your end if its working?

@jbroma Everything is working now on my end when I run to local but when I release the app. It's not working
I have auth module chunks uploaded to the s3 remote URL and connected to the host app.
on host index, I added this 2 line
import 'react-native-get-random-values';
import 'react-native-url-polyfill/auto';
this is working on my local but when I deploy to production it's not working.
this is the error I'm getting.

@jbroma  Any update on this? Do you support now using aws sdk v3?


Handle GH Actions March 2023 upgrade of ubuntu-latest to ubuntu-22.04.

GitHub Actions runs of Ploutos are now being annotated by GitHub with this warning:

ubuntu-latest workflows will use ubuntu-22.04 soon. For more details, see https://github.com/actions/runner-images/issues/6399

Using an unstable image reference is probably a bad idea, we should reference ubuntu-XXXX directly. We have until March 1st 2023 to either check Ploutos compatibility with the upcoming automatic change or to update the Ploutos workflow to explicitly select an image to use.

Upgrading from Ubuntu 20.04 to Ubuntu 22.04 causes a couple of problems for the pkg-test job:

LXC/LXD containers cannot connect out to the Internet unless a firewall rule is added. See https://discuss.linuxcontainers.org/t/lxd-losts-iptables-rules-with-docker/15045/6.
LXC/LXD containers for older operating systems no longer work under Ubuntu 22.04 because it has upgraded from cgroups v1 to cgroups v2 which causes error:Error: The image used by this instance requires a CGroupV1 host system

Working around the cgroups v2 error by using an LXC VM instead of an LXC container isn't possible with GitHub hosted Ubuntu 22.04 runner because attempting to do so via the --vm argument to lxc causes error:Error: Failed instance creation: Failed creating instance record:
Instance type "virtual-machine" is not supported on this server: KVM support is missing (no /dev/kvm)

Done in https://github.com/NLnetLabs/ploutos/releases/tag/v7.1.1.


Add Electron definitions

Definitions for Electron, formerly known as Atom Shell.

cool! but https://www.npmjs.com/package/electron is already exists...
https://www.npmjs.com/package/github-electron is not exists...
Do you have any good name?

github-electron sounds good. I'll rename everything.

@vvakame everything has been renamed to github-electron.

@jedmao thanks!


feat: update fetch configuration logic

Going through open PRs and seeing what can be merged into a new version (see #64) branch
Includes PRs:

#42
#43
#47
#54

Update fetch detection logic (See: https://github.com/mistralai/client-js/pull/63#discussion_r1582538661):

Add client._fetch hook point for tests rather than using a global
Use top level await, per here and here

On mobile/email.

I believe you are correct regarding the logic but it would depend on how
offended you are by not reducing as to whether it should be corrected. As I
age I find more explicit code easier to work with. A mix of pragmatism and
slowing.
That said, can change it.

Message ID: @.***>


Implement a performant bucketing MSM

Works towards #65. This PR implements a serial version of a bucketing MSM algorithm, and reduces gas costs for large MSMs. We have the following tests on N=8,16, where improvement can already be seen:
Running 5 tests for test/multiscalar-mul-tests.t.sol:MultiscalarMulTest
[PASS] testGetAt() (gas: 3832)
[PASS] testGrumpkin3Serial() (gas: 22090653)
[PASS] testGrumpkin3Unoptimized() (gas: 22876388)
[PASS] testGrumpkin4Serial() (gas: 29651565)
[PASS] testGrumpkin4Unoptimized() (gas: 46444653)

Todo:

Signed-digit optimizations
Look into optimizing ff/ec routines

I'm just now reading the comments in https://github.com/lurk-lab/solidity-verifier/pull/60.
@storojs72 what would you think is the best way forward? I can continue working on some more optimizations, if that's something we need. We can also merge this as a somewhat self-contained proof-of-concept, and come back to it


Installed Roxy-wi does not work when accessing web console.

The roxy-wi.error.log showed:
[Tue Jan 30 09:29:50.916780 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:16]     from flask import Flask

[Tue Jan 30 09:29:50.916822 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:16] ImportError: No module named flask

[Tue Jan 30 09:29:51.374719 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28] mod_wsgi (pid=10317): Target WSGI script '/var/www/haproxy-wi/app/app.wsgi' cannot be loaded as Python module.

[Tue Jan 30 09:29:51.374838 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28] mod_wsgi (pid=10317): Exception occurred processing WSGI script '/var/www/haproxy-wi/app/app.wsgi'.

[Tue Jan 30 09:29:51.374912 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28] Traceback (most recent call last):

[Tue Jan 30 09:29:51.374987 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28]   File "/var/www/haproxy-wi/app/app.wsgi", line 4, in <module>

[Tue Jan 30 09:29:51.375061 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28]     from app import app as application

[Tue Jan 30 09:29:51.375088 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28]   File "/var/www/haproxy-wi/app/__init__.py", line 1, in <module>

[Tue Jan 30 09:29:51.375132 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28]     from flask import Flask

[Tue Jan 30 09:29:51.375172 2024] [:error] [pid 10317] [remote <IP_ADDRESS>:28] ImportError: No module named flask

web page showed:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

I tried to installed flask with pip3 install flask and it said the requirement already satisfied.
Please help

Please, install all needed modules


add repository and bugs to published packages

WHY are these changes introduced?
In addition to https://github.com/Shopify/cli/pull/424.
Included a link to the repository on the NPM package (etc.) itself.
WHAT is this pull request doing?
Adds repository and bugs properties to package.json of all packages.
How to test your changes?

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

@gonzaloriestra fixed your comment limiting the changes to packages that was in the list of yours. Apparently it was easier to create a new pull request with the fork than cleaning up :-)

Could you please rebase or merge from main? We have just fixed an issue with the tests there.


[DevTools / JS / Get Started / (3) Paused On Correct Line]

snort
The debug demo is running minified js, so it's hard to follow along with the instructions to look for specific variables and set watches on them...
:)
But it's a nice tutorial - thanks for all the effort that went into it!

Hey @rlevine, the demo isn't minified. My guess is that you have an extension that intercepts all click events. So you're actually paused in the extension's handler. If you try running the demo again in Incognito Mode you probably won't be able to reproduce what you're seeing. This comes up often enough that I covered it in the troubleshooting for step 2 (i.e. when you click the something's wrong button) but I don't think I've seen it get reported for step 3 too often.
Let me know if that helps
Glad to hear you're liking the tutorial. It took me a lot of effort

Hi Caye!
Yep, that was the issue.
Here’s a bit of sequence information, if it’s useful. (Full disclosure, I’ve taught debugging and tools for other languages a bunch, but haven’t spent much time in Chrome, so I went in knowing more than some in your audience. I was as curious about the demo as I was the teaching content. :)
I’m running 1password, and it does intercept click events.
When opened the inspector for the first time and clicked on “Sources,” I saw tabs for both the demo html and js files in the tab header, but also for the 1password lib, end.min.js. The file get-started (with no .html extension shown) was selected in the left nav column, so I didn’t think twice about the code display. I then set a mouse click breakpoint, returned to your demo window, and clicked the demo button. The click triggered the breakpoint, and I hit your Step 2 “I TRIGGERED THE BREAKPOINT” feedback button, ‘cause I did trigger it.
At this point, I read Step 3, and I was on line 52, not 19. Bzzzt.
I got this from the “I’M PAUSED ON ANOTHER LINE” troubleshooting button:
Looking at the troubleshooting feedback for Step 2, it seems like it’s swapped with troubleshooting for step 3:
In any case, as I said in my first note, it’s a cool demo. Even though it’s short, this kind of interactive content takes a tremendous amount of work to make it both bombproof and be perceived like it flows easily. The good ones end up being labors of love, eating up far more time than intended.
Thanks for creating it!
Rick Levine
+1<PHONE_NUMBER>

On Apr 25, 2017, at 3:27 PM, Kayce Basques<EMAIL_ADDRESS>wrote:
Hey @rlevine https://github.com/rlevine, the demo isn't minified. My guess is that you have an extension that intercepts all click events. So you're actually paused in the extension's handler. If you try running the demo again in Incognito Mode you probably won't be able to reproduce what you're seeing. This comes up often enough that I covered it in the troubleshooting for step 2 (i.e. when you click the something's wrong button) but I don't think I've seen it get reported for step 3 too often.
Let me know if that helps
Glad to hear you're liking the tutorial. It took me a lot of effort
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/google/WebFundamentals/issues/4460#issuecomment-297183421, or mute the thread https://github.com/notifications/unsubscribe-auth/ACMDKcKFtqh_HHR2ZWJ7mXgQ0qo_w-8Vks5rznNQgaJpZM4NGw4i.

OK cool, that reproduction information is indeed helpful. I think I can re-work the tutorial a bit to catch this, since it happens pretty often.

Re-visiting this old issue, it seems that I've already updated the tutorial to mention why you might pause on the wrong line of code and how to workaround the situation.


Profile header is not centered on iPhone 5S

on a 6S, the profile skews to the left slightly...


Changes api that apple incorrectly flagged

Apple's app store submission automation is flagging internal API as in violation of private Apple API incorrectly. Other folks are having this problem as well. The easiest path to release is changing our internal api to something else. Here goes nothing.

LOL at the SodiumChloride change. Gotta love the App Store.

👍


chore: Do not merge: dummy PR

This is DNM but not a draft and I'm assigned, which means I get gently nudged by the bot to review this. If this isn't needed can it be closed or converted back to a draft?


Mirror bats syntax / theme support

Seeing if we can just depend on a subset of bat: https://github.com/sharkdp/bat/issues/919#issuecomment-1270995318

As for background color handling, they fill to the end of the line with whitespace to get the right background iff a background color is set.

For the gutter (like line numbers), bat uses
const DEFAULT_GUTTER_COLOR: u8 = 238;

       let gutter_style = Style {
            foreground: match theme.settings.gutter_foreground {
                // If the theme provides a gutter foreground color, use it.
                // Note: It might be the special value #00000001, in which case
                // to_ansi_color returns None and we use an empty Style
                // (resulting in the terminal's default foreground color).
                Some(c) => to_ansi_color(c, true_color),
                // Otherwise, use a specific fallback color.
                None => Some(Fixed(DEFAULT_GUTTER_COLOR)),
            },
            ..Style::default()
        };


refactor(scale_degree): ♻ extract romanNumeral getter

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

22 of 22 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1066

Relevant Lines:
1066

💛  - Coveralls


transactions

feat: running a query within a read transaction
feat: determine whether update query
docs: documents the new transaction function calls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


expression is not callable when using O.Writable

Worked ok in 4.x, doesn't work in 6.x
TS 3.7.4
class X {
  fn(): void {}
}

function test<C extends X>(c: C) {
  const cc = c as O.Writable<C>
  cc.fn() // this expression is not callable
}

Hi @xaviergonz, thanks for reporting his. I'm going to push a fix soon.

Hold on, it's out in a few minutes! https://travis-ci.org/pirix-gh/ts-toolbelt/builds/631255536?utm_source=github_status&utm_medium=notification
Cheers

That was fast, thanks!

Like Speedy Gonzales :mouse::dash:


loading state dict failed

Hi,
when I loading the parameters with your pretrained model, a strange problem happens. It looks like below:
While copying the parameter named "sw1.running_cov", whose dimensions in the model are  While copying the parameter named "sw1.running_cov", whose dimensions in the model are torch.Size([4, 16, 16]) and whose dimensions in the checkpoint are torch.Size([4, 16, 16]).
While copying the parameter named "layer1.1.sw2.running_cov", whose dimensions in the model are torch.Size([4, 16, 16]) and whose dimensions in the checkpoint are torch.Size([4, 16, 16]).
While copying the parameter named "layer2.1.sw2.running_cov", whose dimensions in the model are torch.Size([8, 16, 16]) and whose dimensions in the checkpoint are torch.Size([8, 16, 16]).
While copying the parameter named "layer2.3.sw2.running_cov", whose dimensions in the model are torch.Size([8, 16, 16]) and whose dimensions in the checkpoint are torch.Size([8, 16, 16]).
While copying the parameter named "layer3.1.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.3.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.5.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.7.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.9.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.11.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.13.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.15.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.17.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.19.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
While copying the parameter named "layer3.21.sw2.running_cov", whose dimensions in the model are torch.Size([16, 16, 16]) and whose dimensions in the checkpoint are torch.Size([16, 16, 16]).
The input_param and param indeed have the same shape, but why they cannot be loaded.? Have you met this problem?

This seems to be caused by the definition of 'running_cov'. in your code, it is defined by torch.eye(xx).expand(), where 'expand' will cause the copy_() problem when using load_state_dict(). I change 'expand()' to  'repeat()', and the parameter loading problem is addressed. So I think the original code should be updated for correct parameter loading if what I said is right!

@chenbinghui1 Thanks, I'll check and fix it.


Enhance Settlement ITs

Enhance the Settlement ITs in `` to add tests that cover the following scenarios:

[x] Prefunding scenario: Two connectors have balances of 0 between them, and then one connect "tops up" the other by sending a premptive settlement-layer (i.e., XRP) payment. The test should assert that balances are correct in this scenario.

[x] Create an IT where the request to the settlement engine fails. E.g., settleThreshold is 10, and an account goes to 11. A settlement will be triggered,  it will fail. In this scenario, prepares should be rejected until the balance goes below the threshold. In other words, the balance shouldn’t really ever exceed the threshold. (This is the 10 payments of 1100 case that I discussed with @theotherian).

[x] Revisit the leftovers situation (when you go below 1 unit of asset scale 6); make sure the connector handles this correctly.

See #373  and #374 for follow-on tasks.


SWARM-1632: Part 2, Change JWT packages to org.wildfly.swarm.microprofile.jwtauth

This PR also enables the JWT TCK

Does this PR need to rebased onto master once https://github.com/wildfly-swarm/wildfly-swarm/pull/708 is merged?
It seems like there's a lot of files being changed in the PR that are part of other changes

It builds on #708 . So if we merge that first we should be fine I guess

@heiko-braun looks like in merging #708 this needs to be fixed because of conflicts

I'll rebase this

thanks

Superseded by #713


http2: Track scheduled events

Possible fix of #11260. Scheduled events should be tracked and canceled by destructor. Otherwise, scheduled events will be fired to the freed continuation.

@bneradt Good point! Add handlers to the state_closed.

[approve ci autest]

[approve ci autest]

[approve ci autest]

Cherry-picked to v10.0.x


please add a license

Fixed in https://github.com/BCCDC-PHL/cgmlst-clustering/commit/2ccaad159f43fd2b11d75758c304f77fefea2f54


Parse result is wrong where have comma inside double quotation

I notice when data have the comma (,) inside field with quotation (" ") then data of that field will be parse wrong.
Here is the schema:
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://jsapar.tigris.org/JSaParSchema/2.0">
  <csvschema lineseparator="\n">
    <line occurs="*" linetype="Person" cellseparator="," firstlineasschema="true">
      <cell name="Manufacturer" quotebehavior="ALWAYS" />
      <cell name="Model Name" />
      <cell name="Model Code" />
      <cell name="RAM (TotalMem)" />
      <cell name="Form Factor" />
      <cell name="System on Chip" />
      <cell name="Screen Sizes" />
      <cell name="Screen Densities" />
      <cell name="ABIs" />
      <cell name="Android SDK Versions" />
      <cell name="OpenGL ES Versions" />
    </line>
  </csvschema>
</schema>

And CSV input data:
Manufacturer,Model Name,Model Code,RAM (TotalMem),Form Factor,System on Chip,Screen Sizes,Screen Densities,ABIs,Android SDK Versions,OpenGL ES Versions
"Hon Hai Precision Industry Co., Ltd.",Germany,S9714,973MB,Tablet,NVidia Tegra 3 T30,1280x752,160,armeabi-v7a;armeabi,15;16,2.0
10.or,10or_G2,G2,3749MB,Phone,Qualcomm SDM636,1080x2246,480,arm64-v8a;armeabi-v7a;armeabi,27,3.2
zyrex,ZT 216,ZT_216, ,Phone,Spreadtrum SC9832A,600x1024,213,armeabi-v7a;armeabi,24,2.0
Acer,A3-A40,acer_jetfirefhd,1900-1941MB,Tablet,Mediatek MT8163,1920x1200,240,arm64-v8a;armeabi-v7a;armeabi,23,3.0

In above sample data, "Hon Hai Precision Industry Co., Ltd." is parsed into 2 fields: Hon Hai Precision Industry Co and  Ltd.".
Do you know any wrong with my schema? And how to fix it?

You need to define the quote character to use for the line type, like this:
 quotechar="""
So the whole line declaration should be like this:
 <line occurs="*" linetype="Person" cellseparator="," firstlineasschema="true" quotechar=""">
Please let me know if this solved your issue.
The quote behavior that you specified on cell level is only used to specify the behavior while composing, it does not define which quote character to use while parsing.
Another thing. When you use firstlineasschema, you don't necessarily need to specify each cell that may occur if they only should be parsed as strings. It does not harm doing so but the cell names and order will be fetched from the first line anyway. Only cells that has specific characteristics (such as different data type or quote behavior) needs to be specified for the line type.

Thanks @stenix71 it really work.
If you don't mind, I have another issue with double quotation that need your help. In above case, I try to parse such data:
Samsung,"Galaxy Tab A (8.0"", 2019)",gto,1846MB,Tablet,Qualcomm SDM429,800x1280,213,arm64-v8a;armeabi-v7a;armeabi,28,3.2

According to Guide > Basic Schema > Parsing quoted values (link)

As long as you have activated quoting as described above, the parser will automatically detect if a cell is quoted or not. Not all cells needs quoting. A cell is considered to be quoted if and only if the first and the last character of the cell is the quote character. The quote characters will always be removed from the parsed value
...
"aaa","b""bb","ccc"... will be parsed to b""bb

But as my result, the second field is Galaxy Tab A (8.0", the the third field is  2019, while expected is Galaxy Tab A (8.0", 2019).
Do I mis-configure somewhere?

This one is trickier though. Since there is a comma directly after the second quote, the parser will consider this as the end of the cell, even though it is the second quote. I can look into if this can be solved for future release but the current version does not allow this. There are so many variants of CSV files and how to parse quotes.

I have implemented parsing that can handle RFC4180 style quoting you like in your example above. If you are eager to try it out you can use the version published as 2.1.0-SNAPSHOT or you can clone the 2.1-develop branch and build it yourself. If you use the maven snapshot version you need to have snapshot versions enabled while searching the maven repository.
In order to change the quote syntax you will need to set the quotesyntax attribute on csvschema element like this:
<csvschema quotesyntax="RFC4180">
I also changed the default quote character to be the double quote character as you expected so quoting is now enabled by default. The reason for not having so in the first place was that in an older version of the library, parsing quoted sources was quite inefficient. This has been solved now though. Parsing quoted and non-quoted sources takes roughly the same time now.
I will need to test the 2.1.0 version a bit more until I release it officially.

I try to search for enable Snapshot in Intellij but it doesn't found org.tigris.jsapar:jsapar:2.1.0-SNAPSHOT, thus I build it myself.
Well, after upgrade to 2.1.0-SNAPSHOT, I use following schema (as you said):
<schema xmlns="http://jsapar.tigris.org/JSaParSchema/2.0">
    <csvschema lineseparator="\n" quotesyntax="RFC4180">
        <line occurs="*" linetype="Person" cellseparator="," firstlineasschema="true" quotechar=""">
        </line>
    </csvschema>
</schema>

And the result looks so good: text like "Galaxy Tab A (8.0"", 2019)" is parsed correctly to "Galaxy Tab A (8.0\", 2019)". That's what I expected. Thank you for your hard work.


Revoking a token does not pass the Bearer token

Describe the bug
I'm filing this under general questions as I am not sure whether this is a bug or a feature.
After I have successfully authenticated with the auth server (in this case it's Spring Authorization Server), I want to call revokeTokenAndLogout(). I get a 401 from the server and I can see that the Bearer token is not passed along on the POST. Spring Authorization Server does not know who the caller is and consequently returns a 401 in return.
Is this mentioned in the OAuth2 spec? Is there a requirement to pass the Bearer token? Should this be configurable.
I am new to implementing OAuth2 so please pardon my ignorance.
I have filed a similar ticket with the Spring Authorization Server team here: https://github.com/spring-projects/spring-authorization-server/issues/574
Regards,
Bjorn

I'm no full spec expert either, but I presume if you're relying on this library's logout features it initiates OpenID's "front-channel logout" which (as far as I can tell) does not mention said endpoint from being protected. I think typically such a logout URL is reached in a redirect manner, via GET (usually?), and the user is asked to confirm they want to logout. This will end the session with the IDP typically by clearing the cookie that the Browser and the IDP have for the IDP's domain / identity features.
Can it be that you're using a back-channel logout endpoint or similar, from Spring? This is where an API (e.g. if you have a "BFF: Backend-For-Frontend" style setup) can log out the user at the IDP. Here it makes more sense for the endpoint to expect POST and a token to secure it, since there is no cookie involved.
Perhaps your IDP supports both logout types, and you just need to get the front-channel logout URI into this library's configuration?
Either way, the library doesn't support anything in this regard, as far as I know.
A straightforward workaround would exist though: intercept the redirect to the logout URL, and convert it to a POST with the access token yourself.
Hope that helps!

Very helpful @jeroenheijmans! Thank you.
...and if you are not an expert on this, I would venture to ask: WHO IS???
Wishing you fun and success in 2022 🚀


nixos/restic: fix #264696 and add a regression test

Description of changes
Make sure that preStart and postStop are included whenever they need to be.
Fixes #264696
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

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@hughobrien @i077

@ofborg test restic

For me the edits look sane and the test runs successful, I would like to get this in before branch of and also would like my backups to work as expected again since I would consider them somewhat critical..

close #264696

@Janik-Haag, you have more domain knowledge than me. Could you review the difference between this and #264849? Either are fine IMO, but i do not feel suited to be the tie-breaker.

I don't believe I have more knowledge but this PR seems a bit more cleaner since doBackup basically already implements filesFromStaticPaths and filesFromFile. And we can add the tests from #264849 in another pr or just rebase it once this one is merged.


Implement RTCDataChannel onError

OnError sets event handler which is called when the data transport cannot be read
Reference issue
#746

Fantastic work @spaceCh1mp !
Mind making those changes, and then adding yourself to the README.md then I think it is good for merge! Really excited to have you involved.
thanks

Codecov Report

Merging #759 into master will increase coverage by 0.1%.
The diff coverage is 60%.

@@            Coverage Diff            @@
##           master     #759     +/-   ##
=========================================
+ Coverage   76.69%   76.79%   +0.1%
=========================================
  Files          58       58
  Lines        4037     4051     +14
=========================================
+ Hits         3096     3111     +15
- Misses        685      688      +3
+ Partials      256      252      -4

Impacted Files
Coverage Δ

datachannel.go
81.03% <60%> (-1.22%)
:arrow_down:

peerconnection.go
73.25% <0%> (+0.28%)
:arrow_up:

dtlstransport.go
70.34% <0%> (+2.32%)
:arrow_up:

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 0a62e5d...30156fa. Read the comment docs.

Done, thank you for putting me through.

Congrats your PR has landed @spaceCh1mp https://github.com/pion/webrtc/commit/26f0fa5d3320bbc615db30915715f0c86d23622b
I modified your commit message to pass our linters. I didn't want to make you jump through hoops for no reason. You can see in travis-ci at the bottom we have a check https://travis-ci.org/pion/webrtc/builds/564512300?utm_source=github_status&utm_medium=notification
You can run the same command locally and should get this output!
0.01s$ bash .github/lint-commit-message.sh
Implement RTCDataChannel onError
OnError sets event handler which is called when the data transport cannot be read, addresses issue #746
-------------------------------------------------
The preceding commit message is invalid
it failed 'Separate subject from body with a blank line' of the following checks
* Separate subject from body with a blank line
* Limit the subject line to 50 characters
* Capitalize the subject line
* Do not end the subject line with a period
* Wrap the body at 72 characters
The command "bash .github/lint-commit-message.sh" exited with 1.

Really excited to have your involvement. Hopefully we get more PRs, and would love your feedback, how can we make Pion easier for users/contributors! Anything we can change to make better I would love to know.

great, I'll be contributing a lot with time. Then I thought of something, what if instead of doing away with the log command, have the onError function log the error when the handler hasn't been set


Add loading state while node is starting up

From https://github.com/getAlby/nostr-wallet-connect-next/pull/225#discussion_r1560675322

The balances do not refresh, so I had 0 until I reloaded the page (this will only happen immediately after startup though - I wonder if we should wait for the node to fully start up...?).

Related: https://github.com/getAlby/nostr-wallet-connect-next/issues/200


Object Oriented Approach

Created to solve #80.

Pep8 Failure:
FAIL: Test that Docbuilder does comply with PEP8.

----------------------------------------------------------------------

Traceback (most recent call last):

  File "/home/travis/build/shakna-israel/docbuilder/tests/test.py", line 45, in test_pep8_complicance

    "Found code style errors (and warnings).")

AssertionError: Found code style errors (and warnings).

-------------------- >> begin captured stdout << ---------------------

docbuilder.py:340:29: E231 missing whitespace after ':'

docbuilder.py:340:36: E231 missing whitespace after ','

docbuilder.py:340:45: E231 missing whitespace after ':'

docbuilder.py:340:52: E231 missing whitespace after ','

docbuilder.py:340:62: E231 missing whitespace after ':'

docbuilder.py:340:70: E231 missing whitespace after ','

docbuilder.py:340:87: E231 missing whitespace after ':'

docbuilder.py:340:102: E231 missing whitespace after ','

docbuilder.py:340:116: E231 missing whitespace after ':'

docbuilder.py:340:128: E231 missing whitespace after ','

docbuilder.py:340:140: E231 missing whitespace after ':'

docbuilder.py:340:150: E231 missing whitespace after ','

docbuilder.py:340:166: E231 missing whitespace after ':'

Now that its compliant with PEP8, it needs a series of test created for it.


Emails for each language are not editable

Can you reproduce this issue on default Wordpress theme (eg Storefront)?
Can you reproduce this issue when all other plugins are disabled except WooCommerce, Polylang and Hyyan WooCommerce Polylang Integration?
What product versions and settings are you using when this issue occurs?

PHP:
WordPress: 4.8.1.
WooCommerce: 3.1.1.
Polylang: 2.1.6.
Hyyan WooCommerce Polylang Integration: 1.0.3.
Browser: Chrome

What I Expected
I would expect that for each available language I will be able to create all WooCommerce order emails.
What Happened Instead
Always the main language is used as a template. And if I select language (menu at the top of the Admin Area) all other languages are using always same template.
Is there some process how to have separate emails for each language activated in WooPoly? And if it is solved, where can I edit each language?
Thank you
Pavel

Yes there is one set of templates, and all the strings in that template are translatable, either as standard wordpress translation files, or (for the strings customisable in the woocommerce admin UI) the Polylang strings translation table.
If you want additional text blocks or per-language formatting customizations, then just copy the email templates from wooCommerce to your theme directory\woocommerce\emails and then you can implement however you like.


Simplify logging evaluation parameters

Summary
This adds standardized fields to the evaluation parameters logging by introducing a
helper function. By using it, we don't need to repeat the fields we need to log for
each evaluation.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.798% (+0.09%) from 47.713%
when pulling f8ac009408bcf9aa7509abc5f5a96ed7e9194c5c on executor-logger
into 66b7a906fe0df9b20dceaa2624ef511942739a25 on main.


Yarn screws the project

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

If you try to install/run project using yarn something screws jQuery mapping and all jQuery plugins start to report jQuery().<pluginame> is not a function.
Just install yarn and install project with yarn and try to run it.

Angular version: 2.0.0-rc.4
Browser: [all]

@sielay Please try to update Yarn to the new version and build with it. If there are any problems, please notify us.


Known Failing Tests on Lucene.Net

All 7500+ tests pass most of the time, but there are still a few that fail under the random conditions we test them in. This is a complete list of the known tests that fail and what is known about them. Note that these may not be all of the ways the tests can fail.

[x] Lucene.Net.Index.TestTermVectorsWriter::TestTermVectorCorruption() and Lucene.Net.Index.TestIndexWriterReader::TestDuringAddIndexes()

Fails with a message like System.IO.IOException : The process cannot access the file '/tmp/LuceneTemp/index-NIOFSDirectory-fkqg2vah/write.lock' because it is being used by another process.
Happens on macOS and Linux, but not on Windows

[x] Lucene.Net.Search.TestSearchAfter::TestQueries()

Related to current culture
Happens on netcoreapp2.1 on macOS
Happens on netcoreapp1.0 on Linux

[x] Lucene.Net.Util.TestVersionComparer::TestVersions()

Related to current culture
Happens on netcoreapp2.1 on macOS

[x] Lucene.Net.Index.TestIndexWriter::TestTwoThreadsInterruptDeadlock()

Happens on every target framework/OS
Fixed in #525

[x] Lucene.Net.Index.TestIndexWriter::TestThreadInterruptDeadlock()

Happens on every target framework/OS
Fixed in #525
The error message doesn't occur when using lock (this) in IndexWriter.CommitInternal() to make PrepareCommitInternal()
The test does not fail if both of the following lines are commented in TestIndexWriter.IndexerThreadInterrupt::Run()
w.UpdateDocument(new Term("id", idField.GetStringValue()), doc);
w.AddDocument(doc);
The test does not fail if RAMDirectory is used instead of MockDirectoryWrapper
It is quite possible that the problem is with MockDirectoryWrapper or one of its subcomponents, although the locking behavior of IndexWriter is also suspicious
Fails with message:

FAILED; unexpected exception
 System.InvalidOperationException: cannot close: prepareCommit was already called with no corresponding call to commit
 at Lucene.Net.Index.IndexWriter.CloseInternal(Boolean waitForMerges, Boolean doFlush) in F:\Projects\lucenenet\src\Lucene.Net\Index\IndexWriter.cs:line 1157
 at Lucene.Net.Index.IndexWriter.Dispose(Boolean waitForMerges) in F:\Projects\lucenenet\src\Lucene.Net\Index\IndexWriter.cs:line 1096
 at Lucene.Net.Index.IndexWriter.Dispose() in F:\Projects\lucenenet\src\Lucene.Net\Index\IndexWriter.cs:line 1053
 at Lucene.Net.Index.TestIndexWriter.IndexerThreadInterrupt.Run() in F:\Projects\lucenenet\src\Lucene.Net.Tests\Index\TestIndexWriter.cs:line 1223

[x] Lucene.Net.Classification.KNearestNeighborClassifierTest::TestPerformance()

Happens on netcoreapp2.1 on Windows
Happens on net451 on Windows

[x] Lucene.Net.Analysis.NGram.EdgeNGramTokenizerTest::TestFullUTF8Range()
[x] Lucene.Net.Analysis.NGram.NGramTokenizerTest::TestFullUTF8Range()

Happens on net451 on Windows
Happens on netcoreapp2.1 on macOS

[x] Lucene.Net.Search.VectorHighlight.SimpleFragmentsBuilderTest::
TestRandomDiscreteMultiValueHighlighting()

Happens on Windows
Not related to current culture
Definitely a problem with the highlighter, not the test or test framework
As of 2020-07-23, this test no longer fails even after running continuously with different seeds for 8 minutes. I suspect that the J2N structural equality comparer fix https://github.com/NightOwl888/J2N/commit/33382d9a67db693fe2cc6ddefc21dde95f3dfdb4 inadvertently fixed this issue.

[x] Lucene.Net.QueryParsers.Flexible.Standard.TestQPHelper::TestDateRange()

Does not happen on Windows, but happens on both Linux and macOS
Related to current culture - fails with new CultureInfo("ar") specifically (and others)
As of 2020-08-11, this test hasn't failed for several hundred test runs on Azure DevOps.
2021-11-19 - The test started failing again after fixing the random seed functionality in the test framework. It was fixed in #543.
Stack trace

System.FormatException : String '1/1/2002' was not recognized as a valid DateTime.
 at System.DateTimeParse.Parse(ReadOnlySpan`1 s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
 at Lucene.Net.QueryParsers.Flexible.Standard.TestQPHelper.AssertDateRangeQueryEquals(StandardQueryParser qp, String field, String startDate, String endDate, DateTime endDateInclusive, Resolution resolution) in D:\a\1\s\src\Lucene.Net.Tests.QueryParser\Flexible\Standard\TestQPHelper.cs:line 837
 at Lucene.Net.QueryParsers.Flexible.Standard.TestQPHelper.TestDateRange() in D:\a\1\s\src\Lucene.Net.Tests.QueryParser\Flexible\Standard\TestQPHelper.cs:line 826

[x] Lucene.Net.Expressions.TestExpressionSorts::TestQueries()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Sandbox.TestSlowFuzzyQuery::TestTieBreaker()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Sandbox.TestSlowFuzzyQuery::TestTokenLengthOpt()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Search.TestBooleanQuery::TestBS2DisjunctionNextVsAdvance()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Search.TestFuzzyQuery::TestTieBreaker()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Search.TestSearchAfter::TestQueries()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Search.TestTopDocsMerge::TestSort_1()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Search.TestTopDocsMerge::TestSort_2()

Happens on .NET Framework on Windows, x86, in Release mode only (if not Release, x86, or different target framework, does not fail)
Does not fail when optimizations are disabled in Lucene.Net.dll
Fixed in #529

[x] Lucene.Net.Index.TestTaskMergeScheduler::TestSubclassTaskMergeScheduler()

2020-02-18 - Deprecated TaskMergeScheduler and deleted its tests, so this is no longer applicable
Happens rarely
Stack Trace:

System.ObjectDisposedException : Cannot access a disposed object.
at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout)
at System.Threading.ReaderWriterLockSlim.EnterReadLock()
at Lucene.Net.Support.Threading.ReaderWriterLockSlimExtensions.ReadLockToken..ctor(ReaderWriterLockSlim sync) in D:\a\1\s\src\Lucene.Net\Support\Threading\ReaderWriterLockSlimExtensions.cs:line 40
at Lucene.Net.Support.Threading.ReaderWriterLockSlimExtensions.Read(ReaderWriterLockSlim obj) in D:\a\1\s\src\Lucene.Net\Support\Threading\ReaderWriterLockSlimExtensions.cs:line 74
at Lucene.Net.Index.TaskMergeScheduler.MergeThread.get_IsAlive() in D:\a\1\s\src\Lucene.Net\Support\Index\TaskMergeScheduler.cs:line 535
at Lucene.Net.Index.TaskMergeScheduler.Sync() in D:\a\1\s\src\Lucene.Net\Support\Index\TaskMergeScheduler.cs:line 191
at Lucene.Net.Index.TestTaskMergeScheduler.TestSubclassTaskMergeScheduler() in D:\a\1\s\src\Lucene.Net.Tests\Support\Index\TestTaskMergeScheduler.cs:line 106

[X] Lucene.Net.Analysis.Th.TestThaiAnalyzer::TestRandomStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
See #313
(Split out as #1044, fix ready pending ICU4N release)

[X] Lucene.Net.Analysis.Th.TestThaiAnalyzer::TestRandomHugeStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
See #313
(Split out as #1044, fix ready pending ICU4N release)

[x] Lucene.Net.Analysis.Icu.TestICUFoldingFilter::TestRandomStrings()

This turned out to be an issue with culture sensitivity that was introduced in 4.8.0-beta00008. See #321.

[X] Lucene.Net.Analysis.Icu.TestICUTokenizerCJK::TestRandomStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
The temporary patch in #328 makes this test pass and is proof that this is a concurrency problem with BreakIterator, and ffc8f2a2b1ad423631a68b0a64f7bf2ab067a3b3 can be reverted once it is fixed.
(Split out as #1044, fix ready pending ICU4N release)

[X] Lucene.Net.Analysis.Icu.TestICUTokenizerCJK::TestRandomHugeStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
The temporary patch in #328 makes this test pass and is proof that this is a concurrency problem with BreakIterator, and ffc8f2a2b1ad423631a68b0a64f7bf2ab067a3b3 can be reverted once it is fixed.
(Split out as #1044, fix ready pending ICU4N release)

[X] Lucene.Net.Analysis.Icu.TestICUTokenizer::TestRandomStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
The temporary patch in #328 makes this test pass and is proof that this is a concurrency problem with BreakIterator, and ffc8f2a2b1ad423631a68b0a64f7bf2ab067a3b3 can be reverted once it is fixed.
(Split out as #1044, fix ready pending ICU4N release)

[X] Lucene.Net.Analysis.Icu.TestICUTokenizer::TestRandomHugeStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Does not occur when these lines are commented - this is definitely a concurrency problem.  See https://github.com/apache/lucenenet/pull/313#issuecomment-667692212.
The temporary patch in #328 makes this test pass and is proof that this is a concurrency problem with BreakIterator, and ffc8f2a2b1ad423631a68b0a64f7bf2ab067a3b3 can be reverted once it is fixed.
(Split out as #1044, fix ready pending ICU4N release)

[x] Lucene.Net.Index.TestIndexWriterWithThreads::TestRollbackAndCommitWithThreads()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur
Began appearing when #326 was put into place
Patched in #335

[x] Lucene.Net.Analysis.Icu.TestICUFoldingFilterFactory::Test()

Only fails on Ubuntu 18.04 when running on GitHub Actions hosted agent
Does not fail using Ubuntu 18.04 on Azure DevOps
Stack Trace:

Lucene.Net.Diagnostics.AssertionException : End() called before IncrementToken() returned false!  1) Expected: resume, Actual: r�sum�
term 0, output[i] = resume, termAtt = r�sum�
at Lucene.Net.Analysis.MockTokenizer.End() in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/MockTokenizer.cs:line 336
at Lucene.Net.Analysis.BaseTokenStreamTestCase.AssertTokenStreamContents(TokenStream ts, String[] output, Int32[] startOffsets, Int32[] endOffsets, String[] types, Int32[] posIncrements, Int32[] posLengths, Nullable1 finalOffset, Nullable1 finalPosInc, Boolean[] keywordAtts, Boolean offsetsAreCorrect, Byte[][] payloads) in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/BaseTokenStreamTestCase.cs:line 415
at Lucene.Net.Analysis.BaseTokenStreamTestCase.AssertTokenStreamContents(TokenStream ts, String[] output, Int32[] startOffsets, Int32[] endOffsets, String[] types, Int32[] posIncrements, Int32[] posLengths, Nullable1 finalOffset, Boolean[] keywordAtts, Boolean offsetsAreCorrect) in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/BaseTokenStreamTestCase.cs:line 428    at Lucene.Net.Analysis.BaseTokenStreamTestCase.AssertTokenStreamContents(TokenStream ts, String[] output, Int32[] startOffsets, Int32[] endOffsets, String[] types, Int32[] posIncrements, Int32[] posLengths, Nullable1 finalOffset, Boolean offsetsAreCorrect) in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/BaseTokenStreamTestCase.cs:line 433
at Lucene.Net.Analysis.BaseTokenStreamTestCase.AssertTokenStreamContents(TokenStream ts, String[] output, Int32[] startOffsets, Int32[] endOffsets, String[] types, Int32[] posIncrements, Int32[] posLengths, Nullable`1 finalOffset) in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/BaseTokenStreamTestCase.cs:line 438
at Lucene.Net.Analysis.BaseTokenStreamTestCase.AssertTokenStreamContents(TokenStream ts, String[] output) in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.TestFramework/Analysis/BaseTokenStreamTestCase.cs:line 453
at Lucene.Net.Analysis.Icu.TestICUFoldingFilterFactory.Test() in /home/runner/work/lucenenet/lucenenet/src/Lucene.Net.Tests.Analysis.ICU/Analysis/Icu/TestICUFoldingFilterFactory.cs:line 39

[ ] Lucene.Net.Analysis.Core.TestRandomChains::TestRandomChains_() and Lucene.Net.Analysis.Core.TestRandomChains::TestRandomChainsWithLargeStrings()

Happens so rarely that it requires [FindFirstFailingSeed] or [Repeat(100)] attribute to force it to occur (this no longer works after fixing the random seed functionality in the test framwork, we need to wait for it to happen in Azure DevOps)
Began appearing when #326 was put into place
2021-11-19 - The cause is now known - see https://github.com/apache/lucenenet/issues/271#issuecomment-973005744.
Upon multiple runs, the only common failure point seems to be HunspellStemFilter
Stack Trace:

Test Name:	TestRandomChainsWithLargeStrings
Test Outcome:	Failed
Result Message:
Thread threw exception: Lucene.Net.Diagnostics.AssertionException: accCount=1 vs existing accept=False states=[0:1]
   at Lucene.Net.Util.Automaton.BasicOperations.Determinize(Automaton a) in F:\Projects\lucenenet\src\Lucene.Net\Util\Automaton\BasicOperations.cs:line 874
   at Lucene.Net.Util.Automaton.MinimizationOperations.MinimizeHopcroft(Automaton a) in F:\Projects\lucenenet\src\Lucene.Net\Util\Automaton\MinimizationOperations.cs:line 67
   at Lucene.Net.Util.Automaton.RegExp.ToAutomaton(IDictionary`2 automata, IAutomatonProvider automaton_provider) in F:\Projects\lucenenet\src\Lucene.Net\Util\Automaton\RegExp.cs:line 616
   at Lucene.Net.Analysis.Hunspell.Dictionary.ParseAffix(SortedDictionary`2 affixes, String header, TextReader reader, String conditionPattern, IDictionary`2 seenPatterns, IDictionary`2 seenStrips) in F:\Projects\lucenenet\src\Lucene.Net.Analysis.Common\Analysis\Hunspell\Dictionary.cs:line 498
   at Lucene.Net.Analysis.Hunspell.Dictionary.ReadAffixFile(Stream affixStream, Encoding decoder) in F:\Projects\lucenenet\src\Lucene.Net.Analysis.Common\Analysis\Hunspell\Dictionary.cs:line 301
   at Lucene.Net.Analysis.Hunspell.Dictionary..ctor(Stream affix, IList`1 dictionaries, Boolean ignoreCase) in F:\Projects\lucenenet\src\Lucene.Net.Analysis.Common\Analysis\Hunspell\Dictionary.cs:line 162
   at Lucene.Net.Analysis.Hunspell.Dictionary..ctor(Stream affix, Stream dictionary) in F:\Projects\lucenenet\src\Lucene.Net.Analysis.Common\Analysis\Hunspell\Dictionary.cs:line 125
   at Lucene.Net.Analysis.Core.TestRandomChains.DictionaryArgProducer.Create(Random random) in F:\Projects\lucenenet\src\Lucene.Net.Tests.Analysis.Common\Analysis\Core\TestRandomChains.cs:line 511
   at Lucene.Net.Analysis.Core.TestRandomChains.NewRandomArg[T](Random random, Type paramType) in F:\Projects\lucenenet\src\Lucene.Net.Tests.Analysis.Common\Analysis\Core\TestRandomChains.cs:line 747
   at Lucene.Net.Analysis.Core.TestRandomChains.NewFilterArgs(Random random, TokenStream stream, Type[] paramTypes) in F:\Projects\lucenenet\src\Lucene.Net.Tests.Analysis.Common\Analysis\Core\TestRandomChains.cs:line 810
   at Lucene.Net.Analysis.Core.TestRandomChains.MockRandomAnalyzer.NewFilterChain(Random random, Tokenizer tokenizer, Boolean offsetsAreCorrect) in F:\Projects\lucenenet\src\Lucene.Net.Tests.Analysis.Common\Analysis\Core\TestRandomChains.cs:line 1023
   at Lucene.Net.Analysis.Core.TestRandomChains.MockRandomAnalyzer.CreateComponents(String fieldName, TextReader reader) in F:\Projects\lucenenet\src\Lucene.Net.Tests.Analysis.Common\Analysis\Core\TestRandomChains.cs:line 849
   at Lucene.Net.Analysis.Analyzer.GetTokenStream(String fieldName, TextReader reader) in F:\Projects\lucenenet\src\Lucene.Net\Analysis\Analyzer.cs:line 265
   at Lucene.Net.Analysis.BaseTokenStreamTestCase.CheckAnalysisConsistency(Random random, Analyzer a, Boolean useCharFilter, String text, Boolean offsetsAreCorrect, Field field) in F:\Projects\lucenenet\src\Lucene.Net.TestFramework\Analysis\BaseTokenStreamTestCase.cs:line 1044
   at Lucene.Net.Analysis.BaseTokenStreamTestCase.CheckRandomData(Random random, Analyzer a, Int32 iterations, Int32 maxWordLength, Boolean useCharFilter, Boolean simple, Boolean offsetsAreCorrect, RandomIndexWriter iw) in F:\Projects\lucenenet\src\Lucene.Net.TestFramework\Analysis\BaseTokenStreamTestCase.cs:line 929
   at Lucene.Net.Analysis.BaseTokenStreamTestCase.AnalysisThread.Run() in F:\Projects\lucenenet\src\Lucene.Net.TestFramework\Analysis\BaseTokenStreamTestCase.cs:line 735
Result StandardOutput:
Exception from random analyzer:
charfilters=
  HTMLStripCharFilter([System.IO.StringReader])
  PatternReplaceCharFilter([a, , Lucene.Net.Analysis.CharFilters.HTMLStripCharFilter])
tokenizer=
  ReversePathHierarchyTokenizer([Lucene.Net.Analysis.Core.TestRandomChains+CheckThatYouDidntReadAnythingReaderWrapper, 蒫, 醙, 24])
filters=
  CJKBigramFilter([ValidatingTokenFilter@368e0a2 term=,bytes=[],startOffset=0,endOffset=0,positionIncrement=1,type=word,positionLength=1, 83])
  IndonesianStemFilter([ValidatingTokenFilter@25a042e term=,bytes=[],startOffset=0,endOffset=0,positionIncrement=1,type=word,positionLength=1,keyword=False, false])
  HunspellStemFilter([ValidatingTokenFilter@20aee5b term=,bytes=[],startOffset=0,endOffset=0,positionIncrement=1,type=word,positionLength=1,keyword=False, Lucene.Net.Analysis.Hunspell.Dictionary, true, false])
  LatvianStemFilter([ValidatingTokenFilter@6f125a term=,bytes=[],startOffset=0,endOffset=0,positionIncrement=1,type=word,positionLength=1,keyword=False])
offsetsAreCorrect=False
Result StandardError:	TEST FAIL: useCharFilter=True text='smfmwktkf \\'\\'

Note we now have an azure-pipelines.yml configuration file in our repository that anyone can use to setup a build pipeline to see the tests run on Windows, macOS and Linux by setting up a free Azure DevOps account. If you create a public project to run the tests in, it will take roughly an hour to see the test results (a private project will take significantly longer on the free subscription because they only provide a single parallel job).
Repeatability
The tests that fail are now marked with the AwaitsFixAttribute. The default behavior of the test framework is to ignore the tests that are marked with this attribute. Any of the following changes can be made to make the AwaitsFixAttribute tests run so they can be debugged.

Comment the AwaitsFixAttribute on the test in question.
Add a file named lucene.testsettings.json in the directory of the test project or a parent directory of the test project with the content:

 {
  "tests": {
    "awaitsfix": "true"
  }
}

To specify a specific target framework to run the tests on, edit the TestTargetFramework.props file. Note that the last property with a given name wins, so to test on .NET Core 3.1 instead of .NET 5, change the file as follows:
Before
    <!--<TargetFramework>net48</TargetFramework>-->
    <!--<TargetFramework>netcoreapp2.1</TargetFramework>-->
    <!--<TargetFramework>netcoreapp3.1</TargetFramework>-->
    <TargetFramework>net5.0</TargetFramework>

After
    <!--<TargetFramework>net48</TargetFramework>-->
    <!--<TargetFramework>netcoreapp2.1</TargetFramework>-->
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <!--<TargetFramework>net5.0</TargetFramework>-->

NOTES

If you want to work on one of these issues, please open a new GitHub issue and make it refer to this one, so your efforts aren't duplicated by someone else. Assign the issue to yourself. If you can't work out the issue, make sure that you unassign yourself and comment on it below that it is still unresolved and up for grabs.
Sometimes problems can be spotted just by comparing the Lucene 4.8.0 code against Lucene.Net 4.8.0 code.
The code should be checked to make sure there were no translation problems from Java to C#. This may be easier than it sounds, as you can type phrases like "java HashMap equivalent c#" into Google to find the answers easily.
We can change the code to properly match the behavior of Java, but no cheating by changing the conditions of the test! Unless, of course, the test conditions were translated to C# wrong, which has been known to happen.
Random failures can often be made to happen more frequently by adding a RepeatAttribute to the top of the test. Try running 30 or 40 times and you will see the failure much more often.
If you find a solution to make the test pass, please open a PR on GitHub or alternatively post the solution here so we can try it ourselves.
If you get the same warm fuzzy feeling we do when we make a test green, feel free to fix another one.

Also, let us know if you find any failing test that is not on this list.
JIRA link - [LUCENENET-619] created by nightowl888

FYI, after many days of effort, we finally found the cause of the TestRandomStrings/TestRandomHugeStrings failures, in ICU4N. We should be able to get these tests re-enabled once an ICU4N release with https://github.com/NightOwl888/ICU4N/pull/96 is released.

With the last remaining test failures split out as separate items (#1044 and #271) and #1045 re-enabling the TestICUFoldingFilterFactory test, I'm going to close this issue as completed. Any new test failures should have their own issues filed.


support custom tenant header and write endpoint

https://github.com/open-cluster-management/backlog/issues/18022
Signed-off-by: Marco<EMAIL_ADDRESS>

/lgtm


🐛 [Bug] Default dtype for torch_tensorrt.Input is set to _enums.dtype.unknown

Bug Description
When constructing a torch_tensorrt.Input object, if the dtype is not specified it is set to _enums.dtype.unknown, while the documentation states that the default dtype is float32.
Relevant lines in source code:
https://github.com/pytorch/TensorRT/blob/deda87bd04e23f0b4cc7cb20bf9be6bd76fcf743/py/torch_tensorrt/_Input.py#L33-L35
Documentation:
https://github.com/pytorch/TensorRT/blob/deda87bd04e23f0b4cc7cb20bf9be6bd76fcf743/docs/v1.3.0/_modules/torch_tensorrt/_Input.html#L384
To Reproduce
Steps to reproduce the behavior:
import torch_tensorrt

input_spec = torch_tensorrt.Input(shape=[1, 1, 32, 32])

assert input_spec.dtype == torch_tensorrt._C.dtype.unknown

Expected behavior

The Input object should have float32 dtype as declared in the docs, or the docs should be changed to reflect the actual behavior.
Environment

Build information about Torch-TensorRT can be found by turning on debug messages

Torch-TensorRT Version (e.g. 1.0.0): 1.3.0
PyTorch Version (e.g. 1.0): 1.13.1+cu117
CPU Architecture:
OS (e.g., Linux):
How you installed PyTorch (conda, pip, libtorch, source): Installed from torch_tensorrt
Build command you used (if compiling from source):
Are you using local sources or building from archives:
Python version: 3.10.6
CUDA version:
GPU models and configuration:
Any other relevant information:

Hello - currently, the frontend Input object assigns the data type to unknown to indicate the user has not specified a type. The default type of Float is then set later in this function (line 40):
https://github.com/pytorch/TensorRT/blob/3467511e8e1e8d60ac1a45ec84b6a5be0cce9cab/py/torch_tensorrt/csrc/tensorrt_classes.cpp#L26-L45
There is currently an issue for centralizing defaults (#1644), which is intended to put all such defaults in a single location.

Hi, thank you for your response. Our initial problem was that the conversion failed with the following error
RuntimeError: [Error thrown at core/util/trt_util.cpp:296] Expected type to be true but got false
Unsupported ATen data type Double

which lead us to conclude that the bug was caused by the unknown data type.
After your comment we investigated a bit more and found out that the unknown data type is not the problem, as you correctly stated. The error is given in a specific situation:

no dtype is specified when constructing the torch_tensorrt.Input object
an arithmetic operation (division, multiplication, subtraction, addition) is carried on with the graph's input tensor and a python float constant (which is actually a double in Cpython)

In this case the compile step infers the input tensor dtype as double, which then causes the error reported above (Unsupported ATen data type Double).
An excerpt of the graph level output log where this behavior is observed is reported here:
GRAPH: [Torch-TensorRT] - Input to node: %x.1 : Tensor = prim::Param()
GRAPH: [Torch-TensorRT] - Input outputs a Tensor
GRAPH: [Torch-TensorRT] - Input to node: %10 : Tensor = prim::Constant[value={255}]() # /code/smallpixels.core/src/smallpixels/core/networks/server/upscaler/residual_upscaler.py:211:0
GRAPH: [Torch-TensorRT] - Input outputs a Tensor
GRAPH: [Torch-TensorRT] - Input is a constant
GRAPH: [Torch-TensorRT] - Found that constant tensor has type: Double
GRAPH: [Torch-TensorRT] - Estimated input type is Double
DEBUG: [Torch-TensorRT] - Found 1 inputs to graph
DEBUG: [Torch-TensorRT] - Handle input of debug name: x.1
DEBUG: [Torch-TensorRT] - Paring 0: x.1 : Input(shape: [1, 1, 32, 32], dtype: Float32, format: NCHW\Contiguous\Linear)
DEBUG: [Torch-TensorRT] - Found 1 inputs to graph
DEBUG: [Torch-TensorRT] - Handle input of debug name: x.1
DEBUG: [Torch-TensorRT] - In MapInputsAndDetermineDTypes, the g->inputs() size is 1, CollectionInputSpecMap size is1
INFO: [Torch-TensorRT] - Since input type is not explicitly defined, infering using first tensor calculation
  Inferred input x.1 has type Double
Traceback (most recent call last):
  File "trt_issue.py", line 51, in <module>
    trtm = torch_tensorrt.compile(sm, **compile_spec)
  File "/usr/local/lib/python3.8/dist-packages/torch_tensorrt/_compile.py", line 125, in compile
    return torch_tensorrt.ts.compile(
  File "/usr/local/lib/python3.8/dist-packages/torch_tensorrt/ts/_compiler.py", line 136, in compile
    compiled_cpp_mod = _C.compile_graph(module._c, _parse_compile_spec(spec))
RuntimeError: [Error thrown at core/util/trt_util.cpp:296] Expected type to be true but got false
Unsupported ATen data type Double

See the complete output log in this gist.
The following code reproduces this case. A very simple nn.Module instance is created, where the forward method just divides the input tensor (this is important: dividing an intermediate result tensor does not cause the problem) by a constant:
import torch_tensorrt
from torch import nn
import torch

class TestModule(nn.Module):
    def forward(self, x):
        return x / 255.0

x = torch.rand(1, 1, 32, 32).cuda()
m = TestModule()
m.eval().cuda()

sm = torch.jit.trace(m, x)

compile_spec = {
    "inputs": [torch_tensorrt.Input(shape=[1, 1, 32, 32])],
    "enabled_precisions": torch.float16,
    "truncate_long_and_double": True,
    "require_full_compilation": True,
}

with torch_tensorrt.logging.graphs():
    trtm = torch_tensorrt.compile(sm, **compile_spec)

trtm(x)

Hello - thank you for the code sample, I am able to reproduce the behavior you have described. After discussing with @narendasan, an updated description of the Unknown (unspecified) data type for input tensors is:

Unknown implies the user has not specified an input type, so the compiler first attempts to determine what that type should be based on its usage, as you had mentioned. If this step fails to determine what the type should be, then the compiler will default the input type to Float32. If the user disagrees with the inferred type, then a user-specified type (dtype=torch.float) will override any inferred data types. In the above case, the compiler inferred the data type of the input should be Double, which is an invalid input type for Torch-TRT currently, yielding the error.

The code snippet which infers the data type and performs the user-specified overrides as necessary, is here:
https://github.com/pytorch/TensorRT/blob/835abf0f32a5e3bbcf7ec092be5cc051393a1d08/core/compiler.cpp#L315-L319

Closing, reopen if there are still issues

@chaoz-dev Tagging myself so I can find this again.


Messages containing dates produce incorrect GO syntax

message MyObj {
    1 -> date Start;
    2 -> date End;
}

Results in code such as:
iohelp.WriteInt64Bytes(buf[at:], (*bbp.Start.UnixNano()/100))
iohelp.WriteInt64Bytes(buf[at:], (*bbp.End.UnixNano()/100))
golangci-lint run my_obj.go
level=error msg="[linters context] typechecking error: my_obj.go:87:27: invalid operation: cannot indirect bbp.Start.UnixNano() (value of type int64)"
level=error msg="[linters context] typechecking error: my_obj.go:95:27: invalid operation: cannot indirect bbp.End.UnixNano() (value of type int64)"

On it, thank you for the report.

Also, is the "tick" concept and hence the division by 100 really necessary?

Unfortunately the 'tick' logic is necessary to keep compatibility with the standard.  Otherwise generated messages could fail to be parsed by other bebop parsers.
I'm not particularly fond of it myself.

@200sc makes sense. Thanks for the quick fix.


Enable HTTP Application Routing on existing AKS

Hello is it possible to enable this add-on for an existing AKS?

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

ID: 51a32f9e-c92f-412b-d460-567f3c542b98
Version Independent ID: fad073ab-a376-1535-7bc4-deaca1d98dd9
Content: HTTP Application Routing add-on on Azure Container Service (AKS)
Content Source: articles/aks/http-application-routing.md
Service: container-service
GitHub Login: @lachie83
Microsoft Alias: laevenso

Thanks for the feedback! We are currently investigating and will update you shortly.

@flmarins I believe you need to add the correct files and redeploy the AKS.
@lachie83 or @neilpeterson could either of you confirm?

@lachie83, I have tought of this option, just wasn't sure it would work. So yes I think it would at least worth metioning that it can be achieved by an incremental template :).
Thanks for the answer.

Thanks @lachie83! I will assign to you while you update the doc. Appreciate the help :)

@flmarins
az aks enable-addons -a http_application_routing -g $RESOURCE_GROUP_NAME -n $AKS_CLUSTER_NAME
I just did this :)

As @berndverst notes, this can now be done with the Azure CLI. I have created a PR to update the doc, which should merge and publish this afternoon.
#in-progress


Suggestion - install 7-Zip on Windows by default to make Composer faster

I'm trying to solve a problem where Composer is several times slower on Windows. For example, on Ubuntu it takes 5-7 seconds to install the dependencies without cache.
On Windows it takes over a minute.
I don't know what's the underlying issue, but the creator of Composer (Jordi Boggiano) suggested we might try installing 7-Zip on Windows to speed it up.
I don't know how to install it in CLI when running in GitHub Actions, so I can't create a proof of concept and a benchmark. If you could tell me how to install 7-Zip so that Composer can see 7z in PATH, we could test if it makes sense to install it for everyone in setup-php.
Thanks.

Oh nevermind, it's probably installed already and Composer is still slow: https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md#tools


Allow DerbyTester to connect to multiple schemas and run liquibase against them

Currently one can only connect to one in-memory Derby instance in unit tests, since DerbyTester does not allow to specify a particular schema, it just has a db() method with no parameters to specify database connection parameters, which would allow to choose a Derby schema by using separate users:
@BQTestTool(BQTestScope.GLOBAL)
    static final DbTester db = DerbyTester.db()
        .initDBWithLiquibaseChangelog(...);

Maybe sth like
@BQTestTool(BQTestScope.GLOBAL)
    static final DbTester dbSchema1 = DerbyTester.db("schema1")
        .initDBWithLiquibaseChangelog(...);

@BQTestTool(BQTestScope.GLOBAL)
    static final DbTester dbSchema2 = DerbyTester.db("schema2")
        .initDBWithLiquibaseChangelog(...);

The DerbyTester would then have to make sure the given Schema is created and used.

I think you can still run multiple sets of migrations against a single Derby DB by prepending schemas to the table names (i.e. namespacing done in SQL, e.g. create table "s1"."t1" ()).
Also you can create multiple DerbyTesters pointing to different DBs via a public constructor:
@BQTestTool(BQTestScope.GLOBAL)
static final DbTester dbSchema1 = new DerbyTester(new File("some/dir"))
   .initDBWithLiquibaseChangelog(...);

But yeah, we should probably provide a complimentary db(File) and db(String) methods for symmetry

I found this after posting the issue above: https://bootique.io/docs/2.x/bootique-jdbc-docs/#_connecting_dbtester_with_test_bqruntime. I can't quite wrap my head around it yet, but this seems to say, that I can have one DbTester which maintains multiple database definitions:
"A single DbTester can be used to bootstrap multiple BQRuntimes or multiple DataSources within a given runtime".
What is the dataSourceName parameter to moduleWithTestDataSource() referring to? Is it the name of a datasource in config.yml?
If so, how would I tell the DerbyTester to apply different liquibase changelogs to the two data sources?

@BQApp
static final BQRuntime myDb1App = Bootique.app()
        .autoLoadModules()
        .module(tester.moduleWithTestDataSource("mydb1"))
        .createRuntime();

@BQApp
static final BQRuntime mydb2App = Bootique.app()
        .autoLoadModules()
        .module(tester.moduleWithTestDataSource("mydb2"))
        .createRuntime();

...
tester
        .initDBWithLiquibaseChangelog("classpath:classpath:changelog1.yml", ???)
        .initDBWithLiquibaseChangelog("classpath:classpath:changelog2.yml", ???);

Also, the sample code above seems to bootstrap multiple BQRuntimes, but how would I bootstrap multiple DataSources within a given runtime?


Add attribution property to schema spec

I added attribution as an optional property, as it's unknown for some endpoints. When providing attribution data, IMHO both license and name should be mandatory – even for CC0 it's common to note who is waiving their rights. The homepage doesn't seem as important to me, so I made it optional
@vkrause could you check whether this is in line with your intentions? If it is, please merge.

Does this mean that explicitly specifying that an endpoint returns proprietary data is impossible?

Does this mean that explicitly specifying that an endpoint returns proprietary data is impossible?

Yes. Right now that's not possible, though it might be useful to have an isProprietary field for that purpose.
How about allowing isProprietary: true instead of license: "..."?
Also, I noticed just now that attribution.name and .name might be redundant. So we could make attribution.name optional and have clients resort to .name if it's missing.

Yes. Right now that's not possible, though it might be useful to have an isProprietary field for that purpose.
How about allowing isProprietary: true instead of license: "..."?
Also, I noticed just now that attribution.name and .name might be redundant. So we could make attribution.name optional and have clients resort to .name if it's missing.

How about allowing isProprietary: true instead of license: "..."? (i.e., an attribution object must have either an isProprietary or a license property)

👍

How about allowing isProprietary: true instead of license: "..."? (i.e., an attribution object must have either an isProprietary or a license property)

👍

Making the fact explicit that the data is proprietary and making the attribution information mandatory is a good idea IMHO.
KPublicTransport currently omits the attribution data in the proprietary case, but that risks potentially missing information for Open Data endpoints.

Making the fact explicit that the data is proprietary and making the attribution information mandatory is a good idea IMHO.
KPublicTransport currently omits the attribution data in the proprietary case, but that risks potentially missing information for Open Data endpoints.


feat: add eth_addr_checksum validation, update eth_addr

Rationale

ethereum addresses are derived from a public key (the last 20 bytes). The network accepts any case insensitive address as long as it is a 40 char alphanumeric (When the last 20 bytes are converted to hex). It is 0x prefixed so that it becomes 42 in length, hence the current eth_addr implementation is modified to reflect this.
Checksum-ing is optional on ethereum and is a way of typo checking the address hence this is introduced as a new validation i.e. eth_addr_checksum.

refs:

https://github.com/ethereum/go-ethereum/blob/master/crypto/crypto.go#L275
https://goethereumbook.org/en/wallet-generate/
https://goethereumbook.org/en/address-check/

other lib implemntations:

https://github.com/chaintool-py/funga-eth/blob/master/funga/eth/encoding.py#L42

Fixes Or Enhances
Fixes #1073
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

@go-playground/validator-maintainers

Coverage: 74.195% (+0.004%) from 74.191% when pulling e2aaf541d370d8a7994ba9ed2628cc69862b04de on kamikazechaser:sohail/eth-addr into 8f07b0368280d9fc70b4ffd3708b31427bbc286d on go-playground:master.


Present UIViewController on AMSlideMenuRightMenuViewController

First thanks for this amazing library! Also i have one question. Is it possible to present a viewcontroller above the right menu like in the pictures below, that when selecting a tableviewcell it opens the contentsegue as a pushsegue without filling the screen. Hope you can help. Thanks in advance.

Unfortunately, AMSlideMenu doesn't support functionality like that.


Permute Type spawn rule component has incorrect type for guaranteed_count

guaranteed_count field is documented as string, but should be integer.

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

ID: b8ba0269-f5c8-888c-1069-4c07e842ec85
Version Independent ID: b8ba0269-f5c8-888c-1069-4c07e842ec85
Content: Entity Documentation - minecraft:permute_type
Content Source: creator/Reference/Content/EntityReference/Examples/Definitions/NestedTables/permute_type.md
Product: gaming
GitHub Login: @docsbryce
Microsoft Alias: v-bbortree

Thanks for reaching out! The documentation will be updated with the next release.


fix rewritten plan output order is not correct

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall


feat: regtest build

Description
This PR adds support to build an app variant having regtest as default bitcoin network.
Aside to the default network, the regtest variant has:

a different name: Bitkit Regtest
a different id:

Android: to.synonym.bitkit.wallet.regtest
iOS to.synonym.bitkit.regtest

a monochrome icon

Considerations

It is expected have a .env.production file with the corresponding configurations.
It is expected if an .env.production.local already exists, that it doesn't include required configs for building.
This is because of the node scripts that are creating a temp file with the same name, overriding only the value of WALLET_DEFAULT_SELECTED_NETWORK.
We could drop the node scripts and simply change the ENV var when creating the manual builds, this could mitigate issues if there are other relevant configs in the local prod env file.
Given this isn't a very repetitive process, it won't be too much work added to the manual process of creating the internal releases.

To Test
Android prerequisite: You should have adb in your path.
1⃣ Regtest Android

Open a terminal in the root repo directory
Run yarn bundle:regtest
After completion, open an emulator from Android Studio
In terminal run adb install android/app/build/outputs/apk/regtest/release/app-regtest-release.apk
Expect to have the app Bitkit Regtest installed on the emulator
Open the app, skip intro, create a New Wallet
Tap the Cog icon to open Settings
Tap the Cog illustration multiple times until you see Dev Options Enabled popup
Tap Advanced
Expect Bitcoin Network to be set to Regtest

2⃣ Mainnet Android

Run yarn bundle in the same terminal from previous step
Await completion
run adb install android/app/build/outputs/apk/mainnet/release/app-mainnet-release.apk
Expect to have the Bitkit app installed on the emulator
Open the app, skip intro, create a New Wallet
Tap the Cog icon to open Settings
Tap the Cog illustration multiple times until you see Dev Options Enabled popup
Tap Advanced
Expect Bitcoin Network to be set to Mainnet

3⃣ Regtest iOS

Run yarn bundle:regtest:ios in repo root dir
Open the workspace in XCode, switch to the bitkit.regtest scheme

Note:
Additional 1-time setup is required as described in this medium post

need to register the new bundle id, get certificates, etc
also might need to create a separate app in TestFlight App Store Connect

Build the app for release
Verify using the same flow as for Android that the Bitcoin Network is Regtest
Verify the two apps (mainnet, bitkit scheme) + (regtest, bitkit.regtest scheme) can be installed side by side
Verify the bitkit app has the Bitcoin Network Mainnet (might need to delete the main.jsbundle from the ./ios/ dir.

➕ Other configurations

Ensure yarn start can still run build and run the app on Android / iOS
Ensure yarn android & yarn ios still works

Linked Issues/Tasks
https://app.asana.com/0/0/1205821036778041/f
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactoring (improving code without creating new functionality)

Tests

[ ] Detox test
[ ] Unit test
[x] No test

Screenshot / Video
N/a - build configs.
QA Notes
N/a - build configs.

Abandoned in favour of new PR from main repo instead of fork.


[dv/otp] Low condition coverage

Description
The low condition coverage might due to unreachable states inside different partitions.
Current plan:

[x] Run OTP UNR.
[ ] Review and see if condition coverage can be above 90%

The main issue for condition coverage is from the prim_secded_inv_72_64 modules . From the UNR results (https://github.com/lowRISC/opentitan/pull/17378) they are proven to be unreachable.
I will find a clean way to exclude these unreachables.

I will check tonight's nightly regression and see if we can close it.

all coverage above 90%. close this issue


SVtyper with long reads

So - I'm trying to generate SV frequencies from long read data (ONT) aligned with a split-read aligner (BWA MEM) using SVtyper, but I keep getting an error:
Error:
Traceback (most recent call last):
File "/home/timp/Code/svtyper/svtyper", line 1078, in
sys.exit(main())
File "/home/timp/Code/svtyper/svtyper", line 1070, in main
args.debug)
File "/home/timp/Code/svtyper/svtyper", line 767, in sv_genotype
sample = Sample(bam_list[i], spl_bam_list[i], num_samp)
File "/home/timp/Code/svtyper/svtyper", line 709, in init
self.name = bam.header['RG'][0]['SM']
KeyError: 'RG'
Command:
##BWAMEM
~/Code/bwa/bwa mem -x ont2d /mithril/Data/NGS/Reference/human/hg19.fa ${fastq}_BC${bc}.fastq.gz >${outdir}/${prefix}.bwa.sam
samtools view -b -S ${outdir}/${prefix}.bwa.sam | samtools sort - ${outdir}/${prefix}.bwa
samtools index ${outdir}/${prefix}.bwa.bam

##From LUMPY readme

samtools view -b -F 1294 -S ${outdir}/${prefix}.bwa.sam >${outdir}/${prefix}.bwa.discordants.unsorted.bam

# Extract the split-read alignments
samtools view -h -S ${outdir}/${prefix}.bwa.sam \
    | ~/Code/lumpy-sv/scripts/extractSplitReads_BwaMem -i stdin \
    | samtools view -Sb - \
    > ${outdir}/${prefix}.bwa.splitters.unsorted.bam

# Sort both alignments
samtools sort ${outdir}/${prefix}.bwa.discordants.unsorted.bam ${outdir}/${prefix}.bwa.discordants
samtools sort ${outdir}/${prefix}.bwa.splitters.unsorted.bam ${outdir}/${prefix}.bwa.splitters

samtools index ${outdir}/${prefix}.bwa.splitters.bam

~/Code/lumpy-sv/bin/lumpy \
    -mw 4 \
    -tt 0 \
    -sr id:${prefix}.bwa,bam_file:${outdir}/${prefix}.bwa.splitters.bam,back_distance:10,weight:1,min_mapping_threshold:20 \
    > ${outdir}/${prefix}.bwa.vcf

cat ${outdir}/${prefix}.bwa.vcf | \
    ~/Code/svtyper/svtyper \
    -B ${outdir}/${prefix}.bwa.bam \
    -S ${outdir}/${prefix}.bwa.splitters.bam \
    > ${outdir}/${prefix}.bwa.gt.vcf

I have no idea how svtyper will react to long-reads in general, but it looks like that problem is a result of improper read groups in your BAM. The easiest way to add readgroup ID and SM information is with bamaddrg

Ok - I have added readgroup ID and SM information by adding an -R tag to my bwa command, but now I get a different error: "IndexError: list index out of range"
Error:
Traceback (most recent call last):
File "/home/timp/Code/svtyper/svtyper", line 1078, in
sys.exit(main())
File "/home/timp/Code/svtyper/svtyper", line 1070, in main
args.debug)
File "/home/timp/Code/svtyper/svtyper", line 767, in sv_genotype
sample = Sample(bam_list[i], spl_bam_list[i], num_samp)
File "/home/timp/Code/svtyper/svtyper", line 734, in init
self.lib_dict[name].calc_insert_hist()
File "/home/timp/Code/svtyper/svtyper", line 689, in calc_insert_hist
med = median(valueCounts)
File "/home/timp/Code/svtyper/svtyper", line 567, in median
v = valueList[i]
IndexError: list index out of range
Code:
##BWAMEM
~/Code/bwa/bwa mem -R "@RG\tID:${fastq}_BC${bc}\tSM:BC${bc}\tPL:ONT" -x ont2d /mithril/Data/NGS/Reference/human/hg19.fa ${fastq}_BC${bc}.fastq.gz >${outdir}/${prefix}.bwa.sam
samtools view -b -S ${outdir}/${prefix}.bwa.sam | samtools sort - ${outdir}/${prefix}.bwa
samtools index ${outdir}/${prefix}.bwa.bam

##From LUMPY readme

samtools view -b -F 1294 -S ${outdir}/${prefix}.bwa.sam >${outdir}/${prefix}.bwa.discordants.unsorted.bam

# Extract the split-read alignments
samtools view -h -S ${outdir}/${prefix}.bwa.sam \
    | ~/Code/lumpy-sv/scripts/extractSplitReads_BwaMem -i stdin \
    | samtools view -Sb - \
    > ${outdir}/${prefix}.bwa.splitters.unsorted.bam

# Sort both alignments
samtools sort ${outdir}/${prefix}.bwa.discordants.unsorted.bam ${outdir}/${prefix}.bwa.discordants
samtools sort ${outdir}/${prefix}.bwa.splitters.unsorted.bam ${outdir}/${prefix}.bwa.splitters

samtools index ${outdir}/${prefix}.bwa.splitters.bam

~/Code/lumpy-sv/bin/lumpy \
    -mw 4 \
    -tt 0 \
    -sr id:${prefix}.bwa,bam_file:${outdir}/${prefix}.bwa.splitters.bam,back_distance:10,weight:1,min_mapping_threshold:20 \
    > ${outdir}/${prefix}.bwa.vcf

cat ${outdir}/${prefix}.bwa.vcf | \
    ~/Code/svtyper/svtyper \
    -B ${outdir}/${prefix}.bwa.bam \
    -S ${outdir}/${prefix}.bwa.splitters.bam \
    > ${outdir}/${prefix}.bwa.gt.vcf

Ok, this may be a larger problem. Are you reads single end or paired end? SVTyper needs paired reads to calculate an insert size distribution

They are single end reads.  I put (perhaps naively) the fully aligned bam into the -B, and the split reads (extracted with "extractSplitReads_BwaMem" from lumpy) into -S
What I'm trying to get out is the frequency of SV versus a background wild-type from a cancer sample - why do I need paired end?  From a quick look at your code, it looks like you are calculating coverage in a region and determining number of breakpoints detected vs. depth of coverage?

Right, that's an accurate description of the tool, but unfortunately SVTyper will not work for your data without modifications. It expects paired-end reads because it was designed for Illumina short data, but you could probably fork it to operate on single-ends alone by removing the calls to calc_insert_hist() and count_pairedend()

I actually plan to just be simpler than that for now - and use bedtools
just to estimate coverage in the region - I'm using amplicons so I know
where I'm looking.
That said, it may be an advantage given the recent work on long single read
stuff (PacBio, ONT) to have an option or the ability to deal with this in
SVtyper?  Especially as long read offers many advantages for SV
identification/typing.
W
On Tue, Jun 9, 2015 at 3:34 PM, Colby Chiang<EMAIL_ADDRESS>wrote:

Right, that's an accurate description of the tool, but unfortunately
SVTyper will not work for your data without modifications. It expects
paired-end reads because it was designed for Illumina short data, but you
could probably fork it to operate on single-ends alone by removing the
calls to calc_insert_hist() and count_pairedend()
—
Reply to this email directly or view it on GitHub
https://github.com/cc2qe/svtyper/issues/11#issuecomment-110478621.

--
Winston Timp
(410)-417-8467
Assistant Professor of Biomedical Engineering
Johns Hopkins University

Ok, this may be a larger problem. Are you reads single end or paired end? SVTyper needs paired reads to calculate an insert size distribution

Same error with paired-end data.
I'm trying to annotate structural variants vcf from "smrtsv2" (PacBio) with illumina reads for same samble aligned with BWA-mem.


Add npm commandlet

We need a commandlet for npm and support from build commandlet.

It is there. Most likely not perfect yet.
I am happy to receice PRs with improvements.