help with install

trying to pip install getting errors
C:\Users\william>pip install pydfs-lineup-optimizer
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Collecting pydfs-lineup-optimizer
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/pydfs-lineup-optimizer/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/pydfs-lineup-optimizer/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/pydfs-lineup-optimizer/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/pydfs-lineup-optimizer/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/pydfs-lineup-optimizer/
Could not fetch URL https://pypi.org/simple/pydfs-lineup-optimizer/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pydfs-lineup-optimizer/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
ERROR: Could not find a version that satisfies the requirement pydfs-lineup-optimizer (from versions: none)
ERROR: No matching distribution found for pydfs-lineup-optimizer

i now have newest version installed


chore(main): release siyuan-plugin-publisher 1.22.0

:robot: A new release will be created
1.22.0 (2024-11-07)
Features

add halo v29 warning (20ad98d)
add halo v29 warning (e84cdc9)
change QQ group (13babdc)
support read halo tags (4afd364)

Bug Fixes

#1394 add halo web (deaf333)
#1394 add halo web (0ca7e7f)
#1394 add halo web (1bb6d25)
#1394 add halo web (0710295)
#1394 add halo web (bf843ad)
deps: bump uuid from 9.0.1 to 10.0.0 (9c27920)
pnpm version error (b8a99c1)
修复 halo2 发布结果为 markdown显示问题。 (0e836e7)

Miscellaneous

fix dev tools (b2eb808)
update deps (9afbdbc)
update docs (bddc12d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/terwer/siyuan-plugin-publisher/releases/tag/siyuan-plugin-publisher-v1.22.0 :sunflower:


lateinit property cachedTypeface has not been initialized Emoji

Describe the bug
I am trying to integrate the emoji library in my kotlin project but I am getting the "lateinit property cachedTypeface has not been initialized" error

@Kuppa, Can you show some code examples ?


openlegaldata wrong file names

In the openlegaldata dataset, the file names are listed as v1.jsonl.gz, v2.jsonl.gz. However, the latest dump on the site is called cases.jsonl.gz. In fact, there don't seem to be a single v1/v2 file anywhere on the download page.
Either the location of these v1/v2 files should be made public or the code should be modified to work on the officially downloadable dump.

The version of Open Legal Data implemented here is different from the one that is publicly (that's why the availability is set to "on request). This version cannot be currently shared publicly due to legal reasons (see here). As soon as this is resolved we will make it available for download.


CI: Adds auto-label Github workflow

This PR adds a new Github worfklow that labels opened or edited PRs based on their content..

I think we should not depend on the branch name but rather the PR itself

I think we should not depend on the branch name but rather the PR itself

Why is that? We are using the Gitflow workflow and agreed to have a controlled vocabular for naming the branches.


Table scoped instruction incorrect

Just as I stated in the subject, the instructions for table scoped command do not work. After re-importing and publishing, it's still only visible in the original app. If I export the solution again it shows the appmoduleid node that I just removed.
I did find that exporting the command and following the instructions but deleting the command directly from D365 before re-importing seems to work.
There should also be a highlighted note drawing attention to the fact that after a command is converted to be table scoped (and I assume global scoped too), it can no longer be modified in the Command Editor UI.

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

ID: 07212979-c625-2ab8-88c4-1c48e612e216
Version Independent ID: 07212979-c625-2ab8-88c4-1c48e612e216
Content: Commanding scopes - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/commanding-scopes.md
Service: powerapps
Sub-service: mda-maker
GitHub Login: @caburk
Microsoft Alias: caburk

Thanks for your comment, @cfharp. This issue has been assigned to the doc author for review.

@cfharp thank you very much for flagging this issue. An important step was missing in this documentation. You also need to change the value of the "appaction uniquename" property within the XML prior to re-importing the solution. Any small edit is sufficient. This will also prevent the 2nd issue you experienced (issue editing using command designer after re-importing the solution).
I'm updating the docs to include this step.


Cannot reference TSC v1.8 compilation

I'm not sure but it looks like an error to me:
I don't seem to be able to reference a TypeScript file transpiled with TSC v1.8.
I have set up a repository with a sample project and a description of the errors I get when I try to reference the transpiled JavaScript type definition file:

all.d.ts is not an external module but just a .d.ts file that contains declarations for three ambient modules.
declare module "_Base" {
    export default class _Base {
        protected element: HTMLElement;
        private _var;
        constructor(element: HTMLElement);
    }
}
declare module "Derived" {
    import _Base from "_Base";
    export default class Derived extends _Base {
        constructor(element: HTMLElement);
    }
}
declare module "Manager" {
    import _Base from "_Base";
    export default class Manager {
        private _provider;
        constructor(provider: _Base);
    }
}

as a consequence:

it cannot be imported as is since the file itself is not a module
it can be referenced to bring these 3 modules into scope.

// main.ts

/// <reference path="../../output/headers/all.d.ts" />
import Derived from "Derived";
import Manager from "Manager";

const d: Derived = new Derived(null);
const m: Manager = new Manager(d);

Thanks for enlightening me! :cake:
Yet, I'm surprised about the syntax. I've not seen this before:
import Derived from "Derived";
import Manager from "Manager";

Would you mind pointing me to where this is documented? I want to understand how this works.

you can find Module documentation at https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Modules.md

The suggested solution doesn't appear to work. It creates false require() statements in the JavaScript file:

The suggested solution doesn't appear to work. It creates false define() statements in the JavaScript file:

what does "false define()" mean? can you provide the expected output?


Add tags to the documentation

Use mdbook-tag. This crate is un-maintained but provides what we need with one exception: the ./tags.html page is a bit too simplistic.
If we go in that direction we will need to:

update mdbook-tag to use the lastest version of mdbook
possibly, improve the ./tags.html page
agree on a list of tags
add a concepts pages that describes these tags/themes.

Proposed changes

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[x] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

@didier-wenzek I had a look at it and it should provide some value to users, so I would agree with going ahead with this. The mdbook-tag style is also fairly similar to other static markup tools like docusaurus, so there should not be any "feature lock-in".
Regarding the list of tags, we should align with the GitHub labels, though without the theme: prefix.


mint dialog overflow issue fixed

Description
Fixed overflow issue on mint dialog.
Fixes Jira Ticket #
AX-784
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Is this a UI Change? If so please include screenshot of before and after states below
yes
after

How Has This Been Tested?
yes
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have assigned 2 reviewers to check my work
[x] I have commented my code, particularly in hard-to-understand areas
[] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[] I have added tests that prove my fix is effective or that my feature works
[] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@durduman fixed


"Swap Icon" Functionality in Convert Section

Describe the bug
When attempting to use the "Swap icon" feature within the "Convert section" of the app, I'm unable to see any swapping action occurring. It's unclear whether this is a bug, a missing feature, or if it's intentional.
To Reproduce
Steps to reproduce the behavior:

Navigate to the "Convert section" of the app.
Click on the "Swap icon".
Observe that the icon does not make any changes.

Expected behavior
The "Swap icon" feature should visually swap the currencies in the "Convert section" when clicked.
Screenshots

Smartphone (please complete the following information):

Device: Pixel_API (Emulator)

Update- I just downloaded the Blink app from the app store, and I couldn't find a Convert Section in the app. Has the release for the same not been made yet, and are we still working on it?


Embed Google Material Design Icons

As a developer
I want to included the Google Icons in the source
So that we don't have a dependency with Google at runtime
Background:
We currently retrieve the Icons from https://fonts.googleapis.com/css?family=Material+Icons+Outlined&display=block
In some environments that isn't allowed, because it's a external source. (‘Content Security Policy’ Error)
Some info to check is
http://google.github.io/material-design-icons/#icon-font-for-the-web
https://github.com/google/material-design-icons/tree/master/font
https://developers.google.com/web/fundamentals/security/csp

@ca-d is this some thing to summit upstream to OpenSCD?

@ca-d is this some thing to summit upstream to OpenSCD?

Absolutely, I hadn't seen this pull request yet, thanks for the mention! We were simply lazy not do bundle both these icons and the Roboto fonts we rely on from the start. We'd be more than happy to accept any work to that effect. These webfonts currently constitute our only reliance on an internet connection at install time as far as I know.

This is currently in the idea phase, we planning to work on this soon.


Error calling Pop on Windows

I'm confused why this is throwing a runtime error when I call VRouter.of(context).pop()

void main() {
  runApp(VRouter(
    initialUrl: HomePage.path,
    routes: [
      VNester(
          path: "/",
          widgetBuilder: (child) {
            return TabbedScaffold(body: child);
          },
          nestedRoutes: [
            VWidget(path: HomePage.path, widget: HomePage()),
            VWidget(path: SettingsPage.path, widget: SettingsPage()),
          ])
    ],
  ));
}

class TabbedScaffold extends StatelessWidget {
  const TabbedScaffold({Key? key, required this.body}) : super(key: key);
  final Widget body;

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        Expanded(child: body),
        Row(
          children: [
            Expanded(
              child: TextButton(
                child: Text("Home"),
                onPressed: () => VRouter.of(context).push(HomePage.path),
              ),
            ),
            Expanded(
              child: TextButton(
                child: Text("Settings"),
                onPressed: () => VRouter.of(context).push(SettingsPage.path),
              ),
            ),
            Expanded(
              child: TextButton(child: Text("<< Back"), onPressed: () => VRouter.of(context).systemPop()),
            ),
          ],
        )
      ],
    );
  }
}

class HomePage extends StatelessWidget {
  static const path = "/home";
  @override
  Widget build(BuildContext context) {
    return Container(
      color: Colors.yellow.shade100,
      child: Text("HOME"),
    );
  }
}

class SettingsPage extends StatelessWidget {
  static const path = "/settings";
  @override
  Widget build(BuildContext context) {
    return Container(
      color: Colors.blue.shade100,
      child: Text("SETTINGS"),
    );
  }
}

Because of this: https://github.com/lulupointu/vrouter/blob/5d6af3cfffbcdaf10b7ee8558920ba72496b16ed/lib/src/vrouter/vrouter.dart#L1273
I did not update the check for desktop platform. I'll do it on Monday.

Nice, you might want to use this package, as .io namespace can't be accessed on web.
https://pub.dev/packages/universal_platform

Yes I know about it but I basically implemented my own universal platform. Plus I don't want to rely on another external package if I don't have to.

I believe there is another use or possibly abuse case as described by the flutter docs. Which is to use Navigator.pop() to close a drawer even on web when the screen is small.
I was about to try the following scaffold key technique?
"https://stackoverflow.com/questions/43807184/how-to-close-scaffolds-drawer-after-an-item-tap"

I know about the Drawer issue, I have given a fix in https://github.com/lulupointu/vrouter/issues/12#issuecomment-790422317
This is not perfect and Navigator.pop should ideally work but I would need to look a bit more into what is happening when the Drawer used. In the meantime the workaround is good enough I think. If this issue appears for other things I might spend more time into it.

Fixed in VRouter 1.1.0+16


⚠ GitLab Server has degraded performance

In 6e3e27f, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11556 ms

Resolved: GitLab Server performance has improved in 1868417.


Error: LuaRocks 2.2.2 bug while trying to install Cassandra 'lua-resty-cassandra' rock

Tools used:

Lua Package Manager: Lua luarocks-2.2.2-win32
Lua interpreter: lua-5.1.5.tar.gz
C Compiler: MinGW
OS: Windows 7 Enterprise Service Pack 1

(Actually same configuration as stated in this tutorial: http://www.thijsschreijer.nl/blog/?p=863)
Behaviour: I opened a cmd console window and install the Cassandra 'lua-resty-cassandra' module.
Error:
C:\Users\ts-ivan.poza>luarocks install cassandra
Installing https://luarocks.org/cassandra-0.5-7.rockspec...
Using https://luarocks.org/cassandra-0.5-7.rockspec... switching to 'build' mode

'"git"' is not recognized as an internal or external command,
operable program or batch file.

Error: LuaRocks 2.2.2 bug (please report at https://github.com/keplerproject/lua
rocks/issues).
... Files (x86)\LuaRocks\2.2\lua\luarocks\fetch\git.lua:19: attempt to index loc
al 'version_string' (a nil value)
stack traceback:
        ... Files (x86)\LuaRocks\2.2\lua\luarocks\fetch\git.lua:19: in function
'git_can_clone_by_tag'
        ... Files (x86)\LuaRocks\2.2\lua\luarocks\fetch\git.lua:63: in function
<... Files (x86)\LuaRocks\2.2\lua\luarocks\fetch\git.lua:33>
        (tail call): ?
        ...gram Files (x86)\LuaRocks\2.2\lua\luarocks\build.lua:207: in function
 <...gram Files (x86)\LuaRocks\2.2\lua\luarocks\build.lua:165>
        (tail call): ?
        ...gram Files (x86)\LuaRocks\2.2\lua\luarocks\build.lua:412: in function
 <...gram Files (x86)\LuaRocks\2.2\lua\luarocks\build.lua:400>
        (tail call): ?
        (tail call): ?
        (tail call): ?
        [C]: in function 'xpcall'
        ...les (x86)\LuaRocks\2.2\lua\luarocks\command_line.lua:208: in function
 'run_command'
        C:\Program Files (x86)\LuaRocks\2.2\luarocks.lua:32: in main chunk
        [C]: ?

'"git"' is not recognized as an internal or external command,
operable program or batch file.

Seems like you don't have git installed (or in your PATH).

@daurnimator , thank you very much for your prompt answer.
You were right. It happened to be that I had Atlassian Source Tree GUI client but nothing in the PATH variable. I just downloaded Msysgit and now got another error.
C:\Users\ts-ivan.poza>luarocks install cassandra
Installing https://luarocks.org/cassandra-0.5-7.rockspec...
Using https://luarocks.org/cassandra-0.5-7.rockspec... switching to 'build' mode

Cloning into 'lua-resty-cassandra'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=No error

Error: Failed cloning git repository.

Probably  I need to set up some network connection parameters.

PRs #387 and #389 have been merged. Both improve the error messages when required tools are not available.
Thanks for reporting.


Class Relationship with itself doesn't render properly

if the class has the relationship to itself it doesn't show it properly.
See the screenshot attached

Unfortunately there is a very big logic in the diagramming framework of how the links are routed, and the only thing I can do to make this "automatically possible" is to rewrite linking code, which may take huge resources.
One option you can use for this, starting from v1.18.0, is to clink on link and drag the pointer out of the class box. Then you can route the link as you need like this:

I think you can just ignore this "self-links" and don't show them at all.
Maybe put a special sign for the property, that it refers to the same
object's instances.
ср, 4 янв. 2017 г. в 2:11, Nikita<EMAIL_ADDRESS>
Unfortunately there is a very big logic in the diagramming framework of
how the links are routed, and the only thing I can do to make this
"automatically possible" is to rewrite linking code, which may take huge
resources.
One option you can use for this, starting from v1.18.0, is to clink on
link and drag the pointer out of the class box. Then you can route the link
as you need like this:
[image: 2017-01-03_201022]
https://cloud.githubusercontent.com/assets/4989256/21617825/aa6e4506-d1f0-11e6-8324-6cfad48f4bec.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-ru/UMLExplorer/issues/13#issuecomment-270181644,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpyP-g3EPQSBI6Phvunpk2EKFyC76JJks5rOo83gaJpZM4K7ytK
.

@evshvarov, or, you can just delete the link you don't need.

Yes I can, should I delete them all? if I didn't do that they are
visualized wrong every time.
So they do not provide any value now.
If I should delete them every time maybe it's better to show them properly
or do not show them at all?
On Wed, Jan 4, 2017 at 6:13 PM, Nikita<EMAIL_ADDRESS>wrote:

@evshvarov https://github.com/evshvarov, or, you can just delete the
link you don't need.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-ru/UMLExplorer/issues/13#issuecomment-270337539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpyPyEgEi6xLoBQzPHKIa_PBCNOmySFks5rO3DGgaJpZM4K7ytK
.

@evshvarov, sometimes they are useful, so... Maybe it make sense to introduce a new option like "draw self-relations".

They are useful, no doubts. But they never look right.

new option like "draw self-relations".
Makes sense, and make it off by default.

On Wed, Jan 4, 2017 at 10:26 PM, Nikita<EMAIL_ADDRESS>wrote:

@evshvarov https://github.com/evshvarov, sometimes they are useful,
so... Maybe it make sense to introduce a new option like "draw
self-relations".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-ru/UMLExplorer/issues/13#issuecomment-270382299,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpyP-npLT39G11CnoVqrNt2TghzrEdpks5rO6wQgaJpZM4K7ytK
.

@evshvarov, they look right after you edit them. That may be useful to save the png of a diagram even if they are not saved.


Increased page size for group member query

Increased page size for group member query to resolve #246

LGTM


Public CI Pipeline

Hey @cppforlife can you make the CI server public (so that you can at least see the pipeline?)

Done.


Master

Conflicts:
SVProgressHUD/SVProgressHUD.h

Dear @yanhooIT.  You are taking my time to check what you have done. If you want to try out this component do it on your local branch without pushing here. It is


[CPU][DT] DT not triggering for i8,i8 -> i32 matmul?

Benoit mentioned that we are not data tiling some matmuls depending on their types. I'm seeing the following one not data tiled:
        %30 = linalg.matmul ins(%22, %cst : tensor<2048x256xi8>, tensor<256x128xi8>) outs(%29 : tensor<2048x128xi32>) -> tensor<2048x128xi32>

Could we enable DT for this type combination?

I think we already have it for x86_64 and arm..
https://github.com/openxla/iree/blob/d07c16ad71d863f48ecdea5ddfb2bcc0b3a01dab/compiler/src/iree/compiler/Codegen/Common/CPU/CPUMaterializeEncodingPass.cpp#L221-L260

What is the compilation flags you're using? What is the target CPU?

@NatashaKnk, could you please help with this? If you use ToT, including your PR, and compile the i8 version of our internal model for pixel 8, you will see that DT is not triggering for some matmuls that should be supported, including: dispatch 45 (i8, i8, i32), dispatch 40 (f32), dispatch 38 (f32), etc., etc.
Please, note that the (f32, i8, f32) case is a different issue, tracked here: https://github.com/openxla/iree/issues/15760

I checked the example here with a simple function:
module {
  func.func @matmul_test(%arg0: tensor<2048x256xi8>, %arg1: tensor<2048x128xi32>) -> tensor<2048x128xi32> {
    %cst = arith.constant dense<3> : tensor<256x128xi8>
    %0 = linalg.matmul ins(%arg0, %cst : tensor<2048x256xi8>, tensor<256x128xi8>) outs(%arg1 : tensor<2048x128xi32>) -> tensor<2048x128xi32>
    return %0 : tensor<2048x128xi32>
  }
}

Using the SoT (65680c69ff1433129be76bf37b028521d30cc5ac) and compile with:
iree-compile --iree-hal-target-backends=llvm-cpu --iree-llvmcpu-target-triple=aarch64-none-linux-android34 --iree-llvmcpu-target-cpu-features=+fp-armv8,+neon,+crc,+lse,+rdm,+ras,+rcpc,+dotprod,+v9a,+sb,+ssbs,+fullfp16,+fp16fml,+i8mm,+bf16,+flagm --mlir-disable-threading --iree-opt-data-tiling --iree-llvmcpu-enable-ukernels=all ./tmp.mlir -mlir-print-ir-after-all 2> tmp.dump

And I got
// -----// IR Dump After LLVMCPUSelectLoweringStrategy (iree-llvmcpu-select-lowering-strategy) //----- //
hal.executable.variant public @embedded_elf_arm_64 target(<"llvm-cpu", "embedded-elf-arm_64", {cpu = "generic", cpu_features = "+fp-armv8,+neon,+crc,+lse,+rdm,+ras,+rcpc,+dotprod,+v9a,+sb,+ssbs,+fullfp16,+fp16fml,+i8mm,+bf16,+flagm,+reserve-x18", data_layout = "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128", native_vector_size = 16 : index, target_triple = "aarch64-unknown-unknown-eabi-elf", ukernels = "all"}>) {
  hal.executable.export public @matmul_test_dispatch_2_mmt4d_256x16x32x8x8x8_i8xi8xi32 ordinal(0) layout(#hal.pipeline.layout<push_constants = 0, sets = [<0, bindings = [<0, storage_buffer, ReadOnly>, <1, storage_buffer>]>]>) attributes {translation_info = #iree_codegen.translation_info<Mmt4dTilingExpert>} {
  ^bb0(%arg0: !hal.device):
    %x, %y, %z = flow.dispatch.workgroup_count_from_slice
    hal.return %x, %y, %z : index, index, index
  }
  builtin.module {
    func.func @matmul_test_dispatch_2_mmt4d_256x16x32x8x8x8_i8xi8xi32() {
      %cst = arith.constant dense<3> : tensor<16x32x8x8xi8>
      %c0 = arith.constant 0 : index
      %c524288 = arith.constant 524288 : index
      %0 = hal.interface.binding.subspan set(0) binding(0) type(storage_buffer) alignment(64) offset(%c0) flags(ReadOnly) : !flow.dispatch.tensor<readonly:tensor<256x32x8x8xi8>>
      %1 = hal.interface.binding.subspan set(0) binding(1) type(storage_buffer) alignment(64) offset(%c524288) : !flow.dispatch.tensor<readwrite:tensor<256x16x8x8xi32>>
      %2 = flow.dispatch.tensor.load %0, offsets = [0, 0, 0, 0], sizes = [256, 32, 8, 8], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:tensor<256x32x8x8xi8>> -> tensor<256x32x8x8xi8>
      %3 = flow.dispatch.tensor.load %1, offsets = [0, 0, 0, 0], sizes = [256, 16, 8, 8], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readwrite:tensor<256x16x8x8xi32>> -> tensor<256x16x8x8xi32>
      %4 = linalg.mmt4d {lowering_config = #iree_codegen.lowering_config<tile_sizes = [[32, 8, 0, 0, 0, 0], [1, 1, 0, 8, 8, 0], [0, 0, 1, 0, 0, 8]]>} ins(%2, %cst : tensor<256x32x8x8xi8>, tensor<16x32x8x8xi8>) outs(%3 : tensor<256x16x8x8xi32>) -> tensor<256x16x8x8xi32>
      flow.dispatch.tensor.store %4, %1, offsets = [0, 0, 0, 0], sizes = [256, 16, 8, 8], strides = [1, 1, 1, 1] : tensor<256x16x8x8xi32> -> !flow.dispatch.tensor<readwrite:tensor<256x16x8x8xi32>>
      return
    }
  }
}

So looks like DT (and UK) is enabled for this case now

Can someone comment on the status of this issue? Seems fixed now. Can we please validate and close?


Question about VA fault detection in system both support Sv32 and Sv39

In such IOMMU implementation with capabilities.Sv32=1 & capabilities.Sv39=1 and 64-bit addresss width, as the IOMMU model suggests, when iosatp.MODE=Sv32 and DC.SXL=1, 63–32 should all equal to bit 31, or else a page-fault exception will occur.
While I think this is not exactly what the IOMMU spec requires:

When SXL is 1, the following rules apply:

If the first-stage is not Bare, then a page fault corresponding to the original access type occurs if
the IOVA has bits beyond bit 31 set to 1.
If the second-stage is not Bare, then a guest page fault corresponding to the original access type
occurs if the incoming GPA has bits beyond bit 33 set to 1.

I prefer this is a bug in the model (see code), since in a 32-bit system, there is no such canonical rule for Sv32 as Sv39/Sv48/Sv57 in 64-bit system. The check may only detect the [63:32] for IOVA and [63:34] not to one.

You are right that the code would produce a wrong result for 0xFFFFFFFF_???????? case for SXL=1. Fixing as follows:
if ( (masked_upper_bits != 0 && masked_upper_bits != mask && SXL == 0) ||
     (masked_upper_bits != 0 && SXL == 1) ) goto page_fault;


[SPARTA-602] set remember field when creating new StreamContext

Given a policy wizard
When I am configuring the settings displayed at the first modal
And I leave remember number and time empty
Then cube is saved successfully
Given a policy wizard
When I am configuring the settings displayed at the first modal
And I leave remember number empty
And I introduce value to remember time field
Then error is shown below remember number
Given a policy wizard
When I am configuring the settings displayed at the first modal
And I leave remember time empty
And I introduce value to remember number field
Then error is shown below remember time
Given a policy wizard
When I am editing the settings displayed at the first modal
And I remove remember number and time fields
Then remember field is not added to policy json

+1

:shipit:

Comment accepted. Will treat it ASAP


Discoverable bug for RequestLogFactory

Pretty sure that META-INF.services -> META-INF/services here.  This is causing custom RequestLogFactories from not being discovered.
Workaround, in your project add a io.dropwizard.jackson.Discoverable file in META-INF/services with contents of io.dropwizard.request.logging.RequestLogFactory and everything is hunky-dory again!
I think the only reason this works in 1.0 is because RequestLogFactory has a default impl class in the jackson annotation.

Nice, did you want to send a PR to fix this?
Is it possible to write a test to ensure that this doesn't regress in the future?

I have a PR for this: https://github.com/dropwizard/dropwizard/pull/1743
I'm unsure how to write a test case as Discoverable is kind of opt-in.  How would you recommend one?  Hard code a check for META-INF.services?

This may be enough of a unit test (it'll fail without your PR) 💭
public class RequestLogFactoryTest {

    @Test
    public void isDiscoverable() throws Exception {
        assertThat(new DiscoverableSubtypeResolver().getDiscoveredSubtypes())
            .contains(LogbackAccessRequestLogFactory.class);
    }
    // ...
}

There are other tests worth looking at in dropwizard-logging

Added test, ci is running…

ci ran and github checks passed


access: may-start-trybots

I'd like trybot access, thanks!
Email<EMAIL_ADDRESS>URL: https://go-review.googlesource.com/#/admin/groups/1030,members
/cc @andybons @dmitshur

Done.

(Usual warnings apply: use your new powers carefully. Review the code before you start the trybots, in case it's malicious... the build system is mostly isolated but not perfectly.)


"Giuvărăști" is listed in the drop-down menu

Description:
"Giuvărăști" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Giuvărăști" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Giuvărăști, OLT (Giuvărăști)".


Fix regex test for CSRPNG

Test string 5BK0n+pM7o35bEyc8p4WFusi147N/JV/ was failing because of the \b.
Refs #212, #277

Coverage remained the same at 89.11% when pulling a6cc41ed4c06a58c14d10b92cf98db3a890a62a1 on shadowhand:hotfix/csprng-test-regex-fix into e420f6c8728b84b766208c3e2dfbf6b1ba749a8f on thephpleague:1.0.


A larger data payload in the response of a block request can't be sent back due to KeepAliveTimeout and then peer disconnected

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
When a node requests a chunk of blocks from another node, if these blocks happen to be huge, the block request is successfully handled on the server node but failed to be sent back to the requester due to the error KeepAliveTimeout
2022-08-24 17:33:04.394 DEBUG tokio-runtime-worker libp2p_swarm: [PrimaryChain] Connection closed with error KeepAliveTimeout: Connected { endpoint: Listener { local_addr: "/ip4/<IP_ADDRESS>/tcp/30333", send_back_addr: "/ip4/<IP_ADDRESS>/tcp/55227" }, peer_id: PeerId("12D3KooWG87xHK71UEKkw4pLCAkaa2C4vCnAsk5hVYD6dzQdua6G") }; Total (peer): 0.
2022-08-24 17:33:04.394 DEBUG tokio-runtime-worker sub-libp2p: [PrimaryChain] Libp2p => Disconnected(PeerId("12D3KooWG87xHK71UEKkw4pLCAkaa2C4vCnAsk5hVYD6dzQdua6G"), Some(KeepAliveTimeout))

Here is the server node log, we can see the byte size of the first request result is 299402, which is sent successfully, the second request result size is 10534306 which failed to be sent back. The reason is that there are some data store transactions after block 64, causing the block size to increase significantly.
2022-08-24 17:28:48.407 DEBUG tokio-runtime-worker libp2p_dns: [PrimaryChain] Dialing /ip4/<IP_ADDRESS>/tcp/21000/p2p/12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS
2022-08-24 17:28:52.713 DEBUG tokio-runtime-worker libp2p_swarm: [PrimaryChain] Connection established: PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS") Listener { local_addr: "/ip4/<IP_ADDRESS>/tcp/30333", send_back_addr: "/ip4/<IP_ADDRESS>/tcp/34940" }; Total (peer): 1. Total non-banned (peer): 1
2022-08-24 17:28:52.713 DEBUG tokio-runtime-worker sub-libp2p: [PrimaryChain] Libp2p => Connected(PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS"))
2022-08-24 17:28:53.318 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping sent to PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:28:53.319 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping received from PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:28:53.930 DEBUG tokio-runtime-worker sync: [PrimaryChain] Connected 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS
2022-08-24 17:28:54.983 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(64)` with maximum blocks of `64`, reputation_change: `None`, small_request `false`, direction `Descending` and attributes `HEADER | BODY | JUSTIFICATION`.
2022-08-24 17:28:55.054 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(64)`: blocks: Some(64), data: Some(299402)
2022-08-24 17:28:55.055 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:28:57.831 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(128)` with maximum blocks of `64`, reputation_change: `None`, small_request `false`, direction `Descending` and attributes `HEADER | BODY | JUSTIFICATION`.
2022-08-24 17:28:57.837 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(128)`: blocks: Some(3), data: Some(10534306)
2022-08-24 17:28:57.840 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:29:08.407 DEBUG tokio-runtime-worker libp2p_kad::behaviour: [PrimaryChain] Address '/ip4/<IP_ADDRESS>/tcp/21000/p2p/12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS' removed from peer '12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS' due to error.
2022-08-24 17:29:08.407 DEBUG tokio-runtime-worker libp2p_swarm: [PrimaryChain] Connection attempt to PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS") failed with Transport([("/ip4/<IP_ADDRESS>/tcp/21000/p2p/12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS", Other(Custom { kind: Other, error: Timeout }))]).
2022-08-24 17:29:09.122 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping received from PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:29:11.989 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping sent to PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:29:26.115 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(64)` with maximum blocks of `1`, reputation_change: `None`, small_request `true`, direction `Ascending` and attributes `HEADER | JUSTIFICATION`.
2022-08-24 17:29:26.115 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(64)`: blocks: Some(1), data: Some(4664)
2022-08-24 17:29:26.115 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:29:26.760 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(128)` with maximum blocks of `64`, reputation_change: `None`, small_request `false`, direction `Descending` and attributes `HEADER | BODY | JUSTIFICATION`.
2022-08-24 17:29:26.767 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(128)`: blocks: Some(3), data: Some(10534306)
2022-08-24 17:29:26.770 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:29:26.989 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping received from PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:29:41.875 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping sent to PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:29:56.875 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping received from PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:30:01.218 DEBUG tokio-runtime-worker libp2p_ping: [PrimaryChain] Ping sent to PeerId("12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS")
2022-08-24 17:30:01.721 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(64)` with maximum blocks of `1`, reputation_change: `None`, small_request `true`, direction `Ascending` and attributes `HEADER | JUSTIFICATION`.
2022-08-24 17:30:01.721 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(64)`: blocks: Some(1), data: Some(4664)
2022-08-24 17:30:01.721 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:30:02.747 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handling block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: Starting at `BlockId::Number(128)` with maximum blocks of `64`, reputation_change: `Some(ReputationChange { value: -2147483648, reason: "Same block request multiple times" })`, small_request `false`, direction `Descending` and attributes `HEADER | BODY | JUSTIFICATION`.
2022-08-24 17:30:02.747 DEBUG tokio-runtime-worker sync: [PrimaryChain] Sending result of block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS starting at `BlockId::Number(128)`: blocks: None, data: None
2022-08-24 17:30:02.747 DEBUG tokio-runtime-worker sync: [PrimaryChain] Handled block request from 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS.
2022-08-24 17:30:02.747 DEBUG tokio-runtime-worker peerset: [PrimaryChain] Report

With interior networking and large blocks which are normal for a storage chain, this issue can occur quite often. I see a few ways to help this:

Allow increasing the timeout, both request and response. If a chain can have a lot of large blocks, a larger timeout should be used.
Send back just one block of data if the data result is huge. 10534306 is actually for 3 blocks, reducing it to one will help a lot. Furthermore, a chain has a nature block size limit, once configurable, the timeout may be adjusted based on this value.

I think https://github.com/paritytech/substrate/issues/11732 is related, after Timeout, we see a flood of duplicated block requests, maybe we can also do something to improve that.
Steps to reproduce
No response

CC @arkpar

@tomaka Could you pleas clarify when exactly KeepAliveTimeout is generated? Documentation says that the connection will be closed after being "idle" for specified time. Is it considered idle when the request is in progress? Here we hardcode keep-alive timeout to 10 seconds.
Also, does KeepAliveTimeout handling mean that the peer disconnects from the sync protocol as well?
@liuchengxu how fast is the network speed?  Is it at least 100mbps?

The keep-alive timeout only starts after there is no activity on a connection anymore. It's the mechanism that we use to kill inactive connections.
Each protocol decides what "no activity" means. In our situation, it means no notifications protocols open and no request (in the request/response system) in progress.
Looking at the issue, the logs are cropped, and I don't see any hint of the fact that the problem could be caused by the KeepAliveTimeout error.

@liuchengxu Could you please full logs for both nodes for the same period of time.

Here is logs of the node that Liu-Cheng's node tried to sync from (we had them added as reserved nodes of each other with --reserved-only): https://nextcloud.mokrynskyi.com/s/xNtYpAsZTFY8YN7
This is with debug log level for everything, thus quite big.

Thanks Nazar.
@arkpar For the convient review, here is the server node log: https://files.slack.com/files-pri/T03LJ85UR5G-F03UZ31SHC3/untitled.txt, the client node log: https://files.slack.com/files-pri/T03LJ85UR5G-F03V6JZ7HQC/client_node.txt Let me know if they are not sufficient.

I think https://github.com/paritytech/substrate/issues/11732 is related, after Timeout, we see a flood of duplicated block requests, maybe we can also do something to improve that.

yeah, duplicated block requests lead to us disconnecting from that node
2022-08-24 17:30:02.747 DEBUG tokio-runtime-worker peerset: [PrimaryChain] Report 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS: -2147483648 to -214748
3648. Reason: Same block request multiple times, Disconnecting
2022-08-24 17:30:02.747  WARN tokio-runtime-worker sync: [PrimaryChain] Reserved peer 12D3KooW9rwH7iqBbynXERRrGHxYn4UbCieByXxnkPGJ3R7wShdS disconnected

To me this looks like this is a duplicate of #11732

I'd say this one is caused by #11732, but they are not quite the same as other slow network data transfers can potentially cause this timeout too.


fix(#2765): 修复Hive类型以数字开头的别名语句解析报错的bug

修复了： #2765
单元测试：com.alibaba.druid.bvt.sql.hive.HiveSelectTest_0#test_2765()

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

代码冲突太大，麻烦基于最新代码重新提交pr


Add accessibility settings

Moved the interface settings into its own menu and separated it into Notifications and Appearance.
In appearance I added a font size range and a font selector with included fonts ^-^
Added the following fonts:

OpenDyslexic
Lexend
Noto Sans (CJK)
Ubuntu
OS's sans-serif font

rest of commits are me trying to reduce filesize the maximum amount i can


StyleCopAnalyzers cannot be used in VS2017 only because StyleCopAnalyzers references Microsoft.CodeAnalysis, Version=<IP_ADDRESS>

The StyleCop analyzers seem to have a reference to "Microsoft.CodeAnalysis, Version=<IP_ADDRESS>".
So unfortunately, when I try to build a project that uses the analyzers on a machine that only has VS2017 installed, I get compilation errors:
(translated to English)
CSC : error CS8032: An instance of StyleCop.Analyzers.SpacingRules.SA1004DocumentationLinesMustBeginWithSingleSpace-Analyzers cannot be built from <PathToMyNuGetPackages>\StyleCop.Analyzers.1.1.0-beta006\analyzers\dotnet\cs\StyleCop.Analyzers.dll: File or assembly "Microsoft.CodeAnalysis, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35" or one of its dependencies cannot be found."

To get it working, it seems that I need to install VS2015.
It would be great if there would be no such reference so that I can use the analyzers also on a new machine that solely has VS2017 installed.

It sounds like the assembly binding redirection for the compiler instance you are using are not correctly applied. On a system with only Visual Studio 2017, the compiler is required (per the backwards compatibility policy) to automatically substitute the 2.x versions of these assemblies when an analyzer requests to load a 1.x version.

I have the same issue (although I have not tried to install VS2015), but I'm not sure I understand your answer. Is there something I can do to fix the issue?

@RalfKoban @dchaib I'm going to need the inner exceptions information to do anything here.

@sharwell I'll be happy to help but I don't know how to get the inner exceptions... Can you help me?

@dchaib If you use the Report a Problem tool in Visual Studio, you can record the steps triggering the problem. The instructions for Performance problems shown on https://aka.ms/reportPerf are sufficient for capturing the errors you described. After uploading your performance report, reply to this thread with a link to the feedback item and I can look at the details.

@sharwell Sorry for the late reply. I have been trying to record the problem, but every time I start recording, it stops immediately, saying :

Please wait while we finish collecting additional information. This may take a few minutes and the Visual Studio instance you are recording for cannot be accessed at this time.

I don't have time to reproduce the issue before...

I finally found a way to fix my issue!
I first upgraded the .Net framework version from 4.5.1 to 4.7.1. It didn't fix the issue, but was maybe necessary for the next step.
I then upgraded the NuGet package Microsoft.Net.Compilers from 1.0.0 to 2.8.2 and all the warnings disappeared.

I then upgraded the NuGet package Microsoft.Net.Compilers from 1.0.0 to 2.8.2 and all the warnings disappeared.

Ah, yes. This forced the compiler to Roslyn 1.0.0, which is lower than the minimum version (1.2.0) supported by StyleCop Analyzers.


install error

cli yarn install secret-agent
env:
yarn: v1.22.5
node: v15.10.0
network location: chinese
[4/4] 🔨  Building fresh packages...
[-/12] ⡀ waiting...
[-/12] ⡀ waiting...
[11/12] ⡀ @secret-agent/mitm-socket
[-/12] ⡀ waiting...
error /.../server/node_modules/@secret-agent/mitm-socket: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /.../server/node_modules/@secret-agent/mitm-socket
Output:
ERROR downloading needed Secret Agent library https://github.com/ulixee/secret-agent/releases/download/v1.4.1-alpha.5/connect.checksum Error: socket hang up
    at connResetException (node:internal/errors:642:14)
    at TLSSocket.socketOnEnd (node:_http_client:486:23)
    at TLSSocket.emit (node:events:390:22)
    at endReadableNT (node:internal/streams/readable:1307:12)
    at processTicksAndRejections (node:internal/process/task_queues:81:21) {
  code: 'ECONNRESET'
}
node:internal/process/promises:245
          triggerUncaughtException(err, true /* fromPromise */);
          ^

Error: socket hang up
    at connResetException (node:internal/errors:642:14)
    at TLSSocket.socketOnEnd (node:_http_client:486:23)
    at TLSSocket.emit (node:events:390:22)
    at endReadableNT (node:internal/streams/readable:1307:12)

Do I need to set socket proxy?, Because of the network problem, the access to some information of GitHub in China often times out of time

When I have NPM image in China, cnpm is installed successfully
run: cnpm install secret-agent
env: cnpm --version
<EMAIL_ADDRESS>(/usr/local/lib/node_modules/cnpm/lib/parse_argv.js)
<EMAIL_ADDRESS>(/usr/local/lib/node_modules/cnpm/node_modules/npm/lib/npm.js)
<EMAIL_ADDRESS>(/usr/local/bin/node)
<EMAIL_ADDRESS>(/usr/local/lib/node_modules/cnpm/node_modules/npminstall/lib/index.js)
prefix=/usr/local
darwin x64 20.5.0
registry=https://r.npm.taobao.org

✔ Installed 1 packages
✔ Linked 101 latest versions
[1/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>run "node install", root: "/.../server/node_modules/_@secret-agent_replay@1.4.1-alpha.5@@secret-agent/replay"
[1/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>finished in 106ms
[2/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>run "node install.js", root: "/.../server/node_modules/_@secret-agent_mitm-socket@1.4.1-alpha.5@@secret-agent/mitm-socket"
Downloading Secret Agent connect library from https://github.com/ulixee/secret-agent/releases/download/v1.4.1-alpha.5/connect_1.4.1-alpha.5_mac_x86_64.gz (checksum=7b7441eb165ef796130c2138e989ea57db882e1f7d03c8a6d713d59c7f1ef495)
Successfully downloaded
[2/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>finished in 2m
[3/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>run "node install.js", root: "/.../server/node_modules/_@secret-agent_emulate-chrome-88@1.4.1-alpha.5@@secret-agent/emulate-chrome-88"
Chrome 88.0.4324.150 is already installed; skipping download.
[3/4] scripts.postinstall<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>finished in 107ms
[4/4] scripts.install<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>run "prebuild-install || npm run build-release", root: "/.../server/node_modules/_better-sqlite3@7.4.1@better-sqlite3"
prebuild-install http request GET https://github.com/JoshuaWise/better-sqlite3/releases/download/v7.4.1/better-sqlite3-v7.4.1-node-v88-darwin-x64.tar.gz
prebuild-install http request Proxy setup detected (Host: <IP_ADDRESS>, Port: 7890, Authentication: No) Tunneling with httpsOverHttp
prebuild-install http 404 https://github.com/JoshuaWise/better-sqlite3/releases/download/v7.4.1/better-sqlite3-v7.4.1-node-v88-darwin-x64.tar.gz
prebuild-install WARN install No prebuilt binaries found (target=15.10.0 runtime=node arch=x64 libc= platform=darwin)
npm http fetch GET 200 https://r.npm.taobao.org/npm 302ms

><EMAIL_ADDRESS>build-release
> node-gyp rebuild --release

  TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediatebao.org/npm 302ms
  ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
  TOUCH Release/obj.target/deps/locate_sqlite3.stampr.npm.taobao.org/npm 302ms
  CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o
  LIBTOOL-STATIC Release/sqlite3.ah GET 200 https://r.npm.taobao.org/npm 302ms
  CXX(target) Release/obj.target/better_sqlite3/src/better_sqlite3.o/npm 302ms
  SOLINK_MODULE(target) Release/better_sqlite3.node/r.npm.taobao.org/npm 302ms
  CC(target) Release/obj.target/test_extension/deps/test_extension.o/npm 302ms
  SOLINK_MODULE(target) Release/test_extension.node/r.npm.taobao.org/npm 302ms
rm b857c92884e9598d609f6be182a2595df7a8e00f.intermediatem.taobao.org/npm 302ms
[4/4] scripts.install<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>finished in 39s
✔ Run 4 scripts
peerDependencies WARNING<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed
peerDependencies WARNING<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed
Recently updated (since 2021-06-16): 1 packages (detail see file /.../server/node_modules/.recently_updates.txt)
✔ All packages installed (110 packages installed from npm registry, used 3m(network 1s), speed 170.97kB/s, json 102(249.96kB), tarball 0B)

https://github.com/ulixee/secret-agent/blob/1389850dbc4b8d2a04560e939a085b816406c1a6/mitm-socket/install.js#L120
I use HTTP in my shampoo environment_ proxy, https_ Proxy, but the request here is not used
https://github.com/nodejs/node/issues/8381

Hi @hehehai, yes it looks like we are missing the proxy configuration for downloading the mitm. Will need to fix this for you to be able to use it unless you can set a system proxy.

@blakebyrnes Yes, system proxy is indeed a problem, but if there is no proxy, network problems will affect the installation of dependency
Sorry, I'd like to ask why the dependent installation chooses this method of code download instead of NPM direct download. Is it because of the file size and update frequency?
I think the current way sometimes leads to errors or abnormal information without feedback. I don't know why, but it makes it difficult to debug the program

I wish I knew a better option. There are 3 binaries compiled "per-system" that we generate (chrome, mitm, replay), and one that we include (better-sqlite3). The size is too big to put directly into an npm package with every architecture and platform.
At some point, you could more reliably see logs output from the program during npm runs, but now it seems to drown out most logging/output, which makes it hard to troubleshoot (I agree).

You can get a sense for some of the assets involved here: https://github.com/ulixee/secret-agent/releases/tag/v1.4.1-alpha.5
Chrome is downloaded in a fashion similar to Puppeteer and Playwright. They don't seem to have found a better way (beyond looking for correct proxy settings, which I'm fixing)


Issue Fixed #3335

BUGS:
#3335

Please describe the issue that you solved if its not filed.

Otherwise please mention issue #id and use comma if your PR
solves multiple issues.

For things other than bugs:

Describe that thing in very short line, word limit is 200.
Otherwise use issue #id if the issue was filed as feature request.

working fine


OCP Support Matrix for kam

Describe the bug
There is no specific OCP support matrix for kam found in the README.md. It would be great if we add the OCP support matrix for user reference.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://github.com/redhat-developer/kam/tree/master/docs/journey/day1#day-1-operations'
No reference for OCP support matrix found

Expected behavior
OCP support matrix for user reference

/kind bug

ping @wtam2018


Kysely.dev homepage playground example seems to be on old version pre-eb v2 (ie. orWhere)

I am brand new to Kysely and looking to implement in our new sqlite project. I was on the homepage and started playing with the playground on the homepage and noticed orWhere is how to do groupings of OR clauses. I later was looking through the advanced docs and saw reference to the eb.or nomenclature and then stumbled across this PR for the migration to expression builder v2: https://github.com/kysely-org/kysely/pull/565

After some investigation I realized the eb.or syntax seemed to be the correct syntax for today and that the home page playground must just be connected to an older version of the API.
To avoid any confusion between the playground and the docs for new users like myself, it would be nice if that playground on the homepage could be updated to the current version / API.
Great product! Looking forward to integrating in our project.

That playground should just be removed. It doesn't use https://kyse.link but some other thing that was thrown together by the person that implemented the first version of kysely.dev.
If you go to the example section, the "correct" playground is used there.

@koskimas as an fyi I will say it was nice as a new prospective user to have a playground on the homepage. If the correct playground is embeddable then I recommend replacing it, otherwise a link to the playground.
Do you want me to close this issue? Or want to leave it open as a reminder to fix the homepage?

Sorry, I meant we should replace the playground with kyse.link and remove the current one from the codebase. Let's leave this open. I'll rename the issue.


Code up workflow for quick, "local" download of WOD required for CARSv2

Code up workflow for quick, "local" download of WOD required for CARSv2
requirements

years: 2005 onward
platforms: all

@Thomas-Moore-Creative I have copied IQuOD files onto Gadi and have been able to read them and plot very quickly with NCI VM 2 cores. Much quicker than files located on Bowen storage and trying to use code sitting on tube-hba which is located in Hobart.

Nice work @BecCowley
It's always exciting when you get your compute and your data right next to each other.
Don't get me started on what has happened to Bowen storage.

@BecCowley (and @ChrisC28 ) - so do we think this issue is resolved?  We plan to bring WOD data in via Gadi and then can transfer to other platforms / locations as needed?

How big is "everything" WOD?
What is the list of platforms / locations we'll need to get the data to?

Assume list includes machines on site in Hobart?  Do we need data on Canberra Bowen to utilise CSIRO HPC?

Might be useful: argopy libraries use DataFetcher
https://github.com/euroargodev/argopy

looks like, for now, @ChrisC28 has WOD2018 downloaded - https://github.com/CARSv2/cars-v2/issues/20#issuecomment-2111431289

Closing this as @ChrisC28 completed


Astro: unordered list not showing bullets

Bullets do not appear in the unordered list at https://www.eidolonai.com/docs/howto/authenticate_llm

Source file: webui/apps/docs/src/content/docs/docs/howto/authenticate_llm.md

Wow: https://tailwindcss.com/docs/preflight#lists-are-unstyled

Ordered and unordered lists are unstyled by default, with no bullets/numbers and no margin or padding.


add nonce to send action to counteract duplicate trx error

this pr  just adds a nonce to the send action to counteract duplicate trx errors when calling the action in a loop. the nonce must be an int.

Why not use --force in cleos?

Because that will limit the use of looped send actions only for cleos.


Yale Lock update

There are a few new events in my log:
No converter available for 'YRD426NRSC' with cid 'genPowerCfg', type 'devChange' and data '{"cid":"genPowerCfg","data":{"batteryVoltage":48,"batteryPercentageRemaining":72}}'
No converter available for 'YRD426NRSC' with cid 'genPowerCfg', type 'devChange' and data '{"cid":"genPowerCfg","data":{"batteryPercentageRemaining":74}}'

But I'm not sure how to add them correctly to the config to not break something for other users.

The devChange event is generated after an attReport or readRsp which is already converted by fz.battery_200.  As devChange will be removed in the future anyway, I think you can add fz.ignore_power_change which will suppress the message.


Towards qt5.9 vcpkg

Is it okay to open an issue for something not available yet, just to collect opinions and experiences for a plan to get qt5.9 (which was released today) into vcpkg. Qt5.9 is planned to be a long term support release, so both a landmark in Qt development, and at some point a challenge to vcpkg's single version policy ;)
Obvious weaknesses I have found in the Qt5.8 vcpkg version:

the private header paths are not generated in the cmake configuration files for the modules (share/cmake ...)
qt's policy to provide libraries with the d suffix, and vcpk's to use a distinct folder debug seem to conflict in subtle ways, like not finding the debug libraries, or - if setting the debug folder as prefix - not finding headers, and some more
static build does not work (but is also not provided by Qt itself)

There must be less obvious problems as my results trying to build against vcpkg's Qt cause quite a few weird errors (while the official distro works). In another thread it was mentioned that Qt should be built insource build, otherwise problems (e.g. missing generation of private header paths) will result. So maybe this is another aspect in which Qt conflicts with overall design decisions of vcpkg.
Otoh I think a vcpkg-Qt will be very useful. From my Mac experience I can say that we never bother to look at the original Qt distribution but go straight to homebrew. Those versions are patched for macos, give options (e.g. webkit, db-support) and are integrated into an popular overall workflow to retrieve libraries. Qt5.9 is not distributed in a msvc_2017 32-bit version (win32/non-uwp), another desideratum vcpkg could fill. And of course we want a coherent Qt in the mix if we build using other vcpkg libraries.

If you upgrade the portfile: At the moment Qt5 copies its cmake files to /share/cmake instead of /share/qt5/cmake

Hi @bagong, thanks for posting this issue. qt5 has been upgraded to version 5.12.3 now. The current states about qt5 are as follows:

when building qt5, the libraries will be added with the d suffix in debug folder.
qt5 supports on Linux and OSX.
qt5 supports static build.

For the cmake configuration files, they are still copied to share/port/cmake.  Normally ports copy their cmake files to share/port/cmake.

Thanks, @NancyLi1013. I've been out of the loop for quite a while, I wasn't even aware this issue was still open. Happy to close. Thanks again!


Moore's law question is not addressed in the lesson

Challenge Name

https://www.freecodecamp.org/videos/computer-basics-chips-and-moores-law
Issue Description

Question 3: "Moore's Law has slowed down in recent years." according to the video would be "false", as it says in the video and in the text accompanying it that "Moore's Law is the observation that the amount of transistors fit on each chip has doubled every two years since 1965." (emphasis mine), but the correct answer is "true". It gives the source for the answer in the hint. Basically, the question and answer is correct but it says differently/doesn't mention it in the lesson

Good catch @DovidM! This is no longer an issue in the beta, because these quizzes were removed. In a case like this one, the ideal solution would be to update the video to mention that progress has slowed down, but updating video's is really hard. That's the main reason for removing the quizzes.
@raisedadead Can this be closed?

Thanks @systimotic


The order of the DApps in the DApp Store

The first ones always  BEAM, no one should get between them

If you are a User, then:
2. The ones you installed.
3. Those that you have not installed, but whose authors you have subscribed to
If you are a Publisher, then:
2. Your publisher DApps
3. Your publisher DApps, but have not installed
4. Those that you have installed by other authors (publishers)
5. DApps of publishers you are subscribed to, but have not installed
approved by @VikMaevskaya
For example :

Checked


Fix line separation in concepts/architecture/nodes

https://github.com/kubernetes/website/pull

It seems link in description is wrong, can you fix that?

/cc @makocchi-git
/assign


@YAJATapps No I'm on stock marshmallow 6.0.1 non rooted

I think that isn't launcher bug

But when I tried there is no such issue with Nova and other launchers

@jerryn70
Can you send a picture of how it looks in nova. You said its fine in it.


How do I use a remote reactor?

I'm working on a library in which I need to use tokio_core::reactor::Remote instead of tokio_core::reactor::Core. Unfortunately, all the examples I can find are using tokio_core::reactor::Core. @carllerche was kind enough to point me in the right direction in https://github.com/tokio-rs/tokio-core/issues/75, so I now have a good idea how this works.
I tried to reproduce the tutorial using Remote instead of Core. Here is the code I came up with so far:-
extern crate futures;
extern crate tokio_core;
extern crate tokio_tls;

use std::net::ToSocketAddrs;
use std::net::TcpStream as StdTcpStream;

use futures::Future;
use tokio_core::reactor::{Core, Remote};
use tokio_core::net::TcpStream;
use tokio_tls::ClientContext;

fn main() {
    let remote = Core::new().unwrap().remote();

    let (tx, rx) = futures::oneshot();

    let stream = StdTcpStream::connect("www.rust-lang.org:443").unwrap();

    remote.spawn(|handle| {
        let addr = stream.peer_addr().unwrap();
        let socket = TcpStream::connect_stream(stream, &addr, handle);
        tx.complete(socket);
        Ok(())
    });

    let tls_handshake = rx.and_then(|socket| {
        let cx = ClientContext::new().unwrap();
        cx.handshake("www.rust-lang.org", socket)
    });

    let request = tls_handshake.and_then(|socket| {
        tokio_core::io::write_all(socket, "\
                GET / HTTP/1.0\r\n\
                Host: www.rust-lang.org\r\n\
                \r\n\
            ".as_bytes())
    });

    let response = request.and_then(|(socket, _)| {
        tokio_core::io::read_to_end(socket, Vec::new())
    });

    let (_, res) = response.wait().unwrap();
    println!("{}", String::from_utf8_lossy(&res));
}

However, this errors out. The first error being:-
error[E0277]: the trait bound `Box<futures::Future<Item=tokio_core::net::TcpStream, Error=std::io::Error> + Send>: tokio_core::io::Io` is not satisfied
  --> src/main.rs:29:12
   |
29 |         cx.handshake("www.rust-lang.org", socket)
   |            ^^^^^^^^^

I have tried calling as_ref() (among other things) to get out of the box on the socket on that line 29 which has the first error. How do I get this to work?

I think you'll want to change the return value of spawn slightly. The TcpStream::connect_stream function returns a future rather than a value, so you'll want to wait for that to finish before calling tx.complete.
If you do that, does it work out?

You mean by replacing
        let socket = TcpStream::connect_stream(stream, &addr, handle);
        tx.complete(socket);

with
        TcpStream::connect_stream(stream, &addr, handle).and_then(|socket| {
            tx.complete(socket);
            Ok(())
        });

Like this?
extern crate futures;
extern crate tokio_core;
extern crate tokio_tls;

use std::net::ToSocketAddrs;
use std::net::TcpStream as StdTcpStream;

use futures::Future;
use tokio_core::reactor::{Core, Remote};
use tokio_core::net::TcpStream;
use tokio_tls::ClientContext;

fn main() {
    let remote = Core::new().unwrap().remote();

    let (tx, rx) = futures::oneshot();

    let stream = StdTcpStream::connect("www.rust-lang.org:443").unwrap();

    remote.spawn(|handle| {
        let addr = stream.peer_addr().unwrap();
        TcpStream::connect_stream(stream, &addr, handle).and_then(|socket| {
            tx.complete(socket);
            Ok(())
        });
        Ok(())
    });

    let tls_handshake = rx.and_then(|socket| {
        let cx = ClientContext::new().unwrap();
        cx.handshake("www.rust-lang.org", socket)
    });

    let request = tls_handshake.and_then(|socket| {
        tokio_core::io::write_all(socket, "\
                GET / HTTP/1.0\r\n\
                Host: www.rust-lang.org\r\n\
                \r\n\
            ".as_bytes())
    });

    let response = request.and_then(|(socket, _)| {
        tokio_core::io::read_to_end(socket, Vec::new())
    });

    let (_, res) = response.wait().unwrap();
    println!("{}", String::from_utf8_lossy(&res));
}

This gives me:-
error[E0271]: type mismatch resolving `<tokio_tls::ClientHandshake<tokio_core::net::TcpStream> as futures::IntoFuture>::Error == futures::Canceled`
  --> src/main.rs:29:28
   |
29 |     let tls_handshake = rx.and_then(|socket| {
   |                            ^^^^^^^^ expected struct `std::io::Error`, found struct `futures::Canceled`
   |
   = note: expected type `std::io::Error`
   = note:    found type `futures::Canceled`

error: no method named `and_then` found for type `futures::AndThen<futures::Oneshot<tokio_core::net::TcpStream>, tokio_tls::ClientHandshake<tokio_core::net::TcpStream>, [closure@src/main.rs:29:37: 32:6]>` in the current scope
  --> src/main.rs:34:33
   |
34 |     let request = tls_handshake.and_then(|socket| {
   |                                 ^^^^^^^^
   |
   = note: the method `and_then` exists but the following trait bounds were not satisfied: `futures::AndThen<futures::Oneshot<tokio_core::net::TcpStream>, tokio_tls::ClientHandshake<tokio_core::net::TcpStream>, [closure@src/main.rs:29:37: 32:6]> : futures::Future`

error[E0277]: the trait bound `[u8]: std::marker::Sized` is not satisfied
  --> src/main.rs:46:13
   |
46 |     let (_, res) = response.wait().unwrap();
   |             ^^^
   |
   = note: `[u8]` does not have a constant size known at compile-time
   = note: all local variables must have a statically known size

Oh the function passed to Remote::spawn is expected to return a closure, so in this case that should be the return value of the connect + and_then

@alexcrichton I'm not sure I totally understand you. I've tried what I thought you meant to no avail. Anyway I think something interesting is going on here. In the following code, I'm not using Remote::spawn and yet I'm running into the same error:-
extern crate futures;
extern crate tokio_core;
extern crate tokio_tls;

use std::net::ToSocketAddrs;

use futures::Future;
use tokio_core::reactor::{Core, Remote};
use tokio_core::net::TcpStream;
use tokio_tls::ClientContext;

fn main() {
    let remote = Core::new().unwrap().remote();

    let addr = "www.rust-lang.org:443".to_socket_addrs().unwrap().next().unwrap();
    let socket = TcpStream::connect(&addr, &remote.current_reactor().unwrap());

    let tls_handshake = socket.and_then(|socket| {
        let cx = ClientContext::new().unwrap();
        cx.handshake("www.rust-lang.org", socket)
    });
    let request = tls_handshake.and_then(|socket| {
        tokio_core::io::write_all(socket, "\
            GET / HTTP/1.0\r\n\
            Host: www.rust-lang.org\r\n\
            \r\n\
        ".as_bytes())
    });
    let response = request.and_then(|(socket, _)| {
        tokio_core::io::read_to_end(socket, Vec::new())
    });

    let (_, data) = response.wait().unwrap();
    println!("{}", String::from_utf8_lossy(&data));
}

Note that remote.current_reactor() is coming from https://github.com/tokio-rs/tokio-core/pull/84. Also note that the only difference this code has with that in the tutorial is the Handle instance and use of the wait method on the future instead of Core::run().

@rushmorem in your previous example yes the types need to match up, but you can fix that by changing this:
let tls_handshake = rx.and_then(|socket| {

to
let tls_handshake = rx.map_err(|_| panic!("canceled")).and_then(|socket| {

The second example doesn't compile for me right now due to the current_reactor method, but it won't work regardless because the Core is dropped immediately, which means you're destroying the event loop as soon as it's created.

I see. In that case I think I'm trying to go about this the wrong way. I'm working on a database driver. I'm using https://github.com/sfackler/r2d2 as my connection pool. I'm trying to bring futures into the mix hence these questions.
I could introduce futures by only using async IO in the final method that actually executes a database connection. That way I can just create the event loop and use it there. However, that means I will be creating and dropping it for every query. I think this is inefficient. I also think that having one instance of the event loop might give me an opportunity to do some interesting things.
Any suggestions?

Ideally the database driver would be async I/O powered to reduce the overhead, but in lieu of that I think a reasonable starting point for an architecture might look like:

You can pull a database connection out of a pool through a future
With that connection you can execute queries which return futures
When the database connection is dropped, it's returned to the pool

You'd then probably implement that with a thread pool where one thread is handing out connections and other threads are executing the actual queries with those connections. (perhaps)
That may not be the most ideal, but is perhaps a place to get started?

Yes you are right. This approach is what I was referring to when I said I could introduce futures in the exec method. Granted it's not ideal but it's a good first step so I will go with that for now. Thanks a lot for all your help and patience.

No problem! Feel free to keep asking questions if you've got them :)


Adding build for ppc64le

This PR adds builds for jiva on ppc64le. Based on #275.

Add auto builds for ppc64le builds.
Ubuntu:18.04 is a multi arch image, so it can be used directly.
Dockerfile_build_ppc64le can be used to build on ppc64le env.
Not running the test on ppc64le.

cc @akhilerm @kmova

@Pensu , you need to also update the push script to push the docker image for ppc64le architecture.

@akhilerm Done!


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 09:18:29 on 2023.05.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 4, errors out: 0
Original problem ID: 20571
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=20571

Problem has been resolved in 6m 0s at 09:24:29 on 2023.05.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 20571


chore(apps/prod/tekton/configs/triggers): add trigger for release branches

Add trigger for LTS release branches:

release-6.1
release-6.5
release-7.1
release-7.5

Also combine the CEL interceptors to save api calls to CEL service.
In feature we can set it for all release branches.
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


question about V0.4.2

Hellow sir，how can i use longshot ’V0.4.2‘? In my knowledge bioconda only relase 'V0.4.1'. when i download code, it only has ''build.rs  Cargo.toml  example_data  LICENSE  README.md '',how can i use ’longshot -bam  -ref -out‘ like this command，or just now can only use the script from v0.4.2 code.

We will push the new version to bioconda soon. Meanwhile, you can compile from the source code: "cargo build --release"

We will push the new version to bioconda soon. Meanwhile, you can compile from the source code: "cargo build --release"

Tried following the instruction to compile from the source code with cargo build --release but it didn't work, throwing a lot of warning messages, and ending on
error: build failed

Same with cargo install --path .:
error: failed to compile `longshot v0.4.2 (/home/coppini/bioinfo/wdl-nanopore/docker/longshot/longshot)`, intermediate artifacts can be found at `/home/coppini/bioinfo/wdl-nanopore/docker/longshot/longshot/target`

Caused by:
  build failed

I already had longshot==0.4.1 installed with conda, on ubuntu:20.04, so I tried installing it on docker, on ubuntu:18.04 as specified, but had the same problems.
Is there any docker images or Dockerfiles available for 0.4.2?


[BugFix] Allow large meta objects in rocksdb block cache to prevent slow BE restart

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Partially fixes #21873
Problem Summary(Required) ：

PK table's tabletmeta object size may got very large(lot's of edit versions), so it may not fit into block cache
that may impact BE load dir time when restart. here we change num_shard_bits to 0 to disable block cache sharding,
so large tabletmeta object can fit in block cache. After we optimize PK table's tabletmeta object size, we can
revert this config change.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


Allow multiple component hooks for a given Component

What problem does this solve or what need does it fill?
It could be useful to have multiple component hooks for a given Component.
A usecase would be to allow libraries to create component-hooks that won't be overriden by the user.
For example, you could imagine bevy_ecs wanting  to update change detection ticks via component hooks, while still allowing the user to define their own component hooks.
PROS:

increased flexibility
CONS:
performance? we would have to store a Vec of hooks instead of just Option
how to guarantee an ordering between the hooks?

What solution would you like?
Letting ComponentHooks store multiple hooks of a given type (on_add, on_remove, etc.) for a component.
What alternative(s) have you considered?

Use observers? (not too familiar with them)
do not allow multiple hooks

Broadly in favor of this: I think that this is going to be a frustrating limitation for end users and third-party crate authors.

performance? we would have to store a Vec of hooks instead of just Option

We should use a SmallVec: I would expect one or two of these hooks at once usually.


CLOUDSTACK-8655: [Browser Based Upload Volume] Partially uploaded vol…

…umes are not getting destroyed as part of storage GC
As part of volume sync, that runs during of SSVM start-up, the volume_store_ref entry was getting deleted. Volume GC relies on this entry to move volume to destroyed state.
Since the entry was getting deleted, GC thread never moved the volume from UploadError/UploadAbandoned to Destroyed. Fix is to not remove the volume_store_ref entry as part
of volume sync and let GC thread handle the clean up.

Test browser based incomplete volume upload, followed by SSVM destroy. Volume should go to UploadAbandoned/Error state and get cleaned up. ... === TestName: test_browser_upload_volume_incomplete | Status : SUCCESS ===
ok

Ran 1 test in 351.347s
OK

LGTM

LGTM

LGTM


Dart processes not exiting in flutter/engine are hard to debug on CI

Type of Request
feature request
Infrastructure Environment
I'm not sure.
What is happening?
Example: https://github.com/flutter/engine/pull/50255/commits/c6e7b5ba4fbfe1c0da0c7595d8b4d33875986e2a.
I inherited a tool (a Dart script called android_integration_tests.dart), that has a bug where it never terminates on CI. I'm still not sure why, but figuring out that the problem was never terminating on CI (since it does terminate locally) was really hard to debug.
@keyonghan and @christopherfujino asked me to file something:

Looks like the OS info is available in the beginning: https://ci.chromium.org/ui/p/flutter/builders/try/Linux Engine Drone/1936229/overview
but not collected when timing out.
Yeah, could you help file a bug to track OS info in the end?
I thought I landed a recipe change to do this (log OS info after a time out). Let me look it up, and see if I just missed some edge case.
never mind, I guess I just did that for devicelab tests: https://flutter.googlesource.com/recipes/+/24cc8a0d05ff25f461d4aac5e48cc6f726d93627^!/#F8

Steps to reproduce
No response
Expected results
No response

We should set up a time out of the specific test (smaller than the build timeout) to allow the os info collection to run in the end.

Also, if this is related to an emulator crash, the test should be able to catch the crash and exit early.

Just to be clear my specific case was a Dart script that ran an emulator, but I don't think the emulator crashed.

Just to be clear my specific case was a Dart script that ran an emulator, but I don't think the emulator crashed.

Add default timeouts for global/build tests: https://flutter-review.googlesource.com/c/recipes/+/55162

@matanlurey infra changes and docs have landed, can you please help us assigning the appropriate timeouts to the emulator tests in the engine json config files?

@matanlurey infra changes and docs have landed, can you please help us assigning the appropriate timeouts to the emulator tests in the engine json config files?

Yup, would love to do that - my only confusion is what to do if I'm happy with the default 1h timeout?
Just close this issue as done?

Yes, I believe we can close this bug as done, with enough time for the build to complete we will have access to the generic logs collection and process cleanup steps. We can also collect test specific logs updating the test script to collect any additional information and save it to "FLUTTER_LOGS_DIR" https://github.com/flutter/engine/blob/main/ci/builders/README.md#tests.
The defaults for tests steps are now:

3 retries on failures.
30 mins timeout

If a test times out it will retry it automatically, if you are ok with the default 30 mins test timeout then my only recommendation would be to increase the build timeout to something that allows enough time for the logs collection step to run. In this case something like 120 mins.
With enough time for the build to complete the dart processes being killed will be available in the cleanup step:

Perfect! This is great, thanks all!


Feature/modals awesome

Description

This PR kicks up the rad level of a couple components, mainly modals. It's a bit all over the place, which is a bummer. 😞  The good news is there a bunch of 👍  clean up work in here.
These are the changes included:

:sparkles: Added fixed-body class for modals
:sparkles: Added footer for modals
:sparkles: Switched some hard-coded CSS to use configurable variables
:white_check_mark: Added those sweet tests for my new feature
:white_check_mark: Got the tagging interaction button tests up and running
:memo: Wrote some rad documentation on using configurations

Tests

[x] I added tests for changes I made
[x] All tests are definitely passing

I fixed a merge conflict caused by my crazy dummy app updates


Not working in iOS release mode

Hi, testing your solution i found out it works fine in all platforms but doesn't apply translations in RELEASE-mode builds for iOS. No problem at all in DEBUG-mode.
I am currently testing in a physical device, I will post again here if i find a workaround for this.

@AdriVergara , thanks for letting me know. I will also look into this.

@AdriVergara , after a quick look at this, it could be linker related. I will do some more digging but you could try to add the following to you application project file.
<ItemGroup>
  <TrimmerRootAssembly Include="LocalizationResourceManager.Maui" />
</ItemGroup>

You can read more here: Linking a .NET MAUI iOS app

There's something wrong with the linker (and/or the LLVM compiler), indeed.
I was struggling with some functionalities (not related with your manager) in my maui app in iOS (release mode), so i have been trying some different iOS project configurations like the Linker Behavior and LLVM optimizing compiler. Finally i found this setting and it started working:

I'm not able to identify the exact moment it started working, though..
Didn't try your suggestion because i just saw it now and the previous configuration seems to be working.
Thanks a lot for the fast reply,


Write Windows linebreaks for TM and .txt files

@dks-mbta does TM have issues with the single "\n" newlines?

TM is sporadically crashing during the import, which might be related. It's also a problem viewing the human-readable files on Windows machines.


Numbers with underscores cause compilation error sometimes

fixes #2701
/cc @AviAvni

@forki thanks sorry for the missing need to add tests in https://github.com/Microsoft/visualfsharp/blob/master/tests/fsharpqa/Source/Conformance/BasicGrammarElements/Constants/BasicConstants.fs

Could you please send a pull request to my fork? Or just add another pull
request to the main fork and merge my stuff. Thanks
Am 26.03.2017 3:42 nachm. schrieb "Avi Avni"<EMAIL_ADDRESS>
@forki https://github.com/forki thanks sorry for the missing need to
add tests in https://github.com/Microsoft/visualfsharp/blob/master/
tests/fsharpqa/Source/Conformance/BasicGrammarElements/
Constants/BasicConstants.fs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/2702#issuecomment-289285376,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNOfzs73dKgfV1iWFP0G6SYbF_JMLks5rpms4gaJpZM4MpacQ
.

@forki I'll send PR with tests later

@forki @KevinRansom @dsyme
After I checked it when I implemented this feature I added this https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/FSharp.Core/prim-types.fs#L2523
but in the compilation of FSharp.Editing it uses the proto compiler and in ilSpy the FSharp.Core in the proto binary don't have this change

@aviavni yes it seems it's only happening in proto

@forki so no need tests if they fix this proto thing all be ok if they want this to be implemented in the lexer and not dependent in the FSharp.Core they can merge this PR

The thing is: we need to fix it in order to have it available in fsharp
itself. But good to know that other projects are not broken. So it's not
that urgent
Am 26.03.2017 7:50 nachm. schrieb "Avi Avni"<EMAIL_ADDRESS>@forki https://github.com/forki so no need tests if they fix this proto
thing all be ok if they want this to be implemented in the lexer and not
dependent in the FSharp.Core they can merge this PR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/2702#issuecomment-289301897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNKW1QuwOb2_vecyiDp22M-dOzlecks5rpqVhgaJpZM4MpacQ
.

@forki
Thank you for this .


Implement Marshalling for result structs containing Group elements

Fixes #57.
This changes these structs to require calling an EmptyResult(group) method, to fix the group used for unmarshalling.

@cronokirby  Wow as someone coming from Ruby/Python this is a mind-blower 🤯.  Thank you for the master-class on how to build marshalable data structures in Go.


Strict mode for scripts

If I have the following code using TSLint 2.1.0:
'use strict';

function example1(): number {
  return 123;
}

function example2(): string {
  return String(example1());
}

Which will generate the following output:
'use strict';
function example1() {
	return 123;
}
function example2() {
	return String(example1());
}

With the following TSLint settings:
"use-strict": [true,
  "check-module",
  "check-function"
],

Will produce the following errors:
src/test.ts[3, 1]: missing 'use strict'
src/test.ts[7, 1]: missing 'use strict'

This is wrong. The 'use strict' statement applies to all functions in the file (reference to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode). Can this be changed?

just turn off the check-function option please.

If you turn that off, it will not check the script scope. The module scope does not apply here.
Please test the example.


Different image types

Hi,
I am currently working with the ISIC-2017 dataset, that contains images as .jpg and masks as .png
When adding the ground truth masks, the output is:

0 ground truth image(s) found.

If I convert the image to .jpg, this problem disappears.
Is is possible to add support to .png?
Thank you,
Francisco

The problem is not the support of .png files since the library works fine with .png files but the extension file in images and groundtrith has to be the same.
From the documentation:
an image titled cat321.jpg will match with the image cat321.jpg in the ground_truth_directory. The function respects each image’s label, therefore the image named cat321.jpg with the label cat will match the image cat321.jpg in the subdirectory cat relative to ground_truth_directory.

Thank you very much!
Though it would be better to match through the same name, independently of the extension in use.


Add categorical sequence generators

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

Comparison is base (067f856) 100.00% compared to head (6f2fcdf) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #54   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           37        38    +1
  Lines         1305      1352   +47
  Branches        95        99    +4
=========================================
+ Hits          1305      1352   +47

Files Changed
Coverage Δ

src/startorch/sequence/__init__.py
100.00% <100.00%> (ø)

src/startorch/sequence/categorical.py
100.00% <100.00%> (ø)

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


open function

Type: Feature Request
To open another file i command.--> f =open("another.txt")
f.write("Please write this to the file")
f.close()
but this program is not running.
VS Code version: Code 1.72.1 (129500ee4c8ab7263461ffe327268ba56b9f210d, 2022-10-10T17:22:48.346Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Bug: 23 MB pdf (limit seems to be 10 MB) causes Java error with very little trace info

Capacitor version: 3.0.0

Run npx cap doctor:
💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 4.1.0
  @capacitor/core: 4.1.0
  @capacitor/android: 4.1.0
  @capacitor/ios: 4.1.0

Installed Dependencies:

  @capacitor/ios: not installed
  @capacitor/cli: 3.6.0
  @capacitor/core: 3.6.0
  @capacitor/android: 3.6.0

[success] iOS looking great! 👌
[success] Android looking great! 👌

Affected Platform(s):

Android

Current Behavior
App crashes with Java error while trying to open the FileShare popup on a native device or AVD.
This is before being able to choose the app to share the file with, the dialog simply won't open.
In Android Studio + the web console, the only error that's being shown is as follows:
E/Capacitor/Console: File: http://localhost/ - Line 316 - Msg: Error: Java exception was raised during method invocation
There doesn't seem to be more info than this, or it's just me not knowing how to get to that point.
Expected Behavior
The dialog to open.
Reproduction Steps
Try sharing this large PDF while on a device or AVD.

Little extra info:
If I simply wipe the contents of the public void share(final PluginCall call) { ... } method, it still won't work with a large base64 string. Same error pops up. It seems that the capacitor-PluginCall class somehow has trouble reading a large base64 string.
I've also tried not encoding the contents, in order to get a smaller string down the line, but it still has the same issue.

Made a PR to be able to send a local filepath instead of base64. It seems a large base64 string simply breaks as a capacitor plugin argument. This way, you pass a _capacitor_file_/directory/file-string and have this plugin fetch the contents into the base64 string.
If possible, plz merge or review 🙂

PR included in 4.0.0.


[BEAM-10114] Allow Pub/Sub Lite Sink to support increasing partitions

Change the publisher used by the beam sink from the RoutingPublisher which uses a static set of partitions determined at startup to the PartitionCountWatchingPublisher which watches for changes in the partition count.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @boyuanzz

R: @boyuanzz

Please fix Java PreCommit and Spotless. Other than test failures, changes look good to me.

Please fix Java PreCommit and Spotless. Other than test failures, changes look good to me.

Please fix Java PreCommit and Spotless. Other than test failures, changes look good to me.

Done! Thanks for the review :)

Please fix Java PreCommit and Spotless. Other than test failures, changes look good to me.

Done! Thanks for the review :)


Dataset object remains in promise class in Workspace unless it gets called

I've found that dataset object remains in promise status in Workspace when loaded with data() function until it explicitly gets called.

Run the following code in a clean R session:

library(ggplot2)
data(mpg)

Execute R: Focus on Workspace View

Check the class of mpg. It is displayed as mpg (promise).

Note: At this point, mpg$ doesn't trigger column-name auto-suggestion.

Run the following in R console:

class(mpg)
#> [1] "tbl_df"     "tbl"        "data.frame"

Execute R: Focus on Workspace View

Check the class of mpg. It is displayed as mpg (tbl_df).

Note: This time, mpg$ triggers column-name auto-suggestion.

Promise objects are intentionally kept as promises until evaluated by the user. It looks like when loading mpg, it is lazy loaded until interacted with. Is this unexpected behaviour?

Yes, I think any dataset when loaded with data() (e.g., data(airquality) is kept as promises until evaluated. For end-user who uses auto-suggestion for dataset column names, however, this is inconvenient. Because the users will have to evaluate the object to benefit from the auto-suggestion.
As you know, you can trigger column name suggestion in RStudio quite lazily. I was wondering if we could come up with any workaround.

Hmmm, we used to grab the names of promise objects, but this meant that they were effectively never lazy loaded. This was especially annoying for stuff like delayedAssign, which would essentially have no effect

The workspace viewer respects the evaluation status of objects in the global environment, i.e. if the object is a promise, we won't force it. Maybe we could allow user to opt-in to force evaluation?


Hunters Scan changed URL.

Source information
Hunters Scans 1.4.40
Source language
Portuguese Brazilian
Source new URL
https://htoons.online/
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Mudaram hj não foi?


feat: Business section is now validated when receiving a xml or json request

Description
Currently we do not validate the businessSection.type. This attribute holds information on, whether the request is for electricity (23) or gas (27)
Where we only support support electricity
References

Codecov Report

Merging #567 (d7bab1b) into main (21978a1) will decrease coverage by 31.91%.
Report is 237 commits behind head on main.
The diff coverage is 33.14%.

@@             Coverage Diff             @@
##             main     #567       +/-   ##
===========================================
- Coverage   83.07%   51.17%   -31.91%
===========================================
  Files         456      323      -133
  Lines       10418     6429     -3989
===========================================
- Hits         8655     3290     -5365
- Misses       1438     3040     +1602
+ Partials      325       99      -226

Files
Coverage Δ

...ivedMessages/ArchivedMessageGetDocumentListener.cs
0.00% <ø> (ø)

source/Api/Common/HttpHeadersExtensions.cs
0.00% <ø> (ø)

...iddleware/Authentication/ActorForAuthentication.cs
0.00% <ø> (ø)

...ntication/Bearer/BearerAuthenticationMiddleware.cs
0.00% <ø> (ø)

...MarketActors/MarketActorAuthenticatorMiddleware.cs
0.00% <ø> (ø)

...ation/Middleware/Correlation/CorrelationContext.cs
66.66% <ø> (ø)

.../Middleware/Correlation/CorrelationIdMiddleware.cs
0.00% <ø> (ø)

...iguration/Middleware/Correlation/UserProperties.cs
0.00% <ø> (ø)

...figuration/Middleware/FunctionContextExtensions.cs
0.00% <ø> (ø)

...rce/Api/Configuration/ServiceBusMessageMetadata.cs
0.00% <ø> (ø)

... and 77 more

... and 416 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add read access for metamist to list objects in dataset buckets

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

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #202   +/-   ##
=======================================
  Coverage        ?   90.66%
=======================================
  Files           ?        4
  Lines           ?      418
  Branches        ?        0
=======================================
  Hits            ?      379
  Misses          ?       39
  Partials        ?        0

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


Cookie lb support

This PR adds support for cookie based stickyness on loadbalancer.
Needs still docs, will add in coming commit
fixes #799
requires https://github.com/kontena/kontena-loadbalancer/pull/18

Looks good!


🎢 Separate deploy and test jobs in build pipeline

Separate the deploy of the proxy node build from the acceptance tests which follow.
This has two benefits:

re-run only acceptance tests through concourse if they fail in a triggered build.
prepare for ZDD - another new zdd test job should run in parallel to the deploy job, and acceptance tests should run after deploy.

Tested the pipeline locally 👇 showing separate deploy and test jobs :

It currently looks like:

Why remove the dependency passed build-proxy-node for the test image?
(I know it looks better and it's probably fine but want to check if there's any specific reason)

I chose to enforce build order on the chart resource (using the passed flag)  as its used in each job except test where its passed through.
The way I see it, we don't need to carry the test-image through delete and deploy jobs.

I've had to rebase, re-review please 🙏