Game crashes as soon as the world loads

As soon as the world loads, the game shows the saving world screen and crashes. I have the latest versions of both Indium as well as the fork of sodium mentioned in the description. I downloaded them from the Actions tab.
Crash Report: Here
File:
crash-2021-03-30_18.28.55-client.txt

Just tried it, works perfectly! Thanks!


update Chinese translation for falco.org/zh home page

Signed-off-by: nevermosby<EMAIL_ADDRESS>
What type of PR is this?
/kind translation
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
This PR provides the Chinese translation for falco.org/zh home page.
Which issue(s) this PR fixes:

This PR is related to #43 .
Special notes for your reviewer:
I extracted the description about falco joins CNCF to a new translation tag, falcoCNCF. Pls check it out.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kris-nova
You can assign the PR to them by writing /assign @kris-nova in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @nevermosby! It looks like this is your first PR to falcosecurity/falco-website 🎉

Hi @fntlnz could u pls help review this pr?

LGTM label has been added.  Git tree hash: 0c2ce32b9167e2110f1fef315345a1ae9f11b0be

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for submitting this! Really appreciated!
To merge this in it needs to be rebased on top of the master

@leodido the content of this or has been included in the pr #157, which has been merged already. So I will close this or. Thank you very much.


Keras LSTM Import Error

Issue Description
Trying to import a Keras LSTM model from a ByteArrayInputStream of an hdf5, but it fails with Unsupported keras layer type RNN. Please file an issue at https://github.com/eclipse/deeplearning4j/issues.
The reason I'm importing from an InputStream and not from a file is because I will be getting the model hdf5 from a remote location in production (a database), so I cannot load it from a file.
(Sample) Code:
import org.deeplearning4j.nn.multilayer.MultiLayerNetwork;
import org.nd4j.linalg.api.ndarray.INDArray;
import org.nd4j.linalg.factory.Nd4j;
import org.deeplearning4j.nn.modelimport.keras.*;
import org.deeplearning4j.nn.modelimport.keras.utils.*;
import org.deeplearning4j.util.ModelSerializer;
import org.deeplearning4j.nn.graph.ComputationGraph;
import org.deeplearning4j.nn.modelimport.keras.exceptions.*;

import java.io.*;
import java.io.FileInputStream;
import java.io.InputStream;
import java.io.ByteArrayInputStream;
import java.nio.file.*;
public class KerasLoader{

    public static void main(String[] args) throws IOException,UnsupportedKerasConfigurationException, InvalidKerasConfigurationException{

        Path path = FileSystems.getDefault().getPath("LSTM.h5");
        byte[] modelByteArray = Files.readAllBytes(path);

        InputStream modelByteStream = new ByteArrayInputStream(modelByteArray);
        MultiLayerNetwork model = KerasModelImport.importKerasSequentialModelAndWeights(modelByteStream);
        System.out.println("done");
    }
}

Version Information

Deeplearning4j version 1.0.0-beta7
Platform information Ubuntu 18.04.4

Additional Information
Where applicable, please also provide:

Full log or exception stack trace (ideally in a Gist: gist.github.com)

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Exception in thread "main" org.deeplearning4j.nn.modelimport.keras.exceptions.UnsupportedKerasConfigurationException: Unsupported keras layer type RNN. Please file an issue at https://github.com/eclipse/deeplearning4j/issues.
	at org.deeplearning4j.nn.modelimport.keras.utils.KerasLayerUtils.getKerasLayerFromConfig(KerasLayerUtils.java:334)
	at org.deeplearning4j.nn.modelimport.keras.KerasModel.prepareLayers(KerasModel.java:218)
	at org.deeplearning4j.nn.modelimport.keras.KerasSequentialModel.<init>(KerasSequentialModel.java:110)
	at org.deeplearning4j.nn.modelimport.keras.KerasSequentialModel.<init>(KerasSequentialModel.java:57)
	at org.deeplearning4j.nn.modelimport.keras.utils.KerasModelBuilder.buildSequential(KerasModelBuilder.java:322)
	at org.deeplearning4j.nn.modelimport.keras.KerasModelImport.importKerasSequentialModelAndWeights(KerasModelImport.java:223)
	at org.deeplearning4j.nn.modelimport.keras.KerasModelImport.importKerasSequentialModelAndWeights(KerasModelImport.java:113)
	at KerasLoader.main(KerasLoader.java:24)

pom.xml file or similar (also in a Gist)

    <properties>
        <scala.binary.version>2.11</scala.binary.version>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
     </properties>
<dependencies>
<dependency>
   <groupId>org.nd4j</groupId>
   <artifactId>nd4j-native</artifactId>
   <version>1.0.0-beta7</version>
   <classifier>linux-x86_64-avx2</classifier>
 </dependency>
 <dependency>
    <groupId>org.deeplearning4j</groupId>
    <artifactId>deeplearning4j-modelimport</artifactId>
    <version>1.0.0-beta7</version>
</dependency>
 <dependency>
    <groupId>org.deeplearning4j</groupId>
    <artifactId>deeplearning4j-core</artifactId>
    <version>1.0.0-beta7</version>
</dependency>
</dependencies>

Update
I tried to read with JSON and H5 just to be sure that wasn't the problem (even though this solution wouldn't work for my situation).
MultiLayerNetwork model = KerasModelImport.importKerasSequentialModelAndWeights("./LSTM.json","./LSTM.h5");
But I received the same error.

Are there any ideas on this issue?

The RNN layer that is included in keras is "SimpleRNN" (see: https://keras.io/api/layers/recurrent_layers/)
I guess the RNN you are seeing in your model is using the RNN(Cell) functionality (see https://keras.io/guides/working_with_rnns/#rnn-layers-and-rnn-cells),
Can you share your model json? That should allow me to tell you more about how you might be able to work around this problem.

@treo Thanks for the reply. I don't have the model JSON anymore (but if need be can recreate it). But the layer I used was the
lstm_layer = tf.keras.layers.RNN(
        tf.keras.layers.LSTMCell(units),
        input_shape=(None, input_dim))

If I understand what you're saying/the docs correctly, I need to change that outer layer with tf.keras.layers.SimpleRNN
Is that correct? Is there a reason why the standard RNN layer isn't supported?
Thanks!

tf.keras.layers.RNN(tf.keras.layers.LSTMCell(units), input_shape=(None, input_dim))

You should replace that with  tf.keras.layers.LSTM(units) instead.

Is there a reason why the standard RNN layer isn't supported?

It isn't the standard in a sense, the docs (https://keras.io/guides/working_with_rnns/) say:

Mathematically, RNN(LSTMCell(10)) produces the same result as LSTM(10). In fact, the implementation of this layer in TF v1.x was just creating the corresponding RNN cell and wrapping it in a RNN layer. However using the built-in GRU and LSTM layers enables the use of CuDNN and you may see better performance.

And https://keras.io/api/layers/ doesn't even mention the RNN(Cell) structure at all.
For this reason, when we import Keras models, we support importing the layers, but not the composites that are based on RNN(Cell).

Got it, thanks for the clarification!


Cleanup Dependencies (Nice to Have)

It would be nice to have the dependencies in package.json cleaned up a little and have the dev-dependencies separate from the runtime dependencies.  This way it's easier to get a better understanding of what all will be included.

Agree that we should do an audit of this. Several of the dependencies that might seem like devDependencies are (currently) dependencies in our case, since our build tools are (currently) required for creating components. It may require a deeper refactor to get this cleaned up properly and make the runtime dependencies a lot more lightweight.


When start typing, cursor start moving arround characters

it's a very good lib.
when i'm typing then cursor start moving arround characters fastly one point to another point. therefore text type not correctly.
example: if typing.. "have"
then cursor start moive arround 'v' and 'e', or 'a' and 'e'. as well as 'space' to 'a'. etc.,
therefor text not writed correclty . haev... this is  typing issue  for any kind of text. cursor not still on it's position after start typing.
plz fix that.. thanks

Did you find any solution for this?

no @ajithv11  .. have you faced this issue??

Yes, I am trying to fix this. It works in the demo application with expo
But not working for my project my react-native version is 0.60.4.
@Waqas-Jani   Are you working on this for fixing the same?

i try it. old version and work fine.. but not latest ..

i'm not using wth expo..

i try it. old version and work fine.. but not latest ..

Which react version have you tred?

react-native 0.60.5.
this lib version 1.0.40.

react-native 0.60.5.
this lib version 1.0.40.

This is your working version ?

no..
this version .working.
react-native-cn-richtext-editor: "1.0.35",

no..
this version .working.
react-native-cn-richtext-editor: "1.0.35",

And your react-native version
For me its not working with react-native-cn-richtext-editor: "1.0.35", and react-native 0.60.5

@Waqas-Jani  Could you please tell the working version of your react-native-cn-richtext-editor  & react-native ?

@Waqas-Jani Could you please tell the working version of your react-native-cn-richtext-editor & react-native ?
working...
"react-native": "^0.59.8",
"react-native-cn-richtext-editor": "^1.0.35",

Hi guys, as in : #70, this issue is related to react-native library version > 0.59.8 and you may follow related issue there.

@imnapo  this issue occure in latest version of this lib

react-native latest version TextInput working ok.

You may specify selection prop also.
I've checked below code with RN v-0.60.5 on android device and its not working there.
import React from 'react';
import { StyleSheet, Text, TextInput, View } from 'react-native';

export default class App extends React.Component {
  constructor(props) {
    super(props);
    this.state = {text: '', selection: {start: 0, end: 0}};
  }

  render() {

    return (
      <View style={styles.container}>
      <Text>Open up App.js to start working on your app!</Text>
      <TextInput
          style={{height: 80, borderWidth: 1}}
          selection={this.state.selection}
          onSelectionChange={(event) => this.setState({selection: event.nativeEvent.selection})}
          placeholder="Type here to translate!"
          onChangeText={(text) => this.setState({text})}
          value={this.state.text}
          />
    </View>
  );
}
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    paddingTop: 20,
    backgroundColor: '#fff',
    alignItems: 'stretch',
    justifyContent: 'center',
  },
});

i also check TextInput "react-native": "0.60.5", and it's work fine

use this code
<CNRichTextEditor
ref={input => this.editor = input}
onSelectedTagChanged={() => this.onSelectedTagChanged}
onSelectedStyleChanged={() => this.onSelectedStyleChanged}
value={this.state.value}
style={{ backgroundColor : '#fff'}}
styleList={defaultStyles}
onValueChanged={() => this.onValueChanged}
/>


Organization of the project with Mayo clinic

In the context of the project with Mayo clinic for the detection of "critical" MS lesions, we received some data today.  The data is in the DICOM format. Following up on this, I have a few questions:

Should we create a specific GitHub repository for this project ? Otherwise, we can integrate it into this existing repo.
The data received today is not the official data for this project (just a sample): should we git-annex it ? If so, what dataset name ?

Tagging @jcohenadad for input

Should we create a specific GitHub repository for this project ? Otherwise, we can integrate it into this existing repo.

Yes, I think we should. I suggest under sct-pipeline organization, given that we will be mostly developing a pipeline. Here you go: https://github.com/sct-pipeline/critical-ms-lesion


--mini cannot be used without internet access

I’d like to use speedtest-cli to test speed between internal servers using Speediest Mini.
However, speedtest-cli tries to retrieve configuration from speedtest.net even for internal Mini tests.
As some of the servers used as client do not have internet access, it fails.
--mini option should be usable without internet access.

Duplicate of https://github.com/sivel/speedtest-cli/pull/182


Added support for lowercase FileFormat for Issue #1340

Modified the FileFormat class so that it utilizes EnumMeta value aliases.
This allows specifying both "AVRO" and "avro" to map to AVRO, for example.
This addresses Issue #1340

thanks for the contribution! do you mind adding a few test cases to validate the new behavior?
in the original issue, the Datafile has to set file_format to uppercase. This would be a good test
https://github.com/apache/iceberg-rust/pull/349/files/a740d28d640543146dc2befbb78461998c469e23#diff-8389535350ef7cddc266dfd18d589a978643da0334c23e16646e62e8d6a0892eR1327-R1337

@hgollakota It looks like there is a formatting issue, could you run make lint? :)


WIP: plausible deniability

🏗

Thank you for the review. Feedback is applied with 863b12d

I'm interested: What does this change do? An emoji is not a very good description…

@Fabian42 : as far as I can interpret the code, a new function for data privacy is introduced. Randomly when opening the app, there is a fake TEK uploading to the server. It is to protect a COVID positive tested user, who uploads his keys to the server to warn the others, while his network traffic is under oberservation (e. g., by a hacker...) By this, he may deny (upon being confronted with 'his network behaviour') that he uploaded keys, because ALL CWA apps now uploading (fake) keys from time. So, network sniffing is not reliable anymore to identify positive tested users.
Dear devs, please correct me if I'm wrong.

@Fabian42 ... sorry, now realized that you most likely don't need any explanation about the code... Your original question had a different intention, I guess... ;)

No, that is actually exactly what I asked about. Thanks!


[Feature request]: Tooltip für Radio Groups

Description
Als Nutzer möchte ich zusätzlich zu den Tooltips in TextInputs und Selects auch ein Tooltip in RadioGroups neben dem Label sehen, damit ich über zusätzliche Informationen zu dem Feld informiert werden kann.
Proposed solution
No response
Confirmations

[X] I have checked that there is not already a feature request for this feature.
[X] I confirm that are no sensitive information included in this feature request. e.g. credentials, internal project details (for employees of the Schwarz Group) etc.

Hello,
thank you for your request! We always want to improve onyx and therefore we are always open to good ideas like yours.
The goal is to find a generic and modular high quality way, to bring useful features like this into the onyx library.
To make sure we find a solution that follows our principle-based onyx strategy, we will elaborate and validate your request.
We will come back to you, when there are more updates on that.
Thank you!


coursier: Fix LD path for libz.so.1

Description of changes
Fix ~/.local/share/coursier/bin/.cs.aux: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.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.

Result of nixpkgs-review pr 261616 run on x86_64-linux 1

4 packages built:

coursier
pre-commit
pre-commit.dist
scala-runners


2.0.3: poll crashes if building is going on

Start building in one terminal
In another run dataserv-client poll

The client starts polling from the right address, but then it crashes.
File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 45, in _url_query
    response = urllib.request.urlopen(req)
  File "/usr/lib/python3.4/urllib/request.py", line 153, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib/python3.4/urllib/request.py", line 461, in open
    response = meth(req, response)
  File "/usr/lib/python3.4/urllib/request.py", line 571, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.4/urllib/request.py", line 499, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.4/urllib/request.py", line 433, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.4/urllib/request.py", line 579, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: NOT FOUND

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/dataserv-client", line 10, in <module>
    cli.main(sys.argv[1:])
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/cli.py", line 153, in main
    return getattr(client, command_name)(**arguments)
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/api.py", line 135, in poll
    self.ping()
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/api.py", line 115, in ping
    self.messenger.ping()
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 110, in ping
    return self._url_query("/api/ping/%s" % self.auth_address())
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 42, in _url_query
    headers = self._create_authentication_headers()
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 77, in _create_authentication_headers
    msg = self._get_node_address() + " " + header_date
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 70, in _get_node_address
    self._server_address = self.address()
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 91, in address
    data = self._url_query("/api/address", authenticate=False)
  File "/usr/local/lib/python3.4/dist-packages/dataserv_client/messaging.py", line 53, in _url_query
    raise exceptions.FarmerNotFound(self._server_url)
dataserv_client.exceptions.FarmerNotFound: Farmer not found at http://status.driveshare.org!

Seems duplicate of https://github.com/Storj/dataserv-client/issues/71


Localization current benefits

Adds text strings for the "Current Benefits" page.

Superseded by #612.

Do we not need the other strings for Current Benefits?

My bad - #612 includes changes for Current Benefits as well.


Promote patch to channel

Fixes #115

Just some ideas to consider.
Easy command
I still wish to have a more straightforward way to apply custom changes to an installation - with a single command. Basically I'm missing the "apply patch" (whatever it is called). It would install the artifacts into the internal installation repo, install or update the channel file, and even perform the server update:
prospero apply <file.zip> -- super simple, no questions raised, and probably good enough for most customers.
Terminology
Regarding the "initialize" / "promote" terminology, what about centering it more around "repository management", keeping it separate from the "channel management"?
Following would be independent of particular installation:
prospero manage-repository install-content --file file.zip --repository-url/path <url/path>
# just brainstorming:
prospero manage-repository list-channels --repository-url <url>
prospero manage-repository list-content --repository-url <url>

And then in an installation:
prospero repository add ...
prospero channel add ...

(The old channel and repository commands seam to me easier to grasp then the initialize :).)
Or perhaps prospero associate-custom-channel --channel <ga> [--repository-url <url>].

Easy command

Yeah I think we can add that

Terminology

I think we should be talking in terms of channels and operations on channels rather than repositories. Maybe the operation should be called something like prospero manage-channels promote

(The old channel and repository commands seam to me easier to grasp then the initialize :).)

The init operation was supposed to simplify the single server set up. I guess if we'd have simple op to combine the setup, promote and update in one we could drop it.

@TomasHofman I'm going to merge this and we can improve on it. There's a few follow up issues here https://github.com/wildfly-extras/prospero/milestone/3 - please add new issues if I missed anything :)


Added issuer icons for CTemplar, Global Rockstar and Kraken.

Solves the following issues:
https://github.com/calleluks/Tofu/issues/90
https://github.com/calleluks/Tofu/issues/85
https://github.com/calleluks/Tofu/issues/79

Solves issue #102 and #103

Also solves #129 (dupe of #79) 🎉


Fix packages that need patchelf

These libraries if pot patchelfed use libraries from the host and may fail if the used libs are missing.
Fixes: https://github.com/ubuntu/microk8s/issues/370
We need to investigate if the rest of the libraries need to be patchelfed: https://github.com/ubuntu/microk8s/issues/371

Merging this to get new snaps.


What even IS eo3?  Fork proposal

an EO3 document is a document that:
a) conforms with the (undocumented) metadata conventions established by eo-datasets; and
b) conforms to datacube-core's (undocumented) assumptions about the structure of eo3 dataset docs.
These are not always in agreement (i.e. datacube-core stores lineage internally in a different format to that output by eo-datasets.)
I propose splitting eo-datasets into two repositories:

A new opendatacube/eo3 repository which defines, documents, validates, serialises and deserialises the attributes and properties of an EO3 document that are assumed internally by core and therefore need formal and strict definition;
Leaving eo-datasets to define, document, and validate the metadata catalog for various collections and packaging conventions, and handle normalising and writing out according to various packaging conventions.  These collections and packaging conventions can vary and diverge as required.

This split will facilitate:
a. Allow better sharing of code between (what is now) eo-datasets and core, e.g. as requested in #294.
b. Facilitate future extensions and updates to what core uses.  e.g. CSIRO are looking into contributing ODC support for loading into multidimensional xarrays (e.g. for hyperspectral or climate modelling use cases)

Whilst we are doing this suggest we look at some aspects of consistency with STAC

Whilst we are doing this suggest we look at some aspects of consistency with STAC

Leaving eo-datasets to define, document, and validate the metadata catalog for various collections and packaging conventions, and handle normalising and writing out according to various packaging conventions.

https://odc-stac.readthedocs.io/en/latest/stac-vs-odc.html
About stac

There's also some metadata differences which I believe Rob encountered recently - e.g. STAC allows list of instruments, ODC flattens this list into a single comma-separated instrument value.

Also ODC needs the product id and metadata id to do its references internally. Some other mostly minor but prohibitive tweaks. @Kirill888 I was looking at doing a PR into odc-stac eo3 but became uncertain after I found more minor differences, wasn't sure what "correct" was. I think this piece of work @SpacemanPaul is proposing with this issue will sort my end and I can work on a PR for odc-stac eo3 for ODC conversion to tidy this up.
FYI, I used odc-stac in this context because it handled stac extensions for projection nicely which resolved my metadata issue and because I think it's a good path forward in this space.

@woodcockr, my understanding is that eo-datasets is all about data generation, both rasters and the accompanying metadata in "eo3 convention". There is actually very little overlap with odc-stac, I just linked that piece of documentation in response to your comment about stac vs odc comment.
As far as "what eo3 is" question? Would be good to have that properly defined, as I'm sure it has changed a lot over time. From "historical" context, "eo3" was all about capturing the following information about the underlying rasters

Precise pixel shape and geo-referencing for all bands of a dataset
Raster properties: dtype,  nodata
De-duplication of duplicated geo-referencing information that is present in eo

Information that was missing in "eo" and that was required for more "automatic" data loading behaviours in dc.load.
The equivalent STAC extensions are Projection (proposed by GA based on eo3) and Raster.

Work is underway: https://github.com/opendatacube/eo3


Whether or not support sort filter operation by sql

Is your feature request related to a problem? Please describe.
Whether or not support sort filter operation by sql?
for example：

put data to es index：
PUT /my_index/blogpost/2 { "title": "Investment secrets", "body":  "What they don't tell you ...", "tags":  [ "shares", "equities" ], "comments": [  {    "name":    "Mary Brown",    "comment": "Lies, lies, lies",    "age":     42,    "stars":   1,    "date":    "2014-10-18"  },  {    "name":    "John Smith",    "comment": "You're making it up!",    "age":     28,    "stars":   2,    "date":    "2014-10-16"  } ] }
dsl expression
GET /_search { "query": {  "nested": {     "path": "comments",    "filter": {      "range": {        "comments.date": {          "gte": "2014-10-01",          "lt":  "2014-11-01"        }      }    }  } }, "sort": {  "comments.stars": {     "order": "asc",       "mode":  "min",       "nested_filter": {       "range": {        "comments.date": {          "gte": "2014-10-01",          "lt":  "2014-11-01"        }      }    }  } } }

Describe the solution you'd like
so, how to do resolve it by sql?
up to now , can not  find any relevant information?
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.

@chloe-zh

Hi @smallAttr unfortunately we have not supported nested fields in sql new engine yet, so the new engine is not able to execute queries like your example. But I'm not sure if old engine supports it or not, I will try it out later and respond here.
Besides, for sort and filter for plain fields, you can try ，order by for sort and where for filter.


Oracle DB image build failed due to missing orainstRoot.sh

I've checked out the master branch and I was trying to build Oracle DB image.
These are the script parameters I've used:

./buildDockerImage.sh -v <IP_ADDRESS> -e -i > output5.txt

These are the logs:
output5.txt
Just for the record, previously I came across docker storage default dedicated space issue, but I increased it to 25GB.
This is my docker deamon status:
`● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Mit 2016-12-28 15:22:00 CET; 1h 28min ago
Docs: https://docs.docker.com
Main PID: 20430 (dockerd)
Tasks: 26
Memory: 4.6G
CPU: 8min 3.942s
CGroup: /system.slice/docker.service
├─20430 /usr/bin/dockerd -H fd:// --storage-opt dm.basesize=25G --storage-driver=overlay --dns <IP_ADDRESS> --dns <IP_ADDRESS> --dns <IP_ADDRESS>
└─20446 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime docker-runc
Dez 28 16:09:09 georgige1 dockerd[20430]: time="2016-12-28T16:09:09.098074247+01:00" level=i
Dez 28 16:09:09 georgige1 dockerd[20430]: time="2016-12-28T16:09:09.851468739+01:00" level=i
Dez 28 16:09:10 georgige1 dockerd[20430]: time="2016-12-28T16:09:10.616971799+01:00" level=i
Dez 28 16:11:48 georgige1 dockerd[20430]: time="2016-12-28T16:11:48.318450590+01:00" level=i
Dez 28 16:15:16 georgige1 dockerd[20430]: time="2016-12-28T16:15:16.901957791+01:00" level=i
Dez 28 16:39:16 georgige1 dockerd[20430]: time="2016-12-28T16:39:16.274297492+01:00" level=i
Dez 28 16:39:17 georgige1 dockerd[20430]: time="2016-12-28T16:39:17.098070217+01:00" level=i
Dez 28 16:39:17 georgige1 dockerd[20430]: time="2016-12-28T16:39:17.891793290+01:00" level=i
Dez 28 16:41:38 georgige1 dockerd[20430]: time="2016-12-28T16:41:38.858238245+01:00" level=i
Dez 28 16:45:04 georgige1 dockerd[20430]: time="2016-12-28T16:45:04.037821707+01:00" level`
I think I tried everything I could think of and I can't figure it out.
Please help!

I don't know what happened, but when I deleted my /var/lib/docker and restarted the machine, it worked.... it remains a mystery. Anyway, it works so it doesn't really matter.


Issue854: ncontrol containers should be removed with network tap removal

Codecov Report

Merging #864 into master will decrease coverage by 0.12%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master     #864      +/-   ##
==========================================
- Coverage   77.02%   76.89%   -0.13%
==========================================
  Files          52       52
  Lines        5497     5502       +5
==========================================
- Hits         4234     4231       -3
- Misses       1263     1271       +8

Impacted Files
Coverage Δ

vent/core/network_tap/ncontrol/ncontrol.py
85.71% <ø> (ø)
:arrow_up:

vent/api/actions.py
76.25% <60%> (-0.1%)
:arrow_down:

vent/api/plugins.py
81.32% <0%> (-1.17%)
: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 c7d4316...4504e75. Read the comment docs.


Validate input sample rate for decoding is a valid value as per opus documentation

Fixes https://github.com/vector-im/swift-ogg/issues/4
The existing code blindly accepted the sample rate in the opus file header(if it was within a specific range).
However as per the opus documentation:

Sampling rate to decode at (in Hz). This must be one of 8000, 12000, 16000, 24000, or 48000.

To fix the issue I have:

Fixed the incorrectly handled optional that was causing a crash before we could read the status error from the attempt to create the decoder. We now throw OpusError.badArgument error if the decoder is nil.
Rather than accepting the sample rate in the header, we now choose the closest valid sample rate to that defined in the header(For example in the bug reported the file had an input sample rate of 44100, this now gets mapped to a valid sample rate of 48000).
Added a test to verify opus files with invalid sample rates are handled correctly.

@pixlwave It' doesn't fix the problem for https://github.com/vector-im/element-ios/issues/6603. I tried to fix that also, but haven't been able to so far.

Not to worry, fixing the crash is the important one 🙌


refactor: rename separators_len to separator_lengths

#404
#403  👈
master

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

Join @rphmeier and the rest of your teammates on  Graphite

Merge activity

Sep 9, 7:34 AM EDT: @pepyakin started a stack merge that includes this pull request via Graphite.


tsconfig parsing breaks if you include any comments

If you use any kind of comments, the tsconfig parser will break.
{
    "compilerOptions": {
        /* Paths */  <--- "Unexpected token /*"
        "rootDir": "src"
        "outDir": "./.tmp/build/"
    }
}

tsconfig is a JSON file. It's not possible to add comments in JSONs


Adding microsoft planetary access to radar water detection notebook

Proposed changes
There is limited gamma0 backscatter data available in the DEA datacube. This change adds a section at the bottom of the notebook showing users how to access global datasets through the microsoft planetary computer.
Checklist
(Replace [ ] with [x] to check off)

[x] Notebook created using the DEA-notebooks template
[x] Remove any unused Python packages from Load packages
[x] Remove any unused/empty code cells
[x] Remove any guidance cells (e.g. General advice)
[x Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[x] Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
[x] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
[X] Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed) [x] Sandbox [] NCI
[x] If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with
[x] Check for any spelling mistakes using the DEA Sandbox's built-in spellchecker (double click on markdown cells then right-click on pink highlighted words). For example:

Other changes not incorporated, new PR will be raised


error during conversion

hi all,
it happens this after a while with a 32G pst file:
Unknown message type: REPORT.IPM.Note.NDR
Unknown message type: REPORT.IPM.Note.NDR
java.lang.NullPointerException
        at com.pff.PSTAttachment.getFileInputStream(PSTAttachment.java:123)
        at pt.cjmach.pstconv.PstConverter.getAttachmentBytes(PstConverter.java:484)
        at pt.cjmach.pstconv.PstConverter.convertAttachments(PstConverter.java:444)
        at pt.cjmach.pstconv.PstConverter.convertToMimeMessage(PstConverter.java:349)
        at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:269)
        at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:320)
        at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:320)
        at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:231)
        at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:191)
        at pt.cjmach.pstconv.Launcher.call(Launcher.java:89)
        at pt.cjmach.pstconv.Launcher.call(Launcher.java:35)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
        at picocli.CommandLine.access$1500(CommandLine.java:148)
        at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
        at picocli.CommandLine.execute(CommandLine.java:2174)
        at pt.cjmach.pstconv.Launcher.main(Launcher.java:104)

I'm on win11
any ideas?

Same issue me too. Tried latest snapshot and v0.9.8.
Mine is a 51GB OST file.
java.lang.NullPointerException
	at com.pff.PSTAttachment.getFileInputStream(PSTAttachment.java:123)
	at pt.cjmach.pstconv.PstConverter.getAttachmentBytes(PstConverter.java:484)
	at pt.cjmach.pstconv.PstConverter.convertAttachments(PstConverter.java:444)
	at pt.cjmach.pstconv.PstConverter.convertToMimeMessage(PstConverter.java:349)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:269)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:320)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:320)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:320)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:231)
	at pt.cjmach.pstconv.PstConverter.convert(PstConverter.java:191)
	at pt.cjmach.pstconv.Launcher.call(Launcher.java:89)
	at pt.cjmach.pstconv.Launcher.call(Launcher.java:35)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
	at picocli.CommandLine.execute(CommandLine.java:2174)
	at pt.cjmach.pstconv.Launcher.main(Launcher.java:104)

I confirm that the PST is greater of 32GB. this could be the point. let's try with this I'm not so confident with java so I'll wait your fix :).
thanks

Yep, let’s try it!Thx,G.Il giorno 31 ott 2024, alle ore 02:14, C. Machado Antunes @.***> ha scritto:
Thanks for reporting the issue.
The exception comes from a class belonging to java-libpst library.
What I could see in java-libpst source code (https://github.com/rjohnsondev/java-libpst/blob/master/src/main/java/com/pff/PSTAttachment.java#L123) is that the exception is caused when accessing an item contained in a HashTable defined in parent class PSTObject (https://github.com/rjohnsondev/java-libpst/blob/master/src/main/java/com/pff/PSTObject.java#L123).
The HashTable uses Integers as keys and there are also some casts from long to int when populating that HashTable (https://github.com/rjohnsondev/java-libpst/blob/master/src/main/java/com/pff/PSTTableBC.java#L80).
As you may understand, I'm not the developer of java-libpst library, but I guess there might be some limitation when converting files that are greater than 32 GB in size, and, to be honest, I didn't test pstconv with files that big.
For now, the only solution I can think of is to catch the NullPointerException, report a message to the console and continue with processing the remaining messages. Would this be an acceptable solution for you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Managed to get a PST file with around 39 GB but could not reproduce this issue. For the record, I merged together a bunch of PST files with the Outlook import wizard until it reached that size.
Nevertheless, I pushed the fix that protects against NullPointerException's  and should allow to extract further messages if all goes well.
I'm going to publish a new release (0.9.9) in the meantime and would really appreciate if you could test it with your own PST files.
Thank you!

I can confirm that v. 0.9.9 is working fine!
thanks


Image zoom modal is broken.

The blog used to allow you to click on any image to open a modal of the image in order to zoom / pan around. Clicking on an image no longer opens a modal.
The functionality should match that of the docs site. E.g. click the image on this page.

After a quick glance out of curiosity: the error thrown in the console seems to be that error is undefined on this line in the zoom modal plugin. Didn't dig into why.


Is there a sample app for Matter Thread ?

I'm looking for an app equivalent to GHSAFM allowing commissioningof  Matter Thread devices (possibly via a border router such as Google Nest).
Any suggestion please ?

We don't have an equivalent of GHSAFM for showcasing the Thread Network SDK for Android (https://developers.home.google.com/thread).
However, please note that GHSAFM can be used to commission Matter-enabled Thread devices.

Do you mean it's possible to control a Matter-enabled Thread device from a custom android app without a border router or Google Nest ?
How could this be possible since smartphones don't support Thread natively ?

You definitely need a thread border router for this to work.
For example, with a Nest Hub and a Thread Matter device, I can commission the thread matter device and control it with the sample app.

I have a Matter enabled Thread device from Telink and a Google Nest.
I'm trying to commission the Matter device with the sample app, but the app says 'Can't find device".
Any idea why please ?
Here are the logs captured after scanning the device's QR code.
logs.txt

From the logs, I can see that commissioning was initiated by the app:
01-18 17:51:46.119 20317 20317 D GHSAFM-HomeFragment: CommissionDevice: Launch GPS activity to commission device

However, the app never gets control back from the commissioning activity that was launched.
We can see why here:
01-18 17:52:55.884 17388 17388 I MatterCommissioner: No matching devices discovered. [CONTEXT service_id=336 ]
01-18 17:52:55.887 17388 17439 I BleScanner: Stopping BLE scanning [CONTEXT service_id=336 ]
01-18 17:52:55.887 17388 17437 I MdnsScanner: Stopping mDNS discovery. [CONTEXT service_id=336 ]
01-18 17:52:55.887 17388 17439 D BluetoothAdapter: isLeEnabled(): ON
01-18 17:52:55.888 17388 19705 I BleConnectorImpl: Bluetooth scan was cancelled [CONTEXT service_id=336 ]
01-18 17:52:55.890  2632  3398 D ActivityAttributionService: notifyActivityAttributionInfo UID=1002 packageName=com.android.bluetooth deviceAddress=no_active_device_address
01-18 17:52:55.890  2632  3398 I bt_btif : packages/modules/Bluetooth/system/btif/src/bluetooth.cc:471 get_profile_interface: get_profile_interface: id = activity_attribution
01-18 17:52:55.890  2632  2952 I bt_stack: [INFO:le_scanning_manager.cc(172)] ScanFilterParamSetup in shim layer
01-18 17:52:55.893  2632  3398 I bt_stack: [INFO:le_scanning_manager.cc(146)] Unregister in shim layer, scanner_id:9
01-18 17:52:55.894  2632  2952 I bt_stack: [INFO:le_scanning_manager.cc(152)] Scan in shim layer stopped
01-18 17:52:55.894  2632  2952 I bt_stack: [INFO:le_scanning_manager.cc(248)] SetScanParameters in shim layer
01-18 17:52:55.894  2632  2952 I bt_stack: [INFO:le_scanning_manager.cc(152)] Scan in shim layer started
01-18 17:52:55.896  2632  2963 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:653 stop_scan: Scanning already stopped, return!
01-18 17:52:55.896  2632  2963 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_scanning_manager.cc:653 stop_scan: Scanning already stopped, return!
01-18 17:52:55.899 17388 17388 E SetupDeviceViewModel: Commissioning failed with state Failed to discover commissionable device. [CONTEXT service_id=336 ]

Maybe there's an issue with the device advertising itself properly?
If you build the sample app from master, there is a new Developer Utility to discover commissionable devices. It would be good to  see if the device shows up.
I'll try to release 1.3.0 by end of week if you just want to use the new APK that will then be available.

V1.3.0 has just been released.
See https://github.com/google-home/sample-app-for-matter-android/releases/tag/v1.3.0.
Please use that APK and verify that the device does show up in the discovered commissionable Matter devices.
Settings > Developer utilities > Commisionable devices

Thanks Pierre. After updating my repo, I'm able see my Telink device in the new "Commissionable Devices" screen. Its MAC address is CE:9F:DF:E3:13:76
However, installing this device in the sample app still fails. Here are the logs from the app:
logs.txt
and the log from Telink devKit:
logs from Telink Thread devKit.txt
Hope this helps

Looking at the phone logs:
01-23 17:35:04.687 20605 20605 D GHSAFM-HomeFragment: CommissionDevice: Launch GPS activity to commission device
...
01-23 17:35:32.864 27124 27124 I MatterCommissioner: Connected to Thread network. [CONTEXT service_id=336 ]
...
01-23 17:35:32.876 27124 27124 I MatterCommissioner: Establishing a CASE connection. (1 of 3) [CONTEXT service_id=336 ]
...
01-23 17:35:47.956 27124 27124 W MatterCommissioner: Failed to establish CASE connection; retrying (1 of 3) in 1,000 ms. [CONTEXT service_id=336 ]
01-23 17:35:47.956 27124 27124 W MatterCommissioner: m.eiu: Failed to resolve pointer for device A23F2BB89ECBF0F6
01-23 17:35:47.956 27124 27124 W MatterCommissioner: 	at m.efs.onConnectionFailure(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):3)
01-23 17:35:47.956 27124 27124 W MatterCommissioner: Caused by: chip.devicecontroller.ChipDeviceControllerException: third_party/connectedhomeip/next/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout
...
01-23 17:35:48.961 27124 27124 I MatterCommissioner: Establishing a CASE connection. (2 of 3) [CONTEXT service_id=336 ]
...
01-23 17:35:50.157 27124 27124 W MatterCommissioner: Failed to establish CASE connection; retrying (2 of 3) in 2,000 ms. [CONTEXT service_id=336 ]
01-23 17:35:50.157 27124 27124 W MatterCommissioner: m.eiu: Failed to resolve pointer for device A23F2BB89ECBF0F6
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.efs.onConnectionFailure(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):3)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at chip.platform.ChipMdnsCallbackImpl.handleServiceResolve(Native Method)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.evv.j(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):7)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.evv.b(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):6)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.ngq.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):4)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.nvx.bq(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):0)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.nlp.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):4)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.ngq.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):8)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.nno.run(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):8)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.dpc.c(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):6)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at m.dpc.run(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):7)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at aajd.run(:com.google.android.gms<EMAIL_ADDRESS>(150400-499278674):0)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: 	at java.lang.Thread.run(Thread.java:923)
01-23 17:35:50.157 27124 27124 W MatterCommissioner: Caused by: chip.devicecontroller.ChipDeviceControllerException: third_party/connectedhomeip/next/src/inet/UDPEndPointImplSockets.cpp:409: OS Error 0x02000065: Network is unreachable
...
01-23 17:35:53.434 27124 27124 E MatterCommissioner: Giving up CASE connection after 3 attempts. [CONTEXT service_id=336 ]
01-23 17:35:53.434 27124 27124 E MatterCommissioner: m.eiu: Failed to resolve pointer for device A23F2BB89ECBF0F6
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.efs.onConnectionFailure(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):3)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at chip.platform.ChipMdnsCallbackImpl.handleServiceResolve(Native Method)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.evv.j(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):7)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.evv.b(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):6)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.ngq.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):4)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.nvx.bq(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):0)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.nlp.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):4)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.ngq.f(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):8)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.nno.run(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):8)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.dpc.c(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):6)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at m.dpc.run(:com.google.android.gms.optional_home<EMAIL_ADDRESS>(100400-0):7)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at aajd.run(:com.google.android.gms<EMAIL_ADDRESS>(150400-499278674):0)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	at java.lang.Thread.run(Thread.java:923)
01-23 17:35:53.434 27124 27124 E MatterCommissioner: Caused by: chip.devicecontroller.ChipDeviceControllerException: third_party/connectedhomeip/next/src/inet/UDPEndPointImplSockets.cpp:409: OS Error 0x02000065: Network is unreachable
01-23 17:35:53.434 27124 27124 E MatterCommissioner: 	... 14 more
01-23 17:35:53.435  1108  1558 E surfaceflinger: [frame_perf] perfboost open boost file failed
01-23 17:35:53.437 27124 27124 I MatterCommissioner: Disarming failsafe. [CONTEXT service_id=336 ]

So the MatterCommissioner in GPS fails to setup a CASE connection with the device.
What would help is if your device logs had a timestamp to be able to sync the two logs and try to understand why the CASE session cannot be established with the device.
But TBH, at this point I would suggest filing an issue with those logs to the Telink team, they'd know best what's happening on the device side.


Popup css missing?

did you remove the previous css ?

You need to run bash build.sh to download some resources, before loading upacked. But if developer mode disabled, i am getting the following error.

It seems there is no way to avoid this than publishing to chrome web store.

yes. we can work in developer mode only till then.


Reordering keypresses for Ergodox Infinity firmware

After upgrading to Sierra and starting to use Karabiner-Elements (KE) as a replacement for Karabiner, I noticed that the macros on my Ergodox Inifinity stopped firing consistently. I first filed an issue over there and through some digging, it was determined that KE was reordering the keypresses and it appeared to be sending CTRL 5 instead of SHIFT 5. Check out the thread and let me know if you need help testing a fix since it's more likely that you don't have an Ergodox Infinity as well.

Karabiner-Elements uses IOHIDQueueRegisterValueAvailableCallback to get hid events.
Does the IOHIDQueueRegisterValueAvailableCallback get your devices event properly?
An example of confirmation:
There is an example program of IOHIDQueueRegisterValueAvailableCallback.
https://github.com/tekezo/Karabiner-Elements/tree/master/appendix/dump_hid_value
Checkout Karabiner-Elements source tree and build it.
https://github.com/tekezo/Karabiner-Elements/#how-to-build
Then
$ cd appendix/dump_hid_value
$ make
$ make run

Open EventViewer and type keys on your device, the HID values will be output in Terminal.
They are the result of IOHIDQueueRegisterValueAvailableCallback.

Check out @gibfahn's comment on the issue I referenced in the description. It sounds like he already inspected what is being sent. It looks like it's receiving CTRL instead of SHIFT.
https://github.com/kiibohd/KiiConf/issues/63#issuecomment-257102499

I cannot reproduce this issue without device.
Thus I cannot distinguish whether it is IOKit issue or Karabiner-Elements issue.

@tekezo Was what @gibfahn did not enough to act on? I'll take a look at observing the behavior and documenting the output tomorrow night and report back.

Karabiner-Elements does not reordering the input events at least in the source code level.
So, I guess this issue is depending on macOS (IOKIt) specification of handling input events.
(For example, IOHIDQueue might reorder input events unless the enough interval between events.)
We have to know the detail of event handling in IOKit in such devices.
But I don't have devices which can reproduce this issue, so I need to your help to know the IOKit behavior.

Completely fair, thanks for the response. I'll build and let you know what I find. I'd love to get this resolved so I can continue using KE.
Thanks for all the work on this project. Looking forward to seeing it progress.

I've gotten such a device and fixed this issue at the latest version (v0.90.73)

👍👍👍 This is great news! I had just resigned to not being able to use KE for my keyboard. I'll have to dive back into the project and see how things are going. Thanks for all the work you do on Karabiner and now Karabiner Elements!


Chore: Update to Angular 13 - Try #2

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

Angular 13 has been released and we should update.
 I decided to start freshly as the original PR of @krusche ( #4245 ) made a lot of problems on my machine (although I think I could have fixed it by what I learned during the creation of this PR, but well, now we're here).
Additionally, about 131 client tests failed after the update, which this PR does fix as well.
Steps for Testing
This PR needs extensive testing in a testing session of literally all UI features. Although all tests pass, some of them had to be changed. Especially, we should review all component usages of which the tests have been changed, and all date picker and code editor usages need to be manually verified as they made a lot of problems during the upgrade as they are extremely old and outdated and are not even compatible with Angular 9. We should figure out if we can replace these two dependencies in the future as they are abandoned and unmaintained since years.
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

This is currently blocked due to
https://github.com/ng-bootstrap/ng-bootstrap/issues/4178
more specifically this fix https://github.com/ng-bootstrap/ng-bootstrap/pull/4185
as we can't run tests without that being fixed
v12 is not an option as it bumps bootstrap to v5 (breaking; additionally blocked by ngx-treeview depending on v4)
Modules with incompatible / outdated deps:
Not yet ready for angular 13, but will (hopefully) be soon:
ngx-charts
ngx-datatable
@danielmoncada/angular-datetime-picker
ng2-charts
Abandoned / archived deps, will probably not be updated):
awesome-typescript-loader
cache-loader (deprecated, advises update to webpack 5)
ng-starrating
ng2-ace-editor (we might just maintain this ourselves)
ng2-dnd
ng2-material-dropdown
ngx-treeview
angular-fittext

I removed cache-loader recently, because it was not used any more.
I integrated ng2-ace-editor in #4441
ng2-material-dropdown is a dependency of ngx-chips which was recently updated to 3.0.0. There are no release notes, but the commits indicate support for Angular 13

danielmoncada/angular-datetime-picker has been updated to v13 and I added it to the PR.
I think we don't need to wait for the other libraries since it seems they aren't really moving.
I'll schedule this PR for testing in the testing session on Thursday

I suggest we integrate the code editor library changes of my other PR first before testing this one

I'll merge it into this PR before we test it in case it's not yet merged, so we can test both at once (or rather, the combination of both) and see if anything breaks


[Removal]:

Hotspot Name
Micro Strawberry Moose
Hotspot b58 Address
1123XwWDr8tUDQrXg16W7SB6Hsmp8a4xtAm3DoqmE2ZQsebJ9G4Z
Discord Handle
No response
Hotspot Manufacturer
Sensecap
Removal Reason
Hello, it's a real deploy. Could you please remove it from denylist? Thank you in advance. Regards
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Hello, it's a real deploy. could you please remove it from dennylist? Thanks

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


hiera source for certificate

I like this idea, but rather than making the source hiera specific, it might work better to set the source to something like string, then add a new parameter for the actual certificate.
We probably should have tests around this too.

Any thoughts on the approach in the text_source branch?
Hopefully the ca_text parameter will cover your use case and possibly others. I'll probably bump the version to 1.0 and make a release if this works for you.

Hi,
Yes I thought about something like this too, but I didn't want to bring too much changes to your code.
This will work for me :)

I merged the ca_text approach in 46d22f80. New version is up on the forge as well.


Call from file blueprint

Hey there,
maybe I'm missing something, but how would I access a file when placing janitor button inside a file blueprint?
Thank you very much!
S1S

it was not possible before but now it is.
https://github.com/bnomei/kirby3-janitor/wiki/HowTo:-with-File-Blueprints

Aren't you the best! THX!


Notification history have not useful sort

current sort of Notification history from oldest to newer.
imo, sort from newer to oldest will be more useful

Done


Tenants uses Central DB

Bug description
I just installed the package on a fresh Laravel application. But, when I try to dump the users in the tenant routes file. I get an error.

P.S: I am using Laravel Herd to setup the domain to the development environment.
Also, I am wondering why I run into the same error on the central domain. Shouldn't it be scoped to tenants subdomains?
Steps to reproduce
Freshly install the package on a brand new Laravel project and follow the documentation steps on https://tenancyforlaravel.com/docs/v3/quickstart
Expected behavior
It should dump the users for each tenant.
Laravel version
10.16.1
stancl/tenancy version
3.7.0

Hey!
Thanks for opening the issue. This doesn't seem to be a bug in package, seems to be related to your setup.
If you need quick support, you can visit our Discord community here: https://archte.ch/discord
Thanks


I get the error "server.createRoom() ERROR InvalidStateError: Channel closed"

hello,i want your help:
I run the command npm start on my laptop ,it work well!
but when I run on the remote server , it's have some Error:
here is the log
Web server start. http://localhost:3000/
server.createRoom() ERROR InvalidStateError: Channel closed
    at Object.close (/root/Projects/webrtcTest/mediasoup_sample/node_modules/mediasoup/lib/Channel.js:246:14)
    at Channel.close (/root/Projects/webrtcTest/mediasoup_sample/node_modules/mediasoup/lib/Channel.js:169:9)
    at Worker.close (/root/Projects/webrtcTest/mediasoup_sample/node_modules/mediasoup/lib/Worker.js:134:17)
    at ChildProcess.Worker._child.on (/root/Projects/webrtcTest/mediasoup_sample/node_modules/mediasoup/lib/Worker.js:103:9)
    at emitOne (events.js:116:13)
    at ChildProcess.emit (events.js:211:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:196:12)
    at onErrorNT (internal/child_process.js:372:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Thanks for your interest.
Sorry, I do not know what is happening in your server.

I am afraid that you are using mediasoup V2.
Please try another example by footniko.
https://github.com/footniko/mediasoup-sample

For mediasoup v2, please try https://github.com/mganeko/mediasoup_sample_v2


Add Tokens for Import and Export Names in JS? (Local, Import and Export Names)

Information

Language: JavaScript
Plugins: I tried with JS-Extras too

Does the problem still occur in the latest version of Prism? Yes
Description
Would it be possible to add tokens for the import and export names in JavaScript? (see patterns below taken from the import examples and export examples in the ECMAScript spec)
See below - currently they are not receiving any tokenization. To be clear, I'm referring to the local names, import names and export names with names such as v, x, v2 and ns:

I also tried using the js-extras language as follows, but that didn't seem to help:
https://codesandbox.io/s/prismjs-forked-wu91d
Code snippet

The code being highlighted incorrectly.
import v from "mod";
import {x as v2} from "mod";
import * as ns from "mod";

export * as ns from "mod";
export {v as x} from "mod";
export {x} from "mod";
export {v as x};
export {x};

What's the use case for this?
Also, we usually highlight concepts, so what is the general idea here?
Syntax-wise, from the imports you want all identifiers (e.g. import { x as y } from "mod" both x and y) and from exports, you want the same, so no export declarations (e.g. export const foo;, export default function foo(){}, and export class Foo {}), right?

Use case is being able to be more specific about import names for themes like this:
https://github.com/PrismJS/prism-themes/pull/103

Also, we usually highlight concepts, so what is the general idea here?

Right ok, I suppose the overarching concept is actually "all identifiers". In addition to the variables in the original post, I would think that a, b, and foo would receive tokens eg. .token.identifier or something:

As for a concrete use case about that (also irrespective of the import and export rules), the VS Code dark theme currently has a mismatch between the identifier colors here:

Maybe for import and export names they could be subclassed as .token.import .token.identifier or .token.identifier.import-identifier or similar, in case the styling changes between import identifiers and regular identifiers in a theme.

If it makes sense, I can change this issue to be about "identifiers" in general.

I suppose another consideration about assigning tokens to identifiers is if it's possible + feasible to handle the other locations where an identifier is used (eg. c, d, e, f, g, h):

[...] the VS Code dark theme currently has a mismatch between the identifier colors here:

Maybe a bit on how VSC highlights variables in JS/TS. VSC uses the TS language server to parse and analyze JS and TS files (among other things). A while ago they introduced sematic highlighting. This means, that variables are not highlighted by syntax alone but with a deeper understanding of the type and other properties of the variable (powered by the TS language server).
This is why VSC can highlight bar as a function even though, syntactically speaking, it's just another variable.

VSC can do this not only for the type of a variable (class/function/other) but also for its mutability. Readonly variables/properties will be highlighted with a darker shade of blue:

This is incredibly useful because it gives a lot of information to the developer that is not obvious from syntax alone.
However, that's the problem for us. We need more information than just syntax to handle the nested properties correctly. For flat variables, syntax alone is technically enough, but...

if it's possible + feasible to handle the other locations where an identifier is used [...].

No. Tracking variables requires an understanding of scope. This is hard enough with an AST but we only have a token stream to work with. This is one of the things that Prism simply can't do.

Right yeah, I understand that we won't get to 100% of the capabilities of an editor with type information.
But for the following, maybe regexes / config like the following would be possible:
const a = 1;
let b = 2,
  c = 3;

export const foo = 1;

Config:
	'declaration': {
		pattern: /(const|let|var)\s+([\n\s]*[_$a-zA-Z\xA0-\uFFFF][$\w\xA0-\uFFFF]*([\n\s]*=[\n\s]*[^,;]+)?[\n\s]*[,;])+/,
		inside: {
			'identifier': {
				pattern: /\b((?!const|let|var)[_$a-zA-Z\xA0-\uFFFF][$\w\xA0-\uFFFF]*)\b/,
				alias: 'string'
			},
			rest: Prism.languages.javascript
        }
    }

For the more complex examples, maybe the contents inside the parentheses of function calls could be parsed with a similar pattern to identifier above.
Technically, it's an expression - maybe a regular expression could be developed for that too... 🤔
const d = e * f;

console.log(g.z);

otherFn(h * i);

This will be hard because we have to deal with JS' semicolon insertion. Basically, we don't know where a variable declaration ends. To get this right, we'd have to match a single valid JS expression. The formal language of a single JS expression is context-free and cannot be expressed by a regex. We can usually work around this because we usually know the next character after the expression (e.g. a comma or closing bracket).
If we assume semicolons, it's doable but otherwise, ... I doubt it.
We could settle for the first declaration. That's easy and, hopefully, nobody uses these merged variable declarations.
However, even then: Will this be beneficial?
The end goal is to give const variables a different color to more closely resemble VSC's highlighting. But I'd argue that this would hurt readability because const variables will appear differently when used compared to when they're declared.
If I remember correctly, VSC used to highlight all variable declarations in a different color but then dropped it again in the next release (I assume for similar reasons).

The formal language of a single JS expression is context-free and cannot be expressed by a regex

Will this be beneficial?

const variables will appear differently when used compared to when they're declared

Ok, I can understand that this goes a bit far then. You're right that the benefit is small here and I agree that it would be confusing.
Maybe we stick with importsandexport`s like this issue's description and forget about declarations for now?
import v from "mod";
import {x as v2} from "mod";
import * as ns from "mod";

export * as ns from "mod";
export {v as x} from "mod";
export {x} from "mod";
export {v as x};
export {x};

Ok. Just one question before I make the pull: Should as {name} identifiers get a different class?

Also, the motivation for this feature is to more closely resemble VSC's theme, right? But that uses the normal variable color for imports/exports, so how do you intend to use the feature?

Right so if you look at the demo, the maybe-class-name token is light green, whereas the imports are light blue:

I suppose an alternative that may work could be (#9cdcfe is the light blue color):
.token.keyword.module + .token.maybe-class-name,
.token.keyword.module + .token.punctuation + .token.maybe-class-name {
    color: #9cdcfe;
}

Should as {name} identifiers get a different class?

I guess the same token name should be fine?

Addressed in #2533 🙌 🚀

Closed by #2533.

Thanks @RunDevelopment !


Problem with AMUSE Development install

Hello，
I had no trouble installing AMUSE, but I had a problem with AMUSE Development.  I got an error when running "test_HRdiagram_cluster.py":No module named 'amuse.community.mesa'.  Then I tried to run pip install -e . and got the following error:
(Amuse-env) tangt@DESKTOP-D7M2799:/mnt/f/amuse-main$ pip install -e .
Obtaining file:///mnt/f/amuse-main
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [36 lines of output]
      Traceback (most recent call last):
        File "/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
          main()
        File "/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 164, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 188, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 281, in run_setup
          super(_BuildMetaLegacyBackend,
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 174, in run_setup
          exec(compile(code, __file__, 'exec'), locals())
        File "setup.py", line 71, in <module>
          setup(
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/__init__.py", line 155, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 109, in setup
          _setup_distribution = dist = klass(attrs)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 458, in __init__          _Distribution.__init__(
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 293, in __init__
          self.finalize_options()
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 851, in finalize_options
          ep(self)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/integration.py", line 104, in infer_version
          _assign_version(dist, config)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/integration.py", line 51, in _assign_version
          _version_missing(config)
        File "/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/__init__.py", line 106, in _version_missing
          raise LookupError(
      LookupError: setuptools-scm was unable to detect version for /mnt/f/amuse-main.

      Make sure you're either building from a fully intact git repository or PyPI tarballs. Most other sources (such as GitHub's tarballs, a git checkout without the .git folder) don't contain the necessary metadata and will not work.

      For example, if you're using pip, instead of https://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

So how can I solve this problen, thank you an advance for your answer.

Dear Tangtong,
In your installation you did not install MESA properly. This package has
to be installed separately. At the moment we have two versions of MESA
in AMUSE, one is a somewhat older (but better tested) version, and the
other has just been adapted to be used with AMUSE. you can install
either of them via a separate download.
Steven, can you tell Tantong what is the current best procedure to
install MESA, because that is not yet reported in the book.
Cheers,
Simon
On Feb 28 2022, at 1:42 pm, tangtong98 @.***> wrote:

Hello，
I had no trouble installing AMUSE, but I had a problem with AMUSE
Development. I got an error when running
"test_HRdiagram_cluster.py":No module named 'amuse.community.mesa'.
Then I tried to run pip install -e . and got the following error:
(Amuse-env) @.***:/mnt/f/amuse-main$ pip install -e .
Obtaining file:///mnt/f/amuse-main
Installing build dependencies ... done
Checking if build backend supports build_editable ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [36 lines of output]
 Traceback (most recent call last):

   File

"/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
line 363, in
     main()

   File

"/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
line 345, in main
     json_out['return_val'] = hook(**hook_input['kwargs'])

   File

"/home/tangt/Amuse-env/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py",
line 164, in prepare_metadata_for_build_wheel
     return hook(metadata_directory, config_settings)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py",
line 188, in prepare_metadata_for_build_wheel
     self.run_setup()

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py",
line 281, in run_setup
     super(_BuildMetaLegacyBackend,

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/build_meta.py",
line 174, in run_setup
     exec(compile(code, __file__, 'exec'), locals())

   File "setup.py", line 71, in <module>

     setup(

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/init.py",
line 155, in setup
     return distutils.core.setup(**attrs)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/_distutils/core.py",
line 109, in setup
     _setup_distribution = dist = klass(attrs)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/dist.py",
line 458, in init          _Distribution.init(
   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py",
line 293, in init
     self.finalize_options()

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools/dist.py",
line 851, in finalize_options
     ep(self)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/integration.py",
line 104, in infer_version
     _assign_version(dist, config)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/integration.py",
line 51, in _assign_version
     _version_missing(config)

   File

"/tmp/pip-build-env-63uiw_nu/overlay/lib/python3.8/site-packages/setuptools_scm/init.py",
line 106, in _version_missing
     raise LookupError(

 LookupError: setuptools-scm was unable to detect version for /mnt/f/amuse-main.

 Make sure you're either building from a fully intact git

repository or PyPI tarballs. Most other sources (such as GitHub's
tarballs, a git checkout without the .git folder) don't contain the
necessary metadata and will not work.
 For example, if you're using pip, instead of

https://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj
 [end of output]

note: This error originates from a subprocess, and is likely not a
problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
So how can I solve this problen, thank you an advance for your answer.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
[ { @.": "http://schema.org", @.": "EmailMessage",
"potentialAction": { @.": "ViewAction", "target":
"https://github.com/amusecode/amuse/issues/829", "url":
"https://github.com/amusecode/amuse/issues/829", "name": "View Issue"
}, "description": "View this Issue on GitHub", "publisher": { @.":
"Organization", "name": "GitHub", "url": "https://github.com" } } ]

I think this may be another error. Did you git clone the amuse repository, or download it from github? I saw a similar error when someone downloaded it, in that case you don't get all of the git infrastructure and amuse seems to require that.  After installing amuse via pip, and building the framework and codes, you should also do make mesa.code DOWNLOAD_CODES=1
And about the new version Simon mentioned, the version currently in amuse is an older version of MESA, and an interface to the modern version has been developed but not yet implemented in the main branch. The example script will definitely have been written with the old version in mind, and may not work with the new version. For completeness, the new version is available on the interface developer's amuse fork, https://github.com/rjfarmer/amuse/tree/mesa_15140 (note the branch used).

Could you post the output of pip list | grep amuse?

I run pip list | grep amuse, get the following results:
(Amuse-env) tangt@DESKTOP-D7M2799:~$ pip list | grep amuse
amuse                 2<IP_ADDRESS>.dev187+g299457310 /home/tangt/amuse/src
amuse-athena          2<IP_ADDRESS>
amuse-bhtree          2<IP_ADDRESS>
amuse-bse             2<IP_ADDRESS>
amuse-capreole        2<IP_ADDRESS>
amuse-evtwin          2<IP_ADDRESS>
amuse-fastkick        2<IP_ADDRESS>
amuse-fi              2<IP_ADDRESS>
amuse-fractalcluster  2<IP_ADDRESS>
amuse-framework       2<IP_ADDRESS>
amuse-gadget2         2<IP_ADDRESS>
amuse-galactics       2<IP_ADDRESS>
amuse-galaxia         2<IP_ADDRESS>
amuse-halogen         2<IP_ADDRESS>
amuse-hermite         2<IP_ADDRESS>
amuse-hop             2<IP_ADDRESS>
amuse-huayno          2<IP_ADDRESS>
amuse-kepler          2<IP_ADDRESS>
amuse-kepler-orbiters 2<IP_ADDRESS>
amuse-mameclot        2<IP_ADDRESS>
amuse-mercury         2<IP_ADDRESS>
amuse-mmams           2<IP_ADDRESS>
amuse-ph4             2<IP_ADDRESS>
amuse-phigrape        2<IP_ADDRESS>
amuse-seba            2<IP_ADDRESS>
amuse-secularmultiple 2<IP_ADDRESS>
amuse-simplex         2<IP_ADDRESS>
amuse-smalln          2<IP_ADDRESS>
amuse-sphray          2<IP_ADDRESS>
amuse-sse             2<IP_ADDRESS>
amuse-tests           2<IP_ADDRESS>
amuse-twobody         2<IP_ADDRESS>

Thanks.
You will need to uninstall all amuse packages except for amuse itself - it should work then.

Thank you very much for your help, I have been able to use it smoothly.


locateCenterOnScreen behaves if image not found

locateCenterOnScreen was calling center() regardless of the success of locating the image on the screen.  In cases where this was None, center() would try to address elements in the None and fail.  In this request, I perform a check to see if locate has returned None before calling center, otherwise, None is returned in keeping with the other locate functions.

Was able to reproduce the error and support this fix.
Would be glad if this could be merged @asweigart

I've already implemented this in PyScreeze, which PyAutoGUI includes, but thanks anyway! I'll add you to the authors.txt file.


Create flexible modals

Component
This component is a modal that can be used for different occasions.
Success criteria

[ ] It needs to work with and without scrolling
[ ] It needs to work with and without a header
[ ] It needs to work with full body and dropdown functionalities
[ ] It need to work as a full page, medium or small modal
[ ] It needs to work with multiple buttons

Please suggest if I am missing cases!

Now the modals are quite simple, so we can use the standard tall modal (with a title, body and footer).

Thank you, these versions are what we needed!
However, is it possible there's something broken?


coverity 1382799, 1382796: Unchecked return value

[approve ci autest]

working on fixing autest for this to pass

[approve ci autest]


Somehow display OEIS sequence "names" or quickly link to OEIS?

This is a stub for future discussion. But if this is envisioned in part as a way to kind of browse the OEIS, then it would seem important to be able to see some information about a sequence from the OEIS -- say at least the "name" field of the sequence, what appears in the top of the entry at oeis.org -- quickly and easily. For example, a hover text that shows the name, or at least occurrences of sequence numbers become links to the OEIS, or a quick way to pop up a mini-page about the sequence, or something...

Note that by now, the backend is always grabbing official sequence names, and I think returning them in the JSON responses whenever it has them. So all that's needed for this issue is for the front end to actually pay attention to that information and display it in some way.

Mostly implemented in ui2, just need links to OEIS page in the description string, which is planned for after beta in our roadmap. So leaving this issue in place in the meantime.


Filling external events fails because extract_dtype does not convert "number" and "integer"

https://github.com/bluesky/databroker/blob/970e9148dfab5e77101d40f059ecb30d064eac81/databroker/core.py#L2146
Filling external events with dtypes other than "array" is currently broken, due to a lack of functionality in extract_dtype
When creating a descriptor document, a "dtype" is required for each entry in "data_keys". This dtype is required to be one of ['string', 'number', 'array', 'boolean', 'integer']. When you try to read data, a complex dance between bluesky-live, databroker, and event_model happens, but the upshot is that one way or another, a Filler instance tries to call a handler that has been wrapped with coerce_dask from databroker.
This dask-coerced handler now tries to understand its data type by looking at the descriptor document
dtype = extract_dtype(descriptor, key)
def extract_dtype(descriptor, key):
    """
    Work around the fact that we currently report jsonschema data types.
    """
    reported = descriptor['data_keys'][key]['dtype']
    if reported == 'array':
        return float  # guess!
    else:
        return reported

The function extract_dtype is supposed to convert the descriptor's json dtypes into a numpy dtype that dask will accept, but it only converts 'array' to float, and passes everything else directly to dask. At the very least, 'number' could be converted to float, and 'integer' could be converted to int. Otherwise, dask crashes as soon as it gets an unrecognized string, and the traceback is an awful mess.

Thanks for this clear description and for your patience with the delayed reply.
We are in the final stages of a major internal refactor of databroker, moving from intake to tiled in the core. I believe that the refactored version handles this case properly. It also simplifies things quite a bit, dispensing with the need for this "coercion" concept entirely.
I would be curious to know if your use case works on the v2.0.0-dev branch of databroker.


Checksum fails for MAMP 4.2.1

General troubleshooting steps

[ X] I have retried my command with --force and the issue is still present.
[ X] I have checked the instructions for reporting bugs (or making requests) before opening the issue.

[ X] None of the templates was appropriate for my issue, or I’m not sure.

[ X] I ran brew update-reset && brew update and retried my command.
[ X] I ran brew doctor, fixed as many issues as possible and retried my command.
[ X] I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue
Error: Checksum for Cask 'mamp' does not match.\n\nExpected: 808e9685153c12a50d582e5eb27badbbc0cdc0df3fd3e0bf4bcaa74c4dc6a058\nActual:   9428a3cf494d02d94ecaec302042822f54273ba9d412ecde25d1155ab07db56e

Verified and is correct
Output of your command with --verbose --debug
Irrelevant
Output of brew cask doctor
Irrelevant
PR incoming

Please don't open issues if you are going to submit a PR.


Add the ability to configure the cache directory

At present the cache directory is hard coded:
def self.setup_default_cache_dir
  windows_dir = windows_data_dir
  @facts_cache_dir = if windows_dir
			 File.join(windows_dir, 'PuppetLabs', 'facter', 'cache', 'cached_facts')
		       else
			 '/opt/puppetlabs/facter/cache/cached_facts'
		       end
end

It would nice to be able to set the cache directory in facter.conf

It would nice to be able to set the cache directory in facter.conf

Could you expand on why it would be nice to have?

I think it will be useful in the OSS version that can be installed anywhere:
$ gem install facter
Successfully installed facter-4.9.0
Parsing documentation for facter-4.9.0
Done installing documentation for facter after 1 seconds
1 gem installed

$ which facter
/Users/example/.rbenv/shims/facter

It would nice to be able to set the cache directory in facter.conf

Could you expand on why it would be nice to have?

My apologies for not being more descriptive. @scrill hinted at the reason for the original request. We use the facter gem in combination with the puppet gem as part of our testing process. When running tests we get this output:
Warning: Facter: Could not write cache: Permission denied @ dir_s_mkdir - /opt/puppetlabs/facter/cache/cached_facts
Warning: Facter: Could not write cache: Permission denied @ dir_s_mkdir - /opt/puppetlabs/facter/cache/cached_facts

I looked for a way to silence this warning, or move the directory somewhere where the non-root testing user could write. This is when I discovered that the path is hard coded, which was the genesis of this feature request. Thanks!

Hi @lollipopman, thank you for reporting this issue! Removing the hard coding for cache is a technical direction that we have decided not to follow at Puppet.
We agree that it would be good to address or have some way to silence the warning you're running into but we do not anticipate addressing this any time soon due to other issues demanding precedence. We have added the help wanted label in case any contributors could submit a PR to address this.


Insufficient constraints for fn inverse in Fp2 (and other) extension field gadgets

As explained in detail in the same issue just patched in our Zexe fork, the two constraints used in the fn inverse in r1cs-std/src/fields/fp2.rs are not sufficient to enforce the inverse relation. The same issue is found in the following gadgets:

Fp4Gadget,
FP6Gadget in fp6_2over3.rs,  and
Fp12Gadget.

The issue is easily patched, one just has to keep the equation for "real" part of the product, i.e. 1 - nonresidue * v1 = a0 * b0 in the notation of the gagdet.

Thanks for bringing this up! I've opened PR #174 with your fix (with proper credit in the code)


Adding two Player in Carla Version 0.8.4

Hi,
I want to add an other vehicle as a main car in Carla Version 0.8.4. How am I adding Two player in Carla? Is this possible?

Hello @FarzanehJafari.
This is not possible in CARLA 0.8.x, but is included in the current experimental 0.9.0!

Thanks
Sent from Yahoo Mail for iPhone
On Wednesday, September 19, 2018, 14:05, Marc Garcia Puig<EMAIL_ADDRESS>wrote:
Hello @FarzanehJafari.
This is not possible in CARLA 0.8.x, but is included in the current experimental 0.9.0!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


get_params function is mandatory for provided ciphers

It appears that having a "get_params" function is mandatory for a provided cipher.
This is not checked for when we check that a cipher has all the minimum functions that it needs:
https://github.com/openssl/openssl/blob/3d623896eb50f5b15d3ef8f53b9f1e5c7546695a/crypto/evp/evp_enc.c#L1630-L1642
But the "fetch" still fails because it must be there when we cache the cipher constants (because otherwise evp_cipher_cache_constants fails:
https://github.com/openssl/openssl/blob/3d623896eb50f5b15d3ef8f53b9f1e5c7546695a/crypto/evp/evp_enc.c#L1647-L1651
This tripped up an author of a new provider here:
https://github.com/orgs/provider-corner/discussions/2
It seems to me that the way evp_cipher_cache_constants is written is that no particular constants need to be present, but "get_params" must be there (so a "get_params" function that supports no parameters would be sufficient). I am not convinced that this requirement to have "get_params" is deliberate. Probably it should be optional to have one (in which case no constants get cached). In fact the man page says that it is optional:

A cipher algorithm implementation may not implement all of these functions. In order to be a consistent set of functions there must at least be a complete set of "encrypt" functions, or a complete set of "decrypt" functions, or a single "cipher" function. In all cases both the OSSL_FUNC_cipher_newctx and OSSL_FUNC_cipher_freectx functions must be present. All other functions are optional.

https://www.openssl.org/docs/man3.0/man7/provider-cipher.html
Either we should make "get_params" optional as per the documentation, or we should update the documentation to say that it is required.

I am not convinced that this requirement to have "get_params" is deliberate.

It isn't, we've been sloppy checking if it's there or not.  The original idea is that it should be possible to do without, in which case there are no values to be cached.
However, come to think of it, this idea might not be feasible after all, since there are some values that we may need to have unconditionally, such as key size, block size, that sort of stuff.

Either we should make "get_params" optional as per the documentation, or we should update the documentation to say that it is required.

I would prefer that it remains optional, but we need to check that it's feasible.

To me it does not make any sense to keep it as optional function. At least it should be possible to query the key size, block size, and iv size, if the algorithm has an iv.

To me it does not make any sense to keep it as optional function. At least it should be possible to query the key size, block size, and iv size, if the algorithm has an iv.

Unfortunately where we are now is that no parameter is listed as mandatory - they are all optional. Making a currently optional parameter mandatory would be a breaking change so its not something we can do in a minor release. So all parameters are optional, but the presence of the "get_params" function itself is mandatory. That doesn't make a lot of sense and I don't think it was what was originally intended. Making "get_params" optional is probably something we can do as a bug fix without breaking anything.

To me it does not make any sense to keep it as optional function. At least it should be possible to query the key size, block size, and iv size, if the algorithm has an iv.

Well, depends.  If the application knows the cipher intimately, it would be unsurprising if it knows all those sizes, or whether an IV is needed or not.  In that case, it has zero need for those cached constants, it would just init, update, final and be done with it.
It is perfectly feasible for a provider to be documented with the necessary information and to expect the application author to read that and act accordingly.
Of course, it's nice if the provider can provide those parameters for you, but that doesn't mean it should be mandatory, however rough that may be.

I did a quick test with the vigenere toy, simply having its get_params do nothing...  It turns out badly, unfortunately...  among others, it seems that we depend on block size being given.
Intuitively, I'm not sure why we couldn't do without a given block size...  essentially, we would have to consider a cipher for which we don't know the block size a stream cipher, but that doesn't seem impossible for most all but ECB mode ciphers, or have I misunderstood that part?

Stream ciphers have block size 1

Stream ciphers have block size 1

Yes.  So our code could assume 1 if the cipher doesn't set a block size

That would be a reasonable default, but if its wrong we will not pad correctly.

I really do not see the fuss of providing one more function returning a few constant params when writing a cipher provider. We could just document the de-facto state.

The original idea (at least in my mind) was that parameters handled with OSSL_PARAMS would always be optional.  That's a reason why it's documented as it is.  In particular, we might want to pay attention to this line:
https://github.com/openssl/openssl/blob/fc2be2d07acc0cfe954320c2491b8c5461cbef09/doc/man7/provider-cipher.pod?plain=1#L207
So, unless blocksize is relevant to some cipher, why should it care to give one?

Didn't you earlier write the our code crashes if no block size is available?
That seems like a good reason to provide one.

Didn't you earlier write the our code crashes if no block size is available? That seems like a good reason to provide one.

That can as well be seen as a bug in our code.

That would be a reasonable default, but if its wrong we will not pad correctly.

I was debating with myself if that's something libcrypto must care about that...  but yeah, I guess it must at least say that there is buffer space for that, there doesn't seem to be a sane way out of that, at least at a quick code read.  If nothing else, this part is a glaring demonstration:
https://github.com/openssl/openssl/blob/fc2be2d07acc0cfe954320c2491b8c5461cbef09/crypto/evp/evp_enc.c#L710-L711

That can as well be seen as a bug in our code.

It is a bug in either our code or documentation.  It also guarantees that nobody is relying on documented behaviour.

block and key size are mandatory

Is key size mandatory? I didn't see anything to suggest that missing a key size would cause a crash at the moment?

block and key size are mandatory

Is key size mandatory?

Looks that way.
https://github.com/openssl/openssl/blob/fc2be2d07acc0cfe954320c2491b8c5461cbef09/crypto/evp/evp_enc.c#L233-L240
https://github.com/openssl/openssl/blob/fc2be2d07acc0cfe954320c2491b8c5461cbef09/crypto/evp/evp_enc.c#L248-L255

I didn't see anything to suggest that missing a key size would cause a crash at the moment?

"crash" is a bit strong, but you get init failure or incorrect encryption because the key size that's passed to ->einit / ->dinit is invalid or smaller than intended (i.e. zero).

"crash" is a bit strong, but you get init failure or incorrect encryption because the key size that's passed to ->einit / ->dinit is invalid or smaller than intended (i.e. zero).

Hmmm. This is actually a bit of an issue because the thing that will fail here is the provider implementation. So, if a we suddenly  make key size a mandatory param that could actually result in a breaking change if the provider implementation ignores that key size that is passed back in the init call.

"crash" is a bit strong, but you get init failure or incorrect encryption because the key size that's passed to ->einit / ->dinit is invalid or smaller than intended (i.e. zero).

Hmmm. This is actually a bit of an issue because the thing that will fail here is the provider implementation. So, if a we suddenly make key size a mandatory param that could actually result in a breaking change if the provider implementation ignores that key size that is passed back in the init call.

Not really?  If their init functions ignored the key size before, they can continue to do so and continue to assume what they already assume about the key buffer.

Not really? If their init functions ignored the key size before, they can continue to do so and continue to assume what they already assume about the key buffer.

Ah, I can actually test that

Not really? If their init functions ignored the key size before, they can continue to do so and continue to assume what they already assume about the key buffer.

My point is that if their init functions ignored the key size before, and their get_param function did not provide a key size param, then making key size a mandatory parameter is a breaking change for them.

Re the key size, not setting one in get_params, and ignoring in the provider's encryption/decryption init function works fine.
... But!
Our openssl enc makes assumptions based on EVP_CIPHER_get_key_length():
https://github.com/openssl/openssl/blob/948c656c66a3846337a0262197766c80ec7c9e59/apps/enc.c#L494-L503
https://github.com/openssl/openssl/blob/948c656c66a3846337a0262197766c80ec7c9e59/apps/enc.c#L546-L553

Re the key size, not setting one in get_params, and ignoring in the provider's encryption/decryption init function works fine.

Right - so basic cipher functionality works. Other things that you might do with that cipher may or may not work, but there is at least some scenarios where making key len a mandatory parameter could cause existing applications to break.


Use the context accessor methods

We have nice accessor methods for the context class so we should use them vs treating it like a hash

ok, thinking this needs to be rebased after #59