Crypto plugin abstractions, encrypted repositories and metadata mgmt

Description
This change is to add crypto plugin abstractions, add required fieds in put repository request and validations for the same and cluster state changes to manage crypto metadata against a repository.
Issues Resolved
This is one of the tasks of meta issue #7229
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #7284 (b681388) into main (72ed13b) will increase coverage by 0.06%.
The diff coverage is 43.50%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #7284      +/-   ##
============================================
+ Coverage     70.55%   70.61%   +0.06%
- Complexity    59441    59481      +40
============================================
  Files          4862     4867       +5
  Lines        285544   285858     +314
  Branches      41153    41215      +62
============================================
+ Hits         201453   201847     +394
+ Misses        67544    67352     -192
- Partials      16547    16659     +112

Impacted Files
Coverage Δ

...ion/admin/cluster/crypto/CryptoRequestBuilder.java
0.00% <0.00%> (ø)

.../repositories/put/PutRepositoryRequestBuilder.java
45.45% <0.00%> (-10.11%)
:arrow_down:

...er/src/main/java/org/opensearch/common/Stream.java
0.00% <0.00%> (ø)

...nsearch/cluster/metadata/RepositoriesMetadata.java
68.22% <21.42%> (-5.18%)
:arrow_down:

...rg/opensearch/cluster/metadata/CryptoMetadata.java
24.13% <24.13%> (ø)

...ch/action/admin/cluster/crypto/CryptoSettings.java
24.52% <24.52%> (ø)

...cluster/repositories/put/PutRepositoryRequest.java
55.91% <25.80%> (-15.06%)
:arrow_down:

...pensearch/crypto/CryptoClientMissingException.java
30.76% <30.76%> (ø)

...pensearch/cluster/metadata/RepositoryMetadata.java
72.85% <54.28%> (-15.24%)
:arrow_down:

...g/opensearch/repositories/RepositoriesService.java
75.88% <81.81%> (+3.46%)
:arrow_up:

... and 3 more

... and 486 files with indirect coverage changes

From this comment:

I believe this is a duplicate of https://github.com/opensearch-project/OpenSearch/issues/5800

Linked issue has specific mentions of Aiven and proposes to use that as a solution. Proposal here though is open for feedback.

@reta would Aiven consider promoting encrypted-repository-opensearch as a core plugin to offer index/repository encryption as a default security option? If so, then I'd like to see us improve that to fill some of the random access encryption gaps needed by this proposal guided by the coming "OnThe Fly Encryption Feature Proposal" and PoC in #3469. Perhaps this PR just gets trimmed to providing the key registry?

@reta would Aiven consider promoting encrypted-repository-opensearch as a core plugin to offer index/repository encryption as a default security option?

@nknize absolutely

If so, then I'd like to see us improve that to fill some of the random access encryption gaps needed by this proposal guided by the coming https://github.com/opensearch-project/OpenSearch/issues/3469 and PoC in https://github.com/opensearch-project/OpenSearch/issues/3469. Perhaps this PR just gets trimmed to providing the key registry?

Makes perfect sense, I will bring that to the team, thank you!

@nknize Thanks for the review!
To clear some confusions, this PR is just an integration PR to add encryption support for repositories but the actual framework implementation is done in other PRs which like you said are built in libs and expose a spi to provide key providers support. PRs are https://github.com/opensearch-project/OpenSearch/pull/8465 and https://github.com/opensearch-project/OpenSearch/pull/8466 . This is the meta issue which encapsulates all PRs.
If you look at other PRs, there is no context of snapshot, remote store or s3 plugin. It also provides the random access support as mentioned in the linked feature.
Structure of the plugin is as follows :

Core plugin - which provides actual encryption and decryption support - including partial encryption or decryption capabilities. This is located in libs.
SPI for key providers - To allow users to define their own key providers. For e.g. users can define their own KMS based key management implementations.

I honestly can't grok what the overall objective is?

Overall objective it to provide encryption/decryption support irrespective of the source and target location of the content.  Repository encryption is just one of the use cases.

What files are you wanting to encrypt?

For remote backed indexes, plan is to encrypt only the user data - translog and segment files.

Are you wanting encryption over the wire as well?

No, objective of this is to provide encryption of data at rest.
I don't think encrypted-repository-opensearch can be extended as it is tightly coupled with repository plugin and doesn't provide partial encryption or decryption support.
If we want to extend support for local disk as well, then we should be able to do that as well with current framework.

no clear use cases or examples how a downstream plugin leverages this framework

This is the spi which downstream plugin will implement to provide custom key providers.
Here is a sample implementation of the same.
I can add more details on exactly how these plugins can be installed. For now, this framework is only integrated with repository and therefore, I can add steps on how it can be used for a repository. Let me know this.

Closing this as it has been crossed out on the meta issue. @vikasvb90 Please reopen if this shouldn't be closed.


Running FASTQC on imported samples is super slow

For ~100 samples (Fix Recoli data), to copy the data into the millstone filesystem and then run FastQC takes about 250 sec.
Maybe we can make running FastQC optional?
Is there any other way to make this faster?

Currently, it should run in the background so that you can still continue
with other operations. I also have no problem making it optional.
On Wed, Feb 10, 2016 at 11:59 AM Gleb Kuznetsov<EMAIL_ADDRESS>wrote:

For ~100 samples (Fix Recoli data), to copy the data into the millstone
filesystem and then run FastQC takes about 250 sec.
Maybe we can make running FastQC optional?
Is there any other way to make this faster?
—
Reply to this email directly or view it on GitHub
https://github.com/churchlab/millstone/issues/629.

I think we should make this optional on a per sample basis (via the dropdown menu)

agreed. the corresponding wishlist feature would be aggregation of the
FASTQC output in the millstone table view - how many reads per sample, how
many adapters are present, what the average read quality is, any red flags,
etc
On Wed, Jun 15, 2016 at 10:04 AM Gleb Kuznetsov<EMAIL_ADDRESS>wrote:

I think we should make this optional on a per sample basis (via the
dropdown menu)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/churchlab/millstone/issues/629#issuecomment-226197099,
or mute the thread
https://github.com/notifications/unsubscribe/AAfcBOSYjgZqM7Mqr_XHC9tdYxQiS2SJks5qMAZmgaJpZM4HXdgz
.


feat: enhancements as result of easy-ui5 integration

this PR is based on using fiori-freestyle for scaffolding a basic UI5 app in easy-ui5.
(more precise, fiori-freestyle's generate()-API is used  in the generator-template-ui5-project sub-generator to scaffold the UI5 app)
as a result, the following enhancements were introduced to open-ux-tools/fiori-freestyle:

dynamically set initial view- and controller-name at scaffolding time: https://github.com/vobu/open-ux-tools-1/commit/bb8a2b508b58321e7cea51ec5f7993b6e4720f61
same for manifest.json: https://github.com/vobu/open-ux-tools-1/commit/1aef09425831277760531d4a1d4dbac1a016f572
provide CDN- and local resources for bootstrapping UI5 in index.html: https://github.com/vobu/open-ux-tools-1/commit/c451411f908539c5a46e6a8c14d13c7ec965249f

Also, a small regex fix is included: https://github.com/vobu/open-ux-tools-1/commit/86a9cb4c4974d3607af53aea2da6caf63d0ed3cc

will add some tests backing up the introduced enhancements, so converting this to draft until

All in all, I see one major bug you fixed and a set of reasonable requests to enhance the API. I will create corresponding feature requests and bug reports which I will send you for review. For each, I would like to see a separate PR for better tracking.
Btw, https://github.com/SAP/open-ux-tools/pull/63 is supposed to go today (or this week) simplifying the fiori-freestyle template leading to incompatible changes with your PR that need to be revisited.

right on, then i'll move to stand-by and wait what's coming my way after #63.
only then will i refactor the easy-ui5 integration.

@vobu can we close this PR? I think the PRs #77, #158 and #144 covered everything outlined in #78 which was defined based on your PR.

yep, closing it.
thx for the cooperation on all thingies so far!!!


Incorrect playback state

From a personal e-mail:

I do have a bug on the Sirius one: The app doesn't seem to be recognized by MPRIS when audio is playing. This results in not showing in the new notification panel for GNOME or for extensions that support this feature, but the bigger issue seems to be that this also doesn't allow the service to run while the page is closed or not in focus like your others.

SiriusXM is no longer available outside US:

Fixed in 1.4.


chore(http_mock): improvements & tapping

Summary
Introduce tapping for testing, expecially OIDC's behavior when sending requests to IDP.
bugfix: assert truthy
alias for not_all
more checks
better comment&document
Checklist

[ ] Cherry-pick to master

Issue reference
N/A

please ensure that the documentation properly renders;
here's how to check:
cd kong/spec
ldoc .
open docs/index.html

It requires to have ldoc installed; luarocks install ldoc

I pushed a commit with some docs fixes, please verify, and if possible extend to the other modules that are currently undocumented. These new get rendered properly.

fyi; the reason I'm pushing on this is because we have been neglecting the documentation in the helpers. Mostly because not everyone realizes this is actually user-facing stuff. We should pay more attention to this.
Plugin developers will use pongo docs to render and show the documentation when developing their plugins.

Added some more fixes, but ldoc simply sucks at multi-file modules/classes 😞
anyway, since I now committed to this PR, I can no longer approve it. Feel free to merge. @oowl @ADD-SP

still could approve 🤷 , so just did


[The Graph] Run the node

Run the graph node and point it to a local anvil instance to test a basic integration.

I got an error:
error: failed to run custom build command for `graph v0.35.0 (/workspace/graph-node/graph)`

Caused by:
  process didn't exit successfully: `/workspace/graph-node/target/debug/build/graph-002e2dacbf9ca36a/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=proto
  cargo:rerun-if-changed=proto/firehose.proto
  cargo:rerun-if-changed=proto/ethereum/transforms.proto
  cargo:rerun-if-changed=proto/near/transforms.proto
  cargo:rerun-if-changed=proto/cosmos/transforms.proto
  cargo:rerun-if-changed=proto

  --- stderr
  thread 'main' panicked at graph/build.rs:14:10:
  Failed to compile Firehose proto(s): Custom { kind: NotFound, error: "Could not find `protoc`. If `protoc` is installed, try setting the `PROTOC` environment variable to the path of the `protoc` binary. To install it on Debian, run `apt-get install protobuf-compiler`. It is also available at https://github.com/protocolbuffers/protobuf/releases  For more information: https://docs.rs/prost-build/#sourcing-protoc" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Installing:
sudo apt-get install protobuf-compiler

Protobuf is one of the requirements. See here.

I'm following this doc -> https://firehose.streamingfast.io/integrate-new-chains/firehose-starter#implement-the-reader, however the console_reader.go file is missing.

Those instructions are now a bit outdated sadly, sorry. There is no need for a specific console reader per integration.
https://github.com/streamingfast/firehose-core?tab=readme-ov-file#firehose-multi-chain-executor
The firehose-core project and its firecore binary can be used directly nowadays, as long as the reader-node invoked program respects the expected output format. No need for a specific firehose-.
Invocation is something like firecore start --reader-node-path= --reader-node-arguments=...
You can find the generic console reader here https://github.com/streamingfast/firehose-core/blob/develop/consolereader.go.
Expected format out of stdout should be:
FIRE INIT 3.0
FIRE BLOCK <block_num:integer> <block_hash:string> <parent_num:integer> <parent_hash:string <last_irreversible_block_num:integer> timestamp:unix_nano_integer <block:base64 encoded google.protobuf.Any of Block model>
...
See  https://github.com/streamingfast/firehose-core/blob/develop/consolereader_test.go#L74-L75 for an test example (it uses 1.0 as the version, but you should really specify 3.0).
Original msg:
https://discord.com/channels/666749063386890256/1278460328933589046/1278523243099197482


Article search for issues is not working

When you try to do an article search to add to an issue it doesn't display the list of articles correctly.

this is due to this.

this is due to this.


Server Failure

Hi,
Good day we are facing lot's of issues due to use for spam checker package
in link given .(https://pypi.python.org/pypi/spamcheck).we noticed that failure is occurring regularly.

Hi @uayyappa seems like the Spamcheck API hosted by Postmark is currently down. This is, unfortunately, out of our control as we only provide a Python wrapper.


Sketch some general principles

@georgiana-gligor agree: 1. estimate how long learning each section would take 2. be practical, i.e. do not ask the beginner to learn all of the HTTP, when he's still at learning HTML, but provide with just enough information for him to really understand why the DOM is built up by using multiple requests; at the bare minimum in this case, he should be instructed to make a few HTTP requests by hand.


Fix doc

Fix https://github.com/paritytech/substrate/issues/10270

This annotation isn't used for anything anyway? Can we not just remove it entirely?

yes annotation was removed


Update for 7.5.1rc2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

This is unrelated to the RC itself, but an error I oversaw in the last build. We need to update this conditional here so it does not run the test suite on PyPy + aarch64.
I think it should be like this:
- {% set with_test_suite = "true" %}  # [arm64 or python_impl == 'pypy']
+ {% set with_test_suite = "true" %}  # [(osx and arm64) or (python_impl == 'pypy' and not aarch64)]

We need to update this conditional here so it does not run the test suite on PyPy + aarch64.

Should I change that here, or just ignore the failure here and change it on the main branch?  Better yet, we should figure out why that test fails on Pypy on ARM.

The log shows a failure in TestDesmondDMSFile.test_NonbondedMethod, not just running out of time:

E       simtk.openmm.OpenMMException: NonbondedForce: There is already an exception for particles 0 and 1

I made the change here so we can get the rc out.

All tests passed, so I'm going to merge.


Add changes to #4007

This attempts to merge #4007 by adding the changes requested by @grobinson-grafana.

Superseded by #4007


add graffitipot

This is 2ch browser application.

Thank you for the contribution. It needed some fixes, so they were made in 1ad240e4f2d517422c04bdd38e03121039b65104. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

Thanks for your help.


syntax error when install busybox

python version:Python 2.7.6
pexpect in /usr/lib/python2.7/dist-packages
android: 7.1.1
the first time run "super_adb"
ls: /data/local/tmp/busybox: No such file or directory
install busybox...
download busybox binary...
2730% completechange permission :
/data/local/tmp/busybox[1]: syntax error: 'newline' unexpected
install busybox :
export PATH=/data/local/tmp/:$PATHsdm660_64:/ $ export PATH=/data/local/tmp/:$PATH
then in adb shell:
/data/local/tmp # busybox
/data/local/tmp//busybox[1]: syntax error: 'newline' unexpected

in adb shell:
/data/local/tmp # busybox
/data/local/tmp//busybox[1]: syntax error: 'newline' unexpected

@samsun639 The download url supplied by busybox has dead, I have made a backup in this project. It can work properly now.


JsonParsingException:null while using custom validations with ARRAY instance type

I am trying to implement a custom validation by implementing FormatAttribute. It works fin when the InstanceType is STRING. However, if I try to apply a format for an InstanceType ARRAY, then I get a JsonParsingException:null
My implementation
  @Override
  public InstanceType valueType() {
    return InstanceType.ARRAY;
  }

Exception Received
javax.json.stream.JsonParsingException: null
liberty    | 	at org.leadpony.justify.internal.base.json.DefaultJsonReader.newParsingException(DefaultJsonReader.java:148)
liberty    | 	at org.leadpony.justify.internal.base.json.DefaultJsonReader.readValue(DefaultJsonReader.java:122)

Sorry @adityamandhare
The current implementation has a restriction on custom formats. They can be applied only to simple types such as string, number, boolean, and null.  I will clarified this limitation in README and Javadoc in the last commit.
Do you really need custom format for array or object?

@leadpony So I have a scenario wherein I have an array of Customer objects. And Customer object can be be of type Manufacturer, Retailer, Distributor and END_USER. The customer object also has other attributes along with type line firstName, lastName etc. I need to make sure that this array of customers must contain Manufacturer and Retailer customers.
So I was thinking that for the array of Customers I can implement a custom validation to make this check and return error if Manufacturer or Retailer customer is missing.
Does this validation library have a better way to support validating this array of objects instead of writing a customer validation?

Hello @adityamandhare
I have imagined the expected JSON documents based on the story you told me.
Good JSON
[
  {
    "type": "Manufacturer",
    "firstName": "John",
    "lastName": "Doe"
  },
  {
    "type": "Retailer",
    "firstName": "Jane",
    "lastName": "Doe"
  },
  {
    "type": "Distributor",
    "firstName": "Precious",
    "lastName": "Doe"
  }
]

Bad JSON (Retailer type is missing)
[
  {
    "type": "Manufacturer",
    "firstName": "John",
    "lastName": "Doe"
  },
  {
    "type": "Distributor",
    "firstName": "Precious",
    "lastName": "Doe"
  }
]

Are these examples appropriate?

Perhaps you need something along the lines of:
{
   ...
  "allOf" : [
       { "contains" : { "properties" : { "type" : { "const" : "Manufacturer" } } } },
       { "contains" : { "properties" : { "type" : { "const" : "Retailer" } } } },
       { "contains" : { "properties" : { "type" : { "const" : "Distributor" } } } }
   ]
   ...
}

note that the contains schema validates against one or more items in the array, so the above example guarantees that your array items have one item of each type. Actually at least one item of each type, since the above validates perfectly fine with duplicates.

@leadpony the JSON you have posted based on my story is correct. @atomictag I tried your suggestion. It did not work in my case.
{
  "type": "array",
  "title": "The Customer Schema",
  "minItems": 2,
  "items": {
    "type": "object",
    "required": [
      "firstName",
      "lastName",
      "type"
    ],
    "properties": {
      "firstName": {
        "type": "string"
      },
      "lastName": {
        "type": "string"
      },
      "type": {
        "type": "string",
        "enum": [
          "Manufacturer",
          "Retailer",
          "Distributor"
        ]
      }
    },
    "allOf": [
      {
        "contains": {
          "properties": {
            "type": {
              "const": "Manufacturer"
            }
          }
        }
      },
      {
        "contains": {
          "properties": {
            "type": {
              "const": "Retailer"
            }
          }
        }
      }
    ]
  }
}

Thank you @adityamandhare @atomictag
The keyword contains must be applied to the array itself, not to each item in it.

@adityamandhare I think you need to move that allOf outside of items - the contains assertion is not a property of items, but of the array schema itself.

oh @leadpony was faster than me on this one :)

ahh, I see. Thanks @leadpony. Moving allOf outside items does work and validate the array for missing objects. However, the errorMessage is too generic At least one of the following sets of problems must be resolved. Also the problem.getPointer() returns null value (which usually returns the field name which has error). The problem.getBranch(0) does help get some useful error message The value must be constant string "Manufacturer". However I would like to give a more user-friendly error message like Missing customer of type 'Manufacturer'. Is there a way I can use contains for identifying the error, but for use my own custom error message?

Hi @adityamandhare
I have tried your modified schema with Justify CLI and got the following problem messages:
Validating the instance "issue35.json"...
At least one of the following sets of problems must be resolved.
1) [3,26][/0/type] The value must be constant string "Retailer".
2) [8,25][/1/type] The value must be constant string "Retailer".
At least 1 problem(s) were found in the instance "issue35.json".

You can try other validator such as https://jsonschema.dev/ and will see similar messages after all.
I agree with you that these are not very user-friendly messages.
It is difficult for a validator to fully understand the real intent of constraints defined in the complex schema.

@leadpony would it be some cool new feature to add wherein you give freedom to the return a customized errorMessage when a schema validation error with a field is found?

Unfortunately there is no such a feature in the current release.
Please see also the issue #16

@leadpony actually the solutions described in issue #16 helped resolve my issue. I can use the contains to make sure the required customer is present and then use my custom keyword to identify the error field and user friendly error message. Thanks 🙂


Allow pubspec to be optional

Allow pubspec to be optional

final pubspec = PubSpec( )... version

I need to set the version dynamically without having to set env desc....

I've just released a version that only requires the name.
On Sat, 13 Jan 2024, 6:10 pm laterdayi, @.***> wrote:

final pubspec = PubSpec( )... version
I need to set the version dynamically without having to set env desc....
—
Reply to this email directly, view it on GitHub
https://github.com/onepub-dev/pubspec_manager/issues/4#issuecomment-1890352642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OG4XENW4YRPMRS2WKLYOIXMRAVCNFSM6AAAAABBZDZXPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGM2TENRUGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Fix a couple typos in README

Nothing major, just fixed two spots in the README file:

The code example for setting the email used init-author-name.
The header for init-scripts-start called it the Test Script.

Thanks @thancock20!


Training details

We greatly appreciate the author's contribution. We are attempting to replicate this work, but we have encountered obstacles during the training process. The dataset is 'reprocessed' at the start of each training session.Below is the list of files from our preprocessed dataset and the training command.

Hi, thanks for running our code.
Sorry for the confusion. The downloaded pkl files (as the p1_root argument) are the prediction results by hivt (we refer to 'trajectory generation backbone' in our original paper). For training, it's necessary to process raw data to pkl files for our refinement.
If you do have your own preprocessed dataset, you can edit this function (like return directly) https://github.com/opendilab/SmartRefine/blob/main/datamodules/argoverse_v1_datamodule.py#L37, so the pipeline won't process data again. Also, this may need some extra editing in the dataset.py file case by case.
Hope it helps. Feel free to ask if you have any further concerns.

have you met this error？ @Harry333777


Use workflow configuration variables for quay organization names

We've defined QUAY_ORGANIZATION and QUAY_ORGANIZATION_DEV workflow configuration variables, so we don't need to use the composite action to set these as environment variables anymore.
Ref: https://github.blog/changelog/2023-01-10-github-actions-support-for-configuration-variables-in-workflows/
Suggested-by: Nicolas Busseneau<EMAIL_ADDRESS>Signed-off-by: Michi Mutsuzaki<EMAIL_ADDRESS>Use workflow configuration variables for quay organization names

@bimmlerd Do we need to backport this for 1.12?

yeah I think we want this for all stable branches, actually.

removed needs-backport labels since this PR was reverted in https://github.com/cilium/cilium/pull/23169


[tool_crash] FileSystemException: Directory listing failed, OS Error: File name too long, errno = 63

Command
flutter run

Steps to Reproduce

...
...
...

Logs
FileSystemException: Directory listing failed, OS Error: File name too long, errno = 63
#0      _Directory._fillWithDirectoryListing (dart:io-patch/directory_patch.dart:42:24)
#1      _Directory.listSync (dart:io/directory_impl.dart:233:5)
#2      ForwardingDirectory.listSync (package:file/src/forwarding/forwarding_directory.dart:43:12)
#3      ForwardingDirectory.listSync (package:file/src/forwarding/forwarding_directory.dart:43:12)
#4      RunCommand.usageValues (package:flutter_tools/src/commands/run.dart:482:14)
<asynchronous suspension>
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1565:15)
<asynchronous suspension>
#6      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
<asynchronous suspension>
#7      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#8      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#9      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
<asynchronous suspension>
#12     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:91:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     main (package:flutter_tools/executable.dart:91:3)

[✓] Flutter (Channel stable, 3.10.0, on macOS 13.4 22F66 darwin-arm64, locale
    en-AE)
    • Flutter version 3.10.0 on channel stable at /Users/ali/Desktop/dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (8 weeks ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/ali/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web

Closing this as a duplicate of https://github.com/flutter/flutter/issues/80873.
Kindly subscribe to the original issue for updates.
Thank you


Fixes #1624 feat: support for landscape mode added

Title
Fixes #1624 (Show 2 images per row instead of 1 in landscape mode while searching)
Description (required)

Checked if Configuration is protrait or landscape and changed the Layout Manager to Linear or Grid accordingly.

Tests performed (required)
Manually Tested on API 25 & MotoG5S+, with ProdDebug variant.
Screenshots showing what changed

Before

After

Codecov Report

Merging #1625 into browse-commons-via-app will decrease coverage by <.01%.
The diff coverage is 0%.

@@                    Coverage Diff                    @@
##           browse-commons-via-app   #1625      +/-   ##
=========================================================
- Coverage                    3.77%   3.77%   -0.01%
=========================================================
  Files                         158     158
  Lines                        7922    7924       +2
  Branches                      733     734       +1
=========================================================
  Hits                          299     299
- Misses                       7606    7608       +2
  Partials                       17      17

Impacted Files
Coverage Δ

...rw/commons/explore/images/SearchImageFragment.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


python312Packages.trimesh: 4.4.9 -> 4.5.0

Changelog: https://github.com/mikedh/trimesh/releases/tag/4.5.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 348741 at 50f31648 run on x86_64-linux 1

:fast_forward: 1 package marked as broken and skipped:

cura

:white_check_mark: 6 packages built:

python311Packages.manifold3d
python311Packages.pyrender
python311Packages.trimesh
python312Packages.manifold3d
python312Packages.pyrender
python312Packages.trimesh


[Feature] Plugin Manifest Output Validation

Describe the solution you'd like
We should ensure that the OpenAPI specification in OpenAI's plugin manifest output folder conforms to the validation rules at https://platform.openai.com/docs/plugins/getting-started:

Keep in mind the following limits in your OpenAPI specification, which are subject to change:

200 characters max for each API endpoint description/summary field in API specification
200 characters max for each API param description field in API specification

Please note that these rules are subject to change. We should look at storing and reading the rules from a configuration file.
This is just a quality-of-life improvement to help customer catch and address common errors that can occur from the manifest.

Transfered to https://github.com/microsoft/OpenApi.ApiManifest/issues/31.


Add option to modify the dialogs buttons labels [Core] [Cocoa]

Ok, I'll reset the other dialogs modifications, but on Stack Trace dialog I think that the default buttons when retry is True should be "Retry" and "Quit" instead of "Retry" and "Cancel". This modification will fit for a "Critical" Stack Trace. The "Cancel" label it's not clear enough to inform the user that this button will terminate the application. what do you think?


tmp folder is not automatically created for uploads

Upload panel assumes that tmp folder found in the config already exists. This leads to errors if someone or other portlets (e.g. barcode creation) have not created it.

Fixed in version 1.10.0


fix: include missing  header

I was getting compilation error, due to the missing header which says
error: ‘plus’ is not a member of ‘std’
error: ‘minus’ is not a member of ‘std’
These function objects are defined in header <functional> since C++-14.
So I included this header.
This PR is also related with issue #50

Thanks for catching this! It didn't pop up compiling on Ubuntu 20 or MacOS


Update Terms of Service to include Azavea

Overview
Update Terms of Service to include Azavea and remove previous partners - https://info.openapparel.org/tos/
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Additional Context
Note that this will need to be updated in the future after OAR incorporation.

These appear on the Squarespace site.

@katieashaw A heads up that these will need to be changed.

Absolutely! This has been on my radar for a while now.
We've got a section on reviewing the current info.openapparel site in our launch GANTT chart, which we'll be sharing with you soon. TofS very definitely a part of that review!

Edit to add that we will need to update the ToS to include GDPR compliance language and info on any tracking and cookies.


[PROPOSAL] Telemetry in Rancher Turtles

Create a proposal on how we add telemetry (logging, metrics, distributed tracing) to Rancher Turtles. We will need to consider how Rancher currently handles this and think about integration.

see #38


bunify package.jsons

Please read contributing guidelines and remove this line.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5528  👈
#5527
#5521
#5526
#5525
#5520
#5519
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @charlielye and the rest of your teammates on  Graphite


[Button] custom buttons hover style on touch device

Hi,
on touch devices, happen only on customs buttons, if you press the button and release pressure outside the hover styles  will be removed only after you will press anywhere else.
happen on the material-ui website it self...
thanks.

@michael-ecb Ahah, yes! The point is precisely to reproduce Bootstrap output. They show the hover style on mobile too. We don't.


pokecli.py: wait_time for every exception randomized

Feature Request (https://github.com/PokemonGoF/PokemonGo-Bot/issues/5579)
Short Description:
it's create a random waiting time based on config for all exception (connection lost, throttling, and so on), so no static time span will be used anymore

randint(min,max)
config.reconnecting -> min
config.reconnection * 60 -> max

👍

Can't review now. Someone please do it and merge, if agreed.

Any updates on this?

still waiting for a review, or further discussion...

👍

This doesn't work as expected...
wait_time = randint((config.reconnecting_timeout * 0.8 * 60), (config.reconnecting_timeout *  1.2 * 60))
randint requires two INTEGER values, whereas this line provides two FLOATS. Result:
Traceback (most recent call last):
  File ".\pokecli.py", line 844, in <module>
    main()
  File ".\pokecli.py", line 189, in main
    wait_time = randint((config.reconnecting_timeout * 0.8 * 60), (config.reconnecting_timeout *  1.2 * 60))
  File "C:\Python27\lib\random.py", line 242, in randint
    return self.randrange(a, b+1)
  File "C:\Python27\lib\random.py", line 187, in randrange
    raise ValueError, "non-integer arg 1 for randrange()"
ValueError: non-integer arg 1 for randrange()

Correction: works if reconnecting_timeout in config is set to default 15, or any multiple of 5, but fails if set to anything else. (5 x 0.8 = 12 (int), 5 x 1.2 = 18 (int). In my case, I have reconnecting_timeout set to 3, so 3 x 0.8 = 2.4 (float), 3 x 1.2 = 3.6 (float).


fix distribution seed in tractablebufferstock

I have to defer to @mnwhite on this.
In some of the ConsumptionSaving models, there was a choice to set seeds in an unconventional way.
I could never tell if this was a deliberate design. (I would like to think it isn't, and would otherwise merge this PR. It looks good to me.)


wait util. Fix #28?

@Muraszko or @foo4thought ?

file changes look good, but what's the question about #28?

but what's the question about #28?

Just some uncertainty about whether this really constituted a fix: I think it does.


Add version/feature check to verible_verilog_syntax.py

Makes VeribleVerilogSyntax constructor raise an exception when verible-verilog-syntax executable version is too old. It checks the version printed by --version switch. It fallbacks to checking --helpfull output for --export_json string when version string is not available.
The executable's version is additionally stored in the version attribute.
Depends on https://github.com/google/verible/pull/832 to pass Windows build in CI.

I think in general, we can't rely on the git outputs available, because if the binary has been compiled from a tar archive source, there is no git info.
So the only thing to look for is probably the built time. It doesn't really help to tell if something is too old as it only regards the build time not the commit time, but that is as close as it gets.

We should be embedding the git info in any tar archives we produce?
On Wed, 19 May 2021 at 13:49, Henner Zeller @.***>
wrote:

I think in general, we can't rely on the git outputs available, because if
the binary has been compiled from a tar archive source, there is no git
info.
So the only thing to look for is probably the built time. It doesn't
really help to tell if something is too old as it only regards the build
time not the commit time, but that is as close as it gets.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/verible/pull/823#issuecomment-844461584, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFFXBCTTT4AV6XN726DUDTOQP5BANCNFSM45EQQWGQ
.

Yes, the binary archives we generate should contain that compiled in.
But if someone just downloads a source archive generated by github, then this will not be included @mithro.

I think in general, we can't rely on the git outputs available, because if the binary has been compiled from a tar archive source, there is no git info.

Yeah, I've added a fallback that just checks --helpfull output for --export_json.

Yes, the binary archives we generate should contain that compiled in.
But if someone just downloads a source archive generated by github, then this will not be included @mithro.

I think we should either refuse to compile or output 'UNKNOWN' version from that?

Taking a step back - what is the problem we try to solve ? I suppose we want to make sure that the json format emitted is compatible with the format being parsed in the Python script. So we should formulate it as such.

Oh, I see I didn't mention this. Originally it was a request from OpenTitan to check whether Verible supports JSON output or not. If it is supported, Verible should be used for parsing.
Eventually it has been done so that the script always tries to use Verible and fallbacks to non-Verible parsing when Verible failed for any reason.
Since the original reason for this PR is no longer valid, I think it can be closed for now. Should I create an issue to make this attempt easily discoverable in case the need for version checking appear in the future?

So to make this more explicit, I'd consider having version numbers in the json output, maybe some toplevel field version: 1 or so which is then checked in the Python script.
Whenever the format changes in an incompatible way (which will be a deliberate choice), we should increase that when emitting the Json format (and adapt the script to understand the new format and compare against version==2). That way, we make versioning and checks a deliberate choice, but also have very discrete points when output changes (and hopefully this number will only increase slowly).

This is a good idea. It could be introduced when the JSON version changes to "2", so that "no version field" == "version 1".

Since the original reason for this PR is no longer valid, I think it can be closed for now. Should I create an issue to make this attempt easily discoverable in case the need for version checking appear in the future?

Yes, I think an issue where we also collect the potential ideas (marking version numbers in json) sounds good.

This is a good idea. It could be introduced when the JSON version changes to "2", so that "no version field" == "version 1".

Sounds good. After all, it will only the version > 1 json that introduces the new feature called version number :)


(feature) Project templates

Pull Request
📖 Description
This PR adds templates to the toolkit that allow you to start a new Blazor Server or Blazor WebAssembly project with all the needed changes to use the Fluent UI component library already in place
🎫 Issues
Addresses #88
👩💻 Reviewer Notes
When merging this in, we need to update the general readme to point to these templates and describe how to set them up
📑 Test Plan
Go through provided readme and see if steps needed are clear.
✅ Checklist
General

[ ] I have added tests for my changes.
[X] I have tested my changes.
[X] I have updated the project documentation to reflect my changes.
[X] I have read the CONTRIBUTING documentation and followed the standards for this project.

⏭ Next Steps
Once the PR #142 is merged in we need to update the templates and generate/upload new NuGet packages (instructions provided in templates/readme.md

I like this. A couple of questions:

Should we simplify the started templates or do you feel it's necessary to have such a "full" starter kit?

Can you elaborate? The templates are a 'translation' of what you get when you do 'File->New' for a Blazor project

Should we change the package name to maybe be something more like Microsoft.Fast.Templates.FluentUI.BlazorWebAssembly?

Yes! I'll add this in a new commit to this PR

Do we need to do anything with our publish process to ensure these additional packages get published?

I'll look into that

I like this. A couple of questions:

Should we simplify the started templates or do you feel it's necessary to have such a "full" starter kit?

Can you elaborate? The templates are a 'translation' of what you get when you do 'File->New' for a Blazor project

Should we change the package name to maybe be something more like Microsoft.Fast.Templates.FluentUI.BlazorWebAssembly?

Yes! I'll add this in a new commit to this PR

Do we need to do anything with our publish process to ensure these additional packages get published?

I'll look into that

For the template content, if that's the same as File->New Blazor then let's leave that as is. We want it to feel familiar for Blazor devs as much as possible.
Thanks @vnbaaij !

Do we need to do anything with our publish process to ensure these additional packages get published?

The packages only need to be re-created when the template sources are changed/updated. This is a manual step (see the readme file in the \templates folder). After that they need to be uploaded to NuGet. I'm not sure how much of that can be automated and if it is worth the hassle.
With my latest changes the latest stable version in the 1.* range of the Fluent UI package should be installed when creating a project. This further reduce the need to update the templates frequently.
The generated NuGet template packages are included in the \templates folder. Once tested and approved they can be made available on NuGet. Instructions on how to install, use and uninstall are in the the readme file in the \templates folder

Result in VS after installing templates:

Result in browser after using Server template:

@awentzel Can you take a look at this when you get a chance? This PR will add two new packages that we'd want to publish, which enable starter templates through Visual Studio and the CLI. I wasn't sure if our publish pipeline and steps would handle multiple packages or if we needed to modify things.

@awentzel Can you take a look at this when you get a chance? This PR will add two new packages that we'd want to publish, which enable starter templates through Visual Studio and the CLI. I wasn't sure if our publish pipeline and steps would handle multiple packages or if we needed to modify things.

@EisenbergEffect I'll investigate, as I unclear as well.

@awentzel let me know if you want to do a call on this to let me explain the details


UI enhancement: MP Span record display

User reported the following:

It would be great if this screen could be modified to show some important information that’s contained in the span record (like the span and/or range). Information like the Method and UOM aren’t as useful to the end user.  I understand there may be real estate issues for displaying ALL the data but think there is more valuable info to communicate without requiring the user to click on the View window.

Review 1.0 and see what values are missing.


fix: ignore harvester patch diff of default sc

Problem:
The mcc-harvester bundle CR will contain an errApplied status after setting a different default storageClass.
Solution:
Ignore the patch diff since Harvester is allowing users to config different default storageClass.
Related Issue:
https://github.com/harvester/harvester/issues/3802
Test plan:

spin up a new harvester cluster with the new ISO image.
config a new storage class and set it as the default one.
check the bundle status of the mcc-harvester later, it should not contain any errors like below:

ks get bundles -n fleet-local
NAME                                          BUNDLEDEPLOYMENTS-READY   STATUS
fleet-agent-local                             1/1
local-managed-system-agent                    1/1
mcc-harvester                                 0/1                       ErrApplied(1) [Cluster fleet-local/local: cannot patch "harvester-longhorn" with kind StorageClass: admission webhook "validator.harvesterhci.io" denied the request: default storage class %!s(MISSING) already exists, please reset it first]; storageclass.storage.k8s.io harvester-longhorn modified {"metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}
mcc-harvester-crd                             1/1
mcc-local-managed-system-upgrade-controller   1/1
mcc-rancher-logging                           1/1
mcc-rancher-logging-crd                       1/1
mcc-rancher-monitoring                        1/1
mcc-rancher-monitoring-crd                    1/1

@mergify backport v1.1


New Deployment

Question
What should I follow to be able to create a kubernetes deployment and be able to see it on the Jaeger UI?

The Kubernetes deployment docs for the Demo


Feature request: custom themes

What about some customazable themes?
(Idk where say a suggestion)

In the text field and borders customazable color

well i guess i could add that, but for now i'd like to focus on improving the mod's features. Right now the text field border is hardcoded, but as far as the buttons are concerned, you should be able to modify those using a resource pack


Update requirements.txt

requirements.txt is for dev deps

@Borda dk what this is about. any tips?

I would keep
coverage==4.5.3
mkdocs==1.0.4
pytest==5.0.1

in separate tests/requiremenst.txt because it is not needed for users who just want to use it...
nice example https://github.com/scikit-image/scikit-image/blob/master/requirements.txt


Update fs2-core, fs2-io, fs2-scodec to 3.5.0

Updates

co.fs2:fs2-core
co.fs2:fs2-io
co.fs2:fs2-scodec

from 3.4.0 to 3.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.4.0).
You might want to review and update them manually.
README.md

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "co.fs2" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1

Superseded by #161.


[Program]: efficency of FindTheMaximumSumOfAContiguousSubarray.js

What would you like to share?
i think there is another way to represent to the requested solution
Additional information
function getTheHighstSumInArr(arr): {
const arrToWork = arr.sort((a, b) => a - b);
[...new Set(arrToWork)];
const arrToSum: number[] = [];
let index = arr.length;
for (let i = 0; i < 4; i++) {
arrToSum.push(arrToWork[--index]);
}
const res = arrToSum.reduce((a, b) => {
return a + b;
});
return res;
}
Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

!assign

This issue is now ready for contribution


Your example for credit card "cardElement" is not declared

How to declare cardElement?

Hi @mylastore!
You can find an example of declaring a cardElement here:
https://github.com/joshnuss/svelte-stripe-js/blob/dfe3338fa32d5530f8a274e21d5dc73c4eca3823/src/routes/examples/credit-card/index.svelte#L26
Closing this issue, since I think it answers the question. Feel free to re-open if you have further questions about this


Failing to re-publish a kata

I don't know if it's just me: I can use the platform normally and solve katas but, at the moment, it doesn't seem to be possible to re-publish one of my katas with 3 translations (already working and validating tests  with no issues) where I simply need to change the description.
I see the red progress bar extending in the browser's window's top (both in Firefox and Chrome) but always getting "Publishing Timed Out!" warning.

background process went down. Its back up but its going to be a while before it catches up on its work.


Buildah bud does not work with SELinux

buildah bud was not setting the mount label on the image
so SELinux in enforcing mode is blocking writing to the image
This patch also fixes a similar problem with the buildah mount
command
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@TomSweeneyRedHat @nalind PTAL
We need this one quick to get it into RHEL.

Yes How did I miss that...

@nalind Should we just remove this param and have it happen automatically?

@rh-atomic-bot r=TomSweeneyRedHat

Related BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1516431


Documentation: Add additional link to FromRequest

I searched the docs for the extractor listings more often then I'm willing to admit, so I'd love to add a link where I would expect it.

Thanks! 🙂


Refactoring Python codebase

Changes
This PR carries the following updates regarding Python library implementation:

[X] Major refactoring
[X] Update to documentation
[X] Library update to 1.1.0
[X] Making library encoding agnostic

Motivation
Standard webhook specification states that:

The payload should be JSON formatted for maximum compatibility, but other content types can be used as well.

The current Python implementation doesn't support the aforementioned statement and exhibits external coupling - two modules share an externally imposed data format.
The significant change is getting rid of returned JSON-encoded payload -- hence removing external coupling
Removing:
return json.loads(payload)

Adding:
return payload

All unit tests pass.
P.S
Now, the meaning of the word standard makes sense.  Otherwise, this library should be renamed to webhookJSONstandard
Live long and pull request!

Hey there, i'm sorry this PR didn't get a review earlier on. Could we rebase this one and work on landing it?


How to use RealSense in .Net Core Native?

I have a RealSense .Net Core project that works fine.
When I generate a single-EXE file with the ILC (https://devblogs.microsoft.com/dotnet/the-net-native-tool-chain/) it fails when creating the config with this error:
System.Exception: Method '[Intel.RealSense]Intel.RealSense.NativeMethods.rs2_create_config(object&)' requires marshalling that is not yet supported by this compiler.
at Intel.RealSense.NativeMethods.rs2_create_config(Object&) + 0x34
at Intel.RealSense.Config..ctor() + 0x23
at RealSenseStreamer.BaseStreamer.FrameGrabber() + 0x5d (<- my code 'New config')
Is .Net Native supported?

Is .Net Native supported?

No, not officially.
Ultimately, you have to include the native realsense2.dll for this to work, I don't see any way around it.

Hi @smirkingman,
Do you need any further clarifications regarding this topic?

Hi Sergey,
thanks for the follow-up. I don't understand your suggestion:

Ultimately, you have to include the native realsense2.dll for this to work, I don't see any way around it.

When I publish as a netcoreapp2.1, realsense2.dll gets copied to the publish directory (so presumably the build recognised tghe dependency) and the program starts but fails with

requires marshalling that is not yet supported by this compiler.

How can I workaround this?

@smirkingman In case there is no corert documentation about marshaling limitations, I suggest checking its source code to find why this exception is thrown: https://github.com/dotnet/corert/blob/71f811248a4e3696d35fa42b7e4884ab66c22d5e/src/Common/src/TypeSystem/IL/Stubs/PInvokeILEmitter.cs#L355

Hi @smirkingman,
Did you have a chance to try out @aalmada's suggestion?
At this stage of development .NET Native precompilation technology is not supported by Intel RealSense SDK 2.0. We are working on adding support for it but there is not a schedule yet.
Thank you!

@aalmada's suggestion indeed answers my question, the header of PInvokeILEmitter.cs says

Provides method bodies for PInvoke methods
This by no means intends to provide full PInvoke support. The intended use of this is to
a) prevent calls getting generated to targets that require a full marshaller
(this compiler doesn't provide that), and b) offer a hand in some very simple marshalling
situations (but support for this part might go away as the product matures).

I was just trying out the precompilation to see if it was an envisageable avenue; if support is planned, I'm happy to wait.
Many thanks, the support here is exceptional, expert and diligent :)


Refactor hardcoded versions in parent pom

Refactor hardcoded dependency  versions in parent pom.

PR https://github.com/apache/incubator-dolphinscheduler/pull/773 addresses trivial refactor.


The cancel method on promises is no longer supported (v4)

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(pagination): create pagination section

This create our default style paginate.

Current coverage is 100% (diff: 100%)

Merging #177 into master will not change coverage

@@           master   #177   diff @@
====================================
  Files          19     19
  Lines         334    334
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          334    334
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 09628a3...3810de2

@leandrogrillo can you see the changes added recently?


Songs doesnt downloads

if i try to download all songs, server seems sending them, but client fails downloading them

arcaea 5.5.8c
server from dev branch

The server cannot get its address correctly. Please set the config item DOWNLOAD_LINK_PREFIX.

how i should get prefix?


fixing bug in generate_pheval_result()

Python was not able to recognise the typing of list contents, i.e., [RankedPhEvalVariantResult] and so threw errors when called in the runner implementation for post-processing. Fixed this issue by checking that all the items in the list are that of the same class and then writing the corresponding result

I cant judge this (too out of the loop with python dev these days) but my gut feeling is telling me https://www.w3schools.com/python/ref_func_all.asp but I might be 100% wrong.

Yes you're completely right! Looks cleaner this way as well


load balancers rely on lighthouse for service discovery

Load balancers currently use a separate protocol for service discovery than service to service calls. This bring load balancers in line with how other parts of Nelson work.

Codecov Report

Merging #7 into master will increase coverage by 0.5%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master       #7     +/-   ##
=========================================
+ Coverage   62.24%   62.74%   +0.5%
=========================================
  Files         124      124
  Lines        4418     4370     -48
  Branches       60       82     +22
=========================================
- Hits         2750     2742      -8
+ Misses       1668     1628     -40

Impacted Files
Coverage Δ

core/src/main/scala/routing/cron.scala
0% <ø> (ø)
:arrow_up:

core/src/main/scala/loadbalancers/package.scala
0% <0%> (-47.06%)
:arrow_down:

core/src/main/scala/Actionable.scala
7.14% <0%> (-0.27%)
:arrow_down:

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 5157989...c176b14. Read the comment docs.


Answerserver helm chart

Think I've included all files, let me know if I've missed anything or included anything I shouldn't have.
Is there a way to add tests for this or is manual testing sufficient?

I seem to be getting errors when I try to deploy the chart, specifically with postgres and answerbank, but I'm not sure if this is an issue with my setup specifically or if it's an actual issue with the chart. I can't see why any of the changes would cause errors.

I can deploy the chart fine, but it gives the same answerbank/postgres errors I was having before. I went to an old commit from last week which worked before and I'm getting the same errors, so think it might be a weird issue with my setup, I'll try recreating my cluster and see if that makes a difference.


reveal nft metadata after mint finished

investigating submarine and also upgrade function to change tokenuri, and subsequently lock it

fixed by #180

closing in favor of implementing rand


Enhancement: "businesslike conduct" round to reduce data error from 0.09 to 0.05 (~50% accuracy enhancement)

hi,
we have seen some problems when it comes to rounding (in our case for temp measurements).
in the current code the float temp just gets cut after the 1st decimal place, which is very inaccurate!
 uint32_t v = value * multiplier;
in this case the error is at worst 0.09. so almost 0.1° off.
instead the float temp should be businesslike conduct rounded (in germany we call this "Kaufmännisches Runden") before chopping off the last digit, like so:
 uint32_t v = round(value * multiplier);
in this case the error is @ max. 0.05° off. which is much more accurate for professional use. of cause other values can benefit from this kind of correction, too.

for reference: https://github.com/ElectronicCats/CayenneLPP/issues/44#issuecomment-1594235566


Feature/13 openapi

Initial OpenAPI integration.
OpenAPI

OpenAPI v3.0 is available

Offers API doc at http://localhost:8080/v3/api-docs & http://localhost:8080/v3/api-docs.yaml

Implemented using org.springdoc:springdoc-openapi-ui (replacement of the late springfox).

Current user credentials:
TestUser / password123
Swagger
Swagger is present, can be loaded at http://localhost:8080/swagger-ui/index.html#

Closes #13

Did you look into the Spring actuator and its possible addition to the Swagger Docs?

Did you look into the Spring actuator and its possible addition to the Swagger Docs?

Yes, this there already is an issue for this - https://github.com/AbsaOSS/login-gateway/issues/6


How to control device used ?

Hello, I don't see any parameter to control if the model runs on GPU or not, is there a way to know ? Because when i have done tests and the model doesn't seem to run on GPU

Sorry, i just found: you have to put map_location='cuda' as argument in the from_pretrained function. You should indicate this in the readme.


miller: 5.9.1 -> 5.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/johnkerl/miller/releases.
meta.description for miller is: "Like awk, sed, cut, join, and sort for name-indexed data such as CSV, TSV, and tabular JSON"
meta.homepage for miller is: "http://johnkerl.org/miller/"
meta.changelog for miller is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.10.0 with grep in /nix/store/cinngs37ais39j88hai10c4d8d2drrmr-miller-5.10.0

directory tree listing: https://gist.github.com/a30eb77e5178b9234e2053813ecb29cb

du listing: https://gist.github.com/2702f407b83b9480a60e6f28342d2060

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
miller

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cinngs37ais39j88hai10c4d8d2drrmr-miller-5.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A miller https://github.com/r-ryantm/nixpkgs/archive/93d86b89e02fa8a149bf1fc5d0de2062c61206ae.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cinngs37ais39j88hai10c4d8d2drrmr-miller-5.10.0
ls -la /nix/store/cinngs37ais39j88hai10c4d8d2drrmr-miller-5.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

miller

Maintainer pings
cc @mstarzyk for testing.

Result of nixpkgs-review pr 105527 run on x86_64-darwin 1

1 package built:

miller


[Fix] Remove readme picture size

Remove picture size to make it looks larger in readme.md.
Before:

After:

:P


bulid error

`
Compiling tectonic_xetex_layout v0.2.4 (/Users/captain/texpresso/tectonic/crates/xetex_layout)
The following warnings were emitted during compilation:
warning<EMAIL_ADDRESS>/opt/homebrew/Cellar/icu4c/74.2/include/unicode/localpointer.h:224:40: error: expected ';' at end of declaration list
warning<EMAIL_ADDRESS>/opt/homebrew/Cellar/icu4c/74.2/include/unicode/localpointer.h:399:36: error: expected ';' at end of declaration list
warning<EMAIL_ADDRESS>/opt/homebrew/Cellar/icu4c/74.2/include/unicode/ubidi.h:579:1: error: expected ';' at end of declaration list
warning<EMAIL_ADDRESS>7 warnings and 3 errors generated.
error: failed to run custom build command for tectonic_xetex_layout v0.2.4 (/Users/captain/texpresso/tectonic/crates/xetex_layout)
Caused by:
process didn't exit successfully: /Users/captain/texpresso/tectonic/target/release/build/tectonic_xetex_layout-b37a63f57be228df/build-script-build (exit status: 1)
--- stdout
cargo:warning=/opt/homebrew/Cellar/icu4c/74.2/include/unicode/localpointer.h:224:40: error: expected ';' at end of declaration list
cargo:warning=/opt/homebrew/Cellar/icu4c/74.2/include/unicode/localpointer.h:399:36: error: expected ';' at end of declaration list
cargo:warning=/opt/homebrew/Cellar/icu4c/74.2/include/unicode/ubidi.h:579:1: error: expected ';' at end of declaration list
cargo:warning=
cargo:warning=7 warnings and 3 errors generated.
exit status: 1
--- stderr
error occurred: Command env -u IPHONEOS_DEPLOYMENT_TARGET "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "layout" "-I" "/Users/captain/texpresso/tectonic/crates/bridge_core/support" "-I" "/Users/captain/texpresso/tectonic/target/release/build/tectonic_bridge_harfbuzz-9e8707849e7aac32/out" "-I" "/opt/homebrew/Cellar/graphite2/1.3.14/include" "-I" "/opt/homebrew/opt/freetype/include/freetype2" "-I" "/opt/homebrew/opt/libpng/include/libpng16" "-I" "/opt/homebrew/Cellar/graphite2/1.3.14/include" "-I" "/opt/homebrew/Cellar/icu4c/74.2/include" "-Wall" "-Wextra" "-Wall" "-Wall" "-Wdate-time" "-Wendif-labels" "-Wextra" "-Wformat=2" "-Wmissing-declarations" "-Wmissing-include-dirs" "-Wpointer-arith" "-Wredundant-decls" "-Wshadow" "-Wswitch-bool" "-Wundef" "-Wextra-semi" "-Wno-unused-parameter" "-Wno-implicit-fallthrough" "-fno-exceptions" "-fno-rtti" "-DXETEX_MAC=1" "-o" "/Users/captain/texpresso/tectonic/target/release/build/tectonic_xetex_layout-db2d797d0ccb69e2/out/layout/xetex-XeTeXLayoutInterface.o" "-c" "layout/xetex-XeTeXLayoutInterface.cpp" with args "c++" did not execute successfully (status code exit status: 1).
make[1]: *** [tectonic] Error 101
make: *** [texpresso-tonic] Error 2
`
The above error occurs when I make texpresso-tonic

Commit fbb1c477bd5d3ebc87e1e5238b17df166e4a866e should fix the build issue. Please try again.

Commit fbb1c47 should fix the build issue. Please try again.

After your modifications, the command 'make texpresso-tonic' now runs successfully. Thank you very much.
However, I have another problem, if it is a Chinese document, the real-time preview is very very slow. Take the following document for example.
\documentclass[12pt]{article} \usepackage{amsmath} \usepackage{ctex} \begin{document} 您好 \end{document}

I confirm there is an issue with handling of fonts with large character sets on macOS :/.
Sorry, I have an idea about what could be done, but I have no time for a fix in the short term.

The problem is that with your document, the CJK fonts are loaded from the OS and the OS font loader is broken on macOS.
I have had more success by loading xeCJK package:
\documentclass[12pt]{article}
\usepackage{amsmath}
\usepackage{xeCJK}
\begin{document}
您好
\end{document}

This results in a decent experience. Fixing support for OS fonts would be nice but this will take some time. If you want, you can use this workaround in the meantime.

The problem is that with your document, the CJK fonts are loaded from the OS and the OS font loader is broken on macOS. I have had more success by loading xeCJK package:
\documentclass[12pt]{article}
\usepackage{amsmath}
\usepackage{xeCJK}
\begin{document}
您好
\end{document}

This results in a decent experience. Fixing support for OS fonts would be nice but this will take some time. If you want, you can use this workaround in the meantime.

Your scheme is indeed a good choice at present, thank you very much.


Inference on a current version of EFO

Hi @dhimmel @eric-czech
I'm going to work on this ^ today as it's one of the last main tasks needed before the MONDO workshop.
I realized I have a few questions regarding the details of the task:

We need to decide which specific model we'd like to use for the inference. I see 2 main contenders:

"Topological features + Text embeddings PCA64": The best performing model, most Occam's razor compliant. Would probably be my top choice.
"All features (Topological + PCA 64 + LDA + KNN + GPT + Subsets)": Would have data on all features which we can talk about during the workshop, show feature importance, ...

IIRC @dhimmel: You mentioned you'd like a dump of the feature values for all the nodes. Would you like to have these formatted  as:

1 files (e.g. CSV with ID, Label and one column per feature)
2 files (CSV with ID and label and another CSV ID, features columns).
(The 2 files approach might be a little cleaner since there are 80+ features. Also the resulting feature file will likely be a little large and hard to compress (lots of random looking floats) & open in a web browser)

In terms of the labels predicted:

Do we want the 3 classes or the 4 classes variant (including the non-disease label)?
Which labels do we want to output: ["01-disease-subtype", "02-disease-root", "03-disease-area"] or ["low", "medium", "high"]
Also the label output: Do you want only 1 column with the top label or 1 column per label proba + 1 column for the top label

Just to confirm:  This version of the ontology is the one we want to run inference on: "https://github.com/related-sciences/nxontology-data/raw/2ce01d8495024d46cbc54fb0c26a92500ad717e0/efo_otar_slim.json"

Thanks for the help!

This version of the ontology is the one we want to run inference on: "https://github.com/related-sciences/nxontology-data/raw/2ce01d8495024d46cbc54fb0c26a92500ad717e0/efo_otar_slim.json"

That's correct.  That link is for EFO version v3.57.0 which we will be using as well.

We need to decide which specific model we'd like to use for the inference

So the GPT and subset features weren't improving the model!! 🤯

Do we want the 3 classes or the 4 classes variant (including the non-disease label)?

I think we should be calculating non-disease on the version of EFO loaded and include that as a column. Those terms don't receive a prediction.

This version of the ontology is the one we want to run inference on

In general, we want to be using the latest version, but fine to hard code the commit hash for now until we set up a continuous build job on CI to reprocess latest every month.

So the GPT and subset features weren't improving the model!! 🤯

Indeed, it appears that the GPT and subset features don't provide much additional knowledge compared to the text embedding vectors. If you want more insights into how much info is actually contained within the GPT and subset features, I can train and export feature importance for models without the text embedding features.

I think we should be calculating non-disease on the version of EFO loaded and include that as a column. Those terms don't receive a prediction.

Sounds good. Could you provide the node attributes & values that I can use to filter out the non-disease node? 🙏

In general, we want to be using the latest version, but fine to hard code the commit hash for now until we set up a continuous build job on CI to reprocess latest every month.

I see. Running the model in an automated (& remote) fashion will require a little more setup than running it on my machine.

Could you provide the node attributes & values that I can use to filter out the non-disease node?

Based on Eric's private slack message, for each node call the roots method to find all top-level ancestors of that term. If all roots are in the following set of non-disease therapeutic areas (aka roots in EFO OTAR Slim), then its non-disease:
term_label, term_id
animal_disease, EFO:0005932
measurement, EFO:0001444
phenotype, EFO:0000651
biological_process, GO:0008150
medical_procedure, EFO:0002571

Based on Eric's private slack message, for each node call the roots method to find all top-level ancestors of that term. If all roots are in the following set of non-disease therapeutic areas (aka roots in EFO OTAR Slim), then its non-disease:

Thanks for the help!
In order to sanity check my logic:
NON_DISEASE_THERAPEUTIC_AREAS: set[str] = {
    "EFO:0005932",  # animal_disease
    "EFO:0001444",  # measurement
    "EFO:0000651",  # phenotype
    "GO:0008150",  # biological_process
    "EFO:0002571",  # medical_procedure
}

def get_disease_nodes(
    nxo: NXOntology[str] | None = None,
) -> Iterable[NodeInfo[NodeT]]:
    """
    If all roots are in the set of non-disease therapeutic areas (aka roots in EFO OTAR Slim),
        then it is non-disease
    """
    nxo = nxo or get_efo_otar_slim()
    for n in sorted(nxo.graph):
        node = nxo.node_info(n)
        if any(root not in NON_DISEASE_THERAPEUTIC_AREAS for root in node.roots):
            yield node

I compared the count of disease nodes and total nodes in the latest EFO graph vs. in the training set:
Nodes in nxo: 25209
Disease nodes in nxo: 14727
Nodes in training set: 20380
Disease nodes in training set: 14353

So FWIW, it seems that of the nodes that were added in the newer version of the ontology, most of them are non-disease nodes.

Noting the initial classifications in efo_otar_slim_v3.57.0_precisions.tsv.


[ADAM-2037] Support GFF3 files containing FASTA formatted sequences.

Fixes #2037.
Ping @benwbooth for review.

Coverage increased (+0.03%) to 79.157% when pulling a40c3f3b385652c2a3766fd481595733c7595b31 on heuermh:fasta-in-gff3 into cb11b4386febb4a117de3caaf9acceaae170d2d7 on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2816/
Test PASSed.

Merged! Thanks @heuermh!


Member's group icon replaced with viacle's one

When party members enters a vehicle, its party icon/portrait and name changes to the vehicle in question.

Thanks, I really appreciate your reports. Can't promise I'll fix em quick but I'll look into them

and I really appreciate you wanting to fix your code. Cheers man.


Value setting is a chaos

It seems the sum of several bugs has provoked this chaotic behaviour.
https://github.com/user-attachments/assets/70a68302-fa6f-44d4-8caa-d7146561e27f

The issue was just the same as the previous bug. Had forgot that Player Prefs value are saved by Unity and not in my asset data so I had to manually delete the Player Pref when deleting it from the asset data. Easily solved.


Discussion: whether we should merge serving and eventing operators into one repository

As it has been brought during the Serving API meeting today on Jan 29, https://docs.google.com/document/d/1NC4klOdNaU-N-PsKLyXBqDKgNSHtxCDep29Ta2b5FK0, we need a broader discussion of this topic.
Please share your comments down below, regarding which option you would like to pick and why.

Keep serving and eventing operators separated as they are.
Merge serving and eventing operators into one operator, living in one repository.
Abstain.

Remember! Say why from any perspective. Thanks.

During the WG meeting today, I took an AI to write up a feature track for this so we can understand exactly what is being proposed before moving forward; hope to have that completed in the next couple of days.

While I support the merge of the operators - I'd not want the CRs for serving/eventing to merge ...

@pmorie Any update on the feature track?
thanks

Feature track doc is here: https://docs.google.com/document/d/1wT6clZg_zuihtRv4dhOPtxkJTtxodV1Pm00I08KMrjI/edit#heading=h.n8a530nnrb
@k4leung4


Paginate during 'log_group_exists?'

Fixes #48.

This conflicts / completes #45

@ryotarai bump

@ryotarai bump :) Currently running this from a github clone in production, would like to use gem install version again

Also rebased, saw you fixed the core issue in a6e97647171b9e4615d66d4ed57b0f35066f6d83

@ryotarai bump

@ryotarai bump

@ryotarai bump

@ryotarai bump


Eligibility for Commercial Use

Several questions:

The GLM repository has MIT license which is different from the chatGLM-6B repository which prohibits commercial use of the pre-trained models. I am just wondering are the GLM pre-trained models (such as GLM-10B) eligible for commercial use?
ChatGLM-6B seems to be newer than GLM-10B, what's the difference? Which one performs better on Chinese and is there benchmark?

Thanks

Same question about license but seem to be no response for a long time


Feature/services take2

Ok basic fetch and save operations are working now in an browserify-less environment and I've started a TODO app in the dummy app

Feel like progress is moving at a good clip but wanted to check in again with you and make sure you're still wanting to do this in collaboration.

Keen on seeing how you're going to approach the horizon-watch adaptor. Specifically how you'll activate the adapter when "off-world" events happen in the database. I'm still not sure how to avoid using the "bad smelling" approach i started earlier. 😄

Going to bed now but hope to hear from you in the morning.

One last question ... in a 1:M relationship (which exists between people and todo) isn't ED meant to update the other side of the relationship if you have bi-directional relationships defined (aka, ownedBy and hasMany on the two sides).

Ken and Kyle. I've been watching the progress the last few days and just wanted to offer some words of encouragement.
I've been able to get a simple app up and running with this addon (albeit with some hackery...) and I think it will be very nice to use Horizon with Ember.
No real opinions as I am pretty noob. But just wanted to say keep up the good work and thanks!!

@levimoore thanks for kind words

Ok, it's all working in non-real time. I'm going to add real-time in. Having dug pretty deeply into this I feel quite strongly that having separate adapters for "fetch" versus "watch" is the wrong approach. I feel that way because:

90% of the code across adapters is boilerplate reuse
all that "watch" is doing is adding a method to interact with external events
integrating it into one doesn't reduce flexibility, it actually increases it ... allowing the user to choose at a macro level on or off but also to enable/disable at a collection level too

I know that you had initially wanted to do this differently so all future work i'll do off a separate feature branch so you can accept this in but ignore my further approach if you're not ok with it.  That leads me to my final point ... I haven't heard from you in days so I'm not sure where your head is. I assume you've been busy but I kinda need to know how to proceed before I start marketing it to others.
Paths forward as I see it:

If you're happy with the design direction i'm taking then great, nothing changes other than your acceptance of the PR. This is my preferred option.
If you feel the development has moved past you and you'd rather pass the repo to me then I'd accept but it would be much nicer to have a partner in crime.
If you don't like the design direction and still want to take it your own way then I will rename my repo and we can give the community choices

Please let me know. My goal is to have real-time working today and start marketing it Monday.


Not working using basic sample

`import UIKit
import ScratchCardView
class ViewController: UIViewController {
@IBOutlet weak var scratchCardView: ScratchCardView!

override func viewDidLoad() {
    super.viewDidLoad()
    // Do any additional setup after loading the view, typically from a nib.

     configureScratchCardView()

}

private func configureScratchCardView() {
    scratchCardView.delegate = self
    scratchCardView.scratchWidth = 150

}

}
extension ViewController: ScratchCardViewDelegate {
func coverView(for scratchCardView: ScratchCardView) -> UIView {
    let coverView = UIView()
    coverView.backgroundColor = UIColor.gray
    return coverView
}

func contentView(for scratchCardView: ScratchCardView) -> UIView {
    let imageView = UIImageView(image: #imageLiteral(resourceName: "tailor-image"))
    imageView.contentMode = .scaleAspectFill
    return imageView
}

}`
Nothing scratching off.

Hi @talkaboutdesign.
What Xcode version did you use? Did you try the basic example in the project?
There where some problems when using Xcode9 but I pushed some fixes for that. Try release 1.2.0

Works. But changing strokeWidth is not reflected.

@talkaboutdesign the scratch width should be fixed in 1.3.0
Let me know if everything works so I will close the issue.

Thank you. Was wondering about s few more things.
Is there an easy way to clear the mask?
Is there a way to get amount on screen scratched off? Like 40% etc?

@talkaboutdesign the functionality you mentioned does not exist currently but I if you open a feature request I can add them.


[VS Code] Joining collaboration session: The host network are no longer connection due to poor network connection.

Error:
Joining collaboration session: The host's network conditions are poor or they are no longer connected to the Live Share cloud relay. Ask them to check their network conditions, restart the collaboration session, and try again.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.905

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.38.1

platformName
MacOS

platformVersion
18.7.0

@shankar524  Thank you for reporting the issue. Can you tell me more about what you were doing when you encountered this error message? Were you able to rejoin the session? Also, your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

Closing due to inactivity. Please re-open if this you're still encountering the issue and can share more details. Thanks!


chore: enable node v14

Node v14 should be allowed

Related Issue
Motivation and Context
If projects depending on aio-lib-runtime are using node v14.x then npm install will complain with
Not compatible with your version of node/npm:
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Just run into the same issue using Node.js v15.
Is it possible to relax the strict check on Node.js versions to be just "greater than 10" - as otherwise you'll need to manually adding support for each new major version of the platform.

Just run into the same issue using Node.js v15.
Is it possible to relax the strict check on Node.js versions to be just "greater than 10" - as otherwise you'll need to manually adding support for each new major version of the platform.

@visiongeist This looks good, however there is a conflict as .travis.yml was deleted upstream.  Fix this and I will merge it.

@purplecabbage done :)


Is this maintained?

I'm considering adding this as a dependency for hydrodynamics in ros2 gazebo simulations. I see old PR's and issues with little to no activity. Is this repo still maintained or no?

Hi,
It looks that this repo is not maintained. Furthermore, many things from UUV/Plankton on the Gazebo part are now included in Ignition/Gazebo (thrusters, hydrodynamics).
Control-related packages should still be valid, though the input/output may differ with Ignition-based simulation.


fix(config): merge app namespace rather than overriding

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)

Description
Note that app should be a reserved namespace in any case so this may be an abundance of caution.
closes #8991
Checklist:

[x] All new and existing tests are passing.

Reverted by #9075


About groupsampler

My question is about this picture, main is num extra samples.
I think above figure is only for single gpu, not consider gpus.
i.e. having 6 imgs, 2 gpus, samplers per gpu is 2.
As shown in the figure above, do not need extra sample.
But actually, batchsize=2*2, take four images at a time, there are two left, but it's not batch enough.
Did I think wrong?
Thank you!

Hi @zhjw0927
Are you using distributed training or non-distributed training?

under non-distributed training.


Add some tests for StaxXmlParserUtils

This PR simply adds some tests for StaxXmlParserUtils, fixes some minor duplicated logics and code-style.

Current coverage is 89.77%

Merging #90 into master will decrease coverage by -0.05% as of af3017e

@@            master     #90   diff @@
======================================
  Files           14      14
  Stmts          629     626     -3
  Branches        82      82
  Methods          0       0
======================================
- Hit            565     562     -3
  Partial          0       0
  Missed          64      64

Review entire Coverage Diff as of af3017e

Powered by Codecov. Updated on successful CI builds.

Merged.


Distance value for extrude command is not cleared out when user steps back to Selection before submitting

If a user hasn't submitted a value for the the Extrude distance argument and they step back, we should reset the values.

I wish I had included a demo video for what this meant originally because I can't picture the abnormal behavior. Here is a demo of the behavior today, which is working as I would expect: switching back to the Selection argument step clears my in-progress changes to the Distance step.
https://github.com/KittyCAD/modeling-app/assets/23481541/2e76e1c2-7e1f-40ea-a61f-2cbcb6f964de
So I'm going to close this as resolved.


add dns txt format list

adding dns txt format list would allow these rules to be deployed and automatically updated up routers and local dns filtering software.

correction, ips.


Null values break tables

Is there an easy way to get the following working?  I would expect the null values to be represented by blank cells in the table.
<kdb-table>([]x:1 0n 3f)</kdb-table>
Fixing null values would also allow for empty tables to be displayed (after transforming by 1#0#t to get the column names in the json).

Thanks!  The null values now work as expected.
However, the change appears also to be blanking zero values, e.g.,
 <kdb-table>([]x:1 0 3f)</kdb-table>
will have a blank 2nd row rather than displaying 0.
Is there a way to differentiate between null and zero?

Yes, I always forget that JS treats many things as false.
null and 0 - fixed. I think it is not possible to get undefined.


SettingDrawer设置没有缓存到localstorage

Is your feature request related to a problem? Please describe.
SettingDrawer设置没有缓存到localstorage，导致刷新或者重新登录，之前的设置就会重置
Describe the solution you'd like
希望作者能把SettingDrawer的设置缓存到localstorage，那样体验就会好很多
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

你需要自行缓存，因为 settingdrawer 是开发者的行为


ad5940 schematic

Can you please provide schematic of ad5940/41 that you have connected with Adafruit Feather? It would be of great help.

AD5941 GPIO0 connected to A1 (Interrupt Pin)
AD5941 GPIO1 connected to A2
AD5941 GPIO2 connected to A3
AD5941 Reset connected to A4
SPI (CS line connected to A5)
provided in the documentation (hardware section)


runtime: 1.7 hits max user processes earlier than 1.6

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
1.7

What operating system and processor architecture are you using (go env)?
amd64, linux

What did you do?
Rebuilding a program that was fine in 1.6, with:
go install -a

What did you expect to see?
normal compilation

What did you see instead?
failed with:

# sort
runtime: failed to create new OS thread (have 3 already; errno=11)
runtime: may need to increase max user processes (ulimit -u)
fatal error: newosproc

(followed by stack dump and several similar messages.)
environment:
ulimit -u gives 30 (it's not my server and I can't increase it)
setting GOMAXPROCS=1 was a work-around that gave successful compilation.

I think you'll probably have to stick with your workaround. 30 is quite low. It's conceivable you have more processors than that, in which case Go's default GOMAXPROCS would already violate your ulimit.
@ianlancetaylor? @aclements?

4 processors. Is there a limit to the number of user processes the build system is likely to need, or does it just increase with the number of files in the project?

-p=1  will limit the number of concurrent compile jobs
GOMAXPROCS=1 should limit the number of concurrently running goroutines
(including gc workers).
This should reduce the number of threads on, say a 4 processor system, by a
factor of 4^2
On Tue, Aug 16, 2016 at 3:29 PM, Gary Houston<EMAIL_ADDRESS>wrote:

4 processors. Is there a limit to the number of user processes the build
system is likely to need, or does it just increase with the number of files
in the project?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/16713#issuecomment-240004728, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA9Z__odVtgLOA0pJbzkRppEsVN1Xks5qgUqkgaJpZM4Jk8Hh
.

@garyhouston, you say that it hits the limit "earlier" than in 1.6. I'm not at all surprised that it hits a limit of 30, but I'm somewhat surprised that it changed from 1.6 to 1.7. At what point did it fail in 1.6?
It could simply be that 1.7 has a slightly different package graph, which causes it to hit a more concurrent part earlier.
At any rate, I think your workaround (or using -p) is the right answer to an extremely low process limit.

Thanks, I made an unwarranted assumption that it "was fine in 1.6", because I never encountered a problem like this previously. But perhaps I didn't use go install -a in 1.6, or maybe my code has changed in some significant way.
I reinstalled 1.6.3 and tried the same command, and got:
runtime/cgo: pthread_create failed: Resource temporarily unavailable
Today I get the same error in 1.7,  instead of the original error that helpfully pointed out the ulimit issue. A regular install, without -a, after modifying only a few files, doesn't have any problem.

30 threads is not remotely "quite a few" by today's standards. It's not really reasonable for Go to attempt to automatically deal with such a constrained environment. Given that there appear to be two viable workarounds and this is not a regression from early Go versions, I'm going to go ahead and close this issue.