Added new packages as dependencies for the root project.

The packages data, legacy, platform and util were not published due to them not being included in the root project.

@non: please +1, this follows our work last month

Codecov Report

Merging #724 into master will increase coverage by 0.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #724      +/-   ##
==========================================
+ Coverage   50.36%   51.19%   +0.83%
==========================================
  Files         192      192
  Lines       11735    11735
  Branches     1602     1611       +9
==========================================
+ Hits         5910     6008      +98
+ Misses       5825     5727      -98

Impacted Files
Coverage Δ

...ore/src/main/scala/spire/math/interval/Bound.scala
53.54% <0%> (-0.79%)
:arrow_down:

...ala/spire/math/poly/BigDecimalRootRefinement.scala
84.76% <0%> (-0.67%)
:arrow_down:

core/src/main/scala/spire/math/Interval.scala
69.66% <0%> (+0.77%)
:arrow_up:

core/src/main/scala/spire/math/Algebraic.scala
67.27% <0%> (+1.21%)
:arrow_up:

...ore/src/main/scala/spire/math/poly/PolyDense.scala
97.36% <0%> (+1.31%)
:arrow_up:

extras/src/main/scala/spire/math/FixedPoint.scala
36.61% <0%> (+1.63%)
:arrow_up:

...spire/optional/intervalGeometricPartialOrder.scala
100% <0%> (+6.25%)
:arrow_up:

util/src/main/scala/spire/util/Opt.scala
66.66% <0%> (+66.66%)
:arrow_up:

util/src/main/scala/spire/util/Pack.scala
81.39% <0%> (+81.39%)
:arrow_up:

Continue to review full report at Codecov.

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

👍


Add json_schema to validate .yml files

Describe the feature
There are many  editors right now have support of LanguageServiceProtocal (lsp).
As for now Yaml & JSON both have dedicated lsp implemantation.
As an example VScode has an extension:
Features

YAML validation:

Detects whether the entire file is valid yaml
Detects errors such as:

Node is not found
Node has an invalid key node type
Node has an invalid type
Node is not a valid child node

Document Outlining (Ctrl + Shift + O):

Provides the document outlining of all completed nodes in the file

Auto completion (Ctrl + Space):

Auto completes on all commands
Scalar nodes autocomplete to schema's defaults if they exist

Hover support:

Hovering over a node shows description if provided by schema

Formatter:

Allows for formatting the current file

Auto completion and hover support are provided by the schema. Please refer to Language Server Settings to setup a schema
Draft version of json schema for DBT
Register schema in vscode:
"yaml.schemas": { "~/schemas/dbt_schema.json": ".schema.yml" },
Who will this benefit?
Anybody who uses vscode/atom/emacs etc. to edit model.
It will allow to improve productivity of creating and modifying yml/json and avoid a lot of error
It also allow to have validation and autocomplete  for customized  meta properties.

This would be super useful.

hey @DmitryMaletin - this is awesome! I spent a couple of mins playing around with something like this evening. I just want to your attention to a script in the dbt codebase that could help with something like this in the future. This script uses dbt's internal dataclasses to generate a json schema for the artifacts produced by dbt.
I don't think we actually have a proper json schema internally that represents the spec for the schema.yml file. Instead, we kind of mix together 1) the input yml provided by users and 2) metadata attached to nodes by dbt as files are parsed.
Here's a super quick version of this. It won't really work for this specific use-case, but I think we're not so far away from being able to automate something like this :)

setup:
python3 -m venv env
source env/bin/activate
pip install dbt

Then run:
#!/usr/bin/env python
from dataclasses import dataclass
from typing import Dict, Any
import json

from hologram import JsonSchemaMixin
from dbt.contracts.graph.unparsed import UnparsedNodeUpdate

model_schema = UnparsedNodeUpdate.json_schema()
print(json.dumps(model_schema))

Note the inclusion of fields like original_file_path and yaml_key in the resulting document. I don't think it will be super hard to build a version of these schemas that omits those dbt-generated fields. We'll also probably want to include human readable descriptions (we can definitely do that).
Thanks for opening this one -- it took me about a month to get around to this. Check out the relevant code [here]https://github.com/fishtown-analytics/dbt/blob/eea51bee30d79054637b2adfffc8d3fb0cf99ce3/core/dbt/contracts/graph/unparsed.py#L119) and let us know what you think :)

Hi @drewbanin
Thank you for advice. I will have a look to suggested codes.

This looks great to me, any progress on it?

I think this can easily be accomplished for folks using VSCode using https://www.schemastore.org/json/!

I've found something, but it's rudimentary: https://app.rakam.io/schema/dbt.schema.json
Did anything better appear?

Due to the shape of our YAML it can't be automatically generated, but I'm hoping to spend some time next month fleshing out a more robust schema version 🤞

Indeed, custom tests can't be checked as well as anything related to file structure. But something can be :)

any news on this? Would love to have some intellisense in vs code 😄

@clrcrl and I paired up last week and got the bones of a schema up and going! It's sitting at https://github.com/dbt-labs/dbt-jsonschema for anyone who wants to follow along/contribute

Just published a mostly complete schema to https://github.com/dbt-labs/dbt-jsonschema!
There's definitely room to keep fleshing it out, especially around descriptions and sample values. Anyone is welcome to open PRs against the repo.
Demo Loom: https://www.loom.com/share/7dd4dfc67765441b80ff454942f59b63


BigtableOptionsFactory.fromConfiguration doesn't respect emulator credential settings

I was attempting to use the google.bigtable.emulator.endpoint.host configuration option when I noticed I still needed application default credentials set up anyways. A quick debug shows that in BigtableOptionsFactory.fromConfiguration it configures the emulator settings, including enabling null credentials, and then overwrites them in the call to setChannelOptions later on in the function.
It does work if I set the following two options as well:
conf.set(BigtableOptionsFactory.BIGTABLE_NULL_CREDENTIAL_ENABLE_KEY, "true");
conf.set(BigtableOptionsFactory.BIGTABLE_USE_SERVICE_ACCOUNTS_KEY, "false");

If the intent was to need all three feel free to close and I'll be on my way, but it seemed unlikely given that the enableEmulator function sets them up.

Woops.  We're looking at this.

This should be fixed by #1948


feat(cts): add client test for retry strategy

🧭 What and Why
Add a retry strategy test, which works by creating 2 servers, the first one should timeout, and the second one returns something we can check against, then we make sure we had the correct response, and that the timeout server was called.
This ensures 3 things in the client:

The hosts are configurable
The timeout is correct
The retry strategy tries another host.

Note: this only works in js for now, but we can add it everywhere

Whooo ! So nice, so fast !

(btw gg to everyone who contributed to this, it's huge!)


Implement a call-loop for failed MAFILDB API calls

Try to send the request max. 5 times with a period of 5-10 seconds and then throw an error.

Try to implement it in the useQuery() hook like this: https://tanstack.com/query/v4/docs/framework/react/guides/query-retries


Update for Spree 3.4. Add complete I18n

I updated the dependencies in the gemset to match spree '~> 3.4.0' and fixed all bugs, so this extension is working with spree 3.4.1.
I also completely I18n'ized the extension, translating all text for both English and Russian.

Sorry, had a typo. Version 3.4.0, not 2.4.0


Additional modmail settings

Is it possible to have modmail setup so that it responds via a command to forward the message? Currently it seems that modmail is just the forwarder cog with a different name and can forward to a channel. it would be nice if there was a additional settings to allow modmail to only be triggered when the person does !modmail in dms or a channel so that admins/mods dont get bombarded with all of the dms to the bot since some people tend to use dms for other stuff such as payday or other similar commands

Forwarding of DMs can now be disabled and can now use [p]modmail to send it manually.


I want to use LSTM as the feature extractor of financial data. When looking up the problem #195 in finrl, I now use the Sb3 framework in finrl, and support LSTM as the feature extractor in SB1. How can I smoothly migrate back.

Hello, I have LSTM as the feature extractor of financial data the problem. I also want to build an LSTM feature extractor on Sb3 for financial time series data, using mlppolicy strategy network. I want to ask whether fin-rl now has an LSTM algorithm feature extractor.
When looking up the problem #195 in finrl, I now use the Sb3 framework in finrl, and support LSTM as the feature extractor in SB1. How can I smoothly migrate back.
Thank you for your previous exploration.

Great question, was wondering same thing

@Zero1366166516 great question!  Your codes of LSTM as feature extractor are welcome!  I will talk with one or two group members to work with you, it is very valuable to provide to our community members. I heard several times when users requested this feature.

I previously made a CNN feature extractor for mlppolicy strategy network, which can be shared with everyone.
CNN feature extractor :

class CustomCNN(BaseFeaturesExtractor):
    """
    :param observation_space: (gym.Space)
    :param features_dim: (int) Number of features extracted.
        This corresponds to the number of unit for the last layer.
    """

    def __init__(self, observation_space: gym.spaces.Box, features_dim: int = 1):
        super(CustomCNN, self).__init__(observation_space, features_dim)
        # We assume CxHxW images (channels first)
        # Re-ordering will be done by pre-preprocessing or wrapper
        n_input_channels = observation_space.shape[0]

        #print("n_input_channels and output_channels", observation_space.shape[0], observation_space.shape)
        #print("features = ", observation)

        self.cnn = nn.Sequential(

            nn.Conv1d(self.features_dim, n_input_channels, kernel_size=1, stride=1, padding=0),
            nn.ReLU(),
            nn.Conv1d(n_input_channels, self.features_dim, kernel_size=1, stride=1, padding=0),
            nn.ReLU(),
            nn.Flatten(),
        )
        #print(self.cnn.type)

        # Compute shape by doing one forward pass
        with th.no_grad():
            n_flatten = self.cnn(
                th.as_tensor(observation_space.sample()[None]).float()
            ).shape[1]
            #print("n_flatten", n_flatten)
            ##print("cnn", self.cnn)

        self.linear = nn.Sequential(nn.Linear(n_flatten, features_dim), nn.Tanh())
        #print(self.linear)
        #self.linear = th.as_tensor(self.linear)
        #exit()

    def forward(self, observations: th.Tensor) -> th.Tensor:
        ##global features_dim, n_flatten
        with th.no_grad():
            n_flatten = np.array(observations).shape[-1]
            features_dim = np.array(observations).shape[-2]
            #print(features_dim, n_flatten, np.array(observations).shape)
            #exit()
            i = 0
            j = 0
            if features_dim != 1:
                self.cnn = nn.Sequential(
                    nn.Conv1d(features_dim, n_flatten, kernel_size=1, stride=1, padding=0),
                    nn.ReLU(),
                    nn.Conv1d(n_flatten, features_dim, kernel_size=1, stride=1, padding=0),
                    nn.ReLU(),
                    nn.Flatten(),
                )
                self.linear = nn.Sequential(nn.Linear(n_flatten, 1), nn.Tanh())
                i += 1
                # print("cnn type is ", self.cnn)
                # print(self.linear)
                # print("go to the forward:", observations)
                # print("the observations number:", np.array(observations).shape)
                # print("output data :", self.linear(self.cnn(observations)))
                # print("output data number:", np.array(self.linear(self.cnn(observations))).shape)
                # print("this is I in {} time".format(i))

            else:
                j += 1
                self.cnn = nn.Sequential(
                    nn.Conv1d(features_dim, n_flatten, kernel_size=1, stride=1, padding=0),
                    nn.ReLU(),
                    nn.Conv1d(n_flatten, features_dim, kernel_size=1, stride=1, padding=0),
                    nn.ReLU(),
                    nn.Flatten(),
                )
                self.linear = nn.Sequential(nn.Linear(n_flatten, 1), nn.Tanh())
                # print("go to the NO 1:", observations)
                # print("the observations NO 1 number:", np.array(observations).shape)
                # print("output data NO 1:", self.linear(self.cnn(observations)))
                # print("output data number:", np.array(self.linear(self.cnn(observations))).shape)
                # print("this is J in {} time".format(j))

        return self.linear(self.cnn(observations))

The following is the call part.
policy_kwargs = dict(
        features_extractor_class=CustomCNN,
        #share_features_extractor=False,
        #features_extractor_kwargs=dict(features_dim=1),
        #features_dim=1,
        net_arch=dict(qf=[128, 128], pi=[256, 256])
    )
    #policy_kwargs = dict(activation_fn=th.nn.ReLU,
    #                     net_arch=[dict(pi=[32, 32], vf=[32, 32])])
    def get_model(
        self,
        model_name: str,
        policy: str = "MlpPolicy",
        #policy: str = "MultiInputPolicy",
        policy_kwargs: dict = policy_kwargs,
        model_kwargs: dict = None,
        verbose: int = 1
    ) -> Any:

        print("set Debug!")

        if model_name not in MODELS:
            raise NotImplementedError("NotImplementedError")

        if model_kwargs is None:
            model_kwargs = MODEL_KWARGS[model_name]

        if "action_noise" in model_kwargs:
            n_actions = self.env.action_space.shape[-1]
            model_kwargs["action_noise"] = NOISE[model_kwargs["action_noise"]](
                mean=np.zeros(n_actions), sigma=0.1 * np.ones(n_actions)
            )
        # print(model_kwargs)
        # print(policy, self.env)
        # print(model_name)
        # #print(self.env.observation)
        # print("dispaly: observation_space", self.env.observation_space)
        # print(self.env.daily_information_cols)

        model = MODELS[model_name](
            policy=policy,
            env=self.env,
            tensorboard_log="{}/{}".format(config.TENSORBOARD_LOG_DIR, model_name),
            verbose=verbose,
            policy_kwargs=policy_kwargs,
            **model_kwargs
        )
        #print("model display: ", model)
        #exit()
        return model

I would like to ask whether this algorithm can be used in real stock trading, and how to realize the operation of the next day in the real world.

I would like to ask whether this algorithm can be used in real stock trading, and how to realize the operation of the next day in the real world.

Can you elaborate more?  Are you asking feedback about its feasibility in a live trading task?   Or would you like to Plug it into a paper trading demo?

My idea is to use it in the real world to use DRL algorithm to make portfolio, such as predicting whether positions should be adjusted tomorrow and how to use it in trading.

My idea is to use it in the real world to use DRL algorithm to make portfolio, such as predicting whether positions should be adjusted tomorrow and how to use it in trading.

Could I understand it as a general question about applying DRL to real-world portfolio allocation?    As far as I know, DRL is a quite powerful tool;  tens of hedge funds and investment banks have deployed it.....and they got around 40% annual return over the past year.  Probably not invest significant capital yet.
ElegantRL has polished the DRL algorithms and is easily adapted to finance applications.  If you need algorithmic support, please let me know.

Thank you very much for your help. Let me talk about my situation first. I am interested in quantitative investment. I am also a shareholder. I found that MLP is used as the feature extractor in the DRL model used to study finance now. I want to try CNN and LSTM as the feature extractor. Now I use the routine of Sb3 to modify a CNN feature extractor, and the effect is OK (after I use MLP as the feature extractor for backtesting, I had better get an annualized yield of 13%, and CNN had better get an annualized yield of 20%).
I have two problems to solve. 1. How can the current algorithm be used for real offer operation? Because now the data that has occurred is used for back testing. I want to use the DRL algorithm in actual transactions. What should I do.
2. I have written CNN feature extractor. I don't know whether anyone has tried it before and how the effect is. LSTM feature extractor I'm looking for information and ready to start. I can write one first. If there is an error, please study it together.

You may be interested to know this repo https://github.com/AI4Finance-Foundation/FinRL-Live-Trading
The team is trying to release codes for live trading. However, it may take some time.
If you like, please try to interact with members there.

Hi @Zero1366166516
I can suggest you try using RLlib. They have LSTMPolicy which you can customise easily


Allow generated password criteria

Add functionality to allow me to customise the length of password generated and character set used.

Closing for merge into #18


Duplicate profile

Being able to duplicate an existing profile would be practical.
For example in the popup after a long press event on a profile, simply having a "Duplicate" action that just copies all the properties of the selected profile and open the create profile view with it would be nice.
I have a lot of almost identical servers and this feature would really speed up the configuration phase.

I would also want this feature and/or the option to export all/part of your servers to a config file wich you could import again in same/other device.


Preparing the docs for pre-release

This one includes a bunch of tweaks to the startpage, sidebar, CSS and content. This PR is WIPish, the sidebar still needs tweaking and there is still plenty of content that needs updating or writing (e.g. #6 ).
The sidebar is pretty flexible, category items can be forced open (collapsed: false), or collapsing can be turned off completely (collapsible: false). Furthermore, category labels themselves could, and should be pointing to a document themselves via category links. This can further help reduce the complexity of the sidebar.
Through these features I made several tweaks to the sidebar already and adjusted content where needed.
I also adjusted the layout and formatting of the startpage to reduce the white space and bring content closer to/above the fold.
Changes can be previewed at: https://suborbital.github.io/docs/

@flaki this is looking GREAT!
The main change I'd like to see is on the homepage:

I've decided not to use the SCN logo, and instead let's just pretend 'Suborbital' and 'Suborbital Compute' are one in the same in this context. Let's have the Suborbital logo first-row-left (instead of the text header), and have the 'get started' link bring you to the Compute docs. Let's change the short blurb to instead be about Compute (extend and customize SaaS, etc)

first-row-right let's have a 'WebAssembly' heading, a quick sentence about Wasm, and the link to 'What is WebAssembly?'

In the second row let's put Atmo and then Sat. I don't have a logo for Sat yet, but let's put it beside Atmo in the second row. Please add an empty category for Sat in the sidebar (I'll be filling in the content soon)

Third row is great!

Well done on this, it's starting to really come together.

Also, on the main 'Compute' page, the 'give it a try' link still goes to the Typeform... let's replace that link with https://suborbital.network

Oh and one last thing, a teeny nit, I like to have the building blocks ordered RVG (Reactr, Vektor, Grav)... it's mostly just a habit, but also roughly the order in which I think people should care about them :)

@cohix the above should all be addressed in the last update. There's plenty to clean up and tweak on the docs themselves (esp. the taxonomy), not to mention going through the docs and ensuring that we use Docusaurus' features to their full extent but it's shaping up real nice I'd say.
PS: I made a quick placeholder icon for Sat so it doesn't mess with the overall looks of the page :)

* In the second row let's put Atmo and then Sat. I don't have a logo for Sat yet, but let's put it beside Atmo in the second row. Please add an empty category for Sat in the sidebar (I'll be filling in the content soon)

Yeah! I'm currently re-thinking the Atmo sidebar/content structure a bit to make it easier to grok but not be too overwhelming, also need to dig into Docusaurus a bit more (e.g. the parent category labels are not showing up anywhere and that kinda makes it less straightforward what's going on, will need to do a bit of research on this, see how it's done on other Docusaurus sites).
But other than that, I'd be happy to pair if you don't have anything on paper yet about Sat to kickstart those docs, or if you do just drop them into e.g. Notion and we can work on that async. Either case, if you have any ideas about how you want to structure it feel free to drop them in a Notion page and send it over. :)

These commits put the docs infra in a good place. There still are various pending tasks of tweaks, refactoring and additional content needs that could be addressed separately, I'm merging this PR as the new baseline.


chore: bdd-nh-1583564181 to 0.0.1

chore: Promote bdd-nh-1583564181 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
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

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


FEAT: Added a get_aggregate_events templatetag to inject AggregateEve…

Hi,
This commit just adds a simple template tag in the module to retrieve easily the AggregateEvent objects in a template.
If you're interested to include such in the module.
Many thanks !

@pierreben thanks for the change!
I'm likely going to make a separate django app just for the admin integration since it's pretty substantial and requested. If I do, I will be sure to add this code there and tag you as a contributor. I'm going to leave this PR open for now with the other admin one

Ok, thanks for your answer.
For the needs of a specific project, I've created a (quite complex) template tag that aims to display the whole changes of an object and its related models (with inheritance handling :)) based on the fieldsets of the modeladmin, and the fieldsets of the inlines.
I think it's generic enough to go on a snippet that can inspire a work on an admin integration.
I need to check if I have the rights to share it and I will notify you in this case, if it can help in any way.


Not able to run the Service

I am trying to simulate cache side channel attacks on two ubuntu VMs running on a hyper-v host but I can't get the service running. I am getting the error attached. I made sure that cargo, rustc and perf were installed and working. Do you have any idea what I am doing wrong?

Okay, seems like the used hardware misses some counters. Could you please paste the output of
sudo perf list

here? Just to see what events are supported on your hardware.

Hi Hagen,
i attached the export since it surpasses the character limit.
Perf Export.txt

hagar@Ubuntu-1:~/barnowld$ sudo perf list
[sudo] password for hagar:
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descri>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descri>
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descri>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descri>
[(see 'man perf-list' on how to encode it)]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descrip>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descrip>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descrip>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descrip>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descrip>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descrip>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descrip>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descrip>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
:
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descript>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descript>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descript>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descript>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descript>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descript>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descript>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descript>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descript>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descript>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
:
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descripto>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descripto>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descripto>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descripto>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
block:block_bio_bounce                             [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descripto>
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descripto>
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
block:block_bio_bounce                             [Tracepoint event]
block:block_bio_complete                           [Tracepoint event]
:
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descriptor]
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descriptor]
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
block:block_bio_bounce                             [Tracepoint event]
block:block_bio_complete                           [Tracepoint event]
:...skipping...
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descriptor]
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descriptor]
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
block:block_bio_bounce                             [Tracepoint event]
block:block_bio_complete                           [Tracepoint event]
block:block_bio_frontmerge                         [Tracepoint event]
:
List of pre-defined events (to be used in -e or -M):
alignment-faults                                   [Software event]
bpf-output                                         [Software event]
cgroup-switches                                    [Software event]
context-switches OR cs                             [Software event]
cpu-clock                                          [Software event]
cpu-migrations OR migrations                       [Software event]
dummy                                              [Software event]
emulation-faults                                   [Software event]
major-faults                                       [Software event]
minor-faults                                       [Software event]
page-faults OR faults                              [Software event]
task-clock                                         [Software event]
duration_time                                      [Tool event]
user_time                                          [Tool event]
system_time                                        [Tool event]
msr/pperf/                                         [Kernel PMU event]
msr/smi/                                           [Kernel PMU event]
msr/tsc/                                           [Kernel PMU event]
rNNN                                               [Raw hardware event descriptor]
cpu/t1=v1[,t2=v2,t3 ...]/modifier                  [Raw hardware event descriptor]
[(see 'man perf-list' on how to encode it)]
mem:[/len][:access]                          [Hardware breakpoint]
alarmtimer:alarmtimer_cancel                       [Tracepoint event]
alarmtimer:alarmtimer_fired                        [Tracepoint event]
alarmtimer:alarmtimer_start                        [Tracepoint event]
alarmtimer:alarmtimer_suspend                      [Tracepoint event]
amd_cpu:amd_pstate_perf                            [Tracepoint event]
avc:selinux_audited                                [Tracepoint event]
block:block_bio_backmerge                          [Tracepoint event]
block:block_bio_bounce                             [Tracepoint event]
block:block_bio_complete                           [Tracepoint event]
block:block_bio_frontmerge                         [Tracepoint event]
:...skipping...


Issue #2287 fixed

@manujain Github is reporting 1,569 files changed in this PR.  Lots of them are in the Build directory (which we don't submit) did you modify your .gitignore file?

Moved to #2569


TLT Models：yolov3  run error (jetson TX2)

when I run :./deepstream-custom -c pgie_yolov3_tlt_config.txt -i $DS_SRC_PATH/samples/streams/sample_720p.h264
Warning: 'input-dims' parameter has been deprecated. Use 'infer-dims' instead.
Now playing: pgie_yolov3_tlt_config.txt
Opening in BLOCKING MODE
Opening in BLOCKING MODE
0:00:00.206458755 10991   0x559c739b00 INFO                 nvinfer gstnvinfer.cpp:619:gst_nvinfer_logger: NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1715> [UID = 1]: Trying to create engine from model files
ERROR: [TRT]: UffParser: Validator error: FirstDimTile_2: Unsupported operation _BatchTilePlugin_TRT
parseModel: Failed to parse UFF model
ERROR: failed to build network since parsing model errors.
ERROR: Failed to create network using custom network creation function
ERROR: Failed to get cuda engine from custom library API
0:00:01.417451184 10991   0x559c739b00 ERROR                nvinfer gstnvinfer.cpp:613:gst_nvinfer_logger: NvDsInferContext[UID 1]: Error in NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1735> [UID = 1]: build engine file failed
Segmentation fault (core dumped)
What is the reason for this problem and how to solve it?

Unsupported operation _BatchTilePlugin_TRT
Please check the README to build the TRT-OSS

ok, I checked the README , and solved the problem.

Hi @mchi-zg and @zahidzqj ,
Even I am facing the same issue, have you resolved it?
Environment:
Device: Tesla T4
Cuda Version: 10.2
Tensorrt version: 7.0
Docker image: docker pull nvcr.io/nvidia/deepstream:5.0-20.07-triton
Command:
./ds-tlt -c /opt/nvidia/deepstream/deepstream-5.0/samples/deepstream_tlt_apps/configs/yolov3_tlt/pgie_yolov3_tlt_config.txt -i /opt/nvidia/deepstream/deepstream-5.0/samples/streams/sample_720p.h264 -b 2
Output Error:
WARNING: Overriding infer-config batch-size (1) with number of sources (2)
Now playing: /opt/nvidia/deepstream/deepstream-5.0/samples/deepstream_tlt_apps/configs/yolov3_tlt/pgie_yolov3_tlt_config.txt
0:00:00.737391560 396 0x563947a11610 INFO nvinfer gstnvinfer.cpp:619:gst_nvinfer_logger: NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1715> [UID = 1]: Trying to create engine from model files
ERROR: ../nvdsinfer/nvdsinfer_func_utils.cpp:33 [TRT]: UffParser: Validator error: FirstDimTile_2: Unsupported operation _BatchTilePlugin_TRT
parseModel: Failed to parse UFF model
ERROR: tlt/tlt_decode.cpp:274 failed to build network since parsing model errors.
ERROR: ../nvdsinfer/nvdsinfer_model_builder.cpp:797 Failed to create network using custom network creation function
ERROR: ../nvdsinfer/nvdsinfer_model_builder.cpp:862 Failed to get cuda engine from custom library API
0:00:00.944565439 396 0x563947a11610 ERROR nvinfer gstnvinfer.cpp:613:gst_nvinfer_logger: NvDsInferContext[UID 1]: Error in NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1735> [UID = 1]: build engine file failed
Segmentation fault (core dumped)


SYSINFO documentation fixups

Remove the double documentation for bit 15 (SYSINFO_FEATURES_HW_RST) of the SYSINFO_FEATURES register.
Add missing formatting (leading underscores) to the CPU_SYSINFO register table.

Great! :) Thanks for fixing! 👍


Design Meeting Notes, 8/30/2024

Adding Compile-Caching Entry Points
#59720

Node.js now supports V8 compilation caching.

Recent PR to Node.js to add module.enableCompilerCache().
Previously were ways to do this with 3rd party packages on npm.

Node.js doesn't do this by default, but things like ts-node does on supported versions of Node.js.
What's the downside?

You need to have require to make this work, awkward for ESM.
This is being worked on.

tsc and tsserver start up about 2.3x faster.
For executables this is a no-brainer. We can actually use import() there too.
For libraries, questionable. So the PR doesn't do it.
The PR must introduce a new entry point for the library. Is this worth the perf improvement?

Yes.
Just add a comment telling people what's going on and it's fine.

Another risk - in development we recompile over and over, and that can pollute the cache.

The files are pretty small - not a huge risk.
We can add hereby clear-node-cache.

Not going to be immediate - Node-specific work would need to be back-ported in in Node.js 22; otherwise only noticeable in Node 23+.

No more notes posts after August? :pleading_face:


Initial capture support in the matching engine.

Introduce capture instructions in the matching engine bytecode and lower capturing groups. Removes the use of legacy regex virtual machines.

@swift-ci please test Linux

All of Regex now go through the matching engine instead of the legacy VMs. I think we can defer deleting VMs to a follow up patch.

All of Regex now goes through the matching engine instead of the legacy VMs. I think we can defer deleting VMs to a follow up patch.

Ah, where is that change in this diff?  I must have missed it

@milseman It is in Core.swift (where Regex is defined).

Ah, so the DSL now always uses matching engine, cool! Did you look at porting the legacy matching tests that check for captures? I believe those are expressed using literals instead of result builders.

Yes, both the DSL and regex literals use the matching engine, since they both use the Regex type. Core.swift should be moved somewhere else (e.g. Regex/), since it's not just about the DSL.

That is, testLegacyVMs()

Ah, thanks for pointing this out! Looking into some errors now.

I didn't want to push to your branch while you're working on it or debugging something. I have simple back references added on top here: https://github.com/milseman/swift-experimental-string-processing/commit/6902f3239e46c0c662cf4809408856e3ab44bd9c, assuming the topLevelCaptures always has the right arity in it.

Can this be closed?


Check for SIGHASH_SINGLE bug in writer fn

Recently we moved the logic for checking for the SIGHASH_SINGLE bug to
the signature_hash() function. Although this left users of the
encode_signing_data_to() function without correct handling of the bug
there is not much else we can do but alert users to this behaviour.
Add documentation to highlight the behaviour of encdoe_signing_data_to
in regards to the sighash single bug. Requires updating docs for
signature_hash also.
Please note, uses non-conventional markdown header # Warning.
Closes: #817

On further reflection I think we should just document that this function does the wrong thing with the SIGHASH_SINGLE bug, and that if the user intends to care about this, they should either call signature_hash or write their own logic.
Changing an infallible function to a fallible one, without changing the type signature, seems like a bad change to make to the library.

I might've asked this already on IRC and I don't remember the answer.
What's the use case of calling encode_signing_data_to and not signature_hash?
if there's no real use case then the best solution IMHO is to make this function private

I think the original author https://github.com/rust-bitcoin/rust-bitcoin/pull/485 just made it public and nobody noticed or complained. I don't remember explicitly thinking about this ever.

Ah, great, thanks for finding this.
So -- if we added an error case, and the author has .expect()ed the output of this function, in theory this could result in his HSM being crashable from the outside, by a user providing a transaction that tries to use the SIGHASH_SINGLE bug. Contrast that with the current behavior where the HSM will harmlessly sign a bad sighash.
So I think we should just document "does the wrong thing given the sighash single bug". Maybe we should even make this explicit, by feeding #"[not a transaction] SIGHASH_SINGLE bug" into the writer or something.

Total re-write of PR including update of PR description. I built the docs and they look ok to me but please not the Warning heading is non-conventional.

ACK 83dda74ecb7e00c1a4e5726a75e4769079e588e8


Option to show a different view by default?

Would be nice if there was an option to set it to always see Text or Fernflower when you click on a file instead of always viewing the Hex :)

Hex is the default view because it is the one format (except for other formats like binary, octal, etc) in which all files can be accurately represented with no missing data. Plaintext would fail to render control codes and whatnot.
As more and more filetypes are supported, you would end up having so many different default options it would be easier just to Ctrl-T and select something.

:ok_woman:

I can sort of understand the logic behind this decision. That it would be jarring to have different default views for different file types. But I most disagree. I've been using this to do my work for SpigotMC's Premium Resource section and having to continuously select the same decompiler for thousands of class files is not only annoying, it's frustrating and inconvenient.
I respectfully ask you reconsider this decision, and expose this in some way, even if it is basic and/or hidden.

Very well. How do you envision selecting default decompilers and filetypes? If you have a preferred method I'll work with that. Otherwise I'll come up with something

I'm not terribly concerned with how it's implemented on your end. I certainly don't see any need to create some massive codebase around this feature. As far as I'm concerned it could be buried in the config file, loaded on startup, just mapping file extensions to some string for the preferred view.
Obviously that isn't terribly user-friendly. But there will always be time to make it prettier.

Thanks :+1:


Tutorial document changes to 05.md section

@nalanirojas25 you see here

We don't see you (@nalanirojas25). I can totally merge this, but you profile won't be credited as it should. You should review your local git config (in ~/.gitconfig) & check the email/username. Be sure to have this email added to your github account so github can track down the fact that it's you.

Thats weird cause its presented with nalanirojas25 on my end. Can you send me a pic of the exact location where its not saying nalanirojas25, please?

I need help with this because I really don't know why its not showing up as nalanirojas25.
These are the places I've looked to see if nalanirojas25 is the account that was used.
This is in the github committed files:

This is in the terminal:

I don't know where else to look. Some guidance would be appreciated.

To check the email used on your computer:
git config --global --includes --get user.email

(should print an email)
Now go to https://github.com/settings/emails
And check that this email is added to the list.
Alternatively, you can change the email used for the commits (email given by the git config command) by using git commit --amend option.

Okay I think I fixed it. If not, please let me know.
Thank you for helping me out with this. I appreciate your patience and help :)

It seems you didn't push your modifications. I can't see anything different from this history https://github.com/nalanirojas25/phenomic/commits/tutorial-document-changes
Can you do locally a git log and paste here at least recent commits so I can help you to see the current local state?

I think I made some improvements. This first line in the git log was a commit I did just now. I don't see changes on github though. I'm still trying to figure this out.

"Changes" are visible

This will not affect all previous commits.
One thing you could do is to do the following from your current branch

git rebase master -i (interactive git rebase)
For all commits except the one at the top of the list change "pick" (in the beginning of the line) to "f" or "fixup" (this will squash each commits with the first one, having one commit for such a change is enough)
once the rebase is finished
git commit --amend --author="Author Name<EMAIL_ADDRESS>(replace with your info).
git push --force to overwrite the entire existing history you previously pushed. PR will be adjusted automatically as soon as the branch is updated.

Did it work? It looks like it did! :)

Yes you did!


Remove magic numbers for heating systems and cooling systems

replace in first step with enumerations / constants, then maybe with classes.

e.g. in calc_Qem_ls

I just checked and it seems we moved to a solution half-way in the middle using "T1", "T2" etc. to name heating and cooling systems.
@JIMENOFONSECA, is there a good reason to do this instead of using more descriptive names?

Good? Lets discuss it on slack one day... Maybe we find a better solution..

On 03.06.2016, at 22:20, Daren Thomas<EMAIL_ADDRESS>wrote:
I just checked and it seems we moved to a solution half-way in the middle using "T1", "T2" etc. to name heating and cooling systems.
@JIMENOFONSECA, is there a good reason to do this instead of using more descriptive names?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Moving this to next milestone, as it might be solved with @gabriel-happle 's changes to the demand calculations...

@daren-thomas is it ready or still important?

@JIMENOFONSECA yes, I think it is important.

There is an issue about the interface addressing this


Randomize on reset fix

I noticed that only the knapsack-v0 environment had the randomize_on_reset attribute implemented on reset.
I added this to the other knapsack environments.
env = or_gym.make('Knapsack-vX', env_config={'randomize_params_on_reset': True})

Also in this PR:

Add .idea/ to .gitignore
Remove redundant print comment in utils | assign_env_config()
Promote the use of local variables instead of adding class attributes by raising an attribute error if a parameter in env_config is not a default attribute.
Add Knapsack-v3 to the ENV_LIST in version.py

@mandjevant Thanks so much for your contribution!


Update Cassandra chart name in example

Fix release name in chart install example

/assign @orange-cscetbon

@yaron2
Would you mind to sign DCO and bump chart to latest version? Thank you.

@yaron2 please sign off your commits and bump the chart version

@yaron2, you tried to assign it to me ?

@yaron2
Would you mind to sign DCO and bump chart to latest version?


feat(common): add a tool method encode

As title.
Close #145

This PR needs to be manually cherry-picked into the server repository afterwards, after https://github.com/apache/incubator-hugegraph/pull/2628 is merged. cc @imbajin


Removing an empty group with name "map" results in a 405 error

Setting up an empty group with the name map makes this group unremovable. If the user tries to remove it the API does return a 405 Method not allowed status without a message body.
Scenario:

Creating an empty group called map.
Destroying it.
API returns 405.

@Poltergeist I am trying to reconstruct the issue by doing following steps through API:

POST on /v2/groups with JSON: { "id": "/map" }
DELETE on /v2/groups/map

Last step yields a 200 status. Is there anything that you do differently?

Tested on Marathon master.
Could not reproduce.


how to import locally saved world

Hi there! :)
Actually no issue but i cant find the directory of my container.
I installed the server on my synology nas via docker and i really have no idea what im doing, but the server is running.
but i cant find the docker dir
Can anybody help me here? :)

I'd love to have this answer as well.

Allright so I succesfully did it in two steps:

Add a volume between a folder (You can create one for Enshrouded specifically) and /home/steam/enshrouded/savegame

Use the File Station app to copy your save game to this new folder:

Allright so I succesfully did it in two steps:

Oh, great, thx a lot!

Hello. I'm in the same situation. I set up the server on a Synology NAS yesterday and the server started. But where does it save the server game files? The folder I mounted only contains compose.yaml. In which folder does the server save all the other files? I also created a separate subfolder “save” where I wanted to copy the save games.

@TFidk,
The docker-compose file in Readme uses persistent storage on volume.
To save data on disk of host system, you can bind it to host's path.
Alternatively, you can upload your saves into volume.

@riuson: Hello and thanks for your fast reply. I'm still very new to the Docker segment. Where can I find this folder? I can't find it in the Synology DS file.

Down container (not stop or restart).
Change compose to
version: '3'
services:
  enshrouded:
    image: sknnr/enshrouded-dedicated-server:latest
    ports:
      - "15636:15636/udp"
      - "15637:15637/udp"
    environment:
      - SERVER_NAME=Enshrouded Containerized
      - SERVER_PASSWORD=PleaseChangeMe
      - GAME_PORT=15636
      - QUERY_PORT=15637
      - SERVER_SLOTS=16
      - SERVER_IP=<IP_ADDRESS>
    volumes:
      - ./data:/home/steam/enshrouded/savegame

Make directory near it:
mkdir ./data
chown 10000:10000 ./data

And up again.

OK, I'll try that. I managed to get it to save the so-called persistent data in a folder I specified. Is that a reflection of the current server status?

I managed

How?

I created a folder to which he has access rights. Then in compose I changed the line in which he wanted to save the persistent data to the folder I assigned. I hope that's not wrong.

If you have changed lines as I have specified before
- ./data:/home/steam/enshrouded/savegame

then this folder should contain saves of game world.

I changed to following line:

How often will he make a backup or do I have to do it manually? I assume that if something changes in the game world, who will save it again at some point?

On my server - with interval 10 minutes:
savegame$ ls -la
total 12648
drwxr-xr-x 1 10000 10000     250 Dec 11 12:18 .
drwxr-xr-x 1 10000 10000    2080 Dec  7 00:19 ..
-rw-r--r-- 1 10000 10000 1292672 Dec 11 10:48 3ad85aea
-rw-r--r-- 1 10000 10000 1292762 Dec 11 10:58 3ad85aea-1
-rw-r--r-- 1 10000 10000 1292719 Dec 11 11:08 3ad85aea-2
-rw-r--r-- 1 10000 10000 1292723 Dec 11 11:18 3ad85aea-3
-rw-r--r-- 1 10000 10000 1292765 Dec 11 11:28 3ad85aea-4
-rw-r--r-- 1 10000 10000 1292792 Dec 11 11:38 3ad85aea-5
-rw-r--r-- 1 10000 10000 1292721 Dec 11 11:48 3ad85aea-6
-rw-r--r-- 1 10000 10000 1292765 Dec 11 11:58 3ad85aea-7
-rw-r--r-- 1 10000 10000 1292670 Dec 11 12:08 3ad85aea-8
-rw-r--r-- 1 10000 10000 1292712 Dec 11 12:18 3ad85aea-9
-rw-r--r-- 1 10000 10000      56 Dec 11 12:18 3ad85aea-index
-rw-r--r-- 1 10000 10000     319 Jan 29  2024 3ad85aea_info

I haven't found how to change this setting.


NTRN-260 slinky bindings (market map & oracle)

Bindings for neutron. Slinky-related
Oracle:

GetPrice
GetAllCurrencyPairs

Marketmap:

Params
MarketMap
LastUpdated

Main PR:
https://github.com/neutron-org/neutron/pull/508

https://github.com/neutron-org/neutron-tests/actions/runs/9104146345


Show more missing in month view after resize

Hi, after window height resize show more link disappear.
Video of the behavior: https://monosnap.com/file/ywFs8eLS0IGzlEEwL7lf3fKz9Yx0R7. (Look at Saturday 20th)
class EventEndingRow extends React.Component {
  render() {
    let {
      segments,
      slotMetrics: { slots },
    } = this.props
    let rowSegments = eventLevels(segments).levels[0] <---- why we get eventLevels and use only the first level ?!

    let current = 1,
      lastEnd = 1,
      row = []

    while (current <= slots) {
      let key = '_lvl_' + current

      let { event, left, right, span } =
        rowSegments.filter(seg => isSegmentInSlot(seg, current))[0] || {} //eslint-disable-line

      if (!event) {
        current++
        continue
      }

I think the problem is that we filter rowSegments array instead of of segments.
Version: 0.22.0

We're having the same issue. After a resize on month view, the more button is missing. Has anyone else seen this?

Yes, same here. Looks like the logic for showing the show more button is only applied on first render. There is a state bool flag which controlls that behavior in MonthView, but no idea how to get to that.


Can you provide release note?

Today I find my env:
 - Removing vlucas/phpdotenv (v2.0.1)
 - Installing vlucas/phpdotenv (v2.1.0)

But i don't know if there any bc changes...

But i don't know if there any bc changes...

We follow semver, so no breaking changes.

Major releases are breaking, minor are new feature, or just more significant changes, and patch are bug fixes or cleanup type things.


Use Drag and Drop with the angular2 DxDataGrid

Hi,
We are using 16.1 of the devextreme suite and would like to use drag drop to reorder rows within the DxDataGrid. The following example from your site shows this using knockout, how would we achieve the same behaviour with angular2?
https://www.devexpress.com/Support/Center/Example/Details/T152596
Thanks, Jon.

Hello,
I am following on the question raised above, could you please clarify regarding the angular support?
Thanks
Nilesh

The approach mentioned in the ticket does not depend on the approach you are using to create our widgets. The main idea is to create a data source that will have a field against which records will be sorted. Then, the jQuery UI draggable and droppable widgets are applied to a grid row. When you drop a grid row to another row, the field used to sort rows is updated. As a result, the grid updates its row indexes according to that field.

I've prepared the Plunker to illustrate this.

Hi GoshaFighten,
The plunker example has jQuery  function (initDragging($gridElement: JQuery)) which works directly with the DOM to reorder when items are dragged up/down. Is there a pure Angular2/TypeScript way of doing this without using jQuery?
Thanks
Nilesh

@nileshdudhal
I'm not sure. I suggest you google for such existing libraries or create your own.


Clarification for NonlinearFormIntegrator

I'm still unsure about a few points regarding a NonlinearFormIntegrator. Consider the equation
H(u) = f

with H(u) = u^2, for which i'd need to implement an element vector and gradient assemble. Looking at DomainLFIntegrator, i could basically copy the assemble and modify the coefficient to be the actual function at the element (the argument is already there but i'm not sure if its intended for that). This looks like
void ReactionNLFIntegrator::AssembleElementVector(const FiniteElement &el,
                                                  ElementTransformation &Tr,
                                                  const Vector &elfun,
                                                  Vector &elvect) {
  int dof = el.GetDof();
  shape.SetSize(dof);
  elvect.SetSize(dof);
  elvect = 0.0;

  const IntegrationRule *ir =
      &IntRules.Get(el.GetGeomType(), 2 * el.GetOrder() + Tr.OrderW());

  for (int i = 0; i < ir->GetNPoints(); i++) {
    const IntegrationPoint &ip = ir->IntPoint(i);
    el.CalcShape(ip, shape);
    Tr.SetIntPoint(&ip);

    double w = Tr.Weight() * elfun(i) * elfun(i);

    add(elvect, ip.weight * w, shape, elvect);
  }
}

Is elfun the function value at the current newton step?
The next part would be the Jacobian. If i use the Gateaux derivative i arrive at
J(u, du, v) = limit((H(u+epsilon*du,v)-H(u,v))/epsilon, epsilon, 0)
J(u, du, v) = 2 * u * du * v

with v being the test function. So i would use the structure of the MassIntegrator (Bilinearform) and get
void ReactionNLFIntegrator::AssembleElementGrad(const FiniteElement &el,
                                                ElementTransformation &Tr,
                                                const Vector &elfun,
                                                DenseMatrix &elmat) {
  int dof = el.GetDof();
  shape.SetSize(dof);
  elmat.SetSize(dof);
  elmat = 0.0;

  const IntegrationRule *ir =
      &IntRules.Get(el.GetGeomType(), 2 * el.GetOrder() + Tr.OrderW());

  for (int i = 0; i < ir->GetNPoints(); i++) {
    const IntegrationPoint &ip = ir->IntPoint(i);
    el.CalcShape(ip, shape);
    Tr.SetIntPoint(&ip);

    double w = Tr.Weight() * 2.0 * elfun(i);

    AddMult_a_VVt(ip.weight * w, shape, elmat);
  }
}

Using the resulting Integrator with the NewtonSolver doesn't converge, so i'm assuming i made an error in defining the element vector and/or gradient.
For reference, this is how i call the newton solver. forcing_coeff is a function callback which returns a sin(pi*x), which fits into the setting regarding boundary conditions (0 on the ends on a 1D line from 0 to 1).
  GridFunction forcing(h1_fespace);
  forcing.ProjectCoefficient(forcing_coeff);

  newton_solver->Mult(forcing, u_gf);

If you're unsure of the Jacobian, you can use PetscNonlinearSolver and
compute the Jacobian from finite differencing for comparison. See
http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESComputeJacobian.html
Il 21 Mar 2017 9:18 PM, "Julian Andrej"<EMAIL_ADDRESS>ha
scritto:

I'm still unsure about a few points regarding a NonlinearFormIntegrator.
Consider the equation
H(u) = f
with H(u) = u^2, for which i'd need to implement an element vector and
gradient assemble. Looking at DomainLFIntegrator, i could basically copy
the assemble and modify the coefficient to be the actual function at the
element (the argument is already there but i'm not sure if its intended for
that). This looks like
void ReactionNLFIntegrator::AssembleElementVector(const FiniteElement &el,
ElementTransformation &Tr,
const Vector &elfun,
Vector &elvect) {
int dof = el.GetDof();
shape.SetSize(dof);
elvect.SetSize(dof);
elvect = 0.0;
const IntegrationRule *ir =
&IntRules.Get(el.GetGeomType(), 2 * el.GetOrder() + Tr.OrderW());
for (int i = 0; i < ir->GetNPoints(); i++) {
const IntegrationPoint &ip = ir->IntPoint(i);
el.CalcShape(ip, shape);
Tr.SetIntPoint(&ip);
double w = Tr.Weight() * elfun(i) * elfun(i);

add(elvect, ip.weight * w, shape, elvect);

}
}
Is elfun the function value at the current newton step?
The next part would be the Jacobian. If i use the Gateaux derivative i
arrive at
J(u, du, v) = limit((H(u+epsilon*du,v)-H(u,v))/epsilon, epsilon, 0)
J(u, du, v) = 2 * u * du * v
with v being the test function. So i would use the structure of the
MassIntegrator (Bilinearform) and get
void ReactionNLFIntegrator::AssembleElementGrad(const FiniteElement &el,
ElementTransformation &Tr,
const Vector &elfun,
DenseMatrix &elmat) {
int dof = el.GetDof();
shape.SetSize(dof);
elmat.SetSize(dof);
elmat = 0.0;
const IntegrationRule *ir =
&IntRules.Get(el.GetGeomType(), 2 * el.GetOrder() + Tr.OrderW());
for (int i = 0; i < ir->GetNPoints(); i++) {
const IntegrationPoint &ip = ir->IntPoint(i);
el.CalcShape(ip, shape);
Tr.SetIntPoint(&ip);
double w = Tr.Weight() * 2.0 * elfun(i);

AddMult_a_VVt(ip.weight * w, shape, elmat);

}
}
Using the resulting Integrator with the NewtonSolver doesn't converge, so
i'm assuming i made an error in defining the element vector and/or gradient.
For reference, this is how i call the newton solver. forcing_coeff is a
function callback which returns a sin(pi*x), which fits into the setting
regarding boundary conditions (0 on the ends on a 1D line from 0 to 1).
GridFunction forcing(h1_fespace);
forcing.ProjectCoefficient(forcing_coeff);
newton_solver->Mult(forcing, u_gf);
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mfem/mfem/issues/160, or mute the thread
https://github.com/notifications/unsubscribe-auth/AE4lAQMGOlVh8LpaLTAKFbpAqVQdiSW8ks5roBRegaJpZM4MkNgX
.

In the Assemble...() functions, elfun are the values at the degrees of freedom, not at the quadrature points.

Thanks for the clarification. So for the residual/gradient assemble i would need the values at the quadrature points? Or do i have to do some different operation with the elfun values?

Yes, you need to use the function values at the quadrature points (you iterate over quadrature points). In the above code, these values would be the inner products (shape * elfun).

Would this be correct? (I didn't understand the part with the inner product in your last message)
  Vector fun_val(dof);
  fun_val = shape * elfun;
  double w = Tr.Weight() * fun_val(i) * fun_val(i);
  add(elvect, ip.weight * w, shape, elvect);

I proceeded similarly with the gradient and the residual decreases
Newton iteration  7 : ||r|| = 0.255388
Newton iteration  8 : ||r|| = 0.0244531
Newton iteration  9 : ||r|| = 0.00552096
Newton iteration 10 : ||r|| = 0.0188555

But still doesn't converge

From the definition of a finite element function, you need to compute
u(q_i) = sum_{j=1..#dofs} elfun_j shape_j(q_i).
That's the inner product part.
So try double fun_val = shape * elfun;
[ I'm not sure why you aren't getting segfaults for that indexing ]

Sure that makes more sense. I just checked and the code is valgrind clean (after the change). There is still the problem with the oscillating and non converging residual of the newton solver. The inner solves seem to be just fine
MINRES: iteration  18: ||r||_B = 2.87843e-10

Try it with H(u) = u.

That won't converge either. The solution somehow looks like if it is going in the right direction with huge oscillations on top. If that does help :-/

Is this H(u) = u? The screenshot shows that the gradient is still 2u :)

You are right, the screenshot is again the H(u) = u^2 case. The H(u) = u converges better but also oscillates somehoe.

Now the Newton solver is behaving correctly, but something is wrong with your visualization. What are you plotting?

I intend to plot the solution from the gridfunction (u_gf)
  GridFunction u_gf(h1_fespace);
  // u_gf.Randomize();
  u_gf = 1.0;

  FunctionCoefficient forcing_coeff(MMS);
  GridFunction forcing(h1_fespace);
  forcing.ProjectCoefficient(forcing_coeff);

  newton_solver->Mult(forcing, u_gf);

  double err = u_gf.ComputeL2Error(exact_sol_coeff);
  std::cout << "\nL2 norm of error: " << err << std::endl;

  socketstream sol_sock;
  char vishost[] = "localhost";
  int visport = 19916;
  sol_sock.open(vishost, visport);
  sol_sock.precision(8);
  sol_sock << "solution\n" << *mesh << u_gf << std::flush;
  sol_sock << "keys "
	   << "ac" << std::endl;

Plot forcing and see it it's correct.

The forcing is correct (perfect sin(a*x) or whatever i choose it to be)

I think you should do RHS_i = integral ( f(x) phi_i(x) ) instead of RHS_i = f(x_i).

Isn't that what ProjectCoefficient is doing? Otherwise it wouldn't display a smooth curve in glvis when plotting "forcing".
Also ProjectCoefficient calls FiniteElement::Project which is most of the time an inner product.


Implement spiral algorithm in Advanced

We need to implement the spiral reading algorithm for the advanced tool. In a grid as shown below:
s s e m l
a i s i a
g s T h r
e a s p i

This will be given to us as ssemlaisiagsThreaspi and can be decoded to "This is a spiral message" when the algorithm is applied in counter-clockwise fashion. This needs to be applied in clockwise fashion as well.

Does the reading start from the center or one of the edges? @Kulendra

Reading can begin from a corner or the center.
However, reading from center will be identical to reading from a corner and reversing it.
Note that the reading will always begin from a corner, not from the middle of an edge.
The matrix/box that is drawn to spiral could be a square OR a rectangle.
Reading can be done clockwise or counterclockwise.

The matrix/box that is drawn to spiral could be a square OR a rectangle.
This basically refers to checking string.length against square and triangular numbers, right? This might require another function to match against known square and triangular numbers.

Not necessary to implement a new function. array factors(string) returns an array of integer factorisations possible. It also returns the full string length as a single element if it is not possible to factorise (i.e. string length is a prime).

Will factors work? The multiplications of a known triangular number won't be triangular numbers, right?

The math for this hurts my head :P I'm just going to write a load of loops and conditions

Ah, didn't notice it was rectangular. Disregard my earlier comment. :sweat_smile:

This is resolved now. Spiral algo is implemented.

Closing as per comment above.


Expect.toContains() with if ...else if...else

want to differentiate some values from list into different different arrays
like $ 1 B , $ 2 B , $ 100 M ,$ 300 M , $ 105 K , $ 205 K
so i tried it with expect.toContain('') method
var ele = element.all(by.css('.company-network-list__header__income.ng-scope .ng-binding.ng-scope'));
var b =[] , m=[], k=[];
ele.map(function(eachName) {
	return eachName.getText().then(function(unSorted) {
if(expect(unSorted).toContain('B')){
     var b = unSorted;
}
else if(expect(unSorted).toContain('M')){
   var m = unSorted;
}
else{
  var k = unSorted;
}
});
});

for 2 values ..i tried with try catch
try{
	expect(unSorted).toContain('B');
	var b = unSorted;
    }catch(e) {
	var m = unSorted;
   }

also this....
expect(unSorted).toContain('B').then(function(result) {
       if(result){
           var b= unSorted;
       }else {
             var m= unSorted;
      }
});

Not working anything from these
Can anyone please help me to solve this issue

I want to differentiate some values from list into different different arrays
like $ 1 B , $ 2 B , $ 100 M ,$ 300 M , $ 105 K , $ 205 K
so i tried it with expect.toContain('') method
var ele = element.all(by.css('.company-network-list__header__income.ng-scope .ng-binding.ng-scope'));
var b =[] , m=[], k=[];
ele.map(function(eachName) {
return eachName.getText().then(function(unSorted) {
if(expect(unSorted).toContain('B')){
var b = unSorted;
}
else if(expect(unSorted).toContain('M')){
var m = unSorted;
}
else{
var k = unSorted;
}
});
});
for 2 values ..i tried with try catch
try{
expect(unSorted).toContain('B');
var b = unSorted;
}catch(e) {
var m = unSorted;
}
also this....
expect(unSorted).toContain('B').then(function(result) {
if(result){
var b= unSorted;
}else {
var m= unSorted;
}
});
Not working anything from these
Can anyone please help me to solve this issue

@hitesh-jani
First, like you have on your post: "Make sure you are not asking a usage or debugging question. If you are, use StackOverflow, Google Group discussion list, or Gitter to get help." this is a question not a protractor issue.
Trying to help you before this issue gets closed, I don't think expect() should be used in if...else clauses.. The expect() is an assertion.
Picking your first example, I don't understand why you define var b = [] and then in the if you redefine it with different type (var b = string).
Give it a try this way:
var ele = element.all(by.css('.company-network-list__header__income.ng-scope .ng-binding.ng-scope'));
var b =[] , m=[], k=[];
ele.each(function(eachName) {
eachName.getText().then(function(unSorted) {
if(unSorted === 'B'){
b.push(unSorted);
}
else if(unSorted ==='M'){
m.push(unSorted);
}
else{
k.push(unSorted);
}
});
});
Hope it helps and don't forget to use StackOverflow for future questions.

@marleitao
Thanks for the help . I will take care of your points next time
but one last question regarding your answer
if(unSorted === 'B')
this will compare $ 1 B to B which will always wrong in this case..
how can i check if unSorted has 'B' in the string then do b.push(unSorted)?

You are right, missed the toContain() part..
Use:
if (unSorted.indexOf('B') > -1);
Google will help you for future js queries ;)

Thanks again
Sure :)

@marleitao thanks so much for jumping in and talking about this! Really appreciate your work in the queue 😄
I'm going to go ahead and close this since it is a usage/debugging questions and is a better fit for Gitter/SO. Cheers everyone!


Add support for IN2, additional mappings for IN1

Add additional fields for Coverage / RelatedPerson from IN2 record.
IN2.2 (SSN) to RelatedPerson.identifier
IN2.63 to RelatedPerson.telecom
IN2.72 as backup relationship for IN1.17.
NOTE: special rules apply for interpreting the direction of the relationship as input and mapping to the direction of the relationship expected by the FHIR field.
Interested parties should read detailed notes in v2ToFhirMapping.yml IMPORTANT NOTES ON RELATIONSHIP MAPPINGS

Coverage.identifier from IN2-6

Coverage.identifier.type:
system= http://terminology.hl7.org/CodeSystem/v2-0203
code=MC
display=Patient's Medicare number

Coverage.identifier from IN2-8

Coverage.identifier.type:
system= http://terminology.hl7.org/CodeSystem/v2-0203
code=MA
display=Patient Medicaid number

Coverage.identifier from IN2-61 which will take precedence over IN1-36.

Coverage.identifier.type:
code='MB'
display='Member Number'
system='http://terminology.hl7.org/CodeSystem/v2-0203'

IN1.35 to Organization.identifier. This identifier will have a value only, no system or type. (PR A)
Coverage.payor create a separate Organization from IN2.25

IN2.25.1 is used to set Organization.id.

If a tenant is set, the id value should be .<IN2-25.1>
If a tenant is not set, the id value will be just IN2-25.1

Organization.identifier using

.1 identifier.value
.4 identifier.system (urn:id:25.4)
.5 identifier.type.code
.7 identifier.period.start
.8 identifier.period.end

Organization.name using IN2.25.1 identifier.value. BJC: current code requires a name. L4H Converter Issue 422 will remove this requirement in the future.
Coverage.policyHolder create a separate Organization from IN2.69
IN2.69.10 is used to set Organization.id.

If a tenant is set, the id value should be .<IN2-69.10>
If a tenant is not set, the id value will be just IN2-69.10
Organization.identifier using

.10 identifier.value
.6 identifier.system (urn:id:69.6)
.7 identifier.type.code
IN2.69.1 is used to set Organization.name

RelatedPerson should only be created when the subscribed is a relative.  (Not an employer)
Patient.identifier from IN1.49
if subscriber=self, use IN2.2 as fallback to populate SSN patient identifier if PID-19 is empty
IN2.6 to Patient.identifier.type.coding.code=MC
IN2.8 to Patient.identifier.type.coding.code=MA
If subscriber=self, use IN2-61 for Patient.identifier.type.coding.code=MB, fallback to IN1-36:

In release 1.0.16


Minor Improvements

After having had a short look at cargo-check, I immediately found it incredibly useful. While staring at the code, I made some improvements that might be more idiomatic Rust. It's quite amazing how much simpler the tests have become now.
As I am still a beginner, please be sure to review the code thoroughly. At least it works both when testing automatically and manually.
Cheers

You can watch the development stream on youtube.
Looksies #7 [Let's look at the cargo-check]
[!thumb](https://youtu.be/DQ8W8gWK-3k)

:+1:
Thank you


I am getting an error trying to use PINCH to rotate the map using Resium

Hi @erikhansenmujica. Resium is not an official cesium component. I would suggest opening a report with the Resium maintainers to get to the bottom of the issue. If it turns out to be a possible bug in CesiumJS, then please post back here with instructions to duplicate using the CesiumJS API. Sandcastle is a good way to share examples. Thanks!


How is issue-pr working ?

There is no column in API containing the data for PRs, then how is it showing it.
For eg :- https://img.shields.io/github/issues-pr/iiitv/ChefLib.svg

Hi! Here is the code that handles that.
If that doesn't answer your question, please reopen!


Feature: Expanded image view

Eigen loads in images nicely but there's no interaction available to expand to view or interact with any context menu. It would be great to get expanded views of images.

I agree, what options would you hope to have in the context menu? Right now I'm thinking of "copy" and "save to disk"

Yeah, I would say copy and save are really all you need for the time being