[flutter_tools] yes | flutter doctor --android-licenses leads to broken pipe on macOS

This was obscured by a crash in a .catchError callback before https://github.com/flutter/flutter/commit/b8f5394a5ca6d2bce062d9d0a20aaffb4289fb4c
danny@Dannys-MacBook-Pro flutter % yes | flutter doctor --android-licenses
Warning: This version only understands SDK XML versions up to 2 but an SDK XML file of version 3 was encountered. This can happen if you use versions of Android Studio and the command-line tools that were released at different times.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"extension-level"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"extension-level"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: Errors limit exceeded. To receive all errors set com.sun.xml.bind logger to FINEST level.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}api-level>
All SDK package licenses accepted.======] 100% Computing updates...

Echoing stdin to the licenses subprocess failed:
SocketException: Write failed (OS Error: Broken pipe, errno = 32), port = 0
#0      _NativeSocket.write (dart:io-patch/socket_patch.dart:1195:34)
#1      _RawSocket.write (dart:io-patch/socket_patch.dart:1938:15)
#2      _Socket._write (dart:io-patch/socket_patch.dart:2385:18)
#3      _SocketStreamConsumer.write (dart:io-patch/socket_patch.dart:2128:26)
#4      _Socket._onData (dart:io-patch/socket_patch.dart:2356:19)
#5      _rootRunUnary (dart:async/zone.dart:1414:13)
#6      _CustomZone.runUnary (dart:async/zone.dart:1307:19)
#7      _CustomZone.runUnaryGuarded (dart:async/zone.dart:1216:7)
#8      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#9      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#10     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#11     _StreamController._add (dart:async/stream_controller.dart:648:7)
#12     _StreamController.add (dart:async/stream_controller.dart:596:5)
#13     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1876:23)
#14     _NativeSocket.issueWriteEvent.issue (dart:io-patch/socket_patch.dart:1354:14)
#15     _NativeSocket.issueWriteEvent (dart:io-patch/socket_patch.dart:1361:7)
#16     _NativeSocket.multiplex (dart:io-patch/socket_patch.dart:1396:13)
#17     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:192:26)

The relevant function looks like:
    try {
      final Process process = await _processManager.start(
        <String>[_androidSdk!.sdkManagerPath!, '--licenses'],
        environment: _androidSdk!.sdkManagerEnv,
      );

      // The real stdin will never finish streaming. Pipe until the child process
      // finishes.
      unawaited(process.stdin.addStream(_stdio.stdin)
        // If the process exits unexpectedly with an error, that will be
        // handled by the caller.
        .then(
          (Object? socket) => socket,
          onError: (dynamic err, StackTrace stack) {
            _logger.printError('Echoing stdin to the licenses subprocess failed:');
            _logger.printError('$err\n$stack');
          },
        ),
      );

      // Wait for stdout and stderr to be fully processed, because process.exitCode
      // may complete first.
      try {
        await Future.wait<void>(<Future<void>>[
          _stdio.addStdoutStream(process.stdout),
          _stdio.addStderrStream(process.stderr),
        ]);
      } on Exception catch (err, stack) {
        _logger.printError('Echoing stdout or stderr from the license subprocess failed:');
        _logger.printError('$err\n$stack');
      }

      final int exitCode = await process.exitCode;
      return exitCode == 0;
    } on ProcessException catch (e) {
      throwToolExit(_userMessages.androidCannotRunSdkManager(
        _androidSdk?.sdkManagerPath ?? '',
        e.toString(),
        _platform,
      ));
    }

The comment that the process exiting with an error will be handled by the caller appears not to be try (there is no error handling at the one non-test callsite in lib/src/doctor.dart

Oh, I see, this is just the stacktrace from the _logger.printError, since the sub-process exited 0 the tool also exited 0.

This is Danny's full log output:
danny@Dannys-MacBook-Pro flutter % yes | flutter doctor --android-licenses
Warning: This version only understands SDK XML versions up to 2 but an SDK XML file of version 3 was encountered. This can happen if you use versions of Android Studio and the command-line tools that were released at different times.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"extension-level"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"extension-level"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
Warning: Errors limit exceeded. To receive all errors set com.sun.xml.bind logger to FINEST level.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}api-level>
All SDK package licenses accepted.======] 100% Computing updates...

Echoing stdin to the licenses subprocess failed:
SocketException: Write failed (OS Error: Broken pipe, errno = 32), port = 0
#0      _NativeSocket.write (dart:io-patch/socket_patch.dart:1195:34)
#1      _RawSocket.write (dart:io-patch/socket_patch.dart:1938:15)
#2      _Socket._write (dart:io-patch/socket_patch.dart:2385:18)
#3      _SocketStreamConsumer.write (dart:io-patch/socket_patch.dart:2128:26)
#4      _Socket._onData (dart:io-patch/socket_patch.dart:2356:19)
#5      _rootRunUnary (dart:async/zone.dart:1414:13)
#6      _CustomZone.runUnary (dart:async/zone.dart:1307:19)
#7      _CustomZone.runUnaryGuarded (dart:async/zone.dart:1216:7)
#8      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#9      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#10     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#11     _StreamController._add (dart:async/stream_controller.dart:648:7)
#12     _StreamController.add (dart:async/stream_controller.dart:596:5)
#13     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1876:23)
#14     _NativeSocket.issueWriteEvent.issue (dart:io-patch/socket_patch.dart:1354:14)
#15     _NativeSocket.issueWriteEvent (dart:io-patch/socket_patch.dart:1361:7)
#16     _NativeSocket.multiplex (dart:io-patch/socket_patch.dart:1396:13)
#17     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:192:26)

Reducing priority as this is not blocking anyone, just a confusing user experience.

Ahh, so this is actually something we can most likely ignore (if the underlying sub-process has already finished, it doesn't really matter that we failed to forward tool stdin to it). This was previously being swallowed (and the stacktrace hidden unless you were in verbose mode) before sound null-safety. We should return to this behavior, with the added restraint that we toolexit if the sub-process exited non-zero.


CentOS 7.0 node/npm are not available under root

After installing via recipe[nodejs::nodejs_from_binary] node and npm are not available under root.

log?

Runlist:
    "recipe[nodejs::nodejs_from_binary]",
    "recipe[nodejs::npm]"
  ],

Attributes:
    "install_method": "binary",
    "version": "0.10.35",
    "source": {
      "checksum": "0043656bb1724cb09dbdc960a2fd6ee37d3badb2f9c75562b2d11235daa40a03"
    },
    "binary": {
      "checksum": {
        "linux_x64": "11f1e0ba34fb77d87db6f2c56898de881fdcf5bcde3e727f00456bfd976d2603",
        "linux_x86": "77b5afee7d5c2e089f432dd3b75e4f5df7dde107193c99a18828590e4f422615"
      }
    },
    "npm": {
      "install_method": "source",
      "version": "2.1.18"
    }
  }

Log:
  * ark[nodejs-binary] action install
    * directory[/usr/local/nodejs-binary-0.10.35] action create
      - create new directory /usr/local/nodejs-binary-0.10.35
      - restore selinux security context
    * remote_file[/var/chef/cache/nodejs-binary-0.10.35.tar.gz] action create
      - create new file /var/chef/cache/nodejs-binary-0.10.35.tar.gz
      - update content in file /var/chef/cache/nodejs-binary-0.10.35.tar.gz from none to 11f1e0
      (new content is binary, diff output suppressed)
      - restore selinux security context
    * execute[unpack /var/chef/cache/nodejs-binary-0.10.35.tar.gz] action nothing (skipped due to action :nothing)
    * execute[set owner on /usr/local/nodejs-binary-0.10.35] action nothing (skipped due to action :nothing)
    * link[/usr/local/bin/node] action create
      - create symlink at /usr/local/bin/node to /usr/local/nodejs-binary-0.10.35/bin/node
    * link[/usr/local/bin/npm] action create
      - create symlink at /usr/local/bin/npm to /usr/local/nodejs-binary-0.10.35/bin/npm
    * link[/usr/local/nodejs-binary] action create
      - create symlink at /usr/local/nodejs-binary to /usr/local/nodejs-binary-0.10.35
    * template[/etc/profile.d/nodejs-binary.sh] action create (skipped due to only_if)
    * ruby_block[adding '/usr/local/nodejs-binary-0.10.35/bin' to chef-client ENV['PATH']] action run (skipped due to only_if)
    * execute[unpack /var/chef/cache/nodejs-binary-0.10.35.tar.gz] action run
      - execute /bin/tar xzf /var/chef/cache/nodejs-binary-0.10.35.tar.gz --strip-components=1
    * execute[set owner on /usr/local/nodejs-binary-0.10.35] action run
      - execute chown -R root:0 /usr/local/nodejs-binary-0.10.35

Recipe: nodejs::npm_from_source
  * ark[npm] action install_with_make
    * directory[/usr/local/npm-2.1.18] action create
      - create new directory /usr/local/npm-2.1.18
      - restore selinux security context
    * remote_file[/var/chef/cache/npm-2.1.18.tgz] action create
      - create new file /var/chef/cache/npm-2.1.18.tgz
      - update content in file /var/chef/cache/npm-2.1.18.tgz from none to 741c0b
      (new content is binary, diff output suppressed)
      - restore selinux security context
    * execute[unpack /var/chef/cache/npm-2.1.18.tgz] action nothing (skipped due to action :nothing)
    * execute[set owner on /usr/local/npm-2.1.18] action nothing (skipped due to action :nothing)
    * execute[autogen /usr/local/npm-2.1.18] action nothing (skipped due to action :nothing)
    * execute[configure /usr/local/npm-2.1.18] action nothing (skipped due to action :nothing)
    * execute[make /usr/local/npm-2.1.18] action nothing (skipped due to action :nothing)
    * execute[make install /usr/local/npm-2.1.18] action nothing (skipped due to action :nothing)
    * execute[unpack /var/chef/cache/npm-2.1.18.tgz] action run
      - execute /bin/tar xzf /var/chef/cache/npm-2.1.18.tgz --strip-components=1
    * execute[set owner on /usr/local/npm-2.1.18] action run
      - execute chown -R root:0 /usr/local/npm-2.1.18
    * execute[autogen /usr/local/npm-2.1.18] action run (skipped due to only_if)
    * execute[configure /usr/local/npm-2.1.18] action run
      - execute ./configure
    * execute[make /usr/local/npm-2.1.18] action run
      - execute make
    * execute[make install /usr/local/npm-2.1.18] action run
      - execute make install

Fixed by configuring sudo secure_path

Hi @andre1810
Can you give us more details about your fix? :)

I set Defaults      secure_path = /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/binin /etc/sudoers file.

It's not adding to the PATH variable, due to this wrong skip
ruby_block[adding '/usr/local/nodejs-binary-0.10.35/bin' to chef-client ENV['PATH']] action run (skipped due to only_if)
I can't figure out how to correct it.
Do you have any idea @mdxp @guilhem?

I've made some more tests and it seems to only don't alter $PATH to root user.
So, not a real problem.

My problem is missing 'npm' soft link in /usr/local/bin and not just for root user.


Bump pip version

We were pinned to a hilariously old pip that was failing to parse some
requirements coming in from oslo.

The packages are to blame! No backwards compatibility? We are only like 6 major versions behind.

++


Doesnt Work

I sent to my own whatsapp and didn't do anything.  just my browser opening up every time an "attack" was launched.

What browser? Just random web?


[terra-icon] Bump one-cerner-style-icons to v1.51.0

Summary

Bumping icon library to the latest version.
Testing

This change was tested using:

[x] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Thank you for contributing to Terra.
@cerner/terra

Looks like some Jest snapshots changed which is failing the build. We can probably go ahead and update them.


[SD-1146] Implement Explain for MongoDB interpreter

Makes some minor modifications to the Explain constructor and adds the implementation for MongoDB.
An output file is added to the Explain constructor as, in this PR, there is no support for streaming queries and it seemed to make sense to handle this in one spot rather than have each backend have to do it. Note that the client API does not require an output file as either the first one from the LP is used or a placeholder is used.

I am not sure I understand the link between not having streaming support in this PR and having to add a file parameter to the Explain term. Do we need to hit MongoDB in order to come up with the PhaseResults?

The link is that the only way to currently execute a LogicalPlan requires the backend to provide the path out the output in the filesystem, thus every execution plan must have someplace to write the output to. It doesn't seem correct to then also ask the backend to explain how it plans on executing a query without also providing it someplace to write the planned results to.
The choice of whether the results of a plan should be written to the filesystem or streamed may also affect the plan itself. i.e. you get a different plan based on which you choose or maybe a particular LogicalPlan isn't executable in streaming form, etc.

What are we going to do then when we do have streaming of results? Make the destination parameter optional in Explain?

Aye, probably something like that.

@jedesah Ok, I fixed the issues you raised, thanks for the feedback!

Not a big deal, but would have been easier to review changes if the commit was not rewritten. I will merge and we can fix the typo at some point :smile:


1037 Use local version of ng

Description:
Change path to ng script

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1040   +/-   ##
=======================================
  Coverage   90.54%   90.54%
=======================================
  Files         114      114
  Lines        2677     2677
  Branches       31       31
=======================================
  Hits         2424     2424
  Misses        249      249
  Partials        4        4

Continue to review full report at Codecov.

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


Route pattern matching

Hi, first of all your library is great and now we are using it in second project, and we are more than happy.
But I have first problem, and I would like you to ask if I am doing something wrong or this type of route is not possible.
I have several deep links that look like application://something?somethingElse=value and i wanted to handle route like ":type?:parameter", and extract value by using query.parameters. But this block never gets called. It is ok when I do something?:parameters something2:parameters ... but it is quite too much code in my opinion.

Hey @jknthn - I think you can achieve this as follows.. I added a test to verify: https://github.com/usebutton/DeepLinkKit/pull/82/files
Anything before the first / is considered the host and DLK supports named groups for anything after the scheme. So.. the DLK matcher :host will match any host and the parameters will be extracted into the queryParmeters array.
self.router[@":host"] = ^(DPLDeepLink *deepLink) {
    NSString *host = deepLink.routeParameters[@"host"];
    // deepLink.queryParameters will contain all your parameters for free.
};

Closing since it looks like we have a solution for this.

@wessmith Sorry for not answering. Your solution as all right, and it worked :) I was trying to figure out something more safe and specific but it ended like that. Thanks.


Disable notifications?

Didn't see anything in the settings...

That's a valid addition I think, and something I overlooked before now. I'll add this option in very shortly as it should be a simple tweak.

Cheers Josh


use jobJarUrl instead of artifactName to avoid stripping path prefixes

Context
I wanted to open a PR to kick off a discussion about the jobJarURL format that the mantis-master expects. It looks like the mantis-master expects the jobJarURL in the JobConfig to have a single path component, e.g. https://my-job-jar.zip, and drops path information when there are multiple path elements, e.g. https://git-sha-prefix/my-job-jar.zip.
A reproduction of the behavior that I've observed is:

Write a jobConfig with jobJarFileLocation like https://git-sha-prefix/my-job-jar.zip
Master submits a job to agent with the jobJarUrl https://git-sha-prefix/my-job-jar.zip
On master restart, the master strips the path prefixes, and persists the jobJarUrl https://my-job-jar.zip to the KV persistence store.
If a job is resubmitted to an agent, it's submitted with the jobJarUrl https://my-job-jar.zip.

I've narrowed down this behavior to a few places:

When a job is read from the KV store, various configurations (like JobClusterConfig) only store the artifactName, and do not store the full jobJarUrl.
When a job is sent to the agent or persisted, the master uses generateURL(artifactName) to generate the jobJarUrl, losing the path prefix information.

I'm curious if there is a deeper mantis or Netflix reason for this behavior, and if changing this behavior will break any other assumptions within Mantis. Also, FWIW we can't use a chained PrefixedBlobStore because these prefixes are dynamic.
@Andyz26 would appreciate any thoughts on this change, especially as it changes the JobClusterConfig interface!
cc @kmg-stripe (I'm going to be out of office and Kevin may take over this PR)
Checklist

[x] ./gradlew build compiles code correctly
[ ] Added new tests where applicable
[x] ./gradlew test passes all tests
[ ] Extended README or added javadocs where applicable

Tested E2E on local mantis cluster (master + DynamoDB + agent)

@sundargates do you have any context on why the jar path is treated this way? I assume it has something todo with how we override the path internally?

@sundargates do you have any context on why the jar path is treated this way? I assume it has something todo with how we override the path internally?

It was done this way because we wanted the paths to be compatible with the old mesos based mantisagent download scripts. I don't think there's any requirement that it has to be kept this way in the current world.

Closing in favor of https://github.com/Netflix/mantis/pull/708.


Error: Cannot navigate to invalid URL

Just checking here -- is there a regression on relative paths?
I am getting this... Error: Cannot navigate to invalid URL When I use a relative path.
This is related to https://github.com/garris/BackstopJS/issues/485

Ah... Sorry, maybe this might be a regression too.
Chromy 0.4.4 and 0.4.5 might have regressions so try to use 0.4.3.

fixed this problem in 0.4.6.

Yup -- verified!


Reduce execution time of TestBuildHistory

Closes #12671
Signed-off-by: Hu Keping<EMAIL_ADDRESS>

This is a bad idea. There was a good reason behind having that many RUN commands.

Perhaps we could modify the test with a comment to explain why it need to have that many RUNs?

@duglin It has it already

// This is a heisen-test.  Because the created timestamp of images and the behavior of
// sort is not predictable it doesn't always fail.

ah, I didn't expand the diff enough. thanks

so I think we should keep this it as  before ?

@HuKeping The number of layers it had before was required to trigger this test previously. I'd very much prefer keeping it this way, rather than risk making it less useful and less likely to trigger the bug in case of a regression.
I think reducing the number of layers for this particular test is a bad idea and I also remember why this test was introduced, so it should be left alone.
Instead of attempting to speed up this test, perhaps we should look into making other changes to speed things up overall.
NOT LGTM

Closing since this test should be left as is for now.

@unclejack You talking about another test. But okay if you're so against it.


feat: relic count

Pull Request

Description

Added display for total relic count and filtered relic count

Related Issue

Closes #424

Checklist

[x] I have added commit messages that are descriptive and meaningful.
[x] I have tested the changes locally.
[x] I have reviewed the code changes.

Screenshots

I think this is probably the wrong solution to the problem, we don't need a custom component when the grid library already provides the functionality - https://www.ag-grid.com/javascript-data-grid/row-pagination/
Changing this to use grid options instead will let us minimize complexity
            pagination={true}
            paginationPageSizeSelector={false}
            paginationPageSize={2000}

Updated to:

the custom component was so that you can see both how many relics pass the filter and how many you have in total at the same time since pagination only shows the number that currently pass the filter


Staged tree doc

The StagedTree user guide is I think mostly complete.
I moved the visual modification section to a separate notebook because it applies not only to staged trees but also all other objects.
Apologies for the forced push. I didn't notice the previous changes made on the branch and then messed merging ...


[WIP] KAFKA-2063: Add Fetch Response Size Limit in Bytes (KIP-74)

@ijuma Was this repo the intended target for this PR?

@ewencp yeah, just wanted to share it with Jason first. Will post a cleaned up version in AK tomorrow.

These changes have been merged to the main PR in the Apache Kafka repo: https://github.com/apache/kafka/pull/1812


add s3 bucket support for storing blocks (one-blocks and hundred-blocks)

Allow blocks to be stored in an s3 bucket as an option.  eg minio.
If using a simple s3 server, then consider also this issue
https://github.com/dfuse-io/dfuse-eosio/issues/56

dstore our abstraction for file storage/retrieval have support for it: https://github.com/dfuse-io/dstore/blob/develop/s3store.go.
But it seems it's not possible to create the store from a string because the NewStore call for s3 scheme is commented out: https://github.com/dfuse-io/dstore/blob/develop/stores.go#L66
I know we did use it a little, maybe @abourget would know more why it's commented out.

It is possible we could mount s3 storage using s3fs-fuse.

We definitely want native S3 storage.  I assumed it was all there and good. I did that recently, probably just forgot to remove the comment.
Do you want to PR that in ?  From what I recall, it's all ready, except this line!

There seems to be an issue with uploading stale files, this is from our logs:
Jun 17 11:07:09 jungle-dm12b nodeos[51511]: 2020-06-17T11:07:09.794Z (mindreader) failed to upload stale files (mindreader/mindreader.go:238){"error": "moving file \"/var/lib/dfuse/mindreader/work/0020417/0020417661-20200617T000645.0-721b69a1-cf97897e.dat\" to storage: writing \"/var/lib/dfuse/mindreader/work/0020417/0020417661-20200617T000645.0-721b69a1-cf97897e.dat\" to storage \"0020417661-20200617T000645.0-721b69a1-cf97897e.dbin.zst\": uploading to S3 through manager: RequestError: send request failed\ncaused by: Put http://<IP_ADDRESS>:9002/jungle-one-blocks/0020417661-20200617T000645.0-721b69a1-cf97897e.dbin.zst: dial tcp <IP_ADDRESS>:9002: connect: cannot assign requested address"}
Note that this only happens after nodeos is shutting down, while being live the mindreader s3 upload works fine. Maybe the connection is closed to early?

I searched for cannot assign requested address on the web and found: https://github.com/golang/go/issues/16012.
It describe a similar issue an explain it's because there is too much resources being used. They give some ideas to augment the resources pool, not sure if it's applicate easily to the s3 sdk client.
When mindreader shut down, maybe it's trying to upload too much blocks in parallel. Will need to think investigate more I guess.

Can we close this issue ? There is this issue remaining (https://github.com/dfuse-io/dfuse-eosio/issues/91) but this one here should be closed, no ? the issues with burst uploading of files from mindreader should also have been addressed by all the rework there...

Yes, should be closed.


[r2.6-rocm-enhanced] Switch to ROCm 5.0.0

going to rerun the Ubuntu-GPU-single test, in hope that the failure was node specific
link to failing test

http://ml-ci.amd.com:21096/job/tensorflow/job/github-prs-rocmfork-r26-rocm-enhanced/job/rocm-latest-ubuntu-gpu-single/25/

jenkins : retest Ubuntu-GPU-single please

FWIW, the Ubuntu-GPU-single CI run had a single failure
//tensorflow/python/kernel_tests:conv2d_transpose_test_gpu               FAILED in 3 out of 3 in 13.9s

The same test passes on the r2.8-rocm-enhanced branch with ROCm 5.0.0 (grep the CI log for the above test in this PR - https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/pull/1571 )
In case, the rerun fails on the same test, I will push out a commit to add the no_rocm tag on that test

same test failed again :(
so definitely a regression with ROCm 5.0, but one that is limited to the r2.6-rocm-enhanced branch


Lajilista

Support for showing all predefined species in given day way of chosen observatory. Added also filters to maintain the usability of the page.

Hurried this feature to staging for Monday morning meeting.


The small (*dns.OPT).SetDo documentation tweak

As I identified in #1460, there is a mistake in the documentation appeared, that I would like to address through the following pull request.  I've tried to change as few symbols, as possible, to keep the documentation comprehensive and concise.
Best regards, @EugeneOne1.

lgtm. It's more to the point.
thanks


Correction for raw affiliation ABSys, Univ Montpellier, CIHEAM-IAMM, CIRAD, INRAE, Institut Agro, Montpellier, France

Correction needed for raw affiliation ABSys, Univ Montpellier, CIHEAM-IAMM, CIRAD, INRAE, Institut Agro, Montpellier, France
raw_affiliation_name: ABSys, Univ Montpellier, CIHEAM-IAMM, CIRAD, INRAE, Institut Agro, Montpellier, France
new_rors: 05kpkpg04;04abkkz03;051escj72;03rnk6m14;0005r2j17;003vg9w96;00n2c0309
previous_rors: 05kpkpg04;04abkkz03;051escj72;03rnk6m14;0005r2j17;003vg9w96
works_examples: W4210643400;W4396912348
contact: 5c28f76ec55ea57ccac932aa31d09ac7:baa7b98e7b251adb41a6032fc5679af6fbc3 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Accessing Arrays - placement of index

Documentation feedback

Page title: Selecting data
Page URL: https://crate.io/docs/crate/reference/en/latest/general/dql/selects.html
Source: https://github.com/crate/crate/blob/master/docs/general/dql/selects.rst

From the documentation it is unclear how to correctly access arrays within objects.
The example has the index right after the identifier, but it is not clear if information is an object or array:
select name, information[1]['population'] as population from locations
... where information['population'] is not null
... order by name;

Putting the index first look unintuitive
CREATE TABLE test (a OBJECT);
insert into a values({ id = 1, name = 'foo', tags = ['apple', 'banana', 'pear'], size = 3.1415, valid = true });

SELECT a FROM test limit 100;
-- SELECT OK, 1 row in set (0.005 sec)

SELECT a[1]['tags'] FROM test limit 100;
-- SELECT a[1]['tags'] FROM test limit 100; --> apple

SELECT a['tags'][1] FROM test LIMIT 100;
-- SQLActionException[UnsupportedFeatureException: Nested array access is not supported]

thanks for the feedback, @proddata!

@mechanomi I think this is something where we can also look into changing the behavior or support both versions.
This is indeed rather unintuitive:
cr> SELECT a['tags'] FROM test limit 100;
+-----------------------------+
| a['tags']                   |
+-----------------------------+
| ["apple", "banana", "pear"] |
+-----------------------------+
SELECT 1 row in set (0.007 sec)
cr> SELECT ['apple', 'banana', 'pear'][1] FROM test limit 100;
+---------+
| 'apple' |
+---------+
| apple   |
+---------+
SELECT 1 row in set (0.005 sec)

relabeled this as a docs correction. will spin off an issue re supporting both versions (and will restore your original labels to that issue)

@mechanomi did you create the feature issue?

@proddata my bad! here you go:
https://github.com/crate/crate/issues/10322

I started work on this today. I thought it was going to be a quick fix (perhaps a small admonition block or something) but the work has expanded
the first issue I found was that the actual data being queried is not shown. there are examples showing inserts, but the actual data being selected and queried is from the test harness. to address this, I started to rework the examples so that the reader is first shown the data and is then shown how it can be selected and queried
however, this wasn't sufficient. even with updated examples and better prose, the content is poorly organized and confusing as a result. this issue is exacerbated by the fact that

Arrays and objects can be nested
There is a special syntax for querying a single property of all objects within an array that looks identical to querying a single object property

that last point was new information to me. the docs do not explain this very well and it took some practical experimentation to figure out
to address this, I have overhauled the bits of selects.html that cover arrays, objects, and their nested permutations
originally, this was going to go into https://github.com/crate/crate/pull/10861, but the scope of these changes has prompted me to spin it out a separate PR (currently a draft). this is in progress
--
a small footnote
the test data is themed around locations from The Hitchhikers Guide to the Galaxy and associates a number of fictional "locations" and "races" (which is fine, in my view). however, the main text confuses things by adding European cities to this data and in one instance identifies "Vorarlberger" as a "race"
this terminology is inaccurate and poorly chosen. I have replaced all instances of "race" with "inhabitants", which works in both contexts
I had to introduce two extra locations while expanding the examples and went with European city names for consistency with the surrounding text. however, having written this, I should probably replace all instances of European city names with additional locations from The Hitchhikers Guide to the Galaxy. the mixing of themes adds unnecessary confusion to an already challenging topic

I am closing this issue as done now that https://github.com/crate/crate/pull/10866 has been merged
you would be able to see the changes on the live site, but unfortunately, the master URL version is broken atm (fix pending at https://github.com/crate/salt/pull/2492). fortunately, you can view staging docs on RTD:
this whole section has been reworked:
https://crate.readthedocs.io/en/latest/general/dql/selects.html#nonscalar-data-types
would be interested in a general review on this. does it read better? flow better? make more sense, and so on?
but, specifically, to close this issue:

@proddata please check out the https://crate.readthedocs.io/en/latest/general/dql/selects.html#nested-structures section and let me know if it addresses your original criticism

@mfussenegger check out https://crate.readthedocs.io/en/latest/general/dql/selects.html#limitations and see if that captures what you were suggesting

in case you're bored, there is a lot of details on https://github.com/crate/crate/pull/10866. or, perhaps more usefully, a reasonably detailed summary in the commit message: https://github.com/crate/crate/pull/10866/commits/9b7c9d16f5b5762b7b7777e61687ed049345322e

I am closing this issue as done now that https://github.com/crate/crate/pull/10866 has been merged
you would be able to see the changes on the live site, but unfortunately, the master URL version is broken atm (fix pending at https://github.com/crate/salt/pull/2492). fortunately, you can view staging docs on RTD:
this whole section has been reworked:
https://crate.readthedocs.io/en/latest/general/dql/selects.html#nonscalar-data-types
would be interested in a general review on this. does it read better? flow better? make more sense, and so on?
but, specifically, to close this issue:

@proddata please check out the https://crate.readthedocs.io/en/latest/general/dql/selects.html#nested-structures section and let me know if it addresses your original criticism

@mfussenegger check out https://crate.readthedocs.io/en/latest/general/dql/selects.html#limitations and see if that captures what you were suggesting

in case you're bored, there is a lot of details on https://github.com/crate/crate/pull/10866. or, perhaps more usefully, a reasonably detailed summary in the commit message: https://github.com/crate/crate/pull/10866/commits/9b7c9d16f5b5762b7b7777e61687ed049345322e

@mechanomi
Looks good to me.
Though I think there is a small typing error Lucine instead of Lucene in the Limitations section ... can't find the pr

@mechanomi
Looks good to me.
Though I think there is a small typing error Lucine instead of Lucene in the Limitations section ... can't find the pr

thanks for the review, @proddata! will close this issue
https://github.com/crate/crate/pull/10951 addresses the spelling mistake. good catch ty!

thanks for the review, @proddata! will close this issue
https://github.com/crate/crate/pull/10951 addresses the spelling mistake. good catch ty!

check out https://crate.readthedocs.io/en/latest/general/dql/selects.html#limitations and see if that captures what you were suggesting

I think the reasoning is not fully correct. The array(array(..)) limitation is not related to the flattening of the index structure. I don't remember the real reason for the limitation, I think by now it might actually be mostly artificial.
The oddity with the placement of the array index in inhabitants[1]['interests'] is also not related to the flattened index structure, but had to do with our type system and how we represent functions internally.

check out https://crate.readthedocs.io/en/latest/general/dql/selects.html#limitations and see if that captures what you were suggesting

I think the reasoning is not fully correct. The array(array(..)) limitation is not related to the flattening of the index structure. I don't remember the real reason for the limitation, I think by now it might actually be mostly artificial.
The oddity with the placement of the array index in inhabitants[1]['interests'] is also not related to the flattened index structure, but had to do with our type system and how we represent functions internally.

@mfussenegger ah. hmm. thx! I'll reopen and take another look

@mfussenegger ah. hmm. thx! I'll reopen and take another look

this is complete now

this is complete now


build_runner does not handle trailing commas in build.yaml

Describe the bug
Paths with trailing commas are not handled correctly when using build_runner.
targets:
  $default:
    builders:
      slang_build_runner:
        options:
          base_locale: en
          input_directory: lib/abc/ # <-- does not work

Fixed in 3.23.0


Get rid of separate CocoaLumberjackSwift.framework for most platforms

For iOS, watchOS, and tvOS, we can support Swift directly with CocoaLumberjack.framework instead of having a separate CocoaLumberjackSwift.framework. OS X still requires CocoaLumberjackSwift.framework because it has a deployment target of 10.7 but Swift requires 10.9 or later.
Also perform some minor cleanup on the Swift support.

I think those changes might break compatibility with the existing installs, so after our recent releases have also done this, not sure it this is wanted.
@rivera-ernesto what do you think?

I think that anything that simplifies the project is good. Let's prepare a 2.3.0 release allowed to break some small things like this and a default ddLogLevel (#648) in order to improve the library.

As for this pull request in particular, I think it should be broken into two different pull requests as modifying the Swift "macros" is not what this pull request describes.
Let's just keep the merge frameworks commits here.

If there are backward-incompatible changes (e.g. to the .xcodeproj), would a 3.0.0 version be preferred to maintain semantic versioning?
SemVer was being advocated in the past (#542).

The macro changes actually are backwards-compatible. This is why I left SwiftLogMacro intact and just marked it as deprecated. The project changes are the backwards-incompatible part.
I almost left the CocoaLumberjackSwift modules intact as stubs, to preserve backwards compatibility, but I took them out entirely because I figured that was just too confusing. CocoaLumberjack already doesn't do a good job of explaining Swift support, so I figured it was better to kill the CocoaLumberjackSwift framework entirely so people wouldn't unnecessarily import it. It also speeds up the build a bit (because building those stub frameworks does take time).

@DD-P only v.v.X versions really need to be minor. We're not rewriting most classes as we did for 2.0.0 and we don't want to be in version 18 in a year, so I think it's ok to make a 2.3.0 release that requires some small migration and only for users that installed manually.
@kballard The macro changes look good, it is just that I think they should be made in a separate pull request to make it cleaner/easier to review/discuss/document.

Ok I'll split it out.

PR updated, #649 filed for the Swift cleanup.

Thanks!


Cannot edit any macro after closing any macro windows by pressing the x button

When I open any macro window and then close it by pressing the x button any other macro window I open, the code cannot be edited. If I close it by pressing "Save Macro"  or the Escape Key this doesn't happen.

I've run into this issue too. Looks like the editor is only cleaned up when the form on the macro editor dialog is submitted.
https://github.com/laquasicinque/monaco-macro-editor/blob/master/src/editor.ts#L147-L152
I believe this can be fixed by updating the hook for renderMacroConfig to take the appId of the new dialog and map it to the editor instance created. Then add a hook for closeMacroConfig and clean up the associated editor. Then the form submit listener would be removed since it would be redundant.
I attempted to fork and make a pull request but wow, I clearly do not know how Typescript works.


Mutual TLS in App Service

When I try to do mutual TLS in Azure App Service , and my client certificate is not a certified CA - can I in any way add my client certificate Root CA to the app service Trust Store ? ( not with ASE option )
Thanks!
[Enter feedback here]

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

ID: eb440603-950a-c224-f6c9-222ca502d5a5
Version Independent ID: 0b5c4944-0327-91fc-2b0b-c19a1b873b64
Content: Configure TLS mutual authentication - Azure App Service
Content Source: articles/app-service/app-service-web-configure-tls-mutual-auth.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @chaisen2006 , Thank you for the question. We are currently investigating and will update you when we have accurate information to provide.

Answered here: https://github.com/MicrosoftDocs/azure-docs/issues/88132


Intacct

[Enter feedback here]

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

ID: 3ef35c6a-1a69-477d-ef75-36f7b5cab254
Version Independent ID: 134037dd-9300-4f58-9efd-18b575b0c898
Content: Tutorial: Azure Active Directory integration with Sage Intacct
Content Source: articles/active-directory/saas-apps/intacct-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

Delete me.

Hope this is created for testing purpose and then closed.


Enabling the issueReporter.experimental.auxWindow setting prevents Issue Reporter window from being focused

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.93.0
OS Version: MacOS Sonoma 14.7 (23H124)

Steps to Reproduce:

With issueReporter.experimental.auxWindow enabled, open the Issue Reporter through the "Help: Report Issue..." command
Move the Issue Reporter window behind another window and call "Help: Report Issue..." again -- the behavior I observe is the Issue Reporter window stays hidden behind the other window
Disable issueReporter.experimental.auxWindow and run "Help: Report Issue..." again -- the window should now pop back into the foreground and into focus

Seen as part of https://github.com/microsoft/vscode/issues/229107
Able to reproduce in the current 1.94 VS Code Insiders build as well.

@shouples thanks, I'll give this a look


Issue with climate entity discovery after updating to 1.2.1

Great work with this so far! Most of my devices are working quite well but I seem to be having a minor issue with HASS discovery of climate devices after updating to 1.2.1.
Discovery worked in version 1.1.1, but after updating, the existing climate entities are marked unavailable. I have tried re-interviewing the node (works fine), rediscovering it (again seems fine), removed the entity in hass (never came back), and fully removing and reinstalling the HASS integration (lost naming, but otherwise seems to work fine). When I watch the HASS logs, the sensors and binary_sensors are discovered, but the climate entities seem to be completely ignored. I have triple checked that discovery is enabled for these nodes, so I would expect that they would show back up.
Here is the discovery payload for an example climate device:
{   "type": "climate",   "object_id": "climate",   "discovery_payload": {     "min_temp": 5,     "max_temp": 40,     "temp_step": 0.5,     "modes": [       "off",       "heat",       "cool",       "auto"     ],     "mode_state_template": "{{ {0: \"off\", 1: \"heat\", 2: \"cool\", 3: \"auto\"}[value_json.value] | default('off') }}",     "current_temperature_topic": "zwave/Master_Bedroom_Thermostat/49/0/Air_temperature",     "current_temperature_template": "{{ value_json.value }}",     "temperature_state_topic": "zwave/Master_Bedroom_Thermostat/67/0/setpoint/1",     "temperature_state_template": "{{ value_json.value }}",     "temperature_command_topic": "zwave/Master_Bedroom_Thermostat/67/0/setpoint/1/set",     "mode_state_topic": "zwave/Master_Bedroom_Thermostat/64/0/mode",     "mode_command_topic": "zwave/Master_Bedroom_Thermostat/64/0/mode/set",     "action_topic": "zwave/Master_Bedroom_Thermostat/66/0/state",     "action_template": "{{ {0: \"idle\", 1: \"heating\", 2: \"cooling\", 3: \"fan\", 4: \"idle\", 5: \"idle\", 6: \"fan\", 7: \"heating\", 8: \"heating\", 9: \"cooling\", 10: \"heating\", 11: \"heating\"}[value_json.value] | default('idle') }}",     "temperature_unit": "F",     "precision": 0.1,     "device": {       "identifiers": [         "zwavejs2mqtt_0xc4468d53_node7"       ],       "manufacturer": "Residential Control Systems, Inc. (RCS)",       "model": "Thermostat (TBZ48)",       "name": "Master_Bedroom_Thermostat",       "sw_version": "1.2"     },     "name": "Master_Bedroom_Thermostat_climate",     "unique_id": "zwavejs2mqtt_0xc4468d53_Node7_climate"   },   "values": [     "49-0-Air temperature",     "64-0-mode",     "67-0-setpoint-1",     "67-0-setpoint-2",     "66-0-state"   ],   "mode_map": {     "off": 0,     "heat": 1,     "cool": 2,     "auto": 3   },   "setpoint_topic": {     "1": "67-0-setpoint-1",     "2": "67-0-setpoint-2"   },   "default_setpoint": "67-0-setpoint-1",   "action_map": {     "0": "idle",     "1": "heating",     "2": "cooling",     "3": "fan",     "4": "idle",     "5": "idle",     "6": "fan",     "7": "heating",     "8": "heating",     "9": "cooling",     "10": "heating",     "11": "heating"   },   "discoveryTopic": "climate/Master_Bedroom_Thermostat/climate/config",   "persistent": false,   "ignoreDiscovery": false,   "id": "climate_climate" }
The device does seem to work correctly in the zwave2js GUI, so this may be an upstream issue with HASS or zwavejs-server. If there are any other logs that may help, please let me know.
Thanks!

Adding node dump.
zwave_js_dump.jsonl.zip

Updated to 1.2.1 as well and the climate entity is not being discovered by HA. Exclude and include did not help. Thermostat is Honeywell TH6320ZW.

zwave-js 6.3.0+ is not compatible with the current release of HA, in regards to thermostats and some RGB devices. If you need the functionality, aside from modifying HA code yourself, you must run the dev version of HA, or rollback to the 6.2.0 version of zwave-js.

FYI, if you are using the Z-Wave JS HA integration, then the MQTT discovery is not used at all.

@kpine Ah, that would explain it. Thank you!
I replaced my local instance of discovery.py for the zwave_js integration with the one from this PR: 46355 and they are now being discovered as expected.
Thank you again for pointing me in the correct direction. I will mark this solved.

@kpine Ah, that would explain it. Thank you!
I replaced my local instance of discovery.py for the zwave_js integration with the one from this PR: 46355 and they are now being discovered as expected.
Thank you again for pointing me in the correct direction. I will mark this solved.

How exactly did you do this? I'm running HASS.IO and I can't find the directory with the zwave_js integration. In fact I can find any of the integrations. Is the directory accessable from the Home Assistant Command Line?

@1iveowl I believe HASS.IO is container based, which means you wouldn't have direct access to the native integration code directories. I suspect that it would be possible to copy the full integration into your local integrations folder however, and update the discovery there.


API design discussion

kk=DataFrame({'a':[1,0,3,5],'b':[2,4,6,8]})
kk['c']=kk.b/kk.a

kk
a  b  c
0  1  2  2
1  0  4  0
2  3  6  2
3  5  8  1

Two issues:
(1) I don't think  kk[1,'c']=0 is a suitable answer
(2) I don't think  kk[3,'c']=1 is a suitable answer, it should be 1.6
while kk['c']=1.0*kk.b/kk.a  give an OK answer

kk
a  b    c
0  1  2  2.0
1  0  4  NaN
2  3  6  2.0
3  5  8  1.6

So pls treat 'int/int' to 'float/float', for current 'int/int' treatment will cause difficult checking error

pandas defaults true div since 0.14 IIRC. The other issue mentioned is detailed in several issues.


can I leave quasar & burst installed while testing elementum?

.

Plugin safe to use near Quasar.


Disable the option to install in a specific namespace

The GitOps operator doesn't support resource installation in a specific namespace. Hence OperatorHub should only display the option to install in all-namespaces.
Signed-off-by: Chetan Banavikalmutt<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested the update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/lgtm


[aes] Clarify documentation

This is related to lowRISC/OpenTitan#2382.

Thanks @silvestrst for your approval. I am merging this now.


Step physics seems to not work properly

❓ Questions and Help
Hi, I'm following the tutorial at https://aihabitat.org/docs/habitat-sim/rigid-object-tutorial.html, but the ball don't fall to the ground even if "step_physics" is properly called. It seems that sim.step_pyhsics is not actually simulating physics, and therefore the result is a ball still in mid-air in all the observations. Am I forgetting something?
Thank you :)
My environment:
python 3.8
habitat_sim 0.1.6 installed with conda

Sounds like the version of Habitat-sim you installed does not have bullet physics enabled. You should see a message in the terminal output that indicates this.

Hi @aclegg3, thanks for answering! Actually, the only physics-related log on the terminal is
PhysicsAttributesManager.cpp:27] File (./data/default.physics_config.json) not found, so new default physics manager attributes created and registered.

Can you provide the full log here? Which conda install did you use?

Yes sure :+1:
I installed it from nightly channel: conda install habitat-sim withbullet  -c conda-forge -c aihabitat-nightly. I tried with conda install habitat-sim  -c conda-forge -c aihabitat-nightly as well.
The full log is here:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1214 17:18:13.351907 304462 ManagedContainerBase.cpp:19] ManagedContainerBase::convertFilenameToJSON : Filename : default changed to proposed JSON configuration filename : default.scene_dataset_config.json
I1214 17:18:13.351999 304462 AssetAttributesManager.cpp:117] Asset attributes (capsule3DSolid : capsule3DSolid_hemiRings_4_cylRings_1_segments_12_halfLen_0.75_useTexCoords_false_useTangents_false) created and registered.
I1214 17:18:13.352063 304462 AssetAttributesManager.cpp:117] Asset attributes (capsule3DWireframe : capsule3DWireframe_hemiRings_8_cylRings_1_segments_16_halfLen_1) created and registered.
I1214 17:18:13.352141 304462 AssetAttributesManager.cpp:117] Asset attributes (coneSolid : coneSolid_segments_12_halfLen_1.25_rings_1_useTexCoords_false_useTangents_false_capEnd_true) created and registered.
I1214 17:18:13.352214 304462 AssetAttributesManager.cpp:117] Asset attributes (coneWireframe : coneWireframe_segments_32_halfLen_1.25) created and registered.
I1214 17:18:13.352238 304462 AssetAttributesManager.cpp:117] Asset attributes (cubeSolid : cubeSolid) created and registered.
I1214 17:18:13.352267 304462 AssetAttributesManager.cpp:117] Asset attributes (cubeWireframe : cubeWireframe) created and registered.
I1214 17:18:13.352295 304462 AssetAttributesManager.cpp:117] Asset attributes (cylinderSolid : cylinderSolid_rings_1_segments_12_halfLen_1_useTexCoords_false_useTangents_false_capEnds_true) created and registered.
I1214 17:18:13.352350 304462 AssetAttributesManager.cpp:117] Asset attributes (cylinderWireframe : cylinderWireframe_rings_1_segments_32_halfLen_1) created and registered.
I1214 17:18:13.352363 304462 AssetAttributesManager.cpp:117] Asset attributes (icosphereSolid : icosphereSolid_subdivs_1) created and registered.
I1214 17:18:13.352375 304462 AssetAttributesManager.cpp:117] Asset attributes (icosphereWireframe : icosphereWireframe_subdivs_1) created and registered.
I1214 17:18:13.352393 304462 AssetAttributesManager.cpp:117] Asset attributes (uvSphereSolid : uvSphereSolid_rings_8_segments_16_useTexCoords_false_useTangents_false) created and registered.
I1214 17:18:13.352411 304462 AssetAttributesManager.cpp:117] Asset attributes (uvSphereWireframe : uvSphereWireframe_rings_16_segments_32) created and registered.
I1214 17:18:13.352416 304462 AssetAttributesManager.cpp:105] AssetAttributesManager::buildCtorFuncPtrMaps : Built default primitive asset templates : 12
I1214 17:18:13.352939 304462 SceneDatasetAttributesManager.cpp:23] File (default) not found, so new default dataset attributes created and registered.
I1214 17:18:13.352946 304462 MetadataMediator.cpp:46] MetadataMediator::createDataset : Dataset default successfully created.
I1214 17:18:13.356528 304462 PhysicsAttributesManager.cpp:27] JSON Configuration File (./data/default.physics_config.json) based physics manager attributes created and registered.
I1214 17:18:13.356539 304462 ManagedContainerBase.cpp:19] ManagedContainerBase::convertFilenameToJSON : Filename : /home/gianlucascarpellini/dev/habitat-sim/data/scene_datasets/habitat-test-scenes/apartment_1.glb changed to proposed JSON configuration filename : /home/gianlucascarpellini/dev/habitat-sim/data/scene_datasets/habitat-test-scenes/apartment_1.stage_config.json
I1214 17:18:13.356631 304462 AbstractObjectAttributesManagerBase.h:180] File (/home/gianlucascarpellini/dev/habitat-sim/data/scene_datasets/habitat-test-scenes/apartment_1.glb) exists but is not a recognized config filename extension, so new default Stage attributes created and registered.
I1214 17:18:13.356662 304462 Simulator.cpp:153] Loading navmesh from /home/gianlucascarpellini/dev/habitat-sim/data/scene_datasets/habitat-test-scenes/apartment_1.navmesh
I1214 17:18:13.356755 304462 Simulator.cpp:155] Loaded.
I1214 17:18:13.356765 304462 SceneGraph.h:93] Created DrawableGroup:
Renderer: GeForce GTX 1650/PCIe/SSE2 by NVIDIA Corporation
OpenGL version: 4.6.0 NVIDIA 450.80.02
Using optional features:
    GL_ARB_ES2_compatibility
    GL_ARB_direct_state_access
    GL_ARB_get_texture_sub_image
    GL_ARB_invalidate_subdata
    GL_ARB_multi_bind
    GL_ARB_robustness
    GL_ARB_separate_shader_objects
    GL_ARB_texture_filter_anisotropic
    GL_ARB_texture_storage
    GL_ARB_texture_storage_multisample
    GL_ARB_vertex_array_object
    GL_KHR_debug
Using driver workarounds:
    no-forward-compatible-core-context
    no-layout-qualifiers-on-old-glsl
    nv-zero-context-profile-mask
    nv-implementation-color-read-format-dsa-broken
    nv-cubemap-inconsistent-compressed-image-size
    nv-cubemap-broken-full-compressed-image-query
    nv-compressed-block-size-in-bits
I1214 17:18:13.485472 304462 ResourceManager.cpp:247] ResourceManager::loadStage : Not loading semantic mesh
I1214 17:18:13.485492 304462 ResourceManager.cpp:1126] Importing Basis files as BC7
W1214 17:18:14.356468 304462 Simulator.cpp:243] :
---
 The active scene does not contain semantic annotations.
---
I1214 17:18:14.356747 304462 simulator.py:213] Loaded navmesh /home/gianlucascarpellini/dev/habitat-sim/data/scene_datasets/habitat-test-scenes/apartment_1.navmesh
I1214 17:18:14.360031 304462 ManagedContainerBase.cpp:19] ManagedContainerBase::convertFilenameToJSON : Filename : /home/gianlucascarpellini/dev/habitat-sim/data/test_assets/objects/sphere changed to proposed JSON configuration filename : /home/gianlucascarpellini/dev/habitat-sim/data/test_assets/objects/sphere.object_config.json
I1214 17:18:14.360046 304462 AttributesManagerBase.h:168] AttributesManager::loadAllFileBasedTemplates : Load Object template: /home/gianlucascarpellini/dev/habitat-sim/data/test_assets/objects/sphere.object_config.json
I1214 17:18:14.360158 304462 AttributesManagerBase.h:179] AttributesManager::loadAllFileBasedTemplates : Loaded file-based Object templates: 1
I1214 17:18:14.360282 304462 ResourceManager.cpp:1126] Importing Basis files as BC7
Simulating 2.0 world seconds.
Encoding the video: /home/gianlucascarpellini/dev/habitat-sim/examples/tutorials/rigid_object_tutorial_output/object permanence.mp4
I1214 17:18:15.746119 304462 PhysicsManager.cpp:33] Deconstructing PhysicsManager
I1214 17:18:15.746165 304462 SemanticScene.h:41] Deconstructing SemanticScene
I1214 17:18:15.746168 304462 SceneManager.h:25] Deconstructing SceneManager
I1214 17:18:15.746171 304462 SceneGraph.h:26] Deconstructing SceneGraph
I1214 17:18:15.746603 304462 Sensor.h:87] Deconstructing Sensor
I1214 17:18:15.747010 304462 Sensor.h:87] Deconstructing Sensor
I1214 17:18:15.747270 304462 Sensor.h:87] Deconstructing Sensor
I1214 17:18:15.752295 304462 Renderer.cpp:34] Deconstructing Renderer
I1214 17:18:15.752308 304462 WindowlessContext.h:17] Deconstructing WindowlessContext
I1214 17:18:15.755002 304462 Simulator.cpp:47] Deconstructing `Simulator`

I see. The "withbullet" build for habitat-nightly does not appear to be up-dating correctly at this time. You should in this case build from source or use the previous version tag (e.g. use -c aihabitat instead).

Hi @aclegg3, Thanks! I solved by build with this (the following code will build two wheels, both with and without display)
# Checkout the latest stable release
cd dev
git clone --branch stable https://github.com/facebookresearch/habitat-sim.git
cd habitat-sim

# We require python>=3.6 and cmake>=3.10
conda create -n habitat python=3.8 cmake=3.14.0
conda activate habitat
pip install -r requirements.txt

python setup.py bdist_wheel --with-cuda --bullet
python setup.py bdist_wheel --with-cuda --bullet --headless # Headless, for cluster


[Doc] Update the tenant permission modifications for pulsar-admin

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
The pulsar-admin tenants update command allows you to make someone a tenant admin, but the doc https://pulsar.apache.org/docs/next/admin-api-permissions/ does not show this.
What is your suggestion?
Update the docs to add in the tenant permission modifications.
Any reference?
//cc @illegalnumbers @vikram-narayan
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Based on my understanding, it's the doc strategy that we don't duplicate all the commands and flags but only document some frequently used ones. The reference link is shown in the following tip for further exploring and you can find this one.

Does it work for you? @illegalnumbers


[Doc] syntax and format issues in README.md and how-to-contribute-to-apache-carbondata.md

Why is this PR needed?
To improve the quality of README.md and how-to-contribute-to-apache-carbondata.md.
What changes were proposed in this PR?
Syntax and format changes.
Does this PR introduce any user interface change?

No

Is any new testcase added?

No

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3625/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5370/

@Indhumathi27 Could you please review this PR? I believe this PR is very simple and thus will not take you much time to review. Thanks~

@Indhumathi27 Hello, I have updated this PR, please check it at your convenience.

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5447/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3703/

@Sunt-ing Since PR-4135, is also documentation related changes, can you please keep one PR(either 4136/4135)
for documentation change and list all the changes in the PR description

@Indhumathi27 Finished. And PR-4135 has been closed.

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3707/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5451/

A little weird... should be fine now. @Indhumathi27

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3716/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5460/

Fix done. @Indhumathi27

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5483/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3739/

Sorry for the long-time bother, but I do think it should be fine now.  @Indhumathi27

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5491/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3748/

LGTM. Thankyou for your contribution.


DFT – WORK_dmi_jtag uncontrolled resets in scan mode

This is a reminder on lc_jtag_req and rv_jtag_req signals in pinmux_strap_sampling block which connected to zero and affecting the resets of 386 FFs in WORK_dmi_jtag block in scan mode, hence these FFs are removed from scan.
SpyGlass message:
'chip_earlgrey_asic.top_earlgrey.u_pinmux_aon.u_pinmux_strap_sampling.lc_jtag_req[trst_n][1]' is not disabled for 193 flip-flop(s)
'chip_earlgrey_asic.top_earlgrey.u_pinmux_aon.u_pinmux_strap_sampling.rv_jtag_req[trst_n][1]' is not disabled for 193 flip-flop(s)
pinmux_strap_sampling.sv file, line 152 and 153.

@tjaychen
@msfschaffner

@arnonsha

Thanks Noam, I'll take a look.

hey all, before we fix this one, can Nuvoton confirm that trst_n does not affect the value of scan_mode in your design?
I'm pretty sure this is the case, but I wanted to make sure.

Yes
trst_n will not take the chip out of scan mode

@NoamGottlieb @arnonsha  if this is issue is now fixed, can you close it?
CC @tjaychen

can't see it in spyglass anymore


Winforms

How Do Used in Winforms?

Hey, what version of .net and winforms are you using? What DI library do you use?
Is haven't used winforms in years, but looking at this it should be possible to use with SlimMessageBus.
https://stackoverflow.com/questions/70475830/how-to-use-dependency-injection-in-winforms

hey @MohMehrnia, is this still an issue? Do you have further questions?


feat: semaphore added

Also using blue-tape to fix a specific test and
Connects to #60

Coverage increased (+0.01%) to 99.288% when pulling e62a56904190efc9739c2f1f691279b0abd3bb34 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.01%) to 99.288% when pulling 0faa766d82413a3e7ba8321fd0a2b5359c27cb50 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Does it make sense to always use execution isolation with semaphores? What if there's not really a need for it? Why have it be always on? Reading the Netflix documentation here https://github.com/Netflix/Hystrix/wiki/How-it-Works#semaphores it really only makes sense to use semaphore isolation in certain use cases where the latency is very low and throughput requirements very high. Given that, we have no real way of implementing thread pool isolation/rate limiting, so maybe it does make sense to have it always on. I'm not 100% sure, but I think we should discuss it.

Indeed, also I need to research more about it.

What happens to the semaphore when a circuit fires, but then times out? Is it released? We need to know that it is.

Good question, I'm going to investigate it.

What happens when the semaphore has reached its limit and semaphore.acquire() is called? Does it return a rejected promise? Immediately? Or something else?

We should test for this.

Agree.

The docs should be updated.

yup

What happens to the semaphore when a circuit fires, but then times out? Is it released? We need to know that it is.

seems like It is not releasing
 Circuit Breaker timeout with semaphore
    ✖ should be equal
    ------------------
      operator: equal
      expected: 10
      actual:   9

@lanceball: not release when CB timeout is a blocker right ?
if yes (I think it is) then maybe we need to test another semaphore lib, because to call the release() we need first the the aquire().then(release => release()) ...
Also, I'm going try to change sem.use() to sem.aquire() and try to call the release() in some place around that timeout code

Coverage increased (+0.01%) to 99.291% when pulling e181d43f3d2075c9a4f6f1d56978818bd3381b9c on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.01%) to 99.291% when pulling 66096e2cfbdef2f7c493e5665790d59f12c24074 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

I'm doing another test, but I missed to add more released() calls.
I'll push the changes soon.

What happens when the semaphore has reached its limit and semaphore.acquire() is called? Does it return a rejected promise? Immediately? Or something else?

We should test for this.

So after change the code , and adding the release() calls, I noticed that the counter is always zeroed after release () and subsequent fire calls are not affected.
I will send the test code because I may be testing the wrong way. So it's good to have a new view on this part

Coverage increased (+0.02%) to 99.298% when pulling 31b6d64649ff67b309252136ed2c1c5923ea0e29 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Now I'm using this lib to run the code in parallel :
https://www.npmjs.com/package/run-parallel
interesting because the code "runs" without error.

@lance when running in parallel we have this :
  Semaphore capacity limit in parallel

    ✔ semaphore count is: 0 and initial capacity is: 1
    ✔ failures: 0
    ✔ fallbacks: 0
    ✔ successes: 2
    ✔ rejects: 0
    ✔ fires: 4
    ✔ semaphore count is: 0 and initial capacity is: 1
    ✔ failures: 0
    ✔ fallbacks: 0
    ✔ successes: 3
    ✔ rejects: 0
    ✔ fires: 4
    ✔ semaphore count is: 1 and initial capacity is: 1
    ✔ failures: 0
    ✔ fallbacks: 0
    ✔ successes: 4
    ✔ rejects: 0
    ✔ fires: 4
    ✔ This is not in parallel -> semaphore count is: 1 and initial capacity is: 1
    ✔ failures: 0
    ✔ fallbacks: 0
    ✔ successes: 4
    ✔ rejects: 0
    ✔ fires: 4

Coverage increased (+0.02%) to 99.298% when pulling 3d990c39e64c0d7a7c8646f5ed19684d24b00978 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Given that, we have no real way of implementing thread pool isolation/rate limiting, so maybe it does make sense to have it always on. I'm not 100% sure, but I think we should discuss it.

true, with the current code we can see some real changes only when we run the code in parallel.
otherwise, looks like a serial code - like running without semaphore. Since it will release() every time btw.

Coverage increased (+0.02%) to 99.298% when pulling b3d7b6f85bc753f4a095522587063c53a26a63f9 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 4d0c0577d1073fc16a74e43f05fd81047455339d on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 4faf0caf7404c9dd1b5e577e47808571318231fb on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 80decd27e31d235b06abd05256359571101bc546 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 2c326cc4bfb78d66e0a17475b330a6b0b75188a8 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 9feb5391d3d3c7bd5dff76c785a4178bb97b30e5 on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.

Coverage increased (+0.1%) to 99.375% when pulling 5b00bdc40b2d68cb4b0c80848f573cb82cf839fd on semaphore into fd0fee28131e142d8c22ad410fd8be78c242aa3e on master.


Feature Request: NGINX's FastCGI cache

For those prefer to use NGINX's native FastCGI cache instead of php based plugins. Feel free to modify and add to globals directory.
fastcgi_cache_path /var/run/nginx-cache levels=1:2
                   keys_zone=WORDPRESS:100m inactive=60m;
fastcgi_cache_key "$scheme$request_method$host$request_uri";

server {
    server_name example.com www.example.com;
    root /var/www/example.com/htdocs;
    index index.php;

    access_log /var/log/nginx/example.com.access.log;
    error_log  /var/log/nginx/example.com.error.log;

    set $skip_cache 0;

    # POST requests and URLs with a query string should always go to PHP
    if ($request_method = POST) {
        set $skip_cache 1;
    }

    if ($query_string != "") {
        set $skip_cache 1;
    }

    # Don't cache URIs containing the following segments
    if ($request_uri ~* "/wp-admin/|/xmlrpc.php|wp-.*.php|/feed/|index.php
                         |sitemap(_index)?.xml") {
        set $skip_cache 1;
    }

    # Don't use the cache for logged-in users or recent commenters
    if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass
        |wordpress_no_cache|wordpress_logged_in") {
        set $skip_cache 1;
    }

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        try_files $uri /index.php;
        include fastcgi_params;
        fastcgi_pass unix:/var/run/php5-fpm.sock;
        fastcgi_cache_bypass $skip_cache;
        fastcgi_no_cache $skip_cache;
        fastcgi_cache WORDPRESS;
        fastcgi_cache_valid  60m;
    }

    location ~ /purge(/.*) {
        fastcgi_cache_purge WORDPRESS "$scheme$request_method$host$1";
    }

    location ~* ^.+\.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|css|rss|atom|js|jpg|jpeg
                      |gif|png|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi
                      |wav|bmp|rtf)$ {

        access_log off;
        log_not_found off;
        expires max;
    }

    location = /robots.txt {
        access_log off;
        log_not_found off;
    }

    location ~ /\. {
        deny  all;
        access_log off;
        log_not_found off;
    }
}

Hello,
Thanks for your efforts to put together the whole configuration.
Here are my thoughts about NGINX's (FastCGI and Proxy) cache in general (not particular to your configuration). Ref: https://www.nginx.com/blog/nginx-caching-guide/

The fastcgi_cache_purge functionality is available only as part of commercial subscription. Ref: https://nginx.org/r/fastcgi_cache_purge
Caching is easy but purging is hard. We definitely need a plugin to purge the cache whenever we publish a new post or update an existing post. There are already a few plugins available in this regard. Each come with its own set of Nginx configuration and recommended settings that are questionable. So, it is easy if someone wants to use Nginx's builtin (proxy or fastcgi) cache by just following the recommended Nginx configuration from the particular plugin.
I'd recommend Varnish if someone wants to utilize server-side caching techniques, because caching and purging are free in Varnish (even though Varnish has commercial interests too). One would still need a plugin to send purge requests. Also, in Varnish, if is not evil. Actually, if can be utilized more effectively in Varnish. For example, we can whitelist purge requests from particular set of IPs easily.

Coming back to the above configuration... as per the official recommendation from Nginx, the only 100% safe things which may be done inside if in a location context are...

return ...;
rewrite ... last;

I will keep this feature request open for now. If there are enough interest in it in the future, we'll work on it to fine-tune it to...

replace if statements that comes with set statement.
limit purge requests to white-listed IPs.
a plugin to send purge requests (this is likely easier, as we can fork an existing Varnish plugin or write a new plugin from scratch).

Thanks again,
Pothi.

Thank you for your constructive options. Not everyone will agree with you, it's good to offer choices, I've seen plenty of debates on which caches are the best... it's same as arguing over vim vs emacs for years which is pointless. There's a plugin for nginx cache, see here https://wordpress.org/plugins/nginx-helper/


fix(writer): buffer race condition

Closes #576

@christophcemper could you try this patch and see if it resolves this data race for you?


KAFKA-6620: Documentation about 'exactly_once' doesn't mention 'transaction.state.log.min.isr'

Add note on transaction.state.log.min.isr property, which can cause a problem when transaction.state.log.replication.factor is set to 1 for development without changing it to 1.

note: GlobalKTableEOSIntegrationTest.java
note: GlobalThreadShutDownOrderTest.java

Retest this please.

@mjsax Could you include this PR in 2.1.0?


Build a proof of concept with some message boxes

Build a proof of concept.
Just add some message boxes to show, that the addin is loaded and unloaded.

Released with version <IP_ADDRESS>


⚠ Bofrost.es has degraded performance

In 2ec3414, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1540 ms

Resolved: Bofrost.es performance has improved in 0efe3ff after 9 minutes.


Screenshot diffing has before/after backwards

I noticed this on this PR #170. The PR introduces changes to remove "Mailing list" from the navbar, but you see that change applied in Before, not After, as I expected:
Before:

After:

Oops I got it backwards, it looks fine actually


[incubator/elasticsearch] Add loadBalancerIP/loadBalancerSourceRanges

It can be very useful to be able to set these 2 variables if necessary. I'm doing it every times with new charts downloaded for my private cloud

@mattfarina @icereval Can you please check the patch? :)

@simonswine @icereval @rendhalver Can you please review this?

Please put the chart name IE: [incubator/elasticsearch] in the PR title so it's easier to know what the PR is for.

@Lord-Y Looks good.
What does setting these variables help us with?

/ok-to-test
(I looked up the docs)
Oh I see. Good addition. Thanks!

@rendhalver The resources of my enterprise are on both Gcloud and 2 datacanceters. When I need to access to my Elasticsearch cluster from the datacenters I specified a loadBalancerIP so the service is available from an IP address like 10.X.X.X.
For the loadBalancerSourceRanges, it's when the service is available from a public IP address and you need to firewall this access

Weird. The last test is complaining about the version but you definitely incremented it.
@mattfarina Any ideas?

/retest

@rendhalver @mattfarina @davidkarlsen I understood the issue. When I forked the repo, it was with version 1.4.0. I then bumped up the charts version but there was already a 1.4.1 version on master branch. So now I bumped it to version 1.4.2

Ahh that would do it.
You will need to merge upstream/master into your branch.

Yeah @rendhalver  now I need some /approve from you guys @mattfarina @icereval to complete the process.

/lgtm

/lgtm
after incrementing the version


support for rsrc_windows_arm64.syso

does the go-winres make support arm64 Architect?
processorArchitecture | Specifies the processor. Valid values include x86, amd64, arm and arm64. Optional.

the winres.json should have something like
 "processor-architecture": ["x86","amd64","arm","arm64"],

Hi,
This should work :
go-winres make --arch arm64

Feel free to file another issue if it doesn't.
Thanks

Thanks for adding
On Fri, Dec 23, 2022 at 3:35 AM tc-hib @.***> wrote:

Hi,
This should work :
go-winres make --arch arm64
Feel free to file another issue if it doesn't.
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/tc-hib/go-winres/issues/10#issuecomment-1363736691,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIO4JGMJQQLROFW4LQH7Z3WOVP6RANCNFSM6AAAAAASQGC6JA
.
You are receiving this because you authored the thread.Message ID:
@.***>