Mass Storage mode doesn't exit on eject in Ubuntu 20.10

I don't know if this is just me but since updating to Ubuntu 20.10, Mass Storage doesn't exit when I "eject" the device. It seems to immediately go back to displaying "MSC mounting"/"MSC mounted" on the screen.
After ejecting sometimes the device shows up on Ubuntu as having no filesystem, sometimes the filesystem is there but not mounted.
Mostly submitting so that this is documented in case anyone else runs into it. (I can't really debug as Mass Stoarge mode causes my desktop to hang for a few seconds on mount)
(blank lines whenever I tried to eject)
[77460.930044] usb 1-4: new full-speed USB device number 94 using xhci_hcd
[77461.270791] usb 1-4: New USB device found, idVendor=0483, idProduct=572a, bcdDevice= 2.00
[77461.270794] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[77461.270795] usb 1-4: Product: 32Blit Mass Storage
[77461.270797] usb 1-4: Manufacturer: STMicroelectronics
[77461.270797] usb 1-4: SerialNumber:<PHONE_NUMBER>37
[77461.285817] usb-storage 1-4:1.0: USB Mass Storage device detected
[77461.285977] scsi host10: usb-storage 1-4:1.0
[77462.317303] scsi 10:0:0:0: Direct-Access     STM      32Blit SD        0.01 PQ: 0 ANSI: 2
[77462.317593] sd 10:0:0:0: Attached scsi generic sg4 type 0
[77462.317997] sd 10:0:0:0: [sde] 3911680 512-byte logical blocks: (2.00 GB/1.87 GiB)
[77462.318237] sd 10:0:0:0: [sde] Write Protect is off
[77462.318239] sd 10:0:0:0: [sde] Mode Sense: 00 00 00 00
[77462.318485] sd 10:0:0:0: [sde] Asking for cache data failed
[77462.318488] sd 10:0:0:0: [sde] Assuming drive cache: write through
[77462.384278]  sde: sde1
[77462.386053] sd 10:0:0:0: [sde] Attached SCSI removable disk
[77467.707943] FAT-fs (sde1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

[77485.414090] sd 10:0:0:0: [sde] Spinning up disk...
[77486.441897] .ready
[77486.459180]  sde: sde1

[77543.719653] sd 10:0:0:0: [sde] Spinning up disk...
[77544.745581] .ready
[77544.762706]  sde: sde1

[77568.920357] sd 10:0:0:0: [sde] Spinning up disk...
[77569.929462] .ready
[77569.946771]  sde: sde1

[77575.178915] usb 1-4: USB disconnect, device number 94
[77575.179157] sd 10:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[77575.179161] sd 10:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 3b ad 81 00 00 f0 00
[77575.179163] blk_update_request: I/O error, dev sde, sector 3911041 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0
[77575.179189] blk_update_request: I/O error, dev sde, sector 3911281 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[77575.179247] blk_update_request: I/O error, dev sde, sector 3911041 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
[77575.179251] Buffer I/O error on dev sde1, logical block 3910912, async page read
[77575.179254] Buffer I/O error on dev sde1, logical block 3910913, async page read
[77575.179255] Buffer I/O error on dev sde1, logical block 3910914, async page read
[77575.179256] Buffer I/O error on dev sde1, logical block 3910915, async page read
[77575.179257] Buffer I/O error on dev sde1, logical block 3910916, async page read
[77575.179258] Buffer I/O error on dev sde1, logical block 3910917, async page read
[77575.179259] Buffer I/O error on dev sde1, logical block 3910918, async page read
[77575.179260] Buffer I/O error on dev sde1, logical block 3910919, async page read

I get the same hang with Windows 10 using Mass Storage Mode. It's definitely a little quirky. I think I have 20.04 on my Linux desktop so I can try it there, too.

Hmm, eject works fine on a pi...

Seems eject is working fine again on 21.04. So maybe an Ubuntu/kernel bug?

... and not working again (same "Spinning up disk..."). Running 21.10 now. Wonder if it still works on the pi with bullseye...

Looks like #774 fixed this. (One of my blits was working and the other wasn't... so I bisected it to that change)


billing: Add removeBillingInfo method for removing billing info

billing: Add removeBillingInfo method for removing billing info
Connects-to: https://github.com/balena-io/balena-ui/pull/6042
Change-type: minor

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

LGTM


Clarify is_polygon_clockwise() coordinate system

The function assumes a normal Cartesian coordinate system.
Fixes #49716
Notes

Alternative would be to add a parameter to do the flip as in #89635, but that may be controversial, and is taking a while to be decided on, so this doc change will do the job either as the final solution, or until we decide on another solution.

Will likely be needed for older versions regardless of adding a handedness option down the line (and likely won't get into 4.3 anyway)

Thanks!


CB-11699 Read files as Data URLs properly

Platforms affected
Android, iOS, Windows
What does this PR do?
This PR fixes reading files as data URLs by modifying chunk size, so concatenated chunks would be a valid Data URL
What testing has been done on this change?
Ran plugin tests on all affected platforms
Checklist

[x] ICLA has been signed and submitted to<EMAIL_ADDRESS>[x] Reported an issue in the JIRA database
[x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[x] Added automated test coverage as appropriate for this change.

When reading file as Data URL, CHUNK_SIZE must be divisible by 3, otherwise the resultant string, made by concatenating chunks, will not be a valid Base64 encoded Data URL. Also Windows do not support reading sliced files as data URLs, so we need to set chunk size equal to file size.
Relevant JIRA issues: CB-11699, CB-11199

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

@daserge, @sgrebnov, please take a look
/cc @jasongin

Please do review this as the function does not work for files over a very small size.

can we expect a fix for this soon?

@Samaludheen, the fix has been released recently. Check out<EMAIL_ADDRESS>

@vladimir-kotikov Thank you a lot, your PR fixed exactly an issue I was facing today!


Merge pull request #2 from dblodgett-usgs/mj

merge conflict bringing over latest fix for #39

huh -- I guess this isn't needed.


Special view is nonsensical

Found in cadview. pressing 'a' will make the camera move to some random specific location that is inside of the model for boxy

Special view is actually a hard coded view for moldy that looks pretty good. Probably added because moldy's default view is the bottom. Mystery solved


bookmarklet version pls

minify or compile to bookmarklet pretty please :looks cutely*

i don't think what you're asking for is possible


Add support for pickled fields

Introduce a new special kind of fields that would let one transparently serialize and deserialize on-heap objects:
@data class Person(@pickle name: String)

Whenever a pickled field is written it would use an implicit serializer to convert objects to bytes and move those bytes to an off-heap array. Reading would materialize on-heap version on every access.
Serialisation mechanism is going to be based on implicit class that would make it easy to bridge to any serialisation framework user might want to use (e.g. scala.pickling, java serialization etc)
This partially addresses issue #15 as one would be able to define a string serializer that encodes string into UTF-8 sequence of bytes. Operations on those strings would materialize an on-heap version though.
/cc @velvia @phaller

Another alternative for the UI is to put pickles into some generic container type:
@data class Person(name: Pickle[String])

It would let one add extra functionality on Pickle[T] type but would make it a bit harder to use.

An interesting development in more or less this area: https://google.github.io/flatbuffers/

FYI I have a project to support fast Scala collections over FlatBuffers:  github.com/velvia/filo
-Evan
"Never doubt that a small group of thoughtful, committed citizens can change the world" - M. Mead

On Aug 10, 2015, at 5:39 AM, Denys Shabalin<EMAIL_ADDRESS>wrote:
An interesting development in more or less this area: https://google.github.io/flatbuffers/
—
Reply to this email directly or view it on GitHub.

People should use normal serialisation frameworks instead.


Update project to use the fully qualified name for JSON.NET

This is a potential fix for #28. I believe it's because a fully qualified assembly name isn't included in the Segment reference, so it will introduce issues if you add Segment to a project that also uses JSON.NET with a different version.
The code change is a result of running:
update-package -reinstall Newtonsoft.Json

+1


not clear that we have classic and native providers if folks first experience is starting out on an api docs page

overview
if folks first start out on an API docs page they may never see the note on the overview page that gives information about the native provider. we may want to consider having access to this information in the header so no matter what page of the package they are on they have access to this info.
original report from a user:
https://github.com/pulumi/registry/issues/547#issuecomment-1011361388

Design Goals
Users may be starting out on the API Docs page and miss the Azure Native provider info. banner that's currently located on the Overview page only. We want to design a way that the user sees this message no matter what page they are on.

Figma File
Engineer Notes

Move the Azure Native provider info. banner above the tabs and keep this banner in the same position on every page - so that no matter what page of the package the user is on, they have access to this info.
Add a close x icon to the right side of the banner header, size: 12x12px - this way the user can close this banner at anytime.
(the info. that we're giving the user isn't necessary information, only suggested, so being able to close this banner should be an option)

Overview

Installation & Configuration

API Docs

How-to Guides

Design Changes
On the Installation & Configuration page, the "Pulumi Azure also works with... " banner can stay in the same position on the page as it is now, but add a close icon as we did with the Azure Native provider banner.

Additional Notes

Comments have been added in Figma, but please feel free to reach out with any questions and/or concerns. Thanks!

@susanev - I definitely think having the message shorter would help and I can update the style of banner- the only reason I didn't make any changes to the styling is I thought this issue was just a minimal effort change and didn't think changing the look of the actual banner was part of it.

ah yah, sry about that. i think this work should possibly be about how we can add some kind of general-purpose notification into the top of package pages (with the first application being this particular use case). ill do better at describing these kinds of things in issues going forward.

No problem. I'll move this back to UX design and work on an updated design.

Figma File
Overview tab

Design Changes

Final design for new info. alert (takes the place of the current note on the Overview page now) - applies to all tabs: Overview, Installation & Configuration, API Docs and How To Guides, and should remain in the same place on the page, at the same size, no matter what tab user is on.
Links to https://www.pulumi.com/registry/packages/azure-native](https://www.figma.com/exit?url=https%3A%2F%2Fwww.pulumi.com%2Fregistry%2Fpackages%2Fazure-native - same link as what's currently in the note on the Overview page now
Has a Close icon so that user can dismiss the alert if they want.

On all of the tabs, Pulumi Official graphic has been moved next to 'Azure Classic' header

Installation & Configuration tab

API Docs tab

How-to-Guides tab

Additional Changes

On all of the tabs, Pulumi Official graphic has been moved next to 'Azure Classic' header

Engineer Notes

Comments have been added in Figma but please feel free to reach out with any questions or concerns.

Thanks!

@anita-trimbur can you take a look at the adjustment to the official label and let us know what you think?
@jonelleb im still worried about the increase in height of this header, lets chat more about this in our 1-1 this week.

I think this label position is great. Kimberley and I weren't able to position it exactly where it was initially designed anyway, so I absolutely support this change.


boards: Pine64 PineTime DevKit0

Board definition for PineTime DevKit0 by Pine64 vendor. It is based on information published in https://wiki.pine64.org/index.php/PineTime
Signed-off-by: Rafa Couto<EMAIL_ADDRESS>

received one of the devkits today and will collaborate on getting zephyr running on it as soon as I've got some free time (sometime in november)

Docs are not quite ready for review, but here's a fix for the doc build failure.

Thank you for the tips :+1:

OK. Doc build errors are resolved. Will there be more documentation coming? I wandered around looking for some sample code for this platform and found some stuff written in Go on GitHub (https://github.com/aykevl/go-smartwatch/blob/master/smartwatch_pinetime-devkit0.go).

I will commit some basic sample in a few days (samples/boards/pinetime_devkit0/blink, right?).

What's the plan for this devkit and Zephyr?

This is the board skeleton in order to developers are able to start their firmware apps with Zephyr.

Any plans to update this PR?

@galak Thanks for cleaning up here. I guess closing this one and opening a new one once there's momentum again would be best. I'm still interested and did some testing based on this PR with the device, but can't forsee when I'll have time to pick it up again.

May I help on this topic, I really would love to see the PineTime officially supported by Zephyr

Closing this PR and lets focus on #26698


about-zulip: Fix tooltip to show zulip version is copied

This fixes the tooltip when click on copy icon to copy zulip version.
After clicking on copy version icon, it will show in tooltip that zulip version has copied.
Fixes: #23210

Screenshots and screen captures:
zulip-version-copy.webm

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot claim

This issue hasn't been resolved. I want to work on this issue

This issue hasn't been resolved. I want to work on this issue

@Tusharjolly21 this is not an issue. This is a pull request.

it is fixing the tooltip bug on the about page. You can manually test this.

@zulipbot claim

Thanks for you work, @iSatVeerSingh ! Closing this PR as #23395 is under review, and there is no indication as to why this approach would be preferred.


Add slack to the readme

Add the same community section from the website to the project's README

Hi folks, this link doesn't work for people who already have an account in the kubernetes slack workspace. This one works for those cases: https://kubernetes.slack.com/messages/cri-dockerd.

Thanks @niladrih!
I've updated the PR to include both links. This way someone can signup for the k8s channel if they need or click the link to go straight to the channe.

Thanks @niladrih!
I've updated the PR to include both links. This way someone can signup for the k8s channel if they need or click the link to go straight to the channel.

Awesome! Thanks!


Add swagger spec for Microsoft.features

Add swagger spec for Microsoft.features/operations/read and Microsoft.features/register/action
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-go

@vivsriaus

Automation for azure-sdk-for-python

@AutorestCI rebuild azure-sdk-for-python

Hi, I see that  vivsriaus started the review but there hasn't been any activity for about a week.  Is this PR still valid or can it be closed?

I will close this PR after Friday if there aren't any response or changes.

Automation for azure-libraries-for-java


Vim performance state time interval

Moved Helper#get_time_interval to the concept that it represented.
second commit: it also was retrieving a hardcoded value, so avoided the lookup

udpate:

rebased
dropped obj passed into vps_capture_interval (it is always going to be the same value)
changed name of variable from capture_interval to date_range.


Do not merge - testing build pipeline

Do not merge - testing build pipeline

/azp run

We're currently processing your upload.  This comment will be updated when the results are available.


v3.10.1

Description

Fixed native middleware don't replace http.Request and always used the initial one.
Fixed CORS options not working on subrouters. The main router's ones were always used.
Fixed route groups at root level don't match routes with / prefix.

Possible drawbacks
None.
Related issue(s)

#150
#152

Pull Request Test Coverage Report for Build 996483067

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0009%) to 99.037%

Totals

Change from base Build 979050875:
0.0009%

Covered Lines:
4217

Relevant Lines:
4258

💛  - Coveralls


getSuiMoveConfig error: Cannot read property of 'bcs' Undefined

Im trying to build and execute a tx that bridges usdc from Sui to Solana and receiving a Cannot read property of bcs undefined
Note: I only encounter this issue on mobile

My signAndSend code for context. I
async signAndSend(txs: UnsignedTransaction[]): Promise<string[]> {
    const senderAddress = this.address();
    const txids: string[] = [];

    for (const txn of txs) {
      const { transaction } = txn as {
        transaction: SuiTransaction;
      };

      transaction.setSender(senderAddress);
      transaction.setGasBudget(SUI_DEFAULT_TX_BUDGET);
      try {
        const serializedTransaction = await transaction.build({
          client: this.client.provider,
        });

        const dryRun = await this.client.simTransaction({
          tx: Buffer.from(serializedTransaction).toString("base64"),
          senderAddress,
        });

        if (dryRun.simulationStatus.status === "failure") {
          console.error(
            "Error simulating the transaction: ",
            dryRun.simulationStatus.error
          );
          throw new Error("Error simulating the transaction");
        }

        const signature = await this.client.signTransaction({
          tx: dryRun.preparedTx,
          publicKey: senderAddress,
          blockchainId: SUI_MAINNET,
        });

        if (!signature.response?.signature) {
          throw new Error("Signature is missing from the response");
        }

        const response = await this.client.executeTransaction({
          transactionBlock: signature.response.tx,
          signature: signature.response.signature,
          options: { showEffects: true, showEvents: true },
        });

        txids.push(response.digest);
      } catch (error) {
        console.error("Error signing or executing the transaction:", error);
        throw error;
      }
    }
    return txids;
  }

Hi!
Your complaint will be best dealt with by the support team.
Please see the link below to our dedicated support line:
HELP DESK
Ticket id: DR1TN
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


Fix alignment and icon position for column tabs on Pipeline

Problem
On Position page, in Pipeline tab: Tab button with columns is not left-aligned and icon is centered:

Solution
Apply same styles as in Tab buttons above (general tabs, placement status tabs) - left-align text and set chevron icon to be at the right end.

Should the internal padding in the dropdown list be the same as the button's padding?

Yes, let's keep it (the other 2 tabs have it I think, so no problem). Also after some recent PRs I noticed that size of the general tabs and this stage column tabs changed (became 41px height). Could you please fix it as well? If will take more than 1h please create separate issue.

@amgalanbadmaev, am I right that pipeline dropdown should have its height changed from 41px as well, not only Sourced?

@amgalanbadmaev, am I right that pipeline dropdown button should have its height changed from 41px as well, not only Sourced?

Let's add that to the issue https://github.com/freeats/freeats/issues/174


already initialized constant warnings

Hey there,
I have updated one of my gems, via bundle update and I reckon one of them gem use faraday gem as their dependency.
And now, everytime I run rspec or migration on my rails app, i have got these warnings
/usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
/opt/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.0/lib/net/protocol.rb:66: warning: previous definition of ProtocRetryError was here
/usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
/opt/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.0/lib/net/protocol.rb:206: warning: previous definition of BUFSIZE was here
/usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
/opt/app/vendor/bundle/ruby/2.7.0/gems/net-protocol-0.1.0/lib/net/protocol.rb:503: warning: previous definition of Socket was here

I found out a comment in here: https://github.com/ruby/net-imap/issues/16#issuecomment-803086765
I wonder whether that will fix this issue.
Thanks

Hi @rizalmuthi-ap, I've discussed a similar issue in this PR: https://github.com/lostisland/faraday-net_http/pull/5
Long story short, you most probably have a dependency in your Gemfile that has net-protocol or similar as a declared dependency. This causes your project to load the gem version of net-protocol.
On the other side, in Faraday, we use net-http without explicitly declaring it as a dependency. This internally loads the stdlib version of net-http for Ruby 2.7 or lower, and the gem version for Ruby 3.0+.
This causes the situation where libraries (like net-protocol, in your example) are loaded twice: their gem version and their stdlib version.
I already explained in the PR why I believe Faraday's approach is better, and that other libraries should avoid this kind of explicit dependencies unless they're planning to target only Ruby 3.0+.
I'm sorry I can't really help much more than this.
If you're having a hard time finding the culprit gem, feel free to share your Gemfile.lock and I'll have a look to help


make dustBin beta visible in configuration

just a tiny tweak 😉

https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum/releases/tag/v0.26.4 should include your changes 🚀


Roslyn Language Server Crashes When Accepting Suggestions from Blink Completion Plugin

Description:
I have been trying to switch from nvim-cmp to blink-cmp but have been experiencing issues with the Roslyn language server (LSP).
I'm encountering a problem where the Roslyn language server stops unexpectedly whenever I accept a suggestion from the Blink completion plugin. Other language servers (LSPs) work fine with Blink, so I'm unsure if the issue lies with Roslyn or Blink.
Initially, everything seems to work, but whenever I accept a suggestion from Blink, I receive the following notification:
Roslyn server stopped
Steps to Reproduce:

Open a project in Neovim using blink-cmp.
Begin typing to trigger auto-completion suggestions from Blink.
Accept one of the suggested completions.

Expected Behavior:

The suggested completion should be inserted without any issues.
The Roslyn language server should continue running normally.

Actual Behavior:

Upon accepting a suggestion, a notification appears stating: Roslyn server stopped.
The language server crashes, and I have to restart it to continue working.

Logs
Here is the relevant excerpt from the :LspLog:
[ERROR][2024-10-10 09:41:16] ...lsp/handlers.lua:624 "[LanguageServerHost] System.InvalidOperationException: Unexpected null - file CompletionResolveHandler.cs line 92
   at Roslyn.Utilities.Contract.Fail(String message, Int32 lineNumber, String filePath) in /_/src/Workspaces/SharedUtilitiesAndExtensions/Compiler/Core/Utilities/Contract.cs:line 157
   at Microsoft.CodeAnalysis.LanguageServer.Handler.CompletionResolveHandler.GetTextDocumentCacheEntry(CompletionItem request) in /_/src/LanguageServer/Protocol/Handler/Completion/CompletionResolveHandler.cs:line 92
   at Microsoft.CodeAnalysis.LanguageServer.Handler.RequestContextFactory.CreateRequestContextAsync[TRequestParam](IQueueItem`1 queueItem, IMethodHandler methodHandler, TRequestParam requestParam, CancellationToken cancellationToken) in /_/src/LanguageServer/Protocol/Handler/RequestContextFactory.cs:line 24
   at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`1.CreateRequestContextAsync[TRequest](IMethodHandler handler, RequestHandlerMetadata requestHandlerMetadata, AbstractLanguageServer`1 languageServer, CancellationToken cancellationToken)
   at Microsoft.CommonLanguageServerProtocol.Framework.RequestExecutionQueue`1.ProcessQueueCoreAsync[TRequest,TResponse](IQueueItem`1 work, IMethodHandler handler, RequestHandlerMetadata metadata, ConcurrentDictionary`2 concurrentlyExecutingTasks, CancellationTokenSource currentWorkCts, CancellationToken cancellationToken) in /_/src/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/RequestExecutionQueue.cs:line 319
   at Microsoft.CommonLanguageServerProtocol.Framework.RequestExecutionQueue`1.InvokeProcessCoreAsync(IQueueItem`1 work, RequestHandlerMetadata metadata, IMethodHandler handler, MethodInfo methodInfo, ConcurrentDictionary`2 concurrentlyExecutingTasks, CancellationTokenSource currentWorkCts, CancellationToken cancellationToken) in /_/src/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/RequestExecutionQueue.cs:line 302
   at Microsoft.CommonLanguageServerProtocol.Framework.RequestExecutionQueue`1.ProcessQueueAsync() in /_/src/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/RequestExecutionQueue.cs:line 254"

Additional Information:

The issue does not occur when using other language servers with Blink.
Disabling Blink or switching back to nvim-cmp eliminates the issue, suggesting an interaction problem between Roslyn and Blink.
I've tried reinstalling both the Roslyn language server and the Blink completion plugin, but the problem persists.

This is most definitely a server issue or blink-cmp issue. We can leave the issue open though, and I can see when I get some time to look a bit into this. There was something similar previously with nvim-cmp and built in completion, and that seemed to be a server issue that was "somewhat" fixed

I tried to install blink myself, and I actually got an error immediately when starting to type. I tried to look a bit into it, but I have no idea why it is failing🤷♂
However, I think it is best to try and open an issue over at blink to see if they understand what the problem might be. It shouldn't be something in this plugin at least since it seems to work perfectly with both nvim-cmp and the builtin lsp completion added in neovim nightly.
I am fine with leaving this open in case anyone else that is looking to switch to blink stumbles upon the same issue. Unfortunately, I personally will probably not spend much more time debugging this issue for now

This issue is resolved in the latest release v0.4, so I am guessing this can be closed now :)
Blink issue for reference https://github.com/Saghen/blink.cmp/issues/158

Thanks for the update! Will close this now then :)


Make a patch release for xarray 0.18 support

With the newest version of xarray, CLISOPS v0.6.3 is broken. The fix is already in master and was just wondering if we could get a 0.6.4 if there's time for it this week?
Thanks again!

Hi @Zeitsperre, Thanks for drawing this to our attention. Unfortunately, we have two members of the team away this week and I am snowed under with proposals and admin. I will ask @ellesmith88 to prioritise this next week when she is back.

@Zeitsperre v0.6.4 out on pypi, conda package coming later today

Thanks a bunch!


Implement token swaps in the SDK

Coverage decreased (-0.2%) to 97.858% when pulling b50598e76e682e3c115ac935eb12e09fc9a6faa0 on swaps into 529ed43647710f9cf9e20f6ef2efe90a4da5925b on dev.


Configure gsoci.azurecr.io as the registry to use by default

Towards

https://github.com/giantswarm/roadmap/issues/3017

This PR replaces any occurrence of docker.io in values.yaml files with gsoci.azurecr.io,
to make the new ACR registry the default one.

@giantswarm/team-phoenix Not sure why, but acceptance-test is failing. If you care about this repo, it would be nice if someone from your team could take a look. Otherwise please let me know.


Dualstack IPv4/IPv6

Please add an ability to configure py-kms server so that it can listen for requests on IPv6 in addition to IPv4
https://py-kms.readthedocs.io/en/latest/Usage.html#docker-environment:~:text=is WDAGUtilityAccount).-,%2Dd%20or%20%2D%2Ddual%20%3Cbool%3E,-Allows%20listening%20to

Simply set KMS_IP: "::" as environment variable.


Standard Message Filter ignores MSB of Id

I had some trouble getting a filter to work with standard messages where the 11. bit in the id is set, for example 0x730. Digging deeper, I noticed that the read/write access to the filter registers has the wrong mask (0x3FF instead of 0x7FF), for example here:
https://github.com/stm32-rs/fdcan/blob/86bb892c76a00031b80a4b43dc47c587e8cf84c8/src/message_ram/standard_filter.rs#L49C28-L49C28

Thanks for reporting! This is indeed a bug


World grows after deserialization

Every time I save the same world after loading, the world grows. This happens even if I save an empty world. This also happens with both Binary and JSON serialization.
I've attached two copies of the world JSON, once from the first save, and again after loading and saving again. note that it keeps growing every time I save and load, not just the first time.
world-empty-1.json
world-empty-2.json
I tracked it to this point:

I dug a bit deeper after this and it seems to do with the way the capacity is calculated, and serialized. I attempted serializing/deserializing the capacity of just a single bucket instead of the total capacity, which seemed to partially fix the issue, but it would still grow in some cases so I moved on to other things.

I found it. Firstly we set capacity in JaggedArray constructor. Then we EnsureCapacity and check newCapacity < Capacity (They are same by constructor) so it increases capacity again..
I think fix should be simple @genaray @richdog

Thanks! What do you think is the second leak problem?


ACS unable to set VLAN to Trunk on Distributed Virtual Switches

ISSUE TYPE

Bug Report

COMPONENT NAME
Networking
CLOUDSTACK VERSION
4.14
CONFIGURATION
Advanced networking, Distributed Virtual Switches on VMWare 6.7
SUMMARY
ACS unable to set VLAN to Trunk on Distributed Virtual Switches
STEPS TO REPRODUCE
1- Create physical network with Distributed Virtual Switches
2- Create guest network on the physical switch with DVS
3- Set VLAN/VNI id to 4095
4 - Deploy VM in new network
Error shows up on vCenter

Can you add some detail please.

Details were there but not showing, some issue with formatting, fixed now.

@alexandremattioli can you check and close the bug if it was env issue, or provide details/steps on how to reproduce it? Thanks

Seems like that ID is out of range @alexandremattioli according to https://kb.vmware.com/s/article/2075351

I tested according to your steps and I get the error, but I believe this is a limitation not on Cloudstack.

@Spaceman1984 can you discuss with @alexandremattioli and @PaulAngus and change the tags to new-feature if this is a CloudStack limitations (known/unknown?).

I propose we move this to 4.16 and to make this a small new feature.
If you are using a dvSwitch and want to do VLAN trunking, a second range parameter is required. In the UI we will need a checkbox and a start and end ID.
Otherwise, a temporary and imperfect fix would be to just trunk all ids if 4095 is sent.
Would you guys agree? @alexandremattioli @PaulAngus

Let's move to 4.16, this is not blocker/critical unless we hear from reporters

Fixed in https://github.com/apache/cloudstack/pull/4557, this will make into future <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>

Fixed in https://github.com/apache/cloudstack/pull/4557, this will make into future <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>


[SPARK-13444] [MLlib] QuantileDiscretizer chooses bad splits on large DataFrames (1.6 patch)

What changes were proposed in this pull request?
Fixes a bug in QuantileDiscretizer that results in the wrong number of bins for datasets larger than 10K rows and adds regression test.  This PR corrects an issue with PR #11319.
How was this patch tested?
Manual tests and test-only QuantileDiscretizerSuite

Can one of the admins verify this patch?

It looks like this only contains the test?

Yeah, was about to add the other stuff and got pulled away on something
else. I'll push the other code this evening when I back to my computer.
On Friday, February 26, 2016, Sean Owen<EMAIL_ADDRESS>wrote:

It looks like this only contains the test?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/11402#issuecomment-189491431.

Ok, this one should be good to go.

Jenkins test this please

Test build #52121 has started for PR 11402 at commit db2594d.

Test build #52121 has finished for PR 11402 at commit db2594d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #52123 has started for PR 11402 at commit db2594d.

Test build #52124 has started for PR 11402 at commit db2594d.

Test build #52123 has finished for PR 11402 at commit db2594d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #52124 has finished for PR 11402 at commit db2594d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

The new test is failing.  I'll try to take a look at it this weekend but may be Monday before I can get to it.

After running the test on my machine again, I discovered that it randomly passes/fails.  It appears that the problem is in findSplitsCandidate.  This method will give n+1 buckets under certain circumstances when only n buckets are desired.  The reason that the new test randomly passes/fails is because it involves random sampling of the data in order to estimate the quantiles.
However, the method can still fail deterministically.  For example, consider the following:
val df = sc.parallelize(1.0 to 10.0 by 1.0).map(Tuple1.apply).toDF("x")
val discretizer = new QuantileDiscretizer().setInputCol("x").setOutputCol("y").setNumBuckets(5)
discretizer.fit(df).getSplits

This gives the following splits:
Array(-Infinity, 2.0, 4.0, 6.0, 8.0, 10.0, Infinity)

which corresponds to six buckets.
There are a few ways to fix findSplitCandidates.  The most straightforward (albeit, less elegant) way is to track the number of splits discovered so far while iterating the while loop and terminate the loop when (index < valueCounts.length && splitsSoFar < numSplits).  I believe this is probably the best option for the bug in branch-1.6.  If there's no objections I can put a commit together.
As for the master branch, I'm considering rewriting the findSplitCandidates method using the usual method for finding quantiles.  It's done this way in Numpy/Scipy and I believe it would be at least as fast as the current routine.  I'm curious if anybody has any objections or concerns when it comes to rewrite?

@oliverpierson I haven't seen this test fails in the master build. If I'm correct, we control the random seed in the master branch resulting deterministic behavior. But we don't have it in branch-1.6. If that is the case, we can either backport the commit that implements setSeed (https://github.com/apache/spark/commit/574571c87098795a2206a113ee9ed4bafba8f00f) or backport it but hide the public APIs and fix the seed on branch-1.6 (so we don't expose new APIs). @srowen Which one do you prefer?

@mengxr You're correct that backporting setSeed will make the new test pass, however we'd still be left with issue above, namely that QuantileDiscretizer can return the wrong number of buckets.  I think that the wrong bucket number issue is minor since (I believe) it only affects the min/max values in your data.  In that case, it may be find to leave the findSplitCandidates as is and just backport setSeed.

Sounds good.  You can find the new JIRA here SPARK-13600.

I think it's simplest to back-port the setSeed commit, and then re-add the call to this PR. OK by everyone?

Sounds good.  Curious how we should go about re-adding the call to setSeed?  Should I wait until after it's backported and then rebase my SPARK-13444 branch of the last commit to branch-1.6?

OK @mengxr I'm going to back-port https://github.com/apache/spark/commit/574571c87098795a2206a113ee9ed4bafba8f00f for 1.6.2. Then we basically try the original approach again here.

OK, it's back-ported now. I think this PR can again use setSeed. If we can make it pass then we deal with SPARK-13600 separately

Let me try to backport the original commit from master to branch-1.6 then.

Merged #11319 back to branch-1.6. Ran the test couple times on my local machine and all passed. @oliverpierson Could you please close this PR? Thanks!

No problem.  Thanks!


allow fallback to secret set in options

Coverage remained the same at 100.0% when pulling c10353b638528edcb8cdb598be66136beee704c2 on feature/allow-fallback-secret into 06dbd4bac381802307a12c7707f5f09f263238d8 on master.


Bug: Small subset of users not receiving push notifications [messaging().send...]

[REQUIRED] Step 2: Describe your environment

Operating System version: Windows 10 && Max OSX Mojave
Firebase SDK version:  7.0.0
Library version: 16?
Firebase Product: Messaging

[REQUIRED] Step 3: Describe the problem
A small subset of our users are not receiving remote push notifications sent via messaging().send.
We seem to be getting two different types of responses from messaging().send:
Response Type A
"response":"projects//messages/1550865983585723
Response Type B
"response":"projects//messages/0:1550864692174221%64f3f09064f3f090
Users receiving Response Type A are getting push notifications without issue.
Users receiving Response Type B are failing to receive push notifications
What's the difference between these two responses? Has anyone else run into an issue with certain users not receiving remote push notifications?
Steps to reproduce:
It's reproduced dependent on FCM token.
Relevant Code:
      const message = {
        notification: {
          title,
          body,
        },
        data,
        token,
        // Apple specific settings
        apns: {
          headers: {
            'apns-priority': '10',
          },
          payload: {
            aps: {
              sound: 'default',
            },
          },
        },
        android: {
          priority: 'high',
          notification: {
            sound: 'default',
          },
        },
      }

      try {
        const response = await admin.messaging().send(message, config.firebase.messaging.dryRun)
        logger.debug({ response }, 'Push notification sent')
      } catch (err) {
        logger.error({ err, message }, 'Unable to send push notification')
      }

I don't think this is something that can be addressed here. I would advice you to contact Firebase support where you can share more details specific to your project: https://firebase.google.com/support/troubleshooter/

Are there any resolutions to this? I'm experiencing exactly the same problem with the difference in response formats.


Is Volar compatible with Yarn PnP?

Hi,
Can't make vscode not showing errors on .vue files. If i enable take over mode, errors spread to .ts files. Am i doing something wrong?
My application is a default Vue3 one, generated by Vitejs with typescript enabled, Yarn Workspace + PnP.
Errors are (on App.vue):

Cannot find module 'vue' or its corresponding type declarations.ts(2307)
There are more error on HelloWorld.vue, like Cannot find name 'defineProps'.ts(2304).

I have exactly the same problem. Any solutions for this?

I'm not so used to TypeScript, there is definitely someone who has better skills than me or can fix the issue with Volar.
Anyhow, for my issue, my current workaround looks like this.
vue-shim.d.ts
declare module '*.vue' {
  import Vue from 'vue';
  export default Vue;
}

// Cannot find module ts(2307)
declare module 'vue' {
  import Vue, {
    ref,
    withDefaults,
    defineProps,
    defineComponent,
    PropType
  } from 'vue';
  import type { Ref } from 'vue';

  // Module '"vue"' has exported member ts(2305)
  export function ref<Ref>(...args: any[]): any;
  // Namespace '"vue"' has no exported member ts(2694)
  interface PropType {
    type: () => PropType;
  }
  export = PropType;

  // define global assets
  declare global {
    // Cannot find name ts (2304)
    function withDefaults(...args: any[]): any;
    function defineProps<Props>(...args: any[]): any;
    // Property does not exist ts(2339)
    function defineComponent(...args: any[]): any;
  }

  export const Vue = Vue;
}

I've followed the guidance on SO here -- it requires to manually install additional modules for ts/vscode support, disable "take over mode" and select the workspace TS SDK. So, this I likely ended up in an environment that prompted the creation of "take over mode" -- but, heck, it does work nicely for me so far.  And unless this is fixed I am happy when VSCode is happy :smile:
This is basically:

vite 3.0.0
yarn 3.2.1 in PnP mode (single root / default workspace)

There's nothing else beyond the default sample project.
$ yarn info --name-only
├─ @vitejs/plugin-vue@npm:3.0.0
├─ breakv2@workspace:.
├─ typescript@patch:typescript@npm%3A4.7.4#~builtin<compat/typescript>::version=4.7.4&hash=7ad353
├─ vite@npm:3.0.0
├─ vue-tsc@npm:0.38.5
└─ vue@npm:3.2.37

The result is proper type resolution both in the .ts as well as in the .vue files.  And I can build the project as I expect it to build / dev via yarn build / yarn dev.

Duplicate of #918


ERROR: [vite-plugin-top-level-await] Fallback bindings does not support this interface yet.

Using the latest version of Vite and Vue I get the above trying to use the plugin.
Vue: 3.2.45
Vite: 4.0.0
vite-plugin-top-level-await: 1.2.4

I think it's a SWC issue rather than this plugin.

What is swc?

Someone other has asked this question. The error message is in https://github.com/swc-project/swc/blob/f12bfd1e5544a88a81398427df31fa97b513679c/node-swc/src/index.ts#L84, which is in my dependency, not in my code.
I can't investigate how to reproduce it since you provide no details of your environment, your project, etc. I can't do anything for you. Maybe you can ask SWC's developer for it.


refactor: refactoring to use simple ApiCollector

⚠ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

[ ] I have read through the Contributing Documentation.
[ ] I have added relevant tests.
[ ] I have added relevant documentation.
[ ] I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary
What does this PR do?
PR collector is now using the simple ApiCollector.
Does this close any open issues?
Closes 7457
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.
You can test this by creating a new Devlake Project that will scrape data from Bitbucket Server.
What you should notice is that there won't be duplicate date in _raw_bitbucket_server_api_pull_requests table and that extractApiPullRequests won't slow down.

@klesh branch synced with master. It's ready to be merged


Hotfix for issue #1208

A more proper fix will come with the AutoRest changes as part of beta5 release.

is this change potentially destabilizing? (should we hold off till after beta4.1?)

Without this users cant get more than 1 page of VMs. This is just a manual hotfix and an actual fix will come later.

i see. So that sounds like it belongs in 4.1 badly. We'll need to test heavily.


[Bug] [With workaround] TaskbarX Configurator crashes if started from a shortcut with empty "Start in:" field

I discovered that TaskbarX Configurator will crash if started from a Shortcut.lnk created with nothing in the "Start in:" field. Run it, try to change any setting, click a button, and it will crash.
Workaround:
Put the path to the TaskbarX folder in the "Start in:" field.

I can't reproduce it but, i will add a start-in directory for the shortcuts the installer creates ;)

I had the problem that it would crash even when running the actual file (double-click) or running it from the start menu search (no shortcut, just typing the file name and finding it). So i created a real shorcut (with "start in:") on the start menu and now it works. Thanks!


Setup release v0.0.3 [phab:D342]

Created by schroederc at 2015-06-16 17:16:21:

schroederc wrote at 2015-06-16 17:17:15:
No changes so far...

amshali wrote at 2015-06-16 17:23:06:
Perfect!

schroederc wrote at 2015-06-16 17:26:08:
https://github.com/google/kythe/releases/tag/untagged-6c6240cab2b8a1933beb

fromberger accepted this revision at 2015-06-16 20:23:31

schroederc closed via commit 6df2ca8e2658e94a871e9a0594cd461281197d18 at 2015-06-16 20:48:43


Convert depth map to real world distance

I have got the depth image form zed camera, but the value is 0-255. I wonder how can I convert the value to the real world distance.

Hi
You probably used the retreiveImage() function which gives you a grayscale view of the depth. If you want the actual depth values, you should use retreiveMeasure(myDepthMat, sl::MEASURE_DEPTH).
You can get the depth at a given pixel using:
float z=0;
myDepthMat.getValue(pixelX, pixelY, &z);

Don't hesitate to take a look at the API documentation for more: https://www.stereolabs.com/developers/documentation/API/v2.4.0/


pseudo element spacing problem

I have a problem with pseudo element.
(I get started scss today.)
I wrote like this:
.dropdown li {
      width: 100%;
      ::after {
        content: "blahblah";
      }
    }

There is no error in scss but it doesn't work.
I found the cause. This is the minified css:
.dropdown li ::after{content:"blahblah"}

As you can see, there is a unexpected space between li and ::after.
However I don't know what makes this.
My scss code is wrong? or a bug in scss processors?
These are my sass-autocompile environment:

windows7(64bit)
node-sass(3.8.0)
libsass(3.3.6)
atom(1.9.8)
sass-autocompile(0.13.0)

Thanks.

I'm sorry I found the solution
This code compiles correctly.
.dropdown li {
      width: 100%;
      &:after {
        content: "blahblah";
      }
    }


[MB-13851] Manage PPM shipment customer homepage payment submitted

Jira ticket for this change
Summary
This PR updates the PPMSummaryList component displayed on the customer app homepage to reflect the submission date and messaging when their PPM payment closeout docs are under final review by the office user.
This should represent the state of the PPM shipment after the customer agrees to submit their PPM on the final incentive screen happening here https://github.com/transcom/mymove/pull/9424.  The PPMShipment status should change to NEEDS_PAYMENT_APPROVAL and the timestamp submittedAt should be set as well.
I know TTV has added a new closeout status so I'll try to align with Felipe's PR or vice versa if things change.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Access the
Login as a

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Messages

:book:
:link: MB-13851

  Generated by :no_entry_sign: dangerJS against 6e3e2cb9a0312cbd0f919caf47d35cc2c08af799


use favicon from marketing assets

Issue: Site is using the old favicon.
I've switched it to use the one from marketing_assets.  Same approach as in the JS Buy SDK. https://shopify.github.io/js-buy-sdk/
Current: https://cdn.shopify.com/assets/favicon.ico
New: https://cdn.shopify.com/shopify-marketing_assets/static/shopify-favicon.png

Note: I'm using RBENV, so I added it to the list of ignores.

👍


bug: Clear cache command not working if cache_key is not specified in template provider

Neovim version (nvim -v)
0.10.0
Operating system/version
Windows 11
Describe the bug
:OverseerClearCache command doesn't clear the cache of a task provider when cache_key is not specified.
What is the severity of this bug?
minor (annoyance)
Steps To Reproduce

Activate debug logs in the setup options:

log = {
  {
    type = "echo",
    level = vim.log.levels.DEBUG,
  },
},

Register the following task provider:

overseer.register_template({
  name = "Test Generator",
  generator = function(_, cb)
    print("DEBUG: Generator executed")

    local templates = {
      {
        name = "Test Task",
        builder = function()
          return {
            cmd = { "cmd" },
            args = { "/c", "echo Test Task" },
            cwd = vim.fn.getcwd(),
          }
        end,
      },
    }

    -- Simulate a long running task to make sure template will be cached
    vim.cmd.sleep(2)

    cb(templates)
  end,
})

Run "Test Task" using :OverseerRun
Note the "DEBUG: Generator executed" message
Note the "[DEBUG] Caching Test Generator: [C:\Dev\] = 1" message
Clear the task cache using :OverseerClearCache
Re-run "Test Task" using :OverseerRun
Note that "DEBUG: Generator executed" is not displayed again

Expected Behavior
The generator should be re-executed after clearing the cache.
Minimal example file
No response
Minimal init.lua
No response
Additional context
I debugged the plugin and the problem comes from the fact that the default cache_key is different in require("overseer.template").clear_cache and require("overseer.template").list.
In list, opts.dir is adjusted before passing it to the provider's cache_key function:
418   -- Make sure the search dir is an absolute path
419   opts.dir = vim.fn.fnamemodify(opts.dir, ":p")

Because of this, cache_key is resolved to "C:\Dev" in clear_cache while it's resolved to "C:\Dev\" in list (note the trailing backspace).
Adjusting opts.dir in clear_cache like it's done in list could solve the issue, but I'm not sure it's the right fix. I can submit a PR if needed.

This is odd because I thought I disabled default caching in 6511b0ee9a54e6b18587aa3c9c55c97fa8bf6bdd. Can you confirm where you're seeing a default cache key in require("overseer.template").list?


query returns one row only, my code style is es5

Hi ufukomer,
Here ais my es5 codes, it always return the first row of results
i think it may caused by the 'pending' state, but how can i get all 50 rows after the pending finished?

> var sql = "select system_name from itm.system group by system_name";
> var client = require('node-impala').createClient({"host": "hadoop3"});
> client.query(sql, function(err, data){ console.log('err', err, 'data', data)  })
{ state: 'pending' }
> err null data [ [ 'CASCECUP01:KUX' ],
[ { name: 'system_name', type: 'string', comment: '' } ] ]

> client.resultType = 'map'
'map'
> client.query(sql, function(err, data){ console.log('err', err, 'data', data)  })
{ state: 'pending' }
> err null data Map { 'system_name' => [ 'CASCECUP01:KUX' ] }

> var client = require('node-impala').createClient({"host": "hadoop3", "resultType": 'map'})
undefined
> client.query(sql, function(err, data){ console.log('err', err, 'data', data)  })
{ state: 'pending' }
> err null data Map { 'system_name' => [ 'CASCECUP01:KUX' ] }

Please check same query under impala-shell :
[hadoop3:21000] > select system_name from itm.system group by system_name;
Query: select system_name from itm.system group by system_name
+----------------+
| system_name    |
+----------------+
| CASCECUP01:KUX |
| ASCECUP14:KUX  |
| ASCECSP02:KUX  |
| ASCECUP15:KUX  |
| ASCECMP01:KUX  |
| ASCECUP10:KUX  |
| ASCECUP09:KUX  |
| ESCECUP03:KUX  |
| DBCECUP02:KUX  |
| ASCECUP11:KUX  |
| ASCECUP07:KUX  |
| DBCECMP02:KUX  |
| ASCECUP08:KUX  |
| ASCECSP01:KUX  |
| FSCECUP01:KUX  |
| CASCECMP01:KUX |
| ASCECUP13:KUX  |
| ASCECMP02:KUX  |
| ASCECUP05:KUX  |
| ASCECUP20:KUX  |
| ASCECUP02:KUX  |
| ASCECUP03:KUX  |
| ASCECUP04:KUX  |
| ESCECUP01:KUX  |
| ESCECUP06:KUX  |
| MQCECUP01:KUX  |
| MQCECUP06:KUX  |
| CESCECUP02:KUX |
| ASCECUP18:KUX  |
| ASCECUP06:KUX  |
| ASCECUP01:KUX  |
| CASCECUP02:KUX |
| MQCECUP03:KUX  |
| MQCECUP04:KUX  |
| MQCECUP05:KUX  |
| CESCECUP01:KUX |
| CASCECUP04:KUX |
| ESCECUP02:KUX  |
| ESCECUP05:KUX  |
| ASCECUP16:KUX  |
| CASCECUP03:KUX |
| DBCECUP01:KUX  |
| ASCECUP12:KUX  |
| DBCECMP01:KUX  |
| ASCECUP17:KUX  |
| CFSCECUP01:KUX |
| FSCECUP02:KUX  |
| ESCECUP04:KUX  |
| MQCECUP02:KUX  |
| ASCECUP19:KUX  |
+----------------+
Fetched 50 row(s) in 0.78s

@jhsea3do As I understand, this is the major problem of Beeswax Service. Each INSERT into HDFS creates a new data file. Unfortunately, Beeswax reads only one of them. I have inserted two sample data into sample_08 database, which means two separate data file:

But Beeswax reads only one of them:
// node-impala: output of query (SELECT * FROM sample_08)
[ { code: '10-0000',
    description: 'Yow',
    total_emp: '1112',
    salary: '2000' } ]

Thus, that issue never happens as long as we keep all data in one data file. But of course that is not the solution. It seems to me that the only suitable solution is using HiveServer2 rather than Beeswax. Although, tha is not straightforward way since I should implement a sasl transport something similar to its Java and Python versions.
I would be glad to hear alternative solutions if you have an idea.

Hi! Do you have other suggestions for using Impala with Node.js?

@tiejian create a command line app then use impala-shell via this app. I have never used in NodeJS but there are many in GitHub, e.g. commander.js, cli. I'm not sure if these tools satisfy your need, so make your own search.
If your impala host is remote you would probably need a socket (e.g. using socket io) to connect from command line app that runs in your local machine to command-line app that runs in remote. Hence, you could use impala-shell in this way, probably.

@kwent we should make this library use HiveServer2 in a way that is similar to its python client as I mentioned in the comment above.

Hello Hello everybody,I encountered this problem recently. And maybe I found a way of bypassing this problem！But I am not sure，So I need you to verify it. and let's talk about the reason。
Similar to you,when I query SELECT * FROM atable limit 10 i got 10 rows;
[
{a:'a',b:2},
{a:'b',b:2},
{a:'b',b:2},
{a:'b',b:2},
{a:'b',b:2},
{a:'a',b:2},
{a:'a',b:2},
{a:'a',b:2},
{a:'a',b:2},
{a:'a',b:2}
]

While I query SELECT a,count(*) FROM atable group BY a  i got only 1 row! This is where the problem lies！
[
  {
    "a": "a",
    "count(*)": "6"
  }
]

After my research I found a way to get the expected result！
I query SELECT a,count(*) FROM atable group BY a **order by a**！！！ the order by  is the key.
[
  {
    "a": "a",
    "count(*)": "6"
  },
  {
    "a": "b",
    "count(*)": "4"
  }
]

Try it！I'm Looking forward to your feedback！
@ufukomer


RELAP5-3D executable in a dedicated folder

Issue Description
What did you expect to see happen?
Running multiple cases with RAVEN/RELAP5-3D for Limit Surface Search, Monte Carlo sampling etc.
What did you see instead?
Random failures of the RAVEN/RELAP5-3D with error messages "text file busy". RELAP5-3D is copied in some directories but input deck are not run.
Do you have a suggested fix for the development team?
In the manual/user guide the following should be reported:
RELAP5-3D exe should be in a dedicated separate folder. It should not be copied in all the directories, therefore it should not be specified in the RAVEN   node, but just in the ...path_to_RELAP. Instead RELAP5 input deck file, the license file and the water tables file should be specified in the  node.
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or improvement?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

@alfoa  @mandd

@mandd  @alfoa

It has been identified that the problem was in RELAP5...
Closing


Contribution information for https://github.com/opscode/chef/pull/2642.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.


[Snyk] Upgrade antd from 4.18.9 to 4.23.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade antd from 4.18.9 to 4.23.2.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 38 versions ahead of your current version.
The recommended version was released a month ago, on 2022-09-17.

Release notes

Package name: antd

4.23.2 - 2022-09-17

4.23.1 - 2022-09-09

4.23.0 - 2022-09-04

4.22.8 - 2022-08-26

4.22.7 - 2022-08-21

4.22.6 - 2022-08-17

4.22.5 - 2022-08-15

4.22.4 - 2022-08-08

4.22.3 - 2022-08-01

4.22.2 - 2022-07-28

4.22.1 - 2022-07-27

4.22.0 - 2022-07-26

4.21.7 - 2022-07-18

4.21.6 - 2022-07-11

4.21.5 - 2022-07-03

4.21.4 - 2022-06-27

4.21.3 - 2022-06-17

4.21.2 - 2022-06-14

4.21.1 - 2022-06-13

4.21.0 - 2022-06-06

4.20.7 - 2022-05-30

4.20.6 - 2022-05-22

4.20.5 - 2022-05-15

4.20.4 - 2022-05-11

4.20.3 - 2022-05-09

4.20.2 - 2022-04-30

4.20.1 - 2022-04-26

4.20.0 - 2022-04-24

4.20.0-alpha.1 - 2022-04-18

4.20.0-alpha.0 - 2022-04-12

4.19.5 - 2022-04-02

4.19.5-alpha.0 - 2022-03-28

4.19.4 - 2022-03-27

4.19.3 - 2022-03-21

4.19.2 - 2022-03-13

4.19.1 - 2022-03-08

4.19.1-alpha.0 - 2022-03-08

4.19.0 - 2022-03-08

4.18.9 - 2022-02-28

    from antd GitHub release notes

Commit messages

Package name: antd

48dfe20 docs(:sparkles:): release 4.23.2 (#37602)
e3f0c59 fix(Card): with tabList props still warning deprecated TabPane and update jest snapshot (#37537)
ff6fd11 fix(Table): filterSearch function does not execute  when filterMode is tree (#37587)
646b71b fix: Tooltip not override children className when it's not a string type (#37598)
08a47a9 docs: Modify res title for Raycast usage
bcd9dca feat: add raycast (#37589)
7da32ce ci: support skip-label (#37482)
3619caf refactor: delete deprecated React.ReactChild (#37551)
c161ab6 chore: Fix Argos build diff fail of outside contributor (#37555)
130b7c2 docs: modify the onChange description of the Upload document (#37553)
711ed90 docs: fix table filterSearch function doesn't work demo (#37536)
851a61a fix: TreeNode not aligned when disabled and draggable (#37534)
c3ebf4b chore: Use new Argos CLI  (#37496)
f082155 docs: add changelog 4.23.1 (#37502)
1bb5817 test: delete icon.svg (#37499)
01ca7c7 test: convert demo to testing-lib (#37381)
1922ad3 type: strong type (#37481)
370c37c test: js => ts (#37485)
9f28e51 test: js => ts (#37484)
e20314c test: move test cases to testing lib for Transfer (#37029)
b5ab2a9 docs: Update fileList.md (#37480)
05ef36e docs: Update CHANGELOG (#37476)
87f3924 fix: unable to close modal when using visible in Modal.confirm().update (#37471)
7c087de chore: Add theme=null export for vite build error (#37462)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

/check


Savegame issue: lara falls under the running twoblock platform after reloading the game.

https://cdn.discordapp.com/attachments/481099779611295747/1007779310385504339/2022-08-13_00-33-38.mp4

Fixed or not?


removes set echo from dotnet-mssql

It was unecessary and throwing a visible error in the container creation log
https://github.com/microsoft/vscode-dev-containers/issues/754
secondary - fixing a residual mistake in the test project

Thanks for updating @dzsquared! The changes make sense to me.
I had a couple of other questions as I checked out this definition:

I ran a .NET Restore, but I'm still receiving the following problems - did I miss a step?

I'm still able to run the app.

Should we update the guidance in the README? I notice the following:

After packages are restored, press F5 to start the project.
Once the project is running, press F1 and select Remote-Containers: Forward Port from Container...
Select port 8090 and click the "Open Browser" button in the notification that appears.
You should see "Hello remote world from ASP.NET Core!" after the page loads.

When I ran this project with the Program.cs in test-project, an F5 autoforwards the port 8090, and opening port 8090 brings me to the following (I can also see where in Program.cs, it's set to print out "The databases are..." rather than "Hello remote world from ASP.NET Core!"):

@dzsquared - Gentle ping on @bamurtaugh 's questions.  Thanks!

Thanks for re-pinging, @Chuxel!
@dzsquared Please let me know when this one is ready for review again, and I'll be happy to look it over. 😄

@bamurtaugh - I finally got back into this.
Made the adjustments/corrections to the README as you noted, thank you!
I also saw the intellisense issue and in troubleshooting it, I bumped the devcontainer to netcore 5 and MDS 3 to match the primary dotnet devcontainer.  Magically, intellisense is now functioning correctly when I build the devcontainer.
thank you!

Thanks for the updates @dzsquared! The readme looks great and matches the experience when I tested the app. My question remains with the IntelliSense/problems that pop up - it looks like I'm still experiencing the same red underlines, any ideas?

@bamurtaugh - as to the intellisense issue with .NET in VS Code I'm not sure of the cause or a definitive fix.  I was able to repro it until I bumped the dev container to netcore 5 and MDS 3.

Thanks for looking into it! Would you be able to resolve the merge conflict so that we can do a final merge?

done, thanks!


Extension ignores PATH set by venv when running test

Environment data

VS Code version: 1.26.1
Extension version (available under the Extensions sidebar): 2018.7.1
OS and version: CentOS Linux release 7.4.1708 (Core)
Python version (& distribution if applicable, e.g. Anaconda): 3.7.0 (built from source)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv

Steps to reproduce:

Set up virtualenv (python -m virtualenv venv)
Open folder in VS Code and choose Python interpreter to "Python 3.7.0 (venv)".
I have a nose test which runs pylint command via Popen(..., shell=True) with plugin in the source code.

Expected  behavior
Test runs pylint installed into virtualenv
Actual behavior
Despite that python is taken from virtualenv, test runs with system PATH variable which does not have installed package (or has wrong version).
Logs
Output from ps -ef | grep python when running the test:
default  21133 21033  0 12:21 ?        00:00:00 /home/default/conan/venv/bin/python /home/default/.vscode/extensions/ms-python.python-2018.7.1/pythonFiles/jedi/evaluate/compiled/subprocess/__main__.py /home/default/.vscode/extensions/ms-python.python-2018.7.1/pythonFiles
default  24974 20915 39 12:37 ?        00:00:00 /home/default/conan/venv/bin/python -m nose --xunit-file=/tmp/tmp-209153hIDoVKwtMyE.xml --with-xunit --with-id conans/test/command/export_linter_test.py:ExportLinterTest.test_basic conans/test/command/export_linter_test.py:ExportLinterTest.test_basic
default  25008 24974  0 12:37 ?        00:00:00 /opt/rh/rh-python36/root/usr/bin/python3 /usr/bin/pylint --output-format=json --py3k --enable=all --reports=no --disable=no-absolute-import --persistent=no --load-plugins=conans.pylint_plugin --init-hook=import sys;sys.path.extend(['/tmp/tmp81scfb65conans/path with spaces', '/home/default/conan']) /tmp/tmp81scfb65conans/path with spaces/conanfile.py

So it runs /usr/bin/pylint instead of /home/default/conan/venv/bin/pylint when VS Code was started from Start Menu.

@ytimenkov what shell are you using and how are you setting PATH to include Pylint? I just opened #2422 to look into more carefully how we are executing subprocesses, but basically we aren't ignoring PATH and more likely that how you modify PATH isn't being picked up by how we execute subprocesses (e.g. you're setting it for your login shell but not interactive shell or something).

Hmm... I use fish. That could be the difference, as it requires sourcing activate.fish.

how are you setting PATH to include Pylint?
That is simple. In my terminal I run:

> python -m virtualenv venv
> . venv/bin/activate.fish
> pip install pylint
...
> which pylint
/home/default/conan/venv/bin/pylint

Is it possible that when I run unit test (via command, or by using CodeLens) it doesn't activate environment but runs interpreter directly?

@ytimenkov We should be running pylint using the -m switch, i.e. python3 -m pylint (unless you override with the python.linting.pylintPath setting). Do you have the virtual environment you're using selected in the interpreter? And what linting settings do you have set?

@brettcannon I think you misunderstand me a bit. It's not the extension itself which runs pylint. It's a unit test which runs pylint via Popen (it could well be any other tool installed with pip).
That one in particular: https://github.com/conan-io/conan/blob/develop/conans/test/command/export_linter_test.py

Do you have the virtual environment you're using selected in the interpreter?

Yes, I set up virtual environment and select it in VS Code. As I wrote before, the interpreter and UT framework (nose in this case) are selected properly, but when test itself tries to execute program it uses system PATH.

@ytimenkov yep, sorry about that.

What you probably want to do is launch VS Code with your virtual environment already activated:
> . venv/bin/activate.fish
> code .

That should cause VS Code to inherit your PATH variable which has ./venv/bin/pylint ahead of /usr/bin/pylint.
Another option is to try setting your PATH in an environment variable definitions file to what you want it to be.
But everything is operating as expected so this isn't a bug.

Although it works as designed I would argue that it is what expected from user perspective.
Running code from activated env doesn't work well since they do some kind of rpc and just open another window from already running instance and this won't inherit shell's environment.
Setting Path in settings is cumbersome as it needs to be changed too when switching venv.
My point is that it is a bug in a sense that it violates the principle of least surprise: selecting venv in the toolbar is expected be similar to activation. It's strange that environment is activated only sometimes (which made me waste some time figuring out why test passes in vs code, but fails on CI).
And regardless of future of this ticket, the extension is awesome!

I've re-opened this as a feature enhancement.


Added initial cut at daily build spec

Part of #4114.
Spec / document detailing changes around how daily builds, weekly builds, and final versions are created, versioned, and pushed to package repositories.
The summary:

Copy with the ASP.Net Core team is doing where possible
Push daily builds to Azure Devops
Push a weekly build to exercise our release pipeline
Clearly define use of tags (-preview, -rc)

Tom had feedback around "We ship some packages as '-preview' and we need to snap with that."


Emits finish dispite still consuming

The following code is a copy of an example in README plus finish event. I assumed the parallel transform emits finish after all data consumption but is didn't.
var stream = transform(10, function (data, callback) {
  setTimeout(function () {
    callback(null, data);
  }, Math.random() * 1000);
});

for (var i = 0; i < 10; i++) {
  stream.write('' + i);
}
stream.end();

stream.on('finish', function () {
  console.log('stream has finished');
});
stream.on('end', function () {
  console.log('stream has ended');
});

output
0
stream has finished
1
2
3
4
5
6
7
8
9
stream has ended

This is not pleasant especially when we use libs such as pump that calls a callback function depending on finish event.
It seems that it emits finish after all writable data is buffered instead of consumed.
This problem occurs also in parallel-stream module.
Also, when we do readable.pipe(parallelTransform).pipe(writable), the writable emits finish earlier than expected.

Any updates on this issue?

Too bad no one has answered before, but I think you are simply misunderstanding the interface provided by a Transform stream. The finish and end events are working correctly, but they represent different parts of the transform stream.

finish means that the Writable side of the Transform stream has been drained and closed, i.e. no new data may written to the transform and all data has been passed to the transform function so that the "write" buffer is empty
end means that the Readable side of the Transform stream has been drained and closed, i.e. all work (including flush function) has been completed and pushed out so the "read" buffer is empty and no more data will be available

pump etc. correctly wait for both sides of the stream to close, and work correctly with this package. See eos for the utility package pump etc. usually use for detecting end of streams.
Here is a more verbose version of your test script and its output annotated with why something fired.

Test script with more logging

Annotated output
[stream] start 0
[stream] start 1
[stream] start 2
[stream] start 3
[stream] start 4
[stream] start 5
[stream] start 6
[stream] start 7
[stream] start 8
[stream] start 9
// Max concurrency tasks are processing
[stream] stop  2
[stream] stop  4
[stream] stop  8
[stream] stop  5
[stream] stop  9
[stream] stop  3
[stream] stop  7
[stream] stop  0
[logger] start 0
[stream] start 10
// Last item has been given to transform function, 'finish' event can now fire
[logger] stop  0
[stream] stop  1
[logger] start 1
// The 'finish' event fires after work that was already queued in Node
- [stream] has finished
// 'finish': Writable side of the Transform stream has been drained and its buffer is empty
[stream] stop  6
[logger] stop  1
[logger] start 2
[logger] stop  2
[logger] start 3
[logger] stop  3
[logger] start 4
[stream] stop  10
// All events have now been processed by the transform stream
- [stream] has ended
// 'end': Processing and Readable buffer have been drained and flush has completed
[logger] stop  4
[logger] start 5
[logger] stop  5
[logger] start 6
[logger] stop  6
[logger] start 7
[logger] stop  7
[logger] start 8
[logger] stop  8
[logger] start 9
[logger] stop  9
[logger] start 10
[logger] stop  10
- [logger] - finished
// 'finish': Writable side of the Transform stream has been drained and its buffer is empty

This issue should probably be closed unless there is a concrete repro case for this statement:

Also, when we do readable.pipe(parallelTransform).pipe(writable), the writable emits finish earlier than expected.

Sounds like a pretty fatal bug in node core

@Tapppi I really appreciate you detailed feedback. @mafintosh I would like you to take a look at this issue, this core bug-fix improves the package even better.

This is a big problem, since the node community encourages using 'pipeline' instead of 'pipe',
and 'pipeline' is finished when 'finished' is fired..

@Eli-Goldberg Hi. pipline-pipe might help you, a forked version of parallel-transform with the fix. Happy if you give me feedback.


Add firebase analytics

Summary
Added firebase analytics and base events
Reasons
Base analytics implementation
References
closes #143

It's already better, but what I expect to see:

Main Analytic class Analytic is a singleton, we can use it in the way Analytic.homeOpened().
Inside, Analytic contains a provider var provider: AnalyticsProvider? = null, only the provider knows about the event tracking library.
AnalyticsProvider is an interface, we can provide any implementation via DI.
Analytic.homeOpened() function calls provider for tracking analytics `fun homeOpened() = provider?.logEvent(Event.HOME_OPENED)
As you can see events string located in Constants
How do we set the provider to Analytic Singleton? For that, we make a function in Analytic like:

    private var provider: AnalyticsProvider? = null
    fun init(provider: AnalyticsProvider) {
        this.provider = provider
    }

And init it in the Application class in onCreate.
7. For Firebase, we make FirebaseAnalyticProvider, and provide it in DI for AnalyticsProvider interface.


loading large model not finished after 16 hours

🐛 Bug
After saving a checkpoint of a large pytorch_forecasting model (10'100 targets forecasting based on previous 10'000 values ), loading the checkpoint lasts forever (i killed loading after 16 hours).
With 5 targets forecasting based on previous 5 values -> works
With 50 targets forecasting based on previous 50 values -> works
With 500 targets forecasting based on previous 500 values -> works
With 5000 targets forecasting based on previous 5000 values -> in test
Atm. trying to find the amount where it stops working.
To Reproduce
The model hast 10'100 target values, the prediction is 24 time intervals based on 48 past time intervals.
The predictions are quantiles(0.25,0.5,0.75)
Expected behavior
the model can be loaded in a reasonable timeframe.
Environment

PyTorch 1.4.9
PyTorch 1.9.1
Python version: 3.8.10
OS (e.g., Linux): Ubuntu 20.04
CUDA/cuDNN version: -
GPU models and configuration: -
How you installed PyTorch (conda, pip, source): pip

Additional context
Loading and saving of small models works well.

I see, can you try to do it with a torch.nn.Module as a baseclass instead? just to see if this is something we are doing different from the original pytorch code?

I have other models in pure pytorch with custom written training loops that have the size of about 200MB and never had issues with loading them but they are just fully convolutional models with maybe less keys in the state_dict. The one here is a temporal fusion transformer and I dont know the structure of it.
But I dont think that the size is the problem, I think the key count is the issue.
The 2 targets from 2 columns already has 292 keys in the state_dict.
The 10 targets from 10 columns already has 668 keys in the state_dict.
The 100 targets from 100 columns already has 4898 keys in the state_dict.
The 1000 targets from 1000 columns already has 47198 keys in the state_dict.
The increase in keys is also some what linear I guess.
Loading the pickle from drive does not work in parallel but cant you assign the state_dict in parallel?
I think one reason for being slow is, that the function does just use one thread (one CPU core is at 100% the rest is idling around).
So using a threadpoolexecutor and start a thread for each key in the state_dict might be an improvement.
Is this a topic for pytorch?

Hi sorry for the late response. I just double checked and we are not doing anything special here. We just rely on the function provided by pytorch, so I do think it would be best if you open an issue with them :)


Fixing build issues caused by dependency update.

Related to this PR. Also testing to see if changing<EMAIL_ADDRESS>account permissions from BigTable Viewer to Bigtable User fixes the failure with Bigtable Test.

BigTable error is in fact fixed, though now there's a BigQuery error that replaced it. Looking into it.

I'm having trouble finding a root cause for this, as the error message isn't very helpful and there isn't much documentation about it that I can find. It seems like the root cause may be buried in the stack trace, but I can't reproduce the error locally.

@tswast PTAL

[ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 8.771 s <<< FAILURE! - in com.example.bigquery.QuerySampleIT
[ERROR] testPermanentTableQuery(com.example.bigquery.QuerySampleIT)  Time elapsed: 2.743 s  <<< ERROR!
com.google.cloud.bigquery.BigQueryException: java.lang.IllegalArgumentException: key completedInputs
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs, field private com.google.api.services.bigquery.model.JobStatistics com.google.api.services.bigquery.model.Job.statistics
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs, field private com.google.api.services.bigquery.model.JobStatistics2 com.google.api.services.bigquery.model.JobStatistics.query
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs, field private java.util.List com.google.api.services.bigquery.model.JobStatistics2.timeline
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs, field private java.util.List com.google.api.services.bigquery.model.JobStatistics2.timeline
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: key completedInputs, field private java.lang.Integer com.google.api.services.bigquery.model.QueryTimelineSample.completedInputs
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)
Caused by: java.lang.IllegalArgumentException: number field formatted as a JSON string must use the @JsonString annotation
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)

[ERROR] Errors:
[ERROR]   QuerySampleIT.testPermanentTableQuery:111 ? BigQuery java.lang.IllegalArgument...
[ERROR] Tests run: 11, Failures: 0, Errors: 1, Skipped: 1
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on project bigquery-google-cloud-samples: There are test failures.

@dzlier-gcp it is probably similar.  It's sounding like some new IAM features were released recently.  I don't see anything in the release notes however.

@pongad did we just discover a bug in the BQ library?
Caused by: java.lang.IllegalArgumentException: number field formatted as a JSON string must use the @JsonString annotation
	at com.example.bigquery.QuerySampleIT.testPermanentTableQuery(QuerySampleIT.java:111)

looks like an error in the library (couldn't parse the job response) as opposed to an error in the sample.

I had a hunch that might be it, but I wanted a second opinion on it. I can file a bug.

@tswast It might very well be. Could you file a bug in google-cloud-java and assign me? A small main method to reproduce this would also be awesome.

Filed https://github.com/GoogleCloudPlatform/google-cloud-java/issues/3015

@dzlier-gcp Do you want to just roll back the bigquery update so that we can pull the rest of the updates?

Another option. You could explicitly declare this dependency in this repo to override. Then after our update makes its way to Maven, you could remove it.
Up to you of course.

Taking care of this this afternoon.

Bigtable errors are gone, but the container registry tests still fail after being pushed almost a month ago, and I'm not having any luck resolving those.

@dzlier-gcp you might as well merge then.  Use admin


VantagePointTree Controlled Randomness

Until now scala.util.Random was used with changing seed.
With this pull-request it is possible to specify the randomness.
Usage:
implicit val rnd = Random(seed)
val tree = VantagePointTree...

Looks good to me.
@Andreas-Forster If you are also happy with the change, can you merge the PR?

@andreas-schneider There is an internal consensus (offline discussion) that the Randomness problem in Scalismo needs to be addressed more fundamentally. The idea is to include a small, dedicated Random class, which provides an implicit instance of a random number generator if the user does not define his/her own implicit instance.
As this will cover your use case as well (and should be available in develop within the next 2 weeks), I will close this PR.

Great!


feat(ndt_scan_matcher): estimate NDT covariance in real-time with limited initial positions

Description
Calculate 2D covariance (xx, xy, yx, yy) in real time using the convergence of NDT.
I limit the arrangement of multiple initial positions based on the Hessian matrix of the NDT score function.
Related links
original paper
Tests performed
I evaluated it In a tunnel evaluation (already shared in weekly meeting).
The real-time covariance estimation obtained the same convergence tendency as offline convergence evaluation.
Notes for reviewers
Related PRs:

https://github.com/tier4/ndt_omp/pull/22
Output Hessian matrix
https://github.com/autowarefoundation/autoware_launch/pull/643
Parameters for this covariance estaimtion

Interface changes

topic
/localization/pose_estimator/multi_ndt_pose
->NDT convergence positions
/localization/pose_estimator/multi_initial_pose
->NDT initial positions

yaml setting (ndt_scan_matcher.param.yaml)
Category: 2D Real-time covariance estimation (output_pose_covariance is the minimum value)
Default use_covariance_estimation is false.

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the [contribution guidelines].
[x] The PR follows the [pull request guidelines].

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the [pull request guidelines].
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.
After all checkboxes are checked, anyone who has write access can merge the PR.
[contribution guidelines]: https://autowarefoundation.github.io/autoware-documentation/main/contributing/
[pull request guidelines]: https://autowarefoundation.github.io/autoware-documentation/main/contributing/pull-request-guidelines/

@KOKIAOKI Thank you for your contribution!
Could you write an explanation in the readme?
I'd also like you to include a link of your paper in the readme.

Thank you for checking my implementation.
Please let me test again after fixing these fixes.
Also, to pass the DCO, I will rebase past commits and group them together, and add Signed-off to the commit message.

Sorry for the delay in reporting.
I have reflected all the reviews made by @Motsu-san  and @KYabuuchi  into the source code.

Changed the calculation of variance to a method that uses smaller variables.
There were many variable names that caused misunderstandings, so we made them easier to understand.
Changed and added notes and explanations in README

@YamatoAndo @KYabuuchi
Thank you for further checks.
I created the function of eigenvector calculation and added README empty line.

@YamatoAndo @KYabuuchi @SakodaShintaro
Thank you for further code checks.
Main changes are as below:

@SakodaShintaro Like your advice, I added parameter warning and std::exeption about Eigen::Success.
@SakodaShintaro Although review about util.cpp was closed, I moved two functions from util.cpp to ndt_scan_matcher.cpp.


Added level order for all tree

Added level order for all trees and also added one test case for each. All test cases pass.

Everything looks ok @aveldan! Thank you for following the steps i have for contributing. Hope to see you contribute again!
This PR will be merged.


Fix clean for 'coverage' and 'asan_testing' toolchains

Because integration tests are included into certain clean targets for all toolchains, e.g. in example_cpp_smart_card_client_app/build/Makefile, clean-all.sh breaks when cleaning with toolchain=coverage and toolchain=asan_testing.

Thanks for catching it. Now that I'm thinking about it, we should probably drop those test-specific references from nested makefiles like example_cpp_smart_card_client_app/build/. We're shifting towards the model in which developers should only trigger make in the root folder, and the root makefile already knows about all modalities.


[Communities] Introduce new communities header UI

Problem:
Currently, our community pages have a simple header UI with just a small icon, which prevents communities from customizing the look and feel of their page and make it inviting to engage with their members.
User Story:
As a community admin, I want to have the ability to customize our page in a visually engaging way so that I can reflect the unique identity of our community and engage with our members.
Acceptance Criteria

Communities header UI element should reflect the attached design

Header image (1320px by 240px)
Profile image (150px by 150px) – Use this image to update the image of the community card on the view all communities page)
Community title (limit character length to fit one line for the description of each community card on the view all community page)
Community short bio (limit character length to fit two lines for the description of each community card on the view all community page)
Share button that allows users to easily copy and share the URL of the community page (can use similar functionality to share button on this page)
Introduce dropdown functionality to categorize common pages such as channels (Telegram, Github)

User with admin permissions can customize all of the above fields in the admin page

Attachments:

Figma design

@ori-near could you assign me?

I finished broadly, will finish up on details like font specifics once the first draft is reviewed.

The current banner is not the same, however I guess after @near-akaia-root is done that can be adjusted easily.

And the mobile view

The current banner is not the same, however I guess after @near-akaia-root is done that can be adjusted easily.

Yep, it's just we don't even have banners yet and they're to introduce in updates I'm working on

Thanks for the progress @Tguntenaar. Is it possible to keep the same proportions for the image in mobile view?

@ori-near thanks for the feedback. Will update it today so it matches the same aspect ratio.

@ori-near I updated it so the aspect ratio of the images stays the same. I created a PR to @near-akaia-root her fork.

Closed in https://github.com/near-akaia-root/neardevhub-widgets/pull/1

@ori-near shall I move it to done now?

Looks great, thank you @Tguntenaar and @near-akaia-root. Is there a preview link to see this?

@ori-near https://near.org/#/root.akaia.near/widget/gigs-board.pages.community.Overview?handle=protocol&nearDevGovGigsContractAccountId=devgovgigs.near

Done by @Tguntenaar


React-Scripts start command throws JavaScript heap out of memory error

Describe the bug
When I start react application with npm start command, it failed to start the application and throws the error Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory.
I tried to change the start script by adjusting max_old_space_size to 8192 but that still does not fix the issue.

$ react-scripts  --max_old_space_size=4096 start
$ react-scripts  --max_old_space_size=8192 start

I looked at existing issues/solutions in this repo and StackOverflow, nothing fixed my issue.
Did you try recovering your dependencies?
Yes, I did. It did not fix the issue.

I deleted node_modules and tried to install them using following commands $npm install
 $npm start

Then deleted them again and installed and ran again with commands $yarn install
 $yarn start

Which terms did you search for in User Guide?
Yes, I searched for heap memory error and didn't find anything useful
Environment
Environment Info:

  current version of create-react-app: 4.0.3
  running from /Users/jaddap2/.npm/_npx/9378/lib/node_modules/create-react-app

  System:
    OS: macOS 11.3
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 14.16.1 - /usr/local/opt/node@14/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.12 - /usr/local/opt/node@14/bin/npm
  Browsers:
    Chrome: 89.0.4389.114
    Edge: 89.0.774.75
    Firefox: 87.0
    Safari: 14.1
  npmPackages:
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: 4.0.3 => 4.0.3
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce
Clone the repo and follow the instructions below

Clone the repo https://github.com/pavankjadda/react-scripts-bug
And run the commands

$ npm install
$ npm start

Expected behavior
Start the application without any issues
Actual behavior
Sees an error Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory.
Stack Trace:
Starting the development server...

<--- Last few GCs --->

[9019:0x1044f3000]   136716 ms: Scavenge (reduce) 8129.9 (8155.3) -> 8129.4 (8155.8) MB, 7.7 / 0.0 ms  (average mu = 0.356, current mu = 0.337) allocation failure
[9019:0x1044f3000]   136724 ms: Scavenge (reduce) 8130.2 (8152.8) -> 8129.6 (8153.8) MB, 6.9 / 0.0 ms  (average mu = 0.356, current mu = 0.337) allocation failure
[9019:0x1044f3000]   136747 ms: Scavenge (reduce) 8130.3 (8152.8) -> 8129.8 (8153.8) MB, 21.7 / 0.0 ms  (average mu = 0.356, current mu = 0.337) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100097949 node::Abort<EMAIL_ADDRESS> 2: 0x100097abf node::OnFatalError(char const*, char const*<EMAIL_ADDRESS> 3: 0x1001a42c1 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool<EMAIL_ADDRESS> 4: 0x1001a426b v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool<EMAIL_ADDRESS> 5: 0x1002def55 v8::internal::Heap::FatalProcessOutOfMemory(char const*<EMAIL_ADDRESS> 6: 0x1002e0214 v8::internal::Heap::MarkCompactPrologue<EMAIL_ADDRESS> 7: 0x1002ddb20 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags<EMAIL_ADDRESS> 8: 0x1002dc03d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags<EMAIL_ADDRESS> 9: 0x1002e5164 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment<EMAIL_ADDRESS>10: 0x1002e51ba v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment<EMAIL_ADDRESS>11: 0x1002c363b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin<EMAIL_ADDRESS>12: 0x1005424ea v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*<EMAIL_ADDRESS>13: 0x1007e4119 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit<EMAIL_ADDRESS>npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `react-scripts  --max_old_space_size=8192 start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/jaddap2/.npm/_logs/2021-04-13T03_22_17_319Z-debug.log

Reproducible demo
Clone the repo and follow the instructions below

Clone the repo https://github.com/pavankjadda/react-scripts-bug
And run the commands

$ npm install
$ npm start

Hi @pavankjadda,
tried to import the project to CodeSandbox quite quickly and @ohif/viewer chocked the process there. This doesn't seem to be a react-script specific problem, so I'd suggest to narrowing the issue down to the correct dependency and acting accordingly (or even bumping the max-old-space to something like 16GB if you can afford it).