increase performance in str2bytes and bytes2str conversions

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
increase performance in string to bytes and bytes to string conversions
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
Issue Number: N/A
What is the new behavior?
Other information

Codecov Report
Patch coverage: 44.44% and project coverage change: -26.49% :warning:

Comparison is base (5a33c7b) 66.32% compared to head (58a0e60) 39.84%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #809       +/-   ##
===========================================
- Coverage   66.32%   39.84%   -26.49%
===========================================
  Files         234      184       -50
  Lines       23132    19754     -3378
===========================================
- Hits        15343     7871     -7472
- Misses       6986    11542     +4556
+ Partials      803      341      -462

Flag
Coverage Δ

?

go-1.17.x
39.62% <44.44%> (-26.43%)
:arrow_down:

go-1.19.x
39.90% <44.44%> (-26.17%)
:arrow_down:

go-1.20.x
39.85% <44.44%> (-26.35%)
:arrow_down:

integration
?

macOS
39.77% <44.44%> (?)

ubuntu
39.78% <44.44%> (+0.02%)
:arrow_up:

unit
39.84% <44.44%> (+0.06%)
:arrow_up:

windows
39.79% <44.44%> (+0.05%)
:arrow_up:

ydb-22.5
?

ydb-23.1
?

ydb-23.2
?

ydb-23.2-slim
?

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

Files Changed
Coverage Δ

internal/value/value.go
61.39% <0.00%> (-3.87%)
:arrow_down:

log/field.go
64.45% <0.00%> (-10.43%)
:arrow_down:

internal/table/scanner/scanner.go
36.31% <25.00%> (-9.47%)
:arrow_down:

table/types/value.go
68.67% <83.33%> (-4.35%)
:arrow_down:

internal/decimal/decimal.go
51.82% <100.00%> (ø)

internal/secret/password.go
100.00% <100.00%> (ø)

internal/table/scanner/scan_raw.go
1.03% <100.00%> (-31.15%)
:arrow_down:

internal/tools/tools.go
100.00% <100.00%> (ø)

... and 169 files with indirect coverage changes

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

Benchmark_StdFromBytes-8        43264756                26.24 ns/op           48 B/op          1 allocs/op
Benchmark_FromBytes-8<PHONE_NUMBER>               0.3079 ns/op          0 B/op          0 allocs/op
Benchmark_StdToBytes-8          36847179                31.33 ns/op           48 B/op          1 allocs/op
Benchmark_ToBytes-8<PHONE_NUMBER>               0.3092 ns/op          0 B/op          0 allocs/op


Fix a bug in peribolos config

Add spec field to peribolos cron job config and rename the test-config to config.

Fix a but -> bug?

Fix a but -> bug?

yes, I've corrected the typo.

/lgtm


Invalid PDF url in README.md

Describe the bug
"阿里巴巴Java开发手册" url in README.md has been out of date.

感谢提出，已修复

修复了的话可以考虑close一下？


deprecation

The "Symfony\Component\HttpKernel\DependencyInjection\Extension" class is considered internal since Symfony 7.1, to be deprecated in 8.1; use Symfony\Component\DependencyInjection\Extension\Extension instead. It may change without further notice. You should not use it from "Lexik\Bundle\JWTAuthenticationBundle\DependencyInjection\LexikJWTAuthenticationExtension".

@lxregistry Can be closed as completed. Please see linked PR


Follow the whole instructions and triple check, but still not working

I hate to open a new issue asking about this question, but got no idea right now.
I am developing a share extention for my app and can't make it work.
Just keep getting these error messages.
2019-01-04 11:39:19.931 [error][tid:com.facebook.react.JavaScript] Native module cannot be null.
2019-01-04 11:39:19.930856+0800 O2ShareExtention[41778:2714130] Native module cannot be null.
2019-01-04 11:39:19.938 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Native module cannot be null.
2019-01-04 11:39:19.938015+0800 O2ShareExtention[41778:2714126] Unhandled JS Exception: Native module cannot be null.
2019-01-04 11:39:19.948 [error][tid:com.facebook.react.JavaScript] Module AppRegistry is not a registered callable module (calling runApplication)
2019-01-04 11:39:19.948537+0800 O2ShareExtention[41778:2714130] Module AppRegistry is not a registered callable module (calling runApplication)

And this is my system setup
React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
      Memory: 173.09 MB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v10.14.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        API Levels: 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3
    IDEs:
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.57.7 => 0.57.7
    npmGlobalPackages:
      react-native-git-upgrade: 0.2.7

Well, did you check what it is that is null when it shouldn't be?

I would start by checking whatever O2ShareExtention is.

O2ShareExtention is the name of my app share extention, just like the MyShareEx of sample code.

Yes, I assumed so. You'll need to find out why it's null.

I found that my problem is similar to this issue #94 ,but got no idea why the extension app looks like not loading/accessing to the js bundle.  The error message Module AppRegistry is not a registered callable module (calling runApplication) also indicates this, React Native Module is not loaded. This is currently what I have.

Well, finally I got it working. #48 did the trick.
Thanks dude.
@isaachinman


cli version does zero report on some servers while web interface works

Ookla's browser version can successfully do a test for example on Chicago Comcast server while speedtest-cli returns pretty much failed result:
[root@unifi ~]# speedtest --version
speedtest-cli 2.1.1
Python 3.6.6 (default, Mar 29 2019, 00:03:27) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
[root@unifi ~]# speedtest --list | grep Chicago | grep Comcast
1776) Comcast (Chicago, IL, United States) [9775.45 km]
[root@unifi ~]# speedtest --server 1776
Retrieving speedtest.net configuration...
Testing from Octopusnet LTD (<IP_ADDRESS>)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Comcast (Chicago, IL) [9775.45 km]: 1800000.0 ms
Testing download speed................................................................................
Download: 0.00 Mbit/s
Testing upload speed......................................................................................................
Upload: 0.00 Mbit/s
[root@unifi ~]# speedtest --secure --server 1776
Retrieving speedtest.net configuration...
Testing from Octopusnet LTD (<IP_ADDRESS>)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Comcast (Chicago, IL) [9775.45 km]: 1800000.0 ms
Testing download speed................................................................................
Download: 0.00 Mbit/s
Testing upload speed......................................................................................................
Upload: 0.00 Mbit/s
Issue appeared on May 2nd-3rd.
Not all of the servers fail but many.

host with the cli tool had no access on port 8080 outside. fixed on submitter side. sorry


RegisterBlockchainTx with empty codecName leads to invalid signature

Error: {
  "data": {},
  "log": "Signature invalid",
  "code": 3,
  "hash": {
    "0": 19,
    "1": 153,
    "2": 253,

Issue with how golang protobuf works...
We enforce canonical Form.
Which means zero values... 0, false, "", empty bytes, etc should be replaced by undefined. Same as with the memo field in SendTx.

Closing as this transaction type does not exist anymore in IOV-Core 0.14+. Hugnet clients just need to set a codecName.


test: properly test web platform tests

It seems that the tests are not passing, right?

It seems that the tests are not passing, right?

Yes, we had a bug in the test runner, which is now fixed. I'm currently tackled with the failed test case.


Building YCSB code

Hi,
I was trying to build the YCSB code in Ubuntu 12 64 bit and came across a lot of issues. There were a few packages missing. I have installed Maven 2 and all its dependencies. It is now complaining of some java jar files missing in classpath like slf4j etc. Can you please give me some information as to what should I do.
Also, I want the MongoDB version built only. Is there some build time flags that I can use?
Thanks and Regards,
Mainak.

closing as stale. if you are still having this problem please reopen.


fix typos

Curious how so many typos appear and how people find them.
Merging but not creating a new release.


Unable to uninstall although version to be uninstalled is listed

Operating system and version:
Windows 10
nvm debug output:

Running version 1.1.7.

nvm ls output:

18.20.5

How did you install nvm?
install script in readme
What steps did you perform?,  What happened?
C:\Users\dlatikay>nvm list
18.20.5
16.13.2

C:\Users\dlatikay>nvm uninstall 16.13.2
node v16.13.2 is not installed. Type "nvm list" to see what is installed.
What did you expect to happen?
I expected to be able to remove the version that is listed as installed.
Is there anything in any of your profile files that modifies the PATH?
no. also, other versions removed flawlessly

You're not using nvm, you're using nvm-windows, an entirely different project.


fix: 'ember' is replaced with 'ng' a bit too eagerly in log output

#1405
before: ng g c member-list output create src/app/ng-list/ng-list.component.scss.
after: ng g c member-list output  create src/app/member-list/member-list.component.scss.

Could you rebase on master please? This is fine by me, so LGTM.

Done


Create Lyrics “phoenix”

Automatically generated by Netlify CMS

:construction_worker: Deploy Preview for thar-ai processing.
:hammer: Explore the source changes: a6a441f5f270fb67b867eb03900d656fbde94ac9
:mag: Inspect the deploy log: https://app.netlify.com/sites/thar-ai/deploys/60ec28651892570007c52dca


Fix login and update problems

Current behaviour:
If a instance in a productive setup is updated then you are being logged out of the browser (chromium)
And if I start my Pc and then open/ call the url of the instance (also in productive Setup) then there is a loading symbol and 'Loading data. Please wait ...'
Wanted behaviour:
You should not be logged out if an instance is updated
Opening openslides for the first time of the day should not send you into a indefinitely spinning wheel

Additionally, this problem also occurs by opening content (e g. menus) in another tab. The problem is, that there is no clear reproduction.


typescript.SymbolTable does not properly implement the ES6 Map interface

TypeScript Version:  3.7.3
The typescript.SymbolTable is like an ES6 Map -- typescript.d.ts describes it as 'based on the ES6 Map interface'.
However, the underlying interface typescript.UnderscoreEscapedMap does not implement the Map interface, or the Iterable, or Iterator protocols. This means it's not possible to iterate over properly without shim code, which varies from manually implementing the Iterator protocol (annoying!) to overriding the type with as Map<ts.__String, ts.Symbol> (bad!).

Code Example
import * as ts from "typescript";

const p = ts.createProgram(["t.d.ts"], {});
const c = p.getTypeChecker();
p.getSourceFiles().map(f => {
    f.forEachChild(n => {
        if (!ts.isModuleDeclaration(n)) return;
        const s = c.getSymbolAtLocation(n.name);
        if (!s) return;

        const scanMembers = (s: ts.Symbol) => {
            if (s.valueDeclaration === undefined)
                console.log("missing valueDeclaration on", s.getName());

            type m = Iterator<any>
            if (!s.exports) return;
            if (!(Symbol.iterator in s.exports))
                return console.log("not iterable", s.getName())
            for (let [/*name*/, member] of (s.exports as Map<ts.__String, ts.Symbol>)) {
                scanMembers(member);
            }
        }

        scanMembers(s);

    })
})

typescript.UnderscoreEscapedMap is not recognized as a Map due to clear(), delete(), set(), [Symbol.toStringTag] and [Symbol.iterator] being undefined.

Testing map assertion
// Type 'ReadonlyUnderscoreEscapedMap<any>' is missing the following properties
// from type 'Map<any, any>': clear, delete, set, [Symbol.iterator],
// [Symbol.toStringTag] ts(2739)
const x: Map<any, any> = void 0 as any as ts.ReadonlyUnderscoreEscapedMap<any>

Perhaps this is a compiler internals issue, as using as Map<ts.__String, ts.Symbol> makes SymbolTables work without issue. If it's not, the fix should be as simple as replacing typescript.UnderscoreEscapedMap with Map and typescript.ReadonlyUnderscoreEscapedMap with ReadonlyMap.

Search Terms:
Code
import * as ts from "typescript";

const p = ts.createProgram(["t.d.ts"], {});
const c = p.getTypeChecker();
p.getSourceFiles().map(f => {
    f.forEachChild(n => {
        if (!ts.isModuleDeclaration(n)) return;
        const s = c.getSymbolAtLocation(n.name);
        if (!s) return;

        const scanMembers = (s: ts.Symbol) => {
            if (s.valueDeclaration === undefined)
                console.log("missing valueDeclaration on", s.getName());

            type m = Iterator<any>
            if (!s.exports) return;
            if (!(Symbol.iterator in s.exports))
                return console.log("not iterable", s.getName())

            // error!!
            for (let [/*name*/, member] of s.exports) {
                scanMembers(member);
            }
        }

        scanMembers(s);

    })
})

Expected behavior:
It should be possible to iterate over a typescript.SymbolTable.
Actual behavior:
typescript.SymbolTable is considered not iterable.

Perhaps this is a compiler internals issue, as using as Map<ts.__String, ts.Symbol> makes SymbolTables work without issue.

Everywhere except old IE, which will use src/shims/mapShim.ts.
I'd like love for the shim to go away and to switch to the standard map definition, this gets in my way frequently.

Is this on any roadmap? Not being able to iterate through symbol tables in a standard way makes life a bit difficult

Hi, sorry to comment on an old issue but I share the sentiment here 😅 I'm curious, does the UnderscoreEscapedMap preclude the SymbolTable from being iterated on?


Consume touchable-bounce from npm

CC: @brentvatne @ide
This is not going to work for now since react-native-touchable-bounce requires react-native (had to change it to be require('../../../') instead to avoid cyclic dependency.
Any suggestions how to solve that? I was thinking about making a package.json for each example similar to this -> https://github.com/grabbou/react-native-touchable-bounce/blob/master/example/package.json

There shouldn't be cycles if you make react-native be a peer dependency (but I don't know if it's actually a good idea to list react-native under peerDependencies). Just remove react-native from your dependencies and everything should still work.

cc @vjeux about moving this component to npm

In fact I do not depend on react-native at all @ide, it's just I am having require('react-native') in my index.js which is causing packager to wait forever for the bundle. Requiring via '../../../ works, which is because react-native itself also depends on that package.

Would it make sense to not depend on it at all? TouchableBounce sounds like sort of a special case of a button that could be a standalone npm module.


test(extension): refactor TransactionNewPage class

Checklist

[X] JIRA - LW-9507
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots
Attach screenshots here if implementation involves some UI changes

coverage: 52.976%. remained the same
when pulling cd9a1e739fb79effd313081ca8d89d39269feee2 on test/LW-9507_refactor_new_transaction_page_pom
into ab41aa3f194a409f0f6e145a96ef019d601fd8a9 on main.


fix the issue that Heron ECO stream builder does not handle IStatefulWindowedBolt

fix style check error
make Heron ECO stream builder handle IStatefulWindowedBolt
add unit test

@joshfischer1108 @nwangtw

The issue still persist even with this fix in our environment. There looks more work to troubleshoot.

lgtm

@simingweng The build error is from here:
Starting audit...
[ERROR] /home/travis/.cache/bazel/_bazel_travis/be6dac4936703c7eedcb4f5cf38cdd65/execroot/org_apache_heron/eco/src/java/org/apache/heron/eco/builder/heron/StreamBuilder.java:47: Line is longer than 100 characters (found 141). [LineLength]
Audit done.
Checkstyle ends with 1 errors.

@nwangtw as I mentioned in the previous comment. The code change in this pull request does not completely solve the problem. Even with the fix, the initState() and preSave() callback are still not invoked for a stateful bolt defined through ECO. But, I do see in the log that the bolt receives checkpoint request from Topology Master. I’ll need to look deeper, but kinda of stuck now. @joshfischer1108 any clue?

Hmm. Interesting. Calling setBolt() with IStatefulWindowedBolt should create a StatefulWindowedBoltExecutor object, which should call the initState() and preSave() functions.

I'll have to double check the code.. I wonder if somewhere along the line the bolt is being casted to an unexpected object.

@simingweng  I've re-looked over the code. I don't see any reason why adding the code you wrote wouldn't work.  Can you log which type of bolts are being returned in the topology builder somehow before submission?

@simingweng @nwangtw I'll have to double check the code.. I wonder if somewhere along the line the bolt is being casted to an unexpected object.

Yeah. Code looks fine. There ain't many classes along the path but it must have been changed in some way. Otherwise it should work.

One of the integration test on a sliding time window bolt has failed the CI. It’s not a stateful topology, isn’t it? I would assume it’s irrelevant to the change in this PR. @nwangtw @joshfischer1108 ideas?
[2019-04-18 23:26:22 +0000] [ERROR]: Actual result did not match expected result [2019-04-18 23:26:22 +0000] [INFO]: Actual result ----------  ['{"1":[{"tuplesInWindow":["1"]},{"newTuples":["1"]},{"expiredTuples":[]}]}', '{"2":[{"tuplesInWindow":["2","3"]},{"newTuples":["2","3"]},{"expiredTuples":["1"]}]}', '{"3":[{"tuplesInWindow":["4"]},{"newTuples":["4"]},{"expiredTuples":["2","3"]}]}', '{"4":[{"tuplesInWindow":["5"]},{"newTuples":["5"]},{"expiredTuples":["4"]}]}', '{"5":[{"tuplesInWindow":["6"]},{"newTuples":["6"]},{"expiredTuples":["5"]}]}', '{"6":[{"tuplesInWindow":["7"]},{"newTuples":["7"]},{"expiredTuples":["6"]}]}', '{"7":[{"tuplesInWindow":["8"]},{"newTuples":["8"]},{"expiredTuples":["7"]}]}', '{"8":[{"tuplesInWindow":["9"]},{"newTuples":["9"]},{"expiredTuples":["8"]}]}', '{"9":[{"tuplesInWindow":["10"]},{"newTuples":["10"]},{"expiredTuples":["9"]}]}'] [2019-04-18 23:26:22 +0000] [INFO]: Expected result ----------  ['{"1":[{"tuplesInWindow":["1"]},{"newTuples":["1"]},{"expiredTuples":[]}]}', '{"10":[{"tuplesInWindow":["10"]},{"newTuples":["10"]},{"expiredTuples":["9"]}]}', '{"2":[{"tuplesInWindow":["2"]},{"newTuples":["2"]},{"expiredTuples":["1"]}]}', '{"3":[{"tuplesInWindow":["3"]},{"newTuples":["3"]},{"expiredTuples":["2"]}]}', '{"4":[{"tuplesInWindow":["4"]},{"newTuples":["4"]},{"expiredTuples":["3"]}]}', '{"5":[{"tuplesInWindow":["5"]},{"newTuples":["5"]},{"expiredTuples":["4"]}]}', '{"6":[{"tuplesInWindow":["6"]},{"newTuples":["6"]},{"expiredTuples":["5"]}]}', '{"7":[{"tuplesInWindow":["7"]},{"newTuples":["7"]},{"expiredTuples":["6"]}]}', '{"8":[{"tuplesInWindow":["8"]},{"newTuples":["8"]},{"expiredTuples":["7"]}]}', '{"9":[{"tuplesInWindow":["9"]},{"newTuples":["9"]},{"expiredTuples":["8"]}]}'] [2019-04-18 23:26:22 +0000] [ERROR]: Checking result failed for<PHONE_NUMBER>1502_IntegrationTest_SlidingTimeWindow1_9c9a09a1-ceaf-4228-a509-b0edd3b876aa topology :: Traceback (most recent call last):   File "integration_test/src/python/test_runner/main.py", line 204, in run_test     return results_checker.check_results()   File "integration_test/src/python/test_runner/main.py", line 123, in check_results     return self._compare(expected_results, actual_results)   File "integration_test/src/python/test_runner/main.py", line 136, in _compare     raise failure TestFailure: ('Actual result did not match expected result', None)

One of the integration test on a sliding time window bolt has failed the CI. It’s not a stateful topology, isn’t it? I would assume it’s irrelevant to the change in this PR. @nwangtw @joshfischer1108 ideas?
[2019-04-18 23:26:22 +0000] [ERROR]: Actual result did not match expected result [2019-04-18 23:26:22 +0000] [INFO]: Actual result ---------- ['{"1":[{"tuplesInWindow":["1"]},{"newTuples":["1"]},{"expiredTuples":[]}]}', '{"2":[{"tuplesInWindow":["2","3"]},{"newTuples":["2","3"]},{"expiredTuples":["1"]}]}', '{"3":[{"tuplesInWindow":["4"]},{"newTuples":["4"]},{"expiredTuples":["2","3"]}]}', '{"4":[{"tuplesInWindow":["5"]},{"newTuples":["5"]},{"expiredTuples":["4"]}]}', '{"5":[{"tuplesInWindow":["6"]},{"newTuples":["6"]},{"expiredTuples":["5"]}]}', '{"6":[{"tuplesInWindow":["7"]},{"newTuples":["7"]},{"expiredTuples":["6"]}]}', '{"7":[{"tuplesInWindow":["8"]},{"newTuples":["8"]},{"expiredTuples":["7"]}]}', '{"8":[{"tuplesInWindow":["9"]},{"newTuples":["9"]},{"expiredTuples":["8"]}]}', '{"9":[{"tuplesInWindow":["10"]},{"newTuples":["10"]},{"expiredTuples":["9"]}]}'] [2019-04-18 23:26:22 +0000] [INFO]: Expected result ---------- ['{"1":[{"tuplesInWindow":["1"]},{"newTuples":["1"]},{"expiredTuples":[]}]}', '{"10":[{"tuplesInWindow":["10"]},{"newTuples":["10"]},{"expiredTuples":["9"]}]}', '{"2":[{"tuplesInWindow":["2"]},{"newTuples":["2"]},{"expiredTuples":["1"]}]}', '{"3":[{"tuplesInWindow":["3"]},{"newTuples":["3"]},{"expiredTuples":["2"]}]}', '{"4":[{"tuplesInWindow":["4"]},{"newTuples":["4"]},{"expiredTuples":["3"]}]}', '{"5":[{"tuplesInWindow":["5"]},{"newTuples":["5"]},{"expiredTuples":["4"]}]}', '{"6":[{"tuplesInWindow":["6"]},{"newTuples":["6"]},{"expiredTuples":["5"]}]}', '{"7":[{"tuplesInWindow":["7"]},{"newTuples":["7"]},{"expiredTuples":["6"]}]}', '{"8":[{"tuplesInWindow":["8"]},{"newTuples":["8"]},{"expiredTuples":["7"]}]}', '{"9":[{"tuplesInWindow":["9"]},{"newTuples":["9"]},{"expiredTuples":["8"]}]}'] [2019-04-18 23:26:22 +0000] [ERROR]: Checking result failed for<PHONE_NUMBER>1502_IntegrationTest_SlidingTimeWindow1_9c9a09a1-ceaf-4228-a509-b0edd3b876aa topology :: Traceback (most recent call last): File "integration_test/src/python/test_runner/main.py", line 204, in run_test return results_checker.check_results() File "integration_test/src/python/test_runner/main.py", line 123, in check_results return self._compare(expected_results, actual_results) File "integration_test/src/python/test_runner/main.py", line 136, in _compare raise failure TestFailure: ('Actual result did not match expected result', None)

CI has false alert sometimes. Let me trigger the build again.

@nwangtw CI checks have passed, it's ready for merging I think.


Added Playbooks and Analytic Rules for Pure Storage Solutions

Required items, please complete
Change(s):
Addition of playbooks and analytic rules for Pure Storage Solutions
Reason for Change(s):
Addition of playbooks and analytic rules for Pure Storage Solutions
Version Updated:
Yes
Testing Completed:
Yes
Checked that the validations are passing and have addressed any issues that are present:
Yes

@v-prasadboke , Thanks for looking into this, Let me know if there are any actions required from my end.

@v-prasadboke , Thanks for looking into this, Let me know if there are any actions required from my end.

Hello @skeerthivasan, Please fill up the metadata details in all the playbooks

@v-prasadboke , Thanks for looking into this, Let me know if there are any actions required from my end.

Hello @skeerthivasan, Please fill up the metadata details in all the playbooks

Hi @v-prasadboke , Thanks for your inputs, I've added requested details, please check and proceed.

Thanks @skeerthivasan, For committing the required changes

Thanks @skeerthivasan, For committing the required changes

@v-prasadboke , if its all fine, please proceed with merging. We need to push the changes into solutions package asap.

Thanks @skeerthivasan, For committing the required changes

@v-prasadboke , if its all fine, please proceed with merging. We need to push the changes into solutions package asap.

@v-prasadboke , did you get chance to look at this ? please help us in expediting, thanks

@v-prasadboke , I have fixed file issue and repushed, checks are passing now. Please check and proceed

@v-prasadboke , I have fixed file issue and repushed, checks are passing now. Please check and proceed

@v-prasadboke , can you please provide an update on this ? Thanks for your understanding.

@v-prasadboke , I have fixed file issue and repushed, checks are passing now. Please check and proceed

@v-prasadboke , can you please provide an update on this ? Thanks for your understanding.

Hello @skeerthivasan, There's something wrong with playbooks. After deploying the solution playbooks cannot be seen in the automation blade.
I'm finding the issue first

@v-prasadboke , I have fixed file issue and repushed, checks are passing now. Please check and proceed

@v-prasadboke , can you please provide an update on this ? Thanks for your understanding.

Hello @skeerthivasan, There's something wrong with playbooks. After deploying the solution playbooks cannot be seen in the automation blade.
I'm finding the issue first

@v-prasadboke , thanks for the update, I haven't seen any errors while packaging. Its strange to have this issue.
Let me know if you have any further pointers to proceed ? If required, I can join on a call to assist, let me know.

@v-prasadboke , I have fixed file issue and repushed, checks are passing now. Please check and proceed

@v-prasadboke , can you please provide an update on this ? Thanks for your understanding.

Hello @skeerthivasan, There's something wrong with playbooks. After deploying the solution playbooks cannot be seen in the automation blade.
I'm finding the issue first

@v-prasadboke , thanks for the update, I haven't seen any errors while packaging. Its strange to have this issue. Let me know if you have any further pointers to proceed ? If required, I can join on a call to assist, let me know.

@v-prasadboke , I was able to figure out the template issue and fixed the same. Also tested using preview links, its working fine. Please check and proceed with merge. Also solution offer certification(pushed from partner page) is pending for manual validation. If that comes to your review, please push the same or let relevant team to expedite. Thanks in advance.

@v-prasadboke , Any updates on this please

@v-prasadboke @v-rusraut , Thanks for merging PR.
Please take care of Solution offer review in Marketplace as well.


Exception: Call to Node module failed with error: ReferenceError: window is not defined

I using template https://github.com/MarkPieszak/aspnetcore-angular2-universal.
first request after server started is fine and reload it throw this error
Exception: Call to Node module failed with error: ReferenceError: window is not defined
at Ng2Webstorage.initStorageListener (/Users/roman_petrenko/git/source/elixir/node_modules/ng2-webstorage/bundles/core.umd.js:354:13)
at new Ng2Webstorage (/Users/roman_petrenko/git/source/elixir/node_modules/ng2-webstorage/bundles/core.umd.js:332:14)
at NgModuleInjector.AppServerModuleInjector.createInternal (/AppServerModule/module.ngfactory.js:576:28)
at NgModuleInjector.create (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8979:80)
at NgModuleFactory.create (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8953:22)
at /Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8523:65
at ZoneDelegate.invoke (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:229:26)
at Object.onInvoke (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:4427:41)
at ZoneDelegate.invoke (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:228:32)
at Zone.run (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:113:43)
at NgZone.run (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:4296:66)
at PlatformRef_.bootstrapModuleFactoryWithZone (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8521:27)
at PlatformRef.bootstrapModuleFactory (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8504:25)
at NodePlatform.bootstrapModule (/Users/roman_petrenko/git/modules/platform-node/node-platform.ts:505:31)
at NodePlatform.serializeModule (/Users/roman_petrenko/git/modules/platform-node/node-platform.ts:153:12)

It looks like ng2-webstorage is not compatible with angular2-universal. It seems angular2-cookies has support for universal. You can switch from using local storage to cookie storage by overriding the tokenStore provider in your app.module.ts.
  providers: [
    {
      provide: StormpathConfiguration, useFactory: stormpathConfig
    },
    {
      provide: 'tokenStore', useClass: CookieTokenStoreManager
    }
  ]

If that doesn't work, you could try implementing your own TokenStoreManager.

you absolutely right. ng2-websorage does not support universal. I replaced it with their store https://github.com/MarkPieszak/aspnetcore-angular2-universal/blob/master/Client/shared/cache/storage/storage.service.ts#L16-L21

If this works for you, please close this issue.


1.6.9 regression: failed passive exchange declare causes InvalidConnectionState

I recently encountered the titular regression in my test code after a cargo update.
Reproduce
With docker run --rm -d -p 5672:5672 rabbitmq running.
// [dependencies]
// lapin = "=1.6.9"
// tokio = { version = "1", features = ["full"] }

use lapin::{options::ExchangeDeclareOptions, Connection};

#[tokio::main]
async fn main() {
    let connection = Connection::connect("amqp://<IP_ADDRESS>:5672/%2f", <_>::default())
        .await
        .unwrap();

    let channel = connection.create_channel().await.expect("channel1");

    // expect this to fail as no such exchange exists
    // we also expect the channel to be dead now
    channel
        .exchange_declare(
            "foo-exchange",
            <_>::default(),
            ExchangeDeclareOptions {
                passive: true,
                ..<_>::default()
            },
            <_>::default(),
        )
        .await
        .unwrap_err();

    let _new_channel = connection.create_channel().await.expect("channel2");

    // non-passively declare exchange etc
}

lapin = "=1.6.9"
thread 'main' panicked at 'channel2: InvalidChannelState(Error)', src/main.rs:31:58
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

lapin = "=1.6.8"
No error.

Thanks a lot, will give it a look and add some regression test around this.
(I didn't know of <_>::default(), always used Default::default() :D)

Caused by 043704fb724d24152cb675808e87f129e2f1d51e
Didn't dig further yet but I probably know why (there's now a place where we set as error instead of just closing)

Fixed in 1.7.0

I'm also getting this InvalidChannelState(Error) error, but can't quite pinpoint it, any ideas?


How to keep checking (and refreshing) session?

Is there a recommend way to keep checking (and refreshing) the session?
There is an checkExpired config option, which when enabled will validate the session after configure, but this is only once, and I'm not sure if it refreshes the session when necessary.

refresh will be triggered automatically on any call based on the refreshThreshold value (at 50% of the ttl by default).
You could set it to 0 (on every call) if you desire but I wouldn't recommend it (too heavy on the database)

Ah alright, I sort of got that from the source code later on. I was confused, the original text made me search for a timing based system (setTimeout, setInterval), but when I didn't find this I assumed I had to do it manually. I'll try to do a suggestion for the readme.
Very nice that this is handled automatically.


Remove cancelled/done MemoryReservationFuture from the queue when freeing memory

If the MemoryReservationFuture has been cancelled or done when freeing memory, we should remove it from the queue, or it may lead to memory leak as showed in the following pic: The queries have finished, but the memory_reservation_size did not decrease.

Codecov Report

Merging #11137 (57a741e) into master (82188e3) will decrease coverage by 0.01%.
Report is 4 commits behind head on master.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master   #11137      +/-   ##
============================================
- Coverage     47.62%   47.61%   -0.01%
+ Complexity    23610    23607       -3
============================================
  Files          2784     2785       +1
  Lines        169885   169925      +40
  Branches      20268    20269       +1
============================================
+ Hits          80907    80911       +4
- Misses        88978    89014      +36

Files Changed
Coverage Δ

...db/db/queryengine/execution/memory/MemoryPool.java
78.94% <100.00%> (+0.13%)
:arrow_up:

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


[ROCm 3.1+] Switch util functions for HIP to hipMemcpyWithStream.

This API was introduced in ROCm 3.1 and provides a much faster path for
copies than hipMemcpyAsync followed by stream synchronize for H2D and
D2H copies, especially for unpinned copies.

@iotamudelta I will merge after 3.1 is released.

@saadrahim ping :-)

@saadrahim Sorry, didn't see your comment till now. Two parts - 1) the API is aware that the call is intended to be synchronous in stream, hence does not need to resolve any dependencies/wrap into async tasks which introduces overhead 2) it uses an optimized synchronous memcpy per stream (as opposed to the nullstream fallback for the old one).
So in scenarios where host memory is unpinned it is vastly more efficient, in cases where the host memory is pinned it is generally more efficient (how much depending upon transfer size and hardware config).


capturing visible portion of the web url

Hi,
I have captured the web url with the below command,
/usr/local/bin/pageres http://500.co/ --format jpg --dest /tmp/ --directory /tmp/ --filename raja
It captures everything in the url. Well and good.
Is it possible to capture the only visible part of the website url ?
Raja K

Yes, see the crop option.
Please use Stack Overflow in the future for support questions.


Incorrect Links on Bug Bounty Page

I found one and it made me dig for a few more on the Bug bounties page. :upside_down_face:
Under Community Bounties, the link to #StacksPack:

current link: https://www.blockstack.org/testnet/bounties#https://twitter.com/search?q=%23StacksPack
should be: https://twitter.com/search?q=%23StacksPack

Under Terms: Services in scope, some of the repo links need to be updated:
docs.blockstack: still resolves but points to old name

current link: https://github.com/blockstack/docs.blockstack
should be: https://github.com/blockstack/docs

cli-blockstack: points to older stacks 1 version, based on readme should be stacks.js

current link: https://github.com/blockstack/cli-blockstack
should be: https://github.com/blockstack/stacks.js/tree/master/packages/cli

stacks-transactions-js: was also moved to the same monorepo for stacks.js

current link: https://github.com/blockstack/stacks-transactions-js
should be: https://github.com/blockstack/stacks.js/tree/master/packages/transactions

bounties: could point to repo instead of the readme inside of it

current link: https://github.com/blockstack/bounties/blob/master/README.md
should be: https://github.com/blockstack/bounties

I made a pr for this, but I was unable to find the bounty links in this repo. I was able to the cli, transactions and docs links.


Adding more FAQs

Expected Behavior:
Adding more FAQs as per https://girlcodeit.com/#faqs
Current Behavior:
What is the current behavior?
Fewer FAQs present in the section currently
Solution:
I will make the required changes in the FAQ data file

Please assign me this issue as a part of GSSOC' 21

@aj3011 Please update the FAQs as below:

What is Opportunity Calendar?
Exactly what the title says : It's a calendar filled with opportunities in the tech industry for you!

Why is it needed?
Many a times, it's not that we don't have the right opportunities - it's that we don't know about them. The opportunity calendar serves the purpose of eliminating this hurdle- by keeping you abreast with all the latest relevant opportunities in the technology world.

How can you benefit?
The way we see it - the benefits are endless. Want to pursue your passion in coding? We're sure you'll find something here suited to your needs. Want to know what companies look for in their ideal candidate? You'll find it here!
It all depends on you from there on out!

How can you contribute?
This is the easiest job in the world. Keep your eyes and ears perked up for such opportunities, and once spotted, give one of us a heads up! As simple as that :)

Okay! Will do it. @vaishali614 Please assign this to me.


Send compliance events in a few more situations

Sending an event whenever the generation changes seems like a good idea
in general. Sending an event when the ComplianceState changes is
particularly useful because other components can use this as a
mechanism to ensure a new compliance event is generated.
Refs:

https://github.com/stolostron/backlog/issues/24750

Signed-off-by: Justin Kulikauskas<EMAIL_ADDRESS>

/cc @mprahl

/hold
I'll triple check this actually accomplishes what I want when I have all the patched images ready

/unhold rebased, and tested more locally

/unhold


Changelog: add a Changelog page & copy paste or automate from Github Changelog

Changelog should be the reposted version of https://github.com/airyhq/airy/releases/tag/0.6.0

@sgarroum How do you imagine this to look? One large page that includes all releases like Rasa does it?

@chrismatix yes that would be the best way, long list of all releases and changes with each release


[BUG]ChangeFeedProcessor on DedicatedGateway

Issue:
When using ChangeFeedProcessor with Dedicated gateway, LeaseLostException is being constantly observed.
Reason:
For Dedicated gateway, the default MaxIntegratedCacheStaleness is 5 minutes, and for cached query, single item update will not evict the cached query results. During load balancing time, staled/cached lease snapshot will be returned and due to the staled timestamp, leases which are actively being processed may mistakenly categorized as expired leases, and the taking ownership process may fail due to etag mistach.
Proposed solution:
using MaxIntegratedCacheStaleness=0 or BypassIntegratedCache(https://github.com/Azure/azure-cosmos-dotnet-v3/pull/3836)

@iainx assigning this one to you. Mike has a similar issue for Java. We can discuss in our next call.
Bottom-line: DedicatedCache is caching query results - and when nothing changes in a query returns the previously cached results. For Change Feed Processor the lease documents are kept in a Cosmos DB container - the load distribution of the ChangeFeedProcessor instances depends on queries against the lease container - these queries should be configured to side-step the dedicated cache - via setting MaxIntegratedCacheStaleness=0 or BypassIntegratedCache(https://github.com/Azure/azure-cosmos-dotnet-v3/pull/3836)
In java similar issue exists for the ThroughputControl metadata container.


Update node16 build image

Updated node16 build image to include additional tooling and dependencies

gcc
gcc-c++
libtiff-tools

Raised in error


Builds unexpectedly failing from Friday

Description
Hi,
I had some actions setup and I got issues from friday - nothing was changed in build.gradle or .yml files. Everything is working when building in Android Studio and in console on my Mac with same commands from actions.
It is an android app, built on every pushed commit and on every pushed tag using actions. It was working last time on thursday.
My actions had:
jobs:
  Build:
    name: Release
    runs-on: ubuntu-latest
    ...

After I got an issue, I have tried fixing runner as:
jobs:
  Build:
    name: Release
    runs-on: ubuntu-20.04
    ...

A few steps passed and it crashes on:
      - name: Build DEV apk
        run: ./gradlew assembleMyAppPackageDebug

More info on build related setup of my app:
build.gradle app module:
    compileOptions {
        targetCompatibility JavaVersion.VERSION_1_8
        sourceCompatibility JavaVersion.VERSION_1_8
    }

I have tried with JavaVersion.VERSION_11 - not working
build.gradle project:
classpath 'com.android.tools.build:gradle:7.3.1'

(inform me if you need more info, I am not sure what else I should include)
Thank you :)
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Runner Image
Image: ubuntu-20.04
Version: 20231025.1.0
Runner Image
Image: ubuntu-22.04
Version: 20231025.1.0
Is it regression?
Image: ubuntu-22.04   Version: 20231016.1.0
Expected behavior
Build should pass sucessfully.
Actual behavior
Build failed with some unexpected errors including build generated files
Repro steps
no steps

Hey @zeroDivider!
There really isn't enough information here to draw any conclusions. Please provide as much information as possible. Error logs, link to the failed launch, repro steps (as short as possible). I don't see anything among the updates between these versions of runners that could affect you, and our tests are also going well.

Hi, here are logs:
/home/runner/work/myaoov1-client-android/myappv1-client-android/app/src/main/java/com/myapp/user/ui/fragment/auth/PhoneNumberFragment.java:171: error: cannot find symbol

                safeNavigate(requireView(), PhoneNumberFragmentDirections.backToLogin());
> Task :app:compileButlerGmsDebugJavaWithJavac
                                                                         ^
  symbol:   method backToLogin()
  location: class PhoneNumberFragmentDirections

Thanks for your patient, I think we may be in different time zones.
I am afraid I cannot send link to build since it is private repository and I cannot make it public, text me if we can do something related to this small issue
It seems it has a problem generating navigation directions. Problem is that it was working until few days ago, I did not do anything about build or library versions. It is also working when building in Android Studio and in command line with same commands listed in my .yml files for GitHub Actions. (you can find it in initial issue description)
I put this in app module build.gradle:
apply plugin: "androidx.navigation.safeargs"

and this is in project build.gradle
classpath 'com.android.tools.build:gradle:7.3.1'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.8.10"
classpath 'androidx.navigation:navigation-safe-args-gradle-plugin:2.5.2'

I am using java 8 for compilation and I have also tried upgrading to 11 and 17 - no changes, still failing.

It's still really hard to say what is the real reason of this issue without repro steps or example project. It might be dependency issue in case you used inherited methods. I'm pretty sure you know that the error itself says that method backToLogin() wasn't recognised by compiler. I may only guess without full information here.
As I said, there were no changes between these two images that could affect your environment. Let's think about the hypothetical possibility that some of the libraries that we cannot yet calculate (without repro) were damaged. In this case, the next image should fix the situation (deployment is already in progress, should take about three days).
I'll be there for you if you found an opportunity to spoil more light on the issue. Might be helpful if you didn't saw it yet: https://stackoverflow.com/questions/25706216/what-does-a-cannot-find-symbol-or-cannot-resolve-symbol-error-mean

Okay. What do you need me to share?
name: "Everyday Development Build"

on:
  pull_request

jobs:
  build:
    name: Build
    runs-on: ubuntu-latest

    strategy:
      fail-fast: false

    steps:
    - name: Checkout branch
      uses: actions/checkout@v3

    - name: Clean
      run: ./gradlew clean

    - name: Build Butler Dev Environment (Google)
      run: ./gradlew app:assembleMyAppVariantDebug

    - name: Release to Firebase App Distribution (Google)
      run: FIREBASE_TOKEN=${{ secrets.FIREBASE_TOKEN }} ./gradlew appDistributionUploadMyAppVariantDebug

I know what is the error, but the fact is that your unchanged environment run same commands that I use last 6 month is now having an error in build. Every time before building, I do clean. So, there is no way your runner was saving something and suddenly it got removed.
This is navigation graph:
<fragment
        android:id="@+id/phoneNumberFragment"
        android:name="com.myapp.ui.fragment.auth.PhoneNumberFragment"
        android:label="PhoneNumberFragment"
        tools:layout="@layout/fragment_phone_number">
        ...
        <action
            android:id="@+id/back_to_login"
            app:destination="@id/signInFragment"
            app:launchSingleTop="true"
            app:popUpTo="@id/phoneNumberFragment"
            app:popUpToInclusive="true" />
    </fragment>

and androidx.navigation.safeargs based on that generates file with direction that we use in app later. This is the output:
public class PhoneNumberFragmentDirections {
  private PhoneNumberFragmentDirections() {
  }

  @NonNull
  public static NavDirections backToLogin() {
    return new ActionOnlyNavDirections(R.id.back_to_login);
  }
}

Directory is: app/build/generated/source/navigation-args/myAppVariant/debug/my/app/package/auth/PhoneNumberFragmentDirections.java
The file is not here after build is done and it says error: cannot find symbol since it is not there.
Just like you, I did not touch my local environment and everything works just fine, after I click Run 'app' green button and also in case I use command line - just like listed in my .yml file:
./gradlew app:assembleMyAppVariantDebug
I am successfully building and installing my app for days, on my computer and on computers of my co-workers.
Last time I merged and built successfully my latest commit and when problem started I tried pushing tag that is triggering my action, it did not work - no matter nothing changed:

GithubActions are not useful to me anymore, as simple as that. If I don't do a thing and it is failing, no point in using it anymore. I am not sure that you believe me when I say a thing did not change except UI - no build files, no graphs.
And the problem is not that that one method is unavailable. It seems no directions are generated. The only thing that changed is something on runner or in library (but I did not change library version)

@zeroDivider
Hey, in no way did I question your words about changes in the project. This is a very common situation when the cause of a build crash is an update of the tools involved in the process, or the dependencies that the project pulls up. This is the difficulty of your particular case. There were no visible changes to the base image that would even theoretically affect your build. In this case, we would have already come to a solution, but this is not it.
I am as interested in solving the problem as you are, but unfortunately this is not always a quick and easy process. At the moment, I believe that we have at least some basis from which we can build on in further investigation. I'll be back with clarifications later.

Just found this out myself. Had updated some docs and then my midi tests fail somehow: https://github.com/Wasted-Audio/hvcc/actions/runs/6716331081/job/18252650852#step:6:22
Reverting to ubuntu-20.04 "fixed it" for me, but it's really hard for me to trace what could've gone wrong in this case.
My tests rely on retrieving stdout and comparing it to a known file and the test-result seems to be it's comparing an empty list. However other tests that work similarly do succeed, so really no clue :shrug:

Hey @dromer! Do you believe that the missing file in this case was caused by the reasons you indicated? I suppose that the current problem (this issue) and yours should not be related, but I would be glad to be wrong.

@erik-bershel what do you mean missing file? I believe a file is created, but stdout is empty somehow.
I honestly don't know to which report this info should go (this was the first I spotted, then later saw more). The fact that other tests that work similarly (run binary; redirect stdout to file; compare with original) are successful just adds to the confusion.
Should I make a separate report then?

@dromer oh, no. I was asking about @zeroDivider issue with android app. Your issue seems not related to the current. It would be better to open new item.

Hi, @erik-bershel
Whatever you did, it worked! <3 It is okay now, my pipelines work like they did just last week.
(It also worked for short period yesterday, cca 18 hours ago, but shortly after that, it started failing again - now okay, as I mentioned)
Thank you for your support!

@zeroDivider I'm glad your builds is okay now. And I’ll add again - it’s really important for us to help users, unfortunately this doesn’t always happen as quickly and as easily as we would like.
A clarification regarding your case - we have not found the real reason for what happened. Looks like a transitive error when building one of the participating libraries (on the image side, not your project itself). Accordingly, hypothetically, this could appear again.

hypothetically, this could appear again.

Yep, it did appear again

@zeroDivider may I ask you to send build-link. No matter private or public. I'll check available information.

Hey @zeroDivider!
We will try to reproduce the error. Couple questions just to be on the same page:

Is it the same mistake now?
In case if it successfully builds in local environment please provide versions of installed software (gradle, android sdk, jdk).
If we have any suggestions (or questions), we will come back with additional information.

Hi, thanks for your reply.
Yes, of course :)

it is same error
installed software versions: gradle - gradle-7.4-all, android sdk - 33 (both compile and target), jdk - JavaVersion.VERSION_1_8

Have a nice day :)

@zeroDivider while we thinking could you be so kind to try run your wf with different Java setups?
example:
- uses: actions/setup-java@v3
  with:
    distribution: 'zulu'
    java-version: '17'

Supported distributions (NOTE: in images you may find Temurin 11.0.21+9 by default): https://github.com/actions/setup-java#supported-distributions

Hey,
I am not using actions for Java setup. I also have tried with java 11, but it was working just the same as with 8. And for Java 17, my app is not compatible with it.

@zeroDivider hmm. I'm not gradle-buld senior user, but it seems like you have to setup Java if you want to build on Java 8, because on image default version is 11. Yes, sure, you may do it on your own (not using actions) since Java 8 is being installed. And it might be distribution related issue too. It's the reason why I ask you to check your build on other versions of JDKs.

It is setup in gradle file and I have tried last time setting it up to 11.. did not work. At some point it started working, no one knew why.

@zeroDivider
Without access to the code, we cannot continue diagnostics on our part. Need a minimal project with a similar problem or a public fork of your project if possible.
Or we can try building with JDKs from other distributors on your side.
I would also like to ask you to check the peak amount of memory that is consumed during the build process in your local environment - I noticed that at a certain point in time the free RAM on the runner runs out. This could be one of the possible reasons if gradle run out of memory.

How much RAM is there on your runner? It is highly demanding build, I think. Android studio is requiring 8 GB RAM or more and it does very well in case there is 16GB+.
I'll try crating similar project when I get time and also do some research/upgrades around my app. For now I think I will disable my actions. It works just fine from Android Studio and from command line running same scripts. Somehow almost magically, it starts happening around runners update lately and I cannot help it, obviously.

Hi @zeroDivider!
Yes, sure, whatever is more convenient for you. Please, text me back when you have new information - I will be happy to join the investigation. Unfortunately, at the moment we can only guess what exactly happened from our side - we do not have access to private projects. Couple cents:

In the case of a blind search, I would start by checking different Java distributions - maybe it'll help catch a more informative error-message about why it fails generating navigation directions.
You can also dig into the optimisation of the build when using Gradle - since such processes are quite resource-intensive, free runners cannot always provide the required amount of resources. Perhaps they were not enough to assemble a component that was to be used later. A fair question would be why the environment did not throw an error in this case. You may read more information about such cases here: https://github.com/actions/runner-images/discussions/7188

So, please, feel free to ping me here about this issue and also feel free to open new items in case of other concerns.

Hi @zeroDivider!
Time was ~8 min and now it is ~4. Is it about build time in local environment or about time building in Actions before getting failure? Hope it's first option.
I'm still trying to find someone with a similar problem to yours. If I'm lucky, I'll be happy to share the information I find.


linux/arm64/v8

Please make version work with linux/arm64/v8

@ripaire whats the issue you are facing can you elaborate ?

@ripaire whats the issue you are facing can you elaborate ?

Make version work with arm64 processors that's it

A number of pull requests are attempting to address this

https://github.com/excalidraw/excalidraw/pull/8250
#7806
#6989
#6796
#3937

Excalidraw doesn't seem to care in adding support for anything other than amd64 because it is too hard for them to use docker buildx.


Support for read and write suggested datalen cmds

Host support for Read and Write Suggested Default Data Length HCI commands.

Style check summary
Our coding style is here!
nimble/host/src/ble_gap.c

@@ -5590,28 +5589,31 @@
 #endif
 }

-int ble_gap_set_data_len(uint16_t conn_handle, uint16_t tx_octets, uint16_t tx_time)
+int
+ble_gap_set_data_len(uint16_t conn_handle, uint16_t tx_octets, uint16_t tx_time)
 {
     return ble_hs_hci_util_set_data_len(conn_handle, tx_octets, tx_time);
 }

-int ble_gap_read_sugg_def_data_len(uint16_t *out_sugg_max_tx_octets,
-                                   uint16_t *out_sugg_max_tx_time)
+int
+ble_gap_read_sugg_def_data_len(uint16_t *out_sugg_max_tx_octets,
+                               uint16_t *out_sugg_max_tx_time)
 {
     return ble_hs_hci_util_read_sugg_def_data_len(out_sugg_max_tx_octets,
                                                   out_sugg_max_tx_time);
 }

-int ble_gap_write_sugg_def_data_len(uint16_t sugg_max_tx_octets,
-                                    uint16_t sugg_max_tx_time)
+int
+ble_gap_write_sugg_def_data_len(uint16_t sugg_max_tx_octets,
+                                uint16_t sugg_max_tx_time)
 {
     return ble_hs_hci_util_write_sugg_def_data_len(sugg_max_tx_octets,
                                                    sugg_max_tx_time);
 }

 /*****************************************************************************
- * $security                                                                 *
- *****************************************************************************/
+* $security                                                                 *
+*****************************************************************************/
 int
 ble_gap_security_initiate(uint16_t conn_handle)
 {

nimble/host/src/ble_hs_hci_util.c

@@ -189,7 +189,7 @@

 int
 ble_hs_hci_util_write_sugg_def_data_len(uint16_t sugg_max_tx_octets,
-                             uint16_t sugg_max_tx_time)
+                                        uint16_t sugg_max_tx_time)
 {
     struct ble_hci_le_wr_sugg_def_data_len_cp cmd;

Style check summary
Our coding style is here!
nimble/host/include/host/ble_gap.h

@@ -1889,10 +1889,10 @@
  * Configure LE Data Length in controller (OGF = 0x08, OCF = 0x0022).
  *
  * @param conn_handle      Connection handle.
- * @param tx_octets        The preferred value of payload octets that the
- *                         Controller should use for a new connection
+ * @param tx_octets        The preferred value of payload octets that the
+ *                         Controller should use for a new connection
  *                         (Range 0x001B-0x00FB).
- * @param tx_time          The preferred maximum number of microseconds that
+ * @param tx_time          The preferred maximum number of microseconds that
  *                         the local Controller should use to transmit a single
  *                         link layer packet (Range 0x0148-0x4290).
  *
@@ -1903,17 +1903,17 @@
                          uint16_t tx_time);

 /**
- * Read LE Suggested Default Data Length in controller
+ * Read LE Suggested Default Data Length in controller
  * (OGF = 0x08, OCF = 0x0024).
  *
  * @param out_sugg_max_tx_octets    The Host's suggested value for the
- *                                  Controller's maximum transmitted number of
- *                                  payload octets in LL Data PDUs to be used
+ *                                  Controller's maximum transmitted number of
+ *                                  payload octets in LL Data PDUs to be used
  *                                  for new connections. (Range 0x001B-0x00FB).
- * @param out_sugg_max_tx_time      The Host's suggested value for the
- *                                  Controller's maximum packet transmission
+ * @param out_sugg_max_tx_time      The Host's suggested value for the
+ *                                  Controller's maximum packet transmission
  *                                  time for packets containing LL Data PDUs to
- *                                  be used for new connections.
+ *                                  be used for new connections.
  *                                  (Range 0x0148-0x4290).
  *
  * @return                          0 on success,
@@ -1923,16 +1923,16 @@
                                    uint16_t *out_sugg_max_tx_time);

 /**
- * Configure LE Suggested Default Data Length in controller
+ * Configure LE Suggested Default Data Length in controller
  * (OGF = 0x08, OCF = 0x0024).
  *
  * @param sugg_max_tx_octets    The Host's suggested value for the Controller's
  *                              maximum transmitted number of payload octets in
- *                              LL Data PDUs to be used for new connections.
+ *                              LL Data PDUs to be used for new connections.
  *                              (Range 0x001B-0x00FB).
  * @param sugg_max_tx_time      The Host's suggested value for the Controller's
- *                              maximum packet transmission time for packets
- *                              containing LL Data PDUs to be used for new
+ *                              maximum packet transmission time for packets
+ *                              containing LL Data PDUs to be used for new
  *                              connections. (Range 0x0148-0x4290).
  *
  * @return                      0 on success,

nimble/host/src/ble_gap.c

@@ -5599,7 +5598,7 @@

 int
 ble_gap_read_sugg_def_data_len(uint16_t *out_sugg_max_tx_octets,
-                                   uint16_t *out_sugg_max_tx_time)
+                               uint16_t *out_sugg_max_tx_time)
 {
     return ble_hs_hci_util_read_sugg_def_data_len(out_sugg_max_tx_octets,
                                                   out_sugg_max_tx_time);
@@ -5607,7 +5606,7 @@

 int
 ble_gap_write_sugg_def_data_len(uint16_t sugg_max_tx_octets,
-                                    uint16_t sugg_max_tx_time)
+                                uint16_t sugg_max_tx_time)
 {
     return ble_hs_hci_util_write_sugg_def_data_len(sugg_max_tx_octets,
                                                    sugg_max_tx_time);

Style check summary
Our coding style is here!
nimble/host/include/host/ble_gap.h

@@ -1889,10 +1889,10 @@
  * Configure LE Data Length in controller (OGF = 0x08, OCF = 0x0022).
  *
  * @param conn_handle      Connection handle.
- * @param tx_octets        The preferred value of payload octets that the
- *                         Controller should use for a new connection
+ * @param tx_octets        The preferred value of payload octets that the
+ *                         Controller should use for a new connection
  *                         (Range 0x001B-0x00FB).
- * @param tx_time          The preferred maximum number of microseconds that
+ * @param tx_time          The preferred maximum number of microseconds that
  *                         the local Controller should use to transmit a single
  *                         link layer packet (Range 0x0148-0x4290).
  *
@@ -1903,17 +1903,17 @@
                          uint16_t tx_time);

 /**
- * Read LE Suggested Default Data Length in controller
+ * Read LE Suggested Default Data Length in controller
  * (OGF = 0x08, OCF = 0x0024).
  *
  * @param out_sugg_max_tx_octets    The Host's suggested value for the
- *                                  Controller's maximum transmitted number of
- *                                  payload octets in LL Data PDUs to be used
+ *                                  Controller's maximum transmitted number of
+ *                                  payload octets in LL Data PDUs to be used
  *                                  for new connections. (Range 0x001B-0x00FB).
- * @param out_sugg_max_tx_time      The Host's suggested value for the
- *                                  Controller's maximum packet transmission
+ * @param out_sugg_max_tx_time      The Host's suggested value for the
+ *                                  Controller's maximum packet transmission
  *                                  time for packets containing LL Data PDUs to
- *                                  be used for new connections.
+ *                                  be used for new connections.
  *                                  (Range 0x0148-0x4290).
  *
  * @return                          0 on success,
@@ -1923,16 +1923,16 @@
                                    uint16_t *out_sugg_max_tx_time);

 /**
- * Configure LE Suggested Default Data Length in controller
+ * Configure LE Suggested Default Data Length in controller
  * (OGF = 0x08, OCF = 0x0024).
  *
  * @param sugg_max_tx_octets    The Host's suggested value for the Controller's
  *                              maximum transmitted number of payload octets in
- *                              LL Data PDUs to be used for new connections.
+ *                              LL Data PDUs to be used for new connections.
  *                              (Range 0x001B-0x00FB).
  * @param sugg_max_tx_time      The Host's suggested value for the Controller's
- *                              maximum packet transmission time for packets
- *                              containing LL Data PDUs to be used for new
+ *                              maximum packet transmission time for packets
+ *                              containing LL Data PDUs to be used for new
  *                              connections. (Range 0x0148-0x4290).
  *
  * @return                      0 on success,

Style check summary
Our coding style is here!
nimble/host/include/host/ble_gap.h

@@ -1907,11 +1907,11 @@
  * (OGF = 0x08, OCF = 0x0024).
  *
  * @param out_sugg_max_tx_octets    The Host's suggested value for the
- *                                  Controller's maximum transmitted number of
- *                                  payload octets in LL Data PDUs to be used
+ *                                  Controller's maximum transmitted number of
+ *                                  payload octets in LL Data PDUs to be used
  *                                  for new connections. (Range 0x001B-0x00FB).
- * @param out_sugg_max_tx_time      The Host's suggested value for the
- *                                  Controller's maximum packet transmission
+ * @param out_sugg_max_tx_time      The Host's suggested value for the
+ *                                  Controller's maximum packet transmission
  *                                  time for packets containing LL Data PDUs to
  *                                  be used for new connections.
  *                                  (Range 0x0148-0x4290).

Style check summary
No suggestions at this time!

Hello @sjanc,
Could you please review this PR. Thanks!

@sjanc,
Can you please review?

Hi,
Could you describe your usecases for those?  While I can see case for setting default values from application, I don't see any usecase for reading those...

Hello @sjanc,

write suggested datalen command -
By default the data length is 27 bytes. If we suggest larger data length values, more data could be sent in a single transmission. This will reduce the fragmentation and hence more packets are sent quickly.

read suggested datalen command -
Bluetooth Specification has support for this HCI command. So logically added supported for read as well in this commit.


test: add generate-application integration tests [FTL-9010]

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


What ore dict name do you use

Is it like IronChunk or Ironchunk  or Ironchunk or something else

All the chunks are automatically registered as chunkIron etc. They are also registered as oreIron etc. by default but this can be changed to dustIron, clumpIron or any other name.

I made a mistake, the oredict name I'm using is actually oreChunkOrename, but you might have noticed that already.


Add broadcast test in test_math.py

Added broadcast tests in binary-arithmetic operation tests in test_math.py.
This PR changes the name of the parameter of shapes which BinaryMathTestBase and  InplaceBinaryMathTestBasetake: shape -> in_shapes.

Jenkins, test this please.

Jenkins CI test (for commit 09bb3c3b87f418191abf1011d2079995a2d99030, target branch master) failed with status FAILURE.

Should we relax the tolerances? https://jenkins.preferred.jp/job/chainer/job/chainer_pr/590/TEST=CHAINERX_chainerx-py3,label=mn1-p100/console

I'll fix the stochastic failure of TanTest in another PR.

LGTM!


KAFKA-6928: Refactor StreamsPartitionAssignor retry logic

The retry loop of the InternalTopicManager would just be: a) describe topics, and exclude those which already exist with the right num.partitions, b) for the remaining topics, try to create them. Remove any inner loops.

In CreateTopicResponse and MetadataResponse (for describe topic), handle the special error code of TopicExist and UnknownTopicOrPartition in order to retry in the next loop.

Do not handle TimeoutException since it should already been handled inside AdminClient.

Add corresponding unit tests for a) topic marked for deletion but not complete yet, in which case metadata response would not contain this topic, but create topic would return error TopicExists; b) request keep getting timed out.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mjsax @bbejeck @vvcephei

Was wondering, if we should add an integration test? Ie, create repartition topic, delete it, start streams. It should hit this case eventually if delete is slow. Thoughts?

I've thought about an integration test case, but the issue is that timing is quite hard to control here: most likely the delete topic will be completed even before streams starting phase start to ask for metadata. The unit test I've added here, is to verify that if a topic is marked for deletion but never completed, streams should "correctly" block in the retry logic until exhausted all retries and fail. I felt it provides a better coverage than the integration test itself.

Cherry-pick to 2.1


Avoid indicating distro-specific issues about databases

False positive, Distro-specific script issue reported against PostgreSQL JDBC driver
https://nvd.nist.gov/vuln/detail/CVE-2017-8806 is reported against

Dependency GAV: org.postgresql:postgresql:9.4.1212.jre7
False positive CPE: cpe:/a:postgresql:postgresql:9.4.1212.jre7
CPE filters that match?

cpe:2.3:a:postgresql:postgresql:-:*:*:*:*:debian:*:*
cpe:2.3:a:postgresql:postgresql:-:*:*:*:*:ubuntu:*:*

Is "target_sw" generally used to indicate distro-specificity in CPE filters on CVEs? If yes, should DependencyCheck perhaps ignore CPE filters that filter on "target_sw"?

The handling of the driver/connectors for databases was resolved as part of the fix for #946 (pending release). However, I agree that a long term enhancing the support for all of the portions of the CPE would help reduce some FP. I'm going to rename this issue and mark this as an enhancement request as the specific FP was already cleaned up.

additional filtering was added in 5.0.0.


fixed real world example links

Updated all the broken real world example links.

Thanks man, very much appreciated! 😅

:+1:


How is metaparticle expected to interact with CI/CD?

An important (and open) question.
Proposals wanted!

Maybe executing the binary with a detach flag could be good?
Return code would naturally reflect whether the application is running properly in the provider.
The provider (k8s/swarm/aci) could decide whether cleanup is necessary for resources in the failure case, or this could be exposed as a flag.
Just brainstorming.

Yeah, I think that's a great idea!
I might use an environment variable instead of a flag, since flags would require munging the command line.  Want to send a PR?
Thanks!

For CI/CD I'll need individual independent operations for at least:

building a docker image
deploying a docker container and detaching

I vote we try a simpler approach first, then go from there. Anyone have any functional reasons why we shouldn't do this with just environment variables? Say:

if METAPARTICLE_CI_BUILD == true then ONLY build
if METAPARTICLE_CI_PUSH == true then ONLY push the image
if METAPARTICLE_CI_DEPLOY == true then ONLY deploy and don't follow logs (however, the return code should reflect the final deployment status... which implies it should wait for a steady state after all probes have completed successfully).


Automate docker builds

Docker builds for dev, staging, master and releases should be automated and pushed to the uniwuezpd Dockerhub

Note: I have recently updated my own Larex Dockerization to use the new tomcat base image as well, but for CI you'd still need a host system that compiles the app (i.e. has maven installed). In my previous version I included compilation in the image itself (by using ubuntu base image). Using Ubuntu as base for a CI would not be a bad choice either IMHO.
But since you also seem have an independent mechanism, which somehow feeds to http://artifactory-ls6.informatik.uni-wuerzburg.de/artifactory/libs-snapshot/de/uniwue (automatically I assume), it would probably be easier to generalize that for the dev/staging/master distinction, and just wget it from there (as you already do in https://github.com/maxnth/LAREX_Docker).


Components that use children get their children set to nil after any rerenders

The faulty code is
https://github.com/fewkz/froact/blob/c9790a07feaea1ef6a598c0471ad8a12752251b0/froact.lua#L174-L176
It sets the children to be blank after the first render, which is bad. We can fix this by removing the line that sets the props[roact.Children] to nil, but we don't really want children to be in props. Haven't quite figured out a better solution yet.
For now, to fix, you have to do this following code: local children = hooks.useMemo(function() return children end, {props}), since the children will get set correct whenever props change.

we could store the children in a table that's weak on props, as a sort of weak cache so that we can recover the children on subsequent renders