_ServerConnection refactor to be able to support upgrading protocols

Do not merge yet. This is more for code review, to see if you have any concerns with refactoring the code this way.
Basically:

Application Protocol (in this case HTTP) parsing logic is moved out of _ServerConnHandler, and into a new class _ServerConnectionProtocol that runs within the context of the _ServerConnection actor.
_ServerConnHandler is just passing raw data to _ServerConnection via received(...)
All protocol related states (close_after, active_request etc) consolidated into _ServerConnectionProtocol implementations (in this case _HTTPServerConnectionProtocol).

The idea being, when upgrading protocols:

Nothing needs to change in _ServerConnHandler
_ServerConnection simply needs to swap _protocols, and will get the upgraded protocol, along with state information needed to support the new protocol.

I designed this with WebSockets in mind, but don't see why this wouldn't apply to HTTP/2 (which I may tackle afterwards).

This looks good to me and i like the idea of this lib becoming extendable. :+1:
This PR preserves having the HTTP logic handled in a separate actor. Creating a class for protocol handling shouldn't be too much overhead. So I am not in general worried about performance here.
How would you signal a protocol upgrade to the _ServerConnection actor? Any ideas here already?

For future "do not merge yet" PRs, please open them as drafts. It avoids them being accidentally merged.

This looks good to me and i like the idea of this lib becoming extendable. 👍
This PR preserves having the HTTP logic handled in a separate actor. Creating a class for protocol handling shouldn't be too much overhead. So I am not in general worried about performance here.
How would you signal a protocol upgrade to the _ServerConnection actor? Any ideas here already?

Thanks for the quick review!
I have attempted a partial POC in this branch - https://github.com/jackgene/http_websocket_server/tree/feature/websocket-support
I confess though that while my initial plan was to make http_server extendable (such that WebSocket and HTTP/2 support can be a completely separate library), I had trouble coming up with a fully extendable design. This implementation still requires WebSocket to be baked into http_server - primarily because I still need _ServerConnection to be able to "speak WebSocket" (for server -> client communications).
I'm hoping to spend this weekend getting the POC fully functional.
After that, I'd like to revisit the idea of making http_server extendable (i.e., support HTTP/1.x only, with the ability to upgrade protocols, but relying on third parties to implement "upgraded" protocols).

Wanted to mention that I attempted to implement a WebSocket POC with this design, but ran into some problems.
However, I thought of an alternate solution that requires even less change to the current http_server design that I'm going to attempt in the coming days.

I was just going to point you at the possibility to switch out the TCPConnectionNotify with TCPConnection.set_notify. Maybe like this you could execute the upgrade and replace the _ServerConnHandler. This way we wouldn't even need the layers of indirection of a _ServerProtocol, although i like some parts of those changes you made in this PR.

I was just going to point you at the possibility to switch out the TCPConnectionNotify with TCPConnection.set_notify. Maybe like this you could execute the upgrade and replace the _ServerConnHandler. This way we wouldn't even need the layers of indirection of a _ServerProtocol, although i like some parts of those changes you made in this PR.

Hi, sorry about the lack of response, I've been trying out various approaches, and the good news is that I was able to get the approach I started on this branch to work. I just need to clean things up a little bit, but I'm hoping to share that shortly (I'll probably create a separate PR against this branch, just to make the changes clearer).
On the subject of using set_notify, I had two concerns with it:

The major one is that in "SSL-mode" I'd have to replace a connection that is wrapped in an SSLConnection with a new connection that is wrapped in a different SSLConnection instance, and I wasn't sure if this would cause problems (e.g., Is the wrapper smart enough to know when SSL handshake has already occurred? Or would it attempt to handshake again, breaking the connection?)
This is more minor, but there are conveniences to keeping a single connection, in terms of the session register/unregister logic.

That said, I do have a separate prototype that uses set_notify that I'll keep around, in case I want to investigate this approach further.

Just wanted to follow up and let you know that I have a working (but incomplete) WebSocket protocol support implemented in:
https://github.com/jackgene/http_websocket_server/pull/1
I made it a separate PR (to this branch), to make it more obvious what are:

Changes to the core server code to support multiple protocols (this PR)
Changes specifically to support WebSockets (linked PR)

Please read initial comment on that other PR for my current thoughts/concerns/plans
In addition, for now, I've created a web application that uses this - to give me a feel for what it's like using this API - here: https://github.com/jackgene/presentation-service-pony

Should this PR be closed given your last comment @jackgene?

Sorry, been meaning to address this. I'll close it for now. As mentioned, I'd like to use this API for a little bit, and try and make it better. Will make another PR when I have something cleaner.


Click-Drag mouse highlighting does not work

Click-drag highlighting with mouse does not work currently, even when running :set mouse=a.
I'd add more info, but I don't know what else to report on the issue. This also may be more of a feature request than an bug.
OS: Windows 10
Version: N/A

Yep, missing feature - basic mouse interaction we need. Thank you for logging it @jrwrigh 👍

Is this feature on the roadmap yet? Being able to use the pointer to interact with the cut-and-paste select buffer would be a huge step toward usability. Thanks!

@smolin  Everything that is tagged as daily-editor-blocker is on the roadmap before we consider Oni2 "beta" quality!


mongomock does not support the $sample operator for aggregation framework

https://docs.mongodb.com/manual/reference/operator/aggregation/sample/

Thank you !!!


Issue: cpuTimeoutError onClientResponse/onClientRequest

Thank you for providing this example! We've successfully deployed the code to an Akamai tier 200 Edgeworker and for the most part things are working great.
About 20% of the time we see a cpuTimeoutError though. We've added retrying using https://techdocs.akamai.com/edgeworkers/docs/site-failover#retry-the-request which works well for Get and other idempotent requests, but this won't work for requests that modify state. For example, if we're making a post request to add an item to the cart, if that fails, and then gets retried we may end up with an error or two items in the cart, etc.
I'm wondering if you have run into this issue and/or have any advice

cc @simone-coelho

With the Akamai increase to EW resource limits we no longer have this issue


CLI support for file name

The npm package allows to set a file name for the generated file, the cli version doesn't have this flag. Would be very handy to support this option.

This is not a CLI option because templates are based in directories, not files. What you see in the package is a handy method for when you want to generate a single file. Not sure if it could be somehow used from the CLI. Ideas?

Thanks. I was speaking about the options.file, which is described as "Path to the file you want to generate".
I was thinking that I could set it to "something.md" and once I run ag -o ./docs asyncapi.yaml markdown I'd get something.md instead of asyncapi.md. Probably I misunderstood the whole "as a module" section. Is there an easy way to implement what I described? Otherwise I'm fine with just renaming the files in CI.

Oh, I understand. What you described is not what is offered as a module. options.file is the entry point for the template compilation. This is for templates to have multiple subtemplates. For instance, the HTML docs template has 2 versions: one with sidebar menu and one without it.
The problem with implementing what you want is that templates might result in many files (e.g. code generation), not just a single one. If you have an idea on how to make it possible, I'm all ears :)


Improve CONNECTOR_API_KEY documentation in all READMEs

Which connector is affected?
All connectors
What would you like to see improved?
Currently it can be confusing or unclear what the CONNECTOR_API_KEY environment variable is used for.
We need to clarify:

That the user will need to create and manage their own keys to secure the connector
That the CONNECTOR_API_KEY is required for all connectors
That this key will be used to authenticate requests to the connector when calling the /search API

Additional information
No response

#136 resolves this - closing


Make stdout/stderr capture optional in BaseTestCase

In order to debug issues in the product tests that we only see on OpenStack,
it would be super helpful to be able to print messages for debugging and see
the output, as we can't log in to any of the docker containers or even debug
the tests themselves. This change makes output capture optional and enables it
for the unit tests that require it.

Aren't you missing the BaseTestCase change?

Nope! I absolutely did not completely forget to include BaseTestChange in the original push to the branch. Nothing to see here :-)

looks good


Draft: Fixed: React lint warnings

This PR intends to resolve the React warnings as described in #598
@BeritJanssen the remaining linting errors are all react-hooks/exhaustive-deps, e.g. "missing" or "incorrect" dependencies. Now, eslint proposes fixes here, but I'm not completely aware of what happens and should happen exactly so I'm afraid to break stuff, and I don't want to risk that over some linting warnings. Perhaps you can look into these or we can look at them together in the future?

Thanks for configuring the linter. I think that indeed we should review the missing dependencies for the hooks manually. #648 should fix some of those warnings already.

I think we can merge some of these adjustments by the linter already, and take care of the missing / incorrect dependencies in the react hooks later. Perhaps as a team we should review our linter settings, since I'm not sure everyone has one configured.
But please undo the change removing finalizeSession from API.js and Final.js. Indeed, I see that finalize() is never called, while it should probably be placed into the useEffect hook as a cleanup function.

I've looked it up and you have updated the call to finalize on June 20 here and made the div into a a element: https://github.com/Amsterdam-Music-Lab/MUSCLE/commit/1cc4ac45c1253761beefc5da76e2b4184e07107a#diff-dd2727c4ba071122a678bb23e7b9b2833fd33ab5995321f1df7d3dc4f4523d33
I think then it got removed after merging develop into a feature branch while resolving conflicts and so on:
https://github.com/Amsterdam-Music-Lab/MUSCLE/commit/1cc4ac45c1253761beefc5da76e2b4184e07107a#diff-dd2727c4ba071122a678bb23e7b9b2833fd33ab5995321f1df7d3dc4f4523d33
Apart from that, I don't know if it ever behaved like it should have? I can imagine when you click a link that also has a onClick handler, race conditions might cause the onClick never to get executed or finished as it already navigates towards a new page.

Merging this and addressed the finalize session not being called as a seperate issue in #676 !


General EFI Question

Appreciate you for sharing your EFI folder. I have the same T480 h/w configuration and wish to install Big Sur and beginning by comparing my EFI based on Dortania's guide to your configuration.
My naive question is are all the 17 SSDT necessary. Many I have not seen in the guide. Similarly 30 kext files is much larger than the 14 or so I gathered.
Thanking you in advance for input.

I think you will be fine by using the EFI folder as default without altering it.. Worked like a dream.. (Do also have the same hw configuration)


Docs error: isort section-order default

The docs for isort section-order setting, list default value as []. From my testing and code spelunking, it seems, that the default value is actually not empty, but the same as the order of sections in the enum that represent this.

Yeah, I think you're right.


Remove Kubic workaround, caasp-tools no longer conflicts

Urgent - there is a mismatch between what is in our git repo and what is in OBS - this resolves that.
Any caasp-container-manifests submissions before this gets submitted to Factory risk breaking Kubic

I was waiting for the tests to finish but they fail. Still I don't think they are related, since your change is related to the package.


Add and fix the new aggregation functions

This changes the aggregation functions under schema.Function to reflect the current API.
To find this bug the pydantic parsing of Enums was changed according to https://github.com/pydantic/pydantic/issues/355.
Also note: It seems that https://github.com/jheddings/notional/blob/main/.github/CONTRIBUTING.md is quite outdated as make devenv didn't work for me and there was a switch to poetry instead of using requirements.txt files directly.
P.S. Thanks for your great work, it's cool to see that you are back and working on this useful library :-)

Thanks for the PR (and your continued use of Notional)!
Like too many of my side projects, I don't get to spend as much time as I would like.  Hopefully this one will continue to be useful and have good users to help move it along.


fix: rename to rustdoc::broken_intra_doc_links

Found in https://github.com/rust-lang/cargo/pull/14209#issuecomment-2216340197.

Thanks!
@bors r+

:pushpin: Commit 7e78271c5f52151ecd41143ea7545da444a3faa3 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 7e78271c5f52151ecd41143ea7545da444a3faa3 with merge caf36efbacc3ca755e52f937bb4cbf6af09502c1...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing caf36efbacc3ca755e52f937bb4cbf6af09502c1 to master...


[DNM] Parse /.../ regex literals

Try to lex regex literals with /.../ delimiters, using two heuristics:

A check on the previous token to see if the opening / must be the start of an expression.
When / starts a new line, the next character must not be a space, as that indicates an operator chain.

The lexing logic is still WIP, but it should be sufficient to gauge the source compatibility impact. This PR enables the lexing by default, but if -enable-experimental-string-processing is omitted, an error will be produced if a regex is parsed. Additionally, this PR bans prefix operators that contain /.

@swift-ci please test source compatibility

@rintaro The lexing logic is still WIP as:

Sub-lexing still needs to taken care of
The heuristic needs formalizing
The lexing loop needs to handle additional cases e.g invisible ASCII
Prefix operators on regex literals needs to be implemented

But let me know if you have any initial thoughts

@swift-ci please test

@swift-ci please test source compatibility

Sub-lexing still needs to taken care of

What do you think are the issues sub-lexing might cause?

The lexing loop needs to handle additional cases e.g invisible ASCII

Could you elaborate? Any example?

What do you think are the issues sub-lexing might cause?

I don't think it currently causes any issues, e.g for delayed body parsing we start on the opening {. But it seems like a sub-lexer should be able to handle the case where it starts on an opening /.

Could you elaborate? Any example?

String literals currently diagnose invisible ASCII characters they come across, we probably ought to do the same for regex literals.
https://github.com/apple/swift/blob/d3702bacbb418afd4d4915cbebd77265dad50a65/lib/Parse/Lexer.cpp#L1338-L1344

@swift-ci please test macOS

@swift-ci please build toolchain

Updated to re-lex regex literals from the parser

@swift-ci please test

@swift-ci please test source compatibility

Continuing work on https://github.com/apple/swift/pull/42119


Update for the latest version of QuadProg++

Now QuadProg++ is hosted on Github, with changes to some names.

looks good

Uploaded to Hackage.


[BUG] ServiceBus ExpiresAt is set incorrectly when sending a cloned message

Library name and version
Azure.Messaging.ServiceBus 7.16.1
Describe the bug
When cloning a message w/o TTL and sending the new message to ASB w/o specifying TTL, the ExpiresAt should be set to the EnqueuedTime + TimeToLive according to docs.

The UTC instant at which the message is marked for removal and no longer available for retrieval from the entity due to expiration. Expiry is controlled by the TimeToLive property and this property is computed from EnqueuedTime+TimeToLive

But that's not the behaviour for a "cloned" message using Azure.Messaging.ServiceBus 7.16.1+5a3f6c0a6c047e8bfa26cdf29ae2f5771ab08b2b w/o TTL on the message.
Expected behavior
ExpireAt should be set to 9999-12-31 23:59 for messages w/o TTL on entities with TTL set to TimeSpan.MaxValue and no TTL on the originally received messages.
Actual behavior
Messages cloned using
var clone = new ServiceBusMessage(serviceBusReceiveMessage);

and sent w/o TTL to an entity with TTL set to TimeSpan.MaxValue

have their ExpiresAt value set to less than 2 months into the future (49.17:02:47.2950000), unless a workaround is applied (highlighted entries, see below)

Workaround
The workaround is to set the TTL on the cloned message to TimeSpan.MaxValue
clone.TimeToLive = TimeSpan.MaxValue;

Reproduction Steps
var clone = new ServiceBusMessage(serviceBusReceiveMessage);

Environment
.NET 6/7

I've peeked into the public ServiceBusMessage(ServiceBusReceivedMessage receivedMessage) constructor code to debug what happened. For a message with ID 350db999-2efd-497e-b2fb-f9df81306f31, the TTL reported by the broker was right.

But when the message was received and used to construct a new ServiceBusMessage, the received message TTL was the arbitrary 49.17:02:47.2950000 value.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

It looks like this is happening because the Microsoft.Azure.Amqp library defines Ttl as a uint which has a max value of<PHONE_NUMBER>, which in milliseconds would be translated to approximately 49 days. The AMQP spec  similarly defines the TTL as millisecond represented using a uint. I'm not sure how Service Bus explorer was showing a larger value, but is it possibly using SBMP?

SBE is using SBMP but it's only reflecting what's coming from the broker. And in this case the cloned message is what's coming from the broker. It's not very obvious in most scenarios unless you need the message to live longer than 49 days. And that's more of a bug than an improvement. I'm not blocked as I can workaround it but a proper behavior would be good to have ootb. Thanks, Josh.

@JoshLove-msft any updates on this?

I am not sure the issue I am facing is the same or not.
Consider an Azure Service Bus queue called main with DeadLetteringOnMessageExpiration = true and ForwardDeadLetteredMessagesTo = "main.dlq".
When a message is published to the main queue with some delay (future scheduledEnqueueTimeUtc) and that message is expired and forwarded to the main.dlq queue, the new message in the main.dlq queue still has the original message ExpiresAt value which is already in past time.
I am using MassTransit and it ignores messages with ExpiresAt in the past, and this message is not processed.

@rmeshksar that would be a service side, not the client SDK IMO. Dead-lettering and auto-forwarding are done by the service.

I think it is client SDK and the value of the ExpiresAt is caculated is here:
https://github.com/rickmark/azure-sdk-for-net/blob/16ac6c4a31cb012560e4ccfd324433365e009ab6/sdk/servicebus/Azure.Messaging.ServiceBus/src/Primitives/ServiceBusReceivedMessage.cs#L366
Let me explain with an example (Screenshots from Azure portal)
At 13:52:09 a message is published to main queue with the delay of 60 seconds

Then when it is queued:

After 2 minutes it gets expired and forwarded to main.dlq

So far according to Azure portal information is good, but when the message is received in the ServiceBusProcessor it has this information:
EnqueuedTime: {2023-12-11 1:55:37 PM +00:00} <--- (Same as above)
ExpiresAt:	{2023-12-11 1:55:09 PM +00:00}  <-- (NOT the same as above)
TimeToLive:	{00:02:00} <-- (Same as above)
As you can see the value of ExpiresAt is NOT the same as what we see in portal as ExpitesAtUtc and the value is not EnqueuedTime + TimeToLive

It seems when expired message is forwarded to the second queue, the AmqpMessage has the original AbsoluteExpiryTime which is in the past. It should be recalculated when message is forwarded.
I am not sure how this issue should be reported though.

So I dug into this some more and found something very interesting. The service behavior of what TTL is sent back appears to depend on how the queue is created. If the queue is created through the portal, and then the TTL is marked as Unbounded after creation (which appears to be the only way to make it unbounded), we see the behavior where the service sends back a TTL that gets transformed to 49 days. However, if I create the queue using the ServiceBusAdministrationClient and do not specify any TTL, then the service does not set a TTL and the client correctly translates this to the max TimeSpan value. I will need to follow up with the service team to see if this behavior is intended.

Discussed with service team and filed https://github.com/Azure/azure-sdk-for-net/issues/40915


Wrong result for query "Get the top 5 grossing states" in sample colab

According to data total value for every row should be calculated as Price Each * Quantity Ordered. In sample colab library summarizes prices but doesn't take in account quantity.

Hey~
Good catch! I agree with your interpretation that the AI should have generated a new feature to measure the "grossing" attribute, and then calculated the result.
This is definitely the main type of failure case with these ai-assistant / code-generation tools, where it misunderstands and gets something "subtly" wrong. This is precisely why we made this tool give you the code back rather than executing the code and telling you the answer
At the quality of current models, we can't blindly trust the code it writes, so; in general, the code that comes back from howto is best thought of as a really good starting place!
Unfortunately, there's not much I can do to improve this, this is somewhat "working as intended" and is reliant on the quality of the underlying model (right now davinci-text-003) so I'm going to close this issue.
If there is anything specific you think I should change (eg. in readmes, or in code) let me know, i welcome any recommendations on how to add clarity!


[FEATURE] Dialog warning that NAM is in beta

Make a dialog that shows up the first time someone opens the standalone warning them that yes, I know there's bugs, and to suggest using the VST3 or AU in the meantime.
Needs to only show up once or else people will complain :)

Persistence gist: https://gist.github.com/olilarkin/4c9b5c9697b5c5720017e7b5c8f030c9?fbclid=IwAR0P32Up9hsx--QM1ZzCa7nnWl-MRTfPqXCAElKTMXHz_20qhIbqh0T86wk


Unnecessary white spaces for before/after HTML tags

Hey, I'm using this in order to achieve a stats bar that will show how many lines, words, chars and spaces a document contains and I realized that there are some extra unnecessary white spaces in your code.
I suggest to remove the white spaces before/after HTML tags for all your default transforms.
Also, transforming the delimiter can be a good idea to be hr instead of br

@georgelemon whitespaces were added for code readability. However, has been removed.
delimiter will remain br for code consistency, and to be in-line with previous versions. However, you can always override defaults with your own.
https://github.com/pavittarx/editorjs-html#extend-for-custom-blocks
Change type to field you want to override. For example {type: 'delimiter'} in your case.


tensorflow-gpu fail for windows 7 T_T

My computer installed tensorflow-gpu for windows 7 (FX 2800M)
but GPU not understanding my counter...T_T
always tensorflow cpu understandig...
CUDA  v8.0 and v6.5 Cudnn v5.1 and v 2.1
Fail log is
F c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\cuda\cuda_driver.cc:94] Check failed: s.ok() could not find cuDevice
plz.. help me!!

According to this page, Quadro FX 2800M only has CUDA Compute Capability 1.1 and therefore is not supported. 3.0 is the minimum requirement.

Thanks for filing the issue @jumemae , and thanks for the reply @microtony !
For future reference, this type of question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


[NEW ALGORITHM] Clone a linked list with Random connection

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:  Clone a linked list with Random connection
[NEW ALGORITHM]
About:
Given a linked list where each node has a next pointer to the next node in the list and a random pointer that can point to any node in the list (or be NULL), create a deep copy (clone) of the list. The cloned list should have nodes with the same values and maintain the same next and random pointers structure as the original list.
Explanation of Solution
We will use an unordered_map to store the mapping from each node in the original list to its corresponding node in the cloned list. This will help us efficiently set up the next and random pointers for the nodes in the copied list.

Mapping Nodes: In the first traversal, we create a new node for each node in the original list and map it to the original node in the unordered_map.
Setting Pointers: In the second traversal, we set the next and random pointers for each cloned node. Using the unordered_map, we can efficiently look up and set these pointers to ensure the cloned list has the same structure as the original.
Returning the Cloned Head: Finally, we return the cloned node that corresponds to the original list’s head.

Labels:
new algorithm, gssoc-ext, hackoctoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

assigned


riscv/mpfs: Add boilerplate code for SMP

Summary
Add boilerplate code for enabling SMP mode for MPFS target.
Impact
Add SMP build support for MPFS target. No other target is affected.
Testing
Build passes
Simple MPFS SMP target boots to nsh console

[Experimental Bot, please feedback here]
Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.
Yes, the PR appears to meet the NuttX requirements.
Here's why:

Summary: Clearly explains the purpose (add SMP support to MPFS), what part of the code is affected (MPFS target), and how it works (adding boilerplate code).
Impact:

Accurately identifies the added feature (SMP build support for MPFS).
Addresses all impact areas, indicating no change or describing the specific impact.

Testing:

Confirms testing on a local setup.
Provides basic evidence that the build passes and the system boots.

Suggestions for Improvement (to make it even stronger):

Summary: Consider linking a related NuttX issue if one exists for tracking the feature request or bug.
Testing:

Specificity:  Be more specific about the build host and target used for testing (e.g., "Linux, x86_64, GCC 12.2.0",  "sim:qemu-rv32").
Functionality: Go beyond basic boot testing. Demonstrate that SMP functionality within the MPFS target is working correctly (e.g., running a multi-threaded application that interacts with the filesystem).
Logs (Optional): While not strictly required in this case, providing relevant snippets of logs (especially around SMP initialization) can be very helpful for reviewers.

By adding these minor enhancements, the PR would be even stronger and easier for reviewers to assess.


Superset becomes unresponsive if a database is not responding

Expected results
If there's an issue with a single database it should not crash the whole system.
Actual results
A couple days ago we experienced a production outage when we noticed all of the web frontends (~10) were unresponsive and removed by the ELB.  After restarting all of the web frontends we were able to load some of the pages.  However, it became unresponsive again shortly after.  Web server logs didn't reveal any obvious errors.  Eventually we noticed the databases tab doesn't load at all after a rolling restart.  It turned out that our Hive server were not able to accept new connections due to hitting its thread limit.  After rebooting Hive server, Superset started to function properly again.
I don't believe many people were trying to load the Databases tab, but people were trying to run adhoc queries using the SQL Editor.  Loading the SQL Editor caused the Databases dropdown to load which I believe is similar to loading the Databases tab.  During this time the Databases and Schema dropdown were blink.
We are running Superset 1.0.1 Docker image.
Screenshots
Didn't take any screenshots, but the Databases tab was completely blink as if it was trying to load.

sounds severe! if you could upload logs that would be helpful @aaronfeng

@amitmiran137 unfortunately I didn't see anything that was useful in the logs.  I assume you mean web server logs?  It was a lot of trial and error to debug the issue.

I dealt with this directly. From what I can tell several operations fail or take unnecessarily long if a db connection fails when they definitely shouldn't. This behavior multiplied the complexity and extent of an otherwise simple outage blocking access for all users on all other DBs.
When a database connection takes a long time to respond we've seen the following endpoints also timeout:
List databases api /api/v1/database/ (breaks sql lab)
List Databases page /databaseview/list/
Database Edit/Save
It's not clear why any one of these pages would need to verify all connections before loading data. I haven't dived into the code, but this seems like a major design flaw. During our outage there was no way to debug or modify anything through the web interface. What's worse is that by design Superset doesn't allow deletion of entities whenever there are dependent tables (delete on cascade) so dealing with the permanent deletion of any database is colossally painful. Anyone who has tried to delete and been blocked by a maze of foreign key constraints. I realise not cascading on delete is safer, but not allowing a safe way to do this makes administration unreasonably cumbersome.

While this issue is obviously stale, it still sounds gross. Did anyone on this thread happen to run into this again or gain any further insight they can add? Is this still a risk in (significantly) newer versions of Superset, e.g. 2.1.0?
CC @betodealmeida @nytai @bkyryliuk in case they have any insight into whether this is adressable and/or ought to remain open (despite the reported version of Superset no longer being officially supported).

As a rule of thumb we separate API endpoints that hit only the metadata database from API endpoints that hit analytical databases. Requests to the latter should be asynchronous and non-blocking (eg, that's how we do loading function names for the autocomplete in SQL Lab). That being said it could be that there are places where we're not doing that properly. I remember fixing a few use cases (including the function names), but it would be nice to do an audit.

We encounter this issue periodically on Superset 2.1.1. When Superset becomes unresponsive, we inspect Trino and identify a long-running query. Once we terminate that query, everything returns to normal.

Just a note that we no longer support Superset 2.x. Is anyone able to repro this in 3.x?

I have encountered this issue with Superset 3.1.0 as well. Any pointers on how to resolve this?

I've encountered the same issue with Superset 4.0.2 on both Chrome and Firefox browsers. The query runs without any problems when using DBeaver (JDBC client) and completes in just 2 seconds.

HI @SGH-N are you able to solve this problem? i am also facing the same issue could you please help.

No, we couldn't find a fix..

HI @SGH-N are you able to solve this problem? i am also facing the same issue could you please help.

No, we couldn't find a fix..

thank you for your response @SGH-N

We have hit this issue on 3.0.3 where a user's dashboard loaded a bunch of Trino queries that were stuck in WAITING state. This lead to the server being completely unresponsive and even liveness probe failures in our k8s deployment.


Stack translation doesn't work with case expression

Currently stack translation doesn't handle correctly case expressions (not detecting tail call position).

@zonyitoo Let me know if it works

let reverse[A] (l : PList[A]) : PList[A] =
    (let rec inner[A] (l : PList[A]) (acc : PList[A]) : PList[A] =
        case l of
            Nil         -> acc
         |  Cons x xs   -> inner[A] (invoke[PList[A]] xs) (Cons[A] x xs);
     inner[A] l (Nil[A]));

If I call this function with
listToString[Int] (reverse[Int] (take[Int] 10000 (nats 1))) (\(x : Int) -> x.toString())

It should show [10000, 9999, 9998, ..., 1], but it only shows [10000].
Full program has been sent to @bixuanzju .

@bixuanzju yes! it works!!!


Search with nested relations has errors

I'm working around search with nested relation and receiving error on column names mismatch.
Here is my example:
class Manufacturer {
     @PrimaryGeneratedColumn()
     public id: number;

     @Column()
     public name: string
}

class PublicCar {
    @Column()
    public manufacturer_id: number;

    @ManyToOne(() => Manufacturer)
    @JoinColumn({ name : 'manufacturer_id' })
    public manufacturer: Manufacturer;
}

class PurchaseRequest {
    @Column({ nullable : true })
    public public_car_id: number;

    @ManyToOne(() => PublicCar)
    @JoinColumn({ name : 'public_car_id' })
    public publicCar: PublicCar;
}

Settings for pagination function:
{
      searchableColumns : [ 'publicCar.manufacturer.name' ],
      relations : {
            publicCar : {
                manufacturer : true,
            }
        },
}

When i try to make ?search=sometext, then i receive a query and an error below:
SELECT ...  Has been reported in here #509 and tests have been provided. Needs fixing/impl.

Thank you, i'll wait.


Bad render results for KHR_materials_unlit Khronos test model

The Khronos Unlit Test sample model README says that for the test model using this extension:

The visible surface ... should appear as a uniform color, so much so that the 3D effect is intentionally lost.

And offers the following as examples of good and bad render results:

Good
Bad

Here are examples of how <model-viewer> renders this model w/ various settings, all if which seem incorrect (possibly for different reasons):

model only
HDR background-image
experimental-pmrem

I also tested to see how Filament's gltf_viewer handles this case. It seems to handle the model correctly (presumably it supports the KHT_materials_unlit extension).

Filament gltf_viewer

The viewer will need to avoid setting .envMap on MeshBasicMaterial - that material type is not subject to all the limits of the glTF unlit material, and adding the envMap will “break” it. Not sure what’s going on in the “model only” case though.

The viewer will need to avoid setting .envMap on MeshBasicMaterial - that material type is not subject to all the limits of the glTF unlit material, and adding the envMap will “break” it. Not sure what’s going on in the “model only” case though.

A "default" env map is created in that case, leading to the "lit" appearance there. For PMREM, this is all black since an unlit material doesn't know what to do with a PMREM environment map


Workdate not correct

Hi,
when creating a new company, for a reason I do not know, the field CompanyInfo.demo environment is set to yes.
thats the reason why the workdate is nog correct, it will take the last posting date on g/l entries.
I can not find how we can add the field on the page, without using a page extension. Even not with personalisation.
I'm working on BC160 saas, so latest CU.
Thanks,
Stijn

Sorry, i meant field 100 Demo Company
On SAAS customers, I can not find this field on the page.

When creating new company, You get a wizard on Saas environment, but can you manipulte this parameter afterwards?

My bad, I was looking at system table Company, not 'normal' table Company Information. I grepped through on-prem source code and can't see anywhere that sets Demo Company. Mysterious...

There are 4 options when you create a new company:
https://docs.microsoft.com/en-us/dynamics365/business-central/about-new-company#creating-a-new-company

Evaluation - Sample Data

Production - Setup Data Only

Advanced Evaluation - Complete Sample Data

Create New - No Data

The "Demo Company" field is set to true for Production and New. It is not supposed to be modified by users, because the evaluation companies are for demonstration only.
But you can create an extension that would add this field to a page, where you can change it.

The "Demo Company" field is set to false for Production and New.

Surely it should be false for those, and true for the others? ;-)

Ok, Thanks. What if you made a mistake, and the company is already used by the customer, there is no way back, except making an extension?

That is right. The evaluation company contains the demonstration data (customers, vendors, items, etc.) and it is not supposed to become a production company.


HRSC2016 download link

Thank you for your wonderful work,I was wondering if you can give me the HRSC2016 dataset download link， I can not find the download linke on the Internet. Appreciate!

I have found it in the https://aistudio.baidu.com/aistudio/datasetlist/2

@byfate This link is invalid. Could you please send another link of HRSC2016 data set?Thank you very much!

@Luiweony here it is,
https://aistudio.baidu.com/aistudio/datasetdetail/75485


[ask] typescript hint and auto complete seems not work as expected

Environment:
vscode: Version: 1.79.1

"orchid-orm": "^1.10.6",
"pqb": "^0.12.5"

Not everything is broken.
For db.table.methods, these methods have right type db.table.method(params).
For db.table.method(params), these params do not have right type hint.

I'm not sure if this is my own problem or something wrong with the lib

But<EMAIL_ADDRESS>&&<EMAIL_ADDRESS>do have the right type suggestions<EMAIL_ADDRESS>&&<EMAIL_ADDRESS>do not work.
Type hint for 0.12.5

Type hint for 0.12.4

expiredAt is what I want.

but in where(params), it even do not verify column corrections

It's really not related to recent versions as there were no type changes for where or nearby in the last maybe few weeks.
On my side TS highlights wrong columns passed into where. VSCode may be confused when switching from one version to another, maybe try to reopen it?
Also, it could be possible that you explicitly listed a specific version of pqb, but orchid-orm depends on a slightly different version and there are type collisions.

Really strange, I'll dig deeper to see what happens.

I may found the reason.
This commit changes orchid-core, but it's not published

So, when new version of pqb and orchid-orm imoprt { TemplateLiteralArgs } from 'orchid-core', it's not exists in<EMAIL_ADDRESS>Rebuild and publish should solve this problem

With the release of the new version, this issue has been automatically resolved.


netload crashes when trying to upload a valid file

I am going to remove the functionality from the bot entirely

Removed in 5ec779b7a9f5ef8ec5d4eebfa749d1f81c2a5b3a


GNOME 45 support

@flexagoon
Hi, I just want to let you know that for some time now I have integrated your extension as one of the options that allows my project to support app-specific (and window-specific) keyboard shortcut remaps on Wayland+GNOME, by providing a way to grab the app class and window title.
I have a couple of other compatible extension options:

Window Calls Extended
Xremap

All three extensions can be installed and enabled, and my project will use the first one it finds responding to queries, and will transparently jump to another one if the active extension is disabled.
Yours is the newest extension, from what I can tell, and I only found it by accident while searching extensions for "focus", which is part of the description of the Xremap extension.
Having three different extensions being compatible with my project means my users will be more likely to have an extension available for any new GNOME version to keep my project working. But the other extensions also support older versions of GNOME, with Xremap supporting GNOME back to 3.38, which turned out to be needed for Zorin OS.
As of today the Extension Manager app scans your extension as not supporting GNOME 45. I've heard that GNOME 45 will be pretty disruptive to extensions that don't get updated. It would be very much appreciated if your extension could be one of those that is compatible with GNOME 45 before the beta period is over. I use Fedora and they generally move onto the latest GNOME release with each of their 6-month releases.
Thanks for the extension. 👍🏽
My project:
https://github.com/RedBearAK/toshy

Hi! The window information API that this extension is using is unlikely to change between GNOME releases, so supporting GNOME 45 is probably as simple as adding 45 to the list of supported versions.
I can go ahead and add it right now, but it'd still be nice to test it first in case the API did actually change somehow. Do you have access to GNOME 45 to help me test if the extension works on it?

Do you have access to GNOME 45 to help me test if the extension works on it?

I do have Fedora 39 beta in a GNOME Boxes VM, where they are already on GNOME 45. I used the "Everything boot" last-known-good ISO build from here, right at the top in the Fedora 39 column:
https://openqa.fedoraproject.org/nightlies.html
I saw someone else posting in the GNOME subreddit about wanting to test their extension on GNOME 45, and the F39 beta ISO was one of the main things mentioned where they already have G45 integrated.
One can hope that it will be as easy as changing the version number, but the articles have been claiming that all current extensions are using a couple of instructions that will need to be replaced because the module type is changing. Or something.
Thanks for the response. I can test any time. I already have my project set up in the F39 beta VM and working in X11/Xorg so as soon as I switch to Wayland there will be no extension active because they are all claiming to be incompatible right now. Should I try the trick where you just go edit the extension file and make it think it's compatible with "45"?

@flexagoon
I tried the trick of just adding the "45" to the version list and rebooted to make sure it would take effect.
As I kind of expected, there is now an error shown in Extension Manager:
import declarations may only appear at top level of a module

I think this is what all extension devs are having to deal with when moving to GNOME 45. There's a migration guide most of the articles about this are linking to.
https://gjs.guide/extensions/upgrading/gnome-shell-45.html#extensionutils
This is not an area I'm familiar with.
https://debugpointnews.com/gnome-extensions-break/
https://news.itsfoss.com/gnome-45-extensions/
So, as of now my project is not usable in a Wayland session with the GNOME 45 beta, because none of the compatible extensions have been updated yet.
Seems like quite a high percentage of the extensions I have installed are not yet scanning as compatible yet, so you're not alone.

@RedBearAK thanks! I'm not that familiar with JavaScript or GJS either, but the fix doesn't seem to hard. I'll try fixing it today.

@flexagoon
I can't be sure about the log() line, but otherwise I seem to have managed to get it working on the Fedora 39 beta VM. I left the original lines in as comments. There may be some things you'd want to do differently. I know there's a way to reload extensions after you change them, but I forget how to do it, so I was just logging out or rebooting every time I thought I might have made all the necessary changes. I was wrong several times. 💀
This in particular was just pulled from the porting guide without fully understanding why it's written that way, it's from one of their examples and probably needs modification:
// const ExtensionUtils = imports.misc.extensionUtils;
import {Extension, gettext as _} from 'resource:///org/gnome/shell/extensions/extension.js';

What I ended up with that works:
'use strict';

// const ExtensionUtils = imports.misc.extensionUtils;
import {Extension, gettext as _} from 'resource:///org/gnome/shell/extensions/extension.js';
// const Me = ExtensionUtils.getCurrentExtension();
import * as MyModule from './extension.js';
// const Gio = imports.gi.Gio;
import Gio from 'gi://Gio';

const DBUS_SCHEMA = `
<node>
    <interface name="org.gnome.shell.extensions.FocusedWindow">
        <method name="Get">
            <arg type="s" direction="out" name="window" />
        </method>
    </interface>
</node>`;

// class Extension {
export default class MyExtension {
    Get() {
        let window_list = global.get_window_actors();
        let focusedWindow = window_list.find(window => window.meta_window.has_focus());

        // Stolen from the "Window Calls" extension
        // https://github.com/ickyicky/window-calls/blob/b5ac7abe7e7acfcced75c5139824bd434d7c8f89/extension.js#L129
        let workspaceManager = global.workspace_manager;
        let currentmonitor = global.display.get_current_monitor();
        if (focusedWindow) {
            return JSON.stringify({
                title: focusedWindow.meta_window.get_title(),
                wm_class: focusedWindow.meta_window.get_wm_class(),
                wm_class_instance: focusedWindow.meta_window.get_wm_class_instance(),
                pid: focusedWindow.meta_window.get_pid(),
                id: focusedWindow.meta_window.get_id(),
                width: focusedWindow.get_width(),
                height: focusedWindow.get_height(),
                x: focusedWindow.get_x(),
                y: focusedWindow.get_y(),
                focus: focusedWindow.meta_window.has_focus(),
                in_current_workspace: focusedWindow.meta_window.located_on_workspace(workspaceManager.get_active_workspace()),
                moveable: focusedWindow.meta_window.allows_move(),
                resizeable: focusedWindow.meta_window.allows_resize(),
                canclose: focusedWindow.meta_window.can_close(),
                canmaximize: focusedWindow.meta_window.can_maximize(),
                maximized: focusedWindow.meta_window.get_maximized(),
                canminimize: focusedWindow.meta_window.can_minimize(),
                display: focusedWindow.meta_window.get_display(),
                frame_type: focusedWindow.meta_window.get_frame_type(),
                window_type: focusedWindow.meta_window.get_window_type(),
                layer: focusedWindow.meta_window.get_layer(),
                monitor: focusedWindow.meta_window.get_monitor(),
                role: focusedWindow.meta_window.get_role(),
                area: focusedWindow.meta_window.get_work_area_current_monitor(),
                area_all: focusedWindow.meta_window.get_work_area_all_monitors(),
                area_cust: focusedWindow.meta_window.get_work_area_for_monitor(currentmonitor)
            });
        } else {
            throw new Error('No window in focus');
        }
    }

    enable() {
        this._dbus = Gio.DBusExportedObject.wrapJSObject(DBUS_SCHEMA, this);
        this._dbus.export(Gio.DBus.session, '/org/gnome/shell/extensions/FocusedWindow');
    }

    disable() {
        this._dbus.flush();
        this._dbus.unexport();
        delete this._dbus;
    }
}

function init() {
//    log(`initializing ${Me.metadata.name}`);
    log(`initializing ${MyModule.metadata.name}`);
//    return new Extension();
    return new MyExtension();
}

@RedBearAK thanks! Can you create a pull request so that I could merge your changes? Also, does the changed code continue to work on GNOME 44?

@flexagoon
I think because of the fundamental nature of the change that separate versions of all extensions have to be uploaded for pre-45 GNOME and GNOME 45 or later. But I didn’t get into how that is done.

@flexagoon
Every source I've seen (including the porting guide) says that the only way to do the transition is to create a separate upload to the extensions site.
Seems like a good idea to create a new branch here (like pre_GNOME_45) to pin the state of the extension that works with GNOME 44 and earlier, in case you need to fix something in that branch and make a new version to upload after the main branch becomes GNOME 45+ only.
Not sure how else to manage the transition, besides keeping archival copies of the older version of the extension. I would not want to lose access to the earlier versions. A number of distros are very slow to move to new GNOME releases. I expect some distros like RHEL/AlmaLinux or openSUSE Leap/SLES to take anywhere from 2 to 4 years to finally get on GNOME 45.

@flexagoon
Submitted tested changes as PR #4. Only apparent issue is nothing coming out in the journal for the log line.

Thanks! I submitted the version with your fixes for review
https://extensions.gnome.org/review/45373

@flexagoon
I appreciate your time. Your extension may end up being the first of the three that make my project usable in GNOME to be compatible with GNOME 45. Only a little over half the extensions I use are now scanning as supported. An improvement from a week ago, but things are moving slowly and some distros are already jumping onto the GNOME 45 release. (Arch, Tumbleweed, some distro betas like Fedora 39.) So this will be nice to have available.

I'll close this issue once it gets approved.

That was my plan as well. Extension Manager should let me know, though I suppose you'll get an email or something when it gets accepted.

@RedBearAK

Only a little over half the extensions I use are now scanning as supported

I just checked and there are only two extensions I'm using which don't have GNOME 45 support yet. One of them (Run Or Raise) is working on it. The other though, Rounded Window Corners doesn't have any recent commits at all, and I really hope it'll get updated, because it's such a significant UI improvement imo

some distros are already jumping onto the GNOME 45 release. (Arch, Tumbleweed, some distro betas like Fedora 39.)

I don't know about other distros, but the planned release date for Fedora 39 is in a month, so I guess there still is some time

That was my plan as well. Extension Manager should let me know, though I suppose you'll get an email or something when it gets accepted.

Yes, I will get an email

@RedBearAK the new version was rejected with the following comment:

Please remove line 76-80. Not needed anymore.

Please use non generic names for the class you are exporting for back tracing (line 13).

Alright, I fixed the issue in https://github.com/flexagoon/focused-window-dbus/commit/89ab6fc80ff3ca3eccd666086bc785e0735d028e, I'll submit the extension again now

@flexagoon

planned release date for Fedora 39 is in a month

Yes, but some have been upgrading to the beta for a while now even before the beta was officially announced, and raving about it on the Fedora subreddit daily now that the beta is out. With GNOME 45 being a primary motivator for jumping into it so early.

Alright, I fixed the issue in 89ab6fc, I'll submit the extension again now

Wondered about that class name, but I didn’t want to go too crazy changing things.
Interesting that the init is not necessary anymore.

Done!
https://extensions.gnome.org/extension/5592/focused-window-d-bus/
Thank you @RedBearAK for your contribution! 🤍

@flexagoon
Fantastic. Thanks for being responsive to updating it.


Feat: changing the filter position

Describe the feature
i want to add the filter section in the right of the search bar to look it more clean and modern
assign this task to me under gssoc
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I want to work on this issue please assign me

I'd like to work on this issue can you pls assign to me


English language is not reflecting for wallet page

Current Behavior

The error msg showed in DE instead of EN
Expected Behavior

The error msg should be in selected language
Steps To Reproduce

Hi @anjuchaurasiya as far as I see on the screenshot everything is in English, for instance "Unknown", "Not Connecet". Could you please highlight more where English Language is not reflected?

Hi @evegufy ,
Thank you for looking into this. The msg below "My Company Wallet" seems in a diff language. That was my concern.

Hi @anjuchaurasiya as Lorem Ipsum isn't a different language, see https://en.wikipedia.org/wiki/Lorem_ipsum, I'll go ahead  with closing the issue, thank you for being so attentive!


Adding a cooldown timer

It would be nice to add a cooldown timer to the bot to help with users spamming the command on reddit.

I added a cool down this morning based on some suggestions on reddit. Do you think we can improve on this?


Duplicate word on README

Description
There is a typo in the README, the duplicate word in the design guidelines bullet point.
Acceptance Criteria
Update [Required]

[ ] Remove duplicate Contributing word from Design guidelines on README

Definition of Done

[ ] All of the required items are completed.
[x] Approval by 1 mentor.

Estimation

0.5 hours

Hi, i would like to work on this issue

sure will assign to you @himanshu007-creator


[BUG] Babel aliases do not work in non-Babel environments

Describe the bug
Refine defines several Babel aliases in its distribution in .babelrc:
{
    "plugins": [
        [
            "module-resolver",
            {
                "root": "./",
                "alias": {
                    "@components": "./src/components",
                    "@containers": "./src/containers",
                    "@pages": "./src/pages",
                    "@contexts": "./src/contexts",
                    "@dataProviders": "./src/dataProviders",
                    "@hooks": "./src/hooks",
                    "@test": "./test",
                    "@definitions": "./src/definitions"
                }
            }
        ]
    ]
}

These aliases do not get resolved in any non-Babel environment, like Vite, leading to errors.
To Reproduce
Steps to reproduce the behavior:

Initialize a new Vite project with React and TypeScript with npm init vite@latest (https://vitejs.dev/guide/#scaffolding-your-first-vite-project).
Follow first steps on Refine tutorial (https://refine.dev/docs/) until just before "Adding resources" chapter.
Run npm run build
Observe errors in the console like ERROR(TypeScript)  Cannot find module '@components' or its corresponding type declarations.

Expected behavior
Should work with Vite just like it does with create-react-app.

Hey @rassie ,
Thanks a lot for the issue. I'll see what we can do!

Hey @rassie,
We released v3.2.4! You can check out refine vite example in here. If you have a problem your project, feel free to write.

Thanks! Will be testing in the next couple of days.


Configurable max_retry_count

For #81
Allows for configuring a global max_retry_count with:
config :verk,
  max_retry_count: 1

Or when the job is added:
Verk.enqueue(%Verk.Job{ queue: "queue", jid: "job_id", class: "TestWorker",
      args: 123, max_retry_count: 10 })

But otherwise continues to default to 25

Changes Unknown when pulling 2b42235a1eda9d9b1f61af9d80e08c9a24f84e84 on mitchellhenke:retry-count into ** on edgurgel:master**.

Changes Unknown when pulling 8f648b57182e800df08089d0d49d9e21700a80ec on mitchellhenke:retry-count into ** on edgurgel:master**.

Other than the minor comment I did, LGTM! Thanks :)

Changes Unknown when pulling b47db85990c3cb0485403ed0f8447941a12716e0 on mitchellhenke:retry-count into ** on edgurgel:master**.

Thanks! I will release a new version soon 🎉

https://github.com/edgurgel/verk/releases/tag/v0.13.1 🎉
Thanks!

Absolutely, happy to be able to add something :)


Create Network Dataset in 10.5 - The row contains a bad value. [RestrictionType]

I have downloaded and converted the .pbf file from here in an attempt to create a network dataset from the entire country of Australia: http://download.geofabrik.de/australia-oceania/australia.osh.pbf
Loading the OSM file works fine, but when creating the network dataset, the error that comes up is:
The row contains a bad value. [RestrictionType]
at ESRI.ArcGIS.Geodatabase.IFeature.Store()
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkTurns.CreateTurnFeature_NO(TurnFeatureClassWrapper turnFCW, OSMTurnInfo osmTurn)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkTurns.PopulateTurnsFromRelations()
at ESRI.ArcGIS.OSM.GeoProcessing.RunTaskManager.ExecuteTask(String messageName, Action task)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkTurns.ExtractTurnRestrictions()
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.ExtractTurnRestrictions()
at ESRI.ArcGIS.OSM.GeoProcessing.RunTaskManager.ExecuteTask(String messageName, Action task)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.CreateNetworkDataset()
at ESRI.ArcGIS.OSM.GeoProcessing.OSMGPCreateNetworkDataset.Execute(IArray paramvalues, ITrackCancel TrackCancel, IGPEnvironmentManager envMgr, IGPMessages message)
Failed to execute (OSMGPCreateNetworkDataset).
Is there a way to view the relations so I can find the row with the bad value and exclude/fix it somehow? From what I read at https://github.com/Esri/arcgis-osm-editor/wiki/Tools#Load_OSM_File, "Relations are stored as a standalone table in the geodatabase and are currently not exposed to you." so it seems like I'm a little stuck.
I have completed this process successfully on the entire NZ dataset, so I would think there are just some bad records, but unfortunately I seem to have no way to find them.

That tool assumes you have used the "Load OSM File" tool to create your File Geodatabase, as that tool loads all the required information to create a network dataset. Since it can only process OSM XML files, I am unsure how you loaded the PBF. Note, that you cannot use the newer "OSM File Loader (Load Only)" tool that supports multi-core processing, as that tool doesn't load all the required data for creating networks.

Thanks for the reply, mboeringa. I see I missed a step - I use Osmconvert to turn the PBF into an OSM file. I ended up solving the problem by deleting the table causing the error from the geodatabase and re-running the tool. That means (I assume) that all of the restrictions and such aren't in my network, but it was closer enough for my purposes.
I think this issue can be closed as it's not really an error with the tool - I'm a bit of a newbie and I didn't realise that I really would need to do more cleaning up before actually using the map for a network dataset.


[SPARK-30199][DSTREAM] Recover spark.(ui|blockManager).port from checkpoint

What changes were proposed in this pull request?
This PR aims to recover spark.ui.port and spark.blockManager.port from checkpoint like spark.driver.port.
Why are the changes needed?
When the user configures these values, we can respect them.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the Jenkins with the newly added test cases.

cc @dbtsai

Test build #115087 has started for PR 26827 at commit 771ac88.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19902/
Test PASSed.

Test build #115089 has started for PR 26827 at commit cfa7494.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19904/
Test PASSed.

Hi @dongjoon-hyun, Can you please explain, how it is useful to recover these port numbers from checkpoint. As these can be picked up from configuration, and may not always be desirable to be picked from checkpoint. For instance the ports availability change between the two runs.

Test build #115087 has finished for PR 26827 at commit 771ac88.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115087/
Test PASSed.

Test build #115089 has finished for PR 26827 at commit cfa7494.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115089/
Test PASSed.

Thank you for review, @ScrapCodes . This PR aims to keep only user-given port numbers like spark.driver.port. You can see the UT about that.

As these can be picked up from configuration, and may not always be desirable to be picked from checkpoint. For instance the ports availability change between the two runs.

Hi, @jerryshao . Could you review this PR? This is basically the same with your spark.driver.port PR (#5060)

The fix LGTM.

Thank you so much, @jerryshao !

Merged to master.


Documentation site domain appears to have been taken

Just posting for awareness. Might make sense to remove links to it, or find a new place to host the docs assuming that can't be reclaimed.
Also having used the docs a few times, kudos on them! They were quite good.
https://owner.aeonbits.org/

Hi
I'll move all documentation on a new site.
The problem is that I have not access to aeonbits.org
ciao
matteo

Hi
I have moved all documentation here
https://matteobaccan.github.io/owner/
ciao
matteo


hdfview: 3.2.0 -> 3.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/hdfview/versions.
meta.description for hdfview is: A visual tool for browsing and editing HDF4 and HDF5 files
meta.homepage for hdfview is: https://portal.hdfgroup.org/display/HDFVIEW/HDFView
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.3.0 with grep in /nix/store/9iigglj7lialxkqydvamdmgna2i4karl-hdfview-3.3.0
found 3.3.0 in filename of file in /nix/store/9iigglj7lialxkqydvamdmgna2i4karl-hdfview-3.3.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
hdfview

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9iigglj7lialxkqydvamdmgna2i4karl-hdfview-3.3.0 \
  --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 hdfview https://github.com/r-ryantm/nixpkgs/archive/3cb838ccbb9d08c9e2dd718d1955a7205d6f19b1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9iigglj7lialxkqydvamdmgna2i4karl-hdfview-3.3.0
ls -la /nix/store/9iigglj7lialxkqydvamdmgna2i4karl-hdfview-3.3.0/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

1 package built:

hdfview

Maintainer pings
cc @jiegec for testing.

Additional patch is required for darwin: https://github.com/NixOS/nixpkgs/commit/01b2b96a1d51c4c21fb64cdf94ef9c0014b1d6b4

@ofborg build hdfview hdfview.passthru.tests

Result of nixpkgs-review pr 229424 run on aarch64-darwin 1

1 package built:

hdfview


Multiple graphql stacks not building when similar naming is used

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.15.0
Amplify CLI Version
v12.10.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
When adding the multiple stack templates under the amplify/backend/api/<api_name>/stacks folder with the naming as <template_name>1.json,  <template_name>2.json, <template_name>3.json... etc. Only the last template file is being built under the cloudformation-template.json and all other template files are being ignored. All the templates file are being uploaded to the deployment S3 bucket.
This is due to the resource name being created under cloudformation-template.json does not have last numerical character.
Expected behavior
Amplify CLI should build and deploy all the stack templates under the amplify/backend/api/<api_name>/stacks folder.
Reproduction steps

Add GraphQL API to the application.
Add the template files under amplify/backend/api/<api_name>/stacks folder.
Name the files as <template_name>1.json, <template_name>2.json, <template_name>3.json... etc. For example, check1.json, check2.json and check3.json.
Run amplify build or amplify push.
The file cloudformation-template.json file under amplify/backend/api/<api_name>/build/ would only have the reference to build the last template file under stacks folder.
Push will only deploy the last stack.

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
Workaround:
Use the different naming for the template files such as <template_name>one.json, <template_name>two.json, <template_name>three.json, etc...
This will build all the template files under stacks folder with different resource name and all the stacks would be deployed.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey  @snsarij👋 , Thanks for raising this issue. We are working on reproducing the issue. Could you please run below command and send us the project identifier.
amplify diagnose --send-report.
please refer here


R disabled by accident or temporarily?

I just initialized a new arbor instance 8/20/2015 and found out just now that R computation is gone.   I reprovisioned on 8/22 in case but same result.  Running an R script results in "invalid mode: r" error message.
Did I catch the master branch of tangelohub out of sync with the new romanesco architecture?  I'll try switching to the romanesco plug-in branch on romanesco and tangelohub.

Hi @curtislisle , this is due to a recent change in romanesco in which we created a plugin architecture within romanesco. R capabilities were moved within a plugin, so a little extra configuration needs to be done to get it enabled. I will update that in the ansible playbook this weekend.

@zachmullen, thanks so much for your quick answer and willingness to work on the playbook.  I will wait for the update, then plan to pull the update and reprovision my instance.  Glad I wasn't just going crazy :-)

Just realized I actually opened a PR to fix this issue at the same time I created the romanesco change:  #157 . It hasn't been officially QA'd yet, though. @curtislisle could you checkout that branch and rebuild the vagrant box and see if it fixes the problem?

I noticed the corresponding changes.  So I just check out the PR for tangelohub and the corresponding romanesco commit, right?  Will be glad to.

On Aug 22, 2015, at 6:10 PM, Zach Mullen<EMAIL_ADDRESS>wrote:
Just realized I actually opened a PR to fix this issue at the same time I created the romanesco change: #157 . It hasn't been officially QA'd yet, though. @curtislisle could you checkout that branch and rebuild the vagrant box and see if it fixes the problem?
—
Reply to this email directly or view it on GitHub.

Yep, that's correct. If that works, I will go ahead and merge #157.

I checked out the "support-romanesco-plugin-framework branch', performed an "npm instdall" in  /vagrant to rebuild the app, and then went to /vagrant/romanesco and performed a git pull to update romanesco, as well.  TangeloHub comes up but I still receive the "Invalid more: r" command when trying to run an R-based analysis.  Did I miss something?

It will require re-running vagrant provision from your host.

This worked and R is enabled again! Great!  Thanks for reminding me, reprovisioning failed the first time and I forgot about it by the time I fixed the issue, until your reminder.  So #157 works for me using this branch and the current head of romanesco  ( 8/27 9:03 AM commit c72fef48c3ffa32d5b6f19997519502b79d12f69)!


Why copy config.php to user during upgrade?

Hello,
your upgrade instructions Step 5 says "Tip: you can now move your config.php file to the /user directory"
It's unclear what is the purpose of this step, whether it is required, what the benefit is, and what are the drawbacks if i don't do it.
I also noticed that config.php is already in /user (from my existing installation), and there's no config.php at the root dir of the upgrade. What config.php are we talking about?
My upgraded install seems to be working fine.
Confused. Fyi, i'm going from 1.7.1 to 1.7.2
thx

Well, if your config.php is already in /user, then I guess you're all good, right? :)
This will be a concern for people whose config.php is not in /user, probably coming from a very old YOURLS version.


Question about Swagger support

Hello,
In this project is using package Swackbucle.AspNetCore 1.0.0 for swagger implementation. But when I open the http://swagger.io site and download server side example for .Net core the packages which are included are Swashbuckle.SwaggerGen (>= 6.0.0-T2016120822) and Swashbuckle.SwaggerUi (>= 6.0.0-T2016120822) - (NOT Swackbucle.AspNetCore 1.0.0)
In packages description looks like that them support .Net Core and .Net standard v1.6.
What is the different between current package in use and these new packages v.6.0.0. What of them is better to be used in the future? I suppose that swagger team with continue with 6.0.0 support. What do you think about this?
Thank you

It hasn't been updated in quite a while here but of course it'd be best for us to use the latest and greatest swagger!
If you're able to get it working with the latest and have the time to get a pull request in to update it here it'd be very helpful for anyone using the repo! Let me know 👍@gettaxsolutions

Ok, We already tested with the last packages and looks ok. Will create branch and pull request to take a look.

@GetTaxSolutions do a fork and open a PR and we will review

Seeing the PR I don't think it is correct to use:
<PackageReference Include="Swashbuckle.SwaggerGen" Version="6.0.0-beta902" />
<PackageReference Include="Swashbuckle.SwaggerUi" Version="6.0.0-beta902" />

Instead of:
<PackageReference Include="Swashbuckle.AspNetCore" Version="1.0.0" />

See README.md on top of this Github repository - domaindrivendev/Swashbuckle. The owner redirects us to his other Github repository - domaindrivendev/Swashbuckle.AspNetCore
Also look at the most recent contributions to both repositories:
Swashbuckle = 15th September 2017
Swashbuckle.AspNetCore = Today
Swashbuckle.AspNetCore is definitely the way to go.


 Is there a better workaround than giving the optional vertical shift to the \sidecite command. I do not like the vertical shift because you might have an other overlapping with an other citation afterwards...
I also approve of the suggestion #216 that could lighten the content of the side margin, and reduce the susceptibility of overlapping issues.

The code referenced in #216 may help to fix this issue too.  If I am not wrong, it keeps track of the position of the last content on the sidebar, so that the next content can be added after it.


Cannot locate symbol on Samsung jfltexx

Fun with Samsung devices: I got this error report from a user of StreetComplete with a samsung jfltexx device, Android 4.4.4, using tangram-es 0.7.2.
Stack trace:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "" referenced by "libtangram.so"...
at java.lang.Runtime.loadLibrary(Runtime.java:364)
at java.lang.System.loadLibrary(System.java:526)
at com.mapzen.tangram.MapController.<clinit>(MapController.java:1097)
at com.mapzen.tangram.MapView.getMapInstance(MapView.java:107)
at com.mapzen.tangram.MapView.getMapAsync(MapView.java:77)
at com.mapzen.tangram.MapView.getMapAsync(MapView.java:61)
...

Line 1097 for tangram-es 0.7.2 is this:
1095  static {
1096    System.loadLibrary("c++_shared");
1097    System.loadLibrary("tangram");
1098  }

Not sure how helpful this stack trace is. What I read from that is that somewhere inside the C++ code, a symbol is not defined for the given device, but doesn't say which symbol.
Feel free to close this report if you can't act on it due to a missing test device. I notified the user via email that I opened this ticket, perhaps he can answer questions that you may have.

Thanks @westnordost
As you mentioned its a hard one to track because we can not get our hands on this rare (:D) device.
Closing for now, let us know if you hear more noise on this. Thanks


Validate that $dockerComposeFile is correct if config_path is not the default path

The Variable $dockerComposeFile is set In the method _init_vars in abstract_config.py. But it is set to the value of config_path wich doesn't seem to make sense.

This shouldn't be needed when #31 is implemented.


error: name 'np' is not defined

I tried one of the example from crawl4ai documentation
https://crawl4ai.com/mkdocs/full_details/extraction_strategies/
from crawl4ai.extraction_strategy import CosineStrategy
from crawl4ai import WebCrawler

crawler = WebCrawler()
crawler.warmup()

# Define extraction strategy
strategy = CosineStrategy(
    semantic_filter="finance economy stock market",
    word_count_threshold=10,
    max_dist=0.2,
    linkage_method='ward',
    top_k=3,
    model_name='BAAI/bge-small-en-v1.5'
)

# Sample URL
url = "https://www.nbcnews.com/business"

# Run the crawler with the extraction strategy
result = crawler.run(url=url, extraction_strategy=strategy)
print(result.extracted_content)

however, error accour
LOG] 🚀 Initializing LocalSeleniumCrawlerStrategy
[LOG] 🌤  Warming up the WebCrawler
Error retrieving cached URL: no such column: links
[LOG] 🌞 WebCrawler is ready to crawl
Error retrieving cached URL: no such column: links
[LOG] 🚀 Crawling done for https://www.nbcnews.com/business, success: True, time taken: 2.4808032512664795 seconds
[LOG] 🚀 Content extracted for https://www.nbcnews.com/business, success: True, time taken: 0.2220618724822998 seconds
[LOG] 🔥 Extracting semantic blocks for https://www.nbcnews.com/business, Strategy: CosineStrategy
[ERROR] 🚫 Failed to crawl https://www.nbcnews.com/business, error: name 'np' is not defined
None

I dont know where the error coming from, np usually related to numpy.

@trimbilrepo If you wanna use Cosine strategy, please install Crwl4ai in this way pip install "crawl4ai[torch] @ git+https://github.com/unclecode/crawl4ai.git"


Error in loading state_dict for DiffVAE

First of all, thank you for your wonderful study in molecular generation.
I am learning a lot from your research.
When I try testing process like below figure, error in loading state_dic was occurred.
(same problem: model.iter-5 in logp04, logp06 in diff_vae, model.iter-3 in qed in diff_vae_gan, etc.)
Is there any solution to this problem?
I'll wait your help.
Thanks.

Sorry for my late reply. Please run the script with --hidden_size 330


Feature Request: Row Action Events

Hello, is there any plan to add row operation events? For example, long press, click, that is, GestureDetector function is put into the row?

At this moment, you can listen when a row changes. Also, you can select the row and get the list of selected rows. Currently, there is no plan for row action events, like a GestureDetector in the row. The way paged_datatable is built makes it a little bit difficult to "just put a GestureDetector" and also I'm working on collapsible/expansible rows, so, after that feature is ready, I can consider start working on this issue, so I'll keep this opened.

The existing function is to select through the selection box and then operate. But there is no way to directly perform it by long pressing, etc. Maybe I can submit a PR for reference.

I'm not thinking about how to implement this because a long press would be possible but without an ink splash, due to how paged_datatable implements fixed columns.


debug.inlineValues does not appear to honour line/column information from scope

I'm trying to improve the display of debug.inlineVariables for Dart. I saw that would code provide Source and line/column information for a Scope to control where the inline values would appear, but it seems to be ignored in my testing.
I've hard-coded some values from line 6-11:

But when I run, I still see the inline values outside of that range:

As far as I remember we decided to ignore stack frame ranges for inline sources and hover since the stack frame ranges were quite incorrect for node.
Here's a code pointer
https://github.com/Microsoft/vscode/blob/e2027598992e56d7f6f6f26f804d53449ea1a2ee/src/vs/workbench/parts/debug/electron-browser/debugEditorContribution.ts#L618
PR that fixes this would be welcome.
The PR would only change the behavior for inlineValues, not for debug hover (due to some other closed issues which I do not want to dig out)

@isidorn I don't entirely understand what you mean. The code you linked looks like it is filtering based on ranges, so what needs fixing?
(I was under the impression that these fields were added specifically to support inline debugging so I'm wondering if I've misunderstood something, or implemented it incorrectly?)
Also:

we decided to ignore stack frame ranges for inline sources

What do you mean by "inline sources"? These are files on disk - my mapToSource function is returning sources with paths - but it's possible I'm doing that wrong. If you think it should work for sources-on-disk lmk and I'll check I'm not doing something wrong in there.


$httpBackend does not respond to request when asynchronous beforeEach is used

If asynchronous beforeEach in jasmine is used (via the parameter done) requests are not responded to. This test timeouts:
      describe('Fails', function() {
        beforeEach(function(done) {
          $timeout(done, 10);
        });
        it('should work', function(done) {
          $httpBackend.expectGET('url').respond();
          $http.get('url').then(done);
          $httpBackend.flush();
        });
      });

If whole the beforeEach part is ommited the request is responded to.
Here is a plunker http://plnkr.co/edit/dwe57Y21wBXcXiXU1Cqq
with jasmine 2.3.4 and angular 1.5.0-beta.1

Trying using the done in your describe instead of your beforeEach. Once that done is finished the tests are ready to be run, so it should run correctly.
      describe('Fails', function(done) {
        beforeEach(function() {
          $timeout(done, 10);
        });
        it('should work', function(done) {
          $httpBackend.expectGET('url').respond();
          $http.get('url').then(done);
          $httpBackend.flush();
        });
      });

describe does not pass done. When changed as described in plunker both the test pass but it is only because they become same - synchronous.

I see. I'm not sure what the Jasmine support for $timeout is, but setTimeout works fine with your updated plunk in the first post.

I found the problem. The second test was actually never run because the $timeout in the beforeEach section was not flushed.
This is the proper way.
      describe('Fails', function() {
        beforeEach(function(done) {
          $timeout(done, 10);
          $timeout.flush();
        });
        it('should work', function(done) {
          $httpBackend.expectGET('url').respond();
          $http.get('url').then(done);
          $httpBackend.flush();
        });
      });

And it works ok
Please mark as Solved

:+1:

Glad you got is solved. You can also close your own issues!


h1 is close to navbar

h3's should be used for titles: https://github.com/Silox/Eddy/blob/master/app/assets/stylesheets/application.scss#L7


Netlify for officialexample

Issue: Netlify example was missing for newly added official storybook example
What I did

Added a netlify site
Added a if case for the pre-defined environment variable to deploy the right example

Works: https://5a3cfb970b79b765073bb74f--storybooks-official.netlify.com/


Make tests more DRY

There are tests, other code in qiita_db/test/test_meta_util.py, etc. that are of the form:
With TRN:
sql =
results = execute(sql)
return results
or similar. This could be wrapped in a util function that reduces the amount of code repeats.

In case it helps, currently there are 171 occurrences of TRN.execute() in 45 files.


Do not set (mongo cursor's) limit to 0 when before offset cursor's value is 0

[X] Includes test to verify the same
[ ] Same for aggregates

Updated the test. Problem here is that if before offset's value is 0, the mongo cursor's limit gets set to 0.

I think the bug is here
https://github.com/entria/graphql-mongoose-loader/pull/35/files#diff-53722dc92b9e827b5e93d11c4f7bd0a3R82
we should split first and last check
if there is no first or last both should be 10
what do you think?

I have updated the code, and the test. But it's still failing:
https://asciinema.org/a/CvvqxqMmiKtv9pALMEDb5xnjp


update raiwidgets and responsibleai to erroranalysis 0.4.2

Description
Update raiwidgets and responsibleai to erroranalysis 0.4.2
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[x] Documentation was updated if it was needed.

Codecov Report

Merging #2001 (0d25eb7) into main (c9a02a5) will increase coverage by 93.63%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           main    #2001       +/-   ##
=========================================
+ Coverage      0   93.63%   +93.63%
=========================================
  Files         0       31       +31
  Lines         0      581      +581
=========================================
+ Hits          0      544      +544
- Misses        0       37       +37

Flag
Coverage Δ

unittests
93.63% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 31 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Mutated ArrayList for "five"

Summary
Description:
In order to keep track of all the outputs to map, I decided to use ArrayList containing suppliers to the values. For example, in level 1, five would contain an ArrayList list containing () -> 5 (with 5 being a String). After mapping five(map(x -> x + 1), the list would contain () -> 5 and () -> 6.
I planned to loop through the list from index 1 onwards to show the mapping of the output. However, I do not quite understand how five 's list mutated, considering my map method returned a new Logger.
Code Snippets
<R> Logger<R> map(Function<? super T, ? extends R> mapper) { R r = mapper.apply(this.get()); return new Logger<R>(() -> r, this.list, () -> String.format("%s", r));}
Screenshots
Screenshots (if any

)

I suggest to not add elements to the existing ArrayList but instead add all the contents of the ArrayList + this new log into another ArrayList. Concept of immutability, I suppose.

I suggest to not add elements to the existing ArrayList but instead add all the contents of the ArrayList + this new log into another ArrayList. Concept of immutability, I suppose.
Update: oh you added a code snippet, I'll update my comments later

It appears I briefly forgot about that concept. I decided to append the elements of this.list into a new one, followed by the supplier to be added in as well. I shouldn't have mutated my this.list in my constructor as much as possible.
Thanks, Russell!


Importer for Biobakery outputs: MetAPhlAn3

Data importer for MetaPhlan outputs, to (Tree)SE format, is missing and could be implemented to mia.
Here is metaphlan to phyloseq import function from @lwaldron
Some more examples here and here.
It should be relatively straightforward to implement a similar one for TreeSE.
Some example data is on the way, for a closer look.

So this is different than https://github.com/microbiome/mia/pull/178?

No I think it's the same :DDD

Easiest issue ever :D


Improve FermionicOp and SpinOp

Summary

Fix the but about an empty string (FermionicOp("") is not allowed now.)
Improve test with assertFemionEqual
~Deprecate initialization with tuple (FermionicOp(("I+", coeff))). Users should use coeff * FermionicOp("I+") or FermionicOp([("I+", coeff)]) instead.~
Support sparse label for FermionicOp
Sparse label requires register_length.
Make internal FermionicOp._coeff_list np.ndarray
~Implement FermionicOp.to_normal_order_list()~ Move to #88.

In regards of 3 above, often we have APIs that take a List[x] (where x in this case is a Tuple[str, complex]) and to simplify things for a user, where they have only one element, so they do not have to make a List to pass it in, we support x directly as a type. In this case you had that and have removed it. Instead requiring the user to make it into a List or to break the Tuple apart to use a different style to initialize it where presumably by passing a str the coeff is implied to be 1 and then multiply it afterwards. Having it support the Tuple directly seems consistent with the usability we do elsewhere. What is the reason to remove it?

Thanks. For 3, I thought it is just adding square brackets to make a list. The reason for deprecating it is that it would be confusing if there were various initialization methods, and I wanted to save tuple for initializing directly from internal data in the future. Of course, this (latter) isn't necessary because we can detect the type from the element of tuple. If you want to use Tuple[label, coeff], I will revert it.

FYI: In commenting on unit test above I will note that in #60 I added a unit test for qubit_converter, which is in operators/second_quant.. and in doing so I created second_quant... folder in that PR and moved the 2 existing unit tests there (which includes the one modified here). That PR is not yet merged so we will have to reconcile things between these.

Please merge this PR if normal_order_list() is ok because this PR blocks other PRs. I will add additional tests and improvement of error messages in follow up PR.

Please merge this PR if normal_order_list() is ok because this PR blocks other PRs. I will add additional tests and improvement of error messages in follow up PR.

I understand you want to get this out. But, let us wait for the offline decision with regards to the endianess convention.
Which PRs are blocked by this one? I just closed the p/h transformer and I know that VibrationalProblem needs this. Anything else?

Yes. PH and VibrationalProblem.

Warning: the sparse labels are still using little endian. A follow-up PR will fix this!

Dense label is also little endian now. I've implemented all operators as little endian from #25 and #35.

Anyway thanks a million. @mrossinek

Dense label is also little endian now. I've implemented all operators as little endian from #25 and #35.

Interesting I had not noticed.. I would have assumed that the mapper unittests would fail in this case :thinking:
But let's still proceed for now. The switch to big endian should follow-up early this week anyways :+1:

Sorry. I was wrong. #25 does not assume endian (endian does not influence) and #35 is little e.g. https://github.com/Qiskit/qiskit-nature/pull/35/files#diff-e1fad0f243ef03387da83f3f9c9b006212b413a01addd08569d3d78048469dd1R131-R132.

I think now this LGTM. We need to add the normal ordering in a different PR for future reference and resolve the big endian discussion we had offline (different PR)


[terraform] Limit container log size

The default json-file log driver has no size limit. Set some.
Test Plan: Deployed to mgorven workspace, inspected containers to check that log config was present.

:hourglass: Testing commit a55897242a66264db1837e5fedb06ecce60e8119 with merge 730398176f421670129f847c9b72eacd58e799ef...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: sherry-x
Pushing 730398176f421670129f847c9b72eacd58e799ef to master...


[FEATURE] Hang up/stall detection.

Currently ripme will still become locked up on certain reddit users post histories.  Would you be able to add some sort of detection that would notice ripme was stuck attempting to download some files.
Once detected a STOP and RIP command could be sent to stop the current rip and to than continue on with the history skipping the current user that locked everything up.
Possibly add a variable for users to edit to decide how long they want to before moving on.
This is not a timeout detection as I am fairly certain ripme already has timeout detection.
Win10 64 build 19041.450
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)

What OS are you running?

win10 64 home.
This hang up on reddit has been around for a while, some of it was caused by RIPME trying to save filenames that were above its character limit, I tracked that down and reported it and that was fixed.
Something else is still causing the program to hang as it waits for files which never come.

Can you post a url that triggers the lock up?

I posted about this same issue with details in #1017

I'll run my entire history and post problem users.

This post is one that causes a hang due to IO bad file path
https://www.reddit.com/r/HugeDildos/comments/ixf6oh/now_you_see_it_now/


Fix celocli accounts:proof-of-possession command

Description
When trying command celocli accounts:proof-of-possession, celocli reports that it does not exists..
I think it should be celocli account:proof-of-possession instead
Tested
celocli account:proof-of-possession works
Commit Message
Fix typo in  celocli accounts:proof-of-possession command

Thanks @sharppanda! Looks like there's a merge conflict so merging this fix in https://github.com/celo-org/celo-monorepo/pull/3479


Support Safari 12.1, fix canvas leak, and improve recognition

https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/srcObject
On Safari 12 (and indeed later verisons of other browsers), the video.src = URL.createObjectURL(mediaStream); syntax is deprecated. Instead, it's
been replaced by video.srcObject.
However, using the srcObject syntax also lead to hundreds of individual canvases
being created in Safari 12.1. This used lots of memory, slowing the app, and
Safari then stopped the website from creating further canvasses and scanning
failed to work. The longer the video preview was open the worse things became.
This version of the code now uses a single canvas for rendering, rather than
relying on garbage collection to clean them up over time.
Additionally, Safari requires a new playsinline attribute for the display
element in the html.
Additionally, I found that on Safari 12.1 with an iPhone 6s plus, the generated
image was vertically squished, and the bar-code wouldn't be recognised as it
was not square. This changes the code to use the rendered window size for the
canvas, rather than what the camera has been detected as. This seems to
dramatically improve QR code recognition.

Based on work done in https://github.com/bitpay/cordova-plugin-qrscanner/pull/164  - thanks!

Example where the image is squished

Heya @bitjson
Not sure if you've seen this yet. Would you let me know your thoughts?
Thanks!

Any update on this? @bitjson


Is it possible to insert a node?

I know this project has been updated for a while... but I still want to see if anyone knows if I can insert a node?

If you use a MutableVisitor you can insert a child node on a parent

If you use a MutableVisitor you can insert a child node on a parent

Thanks it works for me.


[Bug]: Error building OpenSearch: Expected to have Implementation-Version=any of [None, '<IP_ADDRESS>', '1.2.2'], but was '1.2.3'

Describe the bug
Can't build opensearch 1.2.2 from source
To reproduce
$ git clone https://github.com/opensearch-project/opensearch-build.git
$ git checkout opensearch-1.2.2
$ docker build -f docker/ci/dockerfiles/ci-runner.centos7.dockerfile -t opensearch-1.2.2-build .
$ docker run -it --rm -v $(pwd):/project -w /project opensearch-1.2.2-build bash
$ ./build.sh manifests/1.2.2/opensearch-1.2.2.yml
...
2021-12-22 12:48:02 ERROR    Error building OpenSearch, retry with: ./build.sh manifests/1.2.2/opensearch-1.2.2.yml --component OpenSearch
Traceback (most recent call last):
  File "/tmp/opensearch/src/build_workflow/opensearch/build_artifact_check_maven.py", line 41, in check
    properties.check_value_in("Implementation-Version", versions)
  File "/tmp/opensearch/src/system/properties_file.py", line 57, in check_value_in
    raise PropertiesFile.UnexpectedKeyValuesError(key, expected, value)
system.properties_file.UnexpectedKeyValuesError: Expected to have Implementation-Version=any of [None, '<IP_ADDRESS>', '1.2.2'], but was '1.2.3'.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./src/run_build.py", line 78, in <module>
    sys.exit(main())
  File "./src/run_build.py", line 67, in main
    builder.export_artifacts(build_recorder)
  File "/tmp/opensearch/src/build_workflow/builder_from_source.py", line 60, in export_artifacts
    build_recorder.record_artifact(self.component.name, artifact_type, relative_path, absolute_path)
  File "/tmp/opensearch/src/build_workflow/build_recorder.py", line 40, in record_artifact
    BuildArtifactChecks.check(self.target, artifact_type, artifact_file)
  File "/tmp/opensearch/src/build_workflow/build_artifact_checks.py", line 42, in check
    instance.check(path)
  File "/tmp/opensearch/src/build_workflow/opensearch/build_artifact_check_maven.py", line 43, in check
    raise BuildArtifactCheck.BuildArtifactInvalidError(path, str(e))
build_workflow.build_artifact_check.BuildArtifactInvalidError: Artifact custom-settings-1.2.3-javadoc.jar is invalid. Expected to have Implementation-Version=any of [None, '<IP_ADDRESS>', '1.2.2'], but was '1.2.3'.

Expected behavior
Expecting to build opensearch as described in https://github.com/opensearch-project/opensearch-build/blob/main/README.md#building-from-source
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
Docker
Additional context
No response
Relevant log output
No response

I think the 1.2.2 tag was premature and should have included https://github.com/opensearch-project/opensearch-build/commit/7785777cfdcfb5ebbe05307919cbbccf5884d0bc which locked the manifest version(s) at the 1.2.2 tag. I'd rather not re-tag - does this work off main right now?

Thank you, will try. So, you proposing to build from main for next versions too?

Thank you, will try. So, you proposing to build from main for next versions too?

The 1.2.2 tag should have been stable, what you reported is, indeed, a bug.
You can (should be able to) currently build all versions of OpenSearch and OpenSearch Dashboards from main. Our CI does that.

Does this help?

No, I have another error on https://github.com/opensearch-project/opensearch-build/blob/main/docker/release/dockerfiles/opensearch.al2.dockerfile#L37 while building on main:
Step 10/33 : COPY * $TEMP_DIR
When using COPY with more than one source file, the destination must be a directory and end with a /

No, I have another error on https://github.com/opensearch-project/opensearch-build/blob/main/docker/release/dockerfiles/opensearch.al2.dockerfile#L37 while building on main:
Step 10/33 : COPY * $TEMP_DIR
When using COPY with more than one source file, the destination must be a directory and end with a /

I see TEMP_DIR=/tmp/opensearch, maybe that needs to be created if it doesn't exist?

No, this directory is already created and contains opensearch-build tree
Anyway adding / to $TEMP_DIR solves problem, can you fix this?

No, this directory is already created and contains opensearch-build tree
Anyway adding / to $TEMP_DIR solves problem, can you fix this?

Interesting!  How did this ever work before? This was added in https://github.com/opensearch-project/opensearch-build/issues/1154, cc: @peterzhuamazon
@enp You can also PR the change! Thanks.

No, this directory is already created and contains opensearch-build tree
Anyway adding / to $TEMP_DIR solves problem, can you fix this?

Interesting! How did this ever work before? This was added in #1154, cc: @peterzhuamazon
@enp You can also PR the change! Thanks.

As per online research, Docker version 18.09.0, build 4d60db4 and before does not support using wildcard with destination folder w/o /, which has since been patched so docker will auto detect whether destination is a file or dir.
We are using docker enginer Docker version 19.03.13-ce, build 4484c46 or above for our builds, thus does not have this issue with docker builds.
However, this can be easily addressed for older version user with appending slash to the end of the folder name.
Thanks.