Older version libraries coming as dependency

[ ] Steps to reproduce
Add<EMAIL_ADDRESS>library to package.json, it will add<EMAIL_ADDRESS>as dependency. In return<EMAIL_ADDRESS>is adding<EMAIL_ADDRESS>instead of latest. And this version is having a dependency on yargs-parser. Which is failing for contrast.
[ ] Expected behavior
The application should run with contrast but its failing when contrast is enabled. As yargs-parser referred is older version and creating problems.
[ ] Actual behavior
Contrast enabled server fail to start and gives a message.
"ERR npm WARN<EMAIL_ADDRESS>requires a peer of jest@>=24 <25 but none is installed. You must install peer dependencies yourself."
[ ] Node version
10.16.3
[ ] SDK version
IBM SDK for Node.js Buildpack v4.3-20200606-1928

When you open an issue for a feature request, please add as much detail as possible:

[ ] A descriptive title starting with the service name
<EMAIL_ADDRESS>SDK for Node.js
umanam
umanam
23 Jun 2020 (an hour ago)

I'm using<EMAIL_ADDRESS>and it is using<EMAIL_ADDRESS>This is using ts-jest as dependency and loading older version<EMAIL_ADDRESS>There is the problem and its failing in contrast build.
I get error "ERR npm WARN<EMAIL_ADDRESS>requires a peer of jest@>=24 <25 but none is installed. You must install peer dependencies yourself." while deploying application, even fixing with these suggestion its not helping. At the end its conflicting on version of yargs-parser library referenced in ts-jest. Please fix the issue with  ibm-cloud-sdk-core package.json, so that it loads correct version of dependencies.

[ ] A description of the problem you're trying to solve
We want to enable fetch of latest ts-jest  library with latest<EMAIL_ADDRESS>Testing --- Repackage library ibm-cloud-sdk-core and invoke in a project then try if its pulling latest ts-jest or not.
[ ] A suggested solution if possible

Thanks for the issue. We are removing ts-jest as a dependency in the next version, which will be v3.0.0, and this problem will go away.

We were actually able to fix it without a breaking change, this is now fixed in v2.4.2


Support for multiple availability zones in an OpenStack region

Description
osc-core\osc-server\src\main\java\org\osc\core\broker\rest\client\openstack\vmidc\notification\runner\OsDeploymentSpecNotificationRunner.java:139:                    // TODO: Future. Openstack. We need to decide should we piggyback on region/zone/name of the AZ.
Expected Behavior
Actual Behavior
Based on the TODO comment it looks like it could become a bug  if there are more than one availability zone for a given region.
Steps to Reproduce
Additional Information
Merged DE3918
Environment

OSC Version/Build:
Cloud Provider Info:
Plugin Info:
Other:

Status

[ ] Reproduced
[ ] In Progress
[ ] Validated     =>    Verified in Version/Build:

@emanoelxavier Please provide more information on this.

@opensecuritycontroller/osc_triage this originated from a TODO in the code but looking a little deeper this does not seem to surface as functional issue. We are listening to all events related to the region of the DS availability zone instead of just the AZ itself which seems more inclusive. We can probably optimize this further. However I also see from the code that it seems for DS we are listening to events related t host aggregate only, see OsDeploymentSpecNotificationRunner :
private OsNotificationObjectType getMemberObjectType(DeploymentSpec ds) {
        // TODO: Future. Openstack. Later add support for Object Type AZ and Host as well.
        return OsNotificationObjectType.HOST_AGGREGRATE;
    }

This seems more concerning. @ychoma can you ensure our test cases cover notifications related to DS for AZ, host aggregate etc? If the test cases encounter functional issues related to this we should track those as new issues and address something a bit more targeted.

@ychoma Please check the notification scenarios for AZ and other ways where we have in creating deployment specs and create issues.

@larkinscarvalho I remember that you made a change to listen to all notifications.     Not sure if your fix is related at all to AZ and host aggregate.
Please let me know.

@ychoma We still listen to host aggregate events only realted to DS. No changes were made to OsDeploymentSpecNoyifocationRunner.java

@ychoma , could you revert back?

My understanding is that from the code it looks like we are getting notification from AZ only if it's related to DS,  so we will get notifications about our virtual appliances.
For security groups, we don't have the option of grouping by AZ -  only by networks - subnets - and VMs   (The other option is all servers)
It seems like we shouldn't have a problem.  for security groups and for AZ - so should have no problem.
I recommend to close this issue - since we didn't see any real issue with AZ

@ychoma , is this been validated with DS with multiple AZ for a given region?


Implement an Event Hubs Connection String Parser

Summary
Event Hubs allows for authorization using a shared key and shared access signature that is supported using a service-specific shared access key credential.  It is common for the shared key or shared access signature to be passed with the service endpoint and entity path as part of a connection string.  To align with best practices, we would like to guide library users to down the path of using credentials for authorization within production applications.   In order to assist with transforming a connection string for use with credential-based client creation, a parsing utility is desirable.
Scope of Work

Design and implementation of a means for parsing a Event Hubs connection string into its components.  These should include:

FullyQualifiedNamespace
Endpoint
EventHubName
SharedAccessSignature
SharedAccessKeyName
SharedAccessKey

The parser should adhere to the current validation rules for connection string correctness.  For example:

Only one form of authorization should be allowed (shared key or shared access signature)
The Endpoint must be present
The EntityPath is optional
All tokens which are present must have an associated value

The EventHubName reflects the EntityPath token of the connection string, if present.

The host name of the Endpoint should be reflected as the FullyQualifiedNamespace.

Unknown tokens in the connection string are rejected or ignored; they are not reflected in the set of parsed tokens.

The parsed values should be treated as read-only, if idiomatic to the language.

The proposed surface area of the parser, as well as any associated types that change the public API surface should be reviewed with the language architect, and approval obtained.  Full board review is not necessary.

Success Criteria

The design of a parser detailed by the scope has been completed and approved by the language architect.

The parser has been implemented according to the design and is exposed as part of the public API of the library.

The tests necessary for its validation have been created or adjusted and pass reliably.

The existing test suite continues to produce deterministic results and pass reliably.

References

Follow-Up: Client Creation Discussion
Client Creation Discussion

SB _parse_conn_str method (in azure\servicebus\_base_handler.py):
def _parse_conn_str(conn_str):
    # type: (str) -> Tuple[str, Optional[str], Optional[str], str, Optional[str], Optional[int]]
    endpoint = None
    shared_access_key_name = None
    shared_access_key = None
    entity_path = None  # type: Optional[str]
    shared_access_signature = None  # type: Optional[str]
    shared_access_signature_expiry = None  # type: Optional[int]
    for element in conn_str.strip().split(";"):
        key, _, value = element.partition("=")
        if key.lower() == "endpoint":
            endpoint = value.rstrip("/")
        elif key.lower() == "hostname":
            endpoint = value.rstrip("/")
        elif key.lower() == "sharedaccesskeyname":
            shared_access_key_name = value
        elif key.lower() == "sharedaccesskey":
            shared_access_key = value
        elif key.lower() == "entitypath":
            entity_path = value
        elif key.lower() == "sharedaccesssignature":
            shared_access_signature = value
            try:
                # Expiry can be stored in the "se=<timestamp>" clause of the token. ('&'-separated key-value pairs)
                # type: ignore
                shared_access_signature_expiry = int(
                    shared_access_signature.split("se=")[1].split("&")[0]
                )
            except (
                IndexError,
                TypeError,
                ValueError,
            ):  # Fallback since technically expiry is optional.
                # An arbitrary, absurdly large number, since you can't renew.
                shared_access_signature_expiry = int(time.time() * 2)
    if not (
        all((endpoint, shared_access_key_name, shared_access_key))
        or all((endpoint, shared_access_signature))
    ) or all(
        (shared_access_key_name, shared_access_signature)
    ):  # this latter clause since we don't accept both
        raise ValueError(
            "Invalid connection string. Should be in the format: "
            "Endpoint=sb://<FQDN>/;SharedAccessKeyName=<KeyName>;SharedAccessKey=<KeyValue>"
            "\nWith alternate option of providing SharedAccessSignature instead of SharedAccessKeyName and Key"
        )
    entity = cast(str, entity_path)
    host = cast(str, strip_protocol_from_uri(cast(str, endpoint)))

    return (
        host,
        str(shared_access_key_name) if shared_access_key_name else None,
        str(shared_access_key) if shared_access_key else None,
        entity,
        str(shared_access_signature) if shared_access_signature else None,
        shared_access_signature_expiry,
    )

SB _parse_conn_str method (in azure\servicebus\_base_handler.py):
def _parse_conn_str(conn_str):
    # type: (str) -> Tuple[str, Optional[str], Optional[str], str, Optional[str], Optional[int]]
    endpoint = None
    shared_access_key_name = None
    shared_access_key = None
    entity_path = None  # type: Optional[str]
    shared_access_signature = None  # type: Optional[str]
    shared_access_signature_expiry = None  # type: Optional[int]
    for element in conn_str.strip().split(";"):
        key, _, value = element.partition("=")
        if key.lower() == "endpoint":
            endpoint = value.rstrip("/")
        elif key.lower() == "hostname":
            endpoint = value.rstrip("/")
        elif key.lower() == "sharedaccesskeyname":
            shared_access_key_name = value
        elif key.lower() == "sharedaccesskey":
            shared_access_key = value
        elif key.lower() == "entitypath":
            entity_path = value
        elif key.lower() == "sharedaccesssignature":
            shared_access_signature = value
            try:
                # Expiry can be stored in the "se=<timestamp>" clause of the token. ('&'-separated key-value pairs)
                # type: ignore
                shared_access_signature_expiry = int(
                    shared_access_signature.split("se=")[1].split("&")[0]
                )
            except (
                IndexError,
                TypeError,
                ValueError,
            ):  # Fallback since technically expiry is optional.
                # An arbitrary, absurdly large number, since you can't renew.
                shared_access_signature_expiry = int(time.time() * 2)
    if not (
        all((endpoint, shared_access_key_name, shared_access_key))
        or all((endpoint, shared_access_signature))
    ) or all(
        (shared_access_key_name, shared_access_signature)
    ):  # this latter clause since we don't accept both
        raise ValueError(
            "Invalid connection string. Should be in the format: "
            "Endpoint=sb://<FQDN>/;SharedAccessKeyName=<KeyName>;SharedAccessKey=<KeyValue>"
            "\nWith alternate option of providing SharedAccessSignature instead of SharedAccessKeyName and Key"
        )
    entity = cast(str, entity_path)
    host = cast(str, strip_protocol_from_uri(cast(str, endpoint)))

    return (
        host,
        str(shared_access_key_name) if shared_access_key_name else None,
        str(shared_access_key) if shared_access_key else None,
        entity,
        str(shared_access_signature) if shared_access_signature else None,
        shared_access_signature_expiry,
    )


Typo in update version preventing it from updating.

There's a problem with the updated manifest URL for Starfinder. It lists the version as v0.26.1 instead of just 0.26.1. As a result, it keeps saying there's an update available for Starfinder, and when you do update it, it shows that it updated from version 0.26.1 to version 0.26.1. Uninstalling and reinstalling doesn't fix it.

I see this every time I updated all my systems and modules. Continually tells me it can only update to 0.26.1.

If they removed the v from the front of the version number, it should fix it. Of course, I don't know if they're actually going to fix it since they're playtesting Starfinder 2e.


Ring buffer overflow is not properly handed in uart.c

When more data is written to UART ring buffer than its size is, it should not write more than it's size to USB. Buffer structutres cnt_in and cnt_out values must not be used to track how much data must be send to USB.
When buffer overflow is happening, oldest data must be overwritten with new one. When data is sent to USB, no more than buffer size must be sent.
Used project was k20dx_frdmk64f_if and DAPlink version 0242

I've seen this issue also. This shouldn't happen normally if host application read serial data fast enough, but if host doesn't read for a while and meanwhile device send buffer amount of data to daplink this happens. So this is kind of corner case depend on host side implementation. Should be quite easy to fix.

Created PR #179 to improve overflow behavior.

PR merged so this issue should be fixed.


chore: drop GHA CI for linux

We are using Aspect Workflows so it's redundant

Doesn't really reduce our CI load that much for the added complexity


Empty Option Chains for Future Options

Expected Behavior
No need to define SetFilter for the underlying future. The option chain should have the mapped contract.
Actual Behavior
If we need to set the filter.
Potential Solution
N/A
Reproducing the Problem
# region imports
from AlgorithmImports import *
# endregion

class BasicFutureOptionAlgorithm(QCAlgorithm):
    def initialize(self):
        self.set_start_date(2023,1,1)
        self._future = self.add_future(Futures.Indices.SP_500_E_MINI,
            extended_market_hours=True,
            data_mapping_mode=DataMappingMode.OPEN_INTEREST,
            data_normalization_mode=DataNormalizationMode.BACKWARDS_RATIO,
            contract_depth_offset=0)
        #self._future.set_filter(0, 182)   # < --uncomment to get options

        self.add_future_option(self._future.symbol, lambda u: u.strikes(-1, 1))

    def on_data(self, data):
        # Iterate all Option chains to find the desired future and future options contracts
        for canonical_symbol, chain in data.option_chains.items():
            future_contract = canonical_symbol.underlying
            for symbol, contract in chain.contracts.items():
                contract.strike

        # Get the Option chain for the mapped contract
        chain = data.option_chains.get(Symbol.create_canonical_option(self._future.mapped))
        if chain:
            for symbol, contract in chain.contracts.items():
                contract.strike

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

By the way, it would be nice to be able to get the chain with the underlying symbol:
chain = data.option_chains.get(self._future.mapped)


[ownership] Update the ownership utils infrastructure to treat mark_dependence as forwarding.

We have already been forwarding ownership in terms of ValueOwnership and
OwnershipUtils, I just had not setup certain parts of the ownership utils to
recognize mark_dependence as forwarding of guaranteed values. We did not hit
this before since we have not had been late enough in the pipeline to get
mark_dependence on guaranteed values.
In the future, we want to move to mark_dependence only taking guaranteed
values. This is a first step in that direction that at the same time allows me
to enable ownership lowering after diagnostics sooner since fixing the bigger
issue would be a relatively medium sized project.

@swift-ci test


Support MXNet

/kind feature
Support MXNet in KFServing
Since Kubeflow has an MXNet operator, it would be great if MXNet models could also be served with KFServing, as otherwise there is little use for it except in research.

I believe MXNet is deprecated at this point and joins the pytorch community.. so we do not have plan to support and maintain MXNet, you can always build custom model server to serve MXNet model, thanks.

@yuzisun Do you have a link to the deprecation notice because MXNet looks alive: https://github.com/apache/incubator-mxnet
Some APIs (Symbol, Model) have been deprecated.


Security warning messages from the operator pod on Openshift

Deployment of camel-k operator 2.x (main branch) on Openshift results in 2 messages of security warning from the operator pod.
The first one is from the generation of the builder pod:
{
"level":"info",
"ts":1685437946.119213,
"logger":"KubeAPIWarningLogger",
"msg":"would violate PodSecurity \"restricted:latest\": allowPrivilegeEscalation != false (containers \"builder\", \"s2i\" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (containers \"builder\", \"s2i\" must set securityContext.capabilities.drop=[\"ALL\"]), runAsNonRoot != true (pod or containers \"builder\", \"s2i\" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers \"builder\", \"s2i\" must set securityContext.seccompProfile.type to \"RuntimeDefault\" or \"Localhost\")"
}

The second one is from the generation of the integration pod:
{"level":"info",
"ts":1685438084.8166873,
"logger":"KubeAPIWarningLogger",
"msg":"would violate PodSecurity \"restricted:latest\": allowPrivilegeEscalation != false (container \"integration\" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container \"integration\" must set securityContext.capabilities.drop=[\"ALL\"]), runAsNonRoot != true (pod or container \"integration\" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container \"integration\" must set securityContext.seccompProfile.type to \"RuntimeDefault\" or \"Localhost\")"
}

These have been observed on local tests using CRC.
Follow up from issue Operator is not able to push builder image to the internal registry (OpenShift cluster).

@squakez I'll look into it.


Activation Removal

How to control degrees of activation removal in this code?

The removing of activation is organized in the model part. Since the model is organized like LEGO, the activation can be set to be false to restrain its using.

Set relu's inplace parameter to false to disable relu?


Feature: Aeroplanes Index API

Description
Exposed API endpoint for aeroplanes index data according to #6
Changes

Created a aeroplanes controller action for API
Added some data to seed

Kanban Progress

Front End PR
https://github.com/rubydevi/jetlogix-frontend/pull/5

Thanks @RileyManda for the review. I will merge it now.


Filter Activity Stream by Component

The current behaviour of the plugin is to provide a summary of the opened issues filtering by component (jira/component) and project (jira/project-key) as well as displaying the activity stream for the whole project.
Would it be possible to make it so that the "Activity stream" shows only the activity for the issues related to the Component identified by the annotation jira/component rather than displaying the activity for the whole project jira/project-key ?

+1 on this, removing the activity stream is good in this situation, another option could be to add an Epic and pull only issues from a specific Epic into the activity stream

I've been testing an option to filter the activity stream and I think I found a solution for it.
In our company's JIRA instance we have a filter by issue-key, so I changed the issueTypeCounter to a paged request getting only the issue key and the issue type object to reduce the amount of data. Then I use a .reduce() to make the count as before and, finally, I store a list of issue-keys. That list will be used to fetch the stream instead of the project key:streams=issue-key+IS+(list of issue keys). I also found out the confluence activities might be filtered out as well, at least for our case.
If you want to, I could create a pull request for that, I guess it's the only possible option to filter the activity stream right now, but only if your company has the issue-key filter available.


Feature/application

What is this pull request?
Concrete class that contains instances of components which are shared in the system
Why do you implement it? Why do we need this pull request?
It will be used in main application during system initialization, used by Torii, and other components
How to use the features provided in the pull request?
Instantiate this class in main application, handle the errors and ensure the correctness of component initialization, and pass it to other components
Details/Features
Application class which contains following instances:

Ametsuchi storage
Peer communication service
Crypto provider
Hash provider

Will Application be expected to consist of other all modules?

@motxx idea is global modules knows about other modules. Each module by itself separate services by responsibilities  and provide only part of interface.
For example, stateful validation should know about ametsuchi?
Proposal validate(Proposal, Ametsuchi)
But this is bad interface. For performing validation you should use only temporary database state (without affecting on blockstore) - interface will be:
Proposal validate(Proposal, TemporaryWsv)
We reduce responsibility of validate interface.
For using it in business logic you should invoke like this:
// peer communication class
auto verified_proposal = validate(proposal, ametsuchi.getTemporaryWsv())
So, what happens? Global module PeerCommunicationService know about ametsuchi, but parts like stateful validation works only with small part of it.

@muratovv
class PeerCommunicationService : public TransactionPropagator,
public ConsensusListener {};

I'm sorry, I pushed the close button by mistake. Looks nice for me.

In my opinion, and
-- In the future iroha, this is only memo --
If there is application in hyperledger/iroha, There is class Application in libs/application. and it has
virtual void initialize();
virtual void commandParser(int argc,char* argv);
virtual void run();
...

and There is class Irohad : private Application{} in irohad/main/irohad.hpp.
I think Application is separated from irohad/main is better.
but, Is it complex?
-- --
or
I propose we use name class Irohad instead of class Application

@MizukiSonoko
I don't mind for renaming. Pls, commit changes in this branch.

Ok
Can I rename like this?
class Irohad instead of class Application

Yes, u are.

@motxx
Could you review and merge it?


Filename issue when saving a structure

The function saveStructure is not saving the files with the correct name.
The default names appearing are: "Chromosome_0_block0"

Adding to this:
The structure is only saved correctly when adding the TypetoType force because it loads the type_list variable.

@junioreif , is this issue solved?

This is now implemented and released on versions >= 1.0.5


Add photo-z (for object catalog) tutorial

Here's a simple tutorial for the newly added photo-z "add-on" to the object catalog (1.2i). The photo-z catalog was provided by @sschmidt23 and the reader is currently in PR https://github.com/LSSTDESC/gcr-catalogs/pull/266.
To run this notebook, you will need to use GCRCatalog at https://github.com/LSSTDESC/gcr-catalogs/pull/266.
You can preview the rendered (but not run) notebook here. I also plan to generate a rendered one and push to the orphan rendered branch (but this may not happen today).
I am creating this PR now so that people can have a chance to provide ideas. Right now the example is very basic and I am sure people have better use cases to show.

A rendered and run (with current desc-python) notebook can be found here.

I think these address the changes I have, so am happy approve from my side.

Thanks, @reneehlozek. I'll wait till Monday to merge in case @rmandelb has some thoughts.

Thanks, @rmandelb. I addressed the typos and the first and the third points you raised. I'll do the fourth one later (or, leave it out if I cannot find time).
@sschmidt23 may have something to add about the second point.

Thanks.  I've preemptively approved your changes, since I think even if we don't add something for my 2nd point, it's still ready for people to play with and learn from.

:+1: thanks! I'll merge this tonight in case Sam has anything to add.

For the first point, if you plot the 10 PDFs individually, you'll see that three of them are almost identical, which photoz_mode = 0.885 (may be common redshift solution for e.g. u and g-band non-detections if there aren't a lot of exposures in that particular patch), maybe switch to showing 10 panels in subplots rather than 1 plot with 10 PDFs?
For the second point, I did compute a p(z) for every object in the database, regardless of how it was flagged.  Different groups may have different ideas for what constitutes a "viable" p(z), it's one of the things I was hoping for feedback on.  I didn't include the BPZ standard "ODDS" parameter, but we can re-create it from the PDFs if people would find it useful, or there are alternative criteria out there for determining whether a photo-z is "good".  A good place to start is some signal-to-noise threshold in at least a few of the "central" bands, e.g. gri or riz, depending on the redshift range that you care about.  I modified the notebook to add snr requirements for g and r in addition to i in the demo notebook.
I added a simple set of redshift cuts and a couple comments, feel free to edit or not include these if they are not helpful.  Sorry, I don't have a ton of time today to look at these.

@sschmidt23, thanks for the additions! That looks great. I've done a little clean-up and also added you as a notebook owner (i.e. author).
The rendered notebook can be found here.
I plan to merge this tonight.

For the sake of those who might not be aware, I recommend changing "Let's compare the histogram of photoz_mode values to the sum of the individual PDF values, the "stacked" PDF being a common way of estimating redshift distributions" to "Let's compare the histogram of photoz_mode values to the sum of the individual PDF values, the "stacked" PDF being a common (but not statistically correct) way of estimating redshift distributions" - i.e., insert that parenthetical clarification so people  know this isn't actually correct (despite being a common method of inspecting p(z) for an ensemble).
This looks great - thanks very much @sschmidt23 and @yymao !


Add reference to metrics on primary and standby during cutover

Fixes DOC-9168
This PR adds a reference (on the physical cluster replication page) to metrics during the cutover period for the primary and standby clusters.
This came about after a customer asked what happens to metrics in the case where they fail over and then fail back to the primary cluster.

TFTRs!


Add startupinfo to hide subprocess window

Hide the subprocess that runs kindlegen.exe when the program is performing the .mobi creation, to prevent the user from losing focus on what they are doing while a conversion is being done.

D'oh! Sorry for not noticing this Windows-only quirk.
This is probably due to me removing the STDIN=PIPE in

#633
https://stackoverflow.com/questions/24455337/pyinstaller-on-windows-with-noconsole-simply-wont-work

@VampiroMedicado D'oh! Sorry for not noticing this Windows-only quirk.
This is probably due to me removing the stdin=PIPE in

#633
https://stackoverflow.com/questions/24455337/pyinstaller-on-windows-with-noconsole-simply-wont-work

You want to try putting it back? I notice a console window opens at EVERY point I call subprocess.run, including 7z, etc.
You can generate an exe with
python setup.py build_binary

Seems like the removal of Popen is intentional #581.
What about using a utils function def silent_subprocess to handle this?

@VampiroMedicado
Subprocess.run and popen have the same args. Re-adding stdin=PIPE everywhere as an arg should work.

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Yeah, it sounds better now.
I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅
I'll update the PR tomorrow.

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Yeah, it sounds better now.
I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅
I'll update the PR tomorrow.

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Yeah, it sounds better now.
I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅
I'll update the PR tomorrow.

Actually, the proper way to do this is to use the
creationflags=CREATE_NO_WINDOW,

arg in subprocess.run

Yeah, it sounds better now.
I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅
I'll update the PR tomorrow.

I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅

I was basing this on the stackoverflow answer, but it seems to not be true.
Also, the CREATE_NO_WINDOW constant is Windows only and throws an Import Error on mac.

I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅

I was basing this on the stackoverflow answer, but it seems to not be true.
Also, the CREATE_NO_WINDOW constant is Windows only and throws an Import Error on mac.

I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅

I was basing this on the stackoverflow answer, but it seems to not be true.
Also, the CREATE_NO_WINDOW constant is Windows only and throws an Import Error on mac.
https://docs.python.org/3/library/subprocess.html#windows-constants
ImportError: cannot import name 'CREATE_NO_WINDOW' from 'subprocess' (/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/subprocess.py)

What about using a utils function def run_silent_subprocess to handle this?

Sounds good, it just needs to check for windows or not.
It seems this issue stemmed from not using the unsafe shell=True...

The current solution works right in Mac? I only have a Windows desktop.

I was checking the docs and found nothing about how stdin=PIPE might interact with Windows Shell, but I'm not near my computer to test it. 😅

I was basing this on the stackoverflow answer, but it seems to not be true.
Also, the CREATE_NO_WINDOW constant is Windows only and throws an Import Error on mac.
https://docs.python.org/3/library/subprocess.html#windows-constants
ImportError: cannot import name 'CREATE_NO_WINDOW' from 'subprocess' (/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/subprocess.py)

What about using a utils function def run_silent_subprocess to handle this?

Sounds good, it just needs to check for windows or not.
It seems this issue stemmed from not using the unsafe shell=True...

The current solution works right in Mac? I only have a Windows desktop.

Yes, Mac and Linux don't create extra console windows already. This is windows only issue.  Just write your code so it doesn't throw an import error on mac

Yes, Mac and Linux don't create extra console windows already. This is windows only issue.  Just write your code so it doesn't throw an import error on mac

Hi, @axu2 happy new year 🎉
I made some changes, utils.py has the helper function and replaced any ocurrence of subprocess.run with it.

@axu2 changes done.
Tested on Windows without issues.

Looks great, I'll include these fixes in the next release!

I've decided to backport this fix to v5.6.5. V5.7.0 is in prerelease and gets fewer downloads than v5.6.5


Allow switching between updates from LS and document change listener

This could be done with a link similar to the ones we already have for switching between Syntax Tree / Haxe / JSON. If updates from the LS are enabled, the document change listener is disabled and vice versa.

Note: I think a dropdown list would be better than links, but I already tried that for switching between JSON / Haxe / Syntax Tree and couldn't make it work (setting window.location via JS didn't seem to do the job).


Transcriptome File Type

I am attempting to work through your processing examples using my own data sets, and I do not recognize your transcriptome length file type in the run construct_batch pre-processing step (gg_200524_mouse_genome_polyA_cum_1 in your example).
Any assistance on how to generate this file type would be greatly appreciated.

The file type is just a space-separated list in format [name, length, # polyA of length > 4, # polyA of length > 5, ...]. The notebooks used to make these are here:
https://github.com/pachterlab/GP_2021_3/tree/master/processing_scripts/make_references


Add color support

This adds support for settings a color for each task. The default color for all tasks is green (same as the current uniform color).
Fixes #8

Will this support conditional coloring based on value/threshold?

The current PR does not implement conditional colors. Could you give an example of the use case you'd like to see?

I am using Gantt chat to display the dependency tree of services/requests. Below is an example of this from Azure Application Insights. If we notice the below image, we can see if a request status code is error then the corresponding bar is displayed in red. It would be amazing to do the same thing with your Gantt chart tool.

Side Note: It would be nice to have a parent-child relationship support as well. I will open a separate issue regarding this.

Gotcha. Currently, the Gantt panel only expects three dimensions: label (string), start, and end time. AFAIK configuring a color schema works best for number fields. If we introduce an "Color by" dimension, you could use it for thresholds. I'll look at it this week.

yes it should be conditional based on threshold. Thats i what i imagined to be the extra Dimension for. so we can chose which of our fields shall be the provided threshold input

Is it possible to colour based on another column rather than just legend items?
I'm stacking ids vertically, and ideally I'd like each block to have different colour based on a map.

Now I think about it more, colouring types of tasks would be useful even in a true gantt chart layout too

If possible, I'd like to use Grafana's built-in color support here. The Grafana plugin API offers a display function that returns a color based a value within the field, which would means that the color logic is handled by Grafana rather than in the plugin. The downside is that it only supports using numbers to conditionally set colors.
We could add the Color by dimension, and decide on how to handle it based on the type. If Number field, use Grafana field options (supports thresholds), and if String field, use custom logic. The question then would be what strings you'd expect.
My first instinct would be that it would default to color by the text/label dimension, e.g "Task 1", "Task 2". It would then work like shown in the GIF in the description. The question then is how you set the colors when using a string field. If you selected to color by a category, would you still want to configure the colors using the legend? Also conditionally setting a color based on the text would likely require some custom controls that, frankly, should go in Grafana imo.
I don't think returning hex colors from a data source is the right way to go. While it does give a lot of customizability, it also promotes conflating data with its presentation. You'd either have to store the colors in the database, or you'd need a query language that would supports conditional logic.

From my perspective I need to be able to assign based on a value in an arbitrary column (which would  be one of the labels) - I’m not quite sure if that fits in with what you are proposing though?


fixed confirmation selector on Moulton

This yaml does not need this update.
The find step you've changed works as is. Find will look for a selector (in this case, h1) with the text "Form Confirmation", which in this case is enough to be successful. Being more selective on the selector does not improve the yaml, and indeed makes it potentially more fragile, if the member of congress makes minor updates to the selectors they use on this site.

Thanks for the info on it!


Unable to get the pod up and runnning

What version of Kubernetes (kubectl  version) are you using?
OpenShift Master:   v1.5.1
Kubernetes Master: v1.5.2+43a9be4
What version of etcd (etcdctl --version) are you using?
etcdctl version: 3.1.9
API version: 2
What version of ReShifter are you using (for rcli: rcli version otherwise at the bottom of the app)?
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2+43a9be4", GitCommit:"43a9be4", GitTreeState:"clean", BuildDate:"2017-05-24T15:22:02Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"
Development only: what version of Go (go version) and dep (git describe --tags) are you using?
v0.3.14-alpha-6-g62c1c3f
Issue:
Unable to get the pod up and running.
Error:
Getting exec error. Following are the pod logs.
panic: standard_init_linux.go:178: exec user process caused "exec format error" [recovered]
reshifter-app-1-0z5jb.log.txt

Hello Michael,
I was trying to evaluate Re-Shift for an internal project but I'm getting the above error when trying to bring up the pod. Any help is highly appreciated.
Thanks,
Sreekanth

Sreekanth, thanks for trying ReShifter! Now, I'm trying to figure what exactly you are doing so that I can help you here. So, can you please clarify: are you trying to launch the app? And if so, using what command?

Hi Michael,
Appreciate your quick response, I cloned the repo and tried the command given for deploying it on Openshift.
make init
make publish
After the above commands when I login to my openshift console, I can see the pod up but it is crashing frequently, with the logs showing the error that I attached as per my initial query.
Thanks,
Sreekanth

Ah, got it, thanks @sreekanth-ragi for clarifying this. Let me try it out again (has been some time) and come back to you and share if I can replicate it or not, OK?

Sure Michael, appreciate all your help
Thanks,
Sreekanth

Ah, I already know what it is :)
I moved the app to app/ around 4c6356e12adae8f0344726c9d32e0005fdd99f95 but never got to update the OpenShift-related build commands, my bad :(
There should really be test cases for this!

Awesome Michael, so could I simply do a git clone now and will be good to go or you would need more time to fix it.
Thanks again for all your efforts and help
Sreekanth

I'm testing it ATM and yes, once done you only need a git pull (not clone) and you should be good.

Sure Michael, will await for your test results.

Update: still on it, seems to be a little bit more complicated bug (the other thing mentioned above was also due to be fixed but the harder one is the OCI runtime error). So, please stand by, first thing in the morning I'll look into …

OK, figured it out thanks to the awesome @soltysh … the fix is coming very soon now @sreekanth-ragi

@sreekanth-ragi can you do a git pull and then try again the make init please?

@mhausenblas : Build process is failing with the following error
Step 9 : RUN curl -sf -L 'https://github.com/mhausenblas/reshifter/releases/download/v'$rversion'-alpha/reshifter' -o reshifter &&     chmod +x reshifter
EnvVar Value for rversion=0.3.20

Looks like it is an issue with github certificates, I'm not able to open the link directly from the browser either with a security/phishing warning being thrown.

So @sreekanth-ragi you're saying that you can't (in your browser) download from https://github.com/mhausenblas/reshifter/releases/download/v0.3.20-alpha/reshifter yes?

Can you do me a favour @sreekanth-ragi and do a make build now, should resolve it …

OK, so once you've sorted out the cert issue, can you do the make build then? I've updated the instructions accordingly …

@mhausenblas : Sure will let you know once I run the build

@mhausenblas: I was able to run the build successfully and can now see the pod deployed.Thank you a lot for all your efforts and support in getting this resolved.
Thanks,
Sreekanth

Thanks for the confirmation @sreekanth-ragi and glad to see the outcome. Closing this one now.


[WIP][PoC][Flatbuffer] Revisit Flatbuffer interpreter

Revisit Flatbuffer Interpreter for export nntr(circle_plus) format
Add FLatbuffer export method for FullyConnected Layer
will be upload unittest

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2230. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @DonghakPark, The last line of a text file must have a newline character. Please append a new line at the end of the line in nntrainer/compiler/flatbuffer_interpreter.cpp.

:octocat: cibot: @DonghakPark, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2230-202306181108170.34402394294739-9955bcab02dccb1811418ed88e25c3018faef720/.

This Item Pending and will replace with ONNX Importor
So i will Close this PR


feat: Included Norwegian translations for Vuetify

I'd prefer making these changes on a global level here

We should either remove all translation stuff from here, or still get this merged if you got errors that the no translations could not be found. That is a bug here with telling Vuetify to use no, but not actually including no @tfk-kaare.

So were adding this one here? @tfk-kaare

Yes.. lets :-)


Cannot use R because of undefined symbol in readline

miniconda3/lib/R/bin/exec/R: symbol lookup error: miniconda3/lib/R/bin/exec/../../lib/../../libreadline.so.6: undefined symbol: PC

Thanks! What is you channel setup?

Only default. forcibly enabling conda-forge with conda install r -c conda-forge.

The one from the r channel does not seem to have this issue.

Could it be that when you did that installation readline was already present, but coming from defaults? This would explain it, because the readline from conda-forge is likely configured a bit different. The recommendation is to either install everything from conda-forge or everything from defaults. The two are not binary compatible.

gotcha. There were some similar issues with gdal.
Some low-level packages are still missing in conda-forge (util-linux on linux and others) which makes not possible yet to have a pure conda-forge miniconda ...

I will try from a new clean miniconda.

Pure is not necessary. It is sufficient to have conda forge as highest priority channel.

The following CI build seems to show that even with conda-forge being at the higher priority, we have that issue:
https://travis-ci.org/SylvainCorlay/xtensor-r/jobs/242504699
The conda documentation says:
*The command conda config --add channels new_channel adds the new channel to the top of the channel list, making it the highest priority. *
cf https://conda.io/docs/channels.html

I see. @conda-forge/core, are you aware of this?

After adding the channel, you'll have to update everything. conda update readline should do it

@isuruf @jakirkham not sure if related to this issue but there is something fishy. You can reproduce this in the lastest condaforge/linux-anvil Docker image.
(root) [root@7a5e32daa30d /]# conda --version
conda 4.2.13
conda create -v -p /usr/local -c conda-forge r-yaml r-base  # -> readline 6.2-0 & r-base 3.3.2-5
conda create -v -p /usr/local -c conda-forge r-yaml         # -> readline 7.0-0 & r-base 3.3.2-1

Please note that r-base was compiled with readline 6.2.* as seen here: https://github.com/conda-forge/r-base-feedstock/blob/master/recipe/meta.yaml#L40. So we should never ever get readline7 and I would also expect the same packages in both cases.
I also tested it with conda 4.3.21 and got the same results.

build-0 and build-1 of r-base are unpinned and should probably be tagged as damaged or removed.
However, this is probably also a conda bug in resolving the dependency tree.

However, this is probably also a conda bug in resolving the dependency tree.

IMO when conda solver gets a lower build number when triggle o grok the pinned dependencies is a bug.
But since I gave up that discussion I will label them as broken to avoid headaches.

@ocefpaf thanks! Any issue where I can assist you in this discussion?

@ocefpaf thanks! Any issue where I can assist you in this discussion?

We had many in conda-forge's early history. Not worth digging them up. I would open a new one if you want to revive that discussion.
PS: just to be sure you mean r-base build 0 and 1, right?

Yes, r-base. You fixed it in: https://github.com/conda-forge/r-base-feedstock/commit/eb951ec69358293b36330afc79627c2645fc92b9
@kalefranz do you have any idea about this bug?

Yes, r-base. You fixed it in: https://github.com/conda-forge/r-base-feedstock/commit/eb951ec69358293b36330afc79627c2645fc92b9

Should be OK now. Let me know if you still see issues with build number >2
PS: continuum's policy with build number is non-intuitive and different from the packaging world. They hotfix the packages instead of bumping and using the latest one. That is fine, but what we consider a bug they consider a feature :smile:

mh, interesting! Thanks for fixing and the explanation!
@SylvainCorlay hope it is fixed for you as well. Please feel free to reopen if not.

Hotfixing or removing packages is necessary because conda considers all build numbers when resolving dependencies.  If a package contains incorrect requirements simply releasing a new build will not solve the issue because this does not invalidate the older build(s).
There have been discussions about changing this behavior so that only the latest build is considered but before this can be done some additions to conda and likely conda-build are needed.
Consider the case where a package which depends on jpeg is needed with the requirements pinned to jpeg8 and separately jpeg9.  Two packages are required and the solver should consider both when resolving dependencies.  The two packages would likely have the same version and dependencies (besides the jpeg pinning) and would likely differ either by build number or by using a different build string.  If they differ only in build number then restricting the solver to using only the latest build would cause issues. Changing the build string is a better option but the solver does not take this information into consideration.  Assigning meaning to the build string at this point seems to me a bad idea.

@jjhelmus, but if I am not mistaken, what you describe will be solved by conda build 3 where the build string is replaced by a hash, right?

@johanneskoester I don't think the hash in the build string added by conda build 3 really effect this issue.  The hash will change if the package's requirements change but conda still lacks a mechanism to communicate if this change is an update to correct invalid requirements or an entirely different build.

I was talking about your jpeg pinning story. This would get reflected in the hash, and therefore one would not necessarily need to update the build number. Hence, build number could be used for fixes only. However, I have not really thought this through.

I would be possible to have the two jpeg packages maintain the same build number.  The difference in the hash would differentiate the version of jpeg in the requirements (foo_py27habcdef_1.tar.bz2 and foo_py27h0123456_1.tar.bz2) although this can already be done by explicitly setting the build string in the recipe (foo_py27jpeg9_1.tar.bz2 vs foo_py26jpeg8_1.bz2).  In either case the solver would need to assign significance to the build string which is currently does not.

I don't think so. In both cases, it can say, when the build number is the same, I consider both packages for my solution and choose the one that fits. Without looking at the build string at all. And then, it can always consider only the latest build number. But I think this introduces other problems because you have to keep the build number synchronized. Maybe removing broken packages is just fine. It should be ok to advice people to not pin against build numbers in their environments.

There have been discussions about changing this behavior so that only the latest build is considered but before this can be done some additions to conda and likely conda-build are needed.

@jjhelmus just to be clear I am not complaining! My mind set is biased to what happens in the linux world.
From the conda point of view conda-forge is broken when we assume that lower build number should not be considered.
I would welcome the change in the behavior, but if we (conda-forge) do our pinning properly and move unpinned software to the "broken" label everything works just fine too.

@johanneskoester You are right, with the hash as long as the build numbers of the two packages are synchronized the solver doesn't need to consider the build string.  Having to rebuild all variants to invalidate one may be burdensome for some packages but if the build number of the good packages can be patched even that might not be needed. I'll have to give it some though.

This sort of issue with default serving higher build numbers or version numbers makes me think that it could actually be very useful to create a conda-forge miniconda with conda constructor...

Please see this, @SylvainCorlay. Still needs a lot of work including figuring out the name to use.


fix: Use record input props instead of auth

Fixes #250, Supersedes #309

Is there any practical difference with this? In initialization, _record_state_props is still set at the exact conditions as _auth_state_props and is set exclusively for authority. So non-authorities have both variables empty/null. And authorities have both non-empty.


Can I horizontal scale with myself ?

I want to know. Can I horizontal scale Nakama Server with my own server. And use orther function like replica, backup, etc in your enterprise version.
Or I MUST buy your enterprise version only for scale or backup feature ?

@PePoDev Yes, but please ask questions on the forums.

I found some projects with nakama cluster, but I'm not sure it works:
https://github.com/renowncoder/nakama-doublemo-cp
https://github.com/doublemo/nakama-cluster


build(deps): bump kube-rbac-proxy from v0.11.0 to v0.14.1

What type of PR is this?

bump kubebuilder/kube-rbac-proxy from v0.11.0 to v0.14.1

What this PR does / why we need it:

bump kubebuilder/kube-rbac-proxy from v0.11.0 to v0.14.1

kube-rbac-proxy image is stale.

Which issue(s) this PR fixes:

none.

Is the purpose of the upgrade to solve any real problem?

/retest


string_util: added functions for string operations

Added functions:

strcmp: compare strings
strlcpy: copy strings safely

-added include maths to string_util.cpp
-optimized strlen

@ndousse Is it ready to merge ?

The code is ready to be merged, the question remained of where do we used these new functions? Does @basil-huber want to use these new functions in this PR or in the other big one?
If it's in the other one, for me, we can merge this PR.

Yep,
And for small PR like this (with many merge commits from master), squash+merge make more sense than merge.

So let's merge the other one first, because we'll have to merge it back anyway before merging the second PR


HD Retrovision cables

I recently installed the Turbonanza kit in my PC Engine system. I tested both a standard Saturn RCA cable and the HD Retrovision cables. On the RCA is got a picture and sound however on the HD Retrovision cables I got no picture and a buzzing sound and no other audio. I was wondering if these cables are compatible or if there is another mod I need to make to the system. The 10 pin din connector did show up with some damage on the outside shell indicating that it might have be crushed during shipping but since the RCA side works I am not sure what to check next?

Could you please email pictures to @.***?
Thanks,
Zack
On Tue, Aug 8, 2023 at 07:44 superbulk @.***> wrote:

I recently installed the Turbonanza kit in my PC Engine system. I tested
both a standard Saturn RCA cable and the HD Retrovision cables. On the RCA
is got a picture and sound however on the HD Retrovision cables I got no
picture and a buzzing sound and no other audio. I was wondering if these
cables are compatible or if there is another mod I need to make to the
system. The 10 pin din connector did show up with some damage on the
outside shell indicating that it might have be crushed during shipping but
since the RCA side works I am not sure what to check next?
—
Reply to this email directly, view it on GitHub
https://github.com/zaxour/TurboNanza/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU7A2VKGSWDD4EGLWBOAXXTXUI7EDANCNFSM6AAAAAA3IQFJ3Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Documenting thread-safety of DiffRowGenerator

Expected Behavior
Confirm the thread-safety on javadoc of DiffRowGenerator
Actual Behavior
Can not find the information about thread-safety  from javadoc
Steps to Reproduce the Problem
see https://github.com/wumpz/java-diff-utils/blob/master/src/main/java/com/github/difflib/text/DiffRowGenerator.java

Specifications

Version: current version
Platform:
Subsystem:

DiffRowGenerator should be threadsafe . However it was not intentionally designed so. Creating one is very cheap using the builder, so why reuse the generator between different threads?

@wumpz
I tried not to create DiffRowGenerator every time to reduce the  objects generated as much as possible.
Now, I understand that the cost of the creation of this object is cheap, so I do not need to share it in multi-thread. Thank you.


feat: add support for dagger

Codecov Report

Merging #1 (7fa7818) into main (33d39de) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           23        23
=========================================
  Hits            23        23

Impacted Files
Coverage Δ

src/gitlab/jobs.ts
100.00% <100.00%> (ø)

src/gitlab/pipeline.ts
100.00% <100.00%> (ø)


Adding etcd

What do you think about using etc.d to share configuration for the messaging clusters that are spun up, so each daemon wrapper can pull down the configuration details it needs to know about how to set up the given messaging framework?
What were your thoughts on how you wanted this implemented?

Yep, that's pretty much exactly what I was thinking. Also allowing daemons
to register themselves so the client doesn't necessarily have to specify
peers. For example, maybe I start a bunch of daemons across different
machines. It would be nice if the client didn't have to know each IP and
instead just says "run producers/consumers on 5 peers."
On Sat, Jan 10, 2015, 9:24 PM savorywatt<EMAIL_ADDRESS>wrote:

What do you think about using etc.d to share configuration for the
messaging clusters that are spun up, so each daemon wrapper can pull down
the configuration details it needs to know about how to set up the given
messaging framework?
What were your thoughts on how you wanted this implemented?
—
Reply to this email directly or view it on GitHub
https://github.com/tylertreat/Flotilla/issues/2.

That would be nice, or to have a cluster of daemons register themselves with a cluster of clients all using different connection profiles (Comcast). So either way it would be nice if they could all know about each other easily.

alright, after looking this over here is my proposal
Create a new package, coordinator (lightweight service discovery server)
So to get things running  you would start a coordinator
flotilla-coordinator
Start some clients
flotilla-client --coordinator http://localhost:81818181/ --flota "testrun5"
flotilla-client --coordinator http://test.mycoolhost.com/ --flota "testrun5"
flotilla-client --coordinator <IP_ADDRESS> --flota "testrun5"
Start some servers
flotilla-server --coordinator <IP_ADDRESS> --flota "testrun5"
This is an interesting setup because it should let you be able to do a fleet based deployment of docker containers to a cluster on EC2 or wherever (using coreos of course)
https://github.com/coreos/fleet

Are you seeing the coordinator as something that would go in place of etcd? It'd be easy enough to roll something simple since it basically just needs to listen for a heartbeat from the daemons and add/remove them from the registry when they spin up or die. Just making sure I understand.
I'm trying to understand your example use case, but I'm not sure if I completely follow. The clients are still kicking off the benchmarks, right? In this case, you'd be running three different benchmarks? Why are you starting the servers after the clients?

I understand your confusion now that I have actually walked through your code in more depth. Forget the coordinator for the moment (I was thinking of embedding etcd but that is a hassle). This would be much simpler.
start etcd somewhere both the client and the server are going to be able to talk to it.
./etcd

flotilla-server --coordinator <IP_ADDRESS> --flota "testrun5"

server registers itself and establishes heartbeat. (heartbeat not really 'needed' for first pass)
could do that here
https://github.com/tylertreat/Flotilla/blob/fa5c03018a49451dd406127da7c8eebd4744b8de/flotilla-server/main.go#L31
flotilla-client --coordinator <IP_ADDRESS> --flota "testrun5"

client pulls down all active registered 'peers'
could do that here in the client
https://github.com/tylertreat/Flotilla/blob/master/flotilla-client/main.go#L55
It would be easy to expand it out eventually do share configuration details but since you are already sending out the specifics of the test from the client to the servers directly there is no reason to change all that just to have them pull it down from etcd.

Yeah, that sounds good to me.

K, I'l take a stab at it then

Initial pass here
https://github.com/savorywatt/Flotilla/tree/etcd
Ran into some flotilla-server compilation errors
github.com/tylertreat/Flotilla/flotilla-server/daemon/broker/pubsub
daemon/broker/pubsub/orchestrator.go:88: cannot use oauth2.NoContext (type oauth2.Context) as type []byte in argument to google.JWTConfigFromJSON: need type assertion
daemon/broker/pubsub/orchestrator.go:88: cannot use key (type []byte) as type string in argument to google.JWTConfigFromJSON

When I have everything working I'll do a PR

Google loves to break their oauth2 lib...
On Fri, Jan 16, 2015, 1:20 AM savorywatt<EMAIL_ADDRESS>wrote:

Initial pass here
https://github.com/savorywatt/Flotilla/tree/etcd
Ran into some flotilla-server compilation errors
github.com/tylertreat/Flotilla/flotilla-server/daemon/broker/pubsub
daemon/broker/pubsub/orchestrator.go:88 http://github.com/tylertreat/Flotilla/flotilla-server/daemon/broker/pubsubdaemon/broker/pubsub/orchestrator.go:88: cannot use oauth2.NoContext (type oauth2.Context) as type []byte in argument to google.JWTConfigFromJSON: need type assertion
daemon/broker/pubsub/orchestrator.go:88: cannot use key (type []byte) as type string in argument to google.JWTConfigFromJSON
When I have everything working I'll do a PR
—
Reply to this email directly or view it on GitHub
https://github.com/tylertreat/Flotilla/issues/2#issuecomment-70216839.

Yeah, it was just too late to deal with it, I'll hack on it later.
On Jan 16, 2015 8:41 AM, "Tyler Treat"<EMAIL_ADDRESS>wrote:

Google loves to break their oauth2 lib...
On Fri, Jan 16, 2015, 1:20 AM savorywatt<EMAIL_ADDRESS>wrote:

Initial pass here
https://github.com/savorywatt/Flotilla/tree/etcd
Ran into some flotilla-server compilation errors
github.com/tylertreat/Flotilla/flotilla-server/daemon/broker/pubsub
daemon/broker/pubsub/orchestrator.go:88 <
http://github.com/tylertreat/Flotilla/flotilla-server/daemon/broker/pubsubdaemon/broker/pubsub/orchestrator.go:88>:
cannot use oauth2.NoContext (type oauth2.Context) as type []byte in
argument to google.JWTConfigFromJSON: need type assertion
daemon/broker/pubsub/orchestrator.go:88: cannot use key (type []byte) as
type string in argument to google.JWTConfigFromJSON
When I have everything working I'll do a PR
—
Reply to this email directly or view it on GitHub
https://github.com/tylertreat/Flotilla/issues/2#issuecomment-70216839.

—
Reply to this email directly or view it on GitHub
https://github.com/tylertreat/Flotilla/issues/2#issuecomment-70262438.

Got the client pulling down the IP & port the daemon's are setting, all via etcd. Got some cleanup to do and more testing then I'll do a PR.
This fixed the google oauth2 problem https://github.com/savorywatt/Flotilla/commit/7be18010737a56c5bf95adf3f7b5d0c8390f20fe


Create IoT Device from site

@gcrev93 @howlowck  Can you add the screenshot and the required tech for each issue? That would be really helpful now and during Sync Week

@saroup there will be a published link with screen shots to correlate to the issues 😄

Screenshot

@howlowck  I think this task is about creating the device right from the webapp which requires connecting to azure apis to be able to do that. The screenshot you added is for adding a device that was already created from azure. This task is low in priority and Gaby put it in the backlog (instead of in the To do )


Missing features for 1.0 release

In this issue i will keep a list of features missing for mojo.js 1.0. The list will change regularly. Volunteers are welcome to propose an implementation. We do not port features directly from Mojolicious, they also have to use JavaScript best practices. It's best to discuss ideas on IRC (#mojo.js on Libera.Chat), so you don't end up wasting your time.

TypeScript

[x] Port everything (one module at a time is fine)

Cookies:

[x] Client/Server cookie encoding/decoding module
[x] CookieJar for client
[x] Signed cookies for the server
[x] Sessions for the server

Forms (application/x-www-form-urlencoded):

[x] Support client.post('/foo', {form: {a: 'b'}}) in the client
[x] Support await ctx.req.form in the server

Forms (multipart/form-data):

[x] Client/server multipart encoding/decoding module (maybe 3rd party?)
[x] Design API for the client (client.post('...', {formData: ...}), form values and file uploads)
[x] Design API for the server (await ctx.res.formData(), form values and file uploads)

Static:

[x] Last-Modified/If-Modified-Since/Etag support
[x]  Accept-Ranges support
[x] Design API for sending a static file from an action instead of rendering

Test:

[x] WebSocket methods (websocketOk, sendOk, messageOk, messageOk, finishOk)
[x] Make app.newMockContext().someHelper() work
[x] Full test coverage

Content negotiation

[x] respondTo method

General HTTP tools

[x] redirectTo (options for status and maybe some future proofing would be nice)
[x] urlFor method

Renderer

[x] renderMaybe method
[x] renderToString method
[x] Layouts for ejs (maybe as part of the plugin, or maybe as a renderer feature)
[x] Include for ejs (maybe with renderToString, or native ejs include)
[x] gzip compression

Commands:

[x] routes command
[x] get command (already exists, but needs more HTTP features)
[x] gen-lite-app, gen-full-app, gen-plugin (once we have settled on a structure)

Built-in templates

[x] Not found (can be ported directly from Mojolicious)
[x] Exception (can be ported directly from Mojolicious)
[x] Support for custom not found and exception templates
[x] Code preview on development exception page

Config plugin

[x] JSON config (no template for starters, but with support for mode specific files)

Server

[x] MOJO_SERVER_DEBUG=1 from Mojolicious (without performance loss if not used)
[x] HTTPS support
[x] Reverse proxy support (X-Forwarded-For, X-Forwarded-Proto)

Client

[x] Option to follow a certain number of redirects
[x] Basic authentication
[x] CONNECT and SOCKS proxy support (probably via custom agents like https-proxy-agent and socks-proxy-agent)
[x] HTTPS support (with insecure option for self signed certs)
[x] gzip compression

Condition support

[x] Design API on router layer (performance is important)
[x] Header conditions default pluginversion)

Hook support

[x] Design API (expected to be completely different than the Perl version, maybe events on app object)

Docs

[x] Tutorial giving a basic overview of the framework, similar to the Mojolicious tutorial (Markdown)

All features will need full test coverage. And make sure that there are no performance regressions. An easy test is:
$ node examples/hello.js server
...
$ wrk -c 100 -d 10s http://<IP_ADDRESS>:3000
...

Additionally we also have to extend the server-starter module with directory watch and restart capabilities. It will become the Node.js version of the Morbo development server.

server-starter
[ ] File watch and restart

Glad to see you Kraih to the JS world :) I was miss Mojo there.
While you are not too deep. Please consider starting the project with TypeScript natively. It has too many benefits to avoid.

@Snelius30 I'm still undecided about TypeScript. I'd really like to see what lib/file.js and lib/app.js would look like if they had been converted to TypeScript by an expert. Most large projects i've checked out so far that are using TypeScript seem to overuse generics a lot, making the code much less readable.

I've made a branch for TypeScript. It's not very hard to convert everything, but a little inconvenient while APIs are still changing a lot.

The project is already in the polishing phase for the 1.0 release. The last few remaining missing features from the list are mostly optional (aside from docs, which are in progress). Now is the time to start experimenting with APIs and figure out which parts don't work quite ideal yet.

And porting to TypeScript is finally finished.

The generator commands need to be redesigned to work for JavaScript and TypeScript. Open question is how to deal with the tsconfig.json and additional dependencies in package.json.

Main focus now is documentation.

Everything is ready for 1.0, just some polishing to do now.

We are ready. 😁


file flowers.dat not appearing

ADD ISSUE DESCRIPTION HERE
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

Traceback (most recent call last):
File "/workspaces/9780357880876_pld-10e-python-058c4c50-5488-413f-b74a-efcf4b304bbf/chapter7/ex01/student/Flowers.py", line 7, in
inputFile = open("flowers.dat", "r")
FileNotFoundError: [Errno 2] No such file or directory: 'flowers.dat'

/question

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Rediscover nodes under Home assistant tab

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method

[ x] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.0.0-beta.7
zwavejs version: 6.4.0
Describe the bug
When runing rediscover nodes under home assistant tab for a lock device (Danalock V3 and ID lock 150) some entities are removed.
Lock jammed entity is removed for all locks when runing rediscover nodes,
to get the lock jammed entity back you need to exclude the lock and include it again.
To Reproduce
Steps to reproduce the behavior:

Go to Home assistant tab in a lock device
Click on rediscover nodes
See error observe the entity list offerd for HA, multiple entitys are removed,

Expected behavior
runing rediscover nodes should not remove entitys
Additional context
Add any other context about the problem here.

I did try rediscover once more and the missing entitys are now back, closing


Support to configure the http agent

It will be great to be able to control the http agent so we can play with some settings to avoid some built-in features to be disabled, like the reuse of the TLS connection, DNS entry, ... So the timing will be quite similar on sequential calls.

The code set agent to false (https://github.com/prantlf/nettime/blob/master/lib/nettime.js#L224) - so the current issue should be irrelevant.
https://nodejs.org/api/http.html#class-httpagent


Extending Tapestry Plates doesn't work...

When extending the Tapestry overloading of the Plates Engine from a site Kernel, that extension is not made available to the templates with Tapestry returning a function not found error.
The project specific extension to the plates ExtensionInterface is executed, but doesn't appear to be carried over to rendering; write TTD and investigate why.

This is solved by 7dffd4beb4751830311ebd2937e536c96df4bb1b


endpoint for listing all loaded actions

the action server is starting up with a list of available actions:
INFO     rasa_core_sdk.executor  - Registered function for 'action_joke'.
it would be nice to get a list of loaded actions during runtime e.g.
GET /actions
['action_joke']

@jackfreed can I ask what you would use this for?

we wanted to use it for auto creating the domain.yml file and make sure the actions are properly loaded and thus available.


Setting default storage value to 0 for InstalledTechnology

@ChaelKruip and I thought it would be nice to do this last week but now a lot of spec/models/network-specs are failing.
@antw How can this be achieved in the 'nicest' way?

I'm not sure why this needs to default to zero. It's an optional attribute, and nil and 0.0 don't mean the same thing. nil means "this attribute is not relevant to this technology", and 0.0 means "this storage technology stores nothing".
Setting a default value causes the specs fail because InstalledTechnology expects irrelevant attributes to be nil when loading profiles; this will change when I deal with #125 (this week).

To clarify: I think it would be nice if the 'storage' attribute would get a default value for storage technologies only. In those cases, we already have values researched.
BTW: 'volume [kWh]' would perhaps be a better name IMHO. 'Storage' suggests to me that this is a bool indicating if this technology is able to store.

I think it would be nice if the 'storage' attribute would get a default value for storage technologies only.

Presumably this value would be non-zero and specific to each technology? If so, this would be better as part of the Technology model so that you could set different defaults on each one.

BTW: 'volume [kWh]' would perhaps be a better name IMHO. 'Storage' suggests to me that this is a bool indicating if this technology is able to store.

This will happen; I'll see to it tomorrow. :+1:

Can this be closed @antw @grdw ?

Can this be closed

Yes.
Volume and capacity are now imported from ETEngine. I don't think there's any need for Moses to define a default.


Fix group by time intervals

We were not properly setting seek/max bounds on cursors of partial buckets at the beginning and end of a tmax/tmin bucket.
The issue is best illustrated by looking at the added tests.
fixes #3926

Some important fixes, nice, +1.


Action buttons under messages don't work

the bottons for sharing, reply and 'heart' don't work.
when I press one nothing happends.
Only the botton to open the menu works.
The problem acured somewhen after I selected in the settings the gesture function.
I can't tell if it's related

Same issue too.
But I didn't made any changes at gesture options.
I'm using 35.05 version from Fdroid in a CM11 (Android 4.4). Maybe the problem it's there since I've upgraded to 35.05.

These action buttons are fixed in AndStatus v.36, please try https://github.com/andstatus/andstatus/issues/456

Strange, I just tried Reply button on the latest v. 38.02, and it works...
Which version are you using now and which button doesn't work?


Switching camera is not working at all.

.facing(backCamera ? QREader.BACK_CAM : QREader.FRONT_CAM)
i tried with this code. It continuously showing me the same back camera output only

finish();
overridePendingTransition(0, 0);
startActivity(getIntent());
Come up with this solution..!!! :(

@babulpatel1309 thats because once the singleton instance is initialized you can't modify the set values. I can however provide a function to do the same. As of now the library doesnot support this feature.

Another solution is :
 btnCameraSwitch.setOnClickListener(v->{
                backCamera = !backCamera;
//cameraSetting is parent view of surfaceview
                **cameraSetting.removeView(cameraView);
                cameraSetting.addView(cameraView);**
                initQRReader();
                if (qrEader != null)
                    qrEader.initAndStart(cameraView);
            }
        });

private void initQRReader() {
        if (qrEader != null && qrEader.isCameraRunning()) {
            qrEader.stop();
            qrEader.releaseAndCleanup();
            qrEader = null;
        }

        qrEader = new QREader.Builder(getActivity(), cameraView, new QRDataListener() {
            @Override
            public void onDetected(final String data) {
                if (System.currentTimeMillis() - lastScannedMilisec > minMilisecDifference) {
                    onScanQrCodeEvent(data);
                    lastScannedMilisec = System.currentTimeMillis();
                }
            }
        }).facing(backCamera ? QREader.BACK_CAM : QREader.FRONT_CAM).enableAutofocus(true).height(cameraView.getHeight()).width(cameraView.getWidth()).build();
    }

Closing as issue is outdated. Please open a new issue if the issue still persists.


Are the required field and custom validation supported for dropdown fields?

We are trying to make a dropdown field mandatory but it does not work.
Example of dropdown with required
   @Property(label = "Highlight Type", description = "Defines the type of the highlight.", order = 2, property = {
            "required=true",
            "widgetType=dropdown",
            "dropdownOptions=["
                    + "{'value':'thread','description':'Thread'},"
                    + "{'value':'event','description':'Event'},"
                    + "{'value':'video','description':'Video'},"
                    + "{'value':'podcast','description':'Podcast'},"
                    + "{'value':'article','description':'Article'}"
                    + "]"
    })
    String type() default StringUtils.EMPTY;

Example of dropdown with custom validation class.
    @Property(label = "Highlight Type", description = "Defines the type of the highlight.", order = 2, property = {
            "validation=highlight-type-mandatory",
            "validationMessage=Highlight Type field is mandatory.",
            "widgetType=dropdown",
            "dropdownOptions=["
                    + "{'value':'thread','description':'Thread'},"
                    + "{'value':'event','description':'Event'},"
                    + "{'value':'video','description':'Video'},"
                    + "{'value':'podcast','description':'Podcast'},"
                    + "{'value':'article','description':'Article'}"
                    + "]"
    })
    String type() default StringUtils.EMPTY;

Is this supported or will it be in the future?
Many thanks.

no, currently only "text-based input fields" are supported (as of https://wcm.io/caconfig/editor/validation.html, probably not written explicitly enough), that means text field, text area, pathbrowser.
it would be great to extend the validation support for dropdown fields, but it will be a bit tricky due to the combination of AngularJS and Granite UI. PRs would be welcome!
please note there is also a special property "required" to apply a required validation, this is easier then using a custom validation. but iirc it's also currently not supported for dropdown field for same reason.
i will take a not to improve the documentation around this.

many thanks for the quick reply @stefanseifert ! We'll take a look and see if we can come up with a PR.


Feature Request: Add ability to split files

Hi,
first of all thanks for the plugin. Before I had been using the unmaintained "a.vim" plugin and I am happy that there is an alternative to that.
Now to the feature request: Could you add commands that do not change the file in the current window but open the next file in a new window or in a new tab? Additionally it would be great if it just switches to the window/tab if the file is already open. It should be possible to enable and disable the switching of windows. I think not every user will like that behavior.

I have some reservations about this; I may need convincing. Mainly I'm concerned about contributing to the misunderstandings many users have with windows and tabs in vim.
Not only does using tabs in this fashion seem counter to what they actually represent in vim (layouts of windows), I'm also not sure how I'd even go about doing it. For windows, I can do it with bufwinnr, but I'm not aware of a similar function or technique for doing the same with tabs and I'm not sure I'd want to support it even if it existed.
Splitting windows is probably reasonable. There are a few edge cases that might put users in an unexpected spot (when they more than one window viewing a buffer, or previously had a buffer open in a window and thought vim would "remember" that), but I can accept those as things users would need educating about, I think.

My current thinking for this is as follows:

The cycling commands can use the postfix bang to indicate that they should try to switch you to an existing window on the target buffer if it exists.
The cycling commands can also take arguments which are used to define the command that will be run to actually edit the target file; if omitted, the behavior will be as if you passed "edit" as the argument.

This should let you encapsulate the window splitting behavior you outlined. For example, in your .vimrc,
nnoremap <leader>a :CounterpointNext! aboveleft vsplit

will map a command that tries to split the window vertically and open the counterpart on the left, unless the counterpart is already open in another window (in which case you are switched to that window instead).
I'm not 100% sure this is the best approach for the long term, but if you want you can pull the issue-6 branch now and try it out. It should work.

The proposed extension looks really promising to me. I think I can use the extended command to address all my use cases.
Important is the ability to split the window for source and header so I can see them both at the same time. Being able to so this with a single command would help me very much.
Thanks for your effort!

Merged to master.


Add support for gradle platforms

Gradle allows you to declare a platform which will suggest dependency versions so you don't need to manually specify them. Currently with these dependencies, the version is not found.
More info: https://docs.gradle.org/current/userguide/java_platform_plugin.html

Could you share your build script or an example which reproduces the issue?

I think it doesn't export the version for boms

Our buildscript is a bit... complicated haha but if you'd like, here's what I'm working with: https://github.com/MineInAbyss/Geary/blob/master/platforms/geary-platform-papermc/build.gradle.kts
The conventions plugins at the top add implementation(platform("com.mineinabyss:idofront-gradle-platform:${miaConventionsVersion}")) which can be found here https://github.com/MineInAbyss/Idofront/blob/master/idofront-gradle-platform/build.gradle.kts.
Anything currently using slim is what I'd like to move over to be spigot dependencies.

I think I found and fixed the bug. I also added an integration test to make sure this doesn't break

@0ffz It should work now when you use the latest release.
plugins {
  id("de.nycode.spigot-dependency-loader") version "1.1.0"
}

Can confirm it works, thanks!


Dynamic imports not working when acorn has resolutions

Describe the bug
Dynamic imports are not working with any version of acorn specified in resolutions field in package.json.
Did you try recovering your dependencies?

Yes, my yarn version is 1.22.5.
Which terms did you search for in User Guide?

I think every possible one.
Environment

Environment Info:

  current version of create-react-app: 4.0.2
  running from /Users/ochdev/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 11.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 15.8.0 - ~/.nvm/versions/node/v15.8.0/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 7.5.1 - ~/.nvm/versions/node/v15.8.0/bin/npm
  Browsers:
    Chrome: 88.0.4324.146
    Edge: Not Found
    Firefox: 84.0
    Safari: 14.0.2
  npmPackages:
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    react-scripts: 4.0.2 => 4.0.2
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce

(Write your steps here:)

Create new project with create-react-app
Add any version of acorn to resolutions field in package.json
Install deps yarn or npm i
Add any dynamic import to the project
Start project yarn start or npm run start
Go to localhost:3000 and see crashed app

Expected behavior

Dynamic imports should work as expected.
Actual behavior

Reproducible demo

https://github.com/ochmanski/cra-dynamic-import-acorn-res
Instructions are the same as cloning every new CRA project.
$ git clone git@github.com:ochmanski/cra-dynamic-import-acorn-res.git
$ yarn
$ yarn start

$ git clone git@github.com:ochmanski/cra-dynamic-import-acorn-res.git
$ npm i
$ npm run start

Any progress on this issue and i can replicate the same.


add HMap ++

close #40

Codecov Report

Merging #42 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
+ Coverage   82.62%   82.66%   +0.04%
==========================================
  Files          13       13
  Lines         374      375       +1
  Branches       21       20       -1
==========================================
+ Hits          309      310       +1
  Misses         65       65

Impacted Files
Coverage Δ

core/src/main/scala/com/stripe/dagon/HMap.scala
95.83% <100%> (+0.18%)
:arrow_up:

Continue to review full report at Codecov.

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


adal-node depends on @xmldom/xmldom that has a security vulnerability

Core Library
ADAL Node (adal-node)
Core Library Version
0.2.3
Wrapper Library
Not Applicable
Wrapper Library Version
N/A
Public or Confidential Client?
Public
Description
The adal-node package has a dependency on @xmldom/xmldom which in turn has a security vulnerability. Please see https://github.com/advisories/GHSA-9pgh-qqpf-7wqj
Error Message
No response
Msal Logs
No response
MSAL Configuration
N/A

Relevant Code Snippets
https://github.com/advisories/GHSA-9pgh-qqpf-7wqj

Reproduction Steps
https://github.com/advisories/GHSA-9pgh-qqpf-7wqj
Expected Behavior
Package should be installable without any npm audit errors
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
None (Server)
Regression
No response
Source
External (Customer)

Oh I just saw this #5300

The linked pull request will address this. Please be aware that adal-node is deprecated and will no longer be receiving any updates as of December 31st, 2022 You should migrate to msal-node ASAP.

The linked pull request will address this. Please be aware that adal-node is deprecated and will no longer be receiving any updates as of December 31st, 2022 You should migrate to msal-node ASAP.

Cross post to https://github.com/Azure/ms-rest-nodeauth/issues/146

@tnorling, would you release a new version, supposedly 0.2.4?

Yes, we have a release currently scheduled for next Monday. Will make sure this gets out. cc. @sameerag

Apologies the release slipped. @sameerag can provide updates. Reopening this until the new version is released

Since this is a one off release on an old branch, we hit some snag in the process. I am on it to resolve this and will update here as soon as I can. Thanks for reopening @tnorling!

Thank you ! Looking forward to an update

I believe the label is added unintentionally and we are still waiting for the update.

Released 0.2.4 with this change.


Implement Group Policy

Implementing group policy. Interface is roughly based on ExperimentalFeatures and UserSettings.
This is still a draft. Still pending:

E2E testing
Better reporting and logging
Use final registry keys/values from ADMX definition
Implement policies for additional/allowed sources
Showing policies enabled on winget --info

Related: #809 #154
Microsoft Reviewers: Open in CodeFlow

    // Settings can be loaded from settings.json or settings.json.backup files.

If settings is disabled by policy, we should just quit before ever even loading a file.

Refers to: src/AppInstallerCommonCore/UserSettings.cpp:252 in b96cf8a. [](commit_id = b96cf8a646f754d8c24206e26d462cbae9c8ba98, deletion_comment = False)

This is still missing E2E tests and the policies for controlling sources. I'll submit that as a separate PR as this one already got too big.


ModuleNotFoundError: No module named 'binance.um_futures'

Hi,
I'm quite new here.
I used to use "import binance.future"
I saw in the doc that it changed to 'binance.um_futures'.
I uninstalled package with 'pip uninstall binance-futures-connector'
Then i did a 'pip binance-futures-connector'
Since then i get the error ModuleNotFoundError: No module named 'binance.um_futures'
It works nice on my laptop, not at all on my second computer
Any ideas? thanks for help.

To install, you should run:
pip install binance-futures-connector
to verify if you have the package installed:
 pip list | grep binance-futures-connector
If there is no result, then the package is not properly installed. Please check the readme doc and make sure you can install the package.

I'm facing the same problem .
getting same error : "ModuleNotFoundError: No module named 'binance'"
pip3.10 list | grep binance-futures-connector
binance-futures-connector 3.1.1

We can't reproduce the error.

Same thing happened to me today while using Python 3.10. After downgrading to 3.9 it works without any issues.


use kcp-registrar to configure gateway in compute WS

In kcp-registrar script/image we already apply whats in environment/kcp in configure_compute_ws function. So no need for a seperate script image.

Waiting for the CI to be back online before merging.

/retest


Weird floating window resizing after update

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit c5e28ebcfe00a510922779b2c568cfa52a317445  ().
Date: 2024-03-16
Tag:

flags: (if any)

System Information:
System name: Linux
Node name: theseus
Release: 6.7.9
Version: #1-NixOS SMP PREEMPT_DYNAMIC Wed Mar  6 14:54:01 UTC 2024

GPU information:
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller])

os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.05.20240314.d691274"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.05 (Uakari)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.05 (Uakari)"
VERSION_CODENAME=uakari
VERSION_ID="24.05"

plugins:

Bug or Regression?
Regression
Description
Floating windows resizing become kinda weird after last update.
Tested with default config, same stuff. Problem occurs with all windows, so not app or toolkit specific stuff.
See vid
How to reproduce

Resize any floating window from smaller to larger, see the corner opposite to resize direction (top left on vid)
🤡

Crash reports, logs, images, videos
https://github.com/hyprwm/Hyprland/assets/142721811/9a955abf-ee26-44be-9137-989d88591e28

patch.txt
does this suit your tastes better?

Oh god, I don't want to compile stuff right now, if it's reproducible for you can you choose for your own taste?

for my own taste the above looks right

Nah, bad taste. Fixed when resizing to bottom right, but not otherwise. See vid
https://github.com/hyprwm/Hyprland/assets/142721811/43c85c5a-e586-4166-93c8-8895e0dcadc1

Also it not really fixed in this direction. I check older generation (like couple of days ago) and this stuff not appeared in it.

it would be stretched instead, which IMO is a worse option.

repaint artifacts are a bug though yeah I'll fix that

Like it work 100% perfect without any artifacts several days ago, so there must be a solution

it didn't work perfect, it would be stretched, again.

there, fuck off, it will stretch again.

This vid from some older commit, I don't see there anything worse than now. If it considered stretching, it's also appear now.
https://github.com/hyprwm/Hyprland/assets/142721811/f66c432c-32d5-472a-98a0-7a5fd711a356

I'd be worried for your eyesight if you can't see the jitter caused by the stretching

Yea, it jitter a bit, okay, I can see it. It wasn't work 100% perfect and I am wrong, very sorry.
But if border moving faster than window is much worse.


python3Packages.pytest-testinfra: 9.0.0 -> 10.0.0

Description of changes
https://github.com/pytest-dev/pytest-testinfra/compare/9.0.0...10.0.0
Because python3 is now python311, the salt package is now only built for Python 3.11.
Build for Python 3.10 in https://github.com/NixOS/nixpkgs/pull/267699 fails.

Things done

Built on platform(s)

[x] 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

[x] 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/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

@ofborg build python310Packages.pytest-testinfra python311Packages.pytest-testinfra


Update nightly used on CI for testing

Pull in a Cargo fix for flaky failures using -Zpackage-features

Thanks! Hopefully this fixes our CI issues...


Does not work.

[Enter feedback here]
Followed steps on the page.
kubectl get svc shows a load balancer with my external IP. However I cannot reach the target external IP. No default load balancer 404 page is received. It just times out. Have redid these steps several times with the same result.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 12009c1f-282d-2632-fac0-64b09c432833
Version Independent ID: 6052d3d4-d295-9340-b16d-4c200e34cd73
Content: Use ingress controller with static IP - Azure Kubernetes Service
Content Source: articles/aks/ingress-static-ip.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Suggest you mention that if you create a public IP and you add it to the resource group that acr nodes reside within, and associate it with a DNS that it may pick up the NSG rules associated with the cluster.

@garthoid
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@mlearned @zr-msft
Can you please check and add your comments on this doc update request as applicable.

Thank you @garthoid for the feedback.
The article has been verified to work as documented. If you continue to experience issues, please contact support.
#please-close

No, please see the comment above from last March as you are assuming something that was not clear to someone starting out. Nice try to do a quick close though.

FAIL @VikasPullagura-MSFT


Try to fix github pages deployment

The GH_TOKEN seems to have broke when I replaced the previous blanket-permissions GitHub API token with a fine-grained API token after getting a message that my previous token was compromised from GitHub.
The previous github pages deployment action is now archived. https://github.com/alex-page/blazing-fast-gh-pages-deploy
This new https://github.com/actions/deploy-pages does not seem to need an API token so hopefully this works

Not really, but I can try it in a dummy repository

I tried it here, https://github.com/keller-mark/gh-pages-test, it was useful, I found and fixed three bugs:

syntax error due to indentation
lack of runs-on in deploy step
needed to toggle the dropdown at https://github.com/vitessce/vitessce-python/settings/pages to enable the GitHub Action to publish to GitHub pages

Cool, well if it works, that sounds good then to merge.  It's as good as it will get for testing.


Navigating on mouse down is bad for accessibility

Navigating on mouse down instead of mouse up is bad for accessibility for several reasons:

It breaks the ability to drag and drop links.
You cannot "cancel" the navigation. (I often click something and, before releasing, realize I wanted to click something else.)
It can cause scrolling issues on mobile, where I only want to scroll but accidentally trigger navigation.

People expect links to work on mouse up and have adapted their workflows accordingly.
Relevant code: https://github.com/ethanniser/NextMaster/blob/24f8acae72bfb1bb7969b86b002f3a2a9c3cdc06/src/components/ui/link.tsx#L105

It's a tradeoff.

Don't drag and drop links.
Revert your action through other means.
Mousedown on mobile gets triggered the same as click: when you lift your finger son there are no issues here.


Run tests on older versions of Flutter

Newer versions of Flutter may introduce breaking changes or features additional features. During development and in CI, we use the latest version of Flutter. However, users may rely on an older version of Flutter instead, which don't have these new features or rely on an older API. As such, we should run tests on older versions of Flutter to check if Ably Flutter runs on older versions of Flutter.
We may want to discuss a few things:
What minimum version of Flutter should be supported?
When and how do we bump the minimum version of Flutter supported?
How many additional tests should we run?
However, because of the temperamental nature of failing tests, adding more (or doubling) test runs will increase the likelihood of encountering failing tests, slowing down the developer loop significantly. This is specifically because GitHub runners cannot just re-run 1 failed job (e.g. iOS test), but will run the entire workflow again (iOS, Android API level 29, API level 21). All of these tests need to pass in the same workflow to pass.

It was not possible to do this on Flutter 2.2.3, as described in https://github.com/ably/ably-flutter/pull/197


Updated Readme.md to make quality parameter better documented.

Added example of numbers that can be used for quality parameter and explained the current limit of numbers above the 83% quality threshold.
"equivalent to libjpeg quality" does not have inherent meaning to users without the context of the documentation.

I signed it!

"require modifying the code to go bellow the set threshold." - that can easily be interpreted as "require hacking the argument check to allow lower number" rather than "rewriting the compressor to tune it to lower values".
The check isn't there to annoy people and make them compile source with a lower number. It's there to stop people from wasting their time on using quality that this compressor isn't good at.

@pornel That's a very valid point I had not thought of. Is there by chance a way we can change that sentence so that we can still give a user heads up about the limit, and inform them that the compressor should not be bellow that threshold for the reasons you outlined? Or Perhaps we should remove that section from the read me and leave in the example "(0 - 100)"?

Perhaps something like this:

You can pass a --quality Q parameter to set quality in units equivalent to libjpeg quality (84 - 100). Guetzli works best with high qualities. 84 is the lowest supported quality.

@pornel Thanks the the example. I think that the wording is much more elegantly put in these terms.
I updated my pull request to include the text in your example.
Thanks again for the feedback!