First thing I had to face after starting my first VM is the fact that the self signed certificate that was installed automatically expired on November 9th. Just a few days ago.
I guess I'll be able to fix that, but every "vagrant up" will re-install the expired one, I assume.
Could you fix this in the code?
Or give me a hint as to what to modify in the yaml file to generate a proper certificate for each new site?
Thanks,
Christian

Just on the chance that you're referring to the certificate problem that happens when you're using a .app TLD, that's to be expected. At some point the way .app gets treated changed, which I assume is why it's still in some of the tutorial texts. Try using the .test TLD instead and see if that fixes your issue.


Carbon dashboard - Next iteration (v2) UX & Design

This work stream is related to defining the user journey and designs for the next iteration (v2) of the Carbon Dashboard.
Related design issue: KI User Journey Design Review (#478)
Roadmap card here: https://www.notion.so/klima-dao/Carbon-Dashboard-Next-Iteration-v2-84581acfbc7d4d339e9dc93d9332463f
Notes from design ideation meeting:

The Carbon Dashboard is meant to be a reference for industry, press, academic, etc
The home/landing page is meant to act as a total executive summary

Some users will just want the summary and not want to drill into the detailed reporting

Concepts that will help tell the story of tokenized carbon:

Mentioning the on the ground project
Nature vs mitigation credits
Top retired project

Design ideas to try and incorporate

Over time view
Representation of the percentage change
Tie the stats to real world impact, for ex:

hectares of forest
cars off the road
liters of gasoline saved
etc

Full liberty to suggest design changes to the landing page, lean towards more visual, possible use of infographics, animated gifs, etc.

Note: beyond the landing page, the other pages have limitations given the graphing library being used

@theprofessora recommend connecting with pkbims to discuss limitations of the chart/plotting library being used and technical feasibility of possible design suggestions.

Figma design in progress: https://www.figma.com/file/mXI4SzNNmoefYnOdcbXZcO/Carbon-Dashboard?node-id=1563%3A901


Onboarding wizard tweaks

Summary
Fix various UI issues with use case onboarding. Also change max allowed team length to 64 characters (from 15).
Ticket Link
https://mattermost.atlassian.net/browse/MM-29946
https://mattermost.atlassian.net/browse/MM-42050
https://mattermost.atlassian.net/browse/MM-42057
Screenshots
https://user-images.githubusercontent.com/13738432/155454626-e9cbeb95-c34e-40e4-8610-cfffd262952b.mp4
Release Note
Change max allowed team length to 64 characters

@matthewbirtch 1-3 have been addressed, and the server has been re-initialized if you could take another look. Will address 4 when I do the horizontal centering.

Re-requested review since I added horizontal alignment and progress line alignment issues.

/update-branch

/cherry-pick cloud

Cherry pick is scheduled.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-webapp
   50a30531d..e6fe0b6c9  cloud      -> upstream/cloud
   c613883c2..9959d81c4  master     -> upstream/master
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-mattermost-webapp-#9867-upstream-cloud-1645725713
Switched to a new branch 'automated-cherry-pick-of-mattermost-webapp-#9867-upstream-cloud-1645725713'
Branch 'automated-cherry-pick-of-mattermost-webapp-#9867-upstream-cloud-1645725713' set up to track remote branch 'cloud' from 'upstream'.

+++ About to attempt cherry pick of PR #9867 with merge commit 9959d81c412038eb00c1a6996de451f6562aac6f.

error: could not apply 9959d81c4... Onboarding wizard tweaks (#9867)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'

+++ Conflicts detected:

UU i18n/en.json
Aborting.

+++ Aborting in-progress git cherry-pick.

+++ Returning you to the master branch and cleaning up.

Cherry pick completed manually.


Failed login for missing InResponse to at top-level Response node

I'm integrating with an IdP that does not provide InResponse attribute as top-level Response node.
They provide the InResponse value as attribute of the node at Response/Assertion/Subject/SubjectConfirmation/SubjectConfirmationData.
I looked at the specs and it seems that InResponse atribute for top-level Response node is optional.
Would you consider to edit the Response validy check method to look in Response/Assertion/Subject/SubjectConfirmation/SubjectConfirmationData for InResponse if top-level Response does not have it?
It would mean that the lines https://github.com/onelogin/php-saml/blob/5fbf3486704ac9835b68184023ab54862c95f213/src/Saml2/Response.php#L199-L201 would change to this:
if ($this->document->documentElement->hasAttribute('InResponseTo')) {
    $responseInResponseTo = $this->document->documentElement->getAttribute('InResponseTo');
} else {
    $confirmationData = $this->document->getElementsByTagName('SubjectConfirmationData');
    if ($confirmationData->length > 0) {
        $responseInResponseToNode = $confirmationData
            ->item(0)
            ->attributes
            ->getNamedItem('InResponseTo');
        $responseInResponseTo = $responseInResponseToNode
            ? $responseInResponseToNode->nodeValue
            : null;
    }
}

Note how nothing would change if InResponseTo is part of the top-level Response node.
Maybe the retrieval of InResponseTo could be moved to a separate method, something like:
    private function getInResponseTo()
    {
        if ($this->document->documentElement->hasAttribute('InResponseTo')) {
            return $this->document->documentElement->getAttribute('InResponseTo');
        }

        $confirmationData = $this->document->getElementsByTagName('SubjectConfirmationData');
        if ($confirmationData->length <= 0) {
            return null;
        }

        $responseInResponseToNode = $confirmationData
            ->item(0)
            ->attributes
            ->getNamedItem('InResponseTo');

        return $responseInResponseToNode ? $responseInResponseToNode->nodeValue : null;
    }

I'd be happy to send a PR.

I looked at the specs and it seems that InResponse attribute for top-level Response node is optional.

The spec describes it as an Optional attribute but it refers to the case of IdP-initiated SSO
On an SP-initiated flow, the InResponseTo on the SAMLResponse MUST exist
Extracted from SAML core documentation
Section <IP_ADDRESS> Complex Type StatusResponseType

InResponseTo [Optional]
A reference to the identifier of the request to which the response corresponds, if any. If the response is not generated in response to a request, or if the ID attribute value of a request cannot be determined (because the request is malformed), then this attribute MUST NOT be present. Otherwise,
it MUST be present and its value MUST match the value of the corresponding request's ID attribute
value.

So I can't accept your suggestion.
The SubjectConfirmationData elements and its InResponseTo attribute, are both optionals.
That why is only checked if present and not required in the code

Hi @pitbulk and thanks for your thoughtful response.
Reading carefully the specs you're indeed correct. But I can also assure you that there are implementations out there that are not compliant because I'm dealing with one of them (.NET-based IIUC).
The code I proposed would not affect standard-compliant servers but would be error-tolerant. But I can understand you don't want to tolerate errors.

The SubjectConfirmationData elements and its InResponseTo attribute, are both optionals.

I saw that and in fact, my implementation tries to read them and would cause no error of sort if those optional node and/or attribute are not present.
All that said I totally understand if you are not willing to accept my proposal (please close this issue if so). In that case, I will try to deal with the non-compliant server in some way.
Thanks for your time anyway.

You can always extend the SAMLResponse and Auth classes with the custom classes with the specific changes your project requires, overriding the specific methods.


xeofs

Description
Suggestion  of adding xeofs to xarray-contrib.
xeofs enables fully multidimensional PCA / EOF analysis and related techniques with large datasets, thanks to the integration of xarray and dask.
References:

Documentation
JOSS review

Code Repository
https://github.com/nicrie/xeofs
License
MIT
Xarray Support

[X] Yes

PyPI/Conda-forge

[X] Yes

Documentation

[X] A user guide or tutorial
[X] Usage examples
[X] API reference

Unit Tests/Continuous Integration

[X] Yes

PEP8 compliant code style

[X] Yes

Other information
No response

I've created an xeofs-devs team and invited @nicrie  and @slevang

I think you might have to add me as an admin on xeofs to actually transfer the repo

Thanks! I think you should have admin rights now @dcherian

I think I need more permissions unfortunately.

I'm not sure, but I think it might be enough that you have created the xeofs team (and possibly that's our only option). Once added, @nicrie should be able to transfer the repository here.

Ah ok. @nicrie can you try the transfer please?

I think it worked: https://github.com/xarray-contrib/xeofs :)


Issue ATS0 to remove spaces instead of programmatically removing them

The Subject says it all. I think this will speed up processing commands, and remove unnecessary code.

@Pho3niX90 care to open a PR addressing this issue? Glad to review it.

Sure stuff. Just need to review and test first, I have already added the spaces command to my project, still need to remove the redundant code.

Need this first: https://github.com/pires/obd-java-api/pull/68

Hi.
I can't continue with this one. My project has dramatically changed and submitting PR's from it will just be catastrophic. However this change is very simple and will see if I can get some time to do it. For now I am closing.

The thing with AT S0 is that I can guarantee it to work with all ELM devices or that all programmers will send said command. But I can guarantee I remove all spaces, if any.

That makes complete sense.


EncryptionEnvelope should fail if it can't get key info from metadata

I was passing the wrong metadata into the encryption client, which ultimately caused from_metadata to silently proceed instead of failing, and the error was more esoteric:
  File "/usr/local/lib/python3.4/site-packages/s3_encryption/client.py", line 40, in get_object
    context = handler.build_response_context(resp['Metadata'], context)
  File "/usr/local/lib/python3.4/site-packages/s3_encryption/handler.py", line 34, in build_response_context
    self.deconstruct_envelope()
  File "/usr/local/lib/python3.4/site-packages/s3_encryption/handler.py", line 44, in deconstruct_envelope
    self.envelope.key = crypto.aes_decrypt(key, self.envelope.key)
  File "/usr/local/lib/python3.4/site-packages/s3_encryption/crypto.py", line 57, in aes_decrypt
    return aes.decrypt(data)
  File "/usr/local/lib/python3.4/site-packages/s3_encryption/crypto.py", line 24, in decrypt
    return unpad_data(cipher.decrypt(data))
  File "/usr/local/lib/python3.4/site-packages/Crypto/Cipher/_mode_ecb.py", line 151, in decrypt
    expect_byte_string(ciphertext)
  File "/usr/local/lib/python3.4/site-packages/Crypto/Util/_raw_api.py", line 184, in expect_byte_string
    raise TypeError("Only byte strings can be passed to C code")

I believe that from_metadata in envelope.py should raise an error if the metadata entries are incomplete, rather than passing None in.
I could do an basic pull request but I want to know your thoughts first.

I think you're right, throwing an error on incomplete metadata would be a better experience overall.  I'm definitely open to taking a PR for the fix, thanks!

How are you starting the tests, Mike? python setup.py test says Ran 0 tests in 0.000s.

I just cut 0.1.2 which includes your fix for this issue.  I made a minor change, namely that when metadata is missing IncompleteMetadataError will be raised instead of a naked Exception.
Thanks a lot for helping out, I've added you to the (new) CONTRIBUTORS file!

Happy to help. If I get time I'll dig into your code, compare it to mine, and make changes. I know I handled some of the decryption differently.


get_rss_from_url fails at continue instruction

Full disclosure - I don't have a coding background and have been figuring this out as I've gone, so apologies if the answer/error is obvious and I've missed it! Just looking to be pointed in the right direction if possible.
When running the script it appears to run through multiple feeds, but never prints anything to Discord despite there being relevant articles to fetch.
I added some print statements to try and figure out where it was getting lost - note the print("true") check immediately before the continue:
def get_rss_from_url(rss_item, hook_channel_descriptor):
    news_feed = feedparser.parse(rss_item[0])
    date_activity = None

    print("looking at " f'{rss_item[0]}')

    for rss_object in news_feed.entries:
        try:
            date_activity = time.strftime('%Y-%m-%dT%H:%M:%S', rss_object.published_parsed)
        except:
            date_activity = time.strftime('%Y-%m-%dT%H:%M:%S', rss_object.updated_parsed)

        try:
            config_entry = config_file.get('main', rss_item[1])
        except NoOptionError: # automatically add newly discovered groups to config
            config_file.set('main', rss_item[1], " = ?")
            config_entry = config_file.get('main', rss_item[1])

        if config_entry.endswith('?'):
            config_file.set('main', rss_item[1], date_activity)
        else:
            if(config_entry >= date_activity):
                print("true")
                continue
            else:
                config_file.set('main', rss_item[1], date_activity)

        print("passed time check")

This is the terminal output - it spams "true" but then skips the "passed time check" print statement and seems to jump straight to processing the next feed:
PS G:\GithubDesktop\Repos\ThreatIntelligenceDiscordBot\Source> python .\test_DiscordIntelBot.py
looking at https://grahamcluley.com/feed/
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
true
looking at https://threatpost.com/feed/
true
true
true
true
true
true
true
true
true
true

I don't understand why it's spammed the "true" print and skipped over the other print statement and jumped straight to the end. I thought the continue instruction should just tell it to run the next instruction?

So this is actually the intended behavior of the bot. The function get_rss_from_url takes a single RSS feed (from a source like Bleeping Computer) and then processes all of the news articles from that feed. Hovewer, as the bot does this once every half an hour, it is necessary to implement a function to check if it has already sent the article, as the RSS feed doesn't update so often, which is what you se in action here.
Basically the bot writes the publish date of the latest article for each source that it scrapes to a central config file. Then, next time it's run, it goes through all the news articles in every feed, and only if the publish date is more recent than the one in the central config file, it will sent the article to discord and write the new latest publish date to the config file. If however it isn't more recent than the time in the config file,  it will simply skip the article using the "continue" statement, which is what you se when it spams true. Basically it's saying "this article has already been sent, skipping it"

Please update to latest instance.


Document Generation from typings.py

Typings.py is a generated file, but we maybe want to have sphinx make docs for this file.
from enum import Enum
from typing import Union

from armada_client.armada.event_pb2 import (
    JobSubmittedEvent,
    JobQueuedEvent,
    JobDuplicateFoundEvent,
    JobLeasedEvent,
    JobLeaseReturnedEvent,
    JobLeaseExpiredEvent,
    JobPendingEvent,
    JobRunningEvent,
    JobIngressInfoEvent,
    JobUnableToScheduleEvent,
    JobFailedEvent,
    JobSucceededEvent,
    JobUtilisationEvent,
    JobReprioritizingEvent,
    JobReprioritizedEvent,
    JobCancellingEvent,
    JobCancelledEvent,
    JobTerminatedEvent,
    JobUpdatedEvent
)

class EventType(Enum):
    """
    Enum for the event states.
    """

    submitted = "submitted"
    queued = "queued"
    duplicate_found = "duplicate_found"
    leased = "leased"
    lease_returned = "lease_returned"
    lease_expired = "lease_expired"
    pending = "pending"
    running = "running"
    unable_to_schedule = "unable_to_schedule"
    failed = "failed"
    succeeded = "succeeded"
    reprioritized = "reprioritized"
    cancelling = "cancelling"
    cancelled = "cancelled"
    terminated = "terminated"
    utilisation = "utilisation"
    ingress_info = "ingress_info"
    reprioritizing = "reprioritizing"
    updated = "updated"

# Union for the Job Event Types.
OneOfJobEvent = Union[
    JobSubmittedEvent,
    JobQueuedEvent,
    JobDuplicateFoundEvent,
    JobLeasedEvent,
    JobLeaseReturnedEvent,
    JobLeaseExpiredEvent,
    JobPendingEvent,
    JobRunningEvent,
    JobIngressInfoEvent,
    JobUnableToScheduleEvent,
    JobFailedEvent,
    JobSucceededEvent,
    JobUtilisationEvent,
    JobReprioritizingEvent,
    JobReprioritizedEvent,
    JobCancellingEvent,
    JobCancelledEvent,
    JobTerminatedEvent,
    JobUpdatedEvent
]

The problem is that EventType is an Enum, which doesn't current doc well, neither does Job Event Types. Maybe automatically generating docstrings is a better solution?

Discussed with Jay and Kevin, we think its best to leave this, as events.py already has the appropiate typing references to this file.


Hook repository up with ZENODO

You might want to hook up autotyp-data with ZENODO to get

long-term archiving of released versions of the data
a DOI to cite these released versions.

Major releases are now on Zenodo. Thanks for bringing this to our attention!


Known issues isn't linked

Precondition:
User has run with linked known issues.
Steps:

Start new run and wait result.
After ending open it and review failed test.

Expected results: known issues linked at failed test that has same stacktrace like in previous run
Actual results: known issues isn't linked

fixed


Fix TSLint warnings in msbot.ts

Related to #313
Proposed Changes
The following rules have been fixed:

typedef
no-require-imports
no-var-requires
no-any

To fix no-var-require, a dependecy for semver was added in package.json.
To fix no-any for const pkg, a new interface was added.
The variable a was renamed to unknownArgs.
Testing
Travis will no longer report this issue.

Pull Request Test Coverage Report for Build 662

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

Totals

Change from base Build 622:
0.0%

Covered Lines:
2836

Relevant Lines:
3526

💛  - Coveralls


WebMethod improvements

To help create better REST APIs with POJOs,

Define a series of HTTP method annotations like DELETE and GET that lets you write different methods to handle different verbs for the same URL.
Allow @WebMethod on any method, not just those starting with the do prefix

@reviewbybees though I'd like to hear from everyone, not just fellow bees.

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@kohsuke I tried to verify this PR in local, but there are conflicts. Do you plan to solve this?

Somewhere—but how do I find it?—I wrote up an argument that @WebMethod should become mandatory, so that we would drop the magical handling of do* methods. I had a proposal for how to make this binary compatible, I think using an annotation processor. Also that @RequirePOST would become an attribute of @WebMethod, or simply the default.

Ah! In #32.

Specifically I advocate that

you must place @WebMethod on any method you expect to be treated in this way—no more surprise exposure of security-sensitive code to the world

name should be mandatory: a simple Java rename refactoring should not affect behavior

you must select one or more HTTP verbs—no more forgetting to disallow GET on mutators

I think these changes would make for more explicit and safer code. They are not source-compatible but could be made binary-compatible with a little more effort.

I think Jesse is suggesting a change that goes much beyond the scope of this PR.
What this PR does is that it lets us approach that change better than what's stated in issue #32 (namely by having explicit HTTP verb annotations, POST need not be treated any differently from other verbs.)
I'll capture that in a separate ticket for a future consideration, though I don't think I want to make configuration explicit like that.

I think Jesse is suggesting a change that goes much beyond the scope of this PR.

To some extent, yes, but merging this takes the API in a direction from which it might be harder to recover than where we started.


Use faster random source on Linux

Currently Uuid.NewTimeBased() and Uuid.NewMySqlOptimized() use Guid.NewGuid() as a random source. As known, this is not the fastest way to get random data on Unix-like operating systems.
In .NET 6 Random.Shared.NextBytes(span) can be used as a random data source for Uuid. It may improve performance up to 10 times.
If there is doubt about the randomness of Random.Shared, a new method for generating a non-cryptographic random Uuid can be added. The seed of Random.Shared has a size of 256 bits, which should be enough to generate an unique identifier.
The Ulid library uses its own random implementation with a 64-bit seed for compatibility with older runtimes, but IMHO it's not a good idea to implement custom PRNG due to the subtle performance difference with Random.Shared.

The current implementation relies on the PAL layer, which sits beneath the implementation of methods responsible for generating System.Guid on various platforms. Additionally, it rewrites a portion of the bytes in such a way that the resulting value is optimally stored and utilized as a primary key, allowing modern databases to construct an index in the most efficient manner.

Due to this, the current implementation is slower than the equivalent one in System.Guid since it incurs overhead in shuffling a portion of the bytes. However, the main performance loss is attributed to the method that returns the current date.

Taking into account the factors mentioned above, it may not be advisable to allocate time towards actively optimizing the generation of the random component of the value.


PATCH Request cannot be empty in 2.4.0 but can be 2.3.0

I updated to 2.4.0 and it wasn't mentioned in the changelog that PATCH requests can no longer be empty. Is it possible to add this to the changelog or perhaps even allow it again?
#1581 Might be relative as PATCH might've been missed?

Yeah, our support for exotic methods has always been pretty lame. Wanna send a pull requst?

Sure, shouldn't take too long looking at #1581.

Seems to be already fixed in 2.5. Do you still want me to make a pull request for adding the test in? The test is basically just a copy and paste of the put and post request empty test.

Nope. All good.


Inconsistency in dates of Next Launch

The launch with the closest upcoming launch date does not always correspond to the data returned by the /launches/next endpoint.
For example, data returned by /launches/next: Starlink 2 (Oct, 1)
Launch with closest launch date: ANSIS II (Nov, 1)
This makes it harder to rely on the results returned by database queries on cached data from the API.
Also, as is evident from the launch date of Starlink 2, it is not correct to return it as the "next" launch if the launch date has been shifted to an unclear target. While it may well be the next planned launch, the API should at least provide a marker to indicate that a launch's status and launch date may be unclear.

With the way the API handles partial dates, I recommend ordering using flight_number, as it matches nicely with the "most likely" order on the subreddit wiki.
As far as displaying the date goes, I would look at the following fields:
tdb - set as true until a date has a day of the week
is_tentative - set as true until the date has a time
tentative_max_precision- shows the precision of the date. So for Starlink 2, the date is 2019-10-01T00:00:00.000Z, but the date is only precise to the month level, or 2019-10. Potential values are quarter, half, year, month, day, hour. Most people have pre-set date formats for these levels of precision, and display the date according the value of tentative_max_precision

Thank you for the help. Maybe we should consider adding a wiki page on this repository to explain the meaning important parameters such as these.

There's a small section in the top of the docs, but I'll edit it for a bit more clarity for similar issues 👍

Thanks! I apologize for not reading the docs thoroughly. I'm closing this issue now.

No worries 👍


Integrate subscriptions with TanStack Query

So this one is tricky. As I mentioned here websockets don't have first-class support in react-query. But with some boilerplate though (and some discipline on what goes on the websocket - you can't just send any json), one can make it work (the idea is to do useQuery   for the initial fetch, and then do subscriptions to receive updates - a sample code for this is here, sent by @PaulKujawa in this comment)
@tannerlinsley (the Tan from TanStack) thinks implementing websocket support on react-query itself isn't a great fit, exactly because you need to carefully choose the shape of the messages to fit a schema, and react-query is supposed to work with any kind of messages. From TanStack/query#171:
In this comment

After a lot of consideration and playing around with this concept, I don't believe it belongs in this library. I would be happy to help anyone build it for their own use cases, but it will not be making a first-class appearance in React Query for the time being.

And then in this other

I hear you that the subscription library world is super sparse and janky if you ask me. Let me elaborate on a few more things that might help this discussion be more targeted.

Apollo only "supports" subscriptions because they have a unified API on how subscriptions are interpreted (GraphQL) and the expectations behind them. Even so, Apollo (and just GraphQL) subscriptions for that matter still need an implementation layer that adheres to the spec, but actually powers the transactions. This is where there are GQL subscription plugins and layers made in sockets, http polling, grpc, etc. With that said, React Query doesn't force a spec upon you, and thus we cannot provide first class subscription plugins and implementors like Apollo does. This doesn't mean that it's not possible to use subscriptions (as a general concept) with React Query, but it does mean that you would have a different implementation for every combination of technology, eg. the Nozzle app uses sockets via Pusher and a custom hook that calls queryCache.invalidateQueries or queryCache.setQueryData from the events received. Once you change the socket implementation, the event shape/interface, or even what you ID your queries with, the entire custom hook changes.

He points out that a library that has some idea about the schema of the data is better suited to implement websocket support than react-query itself. So every rpc protocol on top of react-query will have a different way to handle subscriptions, but hopefully rspc might settle on a single, standardized way.
I'll probably prototype with this (out of tree) and if it's fruitful I can send a PR, but for now I'm not using react-query for subscriptions.

I would be interested to see your PR but I don't think this is going to work because I don't think you fully understand rspc subscriptions. A subscription is a way for the server to push data to the client, identified by a key, and where the data is arbitrary (hence rspc assumes no format or shape for it). Remember the arbitrary part, it's the important one.
For example say you have a subscription that sends a message like "update data to B". For this usecase we could tie the subscription to React Query so that when a message is received we would update the query cache and the user could access it normally via a useQuery hook. This works because our subscription only holds a single discrete "thing". The useQuery hook would hold the most recent value of the "thing" and every subscription message would hold a modified version of the same discrete "thing". This style of subscription works for the design your proposing.
Now say you have a subscription that sends a message like "show popup notification with message X". Each value that is read from the subscription is a discrete "thing" (unlike the previous example) and so storing it into a useQuery which is designed to hold a single discrete "thing" is problematic.
A useQuery is also designed to support caching and reuse of a discrete "thing" but in this case, a subscription message has no value for that.  This design would also make subscriptions super inflexible which when building a library is something you want to avoid where possible.
What the article TkDodo wrote is using a Websocket for the express purpose of updating the React Query Cache with new data like the first example. From what I understand he doesn't account for the second example (and nor should he or React Query for that matter).
In technical terms rspc would need a stream/generator-style API. It was discussed (TanStack/query#418) and it was decided against supporting in React Query. I fully agree with this move from them because it feels out of scope of React Query even if it would be nice. That discussion also shows using an infinite query to work around this but I struggle the grasp the benefit of that for 99.999% of use cases.
As far as I am concerned what you have described isn't the subscription system as much as it's a separate system on top of the subscription system which I have been refering to as the "invalidation system". Spacedrive has one of these built on top of rspc. The invalidate system could internally create a rspc subscription called something like rspc.invalidate (I am fairly sure I prevent anyone using rspc as a subrouter prefix) and using an internal format could communicate with @rspc/react/@rspc/solid to invalidate/update data.
Now if you reframe this conversion into building an invalidate system for rspc, it makes perfect sense to follow the architecture TkDodo wonderfully documented. However, dealing with invalidation on the Rust side brings another huge set of problems, namely, how does your Rust code tell the frontend to invalidate the query? Now you might think, well that seems easy, it's just a function call, right? Well, rspc is a library all about typesaftey and that is core to any feature it supports so you would need to come up with a typesafe API for invalidation in Rust and that just isn't possible because of rspc's use of string keys. There are some cool features on nightly that could make this work but they are a while off landing in stable and come with their own set of problems given rspc current design (although I would probably have forced it to work if they were stable).
To better explain my point in code:
ctx.invalidate("someQueryThatExists");
ctx.invalidate("thisQueryDoesn'tExistAndThisWillStillWork"); // This should be detectable and preventable in either a unit test or compiler error

ctx.invalidateWithData("someQueryThatExists", SomeQueryThatExistsArgs {});
ctx.invalidateWithData("someQueryThatExists", 42); // The data has the incorrect type based on query key. This should be detectable and preventable in either a unit test or compiler error

Spacedrive has an invalidate_query! macro which allows us to do invalidation in a way we can make typesafe through a unit test but this is not a good enough developer experience that I am willing to support it in rspc so, for now, your on your own to build an invalidation system using the subscription primitive. Our system is defined here and here but I would caution you don't copy it unless you can actually understand what it's doing because it makes many compromises and assumptions (some of the which are documented as part of spacedriveapp/spacedrive#493).
For the future, I am working on some prototypes of a new API in Rust that would allow for typesafe invalidation among other things but I am not certain of many aspects of its design (mainly its usage of macros for large transformations to your code). I am hoping to have a beta of it within the next 2 months but it's still got many unanswered questions and may turn out to not be possible.
On a personal note, I would be careful @'ing people for issues that they aren't personally required in because many people are busy and don't need more notifications (If you really need to be able to navigate to their profile just hyperlink their GH).

As far as I am concerned what you have described isn't the subscription system as much as it's a separate system on top of the subscription system which I have been refering to as the "invalidation system".

Indeed, I think this pretty much sums it. There's value in having a low-level subscription system (like the one that rspc currently have) and a high-level invalidation system (that can be built on top of the low level system).
Maybe the invalidation can even be on a separate npm package, like @rspc/react-invalidation.
And yeah you're right about the @s, sorry.

Spacedrive has an invalidate_query! macro which allows us to do invalidation in a way we can make typesafe through a unit test but this is not a good enough developer experience that I am willing to support it in rspc so, for now, your on your own to build an invalidation system using the subscription primitive. Our system is defined here and here but I would caution you don't copy it unless you can actually understand what it's doing because it makes many compromises and assumptions (some of the which are documented as part of https://github.com/spacedriveapp/spacedrive/pull/493).

That's pretty cool, thanks!


Bumped env version.

Bump the env version for #86.

@sfackler @alexcrichton can we push this to crates.io too?

Ah, sorry didn't see this: https://github.com/rust-lang-nursery/log/commit/41c570079c3b5afdf36008d883b7f18ad68a5fed
0.3.4's released.

Thanks!


A non well formed numeric value encountered

Hi,
I had an error with your plugin in one of your vendors (tubalmartin). I had to change lin 769 to 771 with following code:
case 'M': case 'm': return (int) substr($size, 0, strlen($size) -1) * 1048576;
case 'K': case 'k': return (int) substr($size, 0, strlen($size) -1) * 1024;
case 'G': case 'g': return (int) substr($size, 0, strlen($size) -1) *<PHONE_NUMBER>;

This happend because PHP 7.1 is strict with string & int convetions
Cheers!

Ah interesting, okay thanks, I'll see if they have perhaps updated it upstream.

When you get a chance, can you try out the version I just pushed to the develop branch? I updated all of the dependencies:
https://github.com/nystudio107/minify/tree/develop

Hey @khalwat
Got the same issue after upgrading PHP version and tried the dev branch but no joy. Also tried adding the 3 lines from thomas still getting the error. Did you get a fix for this? Cheers.

Okay guys, I checked in the change:
https://github.com/nystudio107/minify/tree/develop
I don't have a PHP 7.1 setup to test with, so let me know how this works out? If there are still errors, if you paste in the actual error with line number, etc., that'd be great!

https://github.com/mrclay/minify/issues/580

case 'M': case 'm': return intval($size) * 1048576; case 'K': case 'k': return intval($size) * 1024; case 'G': case 'g': return intval($size) *<PHONE_NUMBER>;
will be more suitable

Changes made @panrus
Can someone give this a whirl on a PHP 7.1 setup?
https://github.com/nystudio107/minify/tree/develop

Fixed in https://github.com/nystudio107/minify/releases/tag/1.1.2


cargo-tauri: 1.3.0 -> 1.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tauri-apps/tauri/releases.
meta.description for cargo-tauri is: Build smaller, faster, and more secure desktop applications with a web frontend
meta.homepage for cargo-tauri is: https://tauri.app/
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.1 with grep in /nix/store/wpr6avjky3am9f5k669figqs06bmfqnl-tauri-1.5.1
found 1.5.1 in filename of file in /nix/store/wpr6avjky3am9f5k669figqs06bmfqnl-tauri-1.5.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
cargo-tauri
pot

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/5d5cc30bf3871706c2163cfbf8d56afe2d7af8cb#cargo-tauri

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

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

2 packages built:

cargo-tauri
pot

Maintainer pings
cc @dit7ya for testing.

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

2 packages failed to build:

cargo-tauri
pot


Does chilipie-kiosk support GPIO.

I have a raspbian running chrome in full screen calendar that i hooked a few buttons on to and the python to utlize GPIO to send characters to chromium to control the calendar. Switch views. move forward a month, move back a month. etc.. Can I move this to chilipie-kiosk and make it a little cleaner

As of https://github.com/futurice/chilipie-kiosk/releases/tag/v2.0.0, all the usual GPIO is supported.


Jenkins plugin V3.0.0 connects to mavencentral?

Hi
Im having this error when running the new version 3.0.0
[DependencyCheck] One or more exceptions were thrown while executing Dependency-Check
[DependencyCheck] Exception Caught: org.owasp.dependencycheck.analyzer.exception.AnalysisException
[DependencyCheck] Cause: Finally failed connecting to Central search. Giving up after 5 tries.
[DependencyCheck] Message: Could not connect to Central search. Analysis failed.
[DependencyCheck] org.owasp.dependencycheck.analyzer.exception.AnalysisException: Could not connect to Central search. Analysis failed.
[DependencyCheck] Caused by: java.io.IOException: Could not connect to MavenCentral (403): Forbidden
I am behind a proxy, so this error makes sense, but the previous dependency check versions were not connecting to mavencentral
Why is it connecting there now?
Thanks

Actually, the connection was always attempted - in previous versions it silently failed (even when no proxy was involved if Central returned a 500). 3.0.0 corrected this behavior - so if you do not wish to include the central analyzer you need to disable it; if you do want to use it (which I would highly recommend as it improves accuracy) you need to configure a proxy - alternatively, if you had Nexus Pro you could use that instead of Central. We are planning on including an Artifactory analyzer in the future as well.

Makes sense... If i am using a local nexus repository, could i reference to it, or it needs to be the official nexus?
Regarding maven central, is it connecting to https://search.maven.org/?
Thanks

@jeremylong Do you have any alternative when running nexus pro v.3.x - the nexus alternative only works for v2.x

@davidkarlsen Unfortunately I don't have a Nexus Pro instance to test against. The Nexus analyzer was contributed. PRs are welcome...
@javixeneize apparently, if you have a local Nexus Pro v2.x you can configure the url and enable the NexusAnalyzer; at the same time you should likely disable the central analyzer.

Hi
Which is the expected url for nexus analyser?
Imagine i have
https://nexus.mylocal.com/repository/maven-releases/com/whatever/project/....
What is the url the analyser expects? Its continuously giving me errors
Thanks

Hi
What is the exact nexus url i should configure in jenkins?
Thanks

Checking the documentation - it looks like you need to configure the url to point to the Nexus Server's REST API Endpoint "http://domain/nexus/service/local".

@jeremylong I am using automated process to create and configure jenkins server. I am installing this plugin using scripts, I am facing same issue, how can i configure or disable maaven central analyzer option to false, I am using groovy.

@ashishnm I am going to push a new release this week (today/tomorrow).  Without actually seeing your scripts I wouldn't have a clue how to assist you.

Hi
I think the main problem here is that  it needs to pro version of nexus and
it doesnt work with the standard version
Thanks
On Mon, Nov 13, 2017 at 11:50 AM, Jeremy Long<EMAIL_ADDRESS>wrote:

@ashishnm https://github.com/ashishnm I am going to push a new release
this week (today/tomorrow). Without actually seeing your scripts I wouldn't
have a clue how to assist you.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/932#issuecomment-343896431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55pcmj_B5RVXlTuR5AJZ6qZvyrN6rks5s2C0GgaJpZM4P74Hu
.

@jeremylong when you are going to publish version 3.0.2 in jenkins repo? I have updated to 3.0.1.
My pipeline code is like
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports: false, includeHtmlReports: false, includeJsonReports: false, includeVulnReports: false, isAutoupdateDisabled: false, outdir: '', scanpath: 'facebook-connector/target/facebook-connector-1.0.1.jar', skipOnScmChange: false, skipOnUpstreamChange: false, suppressionFile: '', zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '0', pattern: '', unHealthy: '1000'
also I am trying to scan python files and getting with 0 unique warnings and 0 duplicates. Does this plugin scanning for python working fine. It is also pipeline syntax.
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports: false, includeHtmlReports: false, includeJsonReports: false, includeVulnReports: false, isAutoupdateDisabled: false, outdir: '', scanpath: 'bottle/src/bottle/**/*.py', skipOnScmChange: false, skipOnUpstreamChange: false, suppressionFile: '', zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, defaultEncoding: '', healthy: '0', pattern: '', unHealthy: '1000'

3.0.2 should already be released for Jenkins.
Jeremy
On Nov 16, 2017 2:29 PM, "Ashish Mishra"<EMAIL_ADDRESS>wrote:

@jeremylong https://github.com/jeremylong when you are going to publish
version 3.0.2 in jenkins repo? I have updated to 3.0.1.
My pipeline code is like
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports:
false, includeHtmlReports: false, includeJsonReports: false,
includeVulnReports: false, isAutoupdateDisabled: false, outdir: '',
scanpath: 'facebook-connector/target/facebook-connector-1.0.1.jar',
skipOnScmChange: false, skipOnUpstreamChange: false, suppressionFile: '',
zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, canRunOnFailed: true,
defaultEncoding: '', healthy: '0', pattern: '', unHealthy: '1000'
also I am trying to scan python files and getting with 0 unique warnings
and 0 duplicates. Does this plugin scanning for python working fine. It is
also pipeline syntax.
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports:
false, includeHtmlReports: false, includeJsonReports: false,
includeVulnReports: false, isAutoupdateDisabled: false, outdir: '',
scanpath: 'bottle/src/bottle/**/*.py', skipOnScmChange: false,
skipOnUpstreamChange: false, suppressionFile: '', zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, defaultEncoding: '',
healthy: '0', pattern: '', unHealthy: '1000'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/932#issuecomment-345036526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0qwhTEEUeXMAcX9ZN4RHZgSrZzGUPCks5s3I0zgaJpZM4P74Hu
.

Yes, it is released. I’m already using it
There is another bug. When you analyze a models package it gives an error
in the ruby analyser (...?)
Disabling ruby analyser it works fine
El El jue, 16 nov 2017 a las 19:38, Jeremy Long<EMAIL_ADDRESS>escribió:

3.0.2 should already be released for Jenkins.
Jeremy
On Nov 16, 2017 2:29 PM, "Ashish Mishra"<EMAIL_ADDRESS>wrote:

@jeremylong https://github.com/jeremylong when you are going to
publish
version 3.0.2 in jenkins repo? I have updated to 3.0.1.
My pipeline code is like
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports:
false, includeHtmlReports: false, includeJsonReports: false,
includeVulnReports: false, isAutoupdateDisabled: false, outdir: '',
scanpath: 'facebook-connector/target/facebook-connector-1.0.1.jar',
skipOnScmChange: false, skipOnUpstreamChange: false, suppressionFile: '',
zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, canRunOnFailed: true,
defaultEncoding: '', healthy: '0', pattern: '', unHealthy: '1000'
also I am trying to scan python files and getting with 0 unique warnings
and 0 duplicates. Does this plugin scanning for python working fine. It
is
also pipeline syntax.
dependencyCheckAnalyzer datadir: '', hintsFile: '', includeCsvReports:
false, includeHtmlReports: false, includeJsonReports: false,
includeVulnReports: false, isAutoupdateDisabled: false, outdir: '',
scanpath: 'bottle/src/bottle/**/*.py', skipOnScmChange: false,
skipOnUpstreamChange: false, suppressionFile: '', zipExtensions: ''
dependencyCheckPublisher canComputeNew: false, defaultEncoding: '',
healthy: '0', pattern: '', unHealthy: '1000'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/jeremylong/DependencyCheck/issues/932#issuecomment-345036526
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AA0qwhTEEUeXMAcX9ZN4RHZgSrZzGUPCks5s3I0zgaJpZM4P74Hu
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/932#issuecomment-345038620,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55lpyqTFRoXVEa_JM_iQH2UpLqXwPks5s3I8ogaJpZM4P74Hu
.


Using meltano outside a meltano project should have a pretty error.

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/240
Originally created by @mbergeron on 2018-12-20 20:02:08

The current error is pretty bad: Cannot go any further.
Let's improve it for better UX.

View 3 previous comments from the original issue on GitLab


Speed up algorithm

Firstly, we sort left and right parts, so we can do less operations, because on leftPair < rightPair we can skip this element. The second thing for speed up was using rightIndex, because after sorting we can skip first part of right before rightIndex

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          36     41    +5
=====================================
+ Hits           36     41    +5

Impacted Files
Coverage Δ

index.js
100% <100%> (ø)
: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 c04810e...6d0a3f0. Read the comment docs.

This looks very solid! Did you run benchmark tests to make sure it increases the speed?

Yes, I did
Will send them in comments later

So, I did benchmark tests in vacuum and they are slower than previous solution. Also, in my project we "preprocess" data, so this works faster than existed. I will close PR for now and if "optimized" solution in vacuum will be faster, I will open it again. Anyway, I will continue to work with it

Oh how interesting! Maybe this starts being useful on bigger input values? 🤔


Add in Feature

Add a play mode where map generates a random place within his chosen milage and run with in a mission amount of time. Time required to run toward that point is random but dependent on length of his running route. Also if he did not reach the destination the app will call out and tell him to run faster next time.

Addin Feature Complete.


metrics: fix prefix kubevirt_vm -> kubevirt_vmi

What this PR does / why we need it:
Fix the prefix of the kubevirt metrics to reflect that they are about virtual machine instances
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #Resolves: https://github.com/kubevirt/kubevirt/issues/2504
Special notes for your reviewer:
See discussion on https://github.com/kubevirt/kubevirt/pull/2501
Release note:
VMI-related metrics have been renamed from `kubevirt_vm_` to `kubevirt_vmi_` to better reflect their purpose.

/hold

/retest

/retest

/retest

/cc @rmohr - I think this patch is ready for review.

on hold because we are warning the users about this change, and we want to give time to them to speak out.

/test pull-kubevirt-e2e-k8s-1.11.0

/hold cancel

noone complained about this change in ~10 days

/retest

/test pull-kubevirt-e2e-k8s-1.11.0

/retest

/lgtm
/approve


Drag and Drop Model Quiz Exercise "Generate Quiz Exercise" button not working

Describe the bug
When using the drag-and-drop model quiz, the 'generate quiz exercise' button doesn't appear to function. I expect it to create a quiz exercise and redirect to the course management exercises page. The documentation lacks clear instructions on this.
To Reproduce

Go to Course Management of an Artemis course
Click on Exercises
Scroll down to Quiz Exercises
Click on Create Drag and Drop Model Quiz
Click on Create a new Apollon Diagram
Fill title and select any Diagram Type
Drag-drop some modeling
Click on Generate a Quiz Exercise
No actions happen

Expected behavior
The expectation would be the generation of an drag and drop model quiz exercise
Screenshots

Which version of Artemis are you seeing the problem on?
6.5.0
What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No errors appear on the console

I was just investigating for this issue #7020 when I also realized the problem with the "Generate Quiz Exercise" button. But as far as I could see the button is just not working as long as no interactive parts are inserted/selected in the model (what in general makes sense for a dnd quiz).
But we should disable the button as long no interactive parts are there and display some kind of validation error.


Nuke: fixing node name based on switched asset name

also improving code

Testing

go to settings to your project overides project_settings/nuke/load/LoadClip/node_name_template and add following value "Read_{asset}{subset}{class_name}_{ext}", and save.
load a subset X into nuke test scene
open Manager and right button click at the loaded subset and go to Switch asset.
find another subset Y and hit confirm.
loader should change to other subset Y and also the name of node should change.

Task linked: OP-1012 Nuke manager change read node name


Jekyll can create foldable content from markdown

That is, we want to be able to trigger this feature:
https://docs-staging.secretless.io/Latest/en/Content/Get Started/quick_start.htm
from within our markdown documentation files.

Did some digging and found the following:

Navgoco is a simple JQuery plugin for Jekyll to get the accordion-like look
how to blog to creating a custom accordion template: http://mikelui.io/2018/07/22/jekyll-nested-blocks.html
after slack discussions, Geri brought up a really great point that we may have code that we can repurpose. I created an accordion-like side navbar before we moved the docs off secretless. Will look through the previous site versions to bring this back


Use ExactArgs for unbatched-send-to-ethereum cli command

Fixes the bug mentioned in the Sommelier repo issue here: https://github.com/PeggyJV/sommelier/issues/112

Codecov Report

Merging #466 (56a8d49) into main (7582359) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #466   +/-   ##
=======================================
  Coverage   28.67%   28.67%
=======================================
  Files          47       47
  Lines        6553     6553
=======================================
  Hits         1879     1879
  Misses       4527     4527
  Partials      147      147

Impacted Files
Coverage Δ

module/x/gravity/client/cli/query.go
0.00% <0.00%> (ø)


To 0.2.1

Hi @jertel, I believe this version may work with both ES7 and ES6! We can merge it firs to the es7 branch.

Sorry, please do not merge yet, there seems to be an error
Traceback (most recent call last):
  File "/usr/local/bin/elastalert", line 6, in <module>
    from elastalert.elastalert import main
  File "/usr/local/lib/python2.7/site-packages/elastalert/elastalert.py", line 28, in <module>
    from . import kibana
  File "/usr/local/lib/python2.7/site-packages/elastalert/kibana.py", line 4, in <module>
    import urllib.error
ImportError: No module named error

Hey thanks for merging

You're welcome. Thanks for following up with this. I've confirmed that the new version works with ES 6.8.2. If you can confirm it works with ES 7.3.x I'll merge to master and remove this branch. Let me know.


UART RTS / CTS HW Flow Control

It would be great if the UART ports supported HW flow control.  I would like to run the UARTs at much higher baud rates and transfer large amounts of data. This will require flow control.
BTW: Nice work on this project!  I had it up and running on a Digilent Nexys A7 board quickly without issues.

Interesting idea!
Obviously, the hardware flow control signals could be implemented using the GPIO ports and some software overhead. But this overhead might compromise some of the "very high" data throughput.
So having dedicated control signals seems to be a nice solution. I have checked the RTS / CTS specifications and if I got them right
neorv32.uart.RTS_o (output) would indicate the UART's receiver being ready to receive another byte while neorv32.uart.CTS_i (input) would indicate the UART's transmitter is allowed to transmit another byte, correct?
Right now I am not sure about the polarity of these signals, but this isn't really a big deal.

Yes, that is the way I believe it works: CTS is an input and RTS is an output. I think they are high active signals (at least to the TTL level).
Thanks for considering this enhancement.

I have added (experimental) RTS/CTS hardware flow control with the last repository update. Since I have no full-scale UART-USB adapter available right now, I could only simulate the flow control so far - but it looks pretty good.
Maybe you can give some feedback if you plan to test the new features. :wink:
By the way, RTS and CTS seem to be low-active (they are low-active in the current NEORV32 version).

I'll try it out this weekend and give you any feedback.

It worked great for me on my Nexys A7 board -- RTS/CTS worked as expected.
I'm now running the UART at 460,800 baud, in the bootloader and app code, with no issues.

I'm glad to hear that! 👍


App stops after a few seconds (PoseTrackingGPU +Android) w/o any FATAL log/crash

OS Platform and Distribution : Windows 10 Home 64 Bit, Mobile - Samsung Galaxy S9+ , Android OS Version: 10.
Bazel version: 3.7.2
Solution Pose Tracking GPU
Programming Language and version : Java (Android)
I have made a custom pose_tracking pbtxt file which is almost the same as pose_tracking_gpu.pbtxt file in (mediapipe/graphs/pose_tracking) , but with a few changes according to my need.
Custom_Pose_Tracking_GPU.pbtxt file:
MediaPipe graph that performs pose tracking with TensorFlow Lite on GPU.
CPU buffer. (CpuBuffer)
input_stream: "input_video"
Pose landmarks.  It passes through
the very first incoming image unaltered, and waits for downstream nodes
(calculators and subgraphs) in the graph to finish their tasks before it
passes through another image. All images that come in while waiting are
dropped, limiting the number of in-flight images in most part of the graph to
This prevents the downstream nodes from queuing up incoming images and data
excessively, which leads to increased latency and memory usage, unwanted in
real-time mobile applications. It also eliminates unnecessarily computation,
e.g., the output produced by a node may get dropped downstream if the
subsequent nodes are still busy processing previous inputs._
node: {
calculator: "ImageFrameToGpuBufferCalculator"
input_stream: "input_video"
output_stream: "input_video_gpu"
}
node {
calculator: "FlowLimiterCalculator"
input_stream: "input_video_gpu"
input_stream: "FINISHED:pose_landmarks"
input_stream_info: {
tag_index: "FINISHED"
back_edge: true
}
output_stream: "throttled_input_video"
}
Subgraph that detects poses and corresponding landmarks.
node {
calculator: "PoseLandmarkGpu"
input_stream: "IMAGE:throttled_input_video"
output_stream: "LANDMARKS:pose_landmarks"
output_stream: "DETECTION:pose_detection"
output_stream: "ROI_FROM_LANDMARKS:roi_from_landmarks"
}
The android code looks like this:
private static final String OUTPUT_STREAM_NAME = "pose_landmarks";
private static final String INPUT_VIDEO_STREAM_NAME = "input_video";
void loadModel() {  // runs at the start, initialization method
graph = new Graph();

        if (new File(BINARY_GRAPH_NAME).isAbsolute()) {
            graph.loadBinaryGraph(BINARY_GRAPH_NAME);
        } else {
            graph.loadBinaryGraph(
                    AndroidAssetUtil.getAssetBytes(context.getAssets(), BINARY_GRAPH_NAME));
        }

graph.addPacketCallback(OUTPUT_STREAM_NAME, packet -> //whatever the code is ) ;

graph.setParentGlContext(eglManager.getNativeContext());
        packetCreator = new AndroidPacketCreator(graph);

        graph.startRunningGraph();
} //endOfLoadModelMethod

Hi @sohail-jogo, Could you please provide the error logs to investigate your issue for further level. Thanks!

Sorry for the bother. I debugged the problem, and saw that I having memory leaks. Turned out that I was not releasing the packets. Therefore, packet.release()  solved the problem!


esp_config.h - Missing?

There is a header file named "esp_config.h" that's referred to by other files here but it isn't present anywhere in the folder hierarchy, did I do something wrong or is this an oversight?
Thanks

You have to create this file. Please have a look here: https://majerle.eu/documentation/esp_at/html/page_appnote.html#sect_config


Send box in speech listening mode don't auto scroll to far right

Repro steps:

Resize Web Chat window to be as narrow as possible without clipping
Click on microphone button
Say a very long sentence, like, "A quick brown fox jumped over the lazy dogs"

Expected: when the intermediate result is shown, Web Chat should keep the latest words on the screen by scrolling right
Actual: we only show the first few words, clipped everything else
Investigations:

We move caret with selectionStart = selectionEnd = value.length

This only works when the send box is focused
UX-wise, we stop listening when the send box is focused

When speech start, turn  into a single-line

Change the parent to be scrollable, and auto-scroll to far right

I think a better solution is provide multi-line support.

Related to #124


fix to properly identify CTEs in union select queries

This addresses #70
I have limited understanding of the parsetree, but the existing implementation only searches for CTEs when the statement ['op'] is 0 (couldn't find any documentation about this, would be interested to learn more.) The apparent effective fix was to have it run inside of the SELECT_STMT block regardless of statement op.
query = PgQuery.parse(<<-SQL)
WITH foo (SELECT * FROM bar)
SELECT * FROM baz
UNION
SELECT * FROM foo

Formerly:
query.tables
> ['foo', 'baz']
query.cte_names
> []

post fix:
query.tables
> ['bar', 'baz']
query.cte_names
> ['foo']

@seanmdick Nice, good work - merged!

awesome, thanks for doing all of the other hard work.

@seanmdick Sure thing, you're welcome.
Out of curiosity, what are you using pg_query for?

We're doing some topological sorting of sql references for arcane purposes I have been sworn to secrecy about.

@seanmdick Hah, good luck & thanks for contributing :)


Compile and run core tests on Linux

This is currently being tests. I need to update my version of Boost on Ubuntu to proceed.

Updated Boost but that wasn't the main issue. I need to add the libraries to GNUmakefile. Currently works on Windows with pragma.

As of d96e1360e11e7dd048319506b924f49964dcab99 the tests compile and run. But there are some test helpers that need to be build so some tests fail.

This has been fixed for a long time.


Update transition script to allow docker/podman usage

#4423 is required to merge before this does, hence draft.  Resolves #4386
This PR updates the transition script to...

[x] No longer use temp directory because breadcrumbs are available now.
[x] Allows the transition script to use docker or podman for their transition script run.

TODO:

[x] Update transition script readme

/check-enforcer evaluate

/check-enforcer evaluate

/check-enforcer override


grammatical fixes

fixed orphaned parenthesis and removed unneeded comma

I removed the "into one" statement as I found it quite confusing when I first read through it. I think it could be kept, but if it is, I would at least remove the comma that was right before it. It may also help to clarify the vague term "one" by saying "into an array pointer" or something similar. Thanks for reviewing this request. Ziglings is a blast!

@davidskeck Ha ha, thank you for this. I'm sure "into one" made sense to me at the time, but it's terrible. :laughing:


'shared' bind-propagation not working with unionfs-fuse

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description

Trying to use bind-propagation shared with unionfs-fuse inside podman container does not work. The mount point is correctly shown inside container but not in host. Docker works. I'm not sure it is related to #1834
Steps to reproduce the issue:

create dir layout for unionfs-mount

mkdir -p /tmp/multienv/dir1 && echo "dir1_var1" > /tmp/multienv/dir1/var
mkdir -p /tmp/multienv/dir2 && echo "dir2_var1" > /tmp/multienv/dir2/var
mkdir -p /tmp/multienv/unionfs
cd /tmp/multienv/

Test with podman

## mount 'dir2' over 'dir1' in '/tmp/multienv/unionfs' using a container
podman run --name multienv_unionfs --privileged=true --rm=true --env TZ=America/Costa_Rica --env PGID=1000 --env PUID=1000 --env UNION_DIRS=/dir2=RW:/dir1=RO --env MOUNT_PATH=/unionfs/ --env COW=true --volume /tmp/multienv/dir2:/dir2 --volume /tmp/multienv/dir1:/dir1 --volume /tmp/multienv/unionfs:/unionfs:shared --detach=true jobcespedes/multienv

## container's unionfs mount dir content
podman exec -it multienv_unionfs ls -al unionfs

## host's unionfs mount dir content
ls -al unionfs

## stop and remove container
podman stop multienv_unionfs

Test with docker

## mount 'dir2' over 'dir1' in '/tmp/multienv/unionfs' using a container
docker run --name multienv_unionfs --privileged=true --rm=true --env TZ=America/Costa_Rica --env PGID=1000 --env PUID=1000 --env UNION_DIRS=/dir2=RW:/dir1=RO --env MOUNT_PATH=/unionfs/ --env COW=true --volume /tmp/multienv/dir2:/dir2 --volume /tmp/multienv/dir1:/dir1 --volume /tmp/multienv/unionfs:/unionfs:shared --detach=true jobcespedes/multienv

## container's unionfs mount dir content
docker exec -it multienv_unionfs ls -al unionfs

## host's unionfs mount dir content
ls -al unionfs

## stop and remove container
docker stop multienv_unionfs

Describe the results you received:

With podman, host unionfs dir:

# ls -al unionfs
total 0
drwxrwxr-x. 2 job  40 feb 25 10:29 .
drwxrwxr-x. 5 job 100 feb 25 10:29 ..

With docker, host unionfs dir:

# ls -al unionfs/
total 4
drwxrwxr-x. 1 job  60 feb 25 10:28 .
drwxrwxr-x. 5 job 100 feb 25 10:29 ..
-rw-rw-r--. 1 job  10 feb 25 10:28 var

Describe the results you expected:
Same as Docker: files available in host
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.8.0
RemoteAPI Version:  1
Go Version:         go1.13.6
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.6
  podman version: 1.8.0
host:
  BuildahVersion: 1.13.1
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.10-2.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.10, commit: 6b526d9888abb86b9e7de7dfdeec0da98ad32ee0'
  Distribution:
    distribution: fedora
    version: "31"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree: 352104448
  MemTotal:<PHONE_NUMBER>6
  OCIRuntime:
    name: runc
    package: runc-1.0.0-102.dev.gitdc9208a.fc31.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: 96f6022b37cbe12b26c9ad33a24677bec72a9cc3
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: vm-01
  kernel: 5.4.19-200.fc31.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.3+dev
      commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
  uptime: 141h 29m 58.75s (Approximately 5.88 days)
registries:
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /var/home/job/.config/containers/storage.conf
  ContainerStore:
    number: 2
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.5-2.fc31.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7.5
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /var/home/job/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 9
  RunRoot: /run/user/1000/containers
  VolumePath: /var/home/job/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.8.0-2.fc31.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora Silverblue 31 VM

@rhatdan I think you're the most familiar with mount propagation - mind taking a look?

this is not a bug.  Rootless containers cannot create mounts in the host.
The shared mount is created inside of the rootless mount namespace, you can reach it with podman unshare

@jobcespedes It sounds like we expect this to work as root, but not without.

Thanks for the clarification @giuseppe and @mheon . I was not aware of it.
Two things:

I recently tried running it as root and mount point, files don't show up in host.
podman unshare ls -al /tmp/multienv/unionfs and podman unshare mount  show nothing for '/tmp/multienv/unionfs'

Am I getting it wrong?

If the procedure here fails as root, I'd consider that a bug. Reopening.

@mheon I just find out it works with root outside /tmp. I don't know why it doesn't work in /tmp. For example mounting somewhere inside $HOME instead:
# As root
parent=$HOME
mkdir -p $parent/multienv/dir1 && echo "dir1_var1" > $parent/multienv/dir1/var
mkdir -p $parent/multienv/dir2 && echo "dir2_var1" > $parent/multienv/dir2/var
mkdir -p $parent/multienv/unionfs
cd $parent/multienv/

## mount 'dir2' over 'dir1' in '/tmp/multienv/unionfs' using a container
podman run --name multienv_unionfs --privileged=true --rm=true --env TZ=America/Costa_Rica --env PGID=1000 --env PUID=1000 --env UNION_DIRS=/dir2=RW:/dir1=RO --env MOUNT_PATH=/unionfs/ --env COW=true --volume $parent/multienv/dir2:/dir2 --volume $parent/multienv/dir1:/dir1 --volume $parent/multienv/unionfs:/unionfs:shared --detach=true jobcespedes/multienv

you need to make sure $parent/multienv/unionfs is already a mount on the host.
You can do something like:
# mount --bind --make-shared $parent/multienv/unionfs $parent/multienv/unionfs

for rootless you need to run that command from the podman unshare environment

I see it now with podman unshare. Thank you.
I might need to change my approach. I wanted to symplify having a union directory.  But my current approach of having the unionfs binary and mounting the directory in a  rootless container seems kind of cumbersome related to that initial goal. I though it was just a matter of exposing the union directory to the host.
This is not podman related anymore. But if anyone thinks there is a better approach for simplifying things and don't mind sharing, it’ll be much appreciate it.

I wonder if adding rshared to the options for the volume mount would help

I wonder if adding rshared to the options for the volume mount would help

for rootless no.  Mounts created in a rootless mount namespace will never be propagated to the host.
As unprivileged user you could use directly FUSE on the host to mount the unionfs but you'll have some limitations (no containers, no multiple IDs available...)

Mounts created in a rootless mount namespace will never be propagated to the host

this is great for me actually, since the original intention is not to create one but to expose files from the union directory.
If just files from a directory could be shown in the host without a mount being propagated...
I was thinking live syncing files between the union directory and another second directory, inside the container. Being that second directory, the volume shared with the host. However, it gets me far from my original goal of simplicity.
So, it's probably going to be FUSE in the host as suggested (no containers).
Thank you guys

@jobcespedes It would be good if you could write up a blog talking about what you found out.  Then we could link it from podman.io.

Here is a Draft for the Blog idea. Planning on posting on Dev.to
Let me know what you think.

Looks great, thanks.

Here it is. The final version.


Adding a systematic logging mechanism

One popular option is slf4j, but I am open to other options.

I did a bit of research for alternatives, but I think slf4j still should be fine with logback as its implementation. I will work on this.


Default status code from Err should be 500

When returning from an actix-web endpoint an Err(T) where T: impl ResponseError, the expected default error should be, in my opinion, 500 InternalServerError.
This should be a relatively simple fix by changing this line: https://github.com/enzious/actix-web-thiserror/blob/47ba43d42f87a4deba8d24b57361f6680ba9ca70/actix-web-thiserror-derive/src/response_error.rs#LL197C46-L197C46

I'll look into the changing the default, maybe providing a global config.

Addressed in #4


error in sideband demultiplexer

Hi,
I got this error while deploying an app via git via Azure Websites:

fatal: The remote end hung up unexpectedly
error: error in sideband demultiplexer
To https://...@xxx.scm.azurewebsites.net:443/yyy.git
   d373646..39e03e1  develop -> master

A few minutes later the same command just worked. Seems to be a git issue (discussion on SO), and it's possible to work around by adding another commit and just retry.
Cheers, Philip

We deploy about 30 times a day and see this about twice a day. We've been through the linked stackoverflow question, but we still see the issue. Is this there anything that the azure team can do?

Can you give more details about your scenario? Are you git pushing directly to the site, or do you have continuous deployment set up? I would assume the latter given your deployment frequency, but just making sure.

We are deploying via teamcity, which we use for our testing. We then do a simple git push like so:
git.exe push https://username:password@oursite-staging.scm.azurewebsites.net:443/oursite.git HEAD:master --tags -f

Can you share the site name, either directly or indirectly/

One of the sites is pbdev-software.azurewebsites.net and we see this when pushing to the staging slot. We have seen the same issue on a number of the sites in our subscription.

It could be that the client gets disconnected from the server because of a lack of activity. But that does not imply that the server side is failing. In those cases, what does it look like if you look at the deployment list in the portal? Does it claim that the deployment failed or was successful? You can also look at the full log from there.
From a quick look at some logs, it does seem like some operations are taking a very long time, e.g. I see:
<entry time="2015-03-19T11:53:19.2586088Z">
  <message>Setting AssemblyInformationalVersion</message>
</entry>
<entry time="2015-03-19T11:54:42.744982Z">
  <message>v1.1.2737-dev</message>
</entry>

Which seems to imply that the Setting AssemblyInformationalVersion step is taking 83 seconds. Not saying this is necessarily a problem (if it does expensive things), but looking through the deployment logs can give insight as to what's going on.

Ok, that's odd, all that happens between Setting AssemblyInformationalVersion and the message v1.1.2737-dev is this:
call D:\Python34\python.exe "%DEPLOYMENT_SOURCE%\tagrelease.py"

and in the python script:
__author__ = 'mark'

import subprocess
import re
import fileinput
import os
import string

os.chdir(os.path.dirname(os.path.realpath(__file__)))

output = subprocess.check_output(['git', 'describe', '--tags']).decode('utf-8')
print(output)

Where print(output) produces the value v1.1.2737-dev. It's possible that the remote branch has a large number of tags, but even so, I wouldn't expect it to take 80 seconds.
I'll try to make sure that we clear down the number of pushed tags and see if that helps.

One thing you may want to try to isolate from deployment is to go into Kudu Console and run various actions individually (like the python one above). This way we can test in isolation whether they take longer than expected.

Seeing this today as well while deploying a project as well.
Do we know if this is an internal Azure problem?
Just ran into it twice in a row, one time the git push got further than the previous attempt.
Can't get the whole process to just finish.

Did the deployment end up failing on the server if you look at the history? In some cases, it just means the git client got disconnected from the output stream, with no ill effect on the deployment.

Can't find any logs of it anywhere in Azure, there any specific place you know I should be looking? @davidebbo Thanks for the quick response! 💯 💯

Look under Deployment Options for your web app, and you should see the deployment log. Click item for details.

So (good news at least) it finally finished the git push process and everything got uploaded!
Interestingly enough, when looking there, the previous attempts didn't get logged at all. Very strange. Seems like I'll never know what the issue was now :( haha

It it's the same commit ID, it would replace the old entries. If you hit this again, try looking in portal to see what state things are in.

Hi
Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained.
If the problem persists and is related to running on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


"Il2CppInterop.Common.dll" and "Il2CppInterop.Runtime.dll" missing

Thanks to support in #ml-support in Discord server I have noticed that the DLL's mentioned in the title are missing from the suggested location ([Game Directory]\MelonLoader\Il2CppAssemblies\) in the Wiki, rather they are situated in [Game Directory]\MelonLoader\net6
I'm not sure if this modification is worth an issue opened but I thought I might mention this for users that were confused and couldn't find the DLL's.

Ig it would be a good idea to specify the locations of the assemblies


Design feedback on new static website

Change the logo

removing the Qiskit logo from the front of the word mark, and changing some colors. So it is just “Qiskit Ecosystem”

Color scheme

then the buttons and links should be [Carbon] blue 60.

I would also suggest some color updates to the tagging scheme, but I am happy to mock this up over the next week

Putting this on hold until we get the rest of the feedback

Maybe you can also add the url : https://qiskit.github.io/ecosystem to the site repo Aboutsection :)

Here are some updated designs for this page!
Figma link: https://www.figma.com/file/BpSLUiJyajnZl0oJ82Jzsy/1XP---Web?type=design&node-id=8223%3A25220&mode=design&t=XLEdrQOzoBMReXAK-1
Updates include:

Updated header description & CTA
Updated header graphic/layout
Copy updates for the section headers & descriptions
Some card spacing/design updates


Spotlight: Make character limit check not check formatting or links.

The idea here is that formatting such as **, __, ~~, ect and links (bar the "text" in [[text<url>]]) do not count to the 500 character limit for daily spotlights. This has been requested by UnleashOurPassion (and iirc other staff members).

implementation of a similar thing at #5262

Yeah #5262 is a much cleaner implementation than the code I wrote, and is functionally identical as far as I can tell (provided you fix the regex to actually work)

Closes #5659


Server-side fetch in endpoints should have headers

Describe the bug
This is basically the same issue as #696 but for endpoints instead of the load function: if your endpoint performs a fetch, it will not contain the headers from the user's original request.
Reproduction
https://github.com/rgossiaux/kit-endpoint-headers
Logs
No response
System Info
System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 2.94 GB / 64.00 GB
    Shell: 3.3.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 16.8.0 - /var/folders/rn/2kdgb0jj25q2v656j3qc_ywr0000gn/T/fnm_multishells/764_1646342367055/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 7.21.0 - /var/folders/rn/2kdgb0jj25q2v656j3qc_ywr0000gn/T/fnm_multishells/764_1646342367055/bin/npm
  Browsers:
    Chrome: 99.0.4844.51
    Safari: 15.2
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.30
    @sveltejs/kit: next => 1.0.0-next.291
    svelte: ^3.44.0 => 3.46.4

Severity
serious, but I can work around it
Additional Information
No response

If you want these, you should pass them along yourself. The global fetch that you call in an endpoint has no idea what request it's being called as part of - and it can't in a cross platform way, because of the async single-threaded nature of javascript.
This would only be possible if there were a wrapped fetch function as an argument to the endpoint handler, like what pages get, but this feels too niche for me. Fetches performed in endpoints are generally API calls, and it seems unlikely that these should include all of the headers from the underlying incoming request - unlike what happens in page loads, where we are trying to simulate what the browser's fetch does.


Can't shim 'ipinfo.exe': File doesn't exist.

Bug Report
Package Name: ipinfo
#> scoop install ipinfo
Installing 'ipinfo' (2.8.0) [64bit] from dev-tools bucket
Loading ipinfo_2.8.0_windows_amd64.zip from cache
Checking hash of ipinfo_2.8.0_windows_amd64.zip ... ok.
Extracting ipinfo_2.8.0_windows_amd64.zip ... done.
Linking C:\Scoop\apps\ipinfo\current => C:\Scoop\apps\ipinfo\2.8.0
Creating shim for 'ipinfo'.
Can't shim 'ipinfo.exe': File doesn't exist.

Fixed for the time being


an idea about skip packages

Maybe it could be possible to add options in aursync for:

skip a given list of packages (from file or from option entries)
an other one for tell to skip unresolved updated packages, and put the list of unresolved ones (with errors) inside a specified file (who could be used later by aursync -u for check if stay unresolved).

This was initially discussed in #28.
About 2., if a dependency fails to update, and you're updating stuff that uses it anyway, things might break when you build said dependency later.
About 1., if you use vifm, you could have aursync not build targets when you remove them in vifm, a bit like vipe. I don't know how hard this is to implement though.

Yes, in fact, without aurutils, we can do many things too... without lot of tools, we can do stuff too... but, it is more complicate. The idea is to make the administrative life accessible to most of all of them, that is why i share the idea that, with aursync, we could do update with be locked when a package failed, and/or with give a list of packages we eventually don't want to update. If aurutils make the administrative life "more complixate', so... it is not an helper in some large terms.

this is an exception, and then, this exception could be look like an exception. In many other way (and i than that because i just have this situation happen with "hubic" package), a package failed to use dependencies new versions (said it "half break", because it is not really break), but this has no other impact on the system, just this package can not be update. So... because of that aursync -u will not finish to do his job for all the other packages in the list after this one ? a the reason would be an exception could happen ? ok, then add a condition for check that is a solution.

So you can now ignore packages with -i, e.g. aursync -u -i foo -i bar -i baz excludes foo, bar and baz from the update process. I've refactored some code in the process, so it's likely that things broke.
In addition, as long as you don't use -n, aursync won't retry already built packages (it does a version check).
If you still want to skip errors in the build process, modify aurbuild to something like this:
if ! makepkg <arguments here>; then
  error "Build failed!"
  read -r -p "Continue anyway? [y/N]"
  [[ ! $REPLY == [yY] ]] && exit 1
fi


Transactions: currency mismatch in filter amount and real amount

Describe the bug
on the transactions page, there is a mismatch in filter amount currency and the real amount currency.
To Reproduce
Steps to reproduce the behavior:

Go to /profile/transactions
Click on the Amount filter
See error

Expected behavior
Currency should be the same or it should filter for correct values (after currency conversion).
Screenshots
The amount is showing INR but the expenses are in USD.
The amount is selected as INR 50 - INR 500 but they actually filtered for USD 5 - USD 500

Desktop (please complete the following information):
Any
Smartphone (please complete the following information):
Any
Additional context

This filter uses the currency of your profile, so having ₹50 to ₹500 in there is expected. However it should indeed filter for correct values (after currency conversion).
In the API, the minAmount & maxAmount parameters should be of Amount type so that users can provide a currency. We can eventually implement these as new min and max fields, to make the change in a non-breaking way. Note that this applies to ExpensesQuery and OrdersQuery as well, we should probably update them.
Since an account can have transactions in multiple currencies, we should take that into account in the SQL queries. Something like this could work:
const minAmountUSD = await getAmountInUSD(args.min);
const accountCurrencies = await getCurrenciesUsedByAccount(account);
const amountConditions = {
  [Op.or]: accountCurrencies.map(currency => ({
    [Op.and]: {
      currency,
      amount: { [Op.gte]: await convertToCurrency(minAmountUSD, 'USD', currency) }
    }
  }))
}


MAC OS 10.13.6 + Python 3 + Matplotlib causing Spyder to not start

Issue Report Checklist

[X] Searched the issues page for similar reports
[X] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[X] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[X] Tried basic troubleshooting (if a bug/error)

[X] Restarted Spyder
[X] Reset preferences with spyder --reset
[X] Reinstalled the latest version of Anaconda
[X] Tried the other applicable steps from the Troubleshooting Guide

[X] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Anaconda 2020.02 for macOS Installer Python 3.7 and Python 3.6. with iMac 21.5" mid 2010, MacOS 10.13.6.
After install, launch spyder from anaconda-navigator GUI or from CLI. In the first case, blue and white progress bar goes on the bottom right shows progress for few seconds then nothing, but upon closing anaconda, spyder shows as a running program. From  CLI prompt error in line 4  blablabla "#@" just like many of the other problem report I found on this repository.
HOWEVER, IF UNINSTALL Matplotlib, Spyder 4.1.1. or 4.0.1 start properly but continue to have intermittent pop up windows declaring that has detected a change in the screen resolution and asks to restart Spyder.
What steps reproduce the problem?

Pretty much you need to have the same HW/SW Mac Combination or close. Tried on another old iMac mid 2010 with the same results.
Install Anaconda for python 3
Try to launch spyder
Try conda update -all, or conda update spyder with or without -f and any other suggestion I could find in this thread with no progress
back to Anaconda navigator or CLI, uninstall matplotlib and Spyder starts!

What is the expected output? What do you see instead?
From the combination of messages, pop ups and reading various proposed solution, I am pretty sure that this is a wired HW/SW glitch that has to do with iMac graphic card / MacOS , Matplotlib and Python 3, not Spyder. I post it here because Spyder is the death canary that shows the problem.
If re-install or add another environment with Python 2.7 (Anaconda distro)  all works fine.
MacOS comes with native Python 2.7 so there may be some other wired conflict going on there too.
Hope this help, at least nobody goes  through the whole mess like I did and feels alone against the world!
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

I did not past traceback and other details because i think i need a differ level of error log  to be of any help. If you know where to look I will do. Tks!

Sorry for the caps.
Yes I saw #11846 but I thought it was not related to this report because I only observed it after deleting Matplotlib.
Thank you for the guidance, I will comply.
V/R
Mimmo de Martino
The following is a recent quote from Elon Musk:  “Life cannot just be about solving one sad problem after another. There need to be things that inspire you, that make you glad to wake up in the morning and be part of humanity. That is why we did it. We did for you.”

On Apr 3, 2020, at 14:12, Carlos Cordoba<EMAIL_ADDRESS>wrote:

HOWEVER, IF UNINSTALL Matplotlib, Spyder 4.1.1. or 4.0.1 start properly
First no need of using caps here. It's considered rude on text messages (as you probably know).
Second, this means that this is not an Spyder problem, but a problem with Anaconda. So please report it here:
https://github.com/ContinuumIO/anaconda-issues/issues/
but continue to have intermittent pop up windows declaring that has detected a change in the screen resolution and asks to restart Spyder.
This is a duplicate of #11846. It'll be fixed in our next version.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


bug: weaviate and label_studio dependencies conflicts

Describe the bug
a couple of pip install's in CI and make install invalidate installed requirements installed in requirements/*.txt.
By calling pip install weaviate-client or pip install argilla in CI here:
https://github.com/Unstructured-IO/unstructured/blob/09cc4bf/.github/workflows/ci.yml#L148-L151
or in the Makefile here:
https://github.com/Unstructured-IO/unstructured/blob/main/Makefile#L49
we end up in a situation where the tested or local environments diverge from requirements/*txt and issues may be hard to reproduce.
both of these libraries have been updated since these pip installs were introduced, so it would be worth seeing if these extra installs can just be removed. otherwise, there should be ways of testing modified pip-install environments for each case separately, so that tests and install envs may be deterministic.
Additional context
Add any other context about the problem here.

Addressed in https://github.com/Unstructured-IO/unstructured/pull/1408 , though ideally would avoid a weaviate pin per:
https://github.com/Unstructured-IO/unstructured/pull/1408#issuecomment-1718368331

This seems to be resolved now through some of the more recent dependency refactors.


Compressor options in the .encoding dictionaries of a source xr.Dataset are not exploited by the rechunker

I noticed that when a Zarr store is read into a xr.Dataset (with compressor options present in each DataArray.encoding), and the xr.Dataset is provided as source to the rechunker, the compressor options are discarded in favour of a default
Blosc(cname='lz4', clevel=5, shuffle=SHUFFLE, blocksize=0).
Would be useful if the existing compressor options are exploited when saving the new zarr arrays.

Hi @ghiggi and thanks for the comment! Sorry it took so long to respond--several of us were on vacation in August.
I agree it would be useful to exploit xarray encoding options. We would welcome a PR to implement this.


[SPARK-47329][SS] Persist dataframe while using foreachbatch and stateful streaming query to prevent state from being re-loaded in each batch

What changes were proposed in this pull request?
Persist dataframe while using foreachbatch and stateful streaming query to prevent state from being re-loaded in each batch
Why are the changes needed?
This allows us to prevent stateful operators from reloading state on every foreachbatch invocation. Without this change, if the user did not persist the dataframe in their UDF and multiple actions are called on the dataframe, the query is evaluated multiple times within the same batch leading to the state store invalidating the loaded version and reloading from cloud each time, which leads to severely degraded performance.
For eg -
Without the change, we see the same state instance loaded and committed multiple times
sql/core/target/unit-tests.log:596:10:17:17.090 Executor task launch worker for task 2.0 in stage 8.0 (TID 20) INFO HDFSBackedStateStoreProvider: Committed version 2 for HDFSStateStore[id=(op=0,part=2),dir=file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2] to file file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2/2.delta
sql/core/target/unit-tests.log:710:10:17:17.612 Executor task launch worker for task 2.0 in stage 11.0 (TID 26) INFO HDFSBackedStateStoreProvider: Committed version 2 for HDFSStateStore[id=(op=0,part=2),dir=file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2] to file file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2/2.delta
sql/core/target/unit-tests.log:813:10:17:18.123 Executor task launch worker for task 2.0 in stage 13.0 (TID 31) INFO HDFSBackedStateStoreProvider: Committed version 2 for HDFSStateStore[id=(op=0,part=2),dir=file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2] to file file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-1ff51b75-034b-496d-8fc9-81df5ba78725/state/0/2/2.delta

With the change, we see the same state instance loaded and committed only once
sql/core/target/unit-tests.log:516:10:22:47.150 Executor task launch worker for task 2.0 in stage 8.0 (TID 20) INFO HDFSBackedStateStoreProvider: Committed version 2 for HDFSStateStore[id=(op=0,part=2),dir=file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-870e4666-52dc-471e-bb19-e6c8f372d0ca/state/0/2] to file file:/Users/anish.shrigondekar/spark/spark/target/tmp/temporary-870e4666-52dc-471e-bb19-e6c8f372d0ca/state/0/2/2.delta

Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unit tests
[info] Run completed in 20 seconds, 898 milliseconds.
[info] Total number of tests run: 11
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 11, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

Was this patch authored or co-authored using generative AI tooling?
No

@HeartSaVioR @sahnib @zsxwing - Could you PTAL ? Thx

Thanks! Merging to master.