Navcoin Core Wallet - Error Reading from Database, Shutting Down

Open wallet, starts syncing chain. Crashes with "Error Reading from Database, Shutting Down"

Wallet to open and sync.

Every time I open the wallet.

<IP_ADDRESS> from official website

Windows 10, Ryzen 3800XT, SSD disk

Debug Log
2021-06-12 04:12:25 Peer=30 is stalling block download, disconnecting
...
2021-06-12 04:13:10 UpdateTip: new best=7ded1a885bed22ddc8d0889b1c5cb3fd2a9a9f583559102fc82ee538388865ec height=5265145 version=0x7bf5f5ff log2_work=73.698221 tx=10948967 date='2021-06-08 07:20:16' progress=0.996087 cache=6.3MiB(14859tx)
2021-06-12 04:13:10 UpdateTip: new best=1fcc2c8be9ceca4ba300f5406d42657d973fb435bae8bd924fe60e3c10561ed1 height=5265146 version=0x7bf5f5ff log2_work=73.698221 tx=10948969 date='2021-06-08 07:21:52' progress=0.996088 cache=6.3MiB(14861tx)
2021-06-12 04:13:10 LevelDB read failure: Corruption: block checksum mismatch: C:\Users\Luke\AppData\Roaming\NavCoin4\chainstate/010867.ldb
2021-06-12 04:13:10 Corruption: block checksum mismatch: C:\Users\USER\AppData\Roaming\NavCoin4\chainstate/010867.ldb
2021-06-12 04:13:20 INFO: Updating prices
2021-06-12 04:13:20 INFO: Updated prices
What would I like to see from this ticket?
A wallet UI enhancement. I suspect this is a corrupt DB and there is some esoteric cmd line I can run to fix it or rebuilt it. It's 2021 if we want adoption we shouldn't be forcing people to do that. Put a button on the error popup that says 'Repair' and try and fix this automatically for people. Obviously you can't fix everything and the fallback after that can be said cmd line fix.
Thanks all!

Just FYI as well, I can't get to the FILE -- Repair option suggested here https://info.navcoin.org/navcoin-core/repair-your-wallet/ as the wallet crashes basically as soon as the sync progress screen appears.

So I managed to get to File --> Repair wallet... had to load up my CPU's with a stress test at 100% load so the entire machine was running slowly... gave me just enough time to get to the repair option before the wallet crashed. Popped up the OK message to start repairing and off it went... issue fixed. Still not a great user experience.

from the error log you attach, your issue was a corruption of the chainstate db. this is fixed with a resync/bootstrap
repairing the wallet has nothing to do with the issue you comment. i can’t see the connection

On 12 Jun 2021, at 06:23, yraen69 @.***> wrote:
Open wallet, starts syncing chain. Crashes with "Error Reading from Database, Shutting Down"
Wallet to open and sync.
Every time I open the wallet.
<IP_ADDRESS> from official website
Windows 10, Ryzen 3800XT, SSD disk
Similar issue, different App Data path? Windows 10 thing?
2021-06-12 04:12:25 Peer=30 is stalling block download, disconnecting
...
2021-06-12 04:13:10 UpdateTip: new best=7ded1a885bed22ddc8d0889b1c5cb3fd2a9a9f583559102fc82ee538388865ec height=5265145 version=0x7bf5f5ff log2_work=73.698221 tx=10948967 date='2021-06-08 07:20:16' progress=0.996087 cache=6.3MiB(14859tx)
2021-06-12 04:13:10 UpdateTip: new best=1fcc2c8be9ceca4ba300f5406d42657d973fb435bae8bd924fe60e3c10561ed1 height=5265146 version=0x7bf5f5ff log2_work=73.698221 tx=10948969 date='2021-06-08 07:21:52' progress=0.996088 cache=6.3MiB(14861tx)
2021-06-12 04:13:10 LevelDB read failure: Corruption: block checksum mismatch: C:\Users\Luke\AppData\Roaming\NavCoin4\chainstate/010867.ldb
2021-06-12 04:13:10 Corruption: block checksum mismatch: C:\Users\USER\AppData\Roaming\NavCoin4\chainstate/010867.ldb
2021-06-12 04:13:20 INFO: Updating prices
2021-06-12 04:13:20 INFO: Updated prices
What would I like to see from this ticket?
A wallet UI enhancement. I suspect this is a corrupt DB and there is some esoteric cmd line I can run to fix it or rebuilt it. It's 2021 if we want adoption we shouldn't be forcing people to do that. Put a button on the error popup that says 'Repair' and try and fix this automatically for people. Obviously you can't fix everything and the fallback after that can be said cmd line fix.
Thanks all!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi aguycalled,
thought my experience was pretty clear, end user wise it wasn't great. Yes it was a chain corruption issue. If you look at my screenshot the error box pops up within a couple of seconds of the wallet finally loading. All you can do is click OK and the wallet crashes.
This is BAD. You cannot get to FILE --> Repair Wallet.
I had to load up all of my CPU cores to make my machine run SLOW enough for me to have enough time to get to the FILE --> Repair option and click that before the error message pops up crashing my wallet.
That 'Error reading from database shutting down' message should NOT be a fatal one that instantly closes the wallet and gives you not option but to click OK.
It should instead actually give you the option to repair the wallet ON that error popup or at least grey out the main UI and let you at least click FILE --> Repair wallet.

i understand what you mean, but that would not be a valid solution for issues like yours. clicking repair wallet was not what solved your database corruption, as wallet repair only manipulates walelt.dat while in your case it was the chainstate/* databases what was corrupted
chainstate corruption is only solved by resyncing/reindexing/bootstrapping

On 16 Jun 2021, at 13:14, yraen69 @.***> wrote:
Hi aguycalled,
thought my experience was pretty clear, end user wise it wasn't great. Yes it was a chain corruption issue. If you look at my screenshot the error box pops up within a couple of seconds of the wallet finally loading. All you can do is click OK and the wallet crashes.
This is BAD. You cannot get to FILE --> Repair Wallet.
I had to load up all of my CPU cores to make my machine run SLOW enough for me to have enough time to get to the FILE --> Repair option and click that before the error message pops up crashing my wallet.
That 'Error reading from database shutting down' message should NOT be a fatal one that instantly closes the wallet and gives you not option but to click OK.
It should instead actually give you the option to repair the wallet ON that error popup or at least grey out the main UI and let you at least click FILE --> Repair wallet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi aguycalled,
sure do whatever you like with this ticket. My fix was to click File --> Repair Wallet. That's all I did and about an hour later my wallet worked again.
I stand by my recommendation, that error should not be fatal in my original screenshot it should instead prompt you to repair whatever is broken, I don't particularly care if it's the wallet or the chain, as an end user I shouldn't have to care.
The wallet should be very very difficult to get into an unworkable state that just crashes and crashes if you want to build adoption.
regards
Luke

i agree with you about the importance of improving user experience.
From my point of view the solution is more about educating users who are non-tech savvy in using light wallets instead of running full nodes. A full node will always require technical maintenance - someone who is not skilled enough to run a full node will eventually feel disappointed and have a bad experience, and this not only applies to Navcoin. Our problem is that we offer Navcoin Core as the wallet de facto, so it's the option most of the users choose.
This is something we are currently working to solve, by upgrading our website to adequate the narrative by explaining well what each wallet is used better for and showing light wallets as the first choice; by adding to our light wallets some of the functionality that is currently missing (like xNAV private transactions); and with the release of NavcoinJS, a SDK for developers to easily build wallets on top of our network.
This is our focus currently. I personally think adding extra layers of complication to Navcoin Core's code in sake of automating the solution of some issues won't be as benefitial for the project, the performance of our wallets and the experience of our users as what I aforementioned.

Thank you for your concise and excellent feedback, I'm glad to see the future direction and what's being worked on for light wallets. Agree it's the future. Your time is appreciated! Long time NAV supporter myself, I think it's got a great future.
Given what you've said here I'll close this issue and look forward to what's coming up in the future!


Update webpack configuration

Upgrade to latest webpack and include commit hooks. Included:

linting with eslint
code formatting with prettier
transpiling via babel

Actually this PR would include the functionality of https://github.com/javve/list.js/pull/610 and https://github.com/javve/list.js/pull/611.

Thank you so much @boidolr for your pull requests and sorry for not replying to you earlier. With the recent release of v2.0.0, I've updated the webpack configuration to transpile with babel and I've added prettier as a dependency + included a prettier-config.
I've also included source maps in the same way as you suggested in #610 :)
With that I'll close this PR. Feel free to have a look in my new webpack config and see if you have any new suggestions. Configurating webpack is not my strong side 😅

Are you interested in getting linting and/or commit hooks for prettier etc set up?
Now that babel is set up you could also take advantage of let/const to make the code safer - this could be enforced by eslint, for example.

I think it would be nice with commit hook for Prettier!
...and maybe some nice linting as well. As long as it works well with Prettier :)


HDDS-1908. TestMultiBlockWritesWithDnFailures is failing

What changes were proposed in this pull request?
Multi-block writes tests are failing most of the time because Ratis leader election timeout is about the same length as the client retry timeout (5 times 1 second).  This frequently caused an entire pipeline to be excluded (by KeyOutputStream.handleException) just because client gives up before leader is elected.  There are only 6 nodes in TestMultiBlockWritesWithDnFailures test, 2 of which is shut down as part of the test.  Thus, if this happens, subsequent write fails because new block cannot be allocated.
This change decreases leader election timeout and increases client retries.  It is basically an extension of HDDS-1780.
Additional changes:

move testMultiBlockWritesWithIntermittentDnFailures to TestMultiBlockWritesWithDnFailures
remove unused maxRetries member
call cluster shutdown() regardless of test success/failure (see also HDDS-1949)

https://issues.apache.org/jira/browse/HDDS-1908
How was this patch tested?
Ran both test classes 10+ times, without any intermittent failure.
[INFO] Running org.apache.hadoop.ozone.client.rpc.TestFailureHandlingByClient
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 157.086 s - in org.apache.hadoop.ozone.client.rpc.TestFailureHandlingByClient
[INFO] Running org.apache.hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.308 s - in org.apache.hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

/label ozone

@mukul1987 I wanted to keep the original retry count in TestFailureHandlingByClient, but change it for the multi-block write tests.  Also, @bshashikant moved testMultiBlockWritesWithDnFailures in HDDS-1780, and I thought that testMultiBlockWritesWithIntermittentDnFailures belonged to the same class.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
74
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
604
trunk passed

+1
compile
369
trunk passed

+1
checkstyle
72
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
963
branch has no errors when building and testing our client artifacts.

+1
javadoc
174
trunk passed

0
spotbugs
459
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
679
trunk passed

_ Patch Compile Tests _

+1
mvninstall
556
the patch passed

+1
compile
374
the patch passed

+1
javac
374
the patch passed

+1
checkstyle
78
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
745
patch has no errors when building and testing our client artifacts.

+1
javadoc
185
the patch passed

+1
findbugs
714
the patch passed

_ Other Tests _

+1
unit
357
hadoop-hdds in the patch passed.

-1
unit
2135
hadoop-ozone in the patch failed.

+1
asflicense
42
The patch does not generate ASF License warnings.

8307

Reason
Tests

Failed junit tests
hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1282/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1282

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 912b3b8abb04 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e4b538b

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1282/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1282/1/testReport/

Max. process+thread count
5297 (vs. ulimit of 5500)

modules
C: hadoop-ozone/integration-test U: hadoop-ozone/integration-test

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1282/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thanks @adoroszlai for working on this. The change looks good to me. +1

Thank you @bshashikant for reviewing and committing it.


Volume control for adjusting volume levels

I think the volume control present is for mute/ unmute audio. But can we have a volume control for adjusting volume controls as well?

just in case you're stuck on this or other people are, this is what I did:
@ViewChild("player") player: MatAdvancedAudioPlayerComponent;

public getBasePlayer(): any{
    return this.player?.player?.nativeElement;
  }

  public setPlayerVolume(value: number){
    this.getBasePlayer().volume = value/100
  }

and then i just added a slider that calls the set method.

Fixed in v12.0.1


Small amounts of USD equivalents lest than 1 cent should be shown "like < 1 cent" not "0 USD"

Current:

Expected:

checked on master 5.0.9426.3029


Feature request: customizable tree layout

Left: NERDTree,  Mid: nvim-tree.lua,   Right: NeoTree
It would be great if neotree can support customization tree layout. For example, I personally prefer the style of nvim-tree.lua (or coc-explorer) where a fancy unicode characters is used to denote the expanded tree. Compared to that, the style of NERDTree and NeoTree seem less intuitive for me.
NeoTree follows the default style of NERDTree, but it has another problem: the indent align is not proper. This is more noticable when one has some indent level guide plugin.  I have a tabsize of 4 (&sw = 4) in this example -- somehow it was supposed to be 2 but I just did not have such config (although the plugin itself might want to add buffer-specific options). Please compare with that of NERDTree. It might be fixed either if (i) there is no a padding (in one space character) on the left, (ii) if no space/tab is used with different tree drawing style (like nvim-tree), or (iii) I just don't use the indent-blankline plugin.

In my opinion, adding some configurable option/feature to choose which tree drawing style to be used would be great, but even if an user chooses the current default style the misaligned indentation would need to be fixed.

For the folder icons, that is configurable by setting the folder_open and folder_closed properties on the icon component, see: https://github.com/nvim-neo-tree/neo-tree.nvim/blob/caa64cf0e43cf141bc6d34ff6216c1ab2611d75c/lua/neo-tree/defaults.lua#L140
The problem with the indent alignment is that I pad the window with 1 space because I don't show indent lines on the tree and to me it looks better with the padding. I can certainly make that configurable. There is also a PR that is almost complete to add indent guides. I think that is stalled but I'll finish it up and get it merged.

This should be handled with the changes in #131  which are now in the latest release. You should be able to get what you want with this config:
      require("neo-tree").setup({
        default_component_configs = {
          indent = {
            indent_size = 2,
            padding = 0, -- extra padding on left hand side
            with_markers = true,
            indent_marker = "│",
            last_indent_marker = "└",
            highlight = "NeoTreeIndentMarker",
          },
          icon = {
            folder_closed = "",
            folder_open = "",
            trailing_slash = true,
            default_icon = "*",
          },
          ...

If you have the icon component configured in your renderers as well, those settings will merge and take precedence over the default_component_configs where they conflict.
The indent component is brand new.

Thanks, the new feature works very well for me.
One minor issue: Has the default_icon changed? It was * previously, and now it is just a blank, which confuses indent guide again.

I moved the default settings from the individual renderers to the global_component_config section, so you may have lost it in the transition. If you use the config I posted above then it should still apply as "*". Of course, even without that the true default is a space " " anyhow, so the spacing should be preserved.
I never actually saw the default icon getting used on my computer, web-devicons has always supplied an icon for every file. I'm suprised to see that your Makefile used the default in the screenshot above.

Ok so this seems to be a typo. You probably have meant
 icon = {
-  default_icon = "",
+  default = "",
 },

in the config (README, docs, etc.)

🤦♂ Good catch, thanks for finding that!

While it works, I would like to know why with_markers = true, is needed? It took me some time to realize that I have to also set this option to true to show the markers.

@nyngwang Indent makers are just one of the possible features of indent. The other configurations exposed here are how many spaces to indent and how much padding to add.
Not everyone likes have indent markers so the default is false.

Got it!


NatPunchModule Reliability

Do you currently use the NatPunch feature in production?  I've written a small client -> server -> client command line demo to test this feature and it doesn't seem to be too reliable at the moment.  I'm running into two issues.
1.) Dropped datagrams.   If the two clients receive the HandleNatIntroduction from the server, there is still a chance that the NatPunchMessage will fail to arrive.   Since your demo and the way the NatPunchModule is written is all done with single unreliable datagrams, the chance of a successful punch is very low.
2.) On Successful NatPunchMessage arrival, if both clients are listening with NatIntroductionSuccess and both try to do client.Connect(Endpoint), sometimes the two clients will get stuck sending each other "ConnectRequest" packets and not handle the ConnectAccept message.
If this is still a demo feature, I'm try to add a few reliability features and provide sample code of it working.  We have some experience doing this with our own library.  Otherwise, I might be attempting to use your library incorrectly and maybe you can give me some feedback.
My proposal is to add another event for "HandleNatIntroduction" success so the application can decide how often and how much to send the internal/external punch.  Usually if you get to this point in the negotiations, spamming the punch packet a few times should increase the chance for punch success.  In our experience, the punch packets need to arrive almost at the same time on two clients, so sending just one rarely works in a production environment.
Let me know what you think!  Thanks sharing such a great library.

@dt665m Hi!
NAT punch packets is unreliable by design. You must control this by hands. Punch example resends NAT punch packets if peer requests them (small simple reliability).

Do you currently use the NatPunch feature in production?

Yes)

Yes I understand its unreliable by design, our library does something very similar.  I would like to know for your use case, do you have your clients request the NatIntroduction, which will trigger a NatPunch "N times until giving up"?
In your production experience, how often does this succeed and how big is your "N"?

I would like to know for your use case, do you have your clients request the NatIntroduction, which will trigger a NatPunch "N times until giving up"?

Yes)

In your production experience, how often does this succeed and how big is your "N"?

It depends on your needs. In one mobile game that use LiteNetLib we send NAT requests 2-3 times per second in 5-10 seconds.

Thanks for the feedback.  After turning on DEBUG_MESSAGES, I'm seeing that punchthrough works most of the time, but sometimes two clients will get stuck in "ConnectRequest" loop.  They are both able to send to each other but both clients send the ConnectRequest until MaxConnectAttempts.
This is on 0.7.5.  Any idea why this happens?

Here's the output of the two clients:
https://pastebin.com/p5BNBpBQ
https://pastebin.com/yG01p3Hb


Uplifting ui

Adding a more interesting background and a header to modernize UI

No local DB creation for further analysis for "analysis"-page. Just blueprint analysis.


Session class improvements

Session class currently extends Session class in Toolbox. This is problematic as the class breaks the basic rules of inheritance by not calling parent constructor when creating the object, but later in init().
It would be better to change the class to be wrapper class instead and just forward the method calls or to get rid of init() function and do the work in constructor instead.

Done in 1.4


Page buttons overflow issue fixed.

Fixes Issue
Closes #969

Changes proposed
Page button overflow fixed and also merge conflict causing error in website fixed.

Screenshots

Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

Note to reviewers

Please resolve the merge conflicts

@PoorviShetty I've fixed the conflicts. Kindly check.


The project doesn't work with wokwi microsd

wokwi is an ESP32 simulator. And it supports a FAT16 microSD card. However, VolumeManager::open_volume always returns the following error:
Error::FormatError("Partition type not supported")

I tried different volume numbers, same result. What might be the issue? Have you tried using the project with wokwi? Is it possible that their FAT16 is something esoteric?

Seems like it is fixed in #165! I'll be waiting for the release 🤞🏿


fix/bullmq ttl

@shubhampatwa  Maybe we should name oneDaySecond something like oneDayInSeconds to avoid confusion. Otherwise, LGTM


fix: #135 - case-sensitive paths on a case-insensitive filesystem

fixes #135
combine Bps.yml and bps.yml, Through.yml and through.yml

@gaurav-nelson can you confirm it works as expected?

Thank you @themr0c fixes the issue.


Add onKeyDown and onKeyPress event handlers to the input field

Checklist

[x] All tests passing
[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary
[x] Commits and PR follow conventions

Thank you for your PR! But I'm not completely fine with the fact that we have the keyDown event that is handled in two areas of the component. @Scarysize what do you think?
Anyway, the new props need some documentation. And it should be clearly mentioned that we have this special case for event propagation in the component. I would suggest a whole new paragraph in the readme.

heh, man, why did you ask for pull request then if you aren't sure about it?

First, I did not ask for a PR, my colleague did. We work at the same company but are different persons with different opinions. I just put my concerns in here.
Second, from my understanding @ro-ka said that the keyDown event is already in use but the keyPress event could be used. And that's the same thought that I addressed.

I've deleted onKeyDown event handler, onKeyPress has left

Hey @antoniopuero. Thank you for the changes. That looks very good to me. Can you add a description to the README.md please?

Readme has been updated, translation could be weak though

Ok for me. @Scarysize it's your turn. Merge when ready.
@antoniopuero Thanks again!

no worries, sorry for being a douchebag :)

Thanks!


Fix Faker.Internet.remove_special_characters/1

Changes
Faker.Internet.remove_special_characters/1 didn't actually remove special characters, as the sigil wouldn't match. I've also updated the tests.
To validate, inside an iex repl:
iex> Regex.match?(~r/('|")/<EMAIL_ADDRESS>true
iex><EMAIL_ADDRESS>~s('"))
false

I've added:

[x] CHANGELOG.md

Closes #216

Thank you @JamieREvans, this been fixed earlier in #212.

@igas the tests still aren’t aren’t fixed in #212, though.


Tagalog Language Fix

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Changes primary and secondary languages from Filipino to Tagalog
Issue Number: #6286
What is the current behavior?
Enum is not good for "fil"
What is the new behavior?
Now we have tagalog languages supported.

#6286

This change would require an update in Transifex to rename the translation project from fil to tl.
Tom, you know how?  Hopefully a rename is possible without having the re-translate everything.

Just copy it all to filipino to tagalog @infinite-persistence

Filipino is based on tagalog anyway @infinite-persistence

Yes, rename/copy was what I was saying.  The concern was on the process in Transifex.

The last request to remap the Chinese languages took a while -- not sure what the hiccup was.
When switching from ja_JP to ja, there were 2 projects being worked on independently instead of being copied over.

These gave me an impression that Transifex is preventing the copy, but I'm not sure.  Nah, it shouldn't be that inefficient.

Yes, rename/copy was what I was saying. The concern was on the process in Transifex.

The last request to remap the Chinese languages took a while -- not sure what the hiccup was.
When switching from ja_JP to ja, there were 2 projects being worked on independently instead of being copied over.

These gave me an impression that Transifex is preventing the copy, but I'm not sure. Nah, it shouldn't be that inefficient.

thats sus

#6286

We will need your help for transifex probably @tzarebczan


client incomplete

i feel like this is incomplete, none of the headers or the request type is passed into netty?
https://github.com/plasmaconduit/edge/blob/master/src/main/scala/com/plasmaconduit/edge/http/client/HttpClientImpl.scala

Closed by #2


Address Dependabot security warnings

It appears Dependabot has flagged some packages as requiring security updates.

I fixed the easy ones. If you know how to fix any of the remaining ones, please go for it

Thanks.  Looks like they are all stuck on react-scripts 5.0.1 - not sure if there is newer that can be used

#1799 fixes them for machenmusik/nerfstudio - but could use more testing.


[Feature Request] Support links to open local files in an external app

Attach (recommended) or Link to PDF file here:
See latest page of document
Configuration:

Web browser and its version: 109.0.1
Operating system and its version: Windows 10
PDF.js version: I can't find PDF.js version, it's packaged with Firefox 109.0.1
Is a browser extension: No

Steps to reproduce the problem:

Open an PDF page with a hyperlink to run a file.
Hyperlink is not clickable.

What is the expected behavior? (add screenshot)
Link should be clickable, and should be able to open local file from an absolute o relative path with default app or show a list of options like when you open a file on browser. This is very useful when you want to make a presentation with PDF format, and you need to play a video or run some app.

Link to file on PDF.js is not clickable
If I try to open a APK file in Firefox, and what would be able to do PDF.js

What went wrong? (add screenshot)
Link to local file was not clickable. I add some screenshots about what is happening in Foxit Reader, which is able to open this. (Note that Print Screen doesn't show mouse, but it is clickable)

Foxit Reader clickable link
Foxit Reader option to select open external app

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

This is, for all intents and purposes, a duplicate of e.g. #12415 and bug 1678914.


odo push doesn't propagate file deletions

How to test :

Create a component with a local source
Push the changes
Delete a file from the source
Push again

Actual behaviour
The deleted file remains in the pod after the push
Expected behaviour
The deleted file should be removed from the pod.
Notes from @kadel
For delete propagation and partial update to work in  odo watch  we use a small hack.
Inside the builder image we first backup source files before executing assemble script and then [restoring] it.
Note that due to this files has to be deleted in multiple locations - https://github.com/openshift/odo/blob/8a5950720f74ddf6a4c8bbbab449223eb592e48e/pkg/occlient/occlient.go#L3305

There is another part to this, that we need to also handle properly.
odo component create ..
touch somefile
odo push
echo "somefile" > .odoignore
odo push

Now the question is what we should do in this case.
Should somefile be deleted from the container if it is ignored?
Or should it just be ignored. That means that if user wants to delete a file that is already pushed and it is it odoignore, he/she will have to remote it from the odoignore first and then run push, and then add it back to ignore.

So with some testing, odo watch works perfectly. The problem is indeed odo push that doesn't propagate deletions (we don't even have the code added for it).
~/nodejs-ex  master ✗                                                                                239d ✖ ◒  ⍉
▶ oc rsh nodejs-hjig-app-1-9r6tx ls /tmp/src
README.md  foobar      helm       package.json  tests
foo.txt    foobarrrrr  openshift  server.js

~/nodejs-ex  master ✗                                                                                239d ✖ ◒
▶ rm foobarrrrr

~/nodejs-ex  master ✗                                                                                239d ✖ ◒
▶ oc rsh nodejs-hjig-app-1-9r6tx ls /tmp/src
README.md  foo.txt  foobar  helm  openshift  package.json  server.js  tests

(when using odo watch in the background)
I'll take this up and implement the new feature for odo push.

Update:
This issue relates to https://github.com/openshift/odo/issues/1788 and further discussion will take place there... We need a solution to detect what files have been changed and what hasn't.

If we think about this problem, it can be considered as passive file change monitoring. We cannot have a watch on our directory like we did for odo watch. Which means there are two approaches we can consider
1 - have a state local which helps us detect the change
2 - compare the remote files with local files and sync the differences ( like rsync )

This was unblocked by https://github.com/openshift/odo/pull/1849
/remove-label status/blocked

Hey @mik-dass
Question, as I'm having a brain fart over here trying to implement this.
As of right now, we have the odo-file-index.json.
In order to see what has been deleted, I was thinking of:

Generating another json file
Comparing the two and see what has been changed.

The problem is that some projects have thousands of files (think golang projects).
How do you suggest we compare the two? Is there an algorithm you may have come across when implementing the walker function?

@cdrage I have already implemented the file deletion part here https://github.com/openshift/odo/blob/4929e494b3ae97ebe6ffd3f2cb47b35e837fd75d/pkg/odo/cli/component/common_push.go#L186. The list already contains the list of the deleted files filtered according to the glob rules in .gitignore or .odoignore
Even the e2e test was written for deletion https://github.com/openshift/odo/blob/4929e494b3ae97ebe6ffd3f2cb47b35e837fd75d/tests/integration/cmd_push_test.go#L88. You just need to modify it a bit.

@mik-dass Thanks for the guidance, I'm going to implement it with your advice :+1:


Add Vuetify

ACM Website
Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.
Before opening a new issue, you may find an answer in an already closed issue.
Issue Type

[ ] Bug
[x] Feature

Description
Add Vuetify to the website
(Add images if possible)
Steps to reproduce (if applicable)
(Add link to a demo on https://jsfiddle.net or similar if possible)

Vuetify PR Merged, Closing Issue


DS-3419

lowered the version of grunt-contrib-handlebars to 0.9.3 to resolve conflicts on the handlebars version in Mirage2.
https://jira.duraspace.org/browse/DS-3419

Note, this change has been reverted in #1739, as it also increases the Handlebars version to 4.


[USERSNAP] Search on the dRep Directory page doesn't work.

Taken at: https://gov.tools/dashboard
Fields:

Add a comment: Search on the dRep Directory page doesn't work.

Browser: Chrome 128 (Windows 10)
Screen size: 2560x1440
Open #119 in Usersnap
Powered by Usersnap.

duplicate https://github.com/IntersectMBO/govtool/issues/1893


[Performance]: Multi-node Pipeline Parallel double bandwidth, no change in performance

Misc discussion on performance
I've been running some simple tests on multi-node parallel pipeline with NCCL. I doubled the bandwidth between the nodes but saw no increase in t/s or throughput. I tested with 400Gbps and 800Gbps between nodes and was getting the same t/s, although nccl-tests showed the 2x bandwidth between GPUs.
Questions:

What would be the bottleneck in multi-node parallel pipelines, if not inter-node connectivity?
What other tests or profiling can be done to figure out the bottleneck on parallel pipelines?
Are there currently any benchmarks in vllm (such as benchmark_throughput.py or benchmark_latency.py) that can be run with --pipeline-parallel-size (required Async: Pipeline parallelism is only supported through AsyncLLMEngine as performance will be severely degraded otherwise.)?

Environment:
(2) x GH200 nodes (aarch64) - 800Gbps Ethernet between nodes
Model: L3-70B-Instruct
Test 1:
(4)x 200Gbps Connections (800Gbps total)
NCCL-Test:
Execution Command
mpirun -np 2 -host localhost,<IP_ADDRESS> ./build/{all_reduce_perf,all_gather_perf,alltoall_perf} -b 512k -e 1024M -f 2 -g 1

NCCL Test (all_reduce_perf):  algbw = 70.83GB/s, busbw = 70.83
NCCL Test (all_gather_perf):  algbw = 137.76GB/s, busbw = 68.88
NCCL Test (alltoall_perf):  algbw = 47.32GB/s, busbw = 23.66
VLLM Test:
(Using Open WebUI and OpenAI API)
python -m vllm.entrypoints.openai.api_server --model /models/Meta-Llama-3-70B-Instruct --pipeline-parallel-size 2 --distributed-executor-backend ray

Logs:
INFO 07-20 15:57:52 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.2%, CPU KV cache usage: 0.0%.
INFO 07-20 15:57:57 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.3%, CPU KV cache usage: 0.0%.
INFO 07-20 15:58:02 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.4%, CPU KV cache usage: 0.0%.

Test 2:
(2)x 200Gbps Connections (400Gbps total)
NCCL-Test:
Execution Command
mpirun -np 2 -host localhost,<IP_ADDRESS> ./build/{all_reduce_perf,all_gather_perf,alltoall_perf} -b 512k -e 1024M -f 2 -g 1

NCCL Test (all_reduce_perf):  algbw = 45.42 GB/s, busbw = 45.42 GB/s
NCCL Test (all_gather_perf):  algbw = 91.32 GB/s, busbw = 45.66  GB/s
NCCL Test (alltoall_perf):  algbw = 49.29 GB/s, busbw = 24.64 GB/s
VLLM Test:
(Using Open WebUI and OpenAI API)
python -m vllm.entrypoints.openai.api_server --model /models/Meta-Llama-3-70B-Instruct --pipeline-parallel-size 2 --distributed-executor-backend ray

Logs:
INFO 07-20 17:44:20 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.3%, CPU KV cache usage: 0.0%.
INFO 07-20 17:44:25 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.4%, CPU KV cache usage: 0.0%.
INFO 07-20 17:44:30 metrics.py:295] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 21.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.5%, CPU KV cache usage: 0.0%.

Start-up Logs showing nccl==2.21.5 is used during inference.
INFO 07-20 17:27:16 api_server.py:212] vLLM API server version 0.5.2
INFO 07-20 17:27:16 api_server.py:213] args: Namespace(host=None, port=8000, uvicorn_log_level='info', allow_credentials=False, allowed_origins=['*'], allowed_methods=['*'], allowed_headers=['*'], api_key=None, lora_modules=None, prompt_adapters=None, chat_template=None, response_role='assistant', ssl_keyfile=None, ssl_certfile=None, ssl_ca_certs=None, ssl_cert_reqs=0, root_path=None, middleware=[], model='/models/Meta-Llama-3-70B-Instruct', tokenizer=None, skip_tokenizer_init=False, revision=None, code_revision=None, tokenizer_revision=None, tokenizer_mode='auto', trust_remote_code=False, download_dir=None, load_format='auto', dtype='auto', kv_cache_dtype='auto', quantization_param_path=None, max_model_len=None, guided_decoding_backend='outlines', distributed_executor_backend='ray', worker_use_ray=False, pipeline_parallel_size=2, tensor_parallel_size=1, max_parallel_loading_workers=None, ray_workers_use_nsight=False, block_size=16, enable_prefix_caching=False, disable_sliding_window=False, use_v2_block_manager=False, num_lookahead_slots=0, seed=0, swap_space=4, gpu_memory_utilization=0.9, num_gpu_blocks_override=None, max_num_batched_tokens=None, max_num_seqs=256, max_logprobs=20, disable_log_stats=False, quantization=None, rope_scaling=None, rope_theta=None, enforce_eager=False, max_context_len_to_capture=None, max_seq_len_to_capture=8192, disable_custom_all_reduce=False, tokenizer_pool_size=0, tokenizer_pool_type='ray', tokenizer_pool_extra_config=None, enable_lora=False, max_loras=1, max_lora_rank=16, lora_extra_vocab_size=256, lora_dtype='auto', long_lora_scaling_factors=None, max_cpu_loras=None, fully_sharded_loras=False, enable_prompt_adapter=False, max_prompt_adapters=1, max_prompt_adapter_token=0, device='auto', scheduler_delay_factor=0.0, enable_chunked_prefill=False, speculative_model=None, num_speculative_tokens=None, speculative_draft_tensor_parallel_size=None, speculative_max_model_len=None, speculative_disable_by_batch_size=None, ngram_prompt_lookup_max=None, ngram_prompt_lookup_min=None, spec_decoding_acceptance_method='rejection_sampler', typical_acceptance_sampler_posterior_threshold=None, typical_acceptance_sampler_posterior_alpha=None, model_loader_extra_config=None, preemption_mode=None, served_model_name=None, qlora_adapter_name_or_path=None, otlp_traces_endpoint=None, engine_use_ray=False, disable_log_requests=False, max_log_len=None)
2024-07-20 17:27:16,258 INFO worker.py:1603 -- Connecting to existing Ray cluster at address: <IP_ADDRESS>:6379...
2024-07-20 17:27:16,262 INFO worker.py:1788 -- Connected to Ray cluster.
INFO 07-20 17:27:16 llm_engine.py:174] Initializing an LLM engine (v0.5.2) with config: model='/models/Meta-Llama-3-70B-Instruct', speculative_config=None, tokenizer='/models/Meta-Llama-3-70B-Instruct', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=8192, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=1, pipeline_parallel_size=2, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None), seed=0, served_model_name=/models/Meta-Llama-3-70B-Instruct, use_v2_block_manager=False, enable_prefix_caching=False)
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
INFO 07-20 17:27:20 utils.py:737] Found nccl from library libnccl.so.2
INFO 07-20 17:27:20 pynccl.py:63] vLLM is using nccl==2.21.5
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:27:20 utils.py:737] Found nccl from library libnccl.so.2
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:27:20 pynccl.py:63] vLLM is using nccl==2.21.5
INFO 07-20 17:34:54 model_runner.py:266] Loading model weights took 67.6673 GB
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:34:57 model_runner.py:266] Loading model weights took 67.6673 GB
INFO 07-20 17:34:59 distributed_gpu_executor.py:56] # GPU blocks: 6149, # CPU blocks: 1638
INFO 07-20 17:35:00 model_runner.py:1007] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
INFO 07-20 17:35:00 model_runner.py:1011] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:35:00 model_runner.py:1007] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:35:00 model_runner.py:1011] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:35:12 model_runner.py:1208] Graph capturing finished in 12 secs.

Current Environment
Collecting environment information...
WARNING 07-20 21:08:09 _custom_ops.py:14] Failed to import from vllm._C with ModuleNotFoundError("No module named 'vllm._C'")
/vllm/vllm/usage/usage_lib.py:19: RuntimeWarning: Failed to read commit hash:
No module named 'vllm.commit_id'
  from vllm.version import __version__ as VLLM_VERSION
PyTorch version: 2.4.0a0+f70bd71a48.nv24.06
Is debug build: False
CUDA used to build PyTorch: 12.5
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (aarch64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.3
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-6.8.0-1009-nvidia-64k-aarch64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.5.40
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GH200 480GB
Nvidia driver version: 555.42.06
cuDNN version: Probably one of the following:
/usr/lib/aarch64-linux-gnu/libcudnn.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_adv.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_cnn.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_engines_precompiled.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_graph.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_heuristic.so.9.1.0
/usr/lib/aarch64-linux-gnu/libcudnn_ops.so.9.1.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         aarch64
CPU op-mode(s):                       64-bit
Byte Order:                           Little Endian
CPU(s):                               72
On-line CPU(s) list:                  0-71
Vendor ID:                            ARM
Model name:                           Neoverse-V2
Model:                                0
Thread(s) per core:                   1
Core(s) per cluster:                  72
Socket(s):                            -
Cluster(s):                           1
Stepping:                             r0p0
Frequency boost:                      disabled
CPU max MHz:                          3483.0000
CPU min MHz:                          81.0000
BogoMIPS:                             2000.00
Flags:                                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 svesm4 flagm2 frint svei8mm svebf16 i8mm bf16 dgh bti
L1d cache:                            4.5 MiB (72 instances)
L1i cache:                            4.5 MiB (72 instances)
L2 cache:                             72 MiB (72 instances)
L3 cache:                             114 MiB (1 instance)
NUMA node(s):                         9
NUMA node0 CPU(s):                    0-71
NUMA node1 CPU(s):
NUMA node2 CPU(s):
NUMA node3 CPU(s):
NUMA node4 CPU(s):
NUMA node5 CPU(s):
NUMA node6 CPU(s):
NUMA node7 CPU(s):
NUMA node8 CPU(s):
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Not affected
Vulnerability Spec store bypass:      Not affected
Vulnerability Spectre v1:             Mitigation; __user pointer sanitization
Vulnerability Spectre v2:             Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

Versions of relevant libraries:
[pip3] numpy==1.24.4
[pip3] onnx==1.16.0
[pip3] optree==0.11.0
[pip3] pytorch-quantization==2.1.2
[pip3] pytorch-triton==3.0.0+989adb9a2
[pip3] torch==2.4.0a0+f70bd71a48.nv24.6
[pip3] torch-tensorrt==2.4.0a0
[pip3] torchvision==0.19.0a0
[pip3] transformers==4.42.4
[pip3] triton==3.0.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.2
vLLM Build Flags:
CUDA Archs: 9.0+PTX; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    NIC0    NIC1    NIC2    NIC3    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      SYS     SYS     SYS     SYS     0-71    0               1
NIC0    SYS      X      PIX     SYS     SYS
NIC1    SYS     PIX      X      SYS     SYS
NIC2    SYS     SYS     SYS      X      PIX
NIC3    SYS     SYS     SYS     PIX      X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

NIC Legend:

  NIC0: mlx5_0
  NIC1: mlx5_1
  NIC2: mlx5_2
  NIC3: mlx5_3

you can use https://github.com/vllm-project/vllm/blob/main/benchmarks/benchmark_serving.py to benchmark the performance.
how do you double the bandwidth? if it is some infiniband or roce network, make sure NCCL is using it correctly

Doubled bandwidth by adding an additional bluefield-3 card to each server.
I'll mess with the benchmark_serving.py and see if I can get more thorough test results.
Network is a RoCE and validated all infiniband tests and NCCL worked as expected. VLLM shows the use of nccl correctly:
INFO 07-20 17:27:20 pynccl.py:63] vLLM is using nccl==2.21.5
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:27:20 utils.py:737] Found nccl from library libnccl.so.2
(RayWorkerWrapper pid=593, ip=<IP_ADDRESS>) INFO 07-20 17:27:20 pynccl.py:63] vLLM is using nccl==2.21.5

I'm also running inside of docker container (required for aarch64). Not sure if that has affect on bandwidth.

use export NCCL_DEBUG=TRACE to see nccl information. chances are rdma is not used, and nccl is still using socket.

Thanks for the tip!! You were right that IB wasn't being used and NCCL was using socket.
Setting --privileged for the container solved that. However, I'm still seeing the same throughput. I'll do some more testing and report back if I figure out some more optimizations.
Cheers.

Old ticket that I opened and can now be closed.
The original issue came from a misunderstanding of pipeline-parallel vs tensor-parallel. When using pipeline-parallelism, adding additional bandwidth would have no effect. The solution was to use tensor-parallel instead, which significantly increased throughput with additional bandwidth.


Issue #9 - Fix

Maybe not a huge concern since many devices may not fall in this portion of the md pixel range. However, this fix makes the dropdown menu show until the lg breakpoint (rather than md as is currently), but does still display the documentation search at the md breakpoint to use some of the empty space.

@joshwaiam Is the desktop menu breaking at lg? Can you send me a screenshot please? This is what I see at the smallest lg.

I just went to recreate the issue and it is not happening??? I'm not crazy, I swear I saw it before! Either way, cannot reproduce, so I'm going to close this issue. Sorry to waste your time!


Remove unnecessary namespace fields from Batch API

What changed?

These namespaces are not used since
Added Job ID to start batch operation response

Why?

Batch jobs run in Temporal System Local namespace and not in the namespace from requests
returning Job ID can help with making the Job ID in request optional instead of required

This came up after working on https://github.com/temporalio/temporal/pull/3428

Breaking changes

is this something we now can't just remove? should we use placeholders then?


[Toggl Track] Migrate to API v9 before April 1 2023, when v8 will be disabled

Extension
https://www.raycast.com/franzwilhelm/toggl-track
Description
API v8 which is being used by the extension is deprecated since Oct 1 2022: https://developers.track.toggl.com/changes/2022/10/01/api-v8-deprecation
During March 2023 there will be brownouts:

During brownout periods, endpoints will be temporarily disabled and then re-enabled after a few hours. The goal is to help API clients to notice the scheduled unavailability and plan their migration accordingly.

On April 1 2023 the v8 will be disabled and the extension will stop working. I fill it as a feature request, but if we don't fix it before, then it'll become a major bug. 😉
Here is the migration guide: https://developers.track.toggl.com/docs/additional/v8_migration_guide
Anything else?
https://github.com/raycast/extensions/blob/2de651f199d9c46583b3510f72e24b1c42313a9b/extensions/toggl-track/src/toggl/index.ts#L6

Will try to look at this within march. Any PRs on the extension is welcom @rogatty


调整ParseOldQCStorage的json.Unmarshal指针对象

调整ParseOldQCStorage的json.Unmarshal指针对象,使用 json.Unmarshal(storage, old);

Codecov Report

Merging #449 (f8ed21f) into master (fa11371) will decrease coverage by 0.02%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##           master     #449      +/-   ##
==========================================
- Coverage   43.86%   43.85%   -0.02%
==========================================
  Files         149      149
  Lines       13358    13358
==========================================
- Hits         5860     5858       -2
- Misses       6313     6314       +1
- Partials     1185     1186       +1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add support to run a script before backup

Add support to run a script before backup, either globally as in for all games or per game, for example rclone mount driveName, or 7z a -tzip yourfile.zip yourfolder.

I think this should be added to Ludusavi itself instead of just the Playnite extension, so I've opened a ticket over there: https://github.com/mtkennerly/ludusavi/issues/98


Function to pull neso forecast

Create a function to pull the NESO solar forecast
The url is here https://www.neso.energy/data-portal/embedded-wind-and-solar-forecasts/embedded_solar_and_wind_forecast
Would be great if the solar forecast are return as a pandas dataframe, with the following columns

start_utc,
end_utc
solar_forecast_kw

You can start of just by writing a script, and then make it into a function a bit later
Adding a test for this would be super good too

@Seao7 would you be interested in this?

Yeah I would be!

@peterdudfield I have finished writing a script that has functions to fetch the required data. There are 2 functions - one for a simple API fetch and the other based on SQL Query fetch. Have also written a basic test function and compiled the code with Black. However, currently the repo - neso-solar-consumer is empty and option to Fork is unavailable. I am not really sure as to how I can proceed to create a pull request in this case.

Hi @Seao7 , you should be able to pull now?

Have created a pull request. Do let me know if it looks alright. @peterdudfield


Add S3 VersionId parameter to virus-clade-utils function that downloads sequence metadata from Nexstrain

Background
This function in utils/sequence.py downloads the latest genome sequence metadata file from Nextstrain.
At @elray's request, we also want the ability to download this metadata as it existing at a point in time.
To get started, Evan will use the AWS CLI to determine the required S3 object version id, and pass that version id to the download_covid_genome_metadata function.
Definition of done

download_covid_genome_metadata accepts an optional version id parameter
if version id is supplied, that version of the metadata will be downloaded
otherwise, the function will download the most recent version of the metadata

Resolved by https://github.com/reichlab/virus-clade-utils/pull/23


[Improvement]: Use StruckLikeMap instead of Map<StruckLike, T>  for safer usage.

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
There are many usages of Map<StruckLike, T> in the project code. It's not safe for the PartitionData may have a different hash code when with the same partition value, such as this issue #873
How should we improve?
Change all Map<StruckLike, T>  to StruckLikeMap in projects.
In project production files.

In project test files.

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Subtasks
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

plz assign me, i will take it.

plz assign me, i will take it.

Great, we are very happy to accept your contribution.

plz assign me, i will take it.

Feel free to submit your contributions at any time without the need for assignment or permission. We welcome everyone to contribute to this project.


Node.cursor should respect its inputListeners' cursor

Largely based on work in https://github.com/phetsims/ph-scale/issues/215. @jonathanolson and I decided that it would be nice to add a feature to scenery that Node can get its cursor from its input listeners.

In the above commit we removed the unused option PressListener.preferTargetCursor

We got a very good first pass for this today. PressListener.useInputListenerCursor allows for an opt-in to this new pattern of cursor management. This proof of concept was adopted and used in https://github.com/phetsims/ph-scale/issues/215.
From here:

[ ] pressCursor should become a Property
[ ] Ideally this would become an opt out option, but in order for that to happen, many usages of Node.cursor setting would need to be removed (likely >90% of usages of the cursor setter)
[ ] Once we have fully adopted a listener-first cursor strategy, we may be able to remove the || this._pressCursor in https://github.com/phetsims/scenery/blob/3756dc553ca8bd418ee8cc3d1fcf430039feb3b8/js/listeners/PressListener.js#L650 and rely just on the effective cursor. I'm not positive though.
[ ] While working on this, we found that scenery.serialize was very outdated, and so it doesn't currently include effective opacity or this new effective cursor (or enabled for that matter). It likely should.

Over to @jonathanolson to confirm the above work, and to let me know how I can help.

That work sounds correct!


Format static [u64; 256] is incorrect

When using cargo fmt on a file containing the following static slice
static HASH_64_RESULTS : [u64; 256]  = [
    0x9ae16a3b2f90404f, 0xbe6056edf5e94b54, 0xc2a04665ed038d75, 0x94a13d22e9eba49a,
    ....
];

Each value wraps to a new line, this is not a readable format
static CITY_HASH_64_RESULTS : [u64; 256]  = [
    0x9ae16a3b2f90404f,
    0xbe6056edf5e94b54,
    0xc2a04665ed038d75,
    0x94a13d22e9eba49a,
    ....
];

Behaviour is correct for u32 slice.
static HASH_32_RESULTS: [u32; 256] = [
    0xdc56d17a, 0xc0a92754, 0x2a1678b6, 0xd7c992e2, 0x616e1132, 0xfe6e37d4, 0x5145897e, 0xcfea845d
    ...
]

Thanks for sharing, but this is correct so I'm going to close.
Whether or not the elements get wrapped or unwrapped from a vertical layout is dependent upon the length of the elements. The exact value of that threshold was previously a private/internal configuration option, but the next release of rustfmt will include an option that can be used to control this value.
https://rust-lang.github.io/rustfmt/?version=master&search=short_array_element_width_threshold#short_array_element_width_threshold

This is a good news, I'm waiting for the next release :)
Thank you


Create a none-multicast option for Hazelcast

If multicast is not the prefered way of discovery for the environment, then there should be a configurable way for Hazelcast for full TCP/IP cluster

Add support for externalized hazelcast.xml in config folder so that you can change the default configuration with other discovery methods. Also, to support Kubernetes cluster hazelcast-kubernetes plugin has been included in the classpath.


Rebase on top of latest header package changes

Rebase can be done after https://github.com/celestiaorg/celestia-node/pull/1206 is merged.

Resolved in https://github.com/celestiaorg/celestia-node/pull/1304


River Forcing

@abigale-wyatt is working on some python tools to create river forcing input for ROMS. Abigale, I am happy to provide guidance and help with how to include your tools into our object-oriented ROMS-Tools code down the road. (There is no rush, though!) I'm excited you are working on this!

River forcing is now part of ROMS-Tools via #194, #195, #200.


how to connect custom web app to this front end templete

Thanks for opening this issue, @harishsg99. Can you tell me more about your specific requirements? You can build on top of Staart UI by adding Vue components and Nuxt pages, or do you mean using a different backend rather than Staart API?

I mean using a different backend rather that Staart API

I want to convert my ml web app into SaaS App

I mean how to use this template for above use case

It's just a template, you have to make modifications related to whatever your use case is.

It's just a template, you have to make modifications related to whatever your use case is.


glimmer scaffold:customcontrol[model_form] not working

I ran ➜ glimmer "scaffold[photo_processing]"
and later tried and the rest is just to show the app is working.
`glimmer scaffold:customcontrol[model_form]
zsh: no matches found: scaffold:customcontrol[model_form]
photo_processing on  main [!] via 💎 ruby-3.4.1
➜ glimmer run
Launching Glimmer Application: ./bin/photo_processing
Launching Glimmer Application: /Users/gscar/Documents/Ruby/photo_processing/app/photo_processing/launch.rb
2024-12-26 17:33:09.636 ruby[70704:11837380] +[IMKClient subclass]: chose IMKClient_Modern
2024-12-26 17:33:09.636 ruby[70704:11837380] +[IMKInputSession subclass]: chose IMKInputSession_Modern`
Am I missing something? New to Glimmer and not very skilled in Ruby.

On my Mac ARM64 (M2 Chip) Sequoia 15.0.1, I ran this command:
glimmer "scaffold[photo_processing]"

It generated the app and ran it successfully.

I quit the app, and then I entered the directory of the app:
cd photo_processing

Next, I ran this command to launch the app again:
glimmer run

It started the app again, successfully.

So, I am unable to reproduce the issue you encountered.
However, we might be on different platforms and operating systems.
What OS are you running? Mac, Windows, or Linux? What version is it exactly? What CPU (processor) do you have (Intel or ARM)?

and later tried and the rest is just to show the app is working.

That reads like broken English. Could you please say again what you were saying?

zsh: no matches found: scaffold:customcontrol[model_form]

Regarding that error? It happens under zsh (but not bash) if someone runs a Glimmer command without double-quoting the subcommand that follows glimmer (we need to double-quote scaffold:customcontrol[model_form] as "scaffold:customcontrol[model_form]").
Here is the correct way of running this command, which I tried inside photo_processing and it worked:
% glimmer "scaffold:customcontrol[model_form]"
Created photo_processing/app/photo_processing/view/model_form.rb

Thank you Andy for the quick response. I had just figured that out for myself by setting up a new app and noticing the quotes. But the section on Scaffolding is missing the quotes for these commands. I now see that you clarified that in your response. macOS M2
My "broken English" part was just to show that Glimmer was working. I copied from iTerm. Sorry for the confusion.
Looking forward to working with Glimmer. Looks like what I wanted. Replacing Pashua while updating a personal script. I think I'll make an app now.

OK, it's good to know you got things working.
I just updated the README to include double-quotes for all Glimmer scaffolding commands by assuming most people are using zsh not bash.
Happy Holidays!

Thank you. Glad you made the changes.

On Dec 26, 2024, at 6:29 PM, Andy Maleh @.***> wrote:
OK, it's good to know you got things working.
I just updated the README to include double-quotes for all Glimmer scaffolding commands by assuming most people are using zsh not bash.
Happy Holidays!
—
Reply to this email directly, view it on GitHub https://github.com/AndyObtiva/glimmer-dsl-libui/issues/72#issuecomment-2563247852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABB5KEZ57ZHQJXTSPNQDTL2HS3RRAVCNFSM6AAAAABUH5OTASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTGI2DOOBVGI.
You are receiving this because you authored the thread.


Add new device: Pool-Systems IPS-100max.yaml

This will add this new device: Pool-Systems IPS-100MAX
https://www.pool-systems.de/Pool-Waermepumpe-mit-Inverter/Pool-Waermepumpe-IPS-100MAX-Inverter-Premium-Silent-MAX-10KW-COP20.html
This works:

switching between work modes: OFF, HEAT, COOL, AUTO(HEAT/COOL)
switching between preset modes: SILENT, SMART, BOOST
switching between °C and °F
Setting desired temperature for either mode combination (work modes and preset modes)
Getting current temperature
Getting power level in percent
Getting power in watts
binary_sensor indicating if water flows through the heat pump

There are two more datapoints for which I have no idea what they represent.
The heatpump is assumed to be hardware/software by Fairland.

@make-all
Sorry, I have been on summer vacation not being online.
Thanks for considering and fixing!


Simplify Windows build story

https://github.com/grpc/grpc/pull/7012
We are now using mingw to compile grpcio.  This should allow us to simplify our build logic.
#7012
@ctiller

cc #6791 #6797


Rustup to rust-lang/rust#98320

Fixes #332
Signed-off-by: Yuki Okushi<EMAIL_ADDRESS>

@bors r+

:pushpin: Commit cca6e015c9b77bea111c6c6bf7ac7f51802c847d has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit cca6e015c9b77bea111c6c6bf7ac7f51802c847d with merge df6c6f046859a17d73c3247f12f779a84b0285ab...

:sunny: Test successful - checks-actions
Approved by: JohnTitor
Pushing df6c6f046859a17d73c3247f12f779a84b0285ab to master...


ll leetcode solutions added

Contributing
Before read this file please read the README.md file.

Process of Contribution
The process to contribute this repository may be summarized as follows:

You must have a github account to contribute to this project. You if don't have one, then please create one.

Create a fork of problem-solving repository.

Now, clone the forked repository which is under your account(the possible remote url may be: "https://github.com/{your_user_name}/problem-solving") into your local environment using git clone <remote-url> command. TThen, go to problem-solving drectory using cd problem-solving.

Create an upstream to the real project(where you'll send pull request) i.e. https://github.com/reyadussalahin/problem-solving using the command git remote add upstream https://github.com/reyadussalahin/problem-solving.git.

Fetch all the changes from upstream by using the command git fetch upstream.

Now create a branch with the name of fixes or changes you are making(means "the name" should reflect what changes/fixes you are making). An example would be - if you are adding a solution for cf 233B problem, then give the branch name "add-cf-233b". Like this git checkout -b add-cf-233b upstream/main.

Commit your changes in the new branch using git add <modified-file-name(s)> and git commit -m <commit-message>. Replace <modified-file-name(s)> with actual file names and <commit-message> with information about changes.

This step is optional, but it'll increase the probability of accepting you pull requests. Before pushing your changes, you may want to fetch and merge the changes, those were made in https://github.com/reyadussalahin/problem-solving while you were working on your feature. Cause, it is possible that your commit may create a merge conflict or some other ugly errors. But you can easily handle those errors(if there are any) by just pulling changes from upstream. If you want to pull changes from upstream, you have to made sure that there are not extra merge commit is occuring, you are not allowed to create a merge commit, cause it'll create problem in merge history, we need to keep merge history as clean as possible. For you there is a proper guide, please take a look at this article. This will help you deal with the problem. [Note: if this is too much for you, then you don't have to do it. It is an optional step.]

Push the branch with changes to your remote repository using the command git push origin <branch-name>. Considering step(6) the <branch-name> would be replaced by add-cf-233B.

Go to your remote repository and send a pull request to the real project repository i.e. https://github.com/reyadussalahin/problem-solving.

Rules for contribution

A new branch should contain only one fix, or one solution, or one tutorial, or one tutorial fix etc. But never more than one.
To do another contribution, please use another branch.
Clearly write comments about your pull request, about what you've contributed with specific bullet points.

If you are new to git and github:
If you are new, then you may use the following resources to get started very quickly with git and github:

Git Tutorials Playlist - YouTube
The beginner’s guide to contributing to a GitHub project – Rob Allen's DevNotes
Git docs
Or you may use the command line help "git help command_name". Help would be open in terminal or your default browser.

@pri1311 Congratulations 🎉, you're officially a contributor to our problem-solving community. For your future contribution please read the contributing guidelines. Also, please follow the notes given below:

Always name solution filename in Uppercase i.e. Solution.cpp(notice: the first letter S is in uppercase, it's a convention we're following. If you name it in small letters, there would be some problem as Windows considers both S and s as same when considering filenames but Linux think of these as different. So, it's for maintaining consistency across OSs).

Always provide problem related information in the following format:

// problem name: A Simple Task
// problem link: https://codeforces.com/contest/558/problem/E
// contest link: https://codeforces.com/contest/558
// time: (?)
// author: reyad

// other_tags: (?)
// difficulty_level: expert

// put your code here
int main(int argc, char *argv[]) {
    ...
    ...
    return 0;
}

When it comes to author, you should put your name here(we'd prefer if you use your github username which is pri1311). But you can also use other name, But you must use that name in each of your solution.

We encourage you to add necessary comments in your solution, but never add extra comments. We think of extra comments as redundancy and discourage such comments.

Don't worry about the above rules. You'll pick it up with time. Just send pull requests, if there is any mismatch found with the community guidelines we'll fix it and add your solutions.
Congrats again 🎉 🎉 🎉

fixes #26


Add build for linux-aarch64

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Looks like the import aesara issue only appears in the aarch pypy builds.

I'm not sure what's causing this. I'll start by looking for differences in the test environments for linux_aarch64_python3.8.____73_pypy and linux_aarch64_python3.8.____cpython using conda debug.

The other issue appears to be a Windows-specific test script bug.

Looks like this has been addressed in https://github.com/conda-forge/conda-smithy/pull/1724 and so should be fixed in the next release of conda-smithy.

In the cpython aarch64 builds, Aesara is installed to PREFIX, while in the pypy aarch64 builds it's installed to BUILD_PREFIX, and is subsequently ignored during bundling. I'm not sure why this is happening, but I was able to fix the issue by explicitly setting --prefix ${PREFIX} when running pip.

That's a great find!  I'll take a look at it from the Aesara side; there might be some special platform-specific handling involved.

Very nicely done, @jeffreyenos!
Do you have an explanation for 78c7b82? Namely, is this a conda-forge bug, and if so, has it been reported? (I'm mainly wondering if we'll have to revert this file each time we rerender.)

Very nicely done, @jeffreyenos!

Thank you!

Do you have an explanation for 78c7b82? Namely, is this a conda-forge bug, and if so, has it been reported? (I'm mainly wondering if we'll have to revert this file each time we rerender.)

The batch file issue should be fixed in the next release of conda-smithy (see https://github.com/conda-forge/aesara-feedstock/pull/127#issuecomment-1465051416) so going forward shouldn't be an issue.

Thanks so much for the contribution @jeffreyenos! (Sorry I didn't properly read your previous comment.)

Thanks so much for the contribution @jeffreyenos! (Sorry I didn't properly read your previous comment.)

No worries of course -- thanks for merging!


Improve normal smoothing in the SurfaceTool

This fixes #65076 while keeping it possible to generate smooth normals. SurfaceTool.add_smooth_group() has been renamed to .set_smooth_normals() to better explain what it is doing. The new name also better matches the naming of .set_uv(), set_color(), set_tangent() ...

SurfaceTool.add_smooth_group() has been renamed to .set_smooth_normals()

It seems that the method has been renamed from add_smooth_group to set_smooth_group at some prior time. So this PR doesn't make a breaking change, but needs to update the conversion tool's rules.
You also have a couple of style issues, see https://github.com/godotengine/godot/runs/8101475929?check_suite_focus=true.
And you need to run the doctool locally to properly update the class reference. Please don't update it by hand, and use the doctool instead to avoid mistakes. See https://docs.godotengine.org/en/stable/community/contributing/updating_the_class_reference.html#updating-the-documentation-template.
You should also amend your commit message. It should answer the question what this PR does without being too vague or too detailed. For example, you can use the new title of this PR.

Okay, that took some time because I am new with git but I think that should work now.

I'm not sure about this change. Primary it does 2 things:

Changes the default to non-smooth normals
Changes the API from specifying smooth group, to implicitly inferring smooth group

I think that the current approach of specifying a smooth group for each vertex is unnecessarily complex for users who want non-smooth normals. But at the same time, I think this PR takes away a lot of control from the user and makes the experience worse when smooth normals are desired.
I think a better solution would be to add an optional parameter to generate_normals() to force disable smoothing across the whole mesh. That would make it easy for users to have non-smooth normals (generate_normals(true)) but would also allow for more complex combinations of smooth groups if users require it (like in the OBJ importer).

Superseded by https://github.com/godotengine/godot/pull/68034 which fixes the same core issue but keeps the API the same as what we have now


#[docify::hidden]

within any span of code that is being rendered, the item following this should become hidden. This item could itself contain #[docify::export], so you could do:
#[docify::export]
fn foo() {
    let a = 10;
    #[docify::hidden] // makes this item hidden in the parent
    #[docify::export] // makes this item individually reachable via `#[docify::embed("..", bar)]`
    let bar = 15;
}

First portion of this is adding support for #[docify::export] on expr-position items via outer macro pattern of the enclosing #[docify::export] on the parent, then we can hit the other stuff once that capability is in place.
Have that WIP on allow-expr-exports branch


UI enhancement

Total review of UI. make it more clean and stilistc. More modern - bootstrap:ish. Use sub-pixel fonts and graphicon.

Will work on this as a separat track.

This issue will be terminated. There will be no UI overhaul. Instead we will take menu by menu as part of div other issues.


A2DP Support

Hi,
this library and teh dbus support sounds awesome to auto connect devices. I need this on a raspberry pi, but i need the A2DP protocol for receiving/sending audio. Does Mono.Bluez support it, and how to connect. Or do i need to use dbus directly, as i have no idea how to get the audio source in C# via A2DP.

I have not touched A2DP yet, though it is something I plan to add because I need it as well.
In theory the way it would work would be you would define the various Media related interfaces (http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/media-api.txt) and Register/Proxy them on DBus.
You would definitely need the file descriptor support that I added in my dbus fork.  That should get submitted to the dbus-sharp repo eventually either by me or someone else, but for now the only place I know it exists is in my repo.  Note that you also need to run a very new (like within the last month) mono build for it to work, it hasn't made it into a release yet.

Thanks for the reply. I will definetly take a look at it. Seems to be the only way to get it work. A Bluez setup like others did to make it work via pulseaudio is useless for me.
Maybe, if i get it to work before you implement it, i will give you the source code

I did a little research (had not enough time to try in C#) about Bluez implementation.
http://www.lightofdawn.org/wiki/wiki.cgi/BluezA2DP
And:
`#!/usr/bin/python
from future import absolute_import, print_function, unicode_literals
import sys
import dbus
import dbus.service
import dbus.mainloop.glib
import gobject
import bluezutils
A2DP_SOURCE_UUID = "0000110A-0000-1000-8000-00805F9B34FB"
A2DP_SINK_UUID = "0000110B-0000-1000-8000-00805F9B34FB"
HFP_AG_UUID = "0000111F-0000-1000-8000-00805F9B34FB"
HFP_HF_UUID = "0000111E-0000-1000-8000-00805F9B34FB"
HSP_AG_UUID = "00001112-0000-1000-8000-00805F9B34FB"
SBC_CODEC = dbus.Byte(0x00)
#Channel Modes: Mono DualChannel Stereo JointStereo
#Frequencies: 16Khz 32Khz 44.1Khz 48Khz
#Subbands: 4 8
#Blocks: 4 8 12 16
#Bitpool Range: 2-64
SBC_CAPABILITIES = dbus.Array([dbus.Byte(0xff), dbus.Byte(0xff), dbus.Byte(2), dbus.Byte(64)])
JointStereo 44.1Khz Subbands: Blocks: 16 Bitpool Range: 2-32
SBC_CONFIGURATION = dbus.Array([dbus.Byte(0x21), dbus.Byte(0x15), dbus.Byte(2), dbus.Byte(32)])
MP3_CODEC = dbus.Byte(0x01)
#Channel Modes: Mono DualChannel Stereo JointStereo
#Frequencies: 32Khz 44.1Khz 48Khz
#CRC: YES
#Layer: 3
#Bit Rate: All except Free format
#VBR: Yes
#Payload Format: RFC-2250
MP3_CAPABILITIES = dbus.Array([dbus.Byte(0x3f), dbus.Byte(0x07), dbus.Byte(0xff), dbus.Byte(0xfe)])
JointStereo 44.1Khz Layer: 3 Bit Rate: VBR Format: RFC-2250
MP3_CONFIGURATION = dbus.Array([dbus.Byte(0x21), dbus.Byte(0x02), dbus.Byte(0x00), dbus.Byte(0x80)])
PCM_CODEC = dbus.Byte(0x00)
PCM_CONFIGURATION = dbus.Array([], signature="ay")
CVSD_CODEC = dbus.Byte(0x01)
class Rejected(dbus.DBusException):
_dbus_error_name = "org.bluez.Error.Rejected"
class Endpoint(dbus.service.Object):
exit_on_release = True
configuration = SBC_CONFIGURATION
def set_exit_on_release(self, exit_on_release):
	self.exit_on_release = exit_on_release

def default_configuration(self, configuration):
	self.configuration = configuration

@dbus.service.method("org.bluez.MediaEndpoint1",
				in_signature="", out_signature="")
def Release(self):
	print("Release")
	if self.exit_on_release:
		mainloop.quit()

@dbus.service.method("org.bluez.MediaEndpoint1",
				in_signature="", out_signature="")
def ClearConfiguration(self):
	print("ClearConfiguration")

@dbus.service.method("org.bluez.MediaEndpoint1",
				in_signature="oay", out_signature="")
def SetConfiguration(self, transport, config):
	print("SetConfiguration (%s, %s)" % (transport, config))
	return

@dbus.service.method("org.bluez.MediaEndpoint1",
				in_signature="ay", out_signature="ay")
def SelectConfiguration(self, caps):
	print("SelectConfiguration (%s)" % (caps))
	return self.configuration

if name == 'main':
dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)
bus = dbus.SystemBus()

if len(sys.argv) > 1:
	path = bluezutils.find_adapter(sys.argv[1]).object_path
else:
	path = bluezutils.find_adapter().object_path

media = dbus.Interface(bus.get_object("org.bluez", path),
					"org.bluez.Media1")

path = "/test/endpoint"
endpoint = Endpoint(bus, path)
mainloop = gobject.MainLoop()

properties = dbus.Dictionary({ "UUID" : A2DP_SOURCE_UUID,
				"Codec" : SBC_CODEC,
				"DelayReporting" : True,
				"Capabilities" : SBC_CAPABILITIES })

if len(sys.argv) > 2:
	if sys.argv[2] == "sbcsink":
		properties = dbus.Dictionary({ "UUID" : A2DP_SINK_UUID,
						"Codec" : SBC_CODEC,
						"DelayReporting" : True,
						"Capabilities" : SBC_CAPABILITIES })
	if sys.argv[2] == "mp3source":
		properties = dbus.Dictionary({ "UUID" : A2DP_SOURCE_UUID,
						"Codec" : MP3_CODEC,
						"Capabilities" : MP3_CAPABILITIES })
		endpoint.default_configuration(MP3_CONFIGURATION)
	if sys.argv[2] == "mp3sink":
		properties = dbus.Dictionary({ "UUID" : A2DP_SINK_UUID,
						"Codec" : MP3_CODEC,
						"Capabilities" : MP3_CAPABILITIES })
		endpoint.default_configuration(MP3_CONFIGURATION)
	if sys.argv[2] == "hfpag" or sys.argv[2] == "hspag":
		properties = dbus.Dictionary({ "UUID" : HFP_AG_UUID,
						"Codec" : PCM_CODEC,
						"Capabilities" :  PCM_CONFIGURATION })
		endpoint.default_configuration(dbus.Array([]))
	if sys.argv[2] == "hfphf":
		properties = dbus.Dictionary({ "UUID" : HFP_HF_UUID,
						"Codec" : CVSD_CODEC,
						"Capabilities" :  PCM_CONFIGURATION })
		endpoint.default_configuration(dbus.Array([]))

print(properties)

media.RegisterEndpoint(path, properties)

mainloop.run()`

These seems to be a great way to look for the needed values.
I hope it helps - will try to get it work soon

Seems like this project is dead?
If not, i use a new version where i added newest mono/dbus-sharp library. It has support for filedescriptor as UnixFD (i use extension to create OpenAsStream method).
If correctly using the media interfaces i added, A2DP should already work.


Ability to use gutenberg as a crate

It would be an excellent feature to be able to use gutenberg as a crate to:

Pass data generated on the fly by an outer program to the template engine's context and other environment dependent configuration
Automate deployment processes more easily, without needing to install gutenberg in a CI/CD setup
Have it be installed by cargo, so that contributing to a gutenberg website is easy (currently it's a bit complicated to install and setup gutenberg)

You can also use it as a crate as the gutenberg cli is a thin layer over ~15 subcrates. It's extremely unlikely that it will be put on crates.io though, I have no interest in having the subcrates be in crates.io

contributing to a gutenberg website is easy (currently it's a bit complicated to install and setup gutenberg)

You can just drop the binary in the site repository if you want. I think OS package managers are also better than Cargo for that and Gutenberg is available in many of them.


Moving to 1 instruction

Moving to stable releases, we should warn the users if they are using master and let them  know what to do.

On Tue, Jul 10, 2018 at 3:03 PM, Tzach Livyatan<EMAIL_ADDRESS>wrote:

@tzach commented on this pull request.
In README.md
https://github.com/scylladb/scylla-grafana-monitoring/pull/338#discussion_r201315642
:

+Users should move to a stable release. Current release is 1.0, if you are using master
+do git checkout origin/branch-1.0 to switch to 1.0 version and make sure that you are using the latest stable version.
we agreed to point users to the download page

I did, look at the insturctions

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/scylla-grafana-monitoring/pull/338#pullrequestreview-135790822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBRv2LhYuYue4xTE8Ixiduht7rUhYmjks5uFJf3gaJpZM4VGqEp
.


Add small jupyer notebook to be able to run the script in colab

Jupyter is good for experiments, but create also a python script for end to end training and evaluation

But still add a small jupyter notebook to be able to run the script in colab

Jupyter is good for experiments, but create also a python script for end to end training and evaluation

Completed in 8e61d3cb10af96177acf12adb7e192d6eef874d7


How to determine value for PAKS_AES_KEY_STRINGS?

Greetings.
Thank you for sharing this tool.
How does one determine what value to use for PAKS_AES_KEY_STRINGS in MCDSaveEdit\Data\Secrets.cs?
I have searched but have not yet found an answer.

The AES keys get posted in the Dungeoneer's Hideout discord server when MCD gets updated. You'll have to ask them how they get them. I'm not the expert on that subject.

Hey @CutFlame I believe I have the right AES key but it still seems to not be working.
Do I literally just stick the key in here and that's it?
new AesKey("", "")
Doesn't seem to be working for me also. Your latest release works, are you able to provide me the key you used? I can't seem to get access to Dungeoneer's Hideout discord server.
If you need my email it's in my personal website link on my github profile. I'd really appreciate the help.


cf login error -- uaa HTTP Status 400 - request must be over https

Reopening issue: https://github.com/cloudfoundry/cli/issues/862
I'm facing this error with  cf-release 237 and 238 deployed on OpenStack (kilo), here is the some debugging information:
cf:
VERSION:
6.20.0+25b1961-2016-06-29

OS:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"

cf deployment info:
ubuntu@bosh-cli:~$ bosh stemcells
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Acting as user 'admin' on 'my-bosh'

+-------------------------------------------+---------------+---------+--------------------------------------+
| Name                                      | OS            | Version | CID                                  |
+-------------------------------------------+---------------+---------+--------------------------------------+
| bosh-openstack-kvm-ubuntu-trusty-go_agent | ubuntu-trusty | 3262.2* | 7cd94e9e-8f52-4035-9729-550e649e956b |
+-------------------------------------------+---------------+---------+--------------------------------------+

(*) Currently in-use

Stemcells total: 1

ubuntu@bosh-cli:~$ bosh releases
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Acting as user 'admin' on 'my-bosh'

+------+------------+-------------+
| Name | Versions   | Commit Hash |
+------+------------+-------------+
| cf   | 237+dev.1* | 67b9709b    |
+------+------------+-------------+
(*) Currently deployed

Releases total: 1

All the vms in the deployment are running:
ubuntu@bosh-cli:~$ bosh vms
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Acting as user 'admin' on 'my-bosh'
Deployment 'my-cloud'

Director task 1107

Task 1107 done

+---------------------------------------------------------------------------+---------+-----+-----------+---------------+
| VM                                                                        | State   | AZ  | VM Type   | IPs           |
+---------------------------------------------------------------------------+---------+-----+-----------+---------------+
| api_z1/0 (4df8427b-3508-451e-9d44-628d1cc81759)                           | running | n/a | large_z1  | 192.168.X.X   |
| blobstore_z1/0 (e4420585-b8a6-4743-a95a-5ea3d9975b5a)                     | running | n/a | medium_z1 | 192.168.X.X   |
| consul_z1/0 (1542fca8-2311-41ad-9bb6-11d9c8313353)                        | running | n/a | small_z1  | 192.168.X.X   |
| doppler_z1/0 (054a8863-51e2-4f0d-9dfd-b2960705fbe2)                       | running | n/a | medium_z1 | 192.168.X.X   |
| etcd_z1/0 (e830cd60-e3dd-4199-a5ea-dbfc32d72592)                          | running | n/a | medium_z1 | 192.168.X.X   |
| ha_proxy_z1/0 (aa7e6c7e-926e-4580-a589-3f3ebf8967de)                      | running | n/a | router_z1 | 192.168.X.X   |
|                                                                           |         |     |           | 10.20.X.X     |
| hm9000_z1/0 (bf3a4914-5bab-4ec2-a862-838c3cf849c4)                        | running | n/a | medium_z1 | 192.168.X.X   |
| loggregator_trafficcontroller_z1/0 (53bf79c3-88d3-4906-bba6-366dab62e300) | running | n/a | small_z1  | 192.168.X.X   |
| nats_z1/0 (4fd11cca-c20d-4d22-8163-312aa9e92c44)                          | running | n/a | medium_z1 | 192.168.X.X   |
| postgres_z1/0 (8ab06f5a-dfe5-4018-9c9f-0ca8a9bc1fb6)                      | running | n/a | medium_z1 | 192.168.X.X   |
| router_z1/0 (3efde4f8-24e0-4188-b6f0-f9bc1a530697)                        | running | n/a | router_z1 | 192.168.X.X   |
| runner_z1/0 (eae514bb-6b77-480e-82da-2641f3bb9ff2)                        | running | n/a | runner_z1 | 192.168.X.X   |
| stats_z1/0 (edd899b0-7959-46d0-b47a-9fda54f8e876)                         | running | n/a | small_z1  | 192.168.X.X   |
| uaa_z1/0 (cb0c72f4-d481-4712-9cd9-ce6e1688be13)                           | running | n/a | medium_z1 | 192.168.X.X   |
+---------------------------------------------------------------------------+---------+-----+-----------+---------------+

VMs total: 14

However when I try to login using the cf login the uaa service complaints with error:
ssl:  HTTP Status 400 - request must be over https
ubuntu@bosh-cli:~$ CF_TRACE=true cf api https://api.example.com --skip-ssl-validation
Setting api endpoint to https://api.example.com...

REQUEST: [2016-07-09T16:16:36Z]
GET /v2/info HTTP/1.1
Host: api.example.com
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.20.0+25b1961 / linux

RESPONSE: [2016-07-09T16:16:36Z]
HTTP/1.1 200 OK
Content-Length: 550
Content-Type: application/json;charset=utf-8
Date: Sat, 09 Jul 2016 16:17:38 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: f8434b24-8885-4499-495c-08bc65349485
X-Vcap-Request-Id: f8434b24-8885-4499-495c-08bc65349485::0ffd9d20-375d-4305-a7e1-d30c6d96c467

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://login.example.com","token_endpoint":"https://uaa.example.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.56.0","app_ssh_endpoint":"ssh.example.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","logging_endpoint":"wss://loggregator.example.com:4443","doppler_logging_endpoint":"wss://doppler.example.com:4443"}
OK

API endpoint:   https://api.example.com (API version: 2.56.0)
Not logged in. Use 'cf login' to log in.
ubuntu@bosh-cli:~$ CF_TRACE=true cf login
API endpoint: https://api.example.com

REQUEST: [2016-07-09T16:17:40Z]
GET /v2/info HTTP/1.1
Host: api.example.com
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.20.0+25b1961 / linux

RESPONSE: [2016-07-09T16:17:40Z]
HTTP/1.1 200 OK
Content-Length: 550
Content-Type: application/json;charset=utf-8
Date: Sat, 09 Jul 2016 16:18:43 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 3c4df495-66a2-4c81-7040-55f6464d75ab
X-Vcap-Request-Id: 3c4df495-66a2-4c81-7040-55f6464d75ab::9af417a1-5b19-473e-a5ad-0968bc0ab7b0

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://login.example.com","token_endpoint":"https://uaa.example.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.56.0","app_ssh_endpoint":"ssh.example.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","logging_endpoint":"wss://loggregator.example.com:4443","doppler_logging_endpoint":"wss://doppler.example.com:4443"}

REQUEST: [2016-07-09T16:17:40Z]
GET /login HTTP/1.1
Host: login.example.com
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.20.0+25b1961 / linux

REQUEST: [2016-07-09T16:17:40Z]
GET /login HTTP/0.0
Host: login.example.com
Accept: application/json
Referer: http://login.example.com/login
User-Agent: go-cli 6.20.0+25b1961 / linux

RESPONSE: [2016-07-09T16:17:40Z]
HTTP/1.1 200 OK
Content-Length: 471
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Sat, 09 Jul 2016 16:18:54 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 1fe26828-6c47-4ee3-46a3-0972c69fb00f
X-Xss-Protection: 1; mode=block

{"app":{"version":"<IP_ADDRESS>"},"links":{"uaa":"https://uaa.example.com","passwd":"https://console.example.com/password_resets/new","login":"https://login.example.com","register":"https://console.example.com/register"},"zone_name":"uaa","entityID":"login.example.com","commit_id":"5c23774","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-05-04T21:17:48+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-07-09T16:17:48Z]
POST /oauth/token HTTP/1.1
Host: login.example.com
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.20.0+25b1961 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-07-09T16:17:48Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Sat, 09 Jul 2016 16:19:02 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: ec64ab35-e8c8-413c-4a0d-157f4662583c

<title>Apache Tomcat/7.0.61 - Error report</title>
HTTP Status 400 - {"error": "request must be over https"}

type Status report

message {"error": "request must be over https"}

description The request sent by the client was syntactically incorrect.

Apache Tomcat/7.0.61

Server error, status code: 400, error code: , message:

Password>
ubuntu@bosh-cli:~$

I tried setting require_https: false in uaa.yml but then I face a 404 not found error the router complains that the login.example.com route is not found even when route registrar is working fine and announcing the routes to the nats service.
Another thing I tried is enabling ssl in the router but again I face the route 404 not found error.
services running in ha_proxy, router, uaa and api vms:
ha_proxy_z1:
The Monit daemon 5.2.5 uptime: 14h 30m

Process 'consul_template'           running
File 'haproxy_config'               accessible
Process 'haproxy'                   running
Process 'metron_agent'              running
Process 'consul_agent'              running
System 'system_localhost'           running

router_z1:
The Monit daemon 5.2.5 uptime: 14h 15m

Process 'consul_agent'              running
Process 'gorouter'                  running
Process 'metron_agent'              running
System 'system_localhost'           running

uaa_z1
The Monit daemon 5.2.5 uptime: 14h 21m

Process 'uaa'                       running
Process 'metron_agent'              running
Process 'consul_agent'              running
Process 'route_registrar'           running
Process 'statsd-injector'           running
System 'system_localhost'           running

api_z1:
The Monit daemon 5.2.5 uptime: 14h 22m

Process 'consul_agent'              running
Process 'cloud_controller_ng'       running
Process 'cloud_controller_worker_local_1' running
Process 'cloud_controller_worker_local_2' running
Process 'nginx_cc'                  running
Process 'cloud_controller_migration' running
Process 'cloud_controller_clock'    running
Process 'cloud_controller_worker_1' running
Process 'metron_agent'              running
Process 'statsd-injector'           running
Process 'route_registrar'           running
System 'system_localhost'           running

Hi @mponce
It seems /v2/info advertises an authentication url with http, yet UAA returns an error that the request should have been https.
Looks like a configuration issue on the server side, not an issue with the cf CLI?
Please open an issue in the uaa issue tracker, they are more likely to be able to help.
Regards,
Dies Koper
CF CLI PM

Hi @dkoper
You are right this was a configuration issue on the server side, I have updated the manifest properties
properties.login.protocol = https
properties.cc.external_protocol = https

To use https instead of http re-deployed again and this problem is now fixed.
Thank you,
Mario Ponce

Thanks for sharing how you solved it!

Thanks @mponce. I use cf v245 and adding "properties.login.protocol = https" works.
"properties.cc.external_protocol = https" is not needed, maybe it's default to https or I haven't met issues due to "properties.cc.external_protocol = http".
The related CF docs should be updated as well:
https://github.com/cloudfoundry/cf-release/blob/3d203ce/spec/fixtures/vsphere/cf-stub.yml#L77
https://github.com/cloudfoundry/cf-release/blob/3d203ce/spec/fixtures/openstack/cf-stub.yml#L77
The following memory value for dea in the above sample cf-stub.yml is too small (see this bug):
  dea_next:
    disk_mb: 2048
    memory_mb: 1024

The following value works in my env:
  dea_next:
    disk_mb: 20480
    memory_mb: 4096
    num_instances: 2


native dns resolving fails on macOS + Netty + Java when http filter is set

The bug starts happening with 3.97.0. 3.96.1/0 works fine.
Last version also works if http filter is not set, meaning it's related to the port stealing logic somehow.
https://github.com/metalbear-co/mirrord/compare/3.96.0...3.97.0

I have created a reproducible example on this issue here: https://github.com/nabeelpaytrix/mirrord-srv-connections-broken
Please let me know if the instructions in the README are unclear or invalid