text:
TLA

Adds initial support for TLA with some basic tests, resolving https://github.com/bytecodealliance/StarlingMonkey/issues/14.
There is still work to do on improving errors and unhandled rejections.
Also expands the test suite to better support error output testing to enable these follow-ups.
Note, this requires https://github.com/bytecodealliance/StarlingMonkey/pull/25 to land first for CI to pass.

Oops, hit the button without leaving a comment. This looks really great, thank you!
I requested a few changes, but I think they should all be fairly minor.

source: gharchive/pull-request

authors: guybedford tschneidereit

repo: bytecodealliance/StarlingMonkey

license_type: permissive

license_source: github-api


text:
Store::consume_fuel with u64::MAX prevents future use of Store::add_fuel

Currently the following test will fail:
    let mut config = Config::new();
    config.consume_fuel(true);
    let engine = Engine::new(&config).unwrap();
    let mut store = Store::new(&engine, ());
    store.add_fuel(u64::MAX).unwrap();

    // fuel wraps to i64 so the store has i64::MAX fuel now
    assert_eq!(store.consume_fuel(0).unwrap(), i64::MAX as u64);

    // consume all but one fuel
    assert_eq!(store.consume_fuel(i64::MAX as u64 - 1).unwrap(), 1);

    // confirm that one fuel remains
    assert_eq!(store.consume_fuel(0).unwrap(), 1);

    // try to add fuel to get to 11 more fuel
    store.add_fuel(10).unwrap();
    assert_eq!(store.consume_fuel(0).unwrap(), 11);  // <-- this assertion will fail since the store says it has 1 fuel

The "bug" is here where when 10 fuel is added the counters there look like:
[crates/wasmtime/src/store.rs:1411] adj = 9223372036854775807
[crates/wasmtime/src/store.rs:1412] &consumed_ptr = -1
[crates/wasmtime/src/store.rs:1413] fuel = 10

where adj is already i64::MAX  so adj.checked_add(fuel) overflows and we hit the overflow case which resets everything back to its prior value.
Unfortunately I don't think that this is fixable with the current APIs of Store. Currently Store::consumed_fuel will report how much fuel has been consumed for the entire lifetime of the store which requires keeping the fuel_adj counter around, meaning that we can't actually represent consuming u64::MAX fuel since the fuel_adj is an i64.
I don't know how to best fix this myself, but we have some fuzz targets using this pattern and suffering from it so we'll need to fix them.

Rather than resetting on overflow, what if we set to MAX - 1? or just MAX itself?

I believe this is now fixed now that consume_fuel is gone.

source: gharchive/issue

authors: alexcrichton fitzgen

repo: bytecodealliance/wasmtime


text:
[lightbeam] replace asserts by Errors in module.rs / translate_only

Just a simple PR to replace some asserts by Errors, i have not modify the code logic.
I notice that translate_only is translating wasm module linearly. In short that means that if the import section is after the table function you will get an Error.
I think this function should be rewrite to translate all the sections whatever their order inside the module.

@sunfishcode CI failed but it's not related to this PR.

Thanks!

authors: pventuzelo sunfishcode


text:
Readme Rust example without WASI?

I've tried things out for the first time, so I might be totally wrong. Hence I haven't opened a PR editing the readme, but I thought I ask first.
I've followed the steps from the Guest: Rust section of the readme. It starts with using wasm32-wasi as target. At the end you should use an adapter module to build the component. When I run wasm-tools component wit my-component.wasm I get lots of output that refers to WASI things. I guess that's correct.
But when I try to run it via Wasmtime, I get the error Error: import `wasi-stderr` not defined.
What worked for me is: Using wasm32-unknown-unknown as target. I then don't add the adapter and simply run:
wasm-tools component new ./target/wasm32-wasi/debug/my-project.wasm  -o my-component.wasm

The wasm-tools component wit my-component.wasm prints out what the readme says. When I run the resulting wasm file with Wasmime, it works as expected.

Yes WASI is not required and you can use the wasm32-unknown-unknown target as you've seen. The drawback to this is that many crates and the standard library won't work, along with standard utilities like println!. I think mentioning this in the README is fine since it's basically just dropping the --adapt argument as you've seen.

And what would be the fix to get the WASI version working? Is it a Wasmtime bug?

Ah I just answered a related issue about that, namely that this repository hosts a work-in-progress implementation which will move upstream to Wasmtime eventually.

authors: alexcrichton vmx

repo: bytecodealliance/wit-bindgen


text:
Zoom not working in Firefox (115.0.3)

When using react-flow-builder v2 rendered in Firefox browser, the zoom feature does not work as expected.
When I click my custom zoom buttons or the internal FlowBuilder zoom buttons:
Expected result:
View is updated accordingly in all modern browsers
Actual result:
View is not changed after zoom value is changed when rendered in Firefox. Works as expected in Chrome.
Callback onZoomChange does however provide the expected resulting zoom value also in Firefox. So only the rendered view is not updated.
My zoom handling code:
  const builderRef = useRef<IFlowBuilderMethod>(null);

//Called from click event handler on custom zoom buttons. Also tested with setting zoom numerical value.
  const handleZoom = (zoomtype: ZoomType) => {
    builderRef.current!.zoom(zoomtype);
  };

//Provided as FlowBuilders onZoomChange callback.
//This is called by FlowBuilder with the expected resulting value after zoom level change
  const handleZoomChange = (
    outDisabled: boolean,
    value: number,
    inDisabled: boolean
  ) => {
    setOutDisabled(outDisabled);
    setInDisabled(inDisabled);
    setZoom(value);
  };
        <FlowBuilder
          readonly
          ref={builderRef}
          nodes={nodes as INode[]}
          onZoomChange={handleZoomChange}
          zoomTool={{
            hidden: false,
            min: 10,
            max: 150,
            step: 5,
          }}
          onChange={handleChange}
          registerNodes={registerNodes}
        />

When using react-flow-builder v2 rendered in Firefox browser, the zoom feature does not work as expected.
When I click my custom zoom buttons or the internal FlowBuilder zoom buttons:
Expected result: View is updated accordingly in all modern browsers
Actual result: View is not changed after zoom value is changed when rendered in Firefox. Works as expected in Chrome. Callback onZoomChange does however provide the expected resulting zoom value also in Firefox. So only the rendered view is not updated.
My zoom handling code:
  const builderRef = useRef<IFlowBuilderMethod>(null);

//Called from click event handler on custom zoom buttons. Also tested with setting zoom numerical value.
  const handleZoom = (zoomtype: ZoomType) => {
    builderRef.current!.zoom(zoomtype);
  };

//Provided as FlowBuilders onZoomChange callback.
//This is called by FlowBuilder with the expected resulting value after zoom level change
  const handleZoomChange = (
    outDisabled: boolean,
    value: number,
    inDisabled: boolean
  ) => {
    setOutDisabled(outDisabled);
    setInDisabled(inDisabled);
    setZoom(value);
  };
        <FlowBuilder
          readonly
          ref={builderRef}
          nodes={nodes as INode[]}
          onZoomChange={handleZoomChange}
          zoomTool={{
            hidden: false,
            min: 10,
            max: 150,
            step: 5,
          }}
          onChange={handleChange}
          registerNodes={registerNodes}
        />

I see zoom property is no longer supported in Firefox~, but transform will make the position of Popover and Popconfirm abnormal. So recommend to use this feature in Chrome.

repo: bytedance/flow-builder

license: MIT


text:
vs2022不能编译过

F:\work\github\sonic-cpp\include\sonic/allocator.h(92,9): error C3861: 'builtin_ia32_pause': identifier not found
1>assert_test.cpp
1>document_test.cpp
1>F:\work\github\sonic-cpp\tests\document_test.cpp(17,10): fatal  error C1083: Cannot open include file: 'dirent.h': No such file or directory
1>error_test.cpp
1>F:\work\github\sonic-cpp\include\sonic/error.h(95,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/error.h(95,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/error.h(95,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/error.h(96,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/error.h(96,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/error.h(96,3): error C2535: 'int sonic_json::ParseResult::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/error.h(95,3): message : see declaration of 'sonic_json::ParseResult::attribute'
1>F:\work\github\sonic-cpp\include\sonic/error.h(96,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/allocator.h(92,9): error C3861: 'builtin_ia32_pause': identifier not found
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(55,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(55,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(55,3): error C2535: 'int sonic_json::WriteBuffer::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): message : see declaration of 'sonic_json::WriteBuffer::attribute'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(55,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(56,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(56,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(56,3): error C2535: 'int sonic_json::WriteBuffer::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): message : see declaration of 'sonic_json::WriteBuffer::attribute'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(56,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(57,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(57,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(57,3): error C2535: 'int sonic_json::WriteBuffer::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): message : see declaration of 'sonic_json::WriteBuffer::attribute'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(57,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(63,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(63,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(63,3): error C2535: 'int sonic_json::WriteBuffer::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): message : see declaration of 'sonic_json::WriteBuffer::attribute'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(63,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(78,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(78,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(78,3): error C2535: 'int sonic_json::WriteBuffer::attribute(void)': member function already defined or declared
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(49,3): message : see declaration of 'sonic_json::WriteBuffer::attribute'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(78,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(85,3): error C2988: unrecognizable template declaration/definition
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(85,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(85,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(85,37): error C2334: unexpected token(s) preceding '{'; skipping apparent function body
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(96,3): error C2988: unrecognizable template declaration/definition
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(96,3): error C2059: syntax error: '('
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(96,3): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(96,3): error C2059: syntax error: ')'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(97,10): error C2061: syntax error: identifier 'n'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(97,16): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(98,17): error C2061: syntax error: identifier 'top'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(98,10): error C2838: 'memcpy': illegal qualified name in member declaration
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(99,10): error C2988: unrecognizable template declaration/definition
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(99,10): error C2143: syntax error: missing ';' before '+='
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(99,10): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(99,14): error C2238: unexpected token(s) preceding ';'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(101,3): error C2065: 'always_inline': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(101,3): error C7525: inline variables require at least '/std:c++17'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(101,22): error C2144: syntax error: 'void' should be preceded by ';'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(102,17): error C2065: 'top': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(103,5): error C2065: 'top': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(28,48): error C2614: 'sonic_json::WriteBuffer': illegal member initialization: 'cap' is not a base or member
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,18): error C2039: 'buf_': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,34): error C2039: 'top_': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,50): error C2039: 'cap_': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,9): error C2614: 'sonic_json::WriteBuffer': illegal member initialization: 'buf_' is not a base or member
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,25): error C2614: 'sonic_json::WriteBuffer': illegal member initialization: 'top_' is not a base or member
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(31,41): error C2614: 'sonic_json::WriteBuffer': illegal member initialization: 'cap_' is not a base or member
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(32,9): error C2039: 'setZero': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(34,30): error C2065: 'buf_': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(38,5): error C2065: 'buf_': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(38,16): error C2039: 'buf_': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(39,5): error C2065: 'top_': undeclared identifier
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(39,16): error C2039: 'top_': is not a member of 'sonic_json::WriteBuffer'
1>F:\work\github\sonic-cpp\include\sonic/writebuffer.h(26,7): message : see declaration of 'sonic_json::WriteBuffer'

目前只支持 linux 平台，x86_64 haswell 架构，暂时不支持 msvc

有支持的计划吗？

有支持的计划吗？

@alan0526  msvc 有计划支持的，也欢迎社区同学一起参与。

现在能支持了吗？

@liuq19 windows + clang + x86_64支持吗？

repo: bytedance/sonic-cpp


text:
Add short/ushort support

Currently, cudpp supports char/uchar and int/uint, but not short/ushort.

The attached patch (vs. r285) adds short/ushort support for scan and reduce.
Tested only on Win7 x64, VS 2010, CUDA 4.0, on Fermi hardware. (I don't see why
it wouldn't work everywhere else just as well, but who knows...)

Original issue reported on code.google.com by m0b...@gmail.com on 29 Feb 2012 at 4:00
Attachments:

short.patch

This is awesome, thanks for the patch.

I would imagine this will work out of the box (I've got some compiling
issues on my side, so I'll have to track that down).

My concern, though, is compile time, which (as everyone on this list
knows) is really long. Adding 2 (possibly 4, if we do char) new
datatypes to a scan compile is expensive.

Strawman for discussion: Add this support and wrap it with a #define
that cmake could flag if a user wanted it. (I just don't see a lot of
people wanting to scan shorts or chars.)

Original comment by jow...@gmail.com on 29 Feb 2012 at 7:27

I think all datatypes, operators, and algorithms should be wrapped somehow for
compile-time enable/disable.  Adding CMAKE settings for them would be ideal.  A
core set of datatypes should be enabled by default.

Original comment by harr...@gmail.com on 29 Feb 2012 at 11:47

repo: byzhang/cudpp

license_source: bigquery


text:
BPMN.Model.Read source code ?

Can U provide
BPMN.Model.Read source code.
I'am trying to do bpmn file parsing with standart XmlDocument.
But I could'nt do it, maybe in source code BPMN.Model.Read have some explanation how to do it !

You can validate XML document by many free checkers with detailed report on possible errors. For instance, use this: https://www.businessprocessincubator.com/cloudapps/#web-service-221

Sorry, but wont need to validate bpmn files.
I want to read bpmn file. Searching workable solution with source code !
Could U explain how do U read and parse bpmn files ???

authors: Diaskhan bzinchenko

repo: bzinchenko/bpmnview

license: mit


text:
Adaptive Questionnaire still shows demo surveys

Describe the bug
#227 replaced AQ's own demo surveys with the Kitt4sme one, but the service still shows the demo surveys and the Kitt4sme one isn't accessible.
To Reproduce
Steps to reproduce the behavior:

Browse to https://kitt4sme.collab-cloud.eu/aq/
You should see the "Go to Demo" button is still there
Click on the "Go to Demo" button
You should see the three demo surveys are still there and the kitt4sme one is nowhere to be seen :-)

Expected behavior
The demo button should be gone and the Kitt4sme questionnaire available.
Additional context
#227 provided a docker compose file to test the kitt4sme questionnaire.

Not an issue anymore with the latest release 1.6.6---#307.


text:
🛑 cms5.alejtech.eu is down

In e8c9b8f, cms5.alejtech.eu (http://cms5.alejtech.eu/UserSystem/login/login.alej) was down:

HTTP code: 403
Response time: 314 ms

Resolved: cms5.alejtech.eu is back up in d536da7.


text:
🛑 www.leopoldov.sk is down

In e129e90, www.leopoldov.sk (https://www.leopoldov.sk/) was down:

HTTP code: 403
Response time: 905 ms

Resolved: www.leopoldov.sk is back up in 43d8605.


text:
how to parse java code snippet to AST?

Dear authors,
Thanks for sharing your code. This package is easy to use, while I still encounter some problems.
I want to parse some java code snippet, for example some java functions.
Could you tell me how can parse the java snippet to AST?
here is my code:
import javalang
tokens = javalang.tokenizer.tokenize('public String toString ( ) { return this . getClass ( ) . getName ( ) ; } /** * @return An arbitrary string. */ public String anotherString ( ) { return "An arbitrary string." ; }')
parser = javalang.parser.Parser(tokens)
tree = parser.xxx() // I don't know parse_xx should be here.
I always get the 'javalang.parser.JavaSyntaxError' exception.
Any help from you will be highly appreciated.

I had a similar problem generating AST from a source code java snippet. What I concluded is that you cannot produce a full CompilationUnit from a snippet that won't compile itself.
In that case, the best option you have is to split your snippet in code lines and use javalang.parse.parse_expression(line) separately on each line.
Okay now this won't give you the whole structure information that the AST would give you but still you can get a bunch of information about the code you are parsing.


text:
Minor updates

Use bindings module to resolve inotify.node

fixes a bug where inotify.node can not be located

Use Nan::TryCatch and Nan::FatalException

fixes deprecation warnings during install

Update deps for nan@^2.3.3

for good measure

Tested on node v0.10.33, v5.10.1, v5.11.0

👍

1.4.1 in NPM landed this change.


text:
🛑 CBTB Coffee House Shop is down

In eaac8fd, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1103 ms

Resolved: CBTB Coffee House Shop is back up in fa076f5.

repo: cachetech/service-status


text:
🛑 CBTB Coffee House Shop is down

In 11751c5, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1536 ms

Resolved: CBTB Coffee House Shop is back up in 3e0258b.


text:
🛑 CBTB Coffee House Shop is down

In 87bc28d, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 943 ms

Resolved: CBTB Coffee House Shop is back up in e6f5b08.


text:
🛑 CBTB Coffee House Shop is down

In 632d4c9, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 978 ms

Resolved: CBTB Coffee House Shop is back up in a489b53.


text:
🛑 CBTB Coffee House Shop is down

In 3f32251, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1059 ms

Resolved: CBTB Coffee House Shop is back up in a0137e5.


text:
🛑 CBTB Coffee House Shop is down

In b1d0b35, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1287 ms

Resolved: CBTB Coffee House Shop is back up in 98cf2c4.


text:
Support playwright

Playwright support would be nice.
Currently I'm using:
  inputs = {
    nix-playwright-browsers.url = "github:voidus/nix-playwright-browsers";
    nix-playwright-browsers.inputs = { nixpkgs.follows = "nixpkgs"; };
  };

# [...]
devenv.shells.default =
          let
            browsers = nix-playwright-browsers.packages.${system}.playwright-browsers_v1_47_0;
          in
          {
            packages = with pkgs; [
              playwright-driver.browsers
            ];

            env = {
              PLAYWRIGHT_NODEJS_PATH = "${pkgs.nodejs}/bin/node";
              PLAYWRIGHT_BROWSERS_PATH = "${(browsers)}";
              PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD = 1;
              PLAYWRIGHT_SKIP_VALIDATE_HOST_REQUIREMENTS = 1;
            };

I dont understand why you need this complicated arrangement.
You can simply do this:
  packages = with pkgs; [
    playwright-test
    playwright-driver
  ];

And you have playwright installed with browsers

I'm happy to accept a PR.

authors: bbigras domenkozar rvveber

repo: cachix/devenv


text:
feat: create "biome" hook, preserve "rome" hook as alias

This PR does the following:

Renames the "rome" hook to "biome", correcting any references to the rome tool.
Sets the "rome" hook as an alias to the "biome" hook as a backwards compatibility guard.
Adds relevant documentation to the README.

Fixes #428.

Sure thing, I'm not even sure when the files got formatted :sweat_smile:

I know it's failing as of my last commit. Currently trying to figure out by myself what am I doing wrong and why 👍🏼

I think the better approach here would be to use mkRenamedOptionModule to rename rome -> biome. You get the alias and people will be prompted to switch.

Implemented this approach. For some reason, the deprecation warning is not appearing when enabling the hook:
rome.enable = true;

There's no need to have both rome and biome in config.hooks.

I can't seem to make it work without having config.hooks entries for both tools.

From the failing build:
pre-commit-run> - hook id: nixpkgs-fmt
pre-commit-run> - files were modified by this hook

Ready!


text:
Graphs

Adds graphs to the collection page.
Graph 1: age and gender
Graph 2: adults vs kids vs adults l2 speakers

Oh! Need to add SSR logic!

Oh! Need to add SSR logic!

repo: cadia-lvl/samromur


text:
GH1369: Implemented MSBuild for VS2017

Created enums and logic for handling MSBuild 15/VS2017 for the MSBuild runner. Also created
unit test.

Any progress on this?

I have a PR submitted and an Addin on MyGet you can temporarily use.  I
will post it up when I am at a computer.
On Thu, Jan 5, 2017 at 4:56 AM Rasmus Mikkelsen notifications@github.com
wrote:

Any progress on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cake-build/cake/pull/1419#issuecomment-270606048, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABfthQ4LkKU1YPJAlTWpkk4pHndqwPcYks5rPL4-gaJpZM4LVE0b
.

@rasmus Here is it: https://www.myget.org/F/beta-cake-addins/api/v2
PM> Install-Package Cake.MsBuild15 -Version 1.0.

@phillipsj Thanks

relates to #1369

@phillipsj your changes have now been merged! Thanks for your contribution 👍

Ooops, didn't realize this already was merged 😄

Ok will do.
On Wed, Jan 11, 2017 at 10:46 AM Patrik notifications@github.com wrote:

@patriksvensson commented on this pull request.

In src/Cake.Common.Tests/Fixtures/Tools/MSBuildRunnerFixture.cs
https://github.com/cake-build/cake/pull/1419#pullrequestreview-16165736:

@@ -30,6 +30,8 @@ public MSBuildRunnerFixture(bool is64BitOperativeSystem)

         KnownMSBuildPaths.Add("/Program86/MSBuild/12.0/Bin/amd64/MSBuild.exe");

         KnownMSBuildPaths.Add("/Program86/MSBuild/14.0/Bin/MSBuild.exe");

         KnownMSBuildPaths.Add("/Program86/MSBuild/14.0/Bin/amd64/MSBuild.exe");

       KnownMSBuildPaths.Add("/Program86/Microsoft Visual Studio/2017/Enterprise/MSBuild/15.0/Bin/MSBuild.exe");

I think that we should add some tests for community and professional as
well here.

In src/Cake.Common.Tests/Unit/Tools/MSBuild/MSBuildRunnerTests.cs
https://github.com/cake-build/cake/pull/1419#pullrequestreview-16165736:

@@ -115,6 +115,23 @@ public void Should_Get_Correct_Path_To_MSBuild_Version_35(MSBuildToolVersion ver

         }

         [Theory]

       [InlineData(MSBuildToolVersion.VS2017, PlatformTarget.x64, false, "/Program86/Microsoft Visual Studio/2017/Enterprise/MSBuild/15.0/Bin/amd64/MSBuild.exe")]

       [InlineData(MSBuildToolVersion.VS2017, PlatformTarget.x86, false, "/Program86/Microsoft Visual Studio/2017/Enterprise/MSBuild/15.0/Bin/MSBuild.exe")]

I think that we should add some tests for community and professional as
well here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cake-build/cake/pull/1419#pullrequestreview-16165736,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfthbpV_DqXZeRO4UWjddQLxrxf9dheks5rRPltgaJpZM4LVE0b
.

I can submit another PR ;)
On Wed, Jan 11, 2017 at 10:47 AM Patrik notifications@github.com wrote:

Ooops, didn't realize this already was merged 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cake-build/cake/pull/1419#issuecomment-271904081, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABftheZxFZy_3kiPu9D44g8UYChRc_Mlks5rRPmWgaJpZM4LVE0b
.

authors: devlead patriksvensson phillipsj rasmus

repo: cake-build/cake


text:
🛑 xmr-node.cakewallet.com:18081 is down

In 33701ad, xmr-node.cakewallet.com:18081 (xmr-node.cakewallet.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: xmr-node.cakewallet.com:18081 is back up in cd057ce after 21 minutes.

repo: cake-tech/upptime-cakewallet


text:
Phinx cannot create indexes concurrently for postgres databases

There is no way to perform query which create index concurrently because phinx runs queries in transaction.
So migration have to has option to performs without transaction. For example, check this option in Phinx\Migration\Manager\Environment::executeMigration

Maybe indexes should be done outside of the transaction instead?

Sure. And phinx has to provide ability to do this.

Is there any workaround for this by now?

Closing due to lack of activity or out of scope. If there is new interest, please open a PR.

authors: gr1ev0us lorenzo matejstrasek othercorey

repo: cakephp/phinx


text:
Does anyone want to make a project to implement phinx using python3?

phinx is very easy to use, if it can be used in python, it should be a good choice. Just like the famous http requesst library, there are people in every language to do it.

This is not a valid bug or feature ticket here.

authors: dereuromark dream-mo


text:
feat: replace ReactQuill component with plain Quill

feat: replace ReactQuill component with plain Quill
Summary:
As using ReactQuill has limitations and a lot of bugs in nextJS, I create new issue in their repo and until that is fixed I did not find another way to make some of the wanted behaviours work.
Replaced with plain Quill which uses refs to manipulate inputs and keyDown changes.
Connected Apps PR
Fixes : DEV-159
Tests:
https://github.com/calimero-is-near/VM/assets/93442516/b1c1189b-bae3-4955-b580-d2be882aa53b

https://github.com/zenoamaro/react-quill/issues/936 is closed?

zenoamaro/react-quill#936 is closed?

He tagged me in another comment saying they have fix for it and not to open new issues, decided in the end to ditch react-quill as the new implementation offers much more flexibility regarding features

authors: MatejVukosav frdomovic

repo: calimero-is-near/VM

license: Unlicense


text:
Input has incompatible margin-top and placeholder 'top'

https://monosnap.com/image/ntOzZkaFffQUeuzGyqOIJIxDcNaT2j
Therefore placeholder is drawn over other elements

Thanks @deser. The input component has been re-written and is now TextField. Check out https://github.com/callemall/material-ui/commit/b607a571b34801eef2360018125a200428cd40e2

You are welcome!

authors: deser hai-cea

repo: callemall/material-ui


text:
Unable to install Material-ui via npm

Unable to install material-ui into a boilerplate. The boilerplate I am using is https://github.com/davezuko/react-redux-starter-kit
npm-debug.zip
The console logs and npm-debug logs are pasted/attached here.
D:\workspace\node\react-redux-starter-kit>npm install --save react-tap-event-plugin
react-tap-event-plugin@2.0.1 node_modules\react-tap-event-plugin
└── fbjs@0.8.6 (object-assign@4.1.0, ua-parser-js@0.7.12, loose-envify@1.3.0, promise@7.1.1, isomorphic-fetch@2.2.1, core-js@1.2.7)

D:\workspace\node\react-redux-starter-kit>npm install --save material-ui
npm WARN peerDependencies The peer dependency react-tap-event-plugin@^1.0.0 included from material-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "E:\\Programs\\Nodejs\\node.exe" "E:\\Programs\\Nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save" "material-ui"
npm ERR! node v4.5.0
npm ERR! npm  v2.15.9
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package react-tap-event-plugin@2.0.1 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer material-ui@0.16.2 wants react-tap-event-plugin@^1.0.0

npm ERR! Please include the following file with any support request:
npm ERR!     D:\workspace\node\react-redux-starter-kit\npm-debug.log

Versions

Material-UI: 0.16.2
React: ^15.0.0
Browser: NA

I'm closing this issue for #5573.

Okay, that should do for now. I am anyways just testing out boilerplates .. thanks pal.. Good work

authors: aksappy oliviertassinari


text:
Typescript errors with React 15.5

Problem description
Hi,
Since updating to React 15.5, I've had Typescript errors on every material-ui element.
Link to minimal working code that reproduces the issue
      return (
          // other elements
          <Dialog
          title="Error"
          actions={actions}
          modal={true}
          open={this.state.showModal}
        >

Alternatively you can review this small file which produces the same type error for MuiThemeProvider:
https://github.com/technion/erlvulnscan/blob/ccc50d7b93a249d6648a6185933c74efb3eb47ef/frontend/assets/erlvulnscan-entry.tsx
Produces errors:
(163,9): error TS2605: JSX element type 'FlatButton' is not a constructor function for JSX elements.
  Types of property 'render' are incompatible.
    Type '() => ReactElement<any>' is not assignable to type '() => Element'.
      Type 'ReactElement<any>' is not assignable to type 'Element'.

Versions

Material-UI: 0.17.2
React: 15.5.3
Browser: NA, this at webpack build time

To confirm, tested with material-ui@0.17.3, issue persists.

Sorry, but we don't support Typescript.

Thanks for the reply @mbrookes . To anyone who stumbles on this, I'm pretty sure #6543 is the fix.

authors: mbrookes technion


text:
Popover Component onFocus triggers popover twice

When using onFocus on an element like input or button it triggers Popover component but once you close the popover it triggers the popover again.
Expected Behavior
Popover from onFocus should only be triggered once, similar to onClick.
Current Behavior
Popover from onFocus triggers again after closing it.
Steps to Reproduce (for bugs)
https://codesandbox.io/s/3xq60qy30m
Your Environment

Tech
Version

Material-UI
1.0.0-beta.13

React
16.0.0

browser
Chrome Version 61.0.3163.100 (Official Build) (64-bit)

etc

This is the expected behavior for accessibility consideration, but now, I'm wondering how you could work around it 🤔.

Thanks for the quick response. Is this happening because once the popover is closed, it refocuses back on the origin onFocus element?

@litedesigns Yes, exactly. It's implemented with the following method.
https://github.com/callemall/material-ui/blob/39aa1b7df86b702e9cbf05ee2757606741c18a64/src/internal/Modal.js#L219-L224
We have been facing a similar issue with the SelectInput component. Our solution is close to ignoring the next focus event. In your case, it's gonna be challenging to implement what you are looking for. Listening for key events can also be useful. Anyway. I think that the issue is outside of the scope of the issue tracker of GitHub. I'm not sure we can do much about it.

authors: litedesigns oliviertassinari


text:
[fix #653] destructuring on undefined iconStyle object

Should fix #653

I agree. What do you think about 1ca251d71db80d27d8288f3217e5a7da3c760139 ?

:+1:

Thanks guys :+1:

authors: hai-cea tomesch troutowicz


text:
Fix Exception handling

I think we should probably wrap up the various Exceptions thrown throughout the API into a common run time exception.
Something like:
public class Flickr4JavaException extends RuntimeException;
What do you think?

Actually, just realised there is a FlickrException already.
I can just use that to wrap some of the other exceptions.  Am getting annoyed having to handle SaxException in my calling code. :-)
Am already having second thoughts about making it runtime now as some of the errors returned are not really exceptions so should probably be explicitly handling by the caller.

I've made a FlickrRuntimeException for non Flickr API Exceptions now


text:
[Cart] Can we really pass customer object in update cart

Reference
It suggests that along with customer_id we can pass customer object in update cart api... Not sure if its a mistake or if that's intentional and needs to be supported

Ditto with country object - can that be passed in its entirety?

repo: callmekatootie/medusajs-graphql


text:
Native Component for "RNCSlider" does not exist.

I already installed it and import it but this error shows
"Native Component for "RNCSlider" does not exist."

I got the same
https://take.ms/tSM5O

+1 I have the same error.

+1

+1

+1

You need to link and it works :
react-native link @react-native-community/slider

Yeah, exactly what @LG1710 said - you need to run react-native link @react-native-community/slider. Please check https://github.com/react-native-community/react-native-slider/blob/master/README.md for further instructions.

I don't think this should be closed - this did not fix it for me, I am still getting the same error

I don't think this should be closed - this did not fix it for me, I am still getting the same error

Same for me.
One thing to note is that I use Expo and have not ejected the app.
Do I have to eject the app in order to use this slider or should it work with Expo as well?

I think I am also suffering from this problem.
This is the commit from running react-native link @react-native-community/slider
https://github.com/fo-am/iCrapAppPro/commit/0ab743a8ce1d05bf41b6ed122a2da8b12e4e9a61
I am okay on Android, but on Ios I get

Invariant Violation: Invariant Violation: Invariant Violation: requireNativeComponent: "RNCSlider" was not found in the UIManager.

The manual installation method has me drag something from PushNotificationIOS into my xcode... is this really what is meant?

Having the same issue -- link command worked fine but for some reason I'm getting that same error.
I don't think the RN team should be alerting people to switch over to this package until this is resolved. Lots of man hours wasted collectively speaking.

Do pod install and it works.

@aidanw what if users do not want to eject their application? This seems like a more fundamental issue with a native component that should not be breaking.

I have never used any of the not ejected stuff so I am not sure of the limitations... but yeah this pretty fundamental ui element being funky is bad news.

pod install fixed it for me as well -- I was under the assumption that the react native link did it as well? :P

pod install if you're using cocoapods in your project. Worked for me.

Running the following worked for me:
$ react-native link @react-native-community/slider
$ cd ios/
$ pod install
$ cd ..
$ npm run run:ios

That being said your README needs to be updated with this and your example needs to be fixed either with complete instructions on how to build and run or make it less cumbersome to run.

Same error here
"@react-native-community/slider": "^1.1.2",

@muhammadwfa Did pod install not do the trick for you?

Actually this was not an issue
I solved by react-native-link
@bobber205

How did you end up solving it? @muhammadwfa

by linking
react-native link @react-native-community/slider

I had the same issue and for me this was due to the fact that I had overridden the ReactPackages in MainApplication.getPackages(). I had to add new ReactSliderPackage(); (imported from com.reactnativecommunity.slider.ReactSliderPackage;) to the returned list to fix this.

I'm seeing the same issue. Invariant violation: requireNativeComponent: "RNCSlider" was not found in the UIManager. I've tried re-linking using react-native link and react-native link @react-native-community/slider. I've tried running a manual pod install in the ios folder. And I've also tried blowing out and resetting all node modules.
My instance of Slider is imported like this:
import Slider from "@react-native-community/slider";
react-native-cli: 2.0.1
react-native: 0.59.4

Anyone else still seeing this issue?

In my case it didn't work after re-linking.
This fixed it

npm start -- --reset-cache
Followed by installed app deletion from emulator/device.
Then react-native run-<os>

Does this work without ejecting Expo?

If the above mentioned solutions are not working try to restart the app

I've cleared cache, linked, ejected etc.  No luck.  I've seen bits online that it won't work with Expo but possibly i've read that wrong.  Not explicit in the readme so assume that isn't the case.

Yeah, exactly what @LG1710 said - you need to run react-native link @react-native-community/slider. Please check https://github.com/react-native-community/react-native-slider/blob/master/README.md for further instructions.

Readme doesn't contain that ...

Same. Not working.

Same. Not working.

Depending on your RN version you should either be on 1.X.X or 2.X.X.
after linking, make sure that you run pod install for ios as well.

run pod install
Yes, helped for me. Lot of thanks!

I had the same issue and for me this was due to the fact that I had overridden the ReactPackages in MainApplication.getPackages(). I had to add new ReactSliderPackage(); (imported from com.reactnativecommunity.slider.ReactSliderPackage;) to the returned list to fix this.
I don't know the iOS variant for this but the idea is that you have to ensure your native code advertises all the native packages you need, including your dependencies. react-native link doesn't do that (and should probably warn about ?).

This works for me to fix the same issue when running on android simulator!

I'm seeing the same issue. Invariant violation: requireNativeComponent: "RNCSlider" was not found in the UIManager. I've tried re-linking using react-native link and react-native link @react-native-community/slider. I've tried running a manual pod install in the ios folder. And I've also tried blowing out and resetting all node modules.
My instance of Slider is imported like this:
import Slider from "@react-native-community/slider";
react-native-cli: 2.0.1
react-native: 0.59.4
react-native-slider: 1.1.3

Anyone else still seeing this issue?

I think its due to your React Native being of version < 0.6 but your Slider is version > 2.0. Either upgrade your React Native version or downgrade Slider to 1.x.x

In my case it didn't work after re-linking.
This fixed it
* `npm start -- --reset-cache`

* Followed by installed app deletion from emulator/device.

* Then `react-native run-<os>`

this worked for me

Doesn't work on expo for me, react-native-link is of no help

had the same issue, running react-native link, and pod install helped me as well. The README should be updated.

run pod install
Yes, helped for me. Lot of thanks!

I solved it with the next steps:

yarn add @react-native-community/slider@1.1.3
react-native link
restart your project with react-native start --reset-cache
and command which has to be in you scripts rm -rf node-modules && yarn install && cd ios && rm Podfile.lock && pod install, and voila!

If you see this error again, so restart your server and just try to run one more time.
P.S. Remember, that default version of the component is 2, which supports react-native >0.60. If you have react-native <0.60, you need to install @react-native-community/slider@1.1.3.

It is solved after running link.
I think it should be mentioned in the first page readme.

This works for me on RN 0.59
yarn add @react-native-community/slider@1.1.4
react-native link @react-native-community/slider
yarn add jetifier && yarn && npx jetify

yarn start --reset-cache #to reset the metro bundler

Do it like this!
1- npm install @react-native-community/slider –save
2- react-native link @react-native-community/slider
3- include in your script file like import { Slider } from 'react-native'   instead of import Slider from '@react-native-community/slider';
then expo start --clear
hopefully work for someone.

Do it like this!
1- npm install @react-native-community/slider –save
2- react-native link @react-native-community/slider
3- include in your script file like import { Slider } from 'react-native'  instead of import Slider from '@react-native-community/slider';
then expo start --clear
hopefully work for someone.

This worked for me.

@ashish-padakannaya  this worked, thanks man...

@techtunix Whats the point of adding and linking the @react-native-community/slider at all if you use the deprecated one from react-native?

yarn add @react-native-community/slider
npx pod-install
npx react-native run-ios

Note the last line there. That's what I'd been missing. Rebuild your app after adding native dependencies.

I think it's worth mentioning that one must build the app after linking the packages

I think it's worth mentioning that one must build the app after linking the packages

Can you reopen this please?
I also have the same problem with RN 0.63.
Shouldn't "autolink" work without any other intervention from us? Is this the problem? The "autolinking" fails somehow?
Thanks!

Restarting my Expo process worked for me (Using Expo 4.1.6)

authors: 1int 67millwood Ahmed-Badawy LG1710 LLesage Nikosmonaut NoeFabellon Stunner afilp aidanw ajjubbal bakkelim bobber205 brlocky buschco cmacdonnacha gabrielslach hsiaotinghung jamesmcn1 joIivier kurtmcintire margaridaDinis michalchudziak mstaicu muhammadwfa mynia nikechanhk pachun partriv pfeghali princiya ptaberg rckahale samdelong sandunmj strobox techtunix webraptor willedanielsson

repo: callstack/react-native-slider


text:
Create MOM-2023-11-16.md

What type of PR is this?

documentation
subproject management

What this PR does / why we need it:
Meeting Minutes, 16-NOV
Please Review

Thanks @grgpapadopoulos!

repo: camaraproject/BlockchainPublicAddress


text:
Readiness Checklist step 6 update proposal

With a reference to Issue camaraproject/WorkingGroups#139 (https://github.com/camaraproject/WorkingGroups/issues/139).
I suggest to discuss about step 6 of the Readiness Check List (https://github.com/camaraproject/WorkingGroups/blob/main/Commonalities/documentation/API-Readiness-Checklist.md)
The discussion is driven by the goal of not slowing dawn the possibility for an Operator to promote or sell an API in its marketplace. Step 6 requires two Operators to have implemented and tested an API. Because of this step, it can happen that a stable API can not be marked as v1.0.0 because a second Operator has not yet implemented it.
A proposal could be a modification of step 6 having just one Operator as mandatory and a second Operator or a CAMARA member as recommended.
We could also evaluate the possibility for an API to be promoted and published on a marketplace even if in Beta version. A Beta version is expected to have possible improvements with minor releases while a "full version" (e.g. v1.0.0) is expected to be more stable.
The idea is to gather, in this discussion, the opinion from the group and to present a possible solution to the Governance WG. this because it is a marketing decision rather than a technical one.

Dear all,
This is a long-standing discussion. I see pros (as raised by @FabrizioMoggio) and cons (as noted by @hdamker, probably also shared by GSMA in their goal to increase operator adoption).
GSMA has drafted a WoW between Product WS and CAMARA, with the aim to agree on an agile interaction model for collaboration between both tracks. Among other things, this WoW proposes how both tracks can work together to ensure release cadence of for APIs (important to manage expectations of developers and operator with regards to when new API releases will be available, and with which scope). I think this proposal is closely related to the versioning topic proposed in this issue.
GSMA Open Gateway Product WS will be presenting this WoW in next TSC meeting (7th Sept), in order to get feedback from TSC and finalise on details (e.g. periodicity of API releases). My suggestion is to escalate this issue to the TSC, leaving them to use i) this issue and ii) WoW, as input to decide way forward

@jordonezlucena I agree with you, if we can't find a solution we can escalate to the TSC. Anyway, just to verify if we are all on the same page, my proposal is to follow @hdamker suggestion to have V1.0.0 according to the current step six (two Operators, I see the value for GSMA) and to add to step six a note regarding the Beta version: if an API has completed all the required steps from the checklist but it is just implemented by one Operator, it can be anyway published on the market as Beta version.

@FabrizioMoggio @hdamker: we should steer all the discussion regarding when/how to achieve 1.0 through one single issue - otherwise, it is verify difficult to keep track of progress. I say this because I've just come up with a quite similar issue in Governance, see #85. I guess it falls within the scope of TSC.

@shilpa-padgaonkar how can we bring this discussion to TSC? I mean, what I need to do :-)

@FabrizioMoggio In the last TSC call it was agreed that I would label all issues in commonalities which are somehow relevant for release mgmt concept, under the label release mgmt so that they can be addressed once the topic of release mgmt (E2E) gets started/discussed within TSC in the next/upcoming TSC calls.
The TSC will reach out to you as soon as your point is on the agenda.

repo: camaraproject/Commonalities


text:
feat: auto white space

本次更新的内容主要为"中文与英文、数字之间添加空格"

md 原来有插件的

欢迎前来学习

我超 很完美的兼容🥳

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Add generated resource files to the repository

Currently make.go generates the zembed_*.go resource files (templates/css/js/&c) in its temp build directory to embed them in the final binaries.
We can check them in the main repository to make "go get" work out of the box with all the resources built in, at the expense of a fatter repository.
We can even use go generate. I guess this is a low-priory issue.

Fair do's. Should I close this?

Fair do's. Should I close this?

I think it's especially moot since afair one of the 0.9 release issues is about providing binaries to users. And I suppose devs weren't the ones you were concerned about for them having to cope with this generation.

I think it's especially moot since afair one of the 0.9 release issues is about providing binaries to users. And I suppose devs weren't the ones you were concerned about for them having to cope with this generation.

authors: mpl saljam

repo: camlistore/camlistore


text:
Querying workflow instances by variables

Support querying workflow instances by specific variables names & values.

Sounds interesting :+1:
Do you have an idea of how the GraphQL query/schema should look like?

it's a bit challenging with GraphQL as it requires static definitions of the args,
the easiest way would be to find some filter string that can be easily converted to JPA query or just provide extra sql clause (need to be careful with injections though)
maybe we can do something in the form of:
{
    variables(filter: "foo == \"bar\" and bar != null) {
      name
      value
}

A query string sounds like a simple way. But passing a SQL/JPA query as filter argument feels not right :sweat_smile:
What do you think about something like the following?
{
  variable(filter: { name: "foo", value_eq: "bar"}) {
    name
    value
  }
}

So, the workflow instances would be collected by the variables.
{
  variable(filter: { name: "foo", value_eq: "bar"}) {
    name
    value

    scope {
      workflowInstance {
        key
      }
    }
  }
}

Does this work for you?

@saig0 i think that this syntax restricts a single filter condition, i would make filter an array if possible for multi conditions

Ok. Let's try to make it as simple as possible (because filtering can get complicated :sweat_smile:).
Which queries do you need exactly?

@saig0 i don't have specific demands atm, it was more a suggestion for your project :)

We can give it a try and see how it works out. We should start with a filter for variables first that allow filtering by a variable name and a value. The value must match exactly to make it easy.

@saig0 @asaf any updates on this? We are looking for that feature too.
To be more specific, we have an order management system that creates many workflow instances, one instance for one order.
Lets say we have a variable "order" in each our process instance:
{
  "customer": {
    "msisdn": "123456789",
    "name": "John"
  },
  "items": [
	{
		"name": "some product 1",
                "quantity": 1
	},
	{
		"name": "some product 2",
                "quantity": 2
	}
  ]
}

Now we want to find all processes created by the same customer. At this point we can't know how exact json of each order looks. What we need to do is to find them all using a filter like "order.customer.msisdn": "123456789".
There is an example of how such GraphQL model can be implemented: https://chillicream.com/docs/hotchocolate/v12/integrations/mongodb#filtering
This is how HotChocolate (GraphQL implementation for .NET) interacts with MongoDB databases, transforming GraphQL queries into native MongoDB ones.
query GetPersons {
  persons(
    where: {
      name: { eq: "Yorker Shorton" }
      addresses: { some: { street: { eq: "04 Leroy Trail" } } }
    }
  ) {
    name
    addresses {
      street
      city
    }
  }
}

@aanodin no updates so far. Currently, I don't need this feature at the moment. So, I don't plan to implement something like this soon.
Your request is also more complicated than the initial one. Instead of finding a variable based on a concrete value, you want to find a variable (i.e. the process instance) based on a partial JSON value.
I'm not sure how we could implement this query based on JPA. ZeeQS is not bound to a specific database. Maybe, QueryDSL could help here, but not sure how far.

We hit through this use case too. I am new to graphql a bit. @saig0 - could you please elaborate what would it mean to support such kind of filter queries in zeeqs? What kind of code changes are required?

@shahamit you can have a look at the following examples:

process instance query filters by state using an option function parameter
process instance subscription filters by process key using an input type

From the code perspective, you would need to:

extend the GraphQL definition
implement the query resolver
extend the repository
write a few test cases

authors: aanodin asaf saig0 shahamit

repo: camunda-community-hub/zeeqs


text:
chore(repo): rename Camunda BPM Platform to Camunda Platform

Related to CAM-12950

Thanks, @koevskinikola, I have changed the mentioned file.

repo: camunda/camunda-bpm-spring-boot-starter


text:
Refactor Existing File Dialog

This is part of the overall dialog refactoring #959

remove hardcoded existing-file dialog in favor of reusable dialogs
implement new dialog in a way that it is configured through the client

Is this dialog currently implemented directly from the modeler? I think it is already handled by the normal operating systems' saving dialog..
The hardcoded-dialog function existingFile seems to be also used nowhere else.

https://github.com/camunda/camunda-modeler/pull/1008 will delete the hardcoded dialog in the backend. Since the dialog was never used anywhere in the modeler and the os-dependant existing-file handling is handled in electron#showSaveDialog, this can be closed when the #1008 is merged.

repo: camunda/camunda-modeler


text:
Allow to test multitenancy via GH labels in CI pipeline

          @jessesimpson36 what we can do now is allowing to test MT via GH labels so we don't change the default behavior yet we allow users to test MT if they want.

we can add a multiTenancy key in the tests and make it conditional like we have here:
https://github.com/camunda/camunda-platform-helm/blob/26a13e0f26be665166b7f23345b5c9da18ed1714/.github/workflows/test-integration-main.yaml#L74
Using that var to load an extra val file in the actual tests via TEST_HELM_EXTRA_ARGS.
Originally posted by @aabouzaid in https://github.com/camunda/camunda-platform-helm/issues/963#issuecomment-1764517364

Just for records, currently, zbctl (v8.3.0) doesn't support deploying to a multi-tenancy setup. Till that, it's not possible to properly test the MT in our workflow.

For the record, in W46 grooming, still zbctl doesn't support deploying to a multi-tenancy setup.

Wating for: https://github.com/camunda/zeebe/issues/14477

zbctl update has been de-prioritized so we cannot work on this task for the 8.5 release.

repo: camunda/camunda-platform-helm


text:
Bump bpmnlint-plugin-camunda-compat

Related to https://github.com/camunda/camunda-modeler/issues/3319

Guess we want to add local error messages. I don't know how to do that though.

I'll take this over.

:rocket:

This is how it looks like:

We should also bump the properties panel for the tests.

We should also bump the properties panel for the tests.
This is done via 8694ad4.

authors: barmac nikku

repo: camunda/linting


text:
[Do not Merge] Travis setup

Initial setup of CI and fixing of HTML validation issues.
There is still an issue with the branding that should be switched to an img tag like upstream https://github.com/wet-boew/wet-boew/blob/master/site/includes/brand.hbs

I rebased without fixing any of the new issues to show an example of what this catches

Hey @nschonni  -  this sets up automatic travis checks? Like @quidampepin says, this would be very useful on:
https://github.com/canada-ca/design-system and https://github.com/canada-ca/systeme-conception
It'd be useful here too since though so we can get contributions here - could you rebase and resubmit and one of us will accept it. Thanks!

Rebased, but I think I have to go over everything again since there are new issues and deleted/new files

OK, this should be landable now. There are more things to fix up that are still suppressed, but I don't want to hit a bad rebase again if you make more changes before this lands

authors: nschonni patlaj