Poison dps is not correctly calculated

With the 3.0 patch the way poison damage is scaled changed: many weapon nodes now add "increased damage with ailments" According to the Wiki  ailments include poison, bleeding, ignite, chill, freeze and shock, however selecting those nodes incorrectly does not actually show an increase in bleeding, poison or burning dps. I assume it will also not be factored into freeze/shock calculations, if there are any.
It would also be great to see the total "+damage with ailments" in the menu on the left.

I just tested with v1.4.59 and the Claw specific nodes near the shadow start at least work correctly, can you upload a pastebin for a build with non-working nodes?

I can't reproduce this; all of the Damage with Ailments nodes seem to be applying correctly when using the appropriate weapon type. Could you give me your build, and also point out some specific nodes that don't appear to be applying?

https://pastebin.com/vjcr1t2G is a build with a broken 100% to poison claw (for simplicity on comparing poison damage), the poison nodes near shadow are applying properly but the claw cluster just to the left of the poison cluster and the claw wheel are not applying to poison in anywhere near as meaningful of a way as the poison cluster.

The modifiers to Damage with Ailments from those nodes are applying correctly; this is from the Total Increased under Poison in the Calcs tab:

Then why does going from 0 to 100%+ increased damage not change the relationship between total damage per poison and average damage by more than 1%? Are those stats not included in the Poison DPS and Total Damage per Poison on the statbar on the left? The only nodes I've found that actually change those stats are the pure poison nodes.

Ah, never mind, for a bit there I forgot GGG changed the way ailments work in 3.0...

Fair enough then.
Incidentally, it is mechanically impossible for modifiers to be listed like that in the Calcs tab, but not apply to the numbers shown there or in the stats in the sidebar, as it all uses the same code to determine which modifiers apply.

This is the snapshot of the poison damage. Ailment increase is in the list, but the damage is not calculated correctly.
MH + Chaos shows as 4802.6 (looks correct) * 0.20 = 960 dps. This value is shown in the poison dps section. This for once completely ignores the 670% increase and additionally does not include the 80% chance to poison, so it should actually be 960 * 7.7 * 0.8 = 5913.6 dps. Same goes for the bleed dps calculation.
The total dps including poison then however shows a 10k dps increase for no apparent reason.

Actually, the 670% increase has already been factored into the calculation of the "4802.6" number. And the Poison DPS number is just the average DPS of each Poison stack; your Poison chance is factored in later, during the calculation of Total DPS inc. Poison, which is only shown in the sidebar.

With the base DPS of ~14k of mostly physical damage and a 20% * 80% poison dps of that dps it should be roughly around 2.2k dps without any modifiers, respectively around 17k dps with modifiers. The real number is of course lower, but 0.9k dps just cannot be correct given the numbers.

Doing the complete calculation:
MH + Chaos average hit: 2460
Including crit: 2619.9
At 4.12 attacks/s: 10793.988 dps
80% chance to poison for 20% of that damage: 1727,03808 poison dps
670% increased poison damage: 13298,193216 poison dps total.
There is either an error in my calculation or in the tool. ;)

Oh boy. What you're doing is fundamentally incorrect, due to the Damage over Time changes made in 3.0. Poison's base damage is no longer based on the actual hit damage, but rather is derived using an entirely separate calculation. That's why the program now displays "MH Source Chaos" (and should also display "MH Source Physical", but that's bugged ATM), which is the output of that calculation; and that calculation already includes all modifiers that affect poison damage.

Tough to find some exact information on that. Closest I could find was this from Mark GGG:

Poison deals 20% of the applicable (usually physical + chaos) base and added damage of the skill, per second

I can't however find any clarification what that added damage is.

"Added damage" means modifiers like "Adds X to Y Physical Damage to Attacks".

Got a very detailed official explanation: https://www.pathofexile.com/forum/view-thread/1930909/page/4#p14741874

I removed some items from the build to make the calculation easier:
Bow damage: 79 - 294 physical
Physical added: 48 - 75 (support gem and gloves)
Applicable modifiers: 1.33 (Belt) * 1.94 (Maim + Physical Projectile Support) * 0.69 (Chain support) * 0.614 (Barrage base damage modifier) = 1.093 total modifier
Applicable MH base damage is: (79 + 294 + 48 + 75) / 2 * 1.093 = 271,064
This means poison base damage is: 27.8 - 80.7 damage
Damage modifier: 7.5 (poison/ailment passive skills) * 1.49 (physical projectile support) = 11.175
Crit effect mod: 1+ 13% * 50% = 1.065
Avg poison dps per poison: (27.8 + 80.7) / 2 *11.175 * 1.065 = 645.65 dps (Calcs shows 547.1 here)
Poison damage total per hit: 645.65 dps * 2.8s = 1807.82 damage (Calc shows 1531.9 here based the the different value above)
Max poison stacks: 3.97 (attacks) * 2.8s = 11.1 (Calc shows 8.9 here)
Maximum sustained poison dps: 11.1 * 645.65 = 7177.05 (Calc shows 4870.8 here, not sure if this includes the 1785,1 bleed dps already, calculating total dps incl poison - total dps)
The numbers differ, but I cannot tell why. If my calculation is correct, poison dps displayed in the tool would be off significantly.

Could you give me the exact build? It'd be much easier for me to check the calculations if I had it.

bow_debug.zip

You don't need to upload the build .xml file to share builds; go to the Import/Export Build tab, then in the Build Sharing section you can generate a share code, which you can then turn into a pastebin.com link.
You've made two major errors in your calculations:

Damage modifiers (like PPAD and Chain) do not apply during the calculation of the base damage, and in fact Chain doesn't apply to Poison at all.
When modifying the base damage, you included modifiers for Chaos and Poison damage; but modifiers to Physical damage also apply to the Physical portion of the base damage (including the modifier from Maim).

So the correct calculations are:
Base weapon damage: (79 to 294) * 0.61 = 48.2 to 179.3
Base added damage: (48 to 75) * 0.61 = 29.3 to 45.8
Poison base damage: (48.2 + 179.3 + 29.3 + 45.8) / 2 * 0.2 = 30.2
Relevant modifiers:
650% increased Poison + Chaos Damage
121% increased Physical Damage
49% more Poison/Bleed Damage (from PPAD Support)
30% more Physical Damage (from Maim Support)
Crit effect modifier: 1.065
30.2 * (1 + 6.5 + 1.21) * 1.49 * 1.3 * 1.065 = 542.6 Poison DPS (off by ~1%, but that's rounding error)
Max stacks: 8.9 (you calculated that correctly)
542.6 * 8.9 = 4829.4

Thank you for the detailed explanation.
I am beginning to realize how difficult it is to get the correct formula with everything based on best guesses and occasional official explanations. Hopefully they fix the bug with the current display in the character sheet soon, so there is an officially correct base to check calculations.
It seems to me that I was wrong and the poison dps is correctly calculated (although displayed in a confusing way in the left summary window). Which also - sadly - means that poison dps is currently a worthless waste of skill points.


change color style

Here's how you would set your h2 element's text color to blue:

CatPhotoApp

Change your h2 element's style so that its text color is red.Challenge
my answer

"style="color: red">CatPhotoApp

so whats wrong?
Change the Color of Text has an issue.
User Agent is: Mozilla/5.0 (X11; CrOS x86_64 8743.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.101 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

"color: red">CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Hi,
The code for h2 tag should be:
CatPhotoApp

@scottpepperman Thank you for reporting this issue. Your code is incorrect. Please take a look at the two pieces of code you've written and compare the two. There is a difference that makes one correct and the other one not.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!

I know the issue is closed but I am also experiencing no success in getting this code snippet to work.

My copy/paste didn't pick up the entire statement.  It's:
CatPhotoApp


unsupported multiclient unsolicited response code 1009 Unhandled exception:

Steps to Reproduce

1-Installed flutter plug in from File -->Settings --> Plugin and install latest flutter plugin.
2- After that I created a new flutter project from android studio , which prompted me to install flutter SDK. I install flutter SDK and add the path.
3- Then i connected a device to the PC and run the application. I tried running it from android studio terminal here are the result.
Logs
Microsoft Windows [Version 10.0.17763.503]
(c) 2018 Microsoft Corporation. All rights reserved.

H:\AndroidStudio\timer>flutter run
Error retrieving device properties for ro.product.cpu.abi:

Launching lib/main.dart on SM G355H in debug mode...
Initializing gradle...                                              1.5s
Resolving dependencies...                                           7.2s
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
05-29 11:57:43.359 E/        (  173): unsupported multiclient unsolicited response code 1009
Unhandled exception:
Exit code -1073740940 from: C:\Users\imran.ali\AppData\Local\Android\sdk\platform-tools\adb.exe -s 4203c933c40d4100 shell -x logcat -v time -t 1
#0      _runWithLoggingSync (package:flutter_tools/src/base/process.dart:360:7)
#1      runCheckedSync (package:flutter_tools/src/base/process.dart:289:10)
#2      AndroidDevice.lastLogcatTimestamp (package:flutter_tools/src/android/android_device.dart:513:27)
#3      _AdbLogReader._start (package:flutter_tools/src/android/android_device.dart:688:41)
#4      _runGuarded (dart:async/stream_controller.dart:805:24)
#5      _BroadcastStreamController._subscribe (dart:async/broadcast_stream_controller.dart:213:7)
#6      _ControllerStream._createSubscription (dart:async/stream_controller.dart:818:19)
#7      _StreamImpl.listen (dart:async/stream_impl.dart:472:9)
#8      FlutterDevice.startEchoingDeviceLog (package:flutter_tools/src/resident_runner.dart:318:71)
#9      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:361:5)
<asynchronous suspension>
#10     HotRunner.run (package:flutter_tools/src/run_hot.dart:253:39)
<asynchronous suspension>
#11     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:428:37)
<asynchronous suspension>
#12     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
#13     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#14     _rootRunUnary (dart:async/zone.dart:1132:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#19     Future._complete (dart:async/future_impl.dart:473:7)
#20     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#21     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:28:18)
#22     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:294:13)
#23     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#24     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#25     _rootRunUnary (dart:async/zone.dart:1132:38)
#26     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#27     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#28     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#29     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#30     Future._complete (dart:async/future_impl.dart:473:7)
#31     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#32     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async-patch/async_patch.dart:33:20)
#33     _rootRun (dart:async/zone.dart:1124:13)
#34     _CustomZone.run (dart:async/zone.dart:1021:19)
#35     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#36     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#37     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#38     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
#39     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)

H:\AndroidStudio\timer>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17763.503], locale en-US)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.4)

Scanning for devices is taking a long time...-Error retrieving device properties for ro.product.cpu.abi:

[√] Connected device (1 available)

• No issues found!

H:\AndroidStudio\timer>flutter doctor -v
[√] Flutter (Channel beta, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17763.503], locale en-US)
    • Flutter version 1.5.4-hotfix.2 at H:\flutterSdk\flutter
    • Framework revision 7a4c33425d (4 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

Checking Android licenses is taking an unexpectedly long time...-Error retrieving device properties for ro.product.cpu.abi:

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\imran.ali\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[√] Connected device (1 available)
    • SM G355H • 4203c933c40d4100 • android-arm • Android null (API null)

• No issues found!

Already tried multiple options. Tried with emulator changing the device, restarting the IDE and PC as well. Adding ADBto path. But nothing worked.

This looks like the same issue as https://github.com/flutter/flutter/issues/33938. There's a PR at https://github.com/flutter/flutter/pull/33951 that should fix this.


Truncate charinfo results

Fixes #897
Just uses the LinePaginator. The raw field is present and has the exact same value on every page. I'm concerned it may be unclear whether the value is only for the current page or for the entire input (the truth is the latter).

I also updated the command to use the new send_denial utility function since the existing code was quite similar to what the helper does. The difference is that send_denial has those comedic titles.

could we use a bigger char limit

I don't mind it being 10 lines per page, with a 50 character max.

I was tempted but I ended up waiting for someone else to suggest it 👍


Different backends in a polymorphic model

I'm creating different backends using S3 for each model but I have a StoreImage model that is polymorphic, the store must be dynamic depending on where it comes from. How can I do that.
I have this in my StoreImage model:
class StoreImage < ActiveRecord::Base
  belongs_to :imageable, polymorphic: true
  attachment :file, content_type: ['image/jpeg', 'image/png', 'image/jpg'], store: 'business_images'
end

As you can see  store is static. I need to make it dynamic.

I have the same problem :(


Issue: Correctness of generated SQL queries

Issue you'd like to raise.
I have a huge database hosted in BigQuery. The recommended approach to querying this via natural language is using agents. However, this diminishes the control I have over the intermediate steps, and that leads to many problems.

The generated query isn't correct, and this cannot be reinforced at any intermediate step
Clauses like "ORDER BY" brings NULL to the top, and no amount of prompt engineering can retrieve the top non-null value

Are there any workarounds for this? Or is there any other approach recommended for handling databases of this scale?
Suggestion:
No response

Any progress made here getting more control before queries get full send over to BQ??


feat: powershell rprompt support

Prerequisites

[x] I have read and understand the CONTRIBUTING guide
[x] The commit message follows the conventional commits guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Description
Process rprompt blocks for Powershell.  For Powershell, align rprompt blocks to the right on the same line as the cursor.
** Note:
There is one side effect which some people may not like. If the user's input goes over into the region of the right aligned prompt text, it just clobbers the right aligned prompt text.  I'm not aware of any way around this, and I'm personally fine with it.

Yes, very much yes :-)

@TravisTX did you validate on Windows/MacOS?

@TravisTX did you validate on Windows/MacOS?

Windows only. Unfortunately, I do not have a MacOS computer.

I'll validate on MacOS then 👍🏻


refactor(center-story): stories now centered with official package #479

Closes #479
Summary

@storybook/addon-centered --dev package added as the new standard for
centering stories. https://github.com/storybookjs/storybook/tree/next/addons/centered

imported the new package and added the decorator in config.js

Removed in-line styling from .storybook/Container.js as the new package handles it

Updated the StoryShot snapshots because the new styling added new lines which shifted the rest of the stories down

Change List (commits, features, bugs, etc)

refactor(center-story): stories now centered with official package #479

Acceptance Test (how to verify the PR)

Check the built Storybook to see that each story is indeed centered. https://deploy-preview-790--carbon-addons-iot-react.netlify.com/

One of the challenges that I see with this 'centering' approach is that it is very hard to tell what padding/margin the component is exporting by looking at it.  Some components have padding, some don't.  This makes it hard to tell.

@stuckless While I understand your point, Carbon also centers their components in stories. It seems right to continue their style

@sstone2423 we just need to resolve this conflict and we can merge this.


ci(NODE-5124): ignore curl 92 errors when downloading node

Description
What is changing?
Is there new documentation needed for these changes?
What is the motivation for this change?

Double check the following

[ ] Ran npm run check:lint script
[ ] Self-review completed using the steps outlined here
[ ] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Doesn't seem like even code 92 will work.


Paginate RFC-5988?

Any plans to support pagination for RFC-5988?
We're using the api-pagination gem for rails and would like to find some support for it in angular:
https://github.com/davidcelis/api-pagination
It puts the pagination links in the headers like so:
Link: http://localhost:3000/movies?page=1; rel="first",
http://localhost:3000/movies?page=173; rel="last",
http://localhost:3000/movies?page=6; rel="next",
http://localhost:3000/movies?page=4; rel="prev"
Also, RFC-5988 is the pagination method that github uses in their API:
https://developer.github.com/guides/traversing-with-pagination/
If you would like support RFC-5988, I can try my best swing at it, just point me in the right direction.

Thinking about it one way, range headers are strictly more expressive than pagination link headers (I wrote about it here). But like you say many existing servers have already implemented rfc5988. Is your motivation that you want to paginate resources sent from a server you don't control and which uses the link style pagination?

I'm closing this issue. If you care to reopen let me know.


Add azd update or azd upgrade to update version

A la https://learn.microsoft.com/en-us/cli/azure/update-azure-cli

Initial thoughts (haven't explored the az CLI upgrade process in the code yet) about ways we might implement this and a number of scenarios we might encounter:

Linux

apt/yum - We can leave "witness marks" (i.e. text files) in the package that the binary can read from and infer the install method. This could lead us to run the correct command (i.e. sudo apt upgrade -y azd)
installer script - similar approach to run the curl ... | bash ... command, have the installer set down a "witness mark"

macOS

brew - It's probably possible to leave similar witness marks alongside the binary so we can upgrade using existing infrastructure. There may be interesting corner cases if brew is modified or uninstalled (more likely to happen on macs than with apt/yum on Linux, and also more likely that a user would change their brew binary at some point when running on Apple Silicon)
installer script - have the installer set down a "witness mark"

Windows -- More complicated. We're using the same MSI file to lay down files on the system. We could write "witness marks" to the registry. If the user changes install approaches (e.g. install v1.0.0 via install script, install v1.1.0 via choco, and v1.2.0 via winget) this may change how the package manager is tracking the installed package.

WinGet
Choco
Install script

Moving this one to Gallium cc: @savannahostrowski


Well Structure Documentation Site

Dear all,
My company has finally adopted Office 365 and in the last 2 months me and my team have had better and better surprises....
I am the head of governance of my company and became very interested in having this very site structure to accommodate our "Policies & Procedures" documentation.
How could I approach one of you to implement this same structure of the site into our company ?
Kind regards,
Reginaldo Junior

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f82b9891-876f-515b-5193-e2831dc05235
Version Independent ID: ae11d0d4-c0d6-ad28-341f-c9de5e5080f3
Content: Reference Policies, practices, and guidelines - Office 365
Content Source: microsoft-365/security/office-365-security/reference-policies-practices-and-guidelines.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

Hello @rjuun and thank you for your feedback. This does not appear to be a documentation issue (which is all we can address here). I'm not sure how to route your request, but you could contact support as your starting point. Thanks again, and kind regards.


[linux] maven install broke

Description
Since the maven github tag list returns latest version 3.8.4, but on the constructed maven downloadurl only version 3.8.3 is available the install fails with 404 not found.
    vhd: Downloading 'https://www-eu.apache.org/dist/maven/maven-3/3.8.4/binaries/apache-maven-3.8.4-bin.zip' to '/tmp/maven.zip'...
    vhd: Error — Either HTTP response code for 'https://www-eu.apache.org/dist/maven/maven-3/3.8.4/binaries/apache-maven-3.8.4-bin.zip' is wrong - '404' or exit code is not 0 - '0'. Waiting 30 seconds before the next attempt, 19 attempts left

Would it be better to get the "mavenDownloadUrl" by selecting the zipball_url value?
mavenDownloadUrl=$(echo $json | jq -r '.[1] | .zipball_url')
Virtual environments affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Date: Fri Nov 12 21:43:33 2021 +0300; Commit: 6dc8234648564472f721007db2336b03cec1b8a1 - [macOS] Remove node version 10.x (#4477); Author: Mikhail Koliada<EMAIL_ADDRESS>Is it regression?
No response
Expected behavior
maven will unzip latest version (3.8.4)
Actual behavior
maven binary 3.8.4 not found
Repro steps
Run the packer virtual-environments process for ubuntu20.04
Used the following commit
Date: Fri Nov 12 21:43:33 2021 +0300; Commit: 6dc8234648564472f721007db2336b03cec1b8a1

@HUMBERP Hello!
The problem is that zipball does not have the binary we are installing, only sources

Ok, what about to use
curl -s "http://dlcdn.apache.org/maven/maven-3/"
and extract the latest version from the returned xml structure?

@HUMBERP we have decided to stick to the exact version and update the toolset file manually. The changes are merged and the main branch should work now.


Broken stories: related to next-auth

The following stories are broken and show the same error on Storybook:

AppNav
Error
Layout
Pages/Contributors
Pages/ForgotPassword
Pages/ResetPassword
Pages/UserProfile

I'll look into this issue after migration #2860

This definitely solves the challenge, but it doesn't help you solidify what you learned in the lesson. Your 2nd submission was great. By "simplifying" I meant to simplify it from:
const solution = (num1, num2, num3) => {
  if (num1 > num2 && num1 > num3) {
    return num1;
  } else if (num2 > num1 && num2 > num3) {
    return num2;
  } else if (num3 > num1 && num3 > num2) {
    return num3;
  } else {
    return num3;
  }
};

To:
.div {
  background-color: 20px;
}

I hope you see how this is more simplified than the previous one :)


Critical security update

Hey guys,
could you update your fasterxml dependency to newest version 2.9.5? The one you are using now has critical security vulnerability and fahrschein its the only one we have using those
https://nvd.nist.gov/view/vuln/search-results?adv_search=true&cves=on&cpe_version=cpe%3A%2Fa%3Afasterxml%3Ajackson-databind%3A2.9.3

@lukasniemeier-zalando probably you are right. I just run our dependencies through dependency-check-maven from owasp saw you are using high risk lib and decided to let you know about that.
@jhorstmann it is a one line fix. Would take me more time to clone repo and create PR then to fix it. Can't you just release it with next update? @lukasniemeier-zalando suggested its not as critical as I thought

Closed via https://github.com/zalando-nakadi/fahrschein/pull/269


Add more flexibility to 3X3 autotiles

Removes some conditions that were there to create compatibility of 2X2 conversion to 3X3, but limited a number of possibilities, such as stairs. A runtime conversion of 2X2 to 3X3 bitmasks is a extremely rare, if even that, thing to need (and even so it's still possible), and an editor conversion can be quickly fixed, so it's not a big deal.
Addresses  #16511

@MarianoGnu

yeah, makes sense, but at the same time might cause backward compatibility breackage if omeone expected the previous behabiour, but should be safe, since this wont change already saved maps, unless they are generated randonly using code instead of drawing from the editor. i think a notice on the changelog about this in the next release is enought.

All right, finished reviewing the code, i think it's safe to merge this

Thanks for the fix and the review!


Remove shadow properties

Bug
If BaGet is started in debug mode it will log:
dbug: Microsoft.EntityFrameworkCore.Model.Validation[10600]
      The property 'PackageKey' on entity type 'PackageDependency' was created in shadow state because there are no eligible CLR members with a matching name.
dbug: Microsoft.EntityFrameworkCore.Model.Validation[10600]
      The property 'PackageKey' on entity type 'PackageType' was created in shadow state because there are no eligible CLR members with a matching name.
dbug: Microsoft.EntityFrameworkCore.Model.Validation[10600]
      The property 'PackageKey' on entity type 'TargetFramework' was created in shadow state because there are no eligible CLR members with a matching name.

These logs were added in EF Core 3.
Fix

Add a public int PackageKey { get; set; } property to the PackageType, PackageDependency, and TargetFramework entities.
Generate new migrations, if any

Additional Context
See the documentation on shadow properties: https://docs.microsoft.com/en-us/ef/core/modeling/shadow-properties#foreign-key-shadow-properties

Based on this discussion in the ef repo I am trying to produce a migration to copy the PackageDependencies data to a new table with the new non-nullable FK, but that might be better as a separate issue?

I ran into a similar problem with the case sensitivity on the Version column on SQLite (see https://github.com/loic-sharma/BaGet/pull/466). SQLite cannot alter existing columns, so fixing this in a migration would require a similar trick (create new table -> copy data -> delete original table -> rename new table). I ended up doing a cheaper hack instead: I fixed the column by modifying the initial migration instead of adding a new migration. This fixes new databases going forward; old databases don't get the fix but can be recreated. I think we should take a similar approach for the PackageDependencies table.


[Analyzer] Missing static error on an indirect implementation of a base class.

The static analysis section of the class modifiers spec specifies that the error around implementing a base class from another library extends through the transitive closure of the super-declarations:
    A declaration implements another declaration, and the other
    declaration itself, or any of its super-declarations,
    are marked `base` or `final` and are not from the first declaration's
    library _(with some exceptions for platform libraries)_.

    _(You can only implement an interface if *all* `base` or `final`
    superdeclarations are inside your own library. Or if you're in
    a pre-feature library and all `base` or `final` superdeclarations
    are in platform libraries.)_

    More formally:
    A declaration *C* in library *L* has a declared interface *P*,
    and *P* has any superdeclaration *S*, from a library *K*,
    which is marked `base` or `final` _(including *S* being *P* itself)_,
    and neither:
    * *K* and *L* is the same library, mor
    * *K* is a platform library and *L* is a pre-feature library.

The analyzer does not seem to report this error, the following code produces no error when tested at current HEAD:
// lib.dart
base class C {}

// test.dart
import "lib.dart";
base class Base extends C {}
base class Nefarious implements Base  {}

We seem to currently have no test coverage for this error (and the related errors for final, and for the mixin and mixin class cases).
@munificent is working on adding tests, @dart-lang/language-team please help expedite reviews and landing here.
cc @kallentu @srawlins @bwilkerson @scheglov @itsjustkevin
Tentatively marking this as a blocker for stable, let's plan on a cherry pick if at all possible.  If the fix looks like it will be hard to land in that time frame, we can discuss alternatives and possibly aim for the first patch release.

Duplicate of https://github.com/dart-lang/sdk/issues/52056 ?

I see that https://github.com/dart-lang/sdk/issues/52056 is assigned to @kallentu, so it looks to me that she is working on fixing it in the analyzer as well.
Correct me if this is not so.

Kallen's on vacation this week so given that this is a blocker for stable, we probably shouldn't wait for her return 😃

https://dart-review.googlesource.com/c/sdk/+/298320

cc @goderbauer @zanderso as a heads up - this is a missing static error in both CFE and analyzer, there's a chance that we will need to do some fixup in flutter to roll this.

cc @jason-simmons the engine sheriff
cc @brianquinlan who I think is the VM gardener today.


Compile Folder action fails: Repository '@@intellij_aspect' is not defined

Description of the bug:
When I attempt to use the "Compile Folder" action with the latest version of the plugin (2<IP_ADDRESS>.1-api-version-242), it fails with the following error:
ERROR: Unable to find package for @@intellij_aspect//:intellij_info_bundled.bzl: The repository '@@intellij_aspect' could not be resolved: Repository '@@intellij_aspect' is not defined.

This issue did not occur with the previous version (2<IP_ADDRESS>.2-api-version-242).
The key difference seems to be that the --override_repository flag is no longer passed with the new version. Here's a comparison of the Bazel build commands:
Command with the previous version (works):
bazel build --tool_tag=ijwb:IDEA:community --override_repository='intellij_aspect=/Users/vere10/Library/Application Support/JetBrains/IdeaIC2024.2/plugins/ijwb/aspect' --target_pattern_file=/Users/vere10/verticals-backend/.ijwb/targets/targets-9859192668652861174 --keep_going --build_event_binary_file=/var/folders/rw/1t27mg_52f76gczdd9gt52fj3h788y/T/intellij-bep-5a883ba1-2da1-416c-bc1a-fc05596f2d16 --nobuild_event_binary_file_path_conversion --curses=no --color=yes --noprogress_in_terminal_title --norun_validations --aspects=@@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --output_groups=intellij-compile-java,intellij-compile-py

Command with the latest version (fails):
bazel build --tool_tag=ijwb:IDEA:community --target_pattern_file=/Users/vere10/verticals-backend/.ijwb/targets/targets-9240279939158111114 --keep_going --curses=no --color=yes --noprogress_in_terminal_title --norun_validations --aspects=@@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --output_groups=intellij-compile-java,intellij-compile-py --build_event_binary_file=/var/folders/rw/1t27mg_52f76gczdd9gt52fj3h788y/T/intellij-bep-64ab9a9c-3184-459a-9d21-1f69e0d85011 --nobuild_event_binary_file_path_conversion --build_event_publish_all_actions

The absence of the --override_repository flag in the latest version seems to be causing this issue, as the required repository @@intellij_aspect cannot be resolved.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Use the latest plugin version (2<IP_ADDRESS>.1-api-version-242).
Run the "Compile Folder" action.
Observe the error.

Which Intellij IDE are you using? Please provide the specific version.
2<IP_ADDRESS> (Community Edition), Build #IC-242.20224.419
What programming languages and tools are you using? Please provide specific versions.
Java 21
What Bazel plugin version are you using?
2<IP_ADDRESS>.1-api-version-242
Have you found anything relevant by searching the web?
https://github.com/bazelbuild/intellij/pull/7048 — this might be related, but I’m not sure
https://github.com/bazelbuild/intellij/issues/6705 — this describes a similar issue
Any other information, logs, or outputs that you want to share?
No response

@tpasternak

I think this is fixed with https://github.com/bazelbuild/intellij/pull/7135


App not running

I have developed a fairly complex application based on this template, but have constantly encountered the problem that the application does not always run, but 50% of the time. Sometimes even less. I suspect that vite does not have time to build main.js and electron builds the application while main.js does not yet exist.
I decided to find out where this error came from and started the application from the beginning, and got this error after adding just a couple of files
$ node -v
v18.15.0
chrome
112.0.5615.138
Windows 11 Pro / 22H2 / 22621.1555

All I added to the project is the following

package.json
{
  "name": "electrovite-react",
  "productName": "ElectroVite",
  "version": "1.0.0",
  "description": "A prebuilt project for creating desktop apps with Electron, React, TypeScript & super fast hot-reload of Vite.",
  "main": ".vite/build/main.js",
  "license": "MIT",
  "author": {
    "name": "guasam",
    "url": "https://github.com/guasam"
  },
  "keywords": [
    "electrovite",
    "electron hot reload fast",
    "electron-boilerplate",
    "boilerplate",
    "electron-vite",
    "electron vitejs react",
    "vitejs with electron",
    "electron react boilerplate",
    "reactjs electronjs",
    "secure electron react app"
  ],
  "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "eslint src tools --ext ts,tsx --max-warnings 0"
  },
  "config": {
    "forge": "./tools/forge/forge.config.js"
  },
  "devDependencies": {
    "@electron-forge/cli": "^6.1.1",
    "@electron-forge/maker-deb": "^6.1.1",
    "@electron-forge/maker-rpm": "^6.1.1",
    "@electron-forge/maker-squirrel": "^6.1.1",
    "@electron-forge/maker-zip": "^6.1.1",
    "@electron-forge/plugin-vite": "^6.1.1",
    "@types/react": "^18.2.0",
    "@types/react-dom": "^18.2.1",
    "@typescript-eslint/eslint-plugin": "^5.59.1",
    "@typescript-eslint/parser": "^5.59.1",
    "@vitejs/plugin-react": "^4.0.0",
    "electron": "24.1.2",
    "eslint": "^8.39.0",
    "eslint-plugin-react-hooks": "^4.6.0",
    "eslint-plugin-react-refresh": "^0.3.4",
    "sass": "^1.62.1",
    "typescript": "^5.0.4",
    "vite": "^4.3.2"
  },
  "dependencies": {
    "electron-squirrel-startup": "^1.0.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  }
}

index.ts
export enum SettingsMy {
  SYNC = 'settings:sync',
  SAVE = 'settings:save',
  RESET = 'settings:reset',
}

menu.ts
import {
  app,
  Menu,
  shell,
  BrowserWindow,
  MenuItemConstructorOptions,
} from 'electron';
import { SettingsMy } from '../types';

interface DarwinMenuItemConstructorOptions extends MenuItemConstructorOptions {
  selector?: string;
  submenu?: DarwinMenuItemConstructorOptions[] | Menu;
}

export default class MenuBuilder {
  mainWindow: BrowserWindow;

  constructor(mainWindow: BrowserWindow) {
    this.mainWindow = mainWindow;
  }

  buildMenu(): Menu {
    if (
      process.env.NODE_ENV === 'development' ||
      process.env.DEBUG_PROD === 'true'
    ) {
      this.setupDevelopmentEnvironment();
    }

    const template =
      process.platform === 'darwin'
        ? this.buildDarwinTemplate()
        : this.buildDefaultTemplate();

    const menu = Menu.buildFromTemplate(template);
    Menu.setApplicationMenu(menu);

    return menu;
  }

  setupDevelopmentEnvironment(): void {
    this.mainWindow.webContents.on('context-menu', (_, props) => {
      const { x, y } = props;

      Menu.buildFromTemplate([
        {
          label: 'Inspect element',
          click: () => {
            this.mainWindow.webContents.inspectElement(x, y);
          },
        },
      ]).popup({ window: this.mainWindow });
    });
  }

  buildDarwinTemplate(): MenuItemConstructorOptions[] {
    const subMenuAbout: DarwinMenuItemConstructorOptions = {
      label: 'Electron',
      submenu: [
        {
          label: 'About ElectronReact',
          selector: 'orderFrontStandardAboutPanel:',
        },
        { type: 'separator' },
        { label: 'Services', submenu: [] },
        { type: 'separator' },
        {
          label: 'Hide ElectronReact',
          accelerator: 'Command+H',
          selector: 'hide:',
        },
        {
          label: 'Hide Others',
          accelerator: 'Command+Shift+H',
          selector: 'hideOtherApplications:',
        },
        { label: 'Show All', selector: 'unhideAllApplications:' },
        { type: 'separator' },
        {
          label: 'Quit',
          accelerator: 'Command+Q',
          click: () => {
            app.quit();
          },
        },
      ],
    };
    const subMenuEdit: DarwinMenuItemConstructorOptions = {
      label: 'Edit',
      submenu: [
        { label: 'Undo', accelerator: 'Command+Z', selector: 'undo:' },
        { label: 'Redo', accelerator: 'Shift+Command+Z', selector: 'redo:' },
        { type: 'separator' },
        { label: 'Cut', accelerator: 'Command+X', selector: 'cut:' },
        { label: 'Copy', accelerator: 'Command+C', selector: 'copy:' },
        { label: 'Paste', accelerator: 'Command+V', selector: 'paste:' },
        {
          label: 'Select All',
          accelerator: 'Command+A',
          selector: 'selectAll:',
        },
      ],
    };
    const subMenuViewDev: MenuItemConstructorOptions = {
      label: 'View',
      submenu: [
        {
          label: 'Reload',
          accelerator: 'Command+R',
          click: () => {
            this.mainWindow.webContents.reload();
          },
        },
        {
          label: 'Toggle Full Screen',
          accelerator: 'Ctrl+Command+F',
          click: () => {
            this.mainWindow.setFullScreen(!this.mainWindow.isFullScreen());
          },
        },
        {
          label: 'Toggle Developer Tools',
          accelerator: 'Alt+Command+I',
          click: () => {
            this.mainWindow.webContents.toggleDevTools();
          },
        },
      ],
    };
    const subMenuViewProd: MenuItemConstructorOptions = {
      label: 'View',
      submenu: [
        {
          label: 'Toggle Full Screen',
          accelerator: 'Ctrl+Command+F',
          click: () => {
            this.mainWindow.setFullScreen(!this.mainWindow.isFullScreen());
          },
        },
      ],
    };
    const subMenuWindow: DarwinMenuItemConstructorOptions = {
      label: 'Window',
      submenu: [
        {
          label: 'Minimize',
          accelerator: 'Command+M',
          selector: 'performMiniaturize:',
        },
        { label: 'Close', accelerator: 'Command+W', selector: 'performClose:' },
        { type: 'separator' },
        { label: 'Bring All to Front', selector: 'arrangeInFront:' },
      ],
    };
    const subMenuSettings: DarwinMenuItemConstructorOptions = {
      label: 'Settings',
      submenu: [
        {
          click: () => this.mainWindow.webContents.send('save-options', 1),
          label: 'Save options',
        },
        {
          click: () => this.mainWindow.webContents.send('reset-options', 1),
          label: 'Reset options',
        },
      ],
    };

    const subMenuView =
      process.env.NODE_ENV === 'development' ||
      process.env.DEBUG_PROD === 'true'
        ? subMenuViewDev
        : subMenuViewProd;

    return [
      subMenuAbout,
      subMenuEdit,
      subMenuView,
      subMenuWindow,
      subMenuSettings,
    ];
  }

  buildDefaultTemplate() {
    const templateDefault = [
      {
        label: '&File',
        submenu: [
          {
            label: '&Open',
            accelerator: 'Ctrl+O',
          },
          {
            label: '&Close',
            accelerator: 'Ctrl+W',
            click: () => {
              this.mainWindow.close();
            },
          },
        ],
      },
      {
        label: '&View',
        submenu:
          process.env.NODE_ENV === 'development' ||
          process.env.DEBUG_PROD === 'true'
            ? [
                {
                  label: '&Reload',
                  accelerator: 'Ctrl+R',
                  click: () => {
                    this.mainWindow.webContents.reload();
                  },
                },
                {
                  label: 'Toggle &Full Screen',
                  accelerator: 'F11',
                  click: () => {
                    this.mainWindow.setFullScreen(
                      !this.mainWindow.isFullScreen(),
                    );
                  },
                },
                {
                  label: 'Toggle &Developer Tools',
                  accelerator: 'Alt+Ctrl+I',
                  click: () => {
                    this.mainWindow.webContents.toggleDevTools();
                  },
                },
              ]
            : [
                {
                  label: 'Toggle &Full Screen',
                  accelerator: 'F11',
                  click: () => {
                    this.mainWindow.setFullScreen(
                      !this.mainWindow.isFullScreen(),
                    );
                  },
                },
              ],
      },
      {
        label: 'Settings',
        submenu: [
          {
            click: () => this.mainWindow.webContents.send(SettingsMy.SAVE, 1),
            label: 'Save options',
          },
          {
            click: () => this.mainWindow.webContents.send(SettingsMy.RESET, 1),
            label: 'Reset options',
          },
        ],
      },
    ];

    return templateDefault;
  }
}

main.ts
import { app, BrowserWindow } from 'electron';
import path from 'path';
import MenuBuilder from './menu';

/** Handle creating/removing shortcuts on Windows when installing/uninstalling. */
if (require('electron-squirrel-startup')) {
  app.quit();
}

/**
 * Main window instance.
 */
let mainWindow: BrowserWindow | null;
declare const MAIN_WINDOW_VITE_DEV_SERVER_URL: string;
declare const MAIN_WINDOW_VITE_NAME: string;

/**
 * This method will be called when Electron has finished
 * initialization and is ready to create browser windows.
 * Some APIs can only be used after this event occurs.
 */
app.on('ready', createMainWindow);

/**
 * Emitted when the application is activated. Various actions can
 * trigger this event, such as launching the application for the first time,
 * attempting to re-launch the application when it's already running,
 * or clicking on the application's dock or taskbar icon.
 */
app.on('activate', () => {
  /**
   * On OS X it's common to re-create a window in the app when the
   * dock icon is clicked and there are no other windows open.
   */
  if (BrowserWindow.getAllWindows().length === 0) {
    createMainWindow();
  }
});

/**
 * Emitted when all windows have been closed.
 */
app.on('window-all-closed', () => {
  /**
   * On OS X it is common for applications and their menu bar
   * to stay active until the user quits explicitly with Cmd + Q
   */
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

/**
 * Create main window
 * @returns {BrowserWindow} Main window instance
 */

function createMainWindow() {
  mainWindow = new BrowserWindow({
    width: 1600,
    height: 900,
    backgroundColor: '#202020',
    show: false,
    autoHideMenuBar: false,
    icon: path.resolve('assets/favicon.ico'),
    webPreferences: {
      nodeIntegration: false,
      contextIsolation: true,
      nodeIntegrationInWorker: false,
      nodeIntegrationInSubFrames: false,
      preload: path.join(__dirname, 'preload.js'),
      sandbox: false,
    },
  });

  // Load the index.html of the app window.
  if (MAIN_WINDOW_VITE_DEV_SERVER_URL) {
    mainWindow.loadURL(MAIN_WINDOW_VITE_DEV_SERVER_URL);
  } else {
    mainWindow.loadFile(
      path.join(__dirname, `../renderer/${MAIN_WINDOW_VITE_NAME}/index.html`),
    );
  }
  const menuBuilder = new MenuBuilder(mainWindow);
  menuBuilder.buildMenu();
  // Show window when its ready to
  mainWindow.on('ready-to-show', () => {
    if (mainWindow) mainWindow.show();
  });

  // Close all windows when main window is closed
  mainWindow.on('close', () => {
    mainWindow = null;
    app.quit();
  });

  return mainWindow;
}

/**
 * In this file you can include the rest of your app's specific main process code.
 * You can also put them in separate files and import them here.
 */

Hello @vahromeevilya-widestudio
Gave it a try and seems like working fine.
Node Version:
v18.4.0

Sometimes when we close the app window, we can still notice the terminal is still running the process. So make sure to close the terminal process before running a new instance.

Yes, the application runs sometimes, but that's the problem - only sometimes. Maybe there is some setting to compile main.js first, and only then start the application?
The quality of the video is low, in order to be able to upload it here. But you can see the problem.
https://user-images.githubusercontent.com/98152955/236664995-cde55015-abac-4a1c-b803-7e32e949f829.mp4

It does compile the main process code first and then it goes for devserver (renderer).

I've tried it plenty of times using the source code mentioned above, couldn't reproduce the error you are getting, starts the application here without any issues.
Did you also try to use "npm package" command to see if building executable works or that also causes some error?
Another thing you can try is to remove existing node_modules directory and re-install all the packages using yarn or npm

I created another video, it is unfortunately too big to upload here will give you a link to Yandex, so you can watch it.
The essence of the video: I created a project from scratch from your template, and repeated all the steps I described. There really is no bug. Then I went to my existing project reinstalled the dependencies and the bug still appeared. I forgot to use in the video command npm run package , so attached a screenshot of the problem from the project, where it does not work
Also in the problematic project I moved the index.ts from the types folder to main, I thought the problem was in the types folder. Didn't make any difference
link to video

When you created that new project there isn't any error during app launch?
It'd be nice if you could create a repository based on the project you were having errors with, will try to replicate and see if errors happen by using that repository.


XgBoost error on running xgb.cv - could not find function xgb.cv

Need help - I am running xgb.cv with command below but i get error - Error: could not find function "xgb.cv"
xgboostcv <- xgb.cv(param= param, data  = datamatrix , label = datamatrix, nfold = cv.nfold, nrounds = cv.nround)
What Am I doing wrong here

Please complete your question following the instructions in https://raw.githubusercontent.com/dmlc/xgboost/master/ISSUE_TEMPLATE.md.


added name

sir please merge my pull request and also level it

@sanjay-kv please merge it

this is practice repo

ok


Feature/end to end tests

Codecov Report

Merging #255 (b94b5aa) into main (801561f) will increase coverage by 1.85%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #255      +/-   ##
==========================================
+ Coverage   54.67%   56.52%   +1.85%
==========================================
  Files         228      228
  Lines       27905    27899       -6
==========================================
+ Hits        15257    15771     +514
+ Misses      12648    12128     -520

Flag
Coverage Δ

gsagh
42.10% <0.00%> (+<0.01%)
:arrow_up:

integration
44.92% <0.00%> (+2.64%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <0.00%> (+0.60%)
:arrow_up:

...aGH/Components/5_Results/BeamStrainEnergyResult.cs
53.44% <0.00%> (+0.45%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
61.53% <0.00%> (-0.10%)
:arrow_down:

GsaGH/Components/5_Results/Elem2dContourResults.cs
56.76% <0.00%> (-0.09%)
:arrow_down:

...H/Components/5_Results/Elem2dDisplacementResult.cs
39.41% <0.00%> (+0.28%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
41.66% <0.00%> (+0.24%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dStressResult.cs
42.55% <0.00%> (+0.29%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

... and 19 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Codecov Report

Merging #255 (21d9db1) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

GsaGH/Components/5_Results/NodeContourResults.cs
63.90% <51.51%> (+34.98%)
:arrow_up:

... and 124 more

Codecov Report

Merging #255 (45d804d) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

GsaGH/Components/5_Results/NodeContourResults.cs
63.90% <51.51%> (+34.98%)
:arrow_up:

... and 124 more

Codecov Report

Merging #255 (3f5c50c) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

:exclamation: Current head 3f5c50c differs from pull request most recent head 79d6a82. Consider uploading reports for the commit 79d6a82 to get more accurate results

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

GsaGH/Components/5_Results/NodeContourResults.cs
63.90% <51.51%> (+34.98%)
:arrow_up:

... and 124 more

Codecov Report

Merging #255 (79d6a82) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

GsaGH/Components/5_Results/NodeContourResults.cs
63.90% <51.51%> (+34.98%)
:arrow_up:

... and 124 more

Codecov Report

Merging #255 (07e96e3) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (f8bfcbc) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (f6bab6d) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (ba7fc32) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (6ff1f53) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (ed96395) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (676d955) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (766df5c) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more

Codecov Report

Merging #255 (a617b25) into main (801561f) will increase coverage by 16.85%.
The diff coverage is 65.39%.

@@             Coverage Diff             @@
##             main     #255       +/-   ##
===========================================
+ Coverage   54.67%   71.52%   +16.85%
===========================================
  Files         228      148       -80
  Lines       27905    20661     -7244
===========================================
- Hits        15257    14778      -479
+ Misses      12648     5883     -6765

Impacted Files
Coverage Δ

GsaGH/Components/5_Results/BeamDispResult.cs
94.32% <0.00%> (+0.66%)
:arrow_up:

...H/Components/5_Results/Elem2dDisplacementResult.cs
93.43% <0.00%> (+54.30%)
:arrow_up:

GsaGH/Components/5_Results/Elem2dForceResult.cs
94.64% <0.00%> (+53.22%)
:arrow_up:

...H/Components/5_Results/Elem3dDisplacementResult.cs
88.48% <0.00%> (+49.91%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dStressResult.cs
41.04% <0.00%> (+0.30%)
:arrow_up:

GsaGH/GsaGHInfo.cs
50.00% <ø> (ø)

GsaGH/Helpers/GH/RibbonLayout.cs
100.00% <ø> (+27.27%)
:arrow_up:

GsaGH/Components/5_Results/BeamForceResult.cs
94.87% <33.33%> (+0.60%)
:arrow_up:

GsaGH/Components/5_Results/Elem3dContourResults.cs
50.69% <42.85%> (+35.05%)
:arrow_up:

GsaGH/Components/5_Results/Elem1dContourResults.cs
65.76% <49.20%> (+4.13%)
:arrow_up:

... and 125 more


Use a "warning" icon in OS.alert() on Linux/*BSD

This is the same icon as used on Windows.
Preview
Using Fedora 37 and KDE Breeze Dark theme.
Zenity

KDialog

Title and description seem swapped in the Zenity example.

Thanks!


feat: Delete Wallet & Organization

Closing this task
new link: https://github.com/credebl/platform/issues/335


fixed manageSubscriptions where it should call manageSubscription

instead of manageViewSubscription in RxTiPresenterSubscriptionHandler

Oh wow!
Nice catch. Thank you 👍
Can you please add a test so that something like that will never happen again?!
You can simple copy tests like this but called manageSubscriptions.

@StefMa sure, I'll write up that right now.

@StefMa didn't want to introduce something new, so I followed up manageSusbription tests.

Ouch, that was a good catch!

@StefMa please add a test for RxTiPresenterDisposableHandler#manageDisposables(Disposable...)


SW-4617 Remove the query param and sub location filtering within the inventory list of batches

The query param logic is baked into the InventoryTable (in a later PR) for all filters.
The sub location scrubbing is baked into the Search component (in a later PR) which is where facilities are being populated and selected.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1965

PR #1966

PR #1967

PR #1968   👈

This stack of pull requests is managed by Graphite.

Trying out another build

@karthikbtf  👀

Merge activity

Jan 3, 3:04 PM: @nickgraz started a stack merge that includes this pull request via Graphite.


[after upgraded to v3] Try to add ViewTransitions!

We are not going to add view transitions to this project, nor the tutorial itself.
BUT, we would like to ensure that the project will work if someone who takes it then wants to add View Transitions themselves.
So, once the project has been upgraded to v3.x, and once we are happy with the theme toggle and hamburger menu (which are the things that might have trouble with view transitions?), try adding it and see whether it can be successfully done.
Please report any issues you had doing so, or changes you needed to make to get it to work.  We could eventually turn this into an "Add View Transitions to the Build a Blog Tutorial!" the same way we have done for content collections.

It Works!


where is time series code?

sorry, I do not search code about time series?

The code is in this folder https://github.com/doloMing/Transfer-entropy-spectrum-in-the-Fourier-domain/tree/Beta-Version/Initial-MATLAB-version


Error: Wrong response status (redundant)

OS: Windows 10 Pro
React: 15.6.1
Offline-plugin: 4.8.3
Webpack: 3.10.0
So I receiving the above mentioned error, and am not sure why.
What's the issue here? (see attached images)
Here is my webpack file:
const path = require('path');
const webpack = require('webpack');
const SWPrecacheWebpackPlugin = require('sw-precache-webpack-plugin');
const Dotenv = require('dotenv-webpack');
const CleanWebpackPlugin = require('clean-webpack-plugin');
const HtmlWebpackPlugin = require('html-webpack-plugin');
const CopyWebpackPlugin = require('copy-webpack-plugin');
const OfflinePlugin = require('offline-plugin');

module.exports = {
  devtool: 'source-map',
  context: __dirname,
  entry: {
    main: path.resolve(__dirname, './client/index'),
    vendor: [
      'react',
      'react-dom'
    ]
  },
  plugins: [
    new Dotenv({
      path: './.env',
      safe: true
    }),
    new webpack.DefinePlugin({
      'process.env': {
        'NODE_ENV': "'production'"
      }
    }),
    new webpack.optimize.UglifyJsPlugin({
      compressor: {
        warnings: false
      }
    }),
    new CleanWebpackPlugin(['public']), //Cleans webpack folder before new build
    new HtmlWebpackPlugin({
      title: 'Flamingo City',
      filename: 'index.html',
      template: './index_template.ejs',
    }),
    // See section on 'Extracting Boilerplate: https://webpack.js.org/guides/caching/
    new webpack.HashedModuleIdsPlugin(),
    new webpack.optimize.CommonsChunkPlugin({
      // name: 'vendor'
      names: [ 'vendor', 'manifest' ],
      minChunks: Infinity
    }),
    new webpack.optimize.CommonsChunkPlugin({
      // name: 'manifest'
      async: true,
      children: true,
      minChunks: 4
    }),
    new CopyWebpackPlugin([
      { from: '404.html' },
      { from: 'offline-page.html'},
      { from: 'manifest.json' },
      { from: 'images', to: 'images' },
    ]),
    new OfflinePlugin({
      publicPath: '/',
      safeToUseOptionalCaches: true,
      caches: {
        main: [
          'main-*.js',
          'vendor-*.js',
          'manifest-*.js',
          'index.html',
          '404.html',
          'offline-page.html'
        ],
        additional: [
          ':externals:'
        ],
        optional: [
          ':rest:'
        ]
      },
      externals: [
        '/',
      ],
      ServiceWorker: {
        navigateFallbackURL: '/',
        events: true
      },
      AppCache: {
        FALLBACK: {
          '/': '/offline-page.html'
        },
        events: true
      }
    })
  ],
  output: {
    path: path.join(__dirname, '/public'),
    filename: '[name]-[chunkhash].js',
    publicPath: '/'
  },
  module: {
    rules: [
    // js
    {
      test: /\.js$/,
      use: ['babel-loader'],
      include: path.join(__dirname, 'client')
    },
    // CSS
    {
      test: /\.styl$/,
      include: path.join(__dirname, 'client'),
      use: [
        'style-loader',
        'css-loader',
        'stylus-loader'
      ]
    },
    // sCSS
    {
      test: /\.scss$/,
      include: path.join(__dirname, 'client'),
      use: [
        'style-loader',
        'css-loader',
        'sass-loader'
      ]
    }
    ]
  }
};

My build output is as follows:
Hash: 11e8b97b1153e2c01447
Version: webpack 3.10.0
Time: 60445ms
                           Asset       Size  Chunks                    Chunk Names
   images/icons/icon-152x152.png    5.95 kB          [emitted]
    main-451a5c4adcac7c55b9ea.js     634 kB       0  [emitted]  [big]  main
manifest-fc1f0cec7e8359aeae35.js    1.42 kB       2  [emitted]         manifest
                      index.html    1.04 kB          [emitted]
                        404.html    7.09 kB          [emitted]
               offline-page.html    1.72 kB          [emitted]
                   manifest.json    1.17 kB          [emitted]
             images/Bitmap-3.png    8.48 kB          [emitted]
   images/icons/icon-144x144.png    5.61 kB          [emitted]
   images/icons/icon-128x128.png    4.99 kB          [emitted]
  vendor-0d1fa8f65388c33bce4e.js     149 kB       1  [emitted]         vendor
   images/icons/icon-192x192.png    7.67 kB          [emitted]
   images/icons/icon-384x384.png    7.08 kB          [emitted]
   images/icons/icon-512x512.png    7.08 kB          [emitted]
     images/icons/icon-72x72.png    2.51 kB          [emitted]
     images/icons/icon-96x96.png    3.55 kB          [emitted]
    images/my-favourite-icon.png    13.5 kB          [emitted]
                           sw.js    9.89 kB          [emitted]
      appcache/manifest.appcache  234 bytes          [emitted]
          appcache/manifest.html     3.3 kB          [emitted]
[/Oho] ./client/store.js 2.15 kB {0} [built]
[0uOD] ./client/graphql/mutations-queries.js 8 kB {0} [built]
[6rQ3] ./client/index.js 413 bytes {0} [built]
[DuR2] (webpack)/buildin/global.js 509 bytes {0} [built]
[J+H8] ./client/app.js 5.75 kB {0} [built]
[J4bL] ./client/data/config.js 1.56 kB {0} [built]
[J7fb] ./client/reducers/index.js 1.47 kB {0} [built]
[OvED] ./node_modules/css-loader!./node_modules/stylus-loader!./client/styles/style.styl 6.9 kB {0} [built]
[Swe4] ./client/reducers/logOut.js 477 bytes {0} [built]
[VUDS] ./client/reducers/tokenDetails.js 949 bytes {0} [built]
   [0] multi react react-dom 40 bytes {1} [built]
[bFDD] ./client/styles/style.styl 1.14 kB {0} [built]
[hCih] ./client/reducers/completeUserLogin.js 1.17 kB {0} [built]
[mHWO] ./client/apolloClient.js 4.47 kB {0} [built]
[zU4m] ./client/actions/actionCreators.js 2.51 kB {0} [built]
    + 783 hidden modules
Child __offline_serviceworker:
     1 asset
       2 modules
Child html-webpack-plugin for "index.html":
     1 asset
    [3IRH] (webpack)/buildin/module.js 517 bytes {0} [built]
    [9yyn] ./node_modules/html-webpack-plugin/lib/loader.js!./index_template.ejs 1.26 kB {0} [built]
    [DuR2] (webpack)/buildin/global.js 509 bytes {0} [built]
        + 1 hidden module

It cannot install. Some of your URLs you're trying to cache return not wrong response, not 200ish one. Check the network tab.

@NekR Many thanks. That resolved the issue.


Implement lowercase usage of today,tomorrow, and yesterday within autocomplete

Stemmed from this issue.
Have implemented it so it still defaults to uppercase suggestions, but filling out with lowercase then allows for switching into this mode as well as subsequently displaying lowercase aliases.

@argenos you around?


How do I remove hover background on Menu Items?

[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

How can I remove the background colour on the hover of a menu item, and change the font-color?

Please submit support requests and questions to StackOverflow using the tag material-ui. StackOverflow is better suited for this kind of support. The issue tracker is for bug reports and feature discussions. See also our CONTRIBUTING guidelines.

Even though I support the fact that we shouldn't open an issue in which we ask how to do something, I have to say that the documentation is poor for people who are new to web development. Even though basic usage is covered, when it comes to customizing something, the documentation doesn't help.
material-ui has 30k stars on GitHub, so I expect to find a pretty solid documentation.

@bradeac What version are you using?

I am just playing around with the beta (1.0.0-beta.21). This shouldn't matter because the documentation is quite similar for the stable version.

@bradeac That isn't at all true, the v1-beta documentation is far more comprehensive, and if you're trying out v1 while following the v0.x docs, you're asking for trouble.

when it comes to customizing something, the documentation doesn't help

Your specific question "how do I customize a component?" is explicitly covered: https://material-ui-next.com/customization/overrides/

material-ui has 30k stars on GitHub, so I expect to find a pretty solid documentation

When it comes to open source, you get what you pay for. If you feel that something is lacking, pull up your sleeves and improve it.

Related link for anyone landing on this topic
https://stackoverflow.com/questions/43839297/material-ui-hovercolor-for-menuitem-component

A simple fix, not the best way, but it works
<MenuItem
    onMouseEnter={ (e) => e.target.style.backgroundColor= 'transparent' }
    onMouseLeave={ (e) => e.target.style.backgroundColor= 'transparent' }
>

The above solution can be made more concise by simply using

The easiest way is to set up a class object with:
menuItem: {
  ...,
  '&:hover': {
     backgroundColor: 'transparent'
  },
}

Then, this class should be applied to MenuItem component.
https://codesandbox.io/s/1qqkp3qoq3

@bradeac That isn't at all true, the v1-beta documentation is far more comprehensive, and if you're trying out v1 while following the v0.x docs, you're asking for trouble.
Your specific question "how do I customize a component?" is explicitly covered: https://material-ui-next.com/customization/overrides/
When it comes to open source, you get what you pay for.  Very poor for a member of Material-UI to behave this way

@mtb24 Did you found a solution to your problem?
People can have good and bad days, I think that the core of Matt's point is that there is an important gap between the value created by OSS projects and the value these projects capture. It's an economic reality. We have to account for it to take better decisions.

If you're using MUI 5 you can do this:
<MenuItem sx={[{'&:hover': {backgroundColor: 'transparent'}}]}>{children}</MenuItem>


Lack of pagination for getDocuments

At this moment, we can get document from data contract using limit and startAt/startAfter
But startAt and startAfter only get Identifiers, which makes it impossible to paginate documents adequately
Also we dont have totalCount for documents
Expected Behavior
startAt and startAfter must get integers, because otherwise we need to create many requests for any page
Exmaple with limit 50 and page 10:

Create first and last request with limit 50 and startAfter  equal 50*9

Current Behavior
As example we have limit 50, page 10, and the alghoritm to get it is:

Create first request with limit 100 and empty startAfter
Create second request with limit 100 and startAfter equal  last identifier of document from previous request
Create second request with limit 100 and startAfter equal  last identifier of document from previous request
Create second request with limit 100 and startAfter equal  last identifier of document from previous request
Create second request with limit 50 and startAfter equal  last identifier of document from previous request

Possible Solution
Replacing type for startAt and startAfter from identifier to integer on sever side and in clients and adding totalCount

totalCount sadly is not a capability of the current system, as it's impossible to prove the total amount without a node count. Such a feature would be possible by making a automatic count feature in grovedb, however it just hasn't been done yet.
The system is not designed to paginate integers either. This is because the underlying data might change, and you might miss values.


Add support for vectors

Summary
This PR adds support for vector and tries to export a group if its children are all Vectors. A vector in Bricks nodes corresponds to Ellipse and Vector nodes in Figma. A vector group node in Bricks is a group that consists of only group, frame, vector, ellipse and rectangle nodes in Figma.

How did you test this change?
Try exporting vector nods using Bricks plugin and see if generated code and rendered component include vectors nodes in the form of svg assets.

https://github.com/bricks-cloud/bricks/issues/13


Add synk scanning

Add snyk vulnerability scanning.

Coverage remained the same at 37.003% when pulling a730885dfed30fc8b45abaf5a2684677fb945d96 on feature/snyk-scanning into 021ac71dd37187955a1f0f6583ac622987d519d5 on main.


Configure HTTP client timeouts

We should not wait long for an i/o timeout during sync when a mesos slave is down, etc.

The easiest solution is to wrap consul functions calls with time out wrapper. Unfortunately consul lib doesn't support retrying and timing out.


Larastan infers that deleted_at is a string and not a Carbon.

Larastan Version: 8.6.7

--level used: max
Pull request with failing test: https://github.com/MatanYadaev/larastan/pull/2

Description
Larastan infers that deleted_at is a string and not a Carbon.
Laravel code where the issue was found
class User extends Authenticatable
{
  use SoftDeletes;

   // ...
}

// Cannot call method addDay() on string|null.
User::onlyTrashed()->firstOrFail()->deleted_at->addDay();

BTW, when you add $casts = ['deleted_at' => 'datetime']; the issue is gone - but I believe it's not an ideal solution.

Pull request with failing test:

Thank you for your report.
You do not need to open a PR for your issues.

Do you suggest that onlyTrashed() prevents deleted_at from being null?

@szepeviktor

You do not need to open PR-s for your issues.
Sorry, what do you mean?
Do you suggest that onlyTrashed() prevents deleted_at from being null?
It is, but it's unrelated to the issue. The issue is that Larastan doesn't cast deleted_at to Carbon by default. And in my opinion, it should do it.

Laravel casts created_at and updated_at  to Carbon by default. It does the same thing to deleted_at (SoftDeletes::initializeSoftDeletes), but for some reason, Larastan doesn't understand it.

I don't have to create a PR with failing tests when I open an issue?

Oh yess!!

Maybe here it is
https://github.com/nunomaduro/larastan/blob/7d6e564144b2f9c231d0331d4083905a1b3e872b/src/Properties/SchemaAggregator.php#L372-L378


New filter to the cases endpoint

Link to JIRA ticket
JIRA ticket.
Describe this PR
What is the problem we're trying to solve
Minor tweak to the launch file to connect to the correct historical DB locally
Adding a new filter to the /cases endpoint to exclude audit trail events + provide total count in the API response ( additional request by Jaye )

person updated
person created
warning note added
warning note expired
worker allocated
worker deallocated

What changes have we introduced
Added functionality in CaseRecordsUseCase and relevant test file to support above.
Checklist

[ ] Added end-to-end (i.e. integration) tests where necessary e.g to test complete functionality of a newly added feature
[x] Added tests to cover all new production code
[ ] Added comments to the README or updated relevant documentation (add link to documentation), where necessary.
[x] Checked all code for possible refactoring
[x] Code pipeline builds correctly

Follow up actions after merging PR
n/a

other than the six i mentioned, did you see any mention in the code of other audit-trail-like events we might want to filter out?


Problem with NAT vps

My nat server only has a few ports available.
443 is not available.
How can I use letsencrypt (not reality) with port 1207?
It didn't work with the attached config.

Thanks much

You cannot use letsencrypt with natvps because port 80 must be free for it and this port is not available for natvps servers.

Yes but if I use IPv6 all ports are open. I've mapped ipv6 address of the server to a domain name in Cloudflare and successfully got a let's encrypt certificate.


Add formatted details and Stepf to Trace to avoid needless string concatenation

It's common pattern in k8s to create a trace like so:
trace := utiltrace.New("Get " + req.URL.Path)

Or
trace := utiltrace.New(fmt.Sprintf("GuaranteedUpdate etcd3: %s", getTypeName(out)))

Or
trace.Step(fmt.Sprintf("Writing http response done (%d items)", meta.LenList(result)))

Which results in string concatenation even if the trace is never logged.
This adds WithDetails and Stepf to allow for lazy string concatenation only when needed. E.g.:
trace := utiltrace.New("Get").WithDetails("URL=%s,accepts=%s", req.URL.Path, req.Header.Accepts)

Or
trace.Stepf("Writing http response done (%d items)", meta.LenList(result))

cc @liggitt @roycaihw @sttts

Added.
On Wed, Jul 24, 2019 at 10:34 AM Andrew Sy Kim<EMAIL_ADDRESS>wrote:

@andrewsykim commented on this pull request.
In trace/trace_test.go
https://github.com/kubernetes/utils/pull/105#discussion_r306933603:

	name: "Sample Trace",

	steps: []traceStep{

		{time.Now(), "msg1"},

		{time.Now(), "msg2"},

		{time.Now(), "msg3"},

{

	name: "Check formatting",

	expectedMessages: []string{

		"URL=/api,count=3", "msg1 arg1 2 false",

	},

	sampleTrace: &Trace{

		name:        "Sample Trace",

		details:     "URL=%s,count=%d",

		detailsArgs: []interface{}{"/api", 3},

		steps: []traceStep{

			{stepTime: time.Now(), msg: "msg1 %s %d %t", msgArgs: []interface{}{"arg1", 2, false}},

Probably worth adding a testcase with multiple trace steps to test new
line strings in the buffer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/utils/pull/105?email_source=notifications&email_token=AAD72RUDD6KBVYUBKNWBFZ3QBCHAVA5CNFSM4IGKZQSKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB7OYFTA#pullrequestreview-266175180,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD72RWL7VEILUKQQYGW7NDQBCHAVANCNFSM4IGKZQSA
.

How valuable is the formatting vs simpler key/value pairs? I.e. could you instead do something like:
trace := utiltrace.New("Get").With("URL", req.URL.Path).With("accepts", req.Header.Accepts)

And then carry a map[string]interface{} (or a list of pairs if ordering matters) until you need to concatenate it?
Similary:
trace.Stepf("Writing http response done", n_items, meta.LenList(result), "foo", bar)

This is similar in form to https://github.com/go-logr/logr/blob/master/logr.go#L111 and https://github.com/go-logr/logr/blob/master/logr.go#L143 which you can see implemented in https://github.com/go-logr/glogr/blob/master/glogr.go (particularly https://github.com/go-logr/glogr/blob/master/glogr.go#L140)
You lose some flexibility (oh, I wanted that number in hex) but gain a lot of simplicity. And we can probably add format-wrappers if we needed to, e.g. ...With("foo", trace.AsHex(intValue)).

I like this idea. We'll need to change how the existing trace calls in k8s are output in the logs to adapt them to this, but it does seem like the right approach. I'll try switching to this approach.

@liggitt @thockin I've switched to an optional list of key/value fields. I went with a varadic param for the fields, but it could easily be switched to a .With() builder style if that's preferable. Let me know what you think.

Friendly ping

I like the simplicity of the variadic... keeps order, avoids repeatedly appending to a slice. this looks reasonable to me.

/assign @wojtek-t @thockin

/approve

I like the simplicity of the variadic... keeps order, avoids repeatedly appending to a slice. this looks reasonable to me.

I like that too.
/lgtm


Knight Jousting

Description

Another simple "survive to the end" challenge. Everyone gets knight armor, shields, swords, and a segway. Try and survive for 10-15 seconds to get points.

This can be a special challenge for tiebreaking


Check if meteo data covers entire simulation period

and reindex datasets after reading (in case dates inbetween are missing etc.)

fixed in 48cc25fad2fb2007979fe9f580eadb98270ec6d6, 1ce24210f81635628e7b798f383a4c8e31791509


Fix scripts loading

Hubot loads all modules in src/, which includes stackstorm_api.js.
This means that the StackStorm class gets initialized without a new keyword, which means that its this variable is undefined, so this line:
  self.robot = robot;

causes an error later on TypeError: Cannot read property 'robot' of undefined.
Moving the stackstorm_api.js module into src/lib/ avoids this situation.
The stackstorm.js module properly initializes the StackStorm class with the new keyword, so it stays.
Imports are updated to reflect the moved module.

Yep, I'll add a few lines to the changelog when I make a release.

Changelog should come with a change you're doing to be tightly coupled with PR.


Remove Smapshot when Smapshot doesn't exist

Need to determine a reliable way to determine if Smapshot doesn't exist.
—
Created via Raycast

@martimpassos Can you remind me how we know when Smapshot shouldn't be displayed?

If the item isn't in the Smapshot item set, it isn't in Smapshot


Rework title pages to use mdx for doc cards

^ I'd say the same with the Miscellaneous landing page.

Velocity does this already within the Admin/Dev. Added Misc and also realised i named the branch velocity instead of waterfall 🤦


fix custom metadata edit action

Fixes #5772
Changes proposed in this pull request:

edit setAnyField() method in ProjectMetadata class
add case to edit customMetadata field
parse given String to JSON and JSON to HashMap

You can use mvn formatter:format to resolve the linting issue.

Looks great! Thanks for the prompt turnaround on the review feedback.


Running the listener on a separate host

Hi,
I'm doing my pentesting via a locally installed Pi that offers an OpenVPN connection for me. The Pi is in the LAN of the client and I use that in combination with a Kali install that connects via VPN.
I don't think I can compile the shellcode on the Pi, so I ded that on Kali. I cannot start the listener on Kali however,, because it has no IP on the client's LAN. It has a TUN interface in another range.
Can the code be changed so I can use a listener on another host?
Cheers,
BC

Hey,
I compiled on a x64 host and copied everything over to the Pi and I was able to run both Python scripts.
I do get this though:  good response status: INVALID_PARAMETER
Is that something that can be helped?
Chers,
BC

Hey, this isn't really relevant to this repository. This question is about exploitation guidance and setup and not about any bug in the code itself.
To answer your question however: It should be as simple as specifying your listening hosts IP when you generate the payloads. Then on your listening host, start up metasploit and launch the multi handlers manually. I do this all the time if I need to egress out of an environment for any reason. If it is not working I would advise it's likely a networking issue or an issue on your listening host. That is all I can do to advise however, good luck!


Add tests

We need to add some tests running automatically and set up Travis CI (and Appveyor?). These tests should also check the the integration with Trixi.jl.

Travis is enabled and will run tests once we add them.

Fixed by 35c9316.


Unify C++ source and header file extensions

Overview
Currently, we have different file extensions for the C++ source and header files in the Zephyr repository:
Source Files

cpp
cxx
cc

Header Files

h
hh

For the sake of consistency, the project should decide on and use only single extension each for the C++ source and header files.
Context
Widely-used conventions
C++ source Files: .cpp, .cxx, .cc, C
C++ header Files: .hpp, .hxx, .hh, h
From the perspective of the Standard C++ Foundation

What source-file-name convention is best? foo.cpp? foo.C? foo.cc?
What header-file-name convention is best? foo.H? foo.hh? foo.hpp?

Opinions
Amongst the "widely-used conventions" listed above, some to avoid are:

C (capital C) for source files

This will not play well with the operating systems that do not strictly enforce the case sensitiveness of the file names (e.g. Windows, macOS).
This is more prone to human errors than having alphabetically different names for the C++ source files and the C source files.

h for C++ header files

This provides no distinction between the C++ header files and the C header files.

Proposed Change
TBD (to be discussed and finalised in the relevant meetings)

Please feel free to update this issue with more contexts and opinions.

cc @tejlmand @yperess @carlescufi @nashif @MaureenHelm @alexanderwachter

I would suggest the .hpp/.cpp standard adopted by the Boost libraries. Gcc and Clang will automatically recognize all alternatives, but at least the Arm Keil compiler requires an additional command line switch to recognize the source file as C++ code unless the filename extension is .cpp (see https://www.keil.com/support/man/docs/armcc/armcc_chr1359124195123.htm). I don't know if IAR has similar quirks (or if Zephyr supports/wants to support these toolchains) but I think that .hpp/.cpp are the most widely adopted C++ filename extensions.

.cpp / .hpp is fine with me, although the fact is, 3rd party code will likely be named .cpp / .h and we will need to deal with that as well (CMake handles this just fine).

I also prefer .hpp/.cpp.
By the way, the scope of this is the files that are being committed to the main Zephyr repository (i.e. zephyrproject-rtos/zephyr) only. Third-party code in the modules can keep whatever convention their upstream repo uses.

+1 for .cpp .hpp

Another vote for .hpp/.cpp for files in the main zephyr tree, as mentioned by @stephanosio.

In my experience .hpp/.cpp are most widely used. Let's use these.

I also vote for .hpp / .cpp.
Make sure that you also add a compliance check that fails all the others so we don't forget we made this decision.