No release information

I'm trying to get the first use username/password hash set, but it's not working, I can see from the commit history this was only added to the chart in mid April, how can I see the release or chart version this update made it in to?

I'm guessing as 2021.2.5647 was out on the 12th of April and the chart didn't get updating until the 15 that I didn't make the cut. Would be useful to be able to see what commits are in what release though.

Thanks for the note! We're just getting the release process for this chart nailed down, now; we'll make sure to signal the contents of the next one (2021.3.x) somewhere conspicuous 👍


Add an --only-problematic flag and use multiple resolvers

Hi.
This tool is very interesting.
I am very happy that this store is being maintained.
I have a small opinion.
1.first time
As far as I know, the current option does not have an option that only shows the problem.
So, the user have to execute all the results and check them out.
This reduces efficiency. For priority, I wish I had the option to view the problematic files.

second time

It is now seen as using a local resolvers.txt
However, it would be good to support multiple resolvers if you check for a large amount of domains. Because many requests can be blacklisted.
What do you think?
Thanks.

For 1: I'd agree having an --only-problematic flag in which it only outputted problematic results would be great.
For 2:  To clarify, do you mean the use of the hard-coded DNS_WATCH_RESOLVER used when NS results don't have glue records? I'd be happy to add more and make it so that it chooses one at random. (/ Maybe add an --only-dns-watch-resolver flag for those that wanted to preserve the originally behavior.)
https://github.com/mandatoryprogrammer/TrustTrees/blob/e1b04aba8c8c119f792c7e63285feb466e181941/trusttrees.py#L659
An additional thing I'd like to add to this public repo, but have been to busy with another project recently to addd, are functions that another package can call, that return all problematic results. This makes it so that you can have your e.g. parse domains out of your Terraform repo package call TrustTrees and alert on results :)
Passing AWS credentials to TrustTrees and a bucket/prefix to upload the pngs to an S3 bucket would also be a good feature, in case you made e.g. Jira tickets with the alerts, and wanted to link an S3 signed URL or something, to make the graph easily viewable outside of the box TrustTrees is running on.

Thank you for your prompt reply.

Yes. We'll be able to identify the problem quickly.

Yes. many DNS scan tools receive a resolvers in the form of a file format.
For example, the Massdns tool.

./bin/massdns -r lists/resolvers.txt   (-r option)

The function you said would be very good.  :)

Thanks for making this issue @oldesec!
https://github.com/mandatoryprogrammer/TrustTrees/commit/0fbf2dcaeb7f95896c1993ebe7e19eba8d8f5e49 and https://github.com/mandatoryprogrammer/TrustTrees/commit/bfe5dd1f3f03bff61ca517ee7f776dbbd18c5683 should added this functionality 🎉
I'll close this issue when I release a new version.

I'll close this issue when I release a new version.

Whoops, should have closed this a while back. Thank you so much for making this issue!
We now have only 2 GitHub issues 🎉 🎊


ssh: enable TCP and SSH-level keepalives by default

In order to eventually support #76, SSH connections should have sane defaults, where one or both of TCP keepalive should be enabled, alongside ServerAliveCount and ServerAliveInternal.
Reasonable defaults for the app-level keepalives might be something like interval=15 seconds, count=6, which would disconnect a context only after it has gone AWOL for 90 seconds, but this might be too aggressive, and cause instability for short network outages. At interval=30 seconds, disconnect would only happen after 3 minutes.

App-level keepalive is fine, TCP is overkill


How to config auto fix on save?

I need this feature.
Please help.

I've added a FAQ section in the readme about that: https://github.com/sublimelsp/LSP-stylelint#faq


[help]How to get the TraceId?

I developed a SDK.jar, and in this jar how to get a Span's traceId？Cloud you tell me a better way？

If you think you need to develop a plug-in take a look at our plug-in development guide

@yanpeng-ali  you can add a util class which holds the  TraceContext instance in bootrap-core module. Since pinpoint append all bootstrap jar to bootstrap classloader, so you can access this util class in your SDK.  then you can the TraceContext instance


No way to maximize deephaven.ui dashboards

Deephaven: 0.35
Plugin: 1.3.0 pre
Testing is based off of this blog:  https://deephaven.io/blog/2024/05/06/announcing-dhui/#get-started-with-deephavenui
Run deephaven via:
docker run --rm --name deephaven-ui -p 10000:10000 --pull=always ghcr.io/deephaven/server-ui:latest

Run this code:
from deephaven import ui, agg, empty_table

from deephaven.stream.table_publisher import table_publisher
from deephaven.stream import blink_to_append_only

from deephaven.plot import express as dx
from deephaven import updateby as uby
from deephaven import dtypes as dht

stocks = dx.data.stocks().reverse()

def set_bol_properties(fig):
    fig.update_layout(showlegend=False)
    fig.update_traces(fill="tonexty", fillcolor='rgba(255,165,0,0.08)')

@ui.component
def line_plot(
        filtered_source,
        exchange, window_size, bol_bands):

    window_size_key = {
        "5 seconds": ("priceAvg5s", "priceStd5s"),
        "30 seconds": ("priceAvg30s", "priceStd30s"),
        "1 minute": ("priceAvg1m", "priceStd1m"),
        "5 minutes": ("priceAvg5m", "priceStd5m")}
    # 90th, 95th, 97.5th, and 99.5th percentiles of a standard normal distribution
    bol_bands_key = {"None": None, "80%": 1.282, "90%": 1.645, "95%": 1.960, "99%": 2.576}

    base_plot = ui.use_memo(lambda: (
        dx.line(filtered_source, x="timestamp", y="price", by="exchange" if exchange == "All" else None,
        unsafe_update_figure=lambda fig: fig.update_traces(opacity=0.4))
    ), [filtered_source, exchange])

    window_size_avg_key_col = window_size_key[window_size][0]
    window_size_std_key_col = window_size_key[window_size][1]

    avg_plot = ui.use_memo(lambda: dx.line(filtered_source,
        x="timestamp", y=window_size_avg_key_col,
        color_discrete_sequence=["orange"],
        labels={window_size_avg_key_col: "Rolling Average"}),
        [filtered_source, window_size_avg_key_col]
    )

    bol_bands_key_col = bol_bands_key[bol_bands]

    bol_plot = ui.use_memo(lambda: (
        dx.line(filtered_source \
            .update([
                f"errorY={window_size_avg_key_col} + {bol_bands_key_col}*{window_size_std_key_col}",
                f"errorYMinus={window_size_avg_key_col} - {bol_bands_key_col}*{window_size_std_key_col}",
            ]),
        x="timestamp", y=["errorYMinus", "errorY"],
        color_discrete_sequence=["rgba(255,165,0,0.3)", "rgba(255,165,0,0.3)"],
        unsafe_update_figure=set_bol_properties)
        if bol_bands_key_col is not None else None
    ), [filtered_source, window_size_avg_key_col, window_size_std_key_col, bol_bands_key_col])

    plot = ui.use_memo(lambda: dx.layer(base_plot, avg_plot, bol_plot), [base_plot, avg_plot, bol_plot])

    return ui.panel(plot, title="Prices")

@ui.component
def full_table(source):
    return ui.panel(source, title="Full Table")

@ui.component
def filtered_table(source, exchange):
    if exchange == "All":
        return ui.panel(source \
            .drop_columns([
                "priceAvg5s", "priceStd5s", "priceAvg30s", "priceStd30s",
                "priceAvg1m", "priceStd1m", "priceAvg5m", "priceStd5m"]) \
            .reverse(), title="Filtered Table")
    return ui.panel(source \
        .drop_columns([
            "priceAvg5s", "priceStd5s", "priceAvg30s", "priceStd30s",
            "priceAvg1m", "priceStd1m", "priceAvg5m", "priceStd5m"]) \
        .where(f"exchange == `{exchange}`")
        .reverse(), title="Filtered Table")

@ui.component
def parameters_panel(
        symbols,
        exchanges,
        symbol, set_symbol,
        exchange, set_exchange,
        window_size, set_window_size,
        bol_bands, set_bol_bands):

    symbol_picker = ui.picker(
        *symbols,
        label="Symbol",
        on_selection_change=set_symbol,
        selected_key=symbol,
    )
    exchange_picker = ui.picker(
        *exchanges,
        label="Exchange",
        on_selection_change=set_exchange,
        selected_key=exchange,
    )
    window_size_selector = ui.button_group(
        ui.button("5 seconds", variant="accent" if window_size == "5 seconds" else None, on_press=lambda: set_window_size("5 seconds")),
        ui.button("30 seconds", variant="accent" if window_size == "30 seconds" else None, on_press=lambda: set_window_size("30 seconds")),
        ui.button("1 minute", variant="accent" if window_size == "1 minute" else None, on_press=lambda: set_window_size("1 minute")),
        ui.button("5 minutes", variant="accent" if window_size == "5 minutes" else None, on_press=lambda: set_window_size("5 minutes")),
        margin_x=10
    )
    bolinger_band_selector = ui.button_group(
        ui.button("None", variant="accent" if bol_bands == "None" else None, on_press=lambda: set_bol_bands("None")),
        ui.button("80%", variant="accent" if bol_bands == "80%" else None, on_press=lambda: set_bol_bands("80%")),
        ui.button("90%", variant="accent" if bol_bands == "90%" else None, on_press=lambda: set_bol_bands("90%")),
        ui.button("95%", variant="accent" if bol_bands == "95%" else None, on_press=lambda: set_bol_bands("95%")),
        ui.button("99%", variant="accent" if bol_bands == "99%" else None, on_press=lambda: set_bol_bands("99%")),
        margin_x=10
    )

    return ui.panel(
        ui.flex(
            ui.flex(
                symbol_picker,
                exchange_picker,
                gap="size-200"
            ),
            ui.flex(
                ui.text("Window size:"),
                ui.flex(window_size_selector, direction="row"),
                gap="size-100",
                direction="column"
            ),
            ui.flex(
                ui.text("Bolinger bands:"),
                ui.flex(bolinger_band_selector, direction="row"),
                gap="size-100",
                direction="column"
            ),
            margin="size-200",
            direction="column",
            gap="size-200"
        ),
        title="Parameters"
    )

@ui.component
def orderbook_panel(symbols):

    symbol, set_symbol = ui.use_state("")
    size, set_size = ui.use_state(0)

    blink_table, publisher = ui.use_memo(
        lambda: table_publisher(
            "Order table", {"sym": dht.string, "size": dht.int32, "side": dht.string}
        ),
        [],
    )
    t = ui.use_memo(lambda: blink_to_append_only(blink_table), [blink_table])

    def submit_order(order_sym, order_size, side):
        publisher.add(
            empty_table(1).update(
                [f"sym=`{order_sym}`", f"size={order_size}", f"side=`{side}`"]
            )
        )

    def handle_buy(_):
        submit_order(symbol, size, "buy")

    def handle_sell(_):
        submit_order(symbol, size, "sell")

    symbol_picker = ui.picker(
        *symbols,
        label="Symbol",
        label_position="side",
        on_selection_change=set_symbol,
        selected_key=symbol
    )
    size_selector = ui.number_field(
        label="Size",
        label_position="side",
        value=size,
        on_change=set_size
    )

    return ui.panel(
        ui.flex(
            symbol_picker,
            size_selector,
            ui.button("Buy", on_press=handle_buy, variant="accent", style="fill"),
            ui.button("Sell", on_press=handle_sell, variant="negative", style="fill"),
            gap="size-200",
            margin="size-200",
            wrap=True,
        ),
        t,
        title="Order Book"
    )

@ui.component
def my_layout(source, source_with_stats):

    # lists of symbols and exchanges will inform drop-down selectors
    symbols = ui.use_column_data(source.agg_by(agg.unique(cols="sym"), by="sym"))
    exchanges = ui.use_column_data(source.agg_by(agg.unique(cols="exchange"), by="exchange"))
    exchanges.append("All")

    # state variables
    symbol, set_symbol = ui.use_state(symbols[0])
    exchange, set_exchange = ui.use_state("All")
    window_size, set_window_size = ui.use_state("30 seconds")
    bol_bands, set_bol_bands = ui.use_state("90%")

    # use state variables to par down source table before sending off to other functions
    single_symbol = ui.use_memo(lambda: (
            source_with_stats \
                .where([f"sym == `{symbol}`"]) \
                .drop_columns([
                    "priceAvg5s", "priceStd5s", "priceAvg30s", "priceStd30s",
                    "priceAvg1m", "priceStd1m", "priceAvg5m", "priceStd5m"]) \
                .rename_columns([
                    "priceAvg5s=priceAvg5sAvg", "priceStd5s=priceStd5sAvg",
                    "priceAvg30s=priceAvg30sAvg", "priceStd30s=priceStd30sAvg",
                    "priceAvg1m=priceAvg1mAvg", "priceStd1m=priceStd1mAvg",
                    "priceAvg5m=priceAvg5mAvg", "priceStd5m=priceStd5mAvg"])
            if exchange == "All" else
                source_with_stats \
                    .where([f"sym == `{symbol}`", f"exchange == `{exchange}`"]) \
                    .drop_columns([
                        "priceAvg5sAvg", "priceStd5sAvg", "priceAvg30sAvg", "priceStd30sAvg",
                        "priceAvg1mAvg", "priceStd1mAvg", "priceAvg5mAvg", "priceStd5mAvg"]) \
        ), [symbol, source_with_stats]
    )

    return ui.row(
        ui.column(
            line_plot(
                single_symbol, exchange, window_size, bol_bands
            ),
            ui.stack(
                full_table(source),
                filtered_table(single_symbol, exchange),
            ),
            width=65
        ),
        ui.column(
            ui.row(
                parameters_panel(
                    symbols, exchanges,
                    symbol, set_symbol,
                    exchange, set_exchange,
                    window_size, set_window_size,
                    bol_bands, set_bol_bands
                ),
                height=40
            ),
            ui.row(
                orderbook_panel(symbols),
                height=60
            ),
            width=35
        )
    )

# precompute all of the rolling statistics
_sorted_stocks = stocks.sort("timestamp")
_stocks_with_stats = _sorted_stocks \
    .update_by([
        uby.rolling_avg_time("timestamp", "priceAvg5sAvg=price", "PT2.5s", "PT2.5s"),
        uby.rolling_avg_time("timestamp", "priceAvg30sAvg=price", "PT15s", "PT15s"),
        uby.rolling_avg_time("timestamp", "priceAvg1mAvg=price", "PT30s", "PT30s"),
        uby.rolling_avg_time("timestamp", "priceAvg5mAvg=price", "PT150s", "PT150s"),
        uby.rolling_std_time("timestamp", "priceStd5sAvg=price", "PT2.5s", "PT2.5s"),
        uby.rolling_std_time("timestamp", "priceStd30sAvg=price", "PT15s", "PT15s"),
        uby.rolling_std_time("timestamp", "priceStd1mAvg=price", "PT30s", "PT30s"),
        uby.rolling_std_time("timestamp", "priceStd5mAvg=price", "PT150s", "PT150s"),
    ], by = ["sym"]) \
    .update_by([
        uby.rolling_avg_time("timestamp", "priceAvg5s=price", "PT2.5s", "PT2.5s"),
        uby.rolling_avg_time("timestamp", "priceAvg30s=price", "PT15s", "PT15s"),
        uby.rolling_avg_time("timestamp", "priceAvg1m=price", "PT30s", "PT30s"),
        uby.rolling_avg_time("timestamp", "priceAvg5m=price", "PT150s", "PT150s"),
        uby.rolling_std_time("timestamp", "priceStd5s=price", "PT2.5s", "PT2.5s"),
        uby.rolling_std_time("timestamp", "priceStd30s=price", "PT15s", "PT15s"),
        uby.rolling_std_time("timestamp", "priceStd1m=price", "PT30s", "PT30s"),
        uby.rolling_std_time("timestamp", "priceStd5m=price", "PT150s", "PT150s"),
    ], by = ["sym", "exchange"])

dashboard = ui.dashboard(my_layout(stocks, _stocks_with_stats))

Note that the nice dashboard is created as a tab.  There is no way to go full screen with the dashboard or anything like that.  As a result, my interactions with it feel awkward.  Overall, all of my interactions with the dashboard in VS Code feel awkward.

Using VSCode you can drag a tab out to it's own window: https://code.visualstudio.com/docs/editor/custom-layout#_floating-editor-windows
When in it's own window, you can also maximize it on another monitor if you want (using F11 on Ubuntu, not sure on Mac). Though there is still a tab there with the dashboard name, you could have multiple dashboards in that window and switch between them.


[FEATURE] Publish the documentation in readthedocs

May consider prioritizing this.

https://docs.readthedocs.io/en/stable/webhooks.html

MMLSpark folks just have an automated process where they push the document to a blob: https://github.com/Azure/mmlspark/blob/671b68892ace5967e60c7a064effd42dd5a21ec7/build.sbt#L89
This is the final result: https://mmlspark.blob.core.windows.net/docs/0.18.1/pyspark/modules.html

That sounds great and looks the same as rtd, let's do it.


Savannah map armory doors cannot be opened by riflemen

Description

Reproduction

spawn in savannah as rifleman
try to enter armory
beeptwice sound effect
Screenshots

he craves the rifle
Additional context

i just gotta replace the lock doors with common lock doors lol

@Tunguso4ka ur map

@Tunguso4ka your map
Might be door permissions issue but worth checking

I kinda know why. This door needs Alpha access, but we currently dont have squads so Rifleman and others NCO's dont get squad accesses by default.

It should be resolved when smug commits squads then I think..

requires

#218

Done in https://github.com/CM-14/CM-14/commit/28629cb07033089bc78e213146bb27f91bb78c43


Rebase development branch back to master

There is an outdated develpoment branch with some unmerged changes. I rebased the branch on master. Are those changes still required? If yes then we can merge this PR and then delete the branch.
@evanshortiss what do you think?

@dlabaj I don't think it's still needed given that https://github.com/integr8ly/tutorial-web-app/pull/67 is already merged (and seems to address the same issue). I'm happy to close this PR.


fix(app): Added added success page after pressing save credential button

closes #197
Signed-off-by: Talwinder kaur<EMAIL_ADDRESS>

Codecov Report
Base: 90.62% // Head: 90.62% // No change to project coverage :thumbsup:

Coverage data is based on head (24ee35a) compared to base (77d0624).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #198   +/-   ##
=======================================
  Coverage   90.62%   90.62%
=======================================
  Files          42       42
  Lines        1642     1642
=======================================
  Hits         1488     1488
  Misses        106      106
  Partials       48       48

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Broken link to GWT Calendar WAR

The link at page 236 is broken.
GWT sample apps are now at
https://code.google.com/archive/p/gwt-examples/downloads

moved to better repo.


Need a structure to easily map between security standards/compliance to security rules and vice-versa

security standards and security rules are a many-to-many relationship
security standards are often a list of requirements, with each requirements achieved by security rules.

┆Issue is synchronized with this Jira Task by Unito

PolicyId: #auto generated unique based on create date
policyName: [Security standard] #displayname of policy
cloudProvider: #selectable list [AWS, GCP, Azure, other]
shortDescription: #1 sentence description
longDescription: #full description
version: #auto-increment
lastUpdated: #automatically generated based on submits
requirements:
name:req1
meta1:value1 #meta values should show up in user viewable order
meta2:value2
meta3:value3
rules:
- # list or rules to implement requirement
- # any listed rule will be added to check against the policy
- # a single requirement might have many rules
EXAMPLE
PolicyId: 20211101-c9e120b6-04e5-11ec-9a03-0242ac130003
policyName: "CIS Amazon Web Services Foundations Benchmark v1.3.0"
cloudProvider: "AWS"
shortDescription: "Guidance for configuring security options of foundational, testable, and architecture agnostic settings"
longDescription: >
prescriptive guidance for configuring security options for a subset of Amazon Web Services with an emphasis on foundational, testable, and architecture agnostic settings. Specific Amazon Web Services in scope for this document include:
 AWS Identity and Access Management (IAM)
 AWS Config
 AWS CloudTrail
 AWS CloudWatch
 AWS Simple Notification Service (SNS)
 AWS Simple Storage Service (S3)
 AWS VPC (Default)
To obtain the latest version of this guide, please visit http://benchmarks.cisecurity.org
This benchmark was created using a consensus review process comprised of subject matter experts. Consensus participants provide perspective from a diverse set of backgrounds including consulting, software development, audit and compliance, security research, operations, government, and legal.
version: 1
lastUpdated: 2021-11-01 11:11:11
requirements:
name:1.1 Maintain current contact details
category:Identity and Access Management
description:Ensure contact email and telephone details for AWS accounts are current and map to more than one individual in your organization.
An AWS account supports a number of contact details, and AWS will use these to contact the account owner if activity judged to be in breach of Acceptable Use Policy or indicative of likely security compromise is observed by the AWS Abuse team. Contact details should not be for a single individual, as circumstances may arise where that individual is unavailable. Email contact details should point to a mail alias which forwards email to multiple individuals within the organization; where feasible, phone contact details should point to a PABX hunt group or other call-forwarding system.
Rationale: If an AWS account is observed to be behaving in a prohibited or suspicious manner, AWS will attempt to contact the account owner by email and phone using the contact details listed. If this is unsuccessful and the account behavior needs urgent mitigation, proactive measures may be taken, including throttling of traffic between the account exhibiting suspicious behavior and the AWS API endpoints and the Internet. This will result in impaired service to and from the account in question, so it is in both the customers' and AWS' best interests that prompt contact can be established. This is best achieved by setting AWS account contact details to point to resources which have multiple individuals as recipients, such as email aliases and PABX hunt groups.
Audit: |
This activity can only be performed via the AWS Console, with a user who has permission to read and write Billing information (aws-portal:*Billing )
1. Sign in to the AWS Management Console and open the Billing and Cost Management console at https://console.aws.amazon.com/billing/home#/.
2. On the navigation bar, choose your account name, and then choose My Account.
3. On the Account Settings page, review and verify the current details.
4. Under Contact Information, review and verify the current details.
remediation: lorem ipsum
references: lorem ipsum
rules:
- opnrvn-r-xyz

I dont think this works. Standards have subsections and we need to know the controls that map to the subsections ie CIS standards 1.1, section 2.1. That subsection needs the description as well as all of that data needs to be extrapolated out to build reports. Maybe this is your requirements and meta fields?
We also moved all remediation guidance to the docs (@WIP)

Also to keep this in context this must apply to all the standards in the sheet https://docs.google.com/spreadsheets/d/1N_EgNF5aG2LRKN7LBgVmdb9Xc9gfVfMjomeir-pQ2uI/edit#gid=0

I saw the "subsection" as the requirement identified by name i.e. "1.1 maintain current contacts"
I did have a question if we think the "control ID" needs to be separated from the "control name."  and how generically that would apply to policies (security standards and non standards). I think it can easily be explicitly specified, or smartly pulled out by separating numbers from characters, of course that assumes that the control ID is always a number.
I also had the question if CIS standards 1.1 should be defined by the same file as CIS standards 1.2. I went with the the direction that if the CIS standard changes or updates, it should be a different file. Is there a world where a user might need to maintain v1.1 separate from v1.2? Is it better to have a single file with CIS standards, then in it sections of 1.1 and 1.2?
Yes, my intent was for the metafields to be unconstrained for reports, since different standards, or DIY governance policies will likely have different structures. The belief is that all of them will have a list of subsections though i.e. requirements. What wasn't obvious if they all grouped subsections into sections, but since for the standards I looked at, a section never itself holds a requirement, then it could just be another metadata field.
If remediation is in a separate doc, do we need to keep yet a separate mapping? Or is the suggestion that we don't need the full text here, just a id/link?

updated format, which works better for Java mapping:
PolicyId: #auto generated unique
policyName: [Security standard] #displayname of policy, expected to be human readable
cloudProvider: #selectable list [AWS, GCP, Azure, other]
shortDescription: #1 sentence description
longDescription: #full description
version: #auto-increment
#this is not required in the policy definition (assume 'true')
enabled: false
#this is not required in the policy definition (assume 'true')
archived: false
schedule: 0 0 0 * * *
lastUpdated: #automatically generated based on submits
Section:

SectionID: #autogenerated - maybe null IFF there is one section (for back-compat)
if section ID is null, the rest of these fields, other than list of rules, are optional
refid: 1.1
name: asdfasdf
description: asdfa sdf asdfasdf asdf asdf
these are optional&additional fields/description/etc, mostly for reporting
meta:
meta1: value1 #meta values should show up in user viewable order
meta2: value2 #common metafields are name, category, controlId, name, description, remediation, and references
metaN: valueN #arbitrary number of meta fields
remediation: >
dsfasdf
asdf
asdf
asdfasdf
asdf
rules:

list or rules to implement requirement

any listed rule will be added to check against the policy

a single requirement might have many rules

SectionID: #autogenerated
refid: 1.2
name: sdfsdf
description: sfsdf asdf asdf asdf asdf
meta:
meta1: value1 #meta values should show up in user viewable order
meta2: value2 #common metafields are name, category, controlId, name, description, remediation, and references
rules:
- # list or rules to implement requirement
- # any listed rule will be added to check against the policy
- # a single requirement might have many rules


feat(import/asset): added "Import as asset"

The Import as asset option, can be found under the Geometries category in the file browser, allows users to import assets (.ydr/.yft) that are already YTYP-ready, automatically joining geometries since the purpose is to prop maps.
It also sets imported props as assets so that the asset browser can be used

There is a ton of copy and pasted code here and a lot of it is unnecessary. All you need to do is call obj.mark_asset() after import if the setting is enabled.

Guess I was wrong about running obj.mark_asset() at the end since you can't make hierarchies assets, but still need to refactor to avoid repeated code.

i had decided to create separate functions since i would have to remove 90% of the original function and i noticed that for example the drawable_to_obj function is also called by the yft and probably by something else, creating several problems.
otherwise it is the first time i write blender plugins so if you want to give me some advices is welcome

Or just use my add-on 🤣😂
https://github.com/Yam-Ka/Eazy_Azzets

thanks for sharing your add-on. however, that is a plugin that is not integrated directly into Sollumz.
anyway i tried installing it but doesnt show up in the addons menu.

Implemented in 8d6023f02f6f33dc5205d322f12563bdde90a72e


translate api config resource

What type of PR is this?
/kind documentation
What this PR does / why we need it:
translate api config resource
Which issue(s) this PR fixes:
Part of #483
Special notes for your reviewer:

/cc @chaunceyjiang @windsonsea @RainbowMango


add alphabet-b icon

Preview

@mittalyashu please use the pull request template...

Didn't knew we've PR template, I mostly create a PR directly from VS code.
Will do that next time.

The B feels a bit off for me. It might be the 'comic sans'-y playfullness of the rounded edges, but I think it's mostly the fact that both the upper and lower counter (the open areas inside) are the same size and shape. Most font families will have the upper counter be slightly smaller than the lower one.
I'm sorry for nitpicking here, but I have the feeling this 'B' is also a lot more 'playful' than the even more geometric 'A' in #258.
In general though, I'm personally not entirely sure there's really a need for letters. In my experience fonts are really a skill in its own right, and require a lot of work to look natural. I'm also somewhat afraid of a slippery slope, would we need underscores, slashes, and punctuation as well? Cyrilic characters?

@MoltenCoffee I agree. The design language is not quite the same as the rest of the iconography.
@mittalyashu Adding a random letter suggests the rest of the English speaking alphabet should also be considered. And if so, what about numerals? And even then, why only English? This is a slippery slope and seems like a pretty good way to add unnecessary bloat.
An icon is a way to graphically represent something symbolic, a concept or an idea. Letters and numbers are what they are - just letters and numbers and don't require graphical representation to explain what they are, hence, can not be considered icons.

Hmm... @mikeott you do make a point.
Okay, closing this PR for now.
@ericfennis what should we do about "A" icon already added to the set.

I agree with @MoltenCoffee and @mikeott. We should avoid adding typographic. Then we can better consider making a font 😄 .
@mittalyashu Yeah close it as wel.

@mittalyashu If it helps, there is this: https://lucide.dev/icon/bold

@mittalyashu If it helps, there is this: https://lucide.dev/icon/bold

Wait, when did we had that icon 😂

lmao, perfect.


added endpoint and arn to docdb cluster secret

Description of your changes
Added the Docdb cluster endpoint and arn to the connection details so that the value will appear in the secret created by writeConnectionSecretToRef

Fixes #
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
manually:
> kubectl get secrets/my-docdb
NAME       TYPE                                DATA   AGE
my-docdb   connection.crossplane.io/v1alpha1   3      6m1s

> kubectl get secrets/my-docdb --template={{.data.endpoint}} | base64 -D
docdb-demo-lnj42.cluster-c3kmasxmrnwp.eu-west-1.docdb.amazonaws.com

> kubectl get secrets/my-docdb --template={{.data.arn}} | base64 -D
arn:aws:rds:eu-west-2:<account-id>:cluster:docdb-demo-lnj42

/test-examples="examples/s3/bucket.yaml"

/test-examples="examples/docdb/cluster.yaml"

/test-examples="examples/docdb/cluster.yaml"

/test-examples="examples/docdb/cluster.yaml"

/test-examples="examples/docdb/cluster.yaml"

@ahmedali6 thank you for this PR, could you please rebase to the main?

/test-examples="examples/docdb/cluster.yaml"


Bias between different oversampling levels

Hello! thanks a lot for your work here!
I'm trying to filter out this high frequency noise and, while analizing the data, ultra_low oversampling consistently sheds 20mBar less than ultra_high. I wonder whether this is normal.

Also, it's hard to characterise this noise. There's no spike in the spectrum (fourier transform) for any of the sampling methods. Only the band-base signal.
I'm thinking of the best way to filter out the noise. If you had some ideas (IIR/FIR/Kalman...) and also, maybe the reset(1) method can include this oversampling aware compensation

Thanks for this issue.
You have explored the sensor in far more depth than I have, so I do not have an answer.
(Thinking out loud modus)
One possible cause that I have seen in the past is (partially) integer math. Best known are truncating effects in divisions (11/3 =3). Another is related. Oversampling means more samples and therefore more chance on canceling noise effect.
This latter would show up as more spread, not perse changing the average.

BTW This wider spread with lower oversampling is perfectly visible in your graph.

Had a quick look at the data sheet, and so no indication of this bias.
As it looks like a systematic error, can you tell about the setup used to make these measurements?

I'm thinking of the best way to filter out the noise. If you had some ideas (IIR/FIR/Kalman...) and also,
maybe the reset(1) method can include this oversampling aware compensation

to handle the bias.
As the bias seems constant, the simplest solution might be to add a function to set a "calibration offset".

void setPressureOffset(float offset)
float getPressureOffset()
void setTemperatureOffset(float offset)  for completeness
float getTemperatureOffset()  for completeness

This offset could be added when one calls getPressure() or getTemperature()
to handle the spread
The oversampling could also be done outside the sensor (if your processor has CPU to spare)
I have two libraries that could help.

https://github.com/RobTillaart/runningAverage
https://github.com/RobTillaart/runningMedian

4AM idea!
Can you make a graph of the temperature measured by the sensor for the different modi?
hypothesis
To calculate the pressure the temperature is needed.
Making many measurements probably generates heat.
This could affect the math for the pressure.
More samples more heat more deviation.
Note:
-: the offset for the temperature is not taken into account for the pressure math.

a heatsink on the sensor could help?
is the temperature of the air constant?

Todo check the formulas ( simulation? )

Back to your original post.

ultra_low oversampling consistently sheds 20mBar less than ultra_high.

What is the unit of the y-axis?
If it is mbar, the difference is 0.2 mbar consistently, (not 20) which is well within the error-band of the sensor

@dinigo
Any new insights?

Hello @RobTillaart , didn't have much time this weekend. Your insights are really very valuable. I'll try:

Rising temp hypothesis

I'm using a sketch practically identicall to your test.ino. Except I'd remove delays to get the highest sample rate possible. Oversampling is used "round-robin" style, so the effect of temperature should be consistent. I'd get some temp data anyway 👍

What's the unit of the y-axis?

It's mBar vs millis

the difference is 0.2 mbar consistently, (not 20) which is well within the error-band of the sensor

True! it's ~10x smaller than expected accuracy at this temp (~20ºC). That's actually great!
Other interesting things about noise characteristics of samples:
Looking for the best possible filter I've gone through several steps, in case you're interested:
Check whether there's some common noise component between different oversampling signals. Doesn't seem to (other than the base-band "intended" one)

Same for the spectrum (FFT). It's completely flat, not a single spike (other than the base band delta at 0, which is not visible)

And the spectrogram doesn't show anything other than background/wide-spectrum/white noise

Thanks for this additional analysis.
So in summary, the sensor behaves very nicely within the specifications (in I2C modus).
@dinigo
Do you miss any (generic) functionality in the library?

Not really, this 20mBar error is not such, but rather 0.2mBar.
Thanks for your work (on the lib) and your wise comments


5G not working

Hi Team,
I am using latest version 1.4.1 on my app. But when I use 5G it is sending RealStatusNotReachable result. Although my Networking API is working correctly.
Please support us with this issue.
Thank you!

this only occur when you are using 5g? how about change the network to 4g?

@bekzodrakhmatof

It works with 4G


feat(postgraphql) Added an option to allow the pgRole to be extracted from anywhere in the JWT

When working with Auth0 as the source of the JWT it can be difficult to write directly to the root of the jwt (their rules engine allows writing to the jwt but it has to be namespaced with a url-like property name.)
I created this PR that allows you to specify a path in the jwt from which to set the pgRole; if unset it defaults to the current 'role' property on the root of the jwt.
Since this is my first commit I probably missed something, though I did add unit tests where appropriate, updated docs, ran all tests, and tried to follow the commit guidlines.

oops - didn't run the linter... knew I missed something

@angelosarto In future it's okay to just push your updated code to the branch - there's no need to close the PR and open another one 👍

Replaced by #480


upstream: fix the header file path typo

Description: Fix the header path
Risk Level: LOW
Testing: N/A
Docs Changes: N/A
Release Notes: N/A

/assign htuch


Prepare release v1.4.1

Prepare release v1.4.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.646%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
3377

Relevant Lines:
3389

💛  - Coveralls


Reset Chat 1

Hey, thanks for a great plugin!
Would be really nice to have a button to reset Chat 1 since it can not be deleted and reaches limit sooner or later.
Then the only possibility to "reset" it is by manually deleting all messages.

yes please :)

Hi, thank you for the feature request.
I have actually been thinking about it as well.
The feature will be available sometime early next week.

Feature is available from v2.0.3.


Fix native callback signature to match with C#

Some recent C# PR has changed the expected signature of native callback used in test. This is the fix.
Callback is now only used for testing, so I renamed it.

This should fix C# tests on Windows.


Add a fuzz tests for all binaries

We should add fuzz tests for each binary:

mdbook-xgettext: test that we don't crash on random Markdown input
mdbook-gettext: test that we don't crash on random PO files
mdbook-i18n-normalize: same as for mdbook-gettext (this could have caught #56)

Hey, I would like to work on this issue.

Hi @mgeisler,
Sorry, been busy at my main work lately. I started looking into this issue. I will try to create a PR in the next few days.
I had some questions:

This task is about fuzzing binaries. One approach I can do is within my fuzz test execute the binary by using fuzz provided random input as a file and executing the binaries against that. That probably will be slow and instead I should fuzz main functions in the binaries. Is that correct?
I wanted to start with fuzzing with a sample fuzz target that catches the error fixed by https://github.com/google/mdbook-i18n-helpers/pull/56. Did that PR fix a wrong output or a panic? That is in my fuzz test for mdbook-i18n-normalize - should I be testing equality for some specific expected output or just that the function does not panic?

Thanks for looking at this! I completely understand that main work can become busy :slightly_smiling_face:

This task is about fuzzing binaries. One approach I can do is within my fuzz test execute the binary by using fuzz provided random input as a file and executing the binaries against that. That probably will be slow and instead I should fuzz main functions in the binaries. Is that correct?

Yeah, you should fuzz the main logic by calling functions from your fuzz tests — you should not execute the binaries. I would not focus on the binaries, just use them as a starting point to find the logic to fuzz. Find the functions called by main and try to restructure the code so that it can be fuzzed. This likely means moving a bit more functionality from src/bin/... to src/lib.rs. If we start seeing related functionality in lib.rs, then we'll move it into separate Rust modules.

I wanted to start with fuzzing with a sample fuzz target that catches the error fixed by Handle normalization where old msgid disappears #56. Did that PR fix a wrong output or a panic? That is in my fuzz test for mdbook-i18n-normalize, should I be testing equality for some specific expected output or just that the function does not panic?

In this case is was a panic: if new_msgids.is_empty(), then we crashed below due to an underflow when trying to compute new_msgids.len() - 1.


update develop from master

merging latest changes from master into develop

Guys, I am going to create a new develop from master, rather than this merge


Streamed output printed on new lines with pty option since v0.8.0

Hey, it's me again! :D
I noticed this behaviour with v0.8.0:
irb
require "tty-command"
cmd = TTY::Command.new(pty: true)
cmd.run('rubocop')

=>
8908f6bb] Running rubocop
[8908f6bb]      .rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout
[8908f6bb]      Inspecting 28 files
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]      .
[8908f6bb]

[8908f6bb]      28 files inspected, no offenses detected
[8908f6bb] Finished in 1.704 seconds with exit status 0 (successful)

Without the pty option it works fine, in v0.7.0 both with or without works fine.

For clarity's sake the previous behaviour:
[452673d4] Running rubocop --parallel
[452673d4]      Inspecting 184 files
[452673d4]      ........................................................................................................................................................................................
[452673d4]
[452673d4]      184 files inspected, no offenses detected
[452673d4] Finished in 2.154 seconds with exit status 0 (successful)

I rewrote how streams reading is done. The major issue was that it was a blocking call that expected a new line input in order to consume output. This was problematic in many ways, including the fact that it was hard/impossible to interrupt the child process 'cleanly' and timeout operations.
Therefore, what is probably happening now with pty is that once any output becomes available it is consumed using unix select from underlying system and straight away printed out. In many ways this is what you would expect. I actually don't know how to fix this at this moment as it maybe a Ruby thing and how it deals with non-blocking stream reads when PTY terminal is used. I really need to get on with other projects but if you have time to investigate and submit PR I will review asap and release new version. This is one of those things that can 'consume' hours to figure out which I don't have at the moment.

I don't think this will ever be fixed. Before the change, I was calling gets on the output streams. That's pretty dangerous in many instances. Firstly, it always waits for a newline input, which in your case made things look good when logging but is a rather seriously flawed. In other words, unless a newline is provided on the output the whole reading will be blocked and no output provided. More importantly, there is no 'clean' way to break such reading in cases when script actually hungs. By reading output as we get it and bufferring it, we get output straight away.
What I found testing example case is that the pty is much slower than regular unix pipe, it is an actually full blown terminal emulator! That's why when running command without pty you get all output for the inspected files on one line as there is no overhead. I have run small simulation just printing dots and noticed that sometimes when I run it in pty mode they all get printed on one line, and sometimes they don't, but given sufficient delay between prints the dots are always printed on individual lines. Does that make sense?
I do believe that current implementation is far superior to previous as it allows for proper timeouts and most importantly reads output as it becomes avilable without hanging. I will investigate further if there is a way to have a whole line output but I wouldn't hold your hopes.

By reading output as we get it and bufferring it

Would it make sense to buffer it until a newline is received?  As an option?

@jrochkind I really don't think an option is a right way to go. That would blossom the complexity of pretty printer even further and would only work in rare cases of streaming dots together with :pty option set, which is not enabled by default. If @thisismydesign could adjust his printer based on the pretty printer that would be my preferred way to go. Are you experiencing similar issues with your script?
That's one of the reasons I hold off releasing v1.0.0 to retain the flexibility to change api and allow the gem to mature like wine by being heavily used. More importantly to me v1.0 is a sign that I've finished designing an API which in this case I haven't. However, this is not to say that I intentionally will keep breaking things without a rhyme or reason. I may even write a blog article this year about my weird reasoning.

I have experienced similar issues in the past, and would love a generalized solution, but I didn't really dig into it at the time.

Hmmm streaming vs buffering printer... I suppose we could have :stream_output option by default set to true... Does anyone fancy submitting PR?

Here's a simplified printer that solves my issue: https://github.com/thisismydesign/autowow/blob/ff4da5eb98acfa30e3c9731e3ab3179f8a9bee79/lib/autowow/executor.rb#L22-L47
I used a new, common aggregator instead of the vars @piotrmurach mentioned because 1, I'm not sure whether it'd mess with other features of Pretty and 2, I want to keep the order of output regardless stdout/stderr.
Output:
[fea3fa12] Running rubocop --parallel
[fea3fa12] .rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout
[fea3fa12] Inspecting 28 files
[fea3fa12] ............................
[fea3fa12]
[fea3fa12] 28 files inspected, no offenses detected
[fea3fa12] Finished in 1.357 seconds with exit status 0 (successful)

Would a PR along these lines (with an option as discussed) work for you?
On a side note I noticed that stderr is printed in red which I think should not be the case with :pty. But this is something to be addressed separately if at all. :)

I like it! The only thing I'm still unsure is how to handle the option. I'm swaying more in the direction of having an actual new printer called pretty_bufferred or similar which would basically indicate to people that they are using a different printer rather than setting & changing how tty-command works internally. This would avoid the idea that there maybe a mode of running commands that streams vs buffers output, which wouldn't be true. Any thoughts? Once we have a solution I definietly would encourage a PR!
As far as I know, stderr is not different from stdout in the way it handles escape codes and as such should work fine with/without :pty option. Not sure I fully appreciate why would that be a problem?

Different printer seems fine if there's an easy way set it.
It could also be an option on the printer, you'd still have to set the printer explicitly, cause you'd have to set it to one with this option set.

@jrochkind The reason I thought about having a new printer type as opposed to an extra option that applies neither to the command logic nor to all printers, it is only specific to a pretty printer, in which case a specific printer type kind of makes sense. However, as you say having :pretty type with streaming: false has also an appeal to it....

sorry, can you remind me the API for setting a custom printer?

Congrats and have fun :)

I'm also on the side of a new printer because (as you mentioned) it better communicates what's really happening, also less config clutter.
Another note on my implementation: it doesn't print on newline character but aggregates the whole output. It'd make more sense to print on newline.

I actually have a use case (with capistrano) where aggregating the whole output might make sense. If it's easy, it could be configurable?  I agree if only one is to to be done, it's printing on newlines.

Improved the buffering printer to print finished lines: https://github.com/thisismydesign/autowow/blob/52339c3c6e7496eeea7863476c0ca9ef99169ccb/lib/autowow/executor.rb#L22-L59
This + the option to aggregate output is what I'd put in the PR. Just sharing my (rather slow) progress in the meanwhile.

@thisismydesign I'd like to resolve this issue... I know it's been a while... do you have time to submit PR with your suggestion?


New organization scheme

To make the NodeOS organization easier to manage I've removed the teams and now will continue with fine-grain access control. Now instead of having direct access to the repo, anybody that wants to contribute to NodeOS I can be able to add him to the NodeOS organization and assign him (or her) the corresponding issue to work with, so there's no duplicated efforts. Due to that, they'll need to create a pull-request that will be merged with the reference repo on the NodeOS organization, and also you can be able to create new repos without needing to ask me first (as happened with the docs repo). I will be able to create new teams for specific repos like the website that work together and make sense to have access to all of them at once, but in general terms will not be anymore the "all or nothing" access control of before.
I will continue to use directly the NodeOS organization repos until 1.0 version, after that I'll protect the master branch of all of them and only it will be able to push and merge new commits the NodeOS-bot account managed by the CI server.

Ah this sounds excellent! Will allow for changes to progress quicker. +1

I'm going to remove the issues tracker of the other projects and proxy all of them over this one, this way it will be possible to have all of them on a single place since there's no GitHub issues agregator (or does it?). When refering to a particular repo at its name between brackets on the issue title.
We should add this to the readme or a GitHub issues template...

there's no GitHub issues agregator (or does it?)

Ok, there is, but it's a SpringBoot app... Is it time to develop our own one? And maybe have a NodeOS instance running somewhere in the cloud? :-P

Haha creative idea! It would be nice to have

Since yesterday GitHub support projects! Didn't have the chance yet to read about it, but seems will help us to organice better NodeOS development :-) Can someone take a look on it?

Doing that right now. It looks good!


Updates project dependencies and the linter

Gonna merge this since CI is busted on not being able to install danger, which is updated in the profile 2.0 branch.


Wrong accelerate config path doesn't throw any errors

System Info
`Accelerate` version: 0.15.0

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
accelerate launch --config_file=path/that/does/not/exist/example_config.yaml example_script_that_exists.py`
This will launch the script just fine and use the default values. This behaviour is very confusing and unexpected. You would assume that a wrong path to the config would throw an error.
Expected behavior
See above.

This was fixed last week via https://github.com/huggingface/accelerate/pull/1074 and will be pushed on the next release


Lint policy recommendation PySpark code with flake8

Lint policy recommendation PySpark code with flake8, flake8 configuration is copied from NSX openstack project at https://opendev.org/x/vmware-nsx/src/branch/master/tox.ini.

/theia-test-e2e


User Interface Update

Is your feature request related to a problem? Please describe.
Update is needed of the User Interface to make it even more usable:

[x] Further enhance the dark mode (right now quite some of the elements are not readable in dark mode)
[x] Further refine the individual tasks (more visual seperation between tasks, maybe change the font size?)
#13

Pulling out the last point to be a stand-alone issue is that will probably require a lot more work to develop.

Closed in release 0.1.6 (bad commit message tagging hygiene)


Add --no-preserve option to cleanup workdir

fixing issue #135

How did we get to this option? Today I thought that something opposite - making a copy of directory even if --self-setup was used and storing the log for it may be quite nice..
100% my idea. Reasoning was that after successful execution - since no debugging is required - user might want to purge unnecessary data from storage, especially with (soon-to-be) functioning database and --syslog option. I still stand behind it but counter argument is also valid from admin pov.
Regarding --self-setup - up to the users again (who can use --debug and tee output if it's too long for their console).


On python 3.6, pip-compile adds a python 2.7 dep

pip-compile keeps adding functools32==3.2.3.post2 to my output requirements.txt; this causes pip install to fail:
Collecting functools32==3.2.3.post2
  Downloading functools32-3.2.3-2.zip
    Complete output from command python setup.py egg_info:
    This backport is for Python 2.7 only.

functools32==3.2.3.post2 comes from jsonschema==2.6.0, which comes from nbformat==4.4.0, which comes from notebook.
Environment Versions

macOS 10.12.6
Python version: 3.62
pip version:  9.0.1
pip-tools version: 1.9.0

Steps to replicate

Create a requirements.in with one line: ipython[notebook]
pip-compile requirements.in
pip-install requirements.txt

Expected result
The generated requirements.txt should be valid.
Actual result
It is not, and install fails.

I tried to reproduce with python 3.6.2, and I can't. functools32 is not collected.
requirements.in:
ipython[notebook]

requirements.txt:
#
# This file is autogenerated by pip-compile
# To update, run:
#
#    pip-compile --output-file requirements.txt requirements.in
#
bleach==2.0.0             # via nbconvert
decorator==4.1.2          # via ipython, traitlets
entrypoints==0.2.3        # via nbconvert
html5lib==0.999999999     # via bleach
ipykernel==4.6.1          # via ipywidgets, notebook
ipython-genutils==0.2.0   # via nbformat, notebook, traitlets
ipython[notebook]==6.1.0
ipywidgets==7.0.0         # via ipython
jedi==0.10.2              # via ipython
jinja2==2.9.6             # via nbconvert, notebook
jsonschema==2.6.0         # via nbformat
jupyter-client==5.1.0     # via ipykernel, notebook
jupyter-core==4.3.0       # via jupyter-client, nbconvert, nbformat, notebook
markupsafe==1.0           # via jinja2
mistune==0.7.4            # via nbconvert
nbconvert==5.2.1          # via notebook
nbformat==4.4.0           # via ipywidgets, nbconvert, notebook
notebook==5.0.0           # via ipython, widgetsnbextension
pandocfilters==1.4.2      # via nbconvert
pexpect==4.2.1            # via ipython
pickleshare==0.7.4        # via ipython
prompt-toolkit==1.0.15    # via ipython
ptyprocess==0.5.2         # via pexpect, terminado
pygments==2.2.0           # via ipython, nbconvert
python-dateutil==2.6.1    # via jupyter-client
pyzmq==16.0.2             # via jupyter-client
simplegeneric==0.8.1      # via ipython
six==1.10.0               # via bleach, html5lib, prompt-toolkit, python-dateutil, traitlets
terminado==0.6            # via notebook
testpath==0.3.1           # via nbconvert
tornado==4.5.1            # via ipykernel, notebook, terminado
traitlets==4.3.2          # via ipykernel, ipython, ipywidgets, jupyter-client, jupyter-core, nbconvert, nbformat, notebook
wcwidth==0.1.7            # via prompt-toolkit
webencodings==0.5.1       # via html5lib
widgetsnbextension==3.0.1  # via ipywidgets

The only difference I can think of is that I used a Dokcer container (not macOS), and our setuptool version could be different.
From the top of my head, I'd say:

Try doing pip install jsonschema and confirm it works.
Check/update your setuptools version
Triple-check that you're really using pip-tools 1.9.0.

If all else fails, send the verbose (-v) output of your pip-compile.

Oh boy. Thanks for looking! I'll dig a little more on my end and report back.

As I mentioned in #554, make sure to delete your requirement.txt and try to pip-compile with --rebuild to clear your cache. Tell me if it works out.

Alas: I'm still getting the same result, with the same bad dep, every time: https://pastebin.com/uC1WgxT9

Ah right -- here's the pip-compile -v --rebuild output: https://pastebin.com/8dQS7Y26

Something is not right. My pip-compile on a python 3.6 system will give me ipython 6.1.0, while you get 5.4.1. And the version 5.4.1 is the one offering a py2 wheel, while 6.1.0 offers a py3 wheel.
Somehow, your system act as if is was running in python 2.7. That goes beyond requirements parsing: AFAIK, pip-tools takes no part in the checking the wheel's python version compatibility: that's all handled by pip.
In the same venv, could you give me:

Give me your setuptools version (you can also try updating it)
Try doing pip install ipython[notebook] and give me the output, as well as a pip freeze --all output.

Um. Well. This is all.... perfectly alarming. I will... see if I can't... dig in to this a little further on my end. Something seems to have gone completely sideways, and it's smelling increasingly like it's something subtly borked on my end.
Thanks for your time! I'll report back.

So. A pretty significant part of this seems to be some tooling we use here at my work, which has turned out to be... uh, let's say "bad." Something is... deeply wrong system python. I do not understand what yet -- or, honestly, why it hasn't exploded much more dramatically much earlier. But, I seem to have tooling that is actually using python2.7 pip (and claiming it's python 3 pip), which is probably what's cramming garbage in to the cache.
So. If I meticulously create a new venv with absolutely for-sure only python3 and skip the pip cache for pip-tools installation, everything works great for me.
Beyond "oh god oh god," I'm not... confident yet about what is going on. I'm.... well. I very much appreciate the help digging in to this, and I apologize for any wasted time. It certainly seems like this is something deeply screwed up in my python installation.
In light of this, I'm going to go try and purge/re-install basically everything fresh.

Okay, I have:

Completely scrubbed global pip packages, including blowing away the cache entirely
Fresh venv install
Fresh installation of pip-tools

Everything now seems groovy and consistent.
Thanks for an awesome tool and for the digging!


Street Fighter VIII

Issue Type:

[ ] Bug Report
[X] Feature Request
[ ] Documentaion

I would like to add my game that I made during my classes into your project, the game plays itself but if you agree to put it I will add a 1vs1 mode, the code can be a bit messy and poorly optimized, and the game is a bit weight heavy sorry for that 🙏🏽.
Screenshots

Game Link : https://dinahworld.github.io/University-Fighter-VIII/
The repository : https://github.com/DinahWorld/University-Fighter-VIII

@arpit456jain

ok @DinahWorld make it 1 vs 1 and try to optimized it

It will be done 😉 @arpit456jain

@DinahWorld Do this issue asap otherwise we will close this issue

sorry for not answering you, I'm overwhelmed at the moment, I'll do this issue later


bug(Sort Header): Sort only works if columns are updated

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/edit/angular-ivy-o298jy
Steps to reproduce:

Create a material table with mat-sort directive (3 columns will do)
Add any data
Trigger event to apply sort through [matSortActive] and [matSortDirection]
Trigger another event to change the sort using the same bound string objects, do not update the displayed columns

Reproduce via demo:
In the demo you can sort initially with the "Sort by age" button, pressing "Sort by name" fails to apply the sort to the name column as coded. If you hit Reset then "Sort by name" it works fine because the displayedColumns have been changed.
Expected Behavior
The sort should change from the first column sorted to the new one.
Actual Behavior
The sort icon either goes away or does not change from the first column.
Environment

Angular: 9.1.9
CDK/Material: 9.2.4
Browser(s): Chrome 80
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Thanks for the detailed reproduction - this definitely seems like a bug

I appreciate all the work to get this fixed. Any idea on when it will be completed?


error for middleware

export default function(context) {
    var bs = require('bowser');
    var userAgent = context.isServer ? context.req.headers['user-agent'] :
        navigator.userAgent;
    var bowser = bs._detect(userAgent);
    if (bowser.msie && bowser.version < 9) {
        return context.redirect('/unsuport')
    } else {
        // do nothing else,  i think it should be continued
    }
}

such as the upon code , i think if i visit  the browser which is not ie9 below, it should do nothing in middleware and going on response me the page , but the page keeps always loading , cant stop.
i did not find any case in nuxt project,   am i wrong?  ps. i use nuxt in koa

i guess if  i cant use the nuxt middleware in koa project?

@zhancheng you can use a koa middleware with a specific route /unsuport where user are redirected before using nuxt.render or to use css conditional

@alexchopin  ok, thats what i did, thanks!


Misleading indentation errors on gcc 11.x

Had to suppress that warning to be able to compile.

This does the trick:
if (NOT (GCC_VERSION VERSION_LESS 11.0))

          # Disable warning on misleading indentation it become more aggressive in 11.0

          set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-misleading-indentation")

  endif()

Where do you get indentation errors, it it is localized, perhaps we can fix at source level, otherwise I'm happy to add you suggestion. I presume this is for the main CMake file.

OK, my patience with GCC warnings is limited so I'll disable.

Should be fixed on master, please check.
Wonder why this isn't part of pedantic that should already have been disabled on recent GCC.

It is, thanks. I will close this issue.

I see, pedantic is still on for gcc, next time I'm going to remove pedantic for GCC.

as the problem is still present, what about including #pragma GCC diagnostic ignored "-Wmisleading-indentation" on the generated files?

@amery There is distinction between compiling the flatcc tool chain and the runtime. Notably the runtime (library and generated) can be compiled by whatever tool chain the user prefers. I guess this topic only covers the tool chain.
There is a hook for dealing with runtime warnings in the portable library. This is mostly for generic issues that prevent smooth cross platform behaviour and are therefore always enabled. Others should be dealt with in the users tool chain.
The current situation is a bit special because the warning is actually useful in the general case, but specifically for flatcc generated code, it is not helpful. Therefore we cannot or should not inject the warning at the portable layer because the portable library is not flatcc specific.
I have not fully investigated, but I think can conditionally disable the the warning in pdiagnostic.h which is included in all generated files. Then set a flag in flatcc specific include files to enable the warning in this context.
Would you be willing to look into this?
Here the warning can be added in either pwarnings or probably better pdiagnostic.h, guarded by a PDIAGNOSTIC flag:
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/portable/pwarnings.h
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/portable/pdiagnostic.h
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/portable/pdiagnostic_push.h (and pop)
I think the PDIAGNOSTIC enabled warning could then be enabled with a define in
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/flatcc_flatbuffers.h
or
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/flatcc_rtconfig.h

This issue has been closed, was this fixed in a later version of flatcc? Either by simply adding a newline in the auto generated code, or disabling the warning with a push/pragma/push?

@ndjhartman Please explain your problem more clearly. I assume you that flatbuffers union break for you with -Werror.
The issue with indentation is not limited to any feature but to all generated code, as a rule.
It is not a fixable problem. The flatcc code generator produces large amounts of dense code that is intended for macro expansion not for human consumption. Other flatcc code should be properly indented, and generally is.
You mention pragma push/pop:
I already cover this in my above comment, but there is possibly room for improvement if someone wants to step up.
Historically there are three systems to deal with this:

the CMake build which is not necessarily what users use, but it tells which warnings are considered necessary. It also deals with warnigns that cannot be handled in source code, notably some MSVC warnings.
pwarnings.h : here are some warnings that universally break standard C, this is mosly related to old MSVC compilers, afair.
pdiagnostic_push/pop.h headres. These are included in all generated code. Here the most important compiler specific differences are handled, but handling all compiler variants get complicated fast, just look at CMakeLists.txt

That said, flatcc has always aimed for -Werror with as high a warning level as pratically possible. Because gcc has become overly aggressive, the level of max  warning support for that compiler has been lowered, as it kept breaking things unnecessarily just randomly taking up time to fix nothing, and worse, breaking portability of code. You can again see this in CMakeLists.txt and comments.
So, is it possible to move some of these warning disablers from CMakeLists.txt into pdiagnostics? Yes likely, but we cannot deal with all possible combinations there. If you are willing to put in the effort, and test widely, there is opening here.
See my previous comment where I link these files.
Can we add it to pwarnings.h? No. We want identation warnings in general, and the portable sub library is not flatcc specific, it only disables hostile warnings while pdiagnostics handle cases where flatcc might not adhere to otherwise reasonable warnings for one reason or another.
Can we just use CMakeLists.txt: not really, because users have different builds.
So there isn't a general solution, as there never is with complex software infrastructure.
But the solution is not to modify the flatcc code generator as per earlier comments.

@ndjhartman
I should have added the commit earlier on:
https://github.com/dvidelabs/flatcc/commit/f8c4140dd9dde61c86db751f6002def78754fced
https://github.com/dvidelabs/flatcc/blob/f8c4140dd9dde61c86db751f6002def78754fced/CMakeLists.txt#L228-L231

Thanks @mikkelfj. I do see this check present in the CMakeLists.txt. I haven't had time to debug this specifically, but I'm wondering if it's something to do with using compiling with ARM GCC.


GLES2 Batching - prevent baking on VERTEX use in a shader

Using the operator += in a shader is classified as an 'assign', and so is classified as a write rather than a read. This means that we need to prevent vertex baking on either a write or read (i.e. on usage), rather than just on reads.
Fixes #39651.
Notes

This was probably always needed realistically, and it means that most custom shaders will have some baking prevented.

Discussion
(not really impacting this PR, but more about further work)
This does add to the case for looking for ways to get around these custom shader limitations in either 3.2.3 or 4.x. They currently work, but are not accelerated as much as possible, and for games that rely on a lot of custom shaders, this isn't ideal.
COLOR can be got around by adding an optional wide vertex format containing both the local color and the final modulate. However, I can't see an easy way around the use of VERTEX breaking batching, because the transform is applied AFTER the vertex shader. Short of transferring the transform in the vertex format.
Actually although the full transform is presumably huge, we might still be able to include the transform in a vertex format if it is just a translate / scale, as this is 4 floats.

Thanks!


Lists of input objects do not work

When executing a mutation which accepts a list of input objects as an argument, or accepts an input object which contains a list of input objects, an unexpected error occurs. This also occurs when the input object type is passed as a variable. Lists of scalars work as expected
This appears to be a bug in the execution engine itself, because the message is a standard Python exception (see below).

Tartiflette version: 0.8.8
Python version: 3.7.3

SDL:
type Mutation {
  listFailure(input: [FailureInput!]!): FailureResult
}

type FailureResult {
  result: String!
}

input FailureInput {
  a: Int!
  b: Int!
}

Resolver:
@Resolver('Mutation.listFailure')
async def list_failure(parent, args, ctx, info):
    return {
        'result': str(args)
    }

Query:
mutation {
  listFailure(input: [
    {
      a: 3,
      b: 4
    },
    {
      a: 5,
      b: 6
    }
  ]) {
    result
  }
}

Error (note that the locations do not match the query string because it was passed as a single line, I prettified it above):
{
    "data": {
        "listFailure": null
    },
    "errors": [
        {
            "message": "list indices must be integers or slices, not str",
            "path": [
                "listFailure"
            ],
            "locations": [
                {
                    "line": 1,
                    "column": 12
                }
            ]
        },
        {
            "message": "list indices must be integers or slices, not str",
            "path": [
                "listFailure"
            ],
            "locations": [
                {
                    "line": 1,
                    "column": 12
                }
            ]
        }
    ]
}

Thanks for this bug report


Simplified upsampling

Hi @geneing, thanks for all your hard work! I was wondering why you decided to abandon the simplified upsampling in your model_simplification branch. Was the audio quality significantly worse?

@bshall Well, the main reason for simplified upsampling was to improve data flow. The upsampling part contains a 5 tap convolution, which requires padding the input mels on both sides with at least 2 empty frames on each side. It adds significant amount of work when doing parallel synthesis (by splitting the input mels in time and synthesizing in parallel - each piece has to be padded), and one has to be very careful when stitching padded waveform pieces together.
It turned out that network based upsampling is actually shifting the mels in time a bit, which simple interpolation wasn't doing. This resulted in slightly lower quality speech.
Keep in mind that upsampling is a tiny part of overall timing. Most of the work is done in RNN and post-net FC layers.

Thanks for the response @geneing. Yeah, streaming synthesis would be really cool. I was wondering whether simple "nearest" upsampling would be good enough to replace the upsampling network.

Hi @geneing
I was wondering if you made any progress with the streaming synthesis. I am trying to do something similar to better estimate the inference time/First Time To Response, and the achieved improvements using very helpful techniques that you suggested.


Invalid "found ignored files included in git"

I have a project with a "temp directory" which I want to include but NOT include any files within it EXCEPT for .gitinclude file. (so it preserves the directory)
So my .gitignore looks like this:
#Ensure the files directory is included, but not the contents
tempFiles
!.gitinclude

/tempFiles
-> .gitinclude
-> otherTempFile.xml
-> otherTempFile.xml
-> otherTempFile.xml
However, the plugin is erroneously thinking that .gitinclude is supposed to be ignored rather than specifically un-ingnored

Same here, with this structure:
/storage
  /cache
    .gitignore

And this .gitignore file:
*
!.gitignore

The plugin also doesn't take into account that a checked-in .gitignore file doesn't ignore itself:
/temp
  .gitignore

Where .gitignore is simply:
*

Git still picks up changes to this file.

Confirming, this is happening from the last release

@zeg-io @cviebrock @islemaster @FrancYescO
Thank you for this report. I have fixed both (excluding files with ! and a case with *) issues. They will be delivered with the next v2.0.0 release.


Make it possible to run bananalyzer server using Docker

Enables make commands and makes it possible to run and develop using Docker

All tests pass, but I had to cheat in a couple of spots.
Here's why: recursion.  I tried using Iterable[["AllowedJSON"] but the world is not ready yet, maybe Python 3.12 supports it, maybe it's just the wrong way to do it.
The main issue is that schemas are recursive (as I remember from implementing that part for Harambe).  I'm not familiar enough with bananacrate, so please take a peek and let me know what we can and cannot change to make tests pass;  we can always avoid recursion and have additional methods for filtering and formatting results, but then nested arrays and objects won't be supported.

@snshn is this good to merge now?

@awtkns this should be good, it's passing all the tests, I only worry about https://github.com/reworkd/bananalyzer/pull/87/files#diff-c9d7dc2b19a07bc9d6d674f369754102e904ce405c6261543976430a640db6cbR8 and https://github.com/reworkd/bananalyzer/pull/87/files#diff-222a72beb539b057695aadbedc01313c2d8ba03852fd18e595655df5c0f3f1e2R8 — it may affect what happens outside, on your platform, since the schemas are changed, and now support nulls and recursion where they didn't before

I can go ahead and merge it in if the modified schemas isn't a problem.  I think we can add recursion and deal with nulls later, as long as it doesn't break anything in your live environment.


Update cats-effect to 3.3.10

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #234 (18ebf9b) into master (235cad0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #234   +/-   ##
=======================================
  Coverage   87.30%   87.30%
=======================================
  Files          28       28
  Lines         843      843
  Branches       39       39
=======================================
  Hits          736      736
  Misses        107      107

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 235cad0...18ebf9b. Read the comment docs.

Superseded by #236.


Update accounts-l1-l2.md

What :computer:

Fixing link to correct method

Why :hand:

Cause it was wrong

can you also fix it in https://docs.zksync.io/build/sdks/js/accounts-l1-l2.html ??


fix: bug 1593; scroll bar hides status text

Status area now includes a little right side margin bumper. Bumped up the area's allocation a bit while here

Regression fix: header needs to be always visible

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Is it possible to disable/modify default analytics.page() on page load?

I am attempting to use this module on static pages. Each static page must configure my application angular module. During this configuration I am configuring Segment using segmentProvider. I'm noticing that analytics.page() appears to be called each time a new page is loaded.
Is is possible to disable this?

This Angular integration module doesn't call any tracking methods automatically, so you'll want to find the correct functionality in Analytics.js itself.
There should be a way via the Analytics.js API .page() method, or maybe there's another configuration for it: https://segment.com/docs/libraries/analytics.js/#page.


Input frames when using EventGAN to generate events

Hi, thanks for your work, we want to use EventGAN to generate events according to the method in the paper.
But we're not quite sure that EventGAN's input is the anchor frame and its immediate predecessor, frames 10 and 11 of each sequence?

Hi thanks for your interest.
The generation of EventGAN is presented in our paper. The two frames are the t-1 and t frame of each sequence.


Glossbot not respecting image and name overrides

Hi @ekimia can you give me more detail on this?

sure. I have custom name and icon set in the slack app settings but I'm still seeing the lipstick icon and the name is still GlossBot


[Request] add custom scraper option

The actual scraper is not able to find the correct metadata.
The user experience will be improved adding a dedicated option for set a custom scraper.
Thanks

HI, same request for me, got a licence on emumovies, and i wish use it with Daijishou

The possibility might come with the 1.5 extension update.


Parceler support is too strong

After merging : https://github.com/f2prateek/dart/pull/76/files
@johncarl81 @iainconnor
we see a problem : devs need Parceler to serialize something like an ArrayList. It would even try to use Parceler if it is not available, making the intentfactory and extrainjector fail.
Good catch @dlemures !
So, we would like to make things a bit more subtile :

for collections whose elements use Parceler, use Parceler
for collections that are serializable whose elements don't use Parceler, use serializable
for collections that are not serializable whose elements don't use Parceler, they are not accepted
for types that use Parceler, use it (e.g. @Parceler class House)

Parceler serialization should be a fallback.  If you can serialize using a native technique then you should opt for that.

Yeah, that's exactly our problem right now. We are patching in https://github.com/f2prateek/dart/pull/93

This may be relavent if you're looking for a different approach to support Parceler: https://github.com/f2prateek/dart/issues/36

I think our current problem are not really solvable via adapters. But tomorrow we should get something stable on #93

Fixed.
Final strategy:

If Parcelable is available, and the collection can be handled by it (elements are Serializable, Parcelable or use @Parcel), use Parceler.
If Parcelable is not available, but the collection is serializable, we accept them.
If Parcelable is not available, but the collection is not serializable, we don't accept them (we cannot).


GH-44815: [C++][Parquet] Add an example to dump statistics read as arrow::ArrayStatistics

Rationale for this change
I want to use this in the C data interface statistics documents: https://github.com/apache/arrow/pull/43553
What changes are included in this PR?
Add an executable that reads an Apache Parquet file and dumps statistics read as arrow::ArrayStatistics.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

GitHub Issue: #44815

+1


stayrtr: 0.5.1 -> 0.6.1

Diff: https://github.com/bgp/stayrtr/compare/refs/tags/v0.5.1...v0.6.1
Changelog: https://github.com/bgp/stayrtr/releases/tag/v0.6.1

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351637

x86_64-linux

:white_check_mark: 1 package built:

stayrtr


update external_identifiers.yaml to support JGI metabolomics MASSIVE records

Per Emiley for GSP we'd like to link the JGI metabolomics data to NMDC study page. JGI metabolomics raw data is summited to MASSIVE so we can expect to need to reference these a common external link. My suggestion is that external_identifiers.yaml be updated to allow for MASSIVE records. An example record from Bioscales
https://massive.ucsd.edu/ProteoSAFe/dataset.jsp?task=83574f41458a4b259621d5c32a4d82f9
If it isn't too much additional work it would also be good to add functionally to link records at the biosample level (ie Gb0305843 is a biosample processed as part of this MASSIVE record). This is lower priority and can be broken into a separate ticket, I just thought it might be more efficient to support both at once.
If there are suggestions for supporting linking to these records without schema changes please let me know.

I'd like to start in this order:

Go back and constrain the patterns in external identifiers. For example, all GOLD external identifiers match "^GOLD:"
Add a massive_external_identifiers slot requiring the pattern "^MASSIVE:"

I guess it would be good to formally define that the prefix 'MASSIVE' expands to 'https://massive.ucsd.edu/ProteoSAFe/dataset.jsp?task='
assign the massive_external_identifiers to class Biosample (right?)
make valid and invalid sample data files

I don't think I understand the idea of linking records at the biosamaple level. I was going to assign the massive_external_identifiers to class Biosample, which already contains slots for GOLD identifiers. Do you think it would be better to assign XXX to a class that represents a metabolomics activity, like MetabolomicsAnalysisActivity?

Emiley's suggestion was to assign massive_external_identifiers to Study. The MASSIVE records are a collection of files and there isn't metadata at the sample level currently aside what is embedded in file names.

https://identifiers.org/MASSIVE

OK, thanks. That is how I implemented it. I'll be ready for some review in a day or tow.

massive identifiers slot added to external identifiers YAML file, assigned to Study
using the prefix proposed by @aclum


feat(auto-dialler): dial in parallel

Fixes issues brought up by @achingbrain:

the libp2p auto dialler (component that ensures we always have some good
connections) dials remote peers one at a time - one peer that takes ages to
respond can make this stall, so this needs to become parallelised

Features:

Makes auto-dialer dial in parallel
Prevents dialing to peer.id if peer.id is already being dialed to
Aborts all dial attempts if autoDialer is stopped

Note: With regard to the third item above: I added a parent AbortAbort to the autodialer that is aborted when ’autodialer.stop` is called, which would result in any connection attempts created by the auto-dialer to also be aborted.
A few changes we could make:

Don't cancel pending dials
Cancel only pending dials that have been pending for more than X time (add timeout to AbortAbort for the dial attempt)

Other things of note:

we're not currently passing through any signals (via options) to the auto-dialer. Do we want to?
If the signal passed to openConnection is aborted, but we have a successful connection, does the connection get aborted or just the dial attempt?

test failure restarted: https://github.com/libp2p/js-libp2p/actions/runs/4585538848/jobs/8097751623?pr=1668

@achingbrain something I wanted to call out about testing this over the weekend:
works fine with small peer counts.. with large peer counts, it falls over due to lack of exponential backoff and inability to reach a large number of peers. There is a lot of wasted effort due to

protocols that are obviously not supported. If we fail to utilize dns6/ip6/etc for any/all peers, but connect successfully on others, we need to filter those out - e.g. ip6 on my machine.
peers that are not dialable - should be bumped down in priority for connection attempts.
peers that are dialable are not prioritized - past successful connections to peers means we should probably try them first.
multiaddrs for remote peers advertising private IP addresses - not really sure how we would handle this up front, but if we cannot connect to a peer listing a private/local IP, we should probably ignore that multiaddr at some point.
large number of webtransport requests don't seem to be limited "inherently" the same as other browser requests - I've seen the dialer kick off 150 requests at the same time, and the browser seems to ignore them all. - we should probably have a config that accepts per protocol/transport/whatever limit instead of only global limits like we have now.
too many requests in parallel flooding the browser - we should probably be optimizing requests via batching. i thought that simply setting a config in connection-manager to limit the number of concurrent calls would limit the number of auto-dialer calls, but we can see in the code that auto-dialer is not reading and applying that config

Take a look at https://github.com/libp2p/js-libp2p/pull/1678 - it addresses most of the above points.

Closing because https://github.com/libp2p/js-libp2p/pull/1678 did a much better job of improving things =)


Set base font properties to html instead of p for using rems

In order to use rems, the base font properties need to be declared against the html tag.
This is how it should look like (in type.less):
html {
    font-family: @baseFontFamily;
    font-size: @baseFontSize;
    line-height: @baseLineHeight;
    p {
        margin: 0 0 @baseLineHeight / 2;
        small {
            font-size: @baseFontSize - 2;
            color: @grayLight;
        }
    }
}

Right, but we don't use rems anywhere in Bootstrap. Feel free to make this change yourself for now.


Fixes for 0.5

Use new string methods, and avoid inexact error when converting floats to integers in timestamp routine.

Current coverage is 99.20% (diff: 87.50%)

No coverage report found for master at f03041c.

Powered by Codecov. Last update f03041c...14049d2

Thanks for updating.


style: lint icons after generation

Description:
lint icons after generation
Motivation and Context:
Ensure that newly generated icons do not fail lint checks, and the existing icons are not regenerated with changes that fail our lint rules.
How Has This Been Tested?
Manually (run yarn generate-icons and verify existing icons are not modified.
Types of changes:
Lint fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 21.324% when pulling b44d91174edcd765f79845ff9798ff53c877ef33 on mrfelton:style/lint-icons-after-generation into 3daf176b1a3dd6fd983714418d4333f486c69fda on LN-Zap:next.


[TK-14] Add the "Register Member" page

Pull Request
Story ID: TK-14
Title: [TK-14] Add the "Register Member" page
Card URL: https://trello.com/c/jucjkVw1
Author: @ptchp


why buffers auto close

I've open two files in vim
vi a.txt b.txt
Then I switch from a.txt to b.txt
:b 2
Everything works well. However, when I switch from b.txt back to a.txt, b.txt closed!
:b 1
Why this happens?
How should I switch buffers? Is there any key mappings?

Use Ctrl + ^ to cycle between buffers


Exception List - Teacher attendance showing no data found

Processed the teacher attendance file , teacher attendance exception showing no data found

@FaizanMohammed326 @padmanabha1234 above defect is fixed ? have you done unit test ?

Re-tested the defect is Resolved

The issue is fixed


django-webpack-loader unable to render react code

let me begin by stating I am a novice at fullstack development, I learned a bit of react and django separately and am really hoping not to get discouraged into switching to a different backend framework simply because I can't get past this issue.  FORGIVE ME if the issue I am about to post is not strictly because of django_webpack_loader, but I have been digging all over google/SO/GH for a solution and can't seem to figure out how to solve it.  all i'm trying to do is to get react and django to speak to one another while following this blog http://owaislone.org/blog/webpack-plus-reactjs-and-django/
basically when I run webpack first to bundle the files, I get no errors, then when I run python3 manage.py runserver next, I get no issues.

when I access http://<IP_ADDRESS>:8000/, the browser shows up blank where I expect to see the sample react code (the hello world example from the tutorial).  when I inspect the page in google chrome, the

WOOSH well it finally went, can't believe i struggled for days and solved it hours after posting, so i really hope this post helps somebody else.
first of all the blog link i posted above is from a while ago, understandable that things have changed since.  this post helped me initially.
https://github.com/ezhome/django-webpack-loader/issues/62
the blog doesn't say to import ReactDOM, you definitely should.  the post however doesn't update the render function in the index.js from React.render to ReactDOM.render.  This made it work for me.  once i decided to change the imports to es6, I got a new error in the console, found an SO post that led me to the solve.


Query on restricted tables

[Enter feedback here]
I understand that this article is specific to Dynamics 365 Sales. However, perhaps it should include a reference to this article as well: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-restricted-entities
Also, the other article doesn't mention any of the Sales restricted tables.
From a user perspective, I think it better to have the restricted tables defined in one place only.

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

ID: 68c0cb1f-4699-3076-64bf-9fdcfec3fe9f
Version Independent ID: 68c0cb1f-4699-3076-64bf-9fdcfec3fe9f
Content: Verify license compliance
Content Source: ce/sales/license-enforcement.md
Service: dynamics-365-sales
GitHub Login: @lavanyakr01
Microsoft Alias: lavanyakr

Thanks for your comment, @feridunkadir. This issue has been assigned to the doc author for review.

Hi @feridunkadir
Thanks for your feedback. The license checker feature has been rolled back a week ago. We'll consider this suggestion if the feature gets released in the future. Closing the comment for now.
Have a nice day!


chore: fixing zone from which to fork a new zone

Which problem is this PR solving?

This will fix partly the bug mentioned here
https://github.com/open-telemetry/opentelemetry-js/issues/1206

Another PR will be in contrib

Does this preclude the need for the rxjs/angular plugin, or are you still doing that?

Can you add a test? Since all the tests were passing before I would like to see an example of one that would be broken without this change to more easily understand what is going on.

Does this preclude the need for the rxjs/angular plugin, or are you still doing that?

No the mentioned plugin will be needed in case to fully support context propagation in angular between our plugins like with promiseQ etc. So this is to fix creating new zone from active instead of root always - this was wrong from the beginning.

If it was always wrong how did the tests pass?

If it was always wrong how did the tests pass?

cus it wasn't tested ?

This specific case obviously wasn't tested but it raises the question if we have tests that actually test a real world scenario with some popular frameworks. In addition to unit tests that test specific behavior of some functions or classes, we should have functional or integration tests that instrument a demo application and test the full lifecycle of the app making sure expected spans are generated at the end.

@obecny Thank you so much for the fast turn around on this. You mentioned there will be another PR in contrib to fix this and probably that's why but this fix alone does not fix the bug. You probably are obviously aware of it but just wanted to share in case there was some miscommunication.

This specific case obviously wasn't tested but it raises the question if we have tests that actually test a real world scenario with some popular frameworks.
We don't and to achieve that there was already issue raised long time ago

https://github.com/open-telemetry/opentelemetry-js/issues/650
Without having e2e test we can't test real world scenario
@mayurkale22 @dyladan ^^

We need to add integration tests sooner rather than later. This is must requirement for GA / 1.0.

@open-telemetry/javascript-approvers this is a high priority bugfix please review