IPFS Desktop Revamp

Folllowing IPFS WebUI revamp, we're now focusing on IPFS Desktop. The main points are to make IPFS Desktop's UI more similar to the one we have on IPFS WebUI and also embbed WebUI in Desktop.
Tech Stack

Electron: version 3.0.0 just got out of Beta!
Building:

Electron Forge: they have a version 6.0.0 in Beta which introduces lots and lots of changes since version 5. I push towards using the beta version on this revamp since it will introduce so many changes and If we end up using this, I don't believe it would be worth it to keep on v5 and then have to make so many changes when they release v6 officially.
Or Electron Builder:, which has more stars, which makes me think it's more used and thus more tested. I think we should read the README more carefully and try it out (I'm going to try it this week). It seems promising and maybe easier to use than Electron Forge.

React as our UI framework.

See https://github.com/ipfs-shipyard/ipfs-desktop/issues/661#issuecomment-424706538).

Found some background on the differences between electron-forge and electron-builder: https://github.com/electron-userland/electron-builder/issues/1193

The only ask I have is to plan on having auto-update mechanism from the start.
It could be github-release-based for now, but we should make sure people will follow us on the journey and won't get stuck with old dev version :)

@lidel so far it seems that Electron Builder can better fulfill our needs since its more customizable. We also have to take in account it supports code signing and auto updates.
I've started to create a boilerplate with the new electron version and electron builder but I haven't pushed it yet.
@olizilla @lidel do you think it's better to push it to an orphan branch or just branch out master and clean up the files?

IMO I think its ok to work in PR against master.
Desktop is not as popular/mature as old webui, so we probably don't have to do revamp branch dance and just develop in master.
@olizilla any thoughts on this?

I now remember why I haven't used Electron Builder before: I had an issue with electron-prebuilt-compile I couldn't solve at that time. Now I'm committed to solve this issue: https://github.com/electron-userland/electron-builder/issues/3344

Some more thinking: I believe we should have three main screens:

Welcome Screen: welcome, bienvenue, Bem-vindo, where we show what IPFS is, how it works and what IPFS Desktop can do for you. This shouldn't ask for data to connect to an instance yet.
Menubar: well, our main feature, the menubar! If the user doesn't have a 'favorite' connection or no settings to connect, we have to ask him to set them or to run one with IPFS Desktop itself.
WebUI: WebUI screen! Still don't know how to 'import' it. RIght now, I'm just opening 'webui.ipfs.io' on new branch.

@olizilla I'd really like to hear your thoughts.

❤ I like where this i going!
My guiding principle for this iteration is that we trim the Desktop specific codebase down to just enough code to show a menubar item, and open the Web UI.
We really want a good welcome screen, and I think some of that will be improving the one in Web UI. If we really need a Desktop specific one, then that's ok, but we should share as much as possible with the Web UI.
As for branches, we probably want a dev branch to lay the ground work, and get it all running again with the major upgrades, but I'd fold it back into master as soon as it compiles and runs and shows anything useful. The revamp branch went on way too long, and I don't think desktop has many dependant projects. As long as the README super clearly points people to the last stable release, and that master is unstable, we're fine.
We should focus on automated pre-releases soon after we pull the new branch into master.
I haven't used either of the Electron-* toolchains so it's great that you are doing the research on it. Can you add screenshots and pros and cons here, or arrange a call for us to go through it?

@olizilla yesss!
It would be awesome if we could have the Welcome Screen on WebUI!! A global variable could tell WebUI if it was inside Desktop so we could add some info about Desktop if needed.
Yes, I need to research a bit more about the Electron Builder issue with prebuilt-compile but so far it seemed to me the easiest to use and it compiles a bit faster on my machine.
As soon as I've more info, I'll dump it here or schedule a call.
The code I wrote as for now, already injects window.ipfs, opens the WebUI, creates the menubar, etc. Does not have any visuals nor connects to IPFS, but it's a start. I could dump the Welcome screen if we're going to use it through WebUI (just open a screen to webuiURL#/welcome).

Great. the goal for us on this issue is to define what we want the next version of desktop to look like, and have a bullet point plan for this iteration, that we can break out into issues so we can all jump in and help deliver it as we have time.
One thing that didn't work so well on the Web UI revamp was that a lot of the plan was in my head or was just not defined until the last minute, so it felt like a lot of time I had my head in the code and then had to context switch out to thinking about project management stuff, and all the while I couldn't really give other teams a clear idea of what was left to do to release it.
Lets do a chunk of project management planning up front, so that we don't get too lot later on when we are deep in the code.

Some updates on my mental idea of the structure:
Two Screens

WebUI: works for welcome screen and... WebUI!
Menubar: the famous menubar where you can open WebUI, add more connections and other simple stuff.

Tree Structure

src/ - Uhhh, the source code

index.css - css we will eventually use that isn't part of IPFS CSS
index.js - we have to start the app somewhere
menubar.js - starts up the menubar. (Merge with index?)
hooks/ - hooks that listen on ipcMain events sent from the Menubar.
components/ - nice components that aren't part of our IPFS components library
utils/ or lib/ - files that we don't know where to put or that are used in multiple places.

Two Screens

Web UI: used for welcome screen, files, and all the other features of Web UI.
Menubar: the masterpiece little window.

Tree structure
Please take a look at src on new branch.
Features

Add different IPFS conn configurations
Ability to turn on, turn off, and connect/start to/a different daemon
Ability to open Web UI directly on each page
Which features should the menubar screen itself have?
Should the menubar screen use Redux? is it needed? Or do we have so few actions that we don't need it?

Asking for feedback 😄 Would like to start tackling this tonight and get ir more boilerplated so we can just start developing it.
/cc @ipfs-shipyard/gui

[I have been working on the main process code related to the configurations and multiple connection options. Haven't touched the UI, just moving pieces from the old to the new version that will be helpful. Then we just need to put them together with the UI]

It can run JS-IPFS, GO-IPFS nodes and connect via an API address and inject them to the WebUI. Now I think we just need an interface and make sure that shortcuts (download hash, take screenshot and others are working as they were before).

Shortcuts are working well.

Since it looks like Desktop will get a revamp, can anyone remind me of the goal of this GUI? Is it aimed at beginners -- eg: the IPFS daemon will start with the UI automatically, fancy UI controls and everything --, or is it aimed at developers?
I'm making a website about IPFS and wondering if I should recommend this to beginners, that's why I'd like to know that.
Also, will the new version support the ipfs:// URI scheme?
Thanks

@PaulCombal IPFS Deslkop is intended for everyone and in our vision, it should be the entry point for new users since you get get the most without the command line. This new version will also incorporate the newest release of WebUI, support js-ipfs, multiple daemons and such.

Also, will the new version support the ipfs:// URI scheme?

I think IPFS Companion, the web extension, has that in the works. That's still a feature we have to handle.

@ipfs-shipyard/gui some ideas:

I like the use of On/Off and Settings icons: we use the same in Companion, which makes UIs feel consistent.
The part I am unsure of is the bottom "dial".
Right now it basically copies items present in current Web UI without place to grow.
What will happen when we want to add a new item there? Will we just add another row?

@lidel that's a good question! I think we should have an header (similar to Companion's), an overview of the current connected node, and shortcuts to Web UI's most used pages.
And I agree with you: the most thing I'm unsure about is those Web UI shortcuts: how to place them!?

I too like the on/off switch, settings and the node stats.
I get why we'd want the shortcuts, but I think we could live without them. The WebUI will be the primary focus if a user wants to interact more deeply with the app, so one click more to won't really make a difference. Instead of the shortcuts we can just have a button to open the WebUI no?

Note and FYI, Web UI embedded into Electron doesn't work with File Uploads because Electron sends a different file type to the event! We have to fix this

Here are some mac app menu bar apps that perhaps we can take some ideas from:

Tripmode
Dropzone
Bitdock

Unknown
Fastlane
Guardsense

@fsdiogo thanks for those examples. I really like the blurred background, but I believe it would be a bit difficult to do cross-platform - it is actually something we've talked about in the past.
Here's the current state:

Yeah, I really like it too, but you're right, cross-platform don't know if it works!
I like it. I would change two tings though:

I would put the Open Web UI button with full width like in the Fastlane example above
I'd try to have the arrow and box like the most apps above to make it feel like a floating bar app, instead of just having the rectangle  hanging there

What do you think?

@fsdiogo agree with the floating+arrow thingy. I'll see if I can find a way to do it.
Just unsure about the button with full width, but we might try it!

full width buton looks great, but it also looks a lot less clickable... I vote we keep it looking like a regular button.

Let's continue this discussion on https://github.com/ipfs-shipyard/ipfs-desktop/issues/661.


[Draft] Spill tensor values to SLM to reduce the register requirements.

This is a PoC for spilling the tensor in register to SLM to reduce the register size.
It is not general pass to optimize the kernel for the register size aspect. It only works for the case of 06 tutorial for now.
There are more things need to be finished for performance:

We uses the blocked layout to load the block pointer to reduce the duplication of memory accessing caused by the dot layout. But that is fallback to the gather memory accessing semantic not best performance.

%20 = tt.load %10 {triton_intel_gpu.block_io = "row_major"} : !tt.ptr<tensor<64x64xf16, #blocked>> loc(#loc20)
%21 = triton_gpu.local_alloc %20 {allocation.offset = 0 : i32} : (tensor<64x64xf16, #blocked>) -> !tt.memdesc<64x64xf16, #shared, #triton_gpu.shared_memory> loc(#loc20)
...
%51 = triton_gpu.local_load %21 : !tt.memdesc<64x64xf16, #shared, #triton_gpu.shared_memory> -> tensor<64x64xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #mma, kWidth = 2}>> loc(#loc20)
%52 = tt.dot %51, %49, %cst_2, inputPrecision = tf32 : tensor<64x64xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #mma, kWidth = 2}>> * tensor<64x32xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #mma, kWidth = 2}>> -> tensor<64x32xf32, #mma> loc(#loc59)

There are changes in the RemoveLayout pass. Need to backward propagate the layout before the canonicalizing. Gonna to remove that for decoupling.
The register size is not reduced as expected. Need to check the IGC backend in the register allocation.

To run the CI.

Close this PR as it has no performance improvement for now.


Documentation of example library

Wontfix for now, as the related doc can be found in the readme. Maybe reopen for 1.0


Roll Engine from 51a54c2b729a to 8162e8d86e47 (1 revision)

https://github.com/flutter/engine/compare/51a54c2b729a...8162e8d86e47
2022-01-23<EMAIL_ADDRESS>Roll Skia from cc5601659563 to 5702389f0736 (1 revision) (flutter/engine#31003)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


PostgreSQL databases not shown by default

Is your feature request related to a problem? Please describe.
DBeaver only shows postgres database by default
Describe the solution you'd like
Ideally the option to "Show all databases" would be selected by default (under: Connection settings | PostgreSQL).
Additional context
This is the top voted issue with DBeaver on stack overflow https://stackoverflow.com/questions/54235029/dbeaver-can-only-see-default-postgresql-database-in-connection

Hello, @robianmcd,
This is a known issue. The "Show all databases" option was unchecked on purpose because it was causing too many other issues.


[Run] Custom shortcuts to launch web pages

What i suggest as a addition in the PowerToys Run
I would like have the ability to add custom URL shortcuts and able to launch that URL in my default browser in new tab .
For example
If i add the shortcut g to for URL https://www.google.com/search?q= then when i write

g some-term-i-want-search

what i expect to open an new tab in my web browser to the URL https://www.google.com/search?q=some-term-i-want-search
Similar App
This exist in "Ulauncher app for Linux" that   and you can add custom shortcuts for the URL's that you want and launch your browser at that URL .
How you can add those shortcuts
The way you add the simple , you chose the shortcut and the URL in a simple form .
For the above example the form will be :
Shortcut : g
URL : https://www.google.com/search?q=%s
The %s represents the search term in the URL you want to be placed so the URL work correctly  .

If you'd like to see this feature implemented, add a 👍 reaction to this post.

What browser do you use?
In Chrome and Firefox this is already possible when you type in the address/search bar.

What browser do you use?
In Chrome, Edge and Firefox this is already possible when you type in the address/search bar.

I'm using chrome and i know that functionality ! The suggestion is to be a part of the PowerToys Run so all the process search something somewhere becomes faster than just go to your browser and do the same thing  .
The picture will make it more clear what i suggested !!
Configuration

Search with first shortcut

Search with second shortcut

Search with third shortcut

And when you press enter just opens a new tab in your browser to the exactly search URL that you need to be .

I used this feature in the Wox launcher a lot for e.g. google maps, google translate, duckduckgo, google scholar.

Closing in favor of https://github.com/microsoft/PowerToys/issues/3600 since this is just a subcase of https://github.com/microsoft/PowerToys/issues/3600

Closing in favor of https://github.com/microsoft/PowerToys/issues/3600 since this is just a subcase of https://github.com/microsoft/PowerToys/issues/3600


MM-11556: leverage getDirectAndGroupChannels

Summary
This new selector returns all group messages instead of suppressing ones that were manually or automatically closed.
This also means archived direct and group channels are returned. Direct and group channels aren't archived in quite the same way -- the users in question must be deleted. The behaviour observed with this PR seems reasonable (they show up in the quick switcher), but feedback welcome.
Ticket Link
https://mattermost.atlassian.net/browse/MM-11556
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[ ] Added or updated unit tests (required for all new features)
[x] Has redux changes: https://github.com/mattermost/mattermost-redux/pull/590

Needs to be updated to point at the relevant redux commit.


Issue about hw05 & hw06

In hw06 problem 3, I think that hint '.tale()' should be '.tail()'
In hw05 problem 10, I think that '**2'  in the code below
'data_ci = np.random.normal(loc=?, scale=?**2, size=(n_sample, 100000))'
isn't needed.
Because 'scale' in np.random.normal means standard deviation, not the variance.
(Source : https://docs.scipy.org/doc/numpy-1.15.0/reference/generated/numpy.random.normal.html)

Thanks for the report.
Both of them, you are right. Will correct soon.


Add conditional router tutorial

Fixes #279

After rechecking the pipeline, I don't think using a Multiplexer adds any value here.
Current run():
pipe.run({"prompt_builder": {"query": query, "documents": documents}, "router": {"query": query}})

run() with a Multiplexer:
pipe.run({"prompt_builder": {"documents": documents}, "multiplexer": {"query": query}})

Now that we've decided not to switch to ChatGenerators, there is nothing to change here. @TuanaCelik please take one last look when you can 🙌


When using service-mesh in the pods under test, several tests failed because of istio-proxy container

Hi all,
With this change in dci-openshift-app-agent, I am testing the inclusion of service-mesh (using Aspenmesh) in the pods under test, in order to execute and validate platform-alteration-service-mesh-usage test.
I can confirm the test is working fine and passing. However, there are several tests that now are failing because of the istio-proxy container being deployed in the pods under test. These are the following:

access-control-one-process-per-container
observability-termination-policy
networking-undeclared-container-ports-usage
lifecycle-container-shutdown
lifecycle-liveness
lifecycle-pod-scheduling
lifecycle-statefulset-scaling
platform-alteration-isredhat-release

DCI job where you can see an example of execution.
Having said that, do you think it is feasible to omit istio-proxy container from the tests where containers are check? (because, for example, we can't do anything with lifecycle-statefulset-scaling, I suppose). I mean, while executing these tests, if the container name is istio-proxy, just do not execute the tests on that container. What's your opinion on this?

@edcdavid Do we just want to filter out any containers that are named istio-proxy from the env.Containers in general?

Is there any news regarding this? @sebrandon1 @edcdavid

I'll close this for the moment, if we work again with istio and we continue experiencing issues, I'll let you know


automation tests take longer time

Possible points to look at

Add vault takes ~4m to run
Improve docker build times

https://seleniumjava.com/2015/12/12/how-to-make-selenium-webdriver-scripts-faster/


evaluate what is required to finish the provider consolidation work

evaluate what is required to finish the work in: https://github.com/pulumi/pulumi-hugo/pull/342
this issue is not to finish the work or merge the pr, and is instead to evaluate the level of work required to finish the work

Are we doing this independent of the registry workstream? I am a big fan of the work, but thought that it would be redundant with most of the registry plans, so figured we'd wait.

@joeduffy, i have been advocating that we release this work, its almost done from Dave's description in the pr, and i believe registry is a ways out. i. believe it provides a ton of value that id like to get to users as soon as possible. happy to chat over zoom if im missing context here on why we should wait.

After spending some time looking through the PR today, here's what it's looking like in terms of remaining work. This probably isn't everything, but it should be fairly close. Rough sizings included to give y'all a sense of the overall picture.
In short, there's still a good deal of work to be done -- so my suggestion, given the work we're planning now and how it'll effectively replace everything in #342 and below (and result in yet more URL/redirect churn/risk, etc.), is to close that PR and just focus instead on what's ahead. Nevertheless, here's what it looks like from my perspective:
Functional stuff

Add an API Docs item to the nav for each provider. Small
Devise and draft a release plan. Small

This is necessary because of the coordination that’ll need to be done between pulumi/pulumi (where template updates happen), pulumi/docs (where docs and tutorials will need to be regenerated), pulumi-hugo (which’ll contain the navigational and in-page changes to point to all the new locations), and stakeholders like Paul and others.

Change the location of generated docs and tutorials in pulumi/docs Small
Merge in the changes to pulumi/pulumi to add new frontmatter params to docs templates (to support the new navigation structure). Small
Update docs templates in pulumi/pulumi to add Hugo aliases for all docs. (To make sure we 301 properly.) Small
Regenerate all docs and tutorials to add these new params and aliases. Small
Update a lot of relrefs to make sure all of our links (a) work and (b) link to the right places. Small
Run a full integration build to make sure everything actually builds, looks right, and all the 301s do what they’re supposed to. Share that build and address whatever feedback comes out of that. Small
Execute the release plan. Small

Cosmetic stuff

Add a summary to the top of the SDK page (where the “TODO” text is now). Small
Show the menu items under Packages (Core Providers, Other Providers) as closed by default. (They're open now, which pushes everything below the Packages section off the page.) Small
Resolve the open naming question ("core" vs. "other", "native" vs. "bridged") and apply whatever changes come out of it. Small
Fix the styling on /docs/tutorials (seems broken). Small
Validate that the content changes introduced in the PR are correct. Small

Changes of “providers” -> “packages” in code snippets — is this right? Is what we have today wrong?
Should the new index page be called Packages or Providers? (Nav currently says Packages, but H1 is Providers.)

Closing this as the evaluation is complete.


Return all sections.

Somehow the first of the branches was skipped when returning sections from immutable morphologies.

Wow, thanks for spotting this. I hope that won't have too many consequences.


TipID 1520 - Doing wrong comparison and calculation

Describe the bug
The TipID 1510 is being flagged and reaching a limit but that is not true.
There are two problems
1st one - the comparison:
https://github.com/microsoft/azure-sql-tips/blob/main/sqldb-tips/get-sqldb-tips.sql#L2011
To Reproduce
Steps to reproduce the behavior:

Create a sequence (seen in real life)

CREATE SEQUENCE dbo.testSequence
    AS BIGINT
    START WITH 10000
    INCREMENT BY 1
    MINVALUE -9223372036854775808
    MAXVALUE<PHONE_NUMBER>;

use some values

SELECT NEXT VALUE FOR dbo.testSequence
GO 100

Run the 1520 tip with default configured ration 0.2 (meaning we want to be warned if there is less than 20% available, correct?)

The sequence is flagged with following message:
schema: [dbo], sequence: [testSequence], data type: bigint, start value: 10,000, current value: 10,099, increment: 1, range: -9,223,372,036,854,780,000 to 9,999,999,999, exhausted: No
This happens because using the current calculation the output is 1.08420107626582E-09 (for better readability is 0.000000001084201) which is lower than the 0.2 configured for @IdentitySequenceRangeExhaustionThresholdRatioand, therefore, it appears on the radar.
Expected behavior
It should not flag this sequence.
The calculation may need a 1-"calculation" < 0.2 where 1-"calculation" is the remaining.
In this example, this would translate into 0.999999998915799 which isn't < 0.2 and therefore wouldn't be flagged.
Current:
WHERE -- less than x% of the maximum sequence range remains
      CASE WHEN increment > 0 THEN (maximum_value - current_value) / (maximum_value - minimum_value)
           WHEN increment < 0 THEN (minimum_value - current_value) / (minimum_value - maximum_value)
      END < @IdentitySequenceRangeExhaustionThresholdRatio

Suggestion:
WHERE -- less than x% of the maximum sequence range remains
      (1- CASE WHEN increment > 0 THEN (maximum_value - current_value) / (maximum_value - minimum_value)
           WHEN increment < 0 THEN (minimum_value - current_value) / (minimum_value - maximum_value)
      END) < @IdentitySequenceRangeExhaustionThresholdRatio

2nd one - The calculation
The current calculation isn't looking to the start_value neither to the increment value the sequence.
Continuing with the previous example, the division is done by subtracting max/min value (maximum_value - minimum_value)
If the sequence starts on the minimum value I would agree, but in our example, it starts on 10000 wouldn't be this one the one to consider as minimum_value? Even if it cycles this is the value that will be used.
That said we should have:
StillAvailable: (maximum_value - start_value - current_value)
divided by
TotalAvailable: (maximum_value - start_value)
And that will be a value of: 0.99999899009899 where the current calculation is 0.999999998915799. This gives a difference of 0.000001008816809 more values that actually won't be available.
However, we are still missing the increment variable.
If it increments by 10000 the number of StillAvailable and TotalAvailable will be 10000 times less.
So putting it all together I would suggest (please anyone that confirm my calculations 😄 )
old:
CASE WHEN increment > 0 THEN (maximum_value - current_value) / (maximum_value - minimum_value)

new:
CASE WHEN increment > 0 THEN ((maximum_value - start_value - current_value) / increment) / ((maximum_value - start_value) / increment)

Final question:
What if is_cycling is true? Should this ever be flagged?
Database info
Single database
Additional context
Maybe it is worth double check the TipID 1510 too.

Taking a closer look, I am not sure we should introduce start_value into the calculation. From documentation:

Cycling a SEQUENCE restarts from the minimum or maximum value, not from the start value.

In other words, regardless of where it starts, the sequence still has the entire range defined by minimum_value and maximum_value.

Thanks for the feedback @dimitri-furman .
That said I think we go down to the 1st partial change 👍🏼
I agree with the increment point. I was now thinking that maybe could be nice to have on the output statement something like 'you still have X values before exhausted'. (nice to have != not critical 😄 )

Took another look at this. The original calculation was considering the ratio of remaining numbers (maximum_value - current_value) to the entire available sequence range (maximum_value - minimum_value). The tip would be shown if that ratio dropped below 20%. In your example, maximum_value is 9,999,999,999 and start_value is 10,000, which makes the remaining numbers equal to 9,999,998,999. But that is much smaller than the entire bigint range (18,446,744,073,709,551,616), so the ratio becomes less than 20%, triggering the tip even though there is still a very large range of available numbers.
The fix I am considering is not to use the entire range of bigint as available numbers, and instead use maximum_value - start_value as the denominator (this is actually how 1510 is done). This will show the tip when there is less than 20% of numbers remaining before either exhausting the sequence or rolling over into negatives, both of which are alertable conditions.
I will also add the remaining contiguous numbers to the detailed output because 20% can still be a lot of numbers.

Fixed by #69


[ERROR] UnauthorizedAccessException

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
Good afternoon, please tell me. This error occurred when reinstalling bloxstrap.
System.UnauthorizedAccessException: Access to the path 'C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Logs' is denied.
2024-09-14T20:29:16Z [App::OnStartup] Starting Bloxstrap v2.7.0
2024-09-14T20:29:16Z [App::OnStartup] Compiled Tuesday, 9 July 2024 at 9:03:19 PM from commit a7d2a2c3d5af7137804416ba4e5fbdd27bd10f1e (tag/v2.7.0)
2024-09-14T20:29:16Z [App::OnStartup] Loaded from %UserProfile%\Downloads\Bloxstrap-v2.7.0 (1).exe
2024-09-14T20:29:16Z [LaunchSettings::Parse] Parsing launch arguments
2024-09-14T20:29:16Z [LaunchSettings::Parse] No launch arguments to parse
2024-09-14T20:29:16Z [InstallChecker::Check] Could not find install location. Checking if drive has changed...
2024-09-14T20:29:16Z [InstallChecker::Check] Drive has not changed, folder was likely moved or deleted
2024-09-14T20:29:16Z [JsonManager::Load] Loading from C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Settings.json...
2024-09-14T20:29:16Z [JsonManager::Load] Failed to load!
2024-09-14T20:29:16Z [JsonManager::Load] Could not find a part of the path 'C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Settings.json'.
2024-09-14T20:29:16Z [JsonManager::Load] Loading from C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\State.json...
2024-09-14T20:29:16Z [JsonManager::Load] Failed to load!
2024-09-14T20:29:16Z [JsonManager::Load] Could not find a part of the path 'C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\State.json'.
2024-09-14T20:29:16Z [JsonManager<Dictionary2>::Load] Loading from C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Modifications\ClientSettings\ClientAppSettings.json... 2024-09-14T20:29:16Z [JsonManager<Dictionary2>::Load] Failed to load!
2024-09-14T20:29:16Z [JsonManager<Dictionary`2>::Load] Could not find a part of the path 'C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Modifications\ClientSettings\ClientAppSettings.json'.
2024-09-14T20:29:16Z [FastFlagManager::SetValue] Setting of 'FFlagHandleAltEnterFullscreenManually' to 'False' is pending
2024-09-14T20:29:16Z [FastFlagManager::SetValue] Setting of 'FLogNetwork' to '7' is pending
2024-09-14T20:29:16Z [RobloxDeployment::TestConnection.https://setup.rbxcdn.com] Connecting...
2024-09-14T20:29:16Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/version
2024-09-14T20:29:16Z [RobloxDeployment::InitializeConnectivity] Testing connectivity...
2024-09-14T20:29:16Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/version
2024-09-14T20:29:16Z [RobloxDeployment::InitializeConnectivity] Got https://setup.rbxcdn.com as the optimal base URL
2024-09-14T20:29:16Z [Logger::Initialize] Initializing at C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Logs\Bloxstrap_20240914T202916Z.log
2024-09-14T20:29:16Z [App::GlobalExceptionHandler] An exception occurred
2024-09-14T20:29:16Z [App::FinalizeExceptionHandling] System.UnauthorizedAccessException: Access to the path 'C:\Users\ADCC~1\AppData\Local\Temp\Rar$EXa576.30260\Logs' is denied.
at System.IO.FileSystem.CreateDirectory(String fullPath, Byte[] securityDescriptor)
at System.IO.Directory.CreateDirectory(String path)
at Bloxstrap.Logger.Initialize(Boolean useTempDir)
at Bloxstrap.App.OnStartup(StartupEventArgs e)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Bloxstrap Log
N/A

https://github.com/pizzaboxer/bloxstrap/wiki/"Access-to-the-path-is-denied"-or-"An-error-occurred-trying-to-start-process"-regarding-RobloxPlayerBeta.exe

I created another user and everything works but it doesn’t work for this user, tell me how to solve this problem?

i'm just going to explain this to you since you didn't read it
you have an antivirus and is blocking bloxstrap
solution is to add an exception or disable it

Не помогает, я читал и ознакомился с материалом прежде чем писать

sorry i don't speak russian
try to disable the antivirus

I apologize, I added this file to the list earlier so that it would not be blocked, I read and became familiar with the material before asking for help. It’s quite strange that on another PC user, everything works fine and installed quickly. In this user it gives this error

As I understand it, the installer is trying to find the ADCC~1 user, but I don't have such a user.

how did you even manage to install in the winrar temp directory

To fix this, you'll need to open the Registry Editor and delete the InstallLocation key at HKEY_CURRENT_USER\SOFTWARE\Bloxstrap (better described here). Afterwards, reinstall it as normal.


Make the demo deployable without private resources (other than K8s)

Currently some of the demo scripts might assume the need to push locally compiled images in a private registry.
Since the OS launch, we have official images sitting in dockerhub; this is potentially not strictly needed anymore and would shorten the requirement list and speed up a new user with intention to play with OSM.
Scope (please mark with X where applicable)

[X] Install

Possible use cases
New user who wants to play with OSM, can checkout OSM and run the demo with upstream images out of the box with no intermediate steps.

Hi @eduser25 , is this resolved / ready to be closed?

this is resolved.


Cannot Sign In - version 2.0.7

Version 2.0.7
Windows 10 64 bit

I am unable to connect to twitch with either the 2.0.6 or 2.0.7 versions of TwitchLeecher. Every time I try to sign in I get this error:

I know that the issue is not with my login credentials as I can sign in at the twitch website via my web browser just fine and have signed out and back in thee just to confirm that my credentials work.

Having the same issue, with 2fa turned on or off.
Version 2.0.7
Windows 10 64 bit

I have the same problem. I don't understand why in twitch web if it lets me log in and here not. Any solution?

Same here

Same trouble. I'm tried on versions 2.0.7, 2.0.6 and 2.0.5 - problem exist. Tried with different accounts, some accounts with 2FA enabled, some not - all unable to logging in.

same

Hey im also having the same problem the in program browser is unable to log in, but i can log in on my regular browser.

Im having a same problem. Do you think guys it will be fix? or not?

same for me with windows 11

I'm having the exact same issues

Same issues here. have confirmed I am using correct credentials.
It would also be nice if the login query would just be opened in your default browser instead of an internal one.
It would allow us to give access to the account without giving credentials if we are already logged in.
Maybe the Twitch API is considering this a "new" device and blocking the login attempts? Or does that only happen if you have 2FA on?

I found a new project. devhotteok/TwitchLink Try this.

I am having this same problem. PLEASE help this is crucial

I found a new project. devhotteok/TwitchLink Try this.

is this safe?

is this safe?
I have tried it out and it works great! and why would that one be any un-safer than TwitchLeecher?

is this safe?

See this. #799

Samme issue for me, cannot log in

Please refrain from starting tool comparisons in very specific issues. This issue is called Cannot Sign In - version 2.0.7 and not how to find a better tool than TL in 24 hours. You don't go to a BMW workshop with a broken clutch in your BMW M2 and while the mechanic is working on your car you tell him how much better the Audio RS3 is. That's disrespectful.
Closing this for off-topic and we continue on #800 (and stick to the topic)

I found a new project. devhotteok/TwitchLink Try this.

Thanks man, this is working for me :) Hopefully twitch leecher gets fixed tho but im glad I have two apps now


Remove fspath from AbstractFile since broke some pyarrow

Fixes https://github.com/intake/filesystem_spec/issues/104

Do you need a swift release here?

Nope. I don't think there was a release of fsspec with fspath, right?

Indeed, you are right again!


I am getting below exception on composer update after adding vinelab?

[RuntimeException]
Could not scan for classes inside "/home/vagrant/code/dev/vendor/vinelab/cdn/tests/TestCase.php" which does not appear to be a file nor a f
older

Yes I'm getting this too!
[RuntimeException]
  Could not scan for classes inside "/home/forge/default/releases/20150524121335/vendor/vinelab/cdn/tests/TestCase.php" which does not appear to be a file nor a folder

When you install the package. The 'tests' directory is not included with it which is causing the error.
Guys - This is a breaking issue!

Fix in #621adbb0bcedd02c8f3b2ea3b122b4a9ecb31011
I update the git attributes config file to keep the /tests directory when export-ignore is used with git.
The .gitattributes file is telling git to ignore the /tests directory when downloading the package via composer in your project. Since the /test directory is autoloaded by the composer.josn file it is causing this RuntimeException.


Ansible request for openssl 1.1.1i on Windows

Please put the name of the software product (and affected platforms if relevant) in the title of this issue

[ ] Missing install
[ ] Bug in ansible playbook
[x] Request for new playbook addition

Details:
Requested by OpenJ9 to keep up to date with OpenSSL releases

Playbook addition done - looking to deploy on all build systems

Deploying via AWX. Checklist of systems:

[x] build-azure-win2012r2-x64-1
[x] build-azure-win2012r2-x64-2
[ ] build-ibmcloud-win2012r2-x64-1
[ ] build-ibmcloud-win2012r2-x64-2


Reflow tests

Codecov Report
Attention: Patch coverage is 99.33110% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 83.81%. Comparing base (0167dc0) to head (8706739).

Files
Patch %
Lines

src/uis/reflow.rs
99.33%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
+ Coverage   80.26%   83.81%   +3.55%
==========================================
  Files          39       39
  Lines        4879     5178     +299
==========================================
+ Hits         3916     4340     +424
+ Misses        963      838     -125

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Run multiple files in one folder

I have a nested folder like testJmeter/tests, and there are multiple test cases in it. But when I use
uses<EMAIL_ADDRESS>with:
testFilePath: testJmeter/tests/
outputReportsFolder: reports/
It will failed with An error occurred: The file /github/workspace/tests/.jmx doesn't exist or can't be opened and I checked the log. It says Using Test File Path testJmeter/tests (correct), Running test with tests/.jmx (I think something wrong here as you use BASEFILE_PATH=$(basename $TESTFILE_PATH), you remove the prefix path here).
Is this the issue or I did something wrong? Could you please help me with it. Thanks

Hey @xiaoyu-wu566,
I see where the issue is - https://github.com/rbhadti94/apache-jmeter-action/blob/master/entrypoint.sh#L38
Will get a fix in this week. Thanks for pointing it out. Basically I have to loop recursively through folders rather than the top level.

Hi Ravindra,
Thanks very much! I forked you code and just changed BASEFILE_PATH to TESTFILE_PATH in the for loop. Then everything looks correct.

@xiaoyu-wu566 - v0.6.0 should contain this feature now.


feat: add support for FETCH, PATCH, and iPATCH

This PR adds support for the FETCH, PATCH, and iPATCH CoAP methods, as specified in RFC 8132. I still need to figure out what is actually needed to fully support these methods (besides the status codes), so this PR is for now only opened as a draft.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 89.934%

Files with Coverage Reduction
New Missed Lines
%

lib/cache.js
2
95.45%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
1155

Relevant Lines:
1248

💛  - Coveralls

@Apollon77 It would be awesome if you could have a look on this PR :) For me it seems that there is actually no more logic necessary to support the new methods but maybe you could also have a look into RFC 8132?

I try to check next days ... seems "a lot" that you managed to do :-)

@Apollon77 I think this PR is now the only one that is left :) Would be awesome if you could have a look on it and proceed with merging if it is okay. I guess after that we can create a new release :)

LGTM


[DNM] raftstore: support consistency check

ref #1123 #1286 #1314
@siddontang @hhkbp2 PTAL

PTAL

ping

Rest LGTM

@disksing
We should add MVCC verify later.

Rest LGTM

LGTM


Dependencies for Python 3 and PyPy support

pthon-u2flib-host currently only Python 2.x (in particular CPython 2.x). The limiting factor is the required libraries. Porting python-u2flib-host would first require porting, or replacing

M2Crypto
python-hidapi

I'd like to propose M2Crypto be replaced, the project appears to be stalled (with no commits since May 2015) and it's written using SWIG which isn't compatible with PyPy. I'd like to propose cryptography

Apache/BSD dual licensed
Supports Python 2.6-2.7, Python 3.3+ and PyPy
Tested on Windows, Mac OSX and Linux
Ships pre-built wheels for Python 32-bit and 64-bit on Windows
Has multiple maintainers i.e. a bus factor > 1

I'm happy to do the work and provide a PR, but first I'd like to check you're happy with the concept. Would Yubico be willing to use cryptography instead of M2Crypto for python-u2flib-host?

Closely related to Yubico/python-u2flib-server#9

I'd be very happy to swap out M2Crypto for Cryptography, in both host and server libraries. Last time I checked Cryptography wasn't quite up to the task (details in Yubico/python-u2flib-server#9), but things may have changed since then. I'm a bit hesitant to switch just one of the projects over if the other one can't be, for sake of consistency. Then again, maybe the benefits of switching are enough to motivate the inconsistency.

I'm a bit hesitant to switch just one of the projects over if the other one can't be, for sake of consistency

I plan to do both

See https://github.com/moreati/python-u2flib-server/tree/cryptography for work in progress. Still relies on M2Crypto for certificate verification.

Time to resurrect this. I'll get a pull request together over the weekend, and maybe another for Python 3 support.

Closing since the PR is merged.


IE Edge Carousel slide animation bounces slightly on completion

Similar Issues:
#22291
#21751
#22392
Issue seems not be be solved with current version using Microsoft Edge 42.17134.1.0 and BS v4.1.3:
https://getbootstrap.com/docs/4.1/components/carousel/

@Johann-S @mdo: IE11 doesn't support @supports.
So doesn't this mean that translateX is used instead of translate3d?

Also /CC @MartijnCuppens to chime in.
From a quick look I think the supports check is wrong, but I need someone else to confirm too.


run watch updates app.js twice, then compiles successfully without changing app.js when files change

Laravel Mix Version: 6.0.10
Node Version (node -v): 15.5.1
NPM Version (npm -v): 7.3.0
OS: MacOS 11.2.3

Description: I'm using Mix, Docker, Sail, all right out of the box. Everything was working great, using npm run watch. Suddenly (as far as I know, I didn't change anything relevant) it stopped working. Each time I run npm run watch it compiles successfully and updates app.js twice. The third time my files change, it says it compiled successfully, but app.js has not been modified. (I didn't start counting how many times it updated successfully at first, so I'm not totally certain it's always 2 times, not 3, but since I've been counting it's always 2.) I tried restarting my computer without effect. npm run watch-poll seems to have the same problem.
Steps To Reproduce:
I haven't tried creating a new project to see if it has the same problem.

Same issue here without Sail... watch detects only the first change after starting, and then it looks that it recompiles something but no changes in output

Mine is working again, last I checked. I don't think I did something that fixed it. Would be nice to know what's going on...

Same here!

I do believe I'm having the same issue.
Laravel Mix Version: 6.0.16
Node Version (node -v): 12.16.0
NPM Version (npm -v): 7.7.6
OS: MacOS 11.2.3

On the side, and I cannot confirm if this is related, if I have an error during compilation via typescript mode, mix ends up in an endless loop of compile error compile error so on and so forth

Same here. No changes being reflected after the first compilation...
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><----------------
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

If you're using Docker you're almost certainly gonna have to use watch-poll. File system events don't flow into Docker and that's not something we can fix. If watch-poll is not working that sounds like files aren't syncing in the Docker volume.
I'm not sure what (if anything) we can do about this. For now, I'd recommend running mix outside of Docker when developing.

If you're using Docker you're almost certainly gonna have to use watch-poll. File system events don't flow into Docker and that's not something we can fix. If watch-poll is not working that sounds like files aren't syncing in the Docker volume.
I'm not sure what (if anything) we can do about this. For now, I'd recommend running mix outside of Docker when developing.

@eveames seems to be on docker, however I'm not and I don't think everyone else is either that have had this issue.

@djzara Can you provide a repo that reproduces the problem you're seeing with watching files? (and the typescript one too? — that's very odd)

@thecrypticace yeah it's the weirdest thing I've seen. I've gone through several things to figure out what might cause it to happen. Regular ol' watch, compiles twice with only one compilation doing anything, and then that happens any time i save. No docker, not even a vagrant box piping in fs events. If there's an error you can end up in an infinite loop of compilations.
As soon as I can I'm gonna setup a project from scratch and see if I can manage to reproduce it by gradually incorporating what I've done in to it and then get back to ya.

I'm not on docker & watch poll does the same thing...

Same thing here, anybody has any updates on this?

@wayne-thorley  or @fridzema  have you been able to reliably reproduce this in a new project from scratch? I'm trying to figure out exactly what I'd done to make this happen, what thing I can say is that beyond mix I was using the vue composition api with typescript. Were you all? If that's the case I can see this being something to bring up to the vuejs or typescript folks, but even then I'm not sure how mix would even allow that kind of behavior.

@djzara i can confirm this issue doesnt exist on a fresh install (at least for me). I am currently trying to reproduce the issue in a seperate repo https://github.com/fridzema/mix-watch-issue but eveything is working fine till now.

@fridzema thanks for that. I noticed this issue with typescript + vuex + composition API, so I'll try and hit it from that direction.  Versions for anyone interested:

Laravel 8.35.0
Laravel Mix 6.0.6
Yarn 1.22.10
vue 3.0.7
vuex ^4.0.0
typescript 4.2.3
tailwindcss 2.0.3
postcss 8.1.14
postcss-import 14.0.1

Figured I'd include some of the other items compiled by mix just in case. This is from the project with the problem. I'll keep these in mind when I can get my repro repo setup (crossing my fingers it's soon)

I've been writing a rather significant amount of typescript lately and I've also noticed some oddities around watching files & recompilation. It's like webpack sees the changes and re-runs but ts-loader either doesn't compile again or doesn't write the files to disk. The thing here is it's not easily reproducible — it just happens seemingly at random sometimes. I'm not certain this is a Mix issue or if it's something we can work around. 🤔

I'm in about the same boat @thecrypticace . I don't think it's necessarily a mix issue since it's just wrapping webpack, but it's also in charge of the webpack configuration when you're running it in ts mode (without much in the way of any other modification of the webpack config) so it could definitely be a webpack issue, or even the version of webpack that mix is using? I wouldn't mind poking around their repo and issues as well to see what's up. Maybe a cross reference to help.

I couldn't reproduce myself on a fresh install using the same package versions.
@djzara - It's not related to typescript on my end as I don't use it.
Weirdly, just like @eveames, my original issue seems to have resolved itself today. I haven't done anything that would / could have affected it but watch is now recompiling correctly every time ¯_(ツ)_/¯ It's a weird one!

I had the same problem and tried absolutely everything. Eventually I found that the issue was with how I imported the Vue routes.
{
    path: '/test',
    name: 'test',
    component: () => import("../views/pages/test.vue")
},

I forgot to use a capital letter....
component: () => import("../views/pages/test.vue")
Should be:
component: () => import("../views/pages/Test.vue")
Apparantly when I run 'npm run watch' laravel mix is fine with importing my Test.vue eventhough I wrote 'test.vue'. Thats why I did see changes when I restarted the watch. However, after the initial start laravel mix uses dynamic loading and at that point it will ignore the changes if I do not use the capital letter.
Watch will also ignore changes in components, after first run, if you import it without the correct use of capital or lowercase letters.
import Button from '@/components/Button'
I thought I'd post my mistake. Maybe some of you have the same issue?

@iDoes123 I was running into this issue, and you nailed the cause, I had changed some file names and had the incorrect casing in an import (unrelated to vue). Fixing the casing solved the issue for me. Thanks!

i'm running into the same issue but on a fresh install using laravel new test-app
Laravel v8.83.2 (PHP v7.3.24)
Mac OSX 12.2
Mamp Pro
package.json
{     "private": true,     "scripts": {         "dev": "npm run development",         "development": "mix",         "watch": "mix watch",         "watch-poll": "mix watch -- --watch-options-poll=1000",         "hot": "mix watch --hot",         "prod": "npm run production",         "production": "mix --production"     },     "devDependencies": {         "axios": "^0.21",         "laravel-mix": "^6.0.6",         "lodash": "^4.17.19",         "postcss": "^8.1.14"     } }

npm run watch-poll saved my life,
Check the detail here: https://laravel.com/docs/5.4/mix#running-mix

What fixed it for me was similar to what @ghost mentioned.
I had an Index.vue file inside of a folder called EnrollForm, which I was importing like so:
import EnrollForm from '../../EnrollForm'
When I started up npm run watch, my changes were correctly reflected in the browser only for two compiles, and then the compiler would say "Build successful" but my changes were not reflected in the browser.
Per @ghost's comment, I tried changing the import statement to this:
import EnrollForm from '../../EnrollForm/Index.vue'
And then my changes began to be reflected in the browser every time the compiler ran 🤷♂
Thanks @ghost!

i just looking for some reason for my npm run watch why not apply assets every changes and its working like npm run dev if you have same issue as mine just i have to say some info

i use laravel 8
i use laravel-html version of vuexy

so for that problem i check my package.json and as i know that before my package.json missing dev script so i find it in my other projects and add it at first item of scripts ( in package.json)
"scripts": {
"dev": "npm run development",
.
.
.
now its working just normal and apply all assets after every change
and again i'm not sure about what's purpose in this issue


Python environment is very bloated currently

It's around 2 GB now and we should investigate if it can be trimmed

Looping back to the github issue for documentation's sake: I was looking at this earlier this week, and chatted with Bill a bit as well.
I'm 99% confident that the python wheel doesn't need the static libraries (*.a) files in it, only the *csrc.so one. Also, it shouldn't need debug symbols in those files. strip -d would shed the debug-only portions of the library.
With that, the wheel size would come down quite significantly, and likely make it reasonable to download artifacts instead of rebuild in CI.
I'm documenting here just for posterity. I can't promise I'll get around to making the actual changes, so just in case I don't, at least the idea is captured.

We've done some work recently to help facilitate this.
We are now building across all configs and archs for our stack at a post-commit level and upload the resulting libs and tests. We can use an independent GitHub-hosted runner version of this build job to ensure the build actually works on a reasonably third-party level, whereas @TT-billteng suggested we use our more powerful machines as build machines for specifically CONFIG=ci instead of waiting on the artifacts from the slower GitHub-hosted runners.
Also, just for clarification, just wanted to be a little more verbose on @olofj 's comments on the wheel. There actually is only one so in the wheel and we switched over to using CONFIG=ci a couple days ago. It's much, much smaller now, but the wheel itself is still quite large if you take a look inside by unzipping the wheel as a zip:
rkim@e12cs07:~/wheels/eager-dist-ubuntu-20.04-grayskull/tt_lib$ du . --threshold=15M -hal
25M	./tt_metal/third_party/lfs/profiler/tests/golden/device/outputs
26M	./tt_metal/third_party/lfs/profiler/tests/golden/device
26M	./tt_metal/third_party/lfs/profiler/tests/golden
26M	./tt_metal/third_party/lfs/profiler/tests
26M	./tt_metal/third_party/lfs/profiler
47M	./tt_metal/third_party/lfs
18M	./tt_metal/third_party/umd/device/bin/silicon/wormhole/tt-script
49M	./tt_metal/third_party/umd/device/bin/silicon/wormhole/create-ethernet-map
67M	./tt_metal/third_party/umd/device/bin/silicon/wormhole
45M	./tt_metal/third_party/umd/device/bin/silicon/reset-chip
125M	./tt_metal/third_party/umd/device/bin/silicon
125M	./tt_metal/third_party/umd/device/bin
126M	./tt_metal/third_party/umd/device
130M	./tt_metal/third_party/umd
27M	./tt_metal/third_party/tracy
28M	./tt_metal/third_party/taskflow/doxygen
17M	./tt_metal/third_party/taskflow/3rd-party/eigen-3.3.7
16M	./tt_metal/third_party/taskflow/3rd-party/tbb
36M	./tt_metal/third_party/taskflow/3rd-party
45M	./tt_metal/third_party/taskflow/benchmarks/mnist/train-images.data
53M	./tt_metal/third_party/taskflow/benchmarks/mnist
54M	./tt_metal/third_party/taskflow/benchmarks
139M	./tt_metal/third_party/taskflow
24M	./tt_metal/third_party/sfpi/compiler/lib
39M	./tt_metal/third_party/sfpi/compiler/riscv32-unknown-elf
20M	./tt_metal/third_party/sfpi/compiler/libexec/gcc/riscv32-unknown-elf/10.2.0/lto1
23M	./tt_metal/third_party/sfpi/compiler/libexec/gcc/riscv32-unknown-elf/10.2.0/cc1plus
21M	./tt_metal/third_party/sfpi/compiler/libexec/gcc/riscv32-unknown-elf/10.2.0/cc1
65M	./tt_metal/third_party/sfpi/compiler/libexec/gcc/riscv32-unknown-elf/10.2.0
65M	./tt_metal/third_party/sfpi/compiler/libexec/gcc/riscv32-unknown-elf
66M	./tt_metal/third_party/sfpi/compiler/libexec/gcc
66M	./tt_metal/third_party/sfpi/compiler/libexec
20M	./tt_metal/third_party/sfpi/compiler/bin/riscv32-unknown-elf-lto-dump
58M	./tt_metal/third_party/sfpi/compiler/bin
185M	./tt_metal/third_party/sfpi/compiler
186M	./tt_metal/third_party/sfpi
531M	./tt_metal/third_party
536M	./tt_metal
17M	./_C.cpython-38-x86_64-linux-gnu.so
569M	.

sfpi with its compiler binaries, lfs assets, umd with silicon binaries, and taskflow take up the vast majority of the space.
I don't think MANIFEST.in will help here since that controls stuff at the src distribution level, and we will need most of this to actually build the wheel. We could probably do some setup.py tricks to trim down any fat that we don't need at the wheel level, such as docs and unused source code in the third party.
I'm under the impression Buda is in a similar boat, since it also likely needs umd in its distribution. We should open
The point is, in terms of reducing our C++ libraries' sizes, I think we're in a good place and can start moving forward on things like build artifacts. I made an issue on our side to reduce wheel size: https://github.com/tenstorrent-metal/tt-metal/issues/5990

should re-visit when #6858 is in


show page top bar looks wonky on phones

As a user, when I view on my phone I want the top bar content to lay out nicely.

#119


Is it possible to cancel upgrade/unit ?

So I'm interested if it possible to cancel, for example stalker in gateway,
and does build_progress can work with upgrade/unit ?

Yes, it is possible. I have done it with extractors to get the drone back. You will need to call the CANCEL Ability on the gateway that is creating the stalker. It should look similar to something like this:
extractor = self.units(UnitTypeId.EXTRACTOR).not_ready.first
await self.do(extractor(AbilityId.CANCEL))

@mjschuetze102  wow, didn't noticed this in docs, thx a lot!
and what about ability\upgrade  research progress isit possible?

I haven't looked into this. I would assume something like self.already_pending(research) would work. Again, I wouldn't know though. You can see if it has been completely researched by selecting a unit that would have the upgrade and seeing if the abilities on it have changed. Or by selecting the building doing the research and seeing if it is still available or not. But neither of those would give you how far along the research is. #46 may be what you're looking for.


Change primitive array args to varargs

@paplorinc suggested the following:
interface Stream<T> {

    // before: ofAll(int[] array)
    static Stream<Integer> ofAll(int... array) {
        return Stream.ofAll(Iterator.ofAll(array));
    }

    static Stream<Long> ofAll(long... array) {
        return Stream.ofAll(Iterator.ofAll(array));
    }
}

The test:
public class Test {{

    // ok
    Stream<Integer> ints = Stream.ofAll();

    // IntelliJ IDEA complains: Required: Stream<Long>, Found: Stream<Integer>
    Stream<Long> longs = Stream.ofAll();

    // does also not work
    Stream<Long> longs = Stream.<Long> ofAll();
}}

However, unexpected behavior with varargs can only occur when we have reference types, e.g.
// reference type T
public <T> void foo(T... params) { ... }

int[] arr = {1, 2, 3};

foo(arr); // passes an int[][] array containing a single int[] element

See also this StackOverflow question.
I see no problem to switch to varargs for primitive types. There is no risk that the array is confused with a single object.
We should apply that change to all Javaslang types that have static factory methods ofAll(<primitive array>).
Notes:

We still need to check if the varargs argument is null.
The change is considered backward compatible:

public static void foo(String... string_array) { ... }

public static void bar(String[] string_array) { ... }

String[] arr = {"abc", "def", "ghi"};
foo(arr);  // accept
bar(arr);  // accept
foo("abc", "def", "ghi");  // accept
bar("abc", "def", "ghi");  // reject

Duplicate of: https://github.com/javaslang/javaslang/issues/1544

@paplorinc thx


Update examples and improve Scaladoc

Closing this given it has the problem with valueOf in the prop package in common-test, which was identified by Chee Seng. Will submit a new PR later.


safetensors.torch.save_data modifies the saved data after saving

System Info
The save_data function exhibits weird behavior when re-opening and re-saving/overwriting an existing .safetensors file.
For example, here the data dictionary is not the same after calling the save_file function:

The reason why I need to be able to re-open and overwrite the .safetensors file is checkpointing. I regularly overwrite the .safetensors file (this does not cause the bug). When my script crashes and is restarted, the (existing) .safetensors file is loaded and overwritten again, which causes the bug. Interestingly, when immediately loading the file again after saving with data = load_file("mydata.safetensors"), all three values are correct again. Only the dict in the runtime is modified.
Information

[x] The official example scripts
[ ] My own modified scripts

Reproduction
The following is enough to reproduce the bug:
from safetensors.torch import save_file, load_file
import torch
data = {'a': torch.zeros(10), 'b': torch.zeros(10)}
save_file(data, "mydata.safetensors")
data = load_file("mydata.safetensors")
data['c'] = torch.zeros(10)
print(data)
save_file(data, "mydata.safetensors")
print(data)

The bug even persists when saving the dict with save_file(deepcopy(data), "mydata.safetensors").
For reference, I am using torch 2.0.1 and safetensors 0.4.1 with Python 3.10.12.
Expected behavior
The dictionary should remain unchanged after saving it.

Just trying to raise this issue again, as the bug still exists.


Fix STU3 validation

find correct extension profile, use custom datatype profile, allow to disable terminology checks

Coverage decreased (-0.006%) to 76.911% when pulling a8e248036e73e54d0a88f4e18948403bb7cd35b2 on SRiviere:Stu3_validation into 6c47bd4c5111ca65ceebbbce63927e3c78da87f9 on jamesagnew:master.

Sure sorry i forget it. In summary is in a resource when you specify a list of possible extension you may have a element like that:
    <element>
        <path value="Patient.extension"/>
        <slicing>
            <discriminator>
                <type value="value"/>
                <path value="url"/>
            </discriminator>
            <rules value="open"/>
        </slicing>
        <definition value="May be used to represent additional information that is not part of the basic definition of the element."/>
    </element>

And this element was generating "types == 0, and no children found" when it try to validate an extension

Sure i'll add the tests. In summary this is to manage a element like that:

And avoid a this error: "types == 0, and no children found", because ther is no type define when the extension is defined in is own element so the search should continue

Coverage increased (+0.07%) to 76.985% when pulling ecac0ffb5fff8ce8b138306ad6444aefb7a96a94 on SRiviere:Stu3_validation into 6c47bd4c5111ca65ceebbbce63927e3c78da87f9 on jamesagnew:master.

Thanks @SRiviere , I've merged this!

By the way, I'm crediting this to @SRiviere in the changelog. Please let me know if you would like me to use another name.

(And I'm also forward-porting this fix to the R4 validator)


sddm-kcm: init at 5.10.5

Motivation for this change
I wanted to see if a custom theme was being detected properly, so I packaged this. It is however for all other purposes completely pointless as it tries to change /etc/sddm.conf which is obviously read-only.
@ttuegel - what do you think? Merge or throw away?
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

as it tries to change /etc/sddm.conf which is obviously read-only.

Its not implemented in such a way that it detects its read-only and just greys out all options?

Its not implemented in such a way that it detects its read-only and just greys out all options?

This is KDE.
"Why would you check for a condition that is obviously true?"
No sense in throwing it away. SDDM is terribly difficult to debug. Anything that makes that easier is good in my book.


NPM registry referenced instead of github

It looks like npm is referenced instead of github [here] (https://github.com/nodezoo/nodezoo-github/blob/master/lib/github.js#L9)  and [here] (https://github.com/nodezoo/nodezoo-github/blob/master/srv/start.js#L16).

This is to prove the module exists on npm since only npm modules are considered valid. The ability to swap the registery url is to allow private installations.

Ah this makes perfect sense. Thanks!


NIFI-8422 added auto close/manager for stale PRs

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

@joewitt - happy to merge this one, is it wip or can it be merged?

@joewitt - happy to merge this one, is it wip or can it be merged?

@pvillard31 The concept looks good, but the automated build failed due to the file not containing a license header, so that should be addressed prior to merging.


Update config docs regarding DNS-SD changes.

Fixes https://github.com/prometheus/docs/issues/161

@fabxc

:+1:


Improved Doc

Hi @bit2u! thanks for the suggestion, curious why you think this is an improvement.

This is hacktoberfest-spam. Please mark it with the label invalid.
https://hacktoberfest.digitalocean.com/faq/
https://www.theregister.com/2020/10/01/digitalocean_hacktoberfest_pull_request_spam/

thanks!
Joseph McArthur
Assistant Director: Right to Research Coalition ( http://righttoresearch.org )
Director / Founder: Open Access Button ( http://openaccessbutton.org )
Twitter: @Mcarthur_Joe ( https://twitter.com/Mcarthur_Joe )
Skype: joseph_mcarthur
On Thu, Oct 01, 2020 at 10:42 PM, Danilo Bargen <<EMAIL_ADDRESS>> wrote:

This is hacktoberfest-spam. Please mark it with the label invalid.
https:/ / hacktoberfest. digitalocean. com/ faq/ (
https://hacktoberfest.digitalocean.com/faq/ )
https:/ / www. theregister. com/ 2020/ 10/ 01/ digitalocean_hacktoberfest_pull_request_spam/
(
https://www.theregister.com/2020/10/01/digitalocean_hacktoberfest_pull_request_spam/
)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/OAButton/website/pull/130#issuecomment-702413600 ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABFZMZ4SSE7EC5ND3PO3DJDSITZURANCNFSM4R75X3UA
).


taxon constraint GO:0003382 - new term needed

GO:0003382  epithelial cell morphogenesis
got taxon restricted and was annotated to Dicty ctnnA / DDB_G0285939 since 2012.
I guess the taxon restriction came from being a child of
GO:0009888 tissue development
But this was a Science paper that also showed that ctnnA, the alpha catenin ortholog binds not only the Dicty beta catenin orthalog but also the mouse beta-catenin
https://pubmed.ncbi.nlm.nih.gov/21393547/ and a follow up PMID:22902739
I wonder if I can get a new term, a child of sorocarp stalk morphogenesis

GO:0036360 sorocarp stalk morphogenesis
-- GO:NEW  epithelial polarity establishment during sorocarp stalk morphogenesis

Def:  Establishment of a polarized epithelium consisting of a single layer of structurally and functionally polarized cells that secrete proteins into a luminal space during morphogenesis.
Or, alternatively, to be more widely applicable

GO:0009653 anatomical structure morphogenesis
-- GO:NEW: primordial epithelial polarity establishment

Def:  Establishment of a polarized epithelium consisting of a single layer of structurally and functionally polarized cells that secrete proteins into a luminal space during morphogenesis. An example of this process is found during stalk development in Dictyostelium discoideum.
Thanks for dealing with this soon as I have to delete the taxon violating term.

perhaps
GO:0030010    establishment of cell polarity
GO:0071964    establishment of cell polarity regulating cell shape (I wish this had a better name)
part_of GO:0036360 sorocarp stalk morphogenesis
otherwise terms would be required for every cell and tissue type
Or maybe this would not work here. but in the def you refer to "structurally and functionally polarized cells " so it does seem to be a cell level phenomena?

@pfey03 Dicty doesn't have epithelial cells - I think @ValWood 's suggestion is closer to what you are trying to capture ?

@ValWood @pgaudet
I don't like
GO:0071964 establishment of cell polarity regulating cell shape
This is not it when you read the def:
"Any cellular process that results in the specification or formation of a polarized intracellular organization or cell growth pattern that regulates the shape of a cell."
Also GO:0030010 establishment of cell polarity
doesn't cover it well, or I need to think about a good extension and GO-CAM.
This happens only during development it's not just a single cellular event. It's a polarized cellular tip 'cover' they call epithelium, please see image.

They talk about 'epithelium' as a covering layer, but I dont think they mention 'epithelial cells'. Maybe you can use 'epithelium development' (alhtough I am not sure if that fits the UBERON taxon constraints - this is how UBERON is organized in this branch:

multicellular organism

tissue

epithelium

Or create a new term like 'epithelium-like development/formation/organization'. Would that work ?
Thanks, Pascale

Ah right. I thought it might be OK to use  "cell polarity" terms because the cell polarity changes presumably underlie the tissue polarity. This might be too big an assumption though, because organizing polarized cells in relation to each other is also required (although I thought that was encapsulated by the sorocarp stalk morphogenesis).

@pgaudet sorry for delay
Maybe:
epithelium-like organization
not sure about parentage. Restricting to Dicty and putting it under sorocarp development or keeping it more general?
A possible def: the organization of a polarized cell layer during morphogenesis in protozoa; an example is found during culmination in D. discoideum, involving alpha and beta catenins.
Maybe alpha/beta catenins are too much detail although that's part of the point in the science paper.
Thanks!!

@pgaudet do you want to take this since you are more familiar with dicty than me. If you want to go to the level of the tissue, maybe something like 'specification of axis polarity' would work with the appropriate dicty anatomical structures?

Added new term:
+[Term]
+id: GO:0140509
+name: epithelium-like organization
+namespace: biological_process
+def: "The organization of a polarized cell layer during morphogenesis in protozoa; an example is found during culmination in D. discoideum, involving alpha and beta catenins." [PMID:21393547, PMID:22902739]
+is_a: GO:0009653 ! anatomical structure morphogenesis
+created_by: pg
+creation_date: 2020-08-28T07:29:53Z

Looks like a case of 'false advertising'
'epithelium-like': makes me think of something quite general
Definition: specific to protozoa (but no TCs?)... and protozoa is an informal term I don't think in should be used in the non-gloss part of a definition.
Also all organization terms should follow a pattern and include an anatomy term
E.g see this paper https://elifesciences.org/articles/49801 "A unicellular relative of animals generates a layer of polarized cells by actomyosin-dependent cellularization" (which itself uses a GO enrichment analysis :-)
Even though sponges are animals it's not clear if their "epithelia" are better classified as epithelium-like rather than a true epithelium?
The outer cell layer in plants is often called epithelium e.g. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6296743 - it is certainly not a true epithelium with true epithelial cells, but it could arguably be called "epithelium-like". It follows the GO definition other than the arbitrary 'protozoa' constraint which is IMO a random grab bag of taxa with no basis in homology.
Also this PR doesn't seem to address terms like epithelial cell morphogenesis which still have Dicty annotations:

epithelial cell is a part of an epithelium. As soon as we fix the bug that is omitting CL taxon constraints these annotations will be flagged.
I think we need a more holistic fix loosely coordinated across all three ontologies. Some options:

broaden def of epithelium/epithelial cell across all 3. We still want some kind of cohesive unifying thing beyond linguistically being called an epithelium.
introduce some kind of grouping class, e.g. polarized cell layer, but this seems fuzzy and vague and groups many different non-homologous structures
variant of 2, make it a more restricted grouping, e.g make catenins required
Relabel GO:0140509 to be 'epithelium organization sensu Dicty'. Add logical def using DDANAT. Same for the cell type. Don't worry about grouping, let the data speak for itself.

I am strongly in favor of 4. It's simple. 3 is hard. When we have tried strategies like 1 or 2 before we end up with IMHO mush.
Maybe in future we'll have more data that will inform other ways of organizing things, but 4 is at least safe.
Minor aside: I like having examples in the definition. I like how we say an example is found during culmination in D. discoideum, involving alpha and beta catenins.. But it is also useful to give other examples, otherwise someone coming to this term later doesn't really know if this corresponds to their taxon. Also reading https://pubmed.ncbi.nlm.nih.gov/21393547/ is it really correct to say "involving alpha and beta catenins". The paper seems to hedge bets using language like "β-catenin-related protein called Aardvark" (of course this goes away if we go for my option 4)

@cmungall I updated the annotations just recently as it always takes a while for the new terms to appear and it just didn't make it through P2G release yet. All are annotated to GO:0140509 epithelium-like organization.
Also, it is correct to say "involving alpha and beta catenins". But we could shorten and just say "involving catenins". They did show that Dicty ctnnA, the alpha-catenin orrtholog, binds both the mouse beta-catenin and the Dicty beta-catenin ortholog aardvark. Both bindings are annotated.
If # 4 is done, fine with me while in general I like things more inclusive. But if #4 and sensu Dicty, it can also move under sorocarp morphogenesis. We currently don't have a DDANAT term for 'epithelium-like cell' or such. If required I can go back into the papers and might be able to add a term.

Also, did you block the term in AmiGO, I cannot find it there, only in QuickGO
https://www.ebi.ac.uk/QuickGO/term/GO:0140509

Hi @pfey03
This is because the new GO release has not been completed yet. This should happen soon - right @kltm  ?

Ah ok, thanks @pgaudet. Just because Chris wondered why on their release there is still the taxon restricted term annotated I was surprised.

@pgaudet The September release should be finalized in the next day or so.

@cmungall
The paper you cite (https://elifesciences.org/articles/49801) mentions "a polarized layer of cells resembling an epithelium"  - maybe the label should be 'polarized cell layer '?
(I am not sure 'sensu' is very clear to users)
Thanks, P
Pascale

Don't await my approval before proceeding with any necessary solution, but I will put my thoughts here
I am not so keen on having very fuzzy anatomical classes, or attempts to generalize beyond what we know. Mentioning protozoa in the text definition is a red flag. Having it be mentioned as a necessary condition in the def but not advertised in the label is also a red flag.
I favor having terms be precise and specific, with optional groupings, but only if biologically justified, something like:

polarized cell layer: do-not-annotate

epithelium, aka true epithelium; only eumetazoa
pseudoepithelium of sponges
polarized cell layer of pseudoplasmodium ; only Dicty??

there may be a level of grouping between sponge epithelia and true epithelia justified, see https://academic.oup.com/icb/article/49/2/167/641359
I wouldn't put plant "epithelia" here. I don't think there is any biology justifying grouping them, just similarity in terms of adjacency to outside.
 On the wiki page they say Dicty sometimes called pseudoplasmodium, but that's not even used anymore in a long time. In our anatomy ontology it's a broad synonym for certain people, but only broad.
You can separate Dicty cells a long time into development, give them food and they go back being amoeba, plus each spore and dead stalk cell are defined cells at the end of development. Different cells express different genes as they specialize (like perspire and prestalk), therefore they can form this epithelium like layer, especially as Dicty expresses then alpha and beta catenin and without one of them this layer cannot form.


Front-end unit testing

User Story
As a user, I would like the interface to be free of bugs so that I can access my moods and playlists.
Detailed Description
To ensure our core functionality doesn't get broken by new commits, we should set up unit tests that run automatically when our code is pushed and check that the main features still work.
Acceptance Criteria

[x] Given new code is committed and pushed to GitHub, then a suite of unit tests should run automatically
[x] Given a main feature no longer works, then the developers should be notified and the code should not be deployed automatically
[x] Given nothing is broken, then all tests should pass

Frontend tests were implemented in #81 .


Feature Request - Autocorrect for Lint/DuplicateMethods

Description
Rubocop is not autocorrecting Lint/DuplicateMethods cop. I've searched the issues to see if there was ever a conversation about why this autocorrection is not supported, and I couldn't find any discussion about it. If it's not technically possible, this feature request can be closed.
Describe the solution you'd like
I think it's possible to support at least unsafe autocorrection. If I'm not mistaken in the same class block last definition of the method overrides the previous one defined in the previous lines.
last definition wins
class Duplicated
  def foo
    'will be overriden'
  end

  def foo
    'winning method definition'
  end
end

Previous definitions should be removed on autocorrection.
attr_*
For methods defined via attr_* methods, attr_accesor makes attr_reader inefective; regardless of their ordering.
class Duplicated
  attr_accessor :foo # wins
  attr_reader :foo
end

When attr_accessor is defined in the class, attr_reader and attr_writer should be removed on autocorrection.
class Duplicated
  attr_writer :foo

  private

  def foo=(arg)
    @foo = arg + 123
  end
end

When attr_writer is overriden in class definition, attr_writer :foo should be removed on autocorrection.

Lint offenses are usually an indication of some programmer's error and that he need to pay attention for. I would like to not have autocorrection for these, especially that somehow considers "which implementation wins" etc.

Hi @fatkodima,
I totally get where you're coming from, in most cases I'd agree. But what if we are introducing rubocop into a legacy codebase? Wouldn't this nudge the author toward fixing it based on the currently running code's behavior?
I was thinking it's a bit like the unsafe autocorrection with Lint/AssignmentInCondition. There too, it assumes the author's intention. Because of this it's marked as unsafe autocorrection.
In this Lint/DuplicateMethods case, the autocorrection would assume the current behaviour is the intended one.


mp4 support

GitHub Markdown does not support video tag currently, so I'm not sure if we really should do this right now, but I believe that they will support it soon. MP4 is much cheaper than animated GIF anyways.

Done in #70


Linux fanotify api does not appear to be working on WSL2

Windows Build Number
Microsoft Windows [Version 10.0.19042.985
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 20.04
Other Software
Debugging in Visual Studio Code app that uses fanotify api.
Repro Steps
Just trying to understand if the api is supported or not.
Expected Behavior
Program should received fanotify events
Actual Behavior
No events are received.
Diagnostic Logs
No logs available

Are you running this on /mnt/c? I believe you're seeing this issue which we are tracking here: https://github.com/microsoft/WSL/issues/4739
A quick work around is to store your files in the Linux file system and use VS Code Remote!


Styling the thumb not working

Using v4.0.0; React v15.1.0; Redux v3.5.2
So I've been trying to add my own styling to the thumb and track but I can't seem to get it to work. I figured out that you need to add the complete styling (I did see this is fixed in 4.0.1) but when I try to set a different color to the thumb it doesn't style the actual thumb but just places a 'new' static thumb in that color and the actual thumb that is moving isn't colored, what am I doing wrong?

Also the autoHide={false} doesn't work and it still hides when I'm not scrolling.

< Scrollbars
  autoHide={false}
  autoHeight={true}
  autoHeightMin={this.scrollBarHeight()}
  autoHeightMax={this.scrollBarHeight()}
  renderThumbVertical={props => < div {...props} className="thumb-vertical"/>}
  renderTrackVertical={props => < div {...props} className="track-vertical"/>}>
       // content
< /Scrollbars >

.thumb-vertical {
  position: relative;
  display: block;
  width: 100px;
  height: 100px;
  cursor: pointer;
  border-radius: inherit;
  background-color: #d9534f;
}

.track-vertical {
  position: absolute;
  width: 6px;
  display: block!important;
  right: 2px;
  bottom: 2px;
  top: 2px;
  border-radius: 3px;
}

Hello, you found a solution? I have the same worries, after the custom scrollbar, it remains frozen up and not moving ...

No unfortunately not yet. I've asked this question on stackoverflow (link) as well in the hope somebody there knows the answer, but no response yet.

Actually this should work. Could you post an online example of the bug?
<Scrollbars
  // autoHide={false} drop this property
  autoHeight={true}
  autoHeightMin={this.scrollBarHeight()}
  autoHeightMax={this.scrollBarHeight()}
  renderThumbVertical={props => <div {...props} className="thumb-vertical"/>}>
       // content
</Scrollbars>

.thumb-vertical {
  background-color: #d9534f;
}

Arg no, I only locally for me.. Does that made the parent div either display flex interfere?
I've customized the scrollbar as the screenshot @e11en but not possible to raise / lower it visually freezes up
I've copy paste you're code and I've a same issue.

I had the same issue using OSX, configure "use the scrollbars: always" on system preferences => general. It worked for me.

@mruano29 that might be a work around but you can't really ask people to do that when using your app :p

This issue still persists... renderTrack* does not take initial styling attributes properly.
renderThumb* does

I'm also having the same issue. Anyone got a solution?

+1

I had this issue too. How I can decided it?

same here renderTrackVertical only gets the following style position: absolute; width:6

Ok, your style has to include   height: 100%;   top: 0;   right: 0;

@hackhat I owe you a beer. Here's how the renderTrack method should look like:
  renderTrack = ({ style, ...props }) => {
    const { trackColor } = this.props;

    return (
      <div
        style={{
          ...style,
          backgroundColor: trackColor,
          height: '100%',
          top: 0,
          right: 0,
        }}
        {...props}
      />
    );
  }

@danmo are you sure this is working? You're basically overriding the styling with it's default settings. Move {...props} above the styling props.

@e11en still no luck? and is that an issue only on OSX or also other operation systems ? thx

I'm not using react-custom-scrollbars at the moment, so you can close this issue or leave it open for others.


Vulenerabilites fixes for FileTransformV2

Task name: FileTransformV2
Description:
Documentation changes required: (Y/N)
Added unit tests: (Y/N) <
Attached related issue: (Y/N) https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/1936449/
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected
[x] node make.js build --task FileTransformV2
[x] node make.js test --task FileTransformV2

/azp run

/azp run


Don't create fibers during requests, unless necessary

Currently, as far as I understand, we create fibers for every request, no matter if it's necessary.
See: https://github.com/tarantool/crud/blob/master/crud/common/call.lua#L88-L94
This is not required when you do a call to single storage. Creating fibers takes time, as well as communication through channels. This is only needed when you do select with map/reduce.

This is a dubious optimization (especially when compared to a single net hop) requiring more complex code so are you sure if the game is worth the candle?

There are 2 problems:

Network latency. You are correct that it won't affect it much.
Throughput. Here, unnecessary creation of fibers and interactions through channels will lead to more load on the router, and thus fewer total requests we can process per second.

In general, you have 2 cases:

The request goes to a specific node (get/put/upsert, etc). We need to execute them with minimal overhead.
Full map-reduce (such as pessimistic selects by secondary keys). Here, we may create fibers as we see fit.

Plus, the problem with the current implementation of single-node operations is that they don't pin vshard buckets. See #59 for details. The only sensible/performant way to fix it is to use vshard callro/callrw functions. And if you use them, there is generally no need to create fibers for that.

About this thesis:

Throughput. Here, unnecessary creation of fibers and interactions through channels will lead to more load on the router, and thus fewer total requests we can process per second.

Have you tested both implementations? What difference in performance? If the difference is significant then of course we will do it but I want to remind you about the dangers of premature optimization as far as I know this has not yet been a bottleneck.

Plus, the problem with the current implementation of single-node operations is that they don't pin vshard buckets.

This will be fixed as part of ticket #59

This issue can now be closed because we fixed it in #58.


Validation for date format allows invalid dates

What version of Ajv are you using? Does the issue happen if you use the latest version?
6.10.0
Ajv options object

{
    allErrors: true,
},

JSON Schema

{
   "type": "array",
    "items": {
        "type": "string",
        "format": "date",
    },
}

Sample data

[
    "2018-02-29",
    "2018-02-35",
    "2018-15-01",
]

Your code

const ajv = new Ajv(options);
const isValid = ajv.validate(schema, data);
const errors = ajv.errors;

Also in RunKit.
Validation result, data AFTER validation, error messages
isValid = true;
errors = null;

What results did you expect?
The validation should fail for all values. You can check the same issue in the enjoi project. It refers to RFC 3339, section 5.6. The validation should restrict the max date number to the specific month, taking into account leap years.
Are you going to resolve the issue?
Atm I haven't dug into ajv's codebase to see how to resolve this. I have already done it using Regex in enjoi. So I can try or at least help :)

You need to use the option format: 'full'

https://github.com/epoberezkin/ajv/issues/996

You are correct. Sorry for wasting your time :) Thank you for a great library!

Can you add it into doc's? @epoberezkin


Roll Engine from dddb532b5c7b to 38b6c22d5b23 (5 revisions)

https://github.com/flutter/engine/compare/dddb532b5c7b...38b6c22d5b23
2020-11-13<EMAIL_ADDRESS>PlatformViewIOS CreateExternalViewEmbedder refactor (flutter/engine#22353)
2020-11-13<EMAIL_ADDRESS>Roll Dart SDK from 3e502e0c7e04 to 41893ff76b0f (1 revision) (flutter/engine#22491)
2020-11-13<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from fULjPqtx9... to B4PaMsNWM... (flutter/engine#22490)
2020-11-13<EMAIL_ADDRESS>Roll Skia from a06b63c56ecd to 8ead30d51c86 (1 revision) (flutter/engine#22487)
2020-11-13<EMAIL_ADDRESS>TBR: remove the extra values which was overshadowing the test result (flutter/engine#22483)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from fULjPqtx9XLI to B4PaMsNWMGdY
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


WIP: kernel: provide aligned variants for allocators

Note, this is not really ready for review, but I would like to get some feedback on how to proceed.
The biggest issue that I can see is that sys_mem_pool does not support aligned allocations, and it is non-obvious to me how to make it support aligned allocations efficientlly. The easiest way to support aligned allocations is to use the k_heap API (which uses sys_heap* under the hood.
Aligned allocations are fairly critical for #29029

This change adds support for aligned allocations and also provides posix_memalign(3) and aligned_alloc(3) in the minimal libc.
Fixes #29519

The biggest issue that I can see is that sys_mem_pool does not support aligned allocations, and it is non-obvious to me how to make it support aligned allocations efficientlly. The easiest way to support aligned allocations is to use the k_heap API (which uses sys_heap* under the hood.

In https://github.com/zephyrproject-rtos/zephyr/pull/28611 the sys_mem_pool allocator gets removed

mis-click sorry
can you set this as a Draft PR since it is still WIP

The biggest issue that I can see is that sys_mem_pool does not support aligned allocations, and it is non-obvious to me how to make it support aligned allocations efficientlly. The easiest way to support aligned allocations is to use the k_heap API (which uses sys_heap* under the hood.

In https://github.com/zephyrproject-rtos/zephyr/pull/28611 the sys_mem_pool allocator gets removed

Now it all makes sense! Thanks for pointing that out @maxbachmann

I cherry-picked from #30003 #28611, so please wait until after those are merged before reviewing.

Leaving this as a draft until #30003 and #28611 are merged.

Closing this in favour of #30363 for a couple of reasons.

Newlib does not provide us with aligned_alloc(3) or posix_memalign(3) so it's pointless to offer in the minimal libc
@andrewboie said I should just provide a k_malloc_aligned() instead and I probably should have just listened to him in the first place :wink:

In any case, #30363 is really just recycling the aligned_alloc(3) implementation and test case from here and applying them to k_malloc() instead, so I didn't really waste time / code... right? :man_shrugging:

Newlib does not provide us with aligned_alloc(3) or posix_memalign(3) so it's pointless to offer in the minimal libc

I don't agree with the "pointless" valuation: POSIX provides them, that's pretty good a reason on its own.
That said, you're designer of this feature.

Newlib does not provide us with aligned_alloc(3) or posix_memalign(3) so it's pointless to offer in the minimal libc

I don't agree with the "pointless" valuation: POSIX provides them, that's pretty good a reason on its own.

Sorry, - it's definitely not "pointless". You're right. For my current purposes though (#29029) I can't use posix_memalign() unfortunately though, because it's not both in newlib and in the minimal libc.
I'll keep the branch around just in case we want to add this in the future. Personally, I think supporting standards are important.

I unfortunately can't use posix_memalign() because it's not both in newlib and in the minimal libc.

That at least should lead to traces of ideas for some kind of "polyfills" (curse JavaScript for abusing thru the entire industry), where we can add functionality for both newlib and minlibs. Actually, we do things like that already - newlib doesn't ship e.g. select() implementation, we do.
(That's not call for action, just call for thinking and maybe planning ahead.)


fix(config): Be less permissive of secret keys

SUMMARY

https://www.bleepingcomputer.com/news/security/thousands-of-apache-superset-servers-exposed-to-rce-attacks/ lists a number of common SECRET_KEYS from documentation. The current check only looks for one of these.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Closing this one, feel free to reopen if you want to follow a different approach


More than just eth1 ?

Is the freeRTR container capable of having more than one endpoint? Would like to add a few more devices to the topology but can't seem to add endpoints with anything other than eth1 as the interface.

Nevermind, this is working perfectly for eth >1 now. It must have been a transient issue with my local system at the time I tried it earlier. Working well with a 4 node deployment (square topology). Great work on getting this working!

Nevermind, this is working perfectly for eth >1 now. It must have been a transient issue with my local system at the time I tried it earlier. Working well with a 4 node deployment (square topology). Great work on getting this working!

You can now also play with some new labs here @modonovan. There is a lab that might be of your interest: rift with CLOS architecture

Excellent stuff Frederic, many thanks and hope all is well with you!

remove all regex first from the repo until i unfollowed frederic to the hell.....


Font Fallbacks not working and Not able to load custom font either

Describe the bug
I'm trying to add Chinese font compatibility in my app but I'm not able to get it to work.
Initially there was a font problem and this was added which changed the default font and also add fall backs.
How it was done can be found here
https://github.com/TheMulhima/Scarab/blob/3821c180b9e838bc68e0cc8b288664e952098495/Scarab/Program.cs#L184-L213
However, if the user doesn't have the primary font installed, the app just crashes instead of trying a fall back font which does exist.
See https://github.com/TheMulhima/Scarab/issues/53
This is one of the issues I'm having with fonts
The other issue is I tried to add Noto Sans SC as a embedded font in my app (and set it as the primary font family) but whenever I open the app I get the error could not create glyph Typeface. I added the font as avalonia resource and in the configure fonts extension on app builder I added the font but it doesn't work. The code trying to add that is here
https://github.com/TheMulhima/Scarab/commit/ec4c6cd874ac59988b6217435b58e76b72834c13
Fixing either one of these issues would fix the underlying problem that is Chinese font isn't working. Thanks
Expected behavior

Specifying fallback fonts would use the fallback fonts when primary font is not found.
Embedding the primary font in the app similar to how Avalonia.Fonts.Inter does it should help resolve the couldn't create the Glyph Typeface error

Desktop (please complete the following information):

OS: Windows 11
Version 11.0.0.rc-2.2

Where do you reference fonts:Noto Sans SC?

After the builder is created, I call this function if the current culture is Chinese. Which then sets the font family to this (whose primary font is noto sans SC) using this code

FontFamily="fonts:Noto Sans SC#Noto Sans SC"

Where should that be added?

Adding that like this worked https://github.com/TheMulhima/Scarab/blob/fc8069e443b283afbb0b1b8e9d4d9cf232cc72a7/Scarab/Program.cs#L26
Thank you