Test

TEST

Hi everyone. I've tried msieve and now I've switched to YAFU
Could you please help me in factoring my AES key.
Software has encountered the following unknown AES keys, please crack them first
using msieve:
06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDA
EC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464 found in ./test.pdf.vvv
Alternatively, you can crack the following Bitcoin key(s) using msieve, and use
them with TeslaDecoder:
5113CE9C3BA756B3DE318ECFCC12AB4E92D9E75C51B87E81C77FE6EC55A91628D31FAB3CA084F09F
BE22EB883A02CF315F1C47D869609D4CA13FBF6FD5913CBC found in ./test.pdf.vvv
yafu-x64.exe "factor(0x06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDAEC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464)" -v -threads 4
Three days have passed, but it does not end
Now it is this state.Should I wait while this?
hashtable: 8192 entries,  0.13 MB
polynomial selection complete
R0: -1801997811703616160196891941
R1:<PHONE_NUMBER>276989
A0: -145733234201978104535932630017781952
A1: -689510289864004435983916894676
A2: -158687415267296846122045
A3:<PHONE_NUMBER>72737838
A4: -1958288388
A5: 2664
skew 3066414.88, size 1.560e-013, alpha -7.659, combined = 2.143e-011 rroots = 3
elapsed time of 52867.3162 seconds exceeds 55905 second deadline; poly select done
searching for best poly...
new best score = 1.741000e-011, new best line = 1
new best score = 1.753000e-011, new best line = 9
new best score = 1.758000e-011, new best line = 21
new best score = 1.818000e-011, new best line = 26
new best score = 1.947000e-011, new best line = 48
new best score = 2.176000e-011, new best line = 350
new best score = 2.233000e-011, new best line = 3043
best poly:
norm 2.039457e-013 alpha -7.495928 e 2.233e-011 rroots 3
n:<PHONE_NUMBER>0596608030707088333276465126197614406175085085625182559887044647138650559329121064894995623651439137186413181470132750593184470061
skew: 1831681.21
c0: -24846631245053543211599969579204061
c1: -137064065632221367854619274170
c2: -45148820894553103069635
c3:<PHONE_NUMBER>59024270
c4: -1187126164
c5: 1560
Y0: -2005562304908831121013419070
Y1:<PHONE_NUMBER>94719
nfs: commencing algebraic side lattice sieving over range: 7060000 - 7080000
nfs: commencing algebraic side lattice sieving over range: 7000000 - 7020000
nfs: commencing algebraic side lattice sieving over range: 7040000 - 7060000
nfs: commencing algebraic side lattice sieving over range: 7020000 - 7040000
Warning:  lowering FB_bound to 6999999.
Warning:  lowering FB_bound to 7059999.
Warning:  lowering FB_bound to 7019999.
Warning:  lowering FB_bound to 7039999.
FBsize 476504+0 (deg 5), 910076+0 (deg 1)
FBsize 480307+0 (deg 5), 910076+0 (deg 1)
FBsize 477754+0 (deg 5), 910076+0 (deg 1)
FBsize 479016+0 (deg 5), 910076+0 (deg 1)
total yield: 56191, q=7054897 (0.04841 sec/rel)

Hi everyone. I've tried msieve and now I've switched to YAFU
Could you please help me in factoring my AES key.
Software has encountered the following unknown AES keys, please crack them first
using msieve:
06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDA
EC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464 found in ./1.pdf.vvv
Alternatively, you can crack the following Bitcoin key(s) using msieve, and use
them with TeslaDecoder:
5113CE9C3BA756B3DE318ECFCC12AB4E92D9E75C51B87E81C77FE6EC55A91628D31FAB3CA084F09F
BE22EB883A02CF315F1C47D869609D4CA13FBF6FD5913CBC found in ./1.pdf.vvv
yafu-x64.exe "factor(0x06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDAEC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464)" -v -threads 4

Three days have passed, but it does not end
Now it is this state.Should I wait while this?

hashtable: 8192 entries,  0.13 MB
polynomial selection complete
R0: -1801997811703616160196891941
R1:<PHONE_NUMBER>276989
A0: -145733234201978104535932630017781952
A1: -689510289864004435983916894676
A2: -158687415267296846122045
A3:<PHONE_NUMBER>72737838
A4: -1958288388
A5: 2664
skew 3066414.88, size 1.560e-013, alpha -7.659, combined = 2.143e-011 rroots = 3
elapsed time of 52867.3162 seconds exceeds 55905 second deadline; poly select done
searching for best poly...
new best score = 1.741000e-011, new best line = 1
new best score = 1.753000e-011, new best line = 9
new best score = 1.758000e-011, new best line = 21
new best score = 1.818000e-011, new best line = 26
new best score = 1.947000e-011, new best line = 48
new best score = 2.176000e-011, new best line = 350
new best score = 2.233000e-011, new best line = 3043
best poly:
norm 2.039457e-013 alpha -7.495928 e 2.233e-011 rroots 3
n:<PHONE_NUMBER>0596608030707088333276465126197614406175085085625182559887044647138650559329121064894995623651439137186413181470132750593184470061
skew: 1831681.21
c0: -24846631245053543211599969579204061
c1: -137064065632221367854619274170
c2: -45148820894553103069635
c3:<PHONE_NUMBER>59024270
c4: -1187126164
c5: 1560
Y0: -2005562304908831121013419070
Y1:<PHONE_NUMBER>94719
nfs: commencing algebraic side lattice sieving over range: 7060000 - 7080000
nfs: commencing algebraic side lattice sieving over range: 7000000 - 7020000
nfs: commencing algebraic side lattice sieving over range: 7040000 - 7060000
nfs: commencing algebraic side lattice sieving over range: 7020000 - 7040000
Warning:  lowering FB_bound to 6999999.
Warning:  lowering FB_bound to 7059999.
Warning:  lowering FB_bound to 7019999.
Warning:  lowering FB_bound to 7039999.
FBsize 476504+0 (deg 5), 910076+0 (deg 1)
FBsize 480307+0 (deg 5), 910076+0 (deg 1)
FBsize 477754+0 (deg 5), 910076+0 (deg 1)
FBsize 479016+0 (deg 5), 910076+0 (deg 1)
total yield: 56191, q=7054897 (0.04841 sec/rel)

Hi everyone. I've tried msieve and now I've switched to YAFU
Could you please help me in factoring my AES key.
Software has encountered the following unknown AES keys, please crack them first
 using msieve:
06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDA
EC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464 found in ./1.pdf.vvv
Alternatively, you can crack the following Bitcoin key(s) using msieve, and use
them with TeslaDecoder:
5113CE9C3BA756B3DE318ECFCC12AB4E92D9E75C51B87E81C77FE6EC55A91628D31FAB3CA084F09F
BE22EB883A02CF315F1C47D869609D4CA13FBF6FD5913CBC found in ./1.pdf.vvv

yafu-x64.exe "factor(0x06271483167E7697F03407AF08C1E10185D388830DA4A20EF4B00C24A0EA6A01E23BCB7274141BDAEC381D75768E3722276BFF1BE1F3F77C59FA6ABB2B142464)" -v -threads 4
Three days have passed, but it does not end
Now it is this state.Should I wait while this?
hashtable: 8192 entries,  0.13 MB
polynomial selection complete
R0: -1801997811703616160196891941
R1:<PHONE_NUMBER>276989
A0: -145733234201978104535932630017781952
A1: -689510289864004435983916894676
A2: -158687415267296846122045
A3:<PHONE_NUMBER>72737838
A4: -1958288388
A5: 2664
skew 3066414.88, size 1.560e-013, alpha -7.659, combined = 2.143e-011 rroots = 3
elapsed time of 52867.3162 seconds exceeds 55905 second deadline; poly select done
searching for best poly...
new best score = 1.741000e-011, new best line = 1
new best score = 1.753000e-011, new best line = 9
new best score = 1.758000e-011, new best line = 21
new best score = 1.818000e-011, new best line = 26
new best score = 1.947000e-011, new best line = 48
new best score = 2.176000e-011, new best line = 350
new best score = 2.233000e-011, new best line = 3043
best poly:
 norm 2.039457e-013 alpha -7.495928 e 2.233e-011 rroots 3
n:<PHONE_NUMBER>0596608030707088333276465126197614406175085085625182559887044647138650559329121064894995623651439137186413181470132750593184470061
skew: 1831681.21
c0: -24846631245053543211599969579204061
c1: -137064065632221367854619274170
c2: -45148820894553103069635
c3:<PHONE_NUMBER>59024270
c4: -1187126164
c5: 1560
Y0: -2005562304908831121013419070
Y1:<PHONE_NUMBER>94719
nfs: commencing algebraic side lattice sieving over range: 7060000 - 7080000
nfs: commencing algebraic side lattice sieving over range: 7000000 - 7020000
nfs: commencing algebraic side lattice sieving over range: 7040000 - 7060000
nfs: commencing algebraic side lattice sieving over range: 7020000 - 7040000
 Warning:  lowering FB_bound to 6999999.
 Warning:  lowering FB_bound to 7059999.
 Warning:  lowering FB_bound to 7019999.
 Warning:  lowering FB_bound to 7039999.
FBsize 476504+0 (deg 5), 910076+0 (deg 1)
FBsize 480307+0 (deg 5), 910076+0 (deg 1)
FBsize 477754+0 (deg 5), 910076+0 (deg 1)
FBsize 479016+0 (deg 5), 910076+0 (deg 1)
total yield: 56191, q=7054897 (0.04841 sec/rel)


[feat] Switch to winston logger

Please specify a timestamp that includes milliseconds, as this is used to debug packet round-trip times.


Map attribution is on top

On my Iphone 13 the map attribution is in the top right it should be at the bottom left.

the issue with this are phone screens with rounded corners and software home/back/activities buttons or the iphone bar at the bottom. we can't really put it on the very bottom without overriding safe area margins and risking it being cut off, so it would have to float akwardly pretty far above the bottom screen border like this:

i think on the top it's way less intrusive

Yeah agreed, I think it better when it is at the top. Close the issue if you like to.


use JFrog Artifactory Cloud for deploy and publish

I moved all other 3DCityDB artifacts to citydb.jfrog.io as well. There is a similar jfrog-artifactory-cloud branch in all corresponding GitHub repos. And the Oracle libraries are now also loaded dynamically from the Maven repository and not stored as static files in the repo anymore.


Tweak dev backporting docs

Tweak docs as I do this process

Codecov Report

Merging #466 (189f0a1) into master (1f1c637) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #466      +/-   ##
==========================================
- Coverage   82.65%   82.65%   -0.01%
==========================================
  Files         165      165
  Lines       45563    45563
==========================================
- Hits        37662    37661       -1
- Misses       7901     7902       +1

Impacted Files
Coverage Δ

parquet/src/encodings/encoding.rs
94.85% <0.00%> (-0.20%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1f1c637...189f0a1. Read the comment docs.

Clippy errors were fixed in https://github.com/apache/arrow-rs/pull/470


Files in time_sets that are shorter than the specified time-slot

e.g. filtered_209671000_20241127_1733-20241127_1737

Repaired


More programming languages

Now that we have both http://code.world and http://code.world/haskell, there's a good question about the possibility of more languages.  A particularly easy one to build would be http://code.world/javascript.
There's definitely some appeal in the idea that students could progress from our home-grown language to either full Haskell or JavaScript while having the same general structure of APIs available to them.
I'd also be interested in other beginner-friendly languages, like Python or Lua.

This is not the direction CodeWorld is going.  Closing.


Implement  Outscale cluster infrastructure controller unit test with github action

Is your feature request related to a problem? Please describe.
Implement Outscale cluster infrastructure controller unit test with github action
Describe the solution you'd like in detail
Create unit test with github action

Replace by other issue format


Cache outbound message on events.

And hopefully avoid many Riak lookups.

We need a vumi release and dep version bump for this.

Ready for review.

:+1: from me but it's probably wise to have someone else review as well ;)

Various routing tests now fail. See Travis builds.

They're all failed asserts from the cache now being used in a few places. Fixing.

Ready for re-review once Travis build is done.

:+1: when Travis is happy.


Failed installing alpha version

@devmsh I'm guessing that you have something that conflicts with the Laravel installer.
Can you try requiring the installer first?
composer global require laravel/installer v3.0.1

I expect this to show errors, but those errors will be helpful for us.

It's installed successfully, and I tried to reinstall lambo again and it just works fine.

@devmsh can you close this then?


[SPARK-38271] PoissonSampler may generate more rows than MaxRows

What changes were proposed in this pull request?
when replacement=true, Sample.maxRows returns None
Why are the changes needed?
the underlying impl of SampleExec can not guarantee that its number of output rows <= Sample.maxRows
scala> val df = spark.range(0, 1000)
df: org.apache.spark.sql.Dataset[Long] = [id: bigint]

scala> df.count
res0: Long = 1000

scala> df.sample(true, 0.999999, 10).count
res1: Long = 1004

Does this PR introduce any user-facing change?
No
How was this patch tested?
existing testsuites

cc @cloud-fan

can we add a UT for it in CombiningLimitsSuite?

@cloud-fan Sure, will add a ut today

thanks, merging to master/3.2!


Calc could benefit from named definitions on the command line

Something like:
c -D a:true -D b:123
Not sure if we should go as far as defining functions, but simple variable declarations (with possible value) would be handy for options (for instance)
c -D verbose:true
Should also work in CALC_OPTIONS.
Not sure that it makes any sense to have the value optional -- there is no real point to having this, since a "defined" variable with no value is no different than an "undefined" variable -- the value is always going to be null.
Not sure if ":" or "=" (or both) is better -- I think there may be command-line parsing "things" on some O/Ses.

Because of other aliases already used, the syntax is:
-variable name=value
or
-var name:value
or
-define name=value


Improve partitions mapping so document query is sent to target partitions only

This will help avoid unnecessary query round trips to inapplicable partitions (Fix #5)
cc: @dennyglee @shireeshkthota

@khdang,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

I will resend this from a branch that is not master


[ignition-msgs1] cmake dev warning in portfile

From one of my CI runs:
Building package ignition-msgs1[core]:x64-windows-static...
Could not locate cached archive: W:\08\087749218c4e972449965998fdab076641a6aa50.zip
-- Downloading https://github.com/ignitionrobotics/ign-msgs/archive/ignition-msgs_1.0.0.tar.gz...
-- Extracting source D:/downloads/ignitionrobotics-ign-msgs-ignition-msgs_1.0.0.tar.gz
-- Applying patch fix-protobuf-static-link-order.patch
-- Using source at D:/buildtrees/ignition-msgs1/src/msgs_1.0.0-83c03d2b65.clean
-- Configuring x64-windows-static-dbg
-- Configuring x64-windows-static-rel
-- Building x64-windows-static-dbg
-- Building x64-windows-static-rel
-- Using msys root at D:/downloads/tools/msys2/c809757c94447846
-- Fixing pkgconfig file: D:/packages/ignition-msgs1_x64-windows-static/lib/pkgconfig/ignition-msgs1.pc
-- Fixing pkgconfig file: D:/packages/ignition-msgs1_x64-windows-static/debug/lib/pkgconfig/ignition-msgs1.pc
-- Installing: D:/packages/ignition-msgs1_x64-windows-static/share/ignition-msgs1/copyright
CMake Warning (dev) at ports/ignition-msgs1/portfile.cmake:33 (set):
  Only the first value argument is used when setting an environment variable.
  Argument 'C:\Program Files (x86)\Microsoft Visual
  Studio\2019\Enterprise\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64' and later
  are unused.
Call Stack (most recent call first):
  scripts/ports.cmake:136 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Performing post-build validation
-- Performing post-build validation done

@traversaro: Please fix
https://github.com/microsoft/vcpkg/blob/783763162901f32e6d6270aede22519844b8e9ce/ports/ignition-msgs1/portfile.cmake#L33
should be set(ENV{PATH} "${path_backup}")

This will be fixed by https://github.com/microsoft/vcpkg/pull/14464 .


Doesn't work with ACF 4.x

Plugin enqueues input.js that doesn't exist. No input field appears in admin.

Hello,
Support for ACF4 added and tested. Have fun!


Publish API docs for Firebase service

Tracking issue so we don't forget. We want to help our developers explore the Firebase service.

https://www.dartdocs.org/documentation/firebase/latest/firebase/firebase-library.html

I added a link to docs in README of https://github.com/flutter/firechat-flutter.

Thanks for checking into it, but we might want to update the README for that package. There's no hint that it can be used with Flutter, nor if there are any special gotchas for Flutter+Firebase.  https://www.dartdocs.org/documentation/firebase/0.6.5+1/index.html

I think the next steps are:
[ ] Conditional imports need to be supported in Dart. https://github.com/dart-lang/sdk/issues/24581
[ ] We merge our changes into https://github.com/firebase/firebase-dart. https://github.com/firebase/firebase-dart/issues/71
[ ] Ensure that the Firebase dartdoc describes Flutter usage
[ ] Update the dart Firebase package
Alternatively, we could publish a separate Dart package now for Flutter-enabled Firebase, but that might cause more confusion down the road when we merge into one repo.

We can assume that "Conditional imports need to be supported in Dart." will be a long time coming. How does that change our approach to documenting our Firebase service?

Firebase API docs are at https://github.com/flutter/firebase-dart

For now:

flutter/firebase-dart should link to the firebase/firebase-dart's dartdoc, since the APIs are the same.
Caveats and usage should be noted in the flutter/firebase-dart README.

If we get tired of waiting for conditional imports, we can update firebase-dart to a new major version that doesn't rely on conditional imports but instead has developers import a platform-specific class (FirebaseJs, FirebaseFlutter) when they want to construct a Firebase from a URL.

@sethladd FWIW, we expect to land support for conditional imports in Dart within days -- not weeks. @floitschG is working on it :)

@sethladd
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1030. Any further collaboration will be done there.


YGNodeClone memory leak

Report

[x] I have searched existing issues and this is not a duplicate

Issues and Steps to Reproduce
YGNodeClone have memory leaks. Use Xcode->Instruments->Leaks can find it.

Expected Behavior
Do not have memory leak.
Actual Behavior
Do have memory leak.
Link to Code
N/A

Yoga calls YGNodeClone if the layout pass encounters a Yoga node which it needs to mutate, whose owner is different from the parent node we are laying out. It allows different Yoga trees to share nodes, and copy on write.
It is the callers responsibility to free the cloned node. E.g. with YGNodeFreeRecursive, or Yoga allows setting a callback for when a Node is cloned so that the host platform can handle this.
In this screenshot, it looks like this is happening in React Native's Paper renderer on iOS (guessing with nested views under text?). This is the code which is behaving incorrectly.
Please create an issue with a repro on the React Native repo for this. Because the React Native team is focused on shipping Fabric, we may not end up investigating Paper-specific changes, but PRs are always welcome.


Rename ScheduledJobs to CronJobs

This builds on top of #1506, since the other wasn't merged yet and it also includes some changes that needs to be reflected here.
@kubernetes/docs ptal

This change is

This one will also fix travis, due to the ScheduledJob->CronJob rename thing, so it can replace the other PR as well.

This one will also fix travis, due to the ScheduledJob->CronJob rename thing, so it can replace the other PR as well.

Came here for that, cool

LGTM, but needs docs review from @kubernetes/docs, specifically:

Does the new navigation look good -- (1) Guides > Batch Jobs > Cron Jobs and (2) Reference > Glossary > Cron Jobs
If you click on (2), you'll be brought to (1). Is that acceptable?

Rebased @kubernetes/docs ptal

Can you fix the merge conflict?

Rebased, will merge on green.


Item Collection Accessibility Issues

Bug Report
Description
The terra-clinical-item-display ItemComment text color does not have enough contrast with the terra-list selected background color, the terra-table selected background color, or the terra-table striped background color.
Steps to Reproduce

Visit the selectable test page
Test color contrast using Axe in table mode (larger viewport)
Test color contrast using Axe in list mode (smaller viewport)
Visit the table styles test page
Test color contrast using Axe in table mode (larger viewport)

Additional Context / Screenshots
Selectable

expected no accessibility violations but got:
	{
  "description": "Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds",
  "help": "Elements must have sufficient color contrast",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.0/color-contrast?application=axeAPI",
  "id": "color-contrast",
  "impact": "serious",
  "nodes": [
    {
      "all": [],
      "any": [
        {
          "data": {
            "bgColor": "#e2f2fc",
            "contrastRatio": 3.94,
            "expectedContrastRatio": "4.5:1",
            "fgColor": "#75767d",
            "fontSize": "10.5pt",
            "fontWeight": "normal"
          },
          "id": "color-contrast",
          "impact": "serious",
          "message": "Element has insufficient color contrast of 3.94 (foreground color: #75767d, background color: #e2f2fc, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1",
          "relatedNodes": [
            {
              "html": "
",
              "target": [
                "#item3"
              ]
            }
          ]
        }
      ],
      "failureSummary": "Fix any of the following:\n  Element has insufficient color contrast of 3.94 (foreground color: #75767d, background color: #e2f2fc, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1",
      "html": "
test comment
",
      "impact": "serious",
      "none": [],
      "target": [
        "#item3 > .ItemView__item-view___2qBlH.ItemView__one-column___346PH > .ItemView__body___1Uda5 > .ItemComment__item-comment___IfOdl.ItemDisplay__item-display___3gBY_ > .ItemDisplay__text___2ZB9-"
      ]
    }
  ],
  "tags": [
    "cat.color",
    "wcag2aa",
    "wcag143"
  ]
}

Striped

expected no accessibility violations but got:
	{
  "description": "Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds",
  "help": "Elements must have sufficient color contrast",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.0/color-contrast?application=axeAPI",
  "id": "color-contrast",
  "impact": "serious",
  "nodes": [
    {
      "all": [],
      "any": [
        {
          "data": {
            "bgColor": "#f4f4f4",
            "contrastRatio": 4.11,
            "expectedContrastRatio": "4.5:1",
            "fgColor": "#75767d",
            "fontSize": "10.5pt",
            "fontWeight": "normal"
          },
          "id": "color-contrast",
          "impact": "serious",
          "message": "Element has insufficient color contrast of 4.11 (foreground color: #75767d, background color: #f4f4f4, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1",
          "relatedNodes": [
            {
              "html": "
",
              "target": [
                ".Table-module__striped___1iYyS > tbody > tr:nth-child(2)"
              ]
            }
          ]
        }
      ],
      "failureSummary": "Fix any of the following:\n  Element has insufficient color contrast of 4.11 (foreground color: #75767d, background color: #f4f4f4, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1",
      "html": "
test comment
",
      "impact": "serious",
      "none": [],
      "target": [
        ".Table-module__striped___1iYyS > tbody > tr:nth-child(2) > .ItemCollection__content-comment___1-Riz > .ItemComment__item-comment___IfOdl.ItemDisplay__item-display___3gBY_ > .ItemDisplay__text___2ZB9-"
      ]
    }
  ],
  "tags": [
    "cat.color",
    "wcag2aa",
    "wcag143"
  ]
}

Expected Behavior
No accessibility errors will be encountered
Possible Solution
Change one of the colors

@neilpfeiffer can we get some guidance on colors to get this to meet recommended WCAG 2 AA contrast ratios.

@neilpfeiffer could you please provide the foreground color suggestion for the clinical item display ? current color hexa value of foreground color for clinical  item display is #75767d.

Thanks @ShettyAkarsh - Both the icon and color we use for the “secondary” text treatment should be changed to an rgba so the opacity allows for the change in the  background color to “add” to the light grey color and darken to pass when visually sampled. I will look up what the color is that was chosen to replace hex 75767d.

@ShettyAkarsh -- new color will be rgba(28, 31, 33, 0.65)
for the text color for "secondary" textStyle in terra-clinical-item-display
plus the text color for the ItemDisplay.Comment.
The icon color for ItemDisplay.Comment can stay at rgba(117, 118, 125, 0.30).


Parse FIR into annotation mirror types

This separates the FIR parsing from the interpretation of the semantics.
Refs #19

If I was smarter, I would have migrated the existing parser away from reflection into an abstraction similar to the data classes added in this PR. Then the migration would be "just" adding a FIR-to-data-class step with the semantic parsing still remaining the same.
I guess there's still time... maybe tomorrow.


[backport] Fix subview of zero-sized arrays

Backport of #7037

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 371687acd649c10d0f7d64b1bb3222eb2376347b, target branch v6) failed with status FAILURE.

Failure seem unrelated. LGTM!


Print the panzoom

Hi, there is a way to print the panzoom element? the thing is i have an ng-repeat inside the panzoom, then when I try to print, everithing became a mess, the div doesn't contain correctly the inside images
thanks

Hello @cperezvinsite,
No, I haven't really considered the issue of printing, and I believe it is largely orthogonal to the needs which the pan zoom directive aims to solve. In other words, I don't foresee that special support for printing will become part of angular-pan-zoom.
More broadly speaking, my personal experience with printing web content of any kind over the years has been largely disappointing. Usually the elements end up more or less in a mess and page breaks tend to occur in the most inconvenient of places.
There are libraries out there which promise to be able to print selected HTML elements, e.g. https://www.npmjs.com/package/print-html-element. I haven't tested any of this so I don't know if they play well with angular-pan-zoom.
Sorry that I can't be of more help, but I'll close this as an issue.


feat: add support for breakMw

move _respond from application to response.
add support for break middleware chain.

@dead-horse

@killagu whats a good use case for this?

@maticrivo  proxy middleware will transfer the request in some case.
the response should immediately end,and other middlewares should not continue.


No reduction in graphics memory

1、GPU：A100-80G，
test-code：

2、result

3、conclusion and problem
（1）tomesd：token_ merge_ The higher the ratio, the faster the inference speed, 8.71s ->5.92s (ratio: 0->ratio: 0.5)，however，there has been no significant change in the graphics memory, which is not consistent with the paper. I would like to understand the possible reasons？？？
（2）The inference speed of xforms+tomesd [token merge ratio>0.3] is better than using xforms alone。

All the benchmarks in the paper were done using the original stable diffusion repo, not diffusers (and diffusers may give different results). Also, it's hard to get an accurate memory usage reading with pytorch. The way I estimated it in the stable diffusion repo was I used 512x512 images and then increased the batch size until I ran out of memory. Then the memory per image was the total memory allocated divided by the maximum batch size before running out of memory.
If you don't do it like that, the problem is that pytorch will very often allocate more memory than it needs, and it's hard to find out how much memory the network is actually using.


Add support for multiple senders and proxy

Hi !
Feel free to re-open this pull-request to code-lts/Laravel-FCM
This is a fork that will be maintained as long as possible by @code-lts members :muscle:
:rocket: 1.4.0 was released See how to install it (composer require code-lts/laravel-fcm)


Mahdi Aryayi / Replace normal IBM plex font with variable font

Description
We are using the "IBM Plex Sans" font as our main font. the issue is we need to fetch a new font file for every new font-weight we use. but thanks to Variable Fonts, now we can fetch only one file that supports all font weights (from 100 to 700)
Changes:

The new IBM Plex variable font files and related CSS are added to the repository
the former typeface-ibm-plex-sans package is removed from Deriv-com.
some auto vulnerability fixes applied with npm audit fix

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[x] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[x] Improve performance
[x] Style only
[x] Dependency update
[ ] Documentation update
[ ] Release

Do we need to remove the package-lock.json content for this PR?

That's not directly related to this task. I just did a npm audit fix to fix dependency vulnerabilities. I mentioned that in the PR description

Do we need to remove the package-lock.json content for this PR?

That's not directly related to this task. I just did a npm audit fix to fix dependency vulnerabilities. I mentioned that in the PR description


Improve editorconfig

add all keys https://spec.editorconfig.org/#supported-pairs
repository can be checked with https://github.com/greut/eclint

Only src/__tests__/utils/unicode.data.ts has 120+ long lines.
Maybe TypeScript has a feature to break long lines.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
265

Relevant Lines:
265

💛  - Coveralls


samples: Bluetooth: BAP: Add missing return in stream_is_streaming

Add missing return before a false;.

Setting this as 4.1 milestone, unless someone else wants to create a GH issue for it :)

sorry @Thalley I'm going to override your milestone and just merge this one.  It's an obvious bug fix to me.  Hope you don't mind skipping the wait.


feat(cli): added cli option for ingestion source

I'm adding a new CLI command called "datahub ingest list-source-runs" (name pending) that will give this result

Can also filter by URN and/or source name:

Do we like the resulting columns? Are there any we should add or get rid of?
I attempted to filter by platform but it seems like platform is always null in the graphql response.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

These are output columns for datahub ingest list-runs as of today: runId, rows and created at.
In your proposal, columns are: runId, source, startTime, status and URN.
I guess startTime is same as created at, so this is adding source, status and URN.
Instead of adding a new option to the command line, why not extending existing table with the new columns?
I hope this helps:

datahub ingest list-runs is resolved by https://github.com/datahub-project/datahub/blob/84de42d718ee52be17e77f04bb4ae0df6cd1d2f6/metadata-io/src/main/java/com/linkedin/metadata/systemmetadata/ElasticSearchSystemMetadataService.java#L200
and modelled in https://github.com/datahub-project/datahub/blob/84de42d718ee52be17e77f04bb4ae0df6cd1d2f6/metadata-models/src/main/pegasus/com/linkedin/metadata/run/IngestionRunSummary.pdl#L3

FYI: @hsheth2

I think we decided that making a new working command was better than changing an old one.

I was not aware this had been discussed before, sorry for the confusion I may have caused.
If you discussed this with someone else, feel free to invite them to join the review here.

Going to weight in with my two cents here
Main question is if we consider the old behavior to have any real use cases, or if we'd just say the old behavior was buggy.
If the former -> let's do two commands as done here, and we can mark the old one as deprecated
If the latter -> we can just replace the old command, since there's no real reason to keep it around

Talked to Gabe about this separately. I could see the old behavior having use cases, e.g. if you are disciplined about setting run ids while using the API, that is not represented by the list of custom ingestion sources. In general I think run ids and ingestion source runs are different enough that we can have CLI commands for both, as long as they're distinguished esp in docs.

Another use case: a user produces data from an ingestion source, then hard deletes it. If they want to clean up data from that deleted ingestion source, they need to look at run ids, because the ingestion source no longer exists.

So it looks like we should keep both options. Do we want to change the help output for either one to make it more clear what they're doing? Any changes to docs necessary?

So it looks like we should keep both options. Do we want to change the help output for either one to make it more clear what they're doing? Any changes to docs necessary like adding deprecated?

Keeping both options 👌
My suggestion:

Renaming list-runs to list-run-ids would be a breaking change, which I'd prefer to avoid. Let's maintain list-runs and introduce list-source-runs.
In addition to documenting the new list-source-runs, let's also add the missing documentation for list-runs to help users understand the differences.


Systemd service creation

Hi,  here are a few comments:

please mention clearly that this is a Python 3 project (some Linux flavors use Python 2 by default)
about systemd service files: you can use the example systemd file from the Wiki but only after running useradd --system --user-group powerdnsadmin to create an user for the service, and creating a log file owned by this group with touch YOURLOGFILE / chown powerdnsadmin:powerdnsadmin YOURLOGFILE.

Thanks for this great project!

Thanks for the suggestion. I am going to update the WIKI and README.


Implement a way to skip test cases

Sometimes, one's work on a feature may cause some tests to crash the compiler. In those cases, it could be helpful to skip specific generated test cases, either via an option in the command line or "manually" by editing the test case themselves. That way, one could still run the part of test suite that does not cause compiler crashes.

I don't think there's anything to implement. Swift test has a filter parameter (and a negative variant). You can just edit xxx into the names of the crashers and filter them out.

Nice!


Is there a Swift version coming out?

I've been using your library for quite some time now and love it. Also fully made the transition to Swift.
Can you tell me if and when there will be a Swift version coming out? I'd love use it! If you need testers for this let me know!
Cheers,
Sidney

I did make a start, but am time constrained too at the moment to finish it out. https://github.com/dglancy/SwiftRecord/tree/dg/dev

Popped a SwiftRecord
Working well afaik
https://github.com/arkverse/SwiftRecord

@zaiddag Neat! Though couldn't you get rid off all that forced casting by using Self in those functions?

@stephencelis sadly no. Calls to Core Data like NSEntityDescription.insertNewObjectForEntityForName return AnyObject. There is no support for casting into Self. It seems Self is only useful if you're using your class constructors. Also, there is no support for [Self] return types either.


⚠ Fortnite has degraded performance

In 084aba1, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1551 ms

Resolved: Fortnite performance has improved in ddb3b9b.


GCC 14 exrcheck -c error

Hi,
when using GCC14 for openexr-3.2.2 build on Fedora 40+, all goes well until test phase, where single one test fails with following error
/builddir/build/BUILD/openexr-3.2.2/fedora-build/bin/exrcheck -c /builddir/build/BUILD/openexr-3.2.2/fedora-build/src/test/bin/v2/LeftView/Balls.exr
/usr/include/c++/14/bits/stl_vector.h:1127: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = std::allocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Traceback (most recent call last):
  File "/builddir/build/BUILD/openexr-3.2.2/src/test/bin/test_exrcheck.py", line 41, in <module>
    assert(result.returncode == 0)
AssertionError

Do you have any guess, what can cause this issue? The Balls.exr is the only one file that fails exrcheck -c, all others pass it properly.
Cmake settings below
/usr/bin/cmake -S . -B fedora-build -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON
-- The C compiler identification is GNU 14.0.1
-- The CXX compiler identification is GNU 14.0.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found PkgConfig: /usr/bin/pkg-config (found version "2.1.0")
-- Checking for module 'libdeflate'
--   Found libdeflate, version 1.19
-- Using libdeflate from /usr/lib64/libdeflate.so
-- Using Imath from /usr/lib64/cmake/Imath
-- Performing Test OPENEXR_IMF_HAVE_SYSCONF_NPROCESSORS_ONLN
-- Performing Test OPENEXR_IMF_HAVE_SYSCONF_NPROCESSORS_ONLN - Success
-- Performing Test OPENEXR_IMF_HAVE_GCC_INLINE_ASM_AVX
-- Performing Test OPENEXR_IMF_HAVE_GCC_INLINE_ASM_AVX - Success
-- Looking for include file ucontext.h
-- Looking for include file ucontext.h - found
-- Performing Test IEX_HAVE_CONTROL_REGISTER_SUPPORT
-- Performing Test IEX_HAVE_CONTROL_REGISTER_SUPPORT - Success
-- Looking for include file semaphore.h
-- Looking for include file semaphore.h - found
-- OpenEXR pkg-config generation enabled
-- Configure OpenEXR 3.2.2, library API version: <IP_ADDRESS>
-- Found Python3: /usr/bin/python3.12 (found version "3.12.2") found components: Interpreter
-- adding bin tests
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/TestImages/GrayRampsHorizontal.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/LuminanceChroma/Garden.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/MultiResolution/ColorCodedLevels.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/MultiResolution/WavyLinesLatLong.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/MultiResolution/WavyLinesCube.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/LuminanceChroma/Flowers.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/MultiView/Adjuster.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Chromaticities/Rec709_YC.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Chromaticities/Rec709.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Chromaticities/XYZ_YC.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Chromaticities/XYZ.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/TestImages/GammaChart.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Beachball/singlepart.0001.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/v2/LeftView/Balls.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/v2/Stereo/Trunks.exr
-- Downloading https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr-images/v1.0/Beachball/multipart.0001.exr
-- clang-format not found.
-- Configuring done (2.5s)
-- Generating done (0.1s)

hrm, I am still running gcc 13.2.1, will have to install 14 to check, but my initial guess is that you are hitting a bit of undefined behaviour that I am in the middle of fixing, should have a patch posted shortly.
In the previous patch, we re-enabled some deeper checks for deep files in the core library (-c of exrcheck) and that checking code itself isn't handling when there are no samples to decode and short-cutting the processing. So it is going ahead and saying "make the vector 0 samples sized" (to read into), and then accessing the vector as &v[0]. Because there are 0 samples, it does not actually USE this pointer, so is strictly speaking safe, however the newer safer code asserts and checks are failing on the access of a null pointer (because they don't know we won't use it).


Dev17 - Environment page not presented

It amazingly recovered after a restart.. Maybe it's just something with Dev17

I'm going to close this, but let's keep an eye out for it happening again. Thanks XiaoYun!


Feature request: Play in reverse

The API does not yet include an option to play in reverse. This would enable reuse of animations instead of being required to export a reversed version of the same animation through Bodymovin.

You can play it reversed by animating the progress value to go from 1 to 0.
import React from 'react';
import { Animated } from 'react-native';
import Animation from 'lottie-react-native';

export default class BasicExample extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      progress: new Animated.Value(1), // <-- Start from the end of animation
    };
  }

  componentDidMount() {
    Animated.timing(this.state.progress, {
      toValue: 0, // <-- Animate to the beginning of animation
      duration: 5000,
    }).start();
  }

  render() {
    return (
      <Animation
        style={{
          width: 200,
          height: 200,
        }}
        source={require('../path/to/animation.json')}
        progress={this.state.progress}
      />
    );
  }
}

@AWrightIV You can also set the speed to a negative value.

@gpeal I was looking into this and i noticed that setting speed to negative does nothing on ios is this a bug?


PECropView: Allow to programmatically set the rotation angle (with or without snapping to 90° angles)

This methods allow to easily implement clockwise/counter clockwise rotations from IBAction methods.
- (IBAction)rotationButtonTapped:(id)sender
{
    [_cropView setRotationAngle:_cropView.rotationAngle + M_PI_2
                           snap:YES];
}

Hi, I'm using your useful methods for image rotation.
After rotate the image of 90 degree, I'm tring to refresh the crop rectangle to match the new image size.
Do you have any suggestion on how can I acheve this ?


style: Eliminate some IDE warnings

What is the purpose of the change

Use ? to populate the generics of Class. Avoid IDE warnings
Use @SuppressWarnings("unchecked") to suppress type conversion warnings
Add final to the field ScopeModelAccessor

Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10626 (65ad301) into 3.1 (3431d21) will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.1   #10626      +/-   ##
============================================
- Coverage     64.78%   64.68%   -0.10%
+ Complexity      452      429      -23
============================================
  Files          1334     1334
  Lines         56763    56763
  Branches       8402     8402
============================================
- Hits          36774    36718      -56
- Misses        16038    16080      +42
- Partials       3951     3965      +14

Impacted Files
Coverage Δ

...bo/common/beans/support/InstantiationStrategy.java
88.63% <100.00%> (ø)

...pache/dubbo/common/function/ThrowableFunction.java
71.42% <0.00%> (-28.58%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
80.17% <0.00%> (-12.07%)
:arrow_down:

...va/org/apache/dubbo/remoting/TimeoutException.java
22.22% <0.00%> (-11.12%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
58.33% <0.00%> (-8.34%)
:arrow_down:

.../common/threadpool/serial/SerializingExecutor.java
70.37% <0.00%> (-7.41%)
:arrow_down:

...ava/org/apache/dubbo/rpc/proxy/InvocationUtil.java
84.84% <0.00%> (-6.07%)
:arrow_down:

...ubbo/common/system/OperatingSystemBeanManager.java
50.00% <0.00%> (-4.55%)
:arrow_down:

...registry/zookeeper/util/CuratorFrameworkUtils.java
70.00% <0.00%> (-4.45%)
:arrow_down:

... and 19 more

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


unsafe_rbg fold in function is insensitive to the order data is folded in.

Description
The unsafe_rbg fold_in function is not sensitive to the order in which data is folded in.
The underlying cause is that unsafe_rbg derives its key based on key ^ rbg(data), but XOR is a commutative operation. So if a user folds in two values the order will not change the result since key ^ rbg(1) ^ rbg(2) == key ^ rbg(2) ^ rbg(1).
Reproducing example:
for impl in ['rbg', 'unsafe_rbg']:
  print('impl:', impl)
  key = jax.random.key(42, impl=impl)
  print('Original key:', jax.random.key_data(key))

  key_1 = jax.random.fold_in(key, 1)
  key_12 = jax.random.fold_in(key_1, 2)
  print('Foldin 1 -> 2:', jax.random.key_data(key_12))

  key_2 = jax.random.fold_in(key, 2)
  key_21 = jax.random.fold_in(key_2, 1)
  print('Foldin 2 -> 1:', jax.random.key_data(key_21))

Result:
impl: rbg
Original key: [ 0 42  0 42]
Foldin 1 -> 2: [257214496 567757975 257214496 567757975]
Foldin 2 -> 1: [2853785955  313133857<PHONE_NUMBER>  313133857]
impl: unsafe_rbg
Original key: [ 0 42  0 42]
Foldin 1 -> 2: [2393909057<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>]
Foldin 2 -> 1: [2393909057<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>]

Notice in the unsafe_rbg case the two derived keys are the same.
System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.29
jaxlib: 0.4.29
numpy:  1.26.3
python: 3.11.8 (stable, redacted, redacted) [Clang google3-trunk (fc57f88f007497a4ead0ec8607ac66e1847b02d6)]
jax.devices (1 total, 1 local): [TpuDevice(id=0, process_index=0, coords=(0,0,0), core_on_chip=0)]
process_count: 1
platform: uname_result(system='Linux', node='8f069381872f0396-766a8253c8.borgtask.google.com', release='5.10.0-smp-1<IP_ADDRESS>', version='#1 [v5.10.0-1<IP_ADDRESS>] SMP @1712273364', machine='x86_64')

This is not an urgent issue to fix because it will change the reproducibility of bits produced by the PRNG. Just marking this as a fix we should bundle whenever we make a large breaking change to unsafe_rbg that would modify the bits anyways.


[2pt] PR: Adjusting SRCs using USGS rating curves

This code enhancement allows for the creation of a USGS gage database that contains the USGS rating curves converted to water surface elevations at flow values corresponding to NWM recurrence flow intervals. The database is then used to adjust the HAND-derived synthetic rating curves to more closely align with USGS gage rating curves (hydroID catchments that contain USGS gages). Address #495
Additions

tools/usgs_gage_src_adjust.py: Creates a database of USGS gage locations with USGS rating curve values converted to water surface elevations (sampled at flow values corresponding to NWM recurrence flow intervals -2, 5, 10, 25, 50, 100-year values). Log files are provided in the provided fim_dir in a new directory - src_optimization/

Changes

tools/adjust_rc_with_feedback.py: Updated to pass a dataframe of user supplied WSE/flow data instead of a csv file. Also, added an if statement to catch instances where all valid hydroID roughness calculations are removed when located in lakeid catchments.
tools/rating_curve_comparison.py: Modified to plot both "FIM" and "FIM_default" SRCs where available. Example plots below.
tools/tools_shared_functions.py: Added two new functions. 1) concat_huc_csv concatenates huc output csv files into a single dataframe and 2) check_file_age returns the date modified attribute of a an input file
tools/wrapper_usgs_gage_crosswalk.py: This wrapper function allows the user to run the src/usgs_gage_crosswalk.py function without needing to perform an entire run of fim_run.sh

Testing

Tested usgs_gage_src_adjust.py for fim_dir containing all MS BED hucs: python3 foss_fim/tools/usgs_gage_src_adjust.py -fim_dir data/outputs/dev_v3_0_24_8_fim_run_ms/ -usgs_rc data/inputs/usgs_gages/usgs_rating_curves.csv -nwm_recur data/inundation_review/inundation_nwm_recurr/nwm_recurr_flow_data/nwm21_17C_recurrence_flows_cfs.csv -i True -j 9

Screenshots
Conceptual illustration showing the approach to sampling the USGS rating curve at discrete flow values to inform the adjustment algorithm for optimizing the HAND-SRCs.

Input arguments for usgs_gage_src_adjust.py

Example sierra test plot outputs showing USGS rating curves (blue), default SRCs (green), and modified SRCs using usgs_gage_src_adjust.py (orange).

Notes

Next step: perform alpha evaluation using the updated SRCs output from usgs_gage_src_adjust.py

Todos

Resolve tools/rating_curve_comparison.py differences with active PR 508 (https://github.com/NOAA-OWP/cahaba/pull/508)
Update changelog.md prior to merge (coordinate with others to determine version number)

With some of the SRC evaluations suggesting that SRC error does not correlate with CSI performance (i.e. greater SRC error for high flows where CSI performance is greatest), do we have concerns that calibrating to SRCs will yield lower CSI? @BradfordBates-NOAA @CarsonPruitt-NOAA

@frsalas-noaa Great question - we've been discussing this a lot this sprint. We are going to kick off a MS BED run later today and then produce some fresh alpha test metrics. Hopefully that will shed some light this question. The USGS rating adjustment currently is configured as a stand alone tool and has to be run manually. Before we make a decision on integrating the USGS rating curve calibration, we'll use the alpha test to determine the path forward (e.g. implementing the SRC adjustment as part of fim_run.sh).

Understood Ryan. Thanks!
On Friday, January 21, 2022, Carson Pruitt @.***> wrote:

@.**** approved this pull request.
Tested on a subset of 8 HUCs and everything works well. Also ran
rating_curve_comparison.py on the outputs, which was also a success.
Just a note: there was some weird behavior on huc 05030101. See the
screenshot below.
[image: FIM-USGS_rating_curve_comparison_05030101]
https://user-images.githubusercontent.com/90792257/150586407-86045a90-6d62-4e73-bf01-3be95eacb19e.png
Looking at the recurrence intervals, I think this is just due to the weird
shapes of the rating curves trying to fit to the intervals. The screenshot
below shows the rating curves with the pre-adjusted rating curves.
[image: FIM-USGS_rating_curve_comparison_05030101]
https://user-images.githubusercontent.com/90792257/150586660-e94bed7c-4a3b-4d38-b7ea-3e741426fabd.png
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/cahaba/pull/509#pullrequestreview-859936737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO6EII6VT4YHZ4IPQ2F7LPTUXGWCXANCNFSM5MODHLOQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Fernando R. Salas
National Water Center
Geo-Intelligence Division | Office of Water Prediction
NOAA National Weather Service
Office:<PHONE_NUMBER> | @.*
@.**>
http://water.noaa.gov http://water.noaa.gov


Increase flexibility of date based context parsing

Also converts datetime based context from LocalDateTime to
ZonedDateTime which holds the timezone with the DateTime

TODO on this commit:

[ ] Disambiguate the relative time parsing when the initial sign is a - -> should this only make that term negative or the whole term negative (if not otherwise specified)?
[ ] Documentation changes

Ready for merge.


Remind minutes not working

First, I'd like to say that this tool is great! It work wonders and I really want to use the remind function to run some script whenever an event occur with Raspbian Jessie. So I test it with
gcalcli remind 5 'echo Hello World'
but the Hello World text appear immediately after I enter the command. Did I missed a command or something? Please let me know as I'm quite a beginner :)

Hi there!
The remind command will execute the given command immediately when there is an event in your calendar that starts within the given number of minutes.
So in your example, you obviously had some event in your calendar within the next 5 minutes, that's why the command echo Hello World was correctly executed.
If you wanted the command to be executed after 5 minutes, then maybe you want to try something like sleep 5m && echo Hello World?

I'm having the same problem. Steps to reproduce:

Create an event on my calendar that starts in 10 minutes.
Wait one minute just to ensure there's not a clock skew issue making it hard to repro
Call gcalcli remind 5.

Expected result: No notification
Actual result: Notification

By any chance, do you have the --use_reminders flag activated?
--[no]use_reminders: Honour the remind time when running remind command

According to this codeline, the remind command shows all events that will happen between now and minutes + 5. So if you say gcalcli remind 5, you actually get all events from now to 10 minutes in the future. If your event is 11 minutes or more in the future, the command works as expected.
https://github.com/insanum/gcalcli/blob/master/gcalcli#L1897


[Request] Config option to change infinity drill drop chance / disable drops completely

Industrial Foregoing Version: 1.11.10-223
TeslaCoreLib Version: 1.0.63
Forge Version: <IP_ADDRESS>96
Minecraft Version: 1.12.2
Crashlog (If Any): n/a
Echoing #467 , not sure why this issue was closed but I'd like to revisit it. As of the most recent version of IF, there is no config option to change the drop rate of the infinity drill or disable it entirely. I would very much appreciate such a feature, as having the drill drop from mobs does not fit well with the theme of my modpack. Please consider this request.
Thank you,
Luke616

It doesnt drop anymore stop creating issues without testing...

Then what's up with this guy? I thought these particles meant that mobs had a chance of dropping the drill. Apologies for the misunderstanding.

Screenshot taken in:
Industrial Foregoing Version: 1.11.10-223
TeslaCoreLib Version: 1.0.63

There is another method of obtaining the Shiny variant that I wont spoil

Ah, I see. May I change the request to instead ask for a configurable chance of these shiny mobs? They spawn a little too frequently for my tastes, and are confusing players of my pack. Thanks!

Alright, thanks anyway


feat(delete-deployment): also delete environment

:pencil: Description
Delete the associated GitHub environment when deleting a deployment.

:tada: This PR is included in version 1.22.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Using SASS in the dooz react project

The project uses CSS modules for styling the elements. As you know SASS is just a CSS preprocessor that builds a CSS file at the end. SASS provides more functionality on top of CSS, which is exactly what we'll need to write reusable CSS code. We can start using SASS in React by installing the sass package via npm or yarn, updating our CSS files to .scss or .sass, and then updating our imports to use the new file extension.

nice 👌


[RFE] Support for Swift/UFO Object Storage

On Red Hat's documentation page there are instructions on how to enable/install The swift api for object storage. It's also referred  to as UFO.
I've also used UFO in my previous job and it worked well as I only had to maintain one system (my gluster installation). Now that gluster is containerized; I think it would be a good idea to extend the functionality by enabling UFO.

Hi @christianh814 , thanks for your suggestion!
We are already on it and containerizing gluster-swift. See:

https://hub.docker.com/r/gluster/gluster-object/
https://github.com/gluster/gluster-containers#gluster-object-docker-container

Is that what you're thinking about?


[B11] Missing mossy stone recipe

Hedge Alchemy progress listing Mossy Stone as a requirement, but missing a recipe.

#510

I swear I did use search.


[FLINK-20379][Connector/Kafka] Improve the KafkaRecordDesrializer interface

What is the purpose of the change
The current KafkaRecordDesrializer has the following problems:

The existing DesrializationSchema and legacy KafkaDeserializationSchema implementations cannot be reused.
Missing an open() method with context for serialization and deserialization.

This patch fixes the above issues by doing the following:

Add a getUserCodeClassLoader() method to SourceReaderContext so the SourceReader implementation can construct the SerializationDeserializationContext.
Add the bridge method to facilitate reuse of the DeserializationSchema and legacy KafkaDeserializationSchema.
Rename KafkaRecordDeserializer to KafkaRecordDeserializationSchema to follow the naming convention.

Brief change log

Add a getUserCodeClassLoader() method to SourceReaderContext so the SourceReader implementation can construct the SerializationDeserializationContext.
Add the bridge method to facilitate reuse of the DeserializationSchema and legacy KafkaDeserializationSchema.

Verifying this change
Unit tests have been added to KafkaRecordDeserializationSchemaTest to verify the change in KafkaRecordDeserializationSchema
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (yes)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (Java doc)

On the "Move Deserialization From SplitReader to RecordEmitter" discussion:
I would be interested in seeing how this impacts performance. The current Kafka connector runs deserialization in the processing thread, so we could use this as a baseline for performance comparison.
Right now, the new Kafka connector does strictly more work (in CPU cycles) with its wrapping and re-packaging of records, compared to the old connector, or an approach that deserializes in the RecordEmitter.
The assumption that this is faster can only hold if the actual processing is not sufficiently parallelized (there are unused cores, so it is better to do something less efficient where more threads can be used).
To my knowledge, any setup with sufficient parallelization across partitions wins over setups which try to parallelize across pipeline stages: Data parallelism always beats pipeline parallelism on modern hardware. So if you have spare CPU cores, increasing the parallelism of the operator (and slots per TM) is more efficient than trying to spread work across more threads and stages. Otherwise, it would not be a good idea to chain operators into tasks, but we should have a thread per operator.

I think you are right. At the high level, the performance would be the best all the CPU cores a busy and they do not do unnecessary work.
In the ideal case, there are N dedicated main threads, where N == number of CPU cores, so no computing resource is idle. These main threads will only be "interrupted" by IO, which means there are more records to be handed over to the main threads for processing. Async IO would be beneficial so that can be done in the main thread without interruption or context switch at all. We can achieve this in KafkaSource because KafkaConsumer is designed to be non-blocking.
The only potential problem I can think of is the overhead of increasing the parallelism. e.g. more memory footprint, more IO buffer, etc.
And I think you are also right about the assumption based on which more deserialization threads works. For most streaming systems in production, actually there are spare CPU resources. And increasing the parallelism is usually done by adding a new JVM instance which could be expensive. So adding more deserialization thread helps.


Sunstone error when try to delete recursive service template

Description
When creating a service, if the templates are from different groups the sunstone does a redirection
To Reproduce

Take an existing service template.
Create a full clone (with VM templates and images) of a service.
The newly created service template belongs to the logged-in user and is available in his user group
Delete the service template. The error occurs when deleting only the service template, with VM template and with VM template and image, so with all possible options.
Sunstone will redirect to dashboard

Expected behavior
no redirect to dashboard
Details

Affected Component: [Sunstone]

Additional context
Add any other context about the problem here.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@tinova PRs to apply:

code: https://github.com/OpenNebula/one-ee/pull/1232
docs: https://github.com/OpenNebula/docs/pull/1843


Update Contributors.md

Well, this is the type of thing I was looking for, a reference point from which to start my journey in open source development...The whole experience was great, and has provided me with some amount of confidence that I can proceed with further challenges.
Thank You.
Also, will it be okay if I ask you for help sometimes? I am new to this, and I'll need help while I become proficient at this.

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Unable to connect to choosen node

The app does not connect to the mainnet:

Superhero 83b14be/v.0.4.1

A few of us are having this exact same issue on mobile. Desktop works though.

Same here, issue still persists on Android mobile app.

Current version of wallet doesn't have such problem. Feel free to reopen this issue, if it will pop up in next versions.

Current version of wallet doesn't have such problem. Feel free to reopen this issue, if it will pop up in next versions.


Set module to es2020

Module was previously set to 'es2015' as the default when 'target' is 'es2020'. Now it is set to 'es2020' to support feature like dynamic imports

Closing for now, because it does not give us any benefit right now.


Drop "-demo"

Prepare for new URL.
Note: there was one use of idr-clone.o.org which I don't remember the purpose for. I've changed it to just idr as well. cc: @aleksandra-tarkowska

Looks fine to me, will be tested during the next test deployment


blog: Exp versioning

First draft of experiment versioning blog post. Mostly worked on the intro. The tutorial section is outdated, mainly from when we were still focusing more on "lightweight experiments" rather than "experiment versioning."

Hm, not sure why this isn't deploying. Hoping to start sharing it around for feedback if I can get a preview deployed.

I've requested the redeploy. @dberenbaum does it work for you locally?
@rogermparent I wonder if there is a way to connect Heroku better - see the logs here and a bot that would react to /rebuild command or something.

Sorry, I should have debugged locally first! It's working locally now, but I can't figure out how to add myself as an author. I tried adding myself to content/authors but still getting an error. Also not sure where/how to include the avatar since I see them in multiple folders, and I'm not sure if there are size requirements or anything.

@julieg18 @rogermparent could we please help Dave here and update the contrib docs if needed to help other folks in the future?

Ah, sorry again! I didn't realize we had https://dvc.org/doc/user-guide/contributing/blog. Let me try once more.

Okay, got it working, thanks!

This is still not ready for copy editing, but any other feedback would be appreciated!

Only other thing that needs to be poked in somewhere is link to command ref doc. Maybe in more than one place.  Where appropriate in body and also at the end.

Only other thing that needs to be poked in somewhere is link to command ref doc. Maybe in more than one place. Where appropriate in body and also at the end.

What other links would be useful to add @jendefig?

What other links would be useful to add @jendefig?

Well we discussed putting the video in.  I think after the first paragraph would be a good place.  Then they can continue to read in more detail.
The other links that are in there are good, but just need the right formatting.
The only other things I can think of is to direct to Jorge's Use case doc that should be up and maybe (?) to the meetup where we will have demo (Join us at our December Office Hours for a demo on dvc exp init ! ) But that will be tricky because I will have to have the event posted in Meetup already.  But I can do that by doing some kind of "we have something really exciting planned this day, but I can't tell you yet" kind of thing and then change the info to Meetup correctly on the day of the release.  That would work. And potentially build anticipation.

It is good (and probably the best from technical point of view) but might be too deep\long for a wide audience. It lacks real life examples. I guess, a good portion of our audience values the problem Exp Versioning solves more then machinery behind it including definition of experiments and history. I'd try to create the entire post (or the first part of it) based on examples (what I cannot properly do with MLFlow but I can with DVC?) and talk about experiment definitions and history in the 2nd part. The history is a good foundation for strong conclusion.

Yes, agree this is the key question. I want to wait on addressing the smaller comments until we get a good basic structure in place. I had the same thought that the history stuff might be too much buildup that users don't really care about, depending on what kind of post we want this to be. I had already considered that a lot of the history might get cut out, so no big deal if that's what happens.
Let's discuss this week. I've been working through some ideas that I can also show a little bit during the DVC working session or elsewhere. One challenge is that the biggest advantages shine through in complex examples (working on multiple branches, going back in history after developing many experiments, etc.), so it can be hard to develop succinct examples. Especially if we also want to highlight dvc exp init and getting started quickly, which focuses on more simple use cases.

@dmpetrov and others, PTAL at the latest draft when you have a chance. Thanks!

@dberenbaum Here is the link to the  December OH meetup in which we will have the demo: https://www.meetup.com/DVC-Community-Virtual-Meetups/events/282064369/

@dmpetrov Another version of the blog post is ready.
I left in your ascii drawing, but another option is a tree like we show in the video with experiment leaves growing from the branches.
We may also need to add in some link at the end for where to go to get started.

I left in your ascii drawing, but another option is a tree like we show in the video with experiment leaves growing from the branches.

I've been wondering about this for a few days.  Might it be better if the blog post image is the tree from the video?  I'm sure we can use the other image we've been working on somewhere (another blog post, presentations, etc.). But it might make more sense because the title of the blog post doesn't exactly tie to the image.  (Tracking is not really what's happening, or versioning - it's just the chaos of it all out of control).
And then per @dmpetrov 's point re:

🔥 great section name! is there a way to mention this in the intro\description? 🙂

Maybe add this to the short description, which needs to be as strong as the long description.
"ML Experiments as Code takes ML experiment tracking to the next level; bringing together the benefits of traditional code versioning and modern day experiment tracking, super charging your ability to reproduce your work."

@dmpetrov There's another iteration ready if you want to take a look.

One other idea from https://github.com/iterative/dvc.org/pull/2909/files#r759706747:

It might help to discuss why we have this workflow and want to leave changes un-committed. In other experiment tracking tools, the workflow looks like:

Run the experiment.
Log the commit hash of the current HEAD, even though it doesn't include your dirty changes.
If everything is successful, save changes in a new commit.

This creates a confusing state where the experiment should really be associated with the second commit instead of the first.
It might be too much detail or inappropriate for the page, but maybe it can be summarized, or it might spark other ideas. This is probably a good point for the blog post but not sure if there's a place for it...


Avoid E118 error on trash()

Below error occured using trash on an unsupported platform
because of function type mismatch.
E118: Too many arguments for function: <SNR>144_trash

I found this error when using https://github.com/lambdalisue/fern.vim .
So please update fern.vim also if you can.

Done on fern.vim as well.


feature request: group git hooks together

Here's a list of git hooks that can be applied to the npm scripts. Thoughts?
https://github.com/typicode/husky/blob/HEAD/HOOKS.md

Seems totally reasonable to group these together! Happy to see a PR that adds this feature 😄

@reggi link no longer working and you going to take on this?

@muuvmuuv unable to work on this

Can we close this now?


Don't show items that just have source compatibility

If an item is source compatible, that should be considered a no-op from a porting perspective. Thus, we shouldn't expose that in reports.

Double-checked, I think this should be fixed.

We have this fixed here: https://github.com/Microsoft/dotnet-apiport/blob/master/src/Microsoft.Fx.Portability/Analysis/AnalysisEngine.cs#L249


Features:
📝 Accurate API Documentation - We built Optic to make maintaining accurate specs for your APIs automatic and developer friendly. Once you add Optic to your API repo, it automatically tracks your API’s behavior and maintains a change log of its behavior over time.
It’s kind of like Git, but instead of tracking files, Optic automatically diffs and tracks API endpoints. When new behavior is observed, Optic makes it easy to update the spec.
⚙ Automated Testing - Automate most of your contract testing. Optic uses live testing with spec coverage to make testing APIs easy.
👍 Beautiful Docs - Stripe-style documentation for every API managed by Optic.
👋 100% Open Source, Runs locally, data is only stored in your API Repo

@trulyronak Thanks for your contribs!


Ability to autobench + upload results?

It would be epic if a simple comparison portal could be made, something like (the now defunct?) serverscope.io as well as enabling hosting providers to provide systems which would be periodically auto-benched and collated on this portal.
I / we might be interested in contributing to developing something like this, as existing comparison sites out there are not very vps focused and/or are broken/obsolete in various ways.

Hey there, I appreciate the interest and the great suggestion! Another YABS user had a similar concept in mind, but I don't believe it has been pursued yet.
I am not opposed to this idea and would gladly incorporate into the project, should something be developed to house the scores for comparison. I will, however, like the uploading of the results to the comparison to be opt-in rather than opt-out. Meaning a switch/flag (i.e. -u) would need to be present when running the script in order for the results to be uploaded. Wouldn't be hard on my end to modify the script to save off the values that are going to be uploaded to the comparison site (geekbench scores, disk iops/speed results, net speeds, etc.).
Auto-benching could be done very easily without any modifications, simply by using cron. Add something like:
0 0 */12 * * cd /home/user/yabs && DATE=`date "+%F-%T"` curl -sL yabs.sh | bash >> yabs_"$DATE".log

to the crontab to bench every 12 hours and save the results to a log file. Obviously, this can be changed if the comparison site is completed and the upload flag can be put in place instead of saving the log file.
If you decide to pursue the comparison website idea, feel free and keep me updated on the status! Unfortunately, I can't really commit to helping out with the project due to time constraints, but I'll always be available to bounce ideas off of or to provide feedback, if desired.

That's great news! I was using my "personal" account for the previous post, which is why I didn't see you had replied here till now. But as you can see we are a Cloud hosting provider.
Our core interest is of course - without a doubt - to be able to show users in an objective and "as unpartial as possible" manner what our system scores are as well as enabling users to accurately - and fairly - compare providers across metrics and cost. It takes a lot of time to do manual benchmarking and setting up reports like this, and we have sort-of given up on doing that for our website as it is simply too costly in terms of man-hours.
So, that's our motivation. The other motivation is that the existing comparison sites out there focused on Cloud Hosting are, well, quite bad. Some (will not name names) are for-profit and this gets in the way of usability (sponsored providers are "in the way" of accurate comparisons) while others are simply not maintained / defunct.
We propose the following:

We would come up with a site design and comparison views / logic which we feels serve the customer best (quick, accurate overview of providers based on metrics they are interested in, as well as cost, if known)

As the script / data provider we would defer to your judgment as the fair arbiter of what information should be shown and how

We would, once launched, invite all players in the industry to "sign up" and set up automatic benchmarking of their instances, which will be made available for free, for everybody.

 If the site becomes some sort of industry standard (we can only hope) - then we would convert this to a legal not-for-profit entity, hopefully ensuring unbiased reporting of price/performance throughout the hosting industry for years to come

We agree reporting should be opt in. We also see that your end of this would be very simple - just submit all the data as json, adding in a few fields so users can define a provider name, plan id/name and plan cost.
We imagine we would be able to combat fraudulent submissions with the power of crowdsourcing - i.e. we would suppress test results which are statistically anomalous compared to what has been submitted. Details of this is something we will try and hash out in a sane manner :)
Can you send me a PM with contact details, so we can discuss further? With a positive reply, I will get the design and technical process underway on my end.

@webdock-io - I owe you a response to your email that you sent awhile back so we can talk specifics about this in case you are still interested in pursuing this idea. I dropped the ball on formulating a plan and replying to you quickly, so my apologies on that front. Be sure that this is still on my mind and I've been thinking about it for some time now. Talk soon!

I gave it a shot at vpsbenchmarks.com. It's very fresh, just deployed. New Yab. I tried to keep it simple, you copy and paste the yabs.sh output in the box, add a provider name and a plan name and you get a page with the data in nice html tables plus a couple of charts. There's also a list of recent yabs runs.
The next steps will be to allow sorting and filtering in the list and probably a comparison page. The feature is wide open right now so I expect it will be abused, at that point I'll probably have to require registration to submit new data.
Please give it a try if you get a chance and let me know what you think.

That's sounds great. I'll be glad to adapt or create a new endpoint at vpsbenchmarks.com for the format you come up with. Currently, you can post the yabs.sh output to VPSB with:
curl -sL yabs.sh | bash > yabs.out
curl -F "data=<yabs.out" -F "os_version=`lsb_release -s -d`" https://www.vpsbenchmarks.com/yabs/upload

So it's just a POST with a data and an optional os_version field.
I'm particularly thrilled about getting the data in json format!
I have one additional wish: have the ability to pass an api token as an option to yabs.sh along with the url so that the server can limit abuse if need be.

I applaud this initiative and I apologize for our inactivity on this matter - we fully intended to contribute here at some point, but as our platform grows a lot of other stuff has taken precedence.
While I applaud this development I think a prudent step would be to reach out to the various VPS benchmarking portals and make them aware of this new feature in YABS in case they want to adopt it.
I thank @plerohellec for taking the lead here, although I am still not happy about the fact that vpsbenchmarks.com refused to list us as they thought we were being unfair to the competition :) Maybe they will reconsider once we have our dedicated VPS product online (sometime this year we hope) which should then be more of an apples-to-apples comparison with the traditional providers.
Let us know if we can contribute in any meaningful way here.!

@webdock-io ah yes, I remember your last email. It's been a while, I can take another look if you'd like, please contact me directly, you have my email address.

@plerohellec -

I have one additional wish: have the ability to pass an api token as an option to yabs.sh along with the url so that the server can limit abuse if need be.

I'm pretty sure this can be achieved outside of the script (via the URL directly), but I'll need to test. Imagining something like this:
curl -X POST https://yabs.sh/upload/json?apikey=abcde12345fghij67890
   -H 'Content-Type: application/json'
   -d '{json}'

so, the end user would call something like:
curl -sL yabs.sh | bash -s -- -u "https://yabs.sh/upload/json?apikey=abcde12345fghij67890"

@webdock-io -

I applaud this initiative and I apologize for our inactivity on this matter - we fully intended to contribute here at some point, but as our platform grows a lot of other stuff has taken precedence.

Hey, no worries! I completely understand. Life has a way of throwing constant curve balls your way, especially when running your own business. I think this issue being opened and some of the discussion around has been the catalyst for some of the yabs benchmarks sites that are currently being worked, so thank you nonetheless.

While I applaud this development I think a prudent step would be to reach out to the various VPS benchmarking portals and make them aware of this new feature in YABS in case they want to adopt it.

Good idea! Will try and get the ball rolling on that soon.
@s0c-org has been developing a YABS result aggregator for some time now and we've had a lot of back and forth on the subject. Beta version is here if anyone reading this is curious and would like to check it out: https://debug.s0c.org/. Working him to deploy a test branch of YABS to shoot the json results to his site so we can grease the wheels and get things moving along. Eventually, once the functionality is complete, it'll get merged into the main branch and allow any site to be used (main ones will be listed in the Readme so that users are aware). More to come soon.

@masonr I think you're right about the api key as a query parameter, that should work.
I'd be happy to help you test yabs.sh with json output if it's available somewhere too.

@plerohellec -- sorry for the delay addressing this! I just committed some changes to the repo to JSONify the YABS results and upload them to a benchmark website of choice.
curl -sL yabs.sh | bash -s -- -j "http://example.com/yabs/post"
So you can know what to expect, an example JSON output can be found here: https://github.com/masonr/yet-another-bench-script/blob/master/bin/example.json
Give me a shout with any feedback!

@masonr Although we don't have an immediate use case in mind for us over here at Webdock at this time, this is a pretty epic feature and the json looks yummie! Great work! Thanks for moving on this

Thanks @masonr, that looks awesome! I think this json output will be hugely useful.
One wish though: I think the output format feature should be decoupled from the upload feature. The json output format is by far the most useful part of those changes and it has value even without the upload. The upload is not a "one size fits all" and it can easily be implemented outside of yabs.sh just by piping yabs.sh output. For example, some servers will expect additional parameters, the VPS provider name, authentication parameters/headers or the desired response format (Accept header) but if it's hard coded in yabs.sh, the upload can't be customized.
I'd recommend 2 separate options: "-j" or "-f " for specifying the output format and "-u  for performing the upload for example.
Not as important but I wonder if units and labels should be added to the json output especially for fio, I'm afraid there is a risk for confusion with just ["4k", 154305, 38576, 154712, 38678, 309017, 77254].
Does that make sense?

Thanks for the feedback, @plerohellec!

One wish though: I think the output format feature should be decoupled from the upload feature.

Totally doable and I understand the benefits of doing it that way. I'll work that in shortly when I push some updates.

Not as important but I wonder if units and labels should be added to the json output especially for fio

Yes! Didn't feel like writing up the schema or annotating last night when I cobbled all this together, but yes, desperately needs either more explicit naming in the JSON format, or a companion data schema doc that explains how to interpret all of the fields.
I'll work these changes in over the next couple days and get an update out for some further feedback. Really appreciate your insight and help! :)

@plerohellec just to follow up on this.
I just pushed another update to the JSON-related capabilities. Following your advice, I added a couple additional flags:
-j will print the JSON results out after the script is done running, thus can easily be piped (i.e. curl -sL yabs.sh | bash -s -- -j | tail -1 | <your_cmd_here> -)
-w will write the JSON results out to a file in the current directory (named yabs_{date}-{time}.json)
-s will upload the JSON results to the passed URL. This now also accepts multiple URLs to send the results to multiple websites simultaneously
I touched up the JSON schema as well to make things more explicit. I will be making a companion schema definition soon to define what units are being used for the various fields and all that good stuff. Let me know what your thoughts are!

Thank you @masonr , this is a good, flexible set of options.
For the -w, I'd rather have the yabs.sh user choose the filename himself with -w <filename> because if yabs.sh builds the filename then the user will have to guess this filename/date format when he wants to use it and that could be a frequent source of errors.
For fio units, I wonder if the simplest way would be to have them in the json output in the same fields as the values, the same way you did it for the iperf3 ("122 MB/s")?

@plerohellec  -

For the -w, I'd rather have the yabs.sh user choose the filename himself with -w  because if yabs.sh builds the filename then the user will have to guess this filename/date format when he wants to use it and that could be a frequent source of errors.

Changed up the -w flag to accept a file name (or path + file name)

For fio units, I wonder if the simplest way would be to have them in the json output in the same fields as the values, the same way you did it for the iperf3 ("122 MB/s")?

I personally think that it'd be best for all the units would be in the raw form provided by the tool in whatever base units the tool provides. Fio outputs the speed results as KB/s by default. Unfortunately for iperf3, I'm have to grep the output which doesn't provide a raw measure in a base unit (only formatted [i.e. '122 Mbits/s']), so I'm stuck with the formatted value.

Thanks for the -w  change.
How about add a speed_unit field at the top of fio? Something like this:
"fio": {
  "speed_unit": "KB/s",
  "results": [{
		"bs": "4k",
		"speed_r": 165590,
		"iops_r": 41397,
		"speed_w": 166027,
		"iops_w": 41506,
		"speed_rw": 331617,
		"iops_rw": 82903
	},
  ]
}

FYI For alternative
https://yabsdb.com/
curl -sL yabs.sh | bash -s -- -s "https://yabsdb.com/add"

@masonr, I finally implemented the json parsing and uploading with yabs.sh -s. So you can now run
curl -sL yabs.sh | bash -s -- -s https://www.vpsbenchmarks.com/yabs/upload
and visualize the results at https://www.vpsbenchmarks.com/yabs.
Some more feedback on the json format now that I'm very familiar with it:

There are some fields in the text output format of yabs.sh that are missing from the json. Those that I miss the most are Host, ISP,  Location, Country and VM TYpe. They are all very useful for adding context to the test and organizing the yabs data. I would love to have them in the json.
I still miss units in the json, not only fio but also mem/ram, swap and disk. The problem with the lack of units is that, if either yabs.sh or fio decide to change them for any reason, services that parse the yabs.sh json will have no way to know of the change and will record the data with the wrong unit. I can't think of any solution other than including the unit in the json.

I was looking at how fio does it when it prints json (fio --output-format=json) and I see that it includes the unit as a suffix of the metric name, for example io_bytes, io_kbytes or latency_ms. Maybe that could be a  solution for yabs.sh too? I'm really open to anything to get those units with the data.

I was not sure what the os/virt field was? Is it the same as "VM-x/AMD-V" in the text format?

Thanks again for the great work you're doing with yabs.sh!

@plerohellec - awesome! Sounds good and nice work on the json implementation.
Addressing your feedback:

Missing JSON elements: I'm tracking and will add all the missing pieces to the JSON output very soon. Will push an update that will bring the JSON output 1-to-1 with the textual output (including script start/stop/runtime, vm type, all network info).
Units: Agreed this is a must to standardize and add to the output. I'd like to not cause any backwards compatibility issues if I push a schema change, so any changes to the JSON structure will just be additions to the existing schema for better or worse. mem/disk and fio will be the low hanging fruit to knock out in the near term. With the eventual goal of getting iperf3 and ping latencies standardized as well.
Virt: Yes, cpu/virt field is same as VM-x/VMD-V in text form to indicate if the machine is virtualization ready.

As a side note, I'll be adding your site (and others) to the readme as places where YABS results can be uploaded and viewed.

@plerohellec - finally got around to this. Script now outputs JSON in the format here: example.json. Should address the units issue and add in all the missing stuff that wasn't being put in the JSON results. Also, added the sites that accept JSON results from YABS that I'm aware of to the README.

I'm going to finally put this issue to rest. I think YABS now has a solid way of uploading results and a few really great sites that support JSON result uploads. Appreciate all the input, help, and support to bring this together!
If any other issues or requests come up in the future, feel free to open a new issue for it! Thanks all!


Feature/d1.3 qa tree view h3 compat

Note that importing resources into a harvest (in the Tree View) doesn't work, but this problem already existed in master. I will create a separate issue for this.

I'm getting an error when trying to prune. Does it work for you?
My steps:

select resource
click 'Prune Single Item'
enter Provenance Note
click save

From the UI there's just a generic InvocationTargetException. But the error seems to be originating from the wct-store side, it's throwing an IllegalAccessError at line 675 in ArcDigitalAssetStoreService for the lib org/archive/uid/UUIDGenerator. I checked that webarchive-commons was packaged with the war file and it is, so I'm interested to hear if you have the same problem.

It works on my side, but I've only tested with jetty. I will see if I can reproduce this with tomcat.

I'm deploying the wars in a single Tomcat 8 instance now, and I'm still able to prune/add resources from/to the tree. I did find a different bug, though, but that was a null pointer.
Perhaps you have an old version of the UUIDGenerator class lying around? Perhaps the old H1 lib is also being included in your war?

O I just noticed that aheritrix.jar is indeed packaged in wct-store.war. This might be your problem.

Hmm but is it not packaged in your one as well?

Yeah, perhaps there's a difference in class loading order between our platforms or tomcat versions? Anyway, we can simply remove the old jar from wct-store.war and hopefully that will fix your problem?

It was still being included through the submit-to-rosetta module, which I'm guessing you wouldn't need. So I've swapped the aheritrix dependency within that to webarchive-commons, and that's fixed the original error.


Fix indentation check for access keywords

No whitespace before the access keywords in class/struct declarations
should be acceptable. The behavior of the check correctly reflects the
comment.

I signed it!


Update precision to support bootstrap

Per http://stackoverflow.com/questions/23971428/twitter-bootstrap-3-button-1px-too-small , the precision for this must be at least 10 in order to render bootstrap correctly. In lieu of making this a configurable value of some sort, just set it to 10. It should not have a performance impact, that I can see.

Tests may need to be updated so as to not fail with new precision... I'm not well versed in the testing side of these things, though...

+1
I have the same issue, and yes, sometimes we need to be precise with the complete set of numbers for certain grid systems. As Kevin mentioned, in order to render bootstrap correctly, we need this to be set at 10.

For sass compatibility, we have to leave this at 5.
Can you instead modify bin/pscss to take a command line option, e.g., -p=precision, and if set then call $scss->setNumberPrecision($opts["p"]) ?


💡[FEATURE]: Predicting Real Estate Prices Using Deep Learning

Is your feature request related to a problem? Please describe.
Use deep learning to predict real estate prices based on historical data, economic indicators, and property features.
Describe the solution you'd like
Key Techniques:
CNN for image data (property photos)
LSTM for time series data
Feature Engineering
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@Akshat111111 pls assign it me I'm gssoc'24 contributor


How do I create a trap with a custom message from a NewFunc?

Adjusting the example of #57, I found that if I create a trap like this:
package main

import (
	"runtime"

	"github.com/bytecodealliance/wasmtime-go"
)

func main() {
	bs, err := wasmtime.Wat2Wasm(`
	(module
	  (import "" "hello" (func $hello))
	  (func (export "run")
		(call $hello))
	)
  `)
	check(err)

	for {
		store := wasmtime.NewStore(wasmtime.NewEngine())
		f := wasmtime.NewFunc(store, wasmtime.NewFuncType(nil, nil),
			func(*wasmtime.Caller, []wasmtime.Val) ([]wasmtime.Val, *wasmtime.Trap) {
				return nil, wasmtime.NewTrap(store, "trap")
			})
		imports := []*wasmtime.Extern{f.AsExtern()}
		module, err := wasmtime.NewModule(store.Engine, bs)
		check(err)

		_, err = wasmtime.NewInstance(store, module, imports)
		check(err)

		runtime.GC()
	}
}

func check(e error) {
	if e != nil {
		panic(e)
	}
}

we'll end up leaking memory because the store is closed over in NewFunc (I think). The same isn't the case when changing the crucial bits to this,
		store := wasmtime.NewStore(wasmtime.NewEngine())
		t := wasmtime.NewTrap(store, "trap")
		f := wasmtime.NewFunc(store, wasmtime.NewFuncType(nil, nil),
			func(*wasmtime.Caller, []wasmtime.Val) ([]wasmtime.Val, *wasmtime.Trap) {
				return nil, t
			})

...but then I don't see a way to adjust the trap's message. Is that how traps were intended to be used -- having a static message, and requiring some other means to convey extra information? (Which means would that be, typically?)
Thanks for your time! 😃

💭 I guess there could be an exported method in our Wasm module, "trap_reason()", returning either 0 or a pointer to a string explaining what happened. Inside the module, this would amount to setting some global when an error has happened.

Ah this is indeed unfortunate! I think there may not be a great way to do this right now unless you want to create the trap up-front instead of afterwards (but that's pretty funky).

Thanks for confirming!

unless you want to create the trap up-front instead of afterwards (but that's pretty funky).

Yeah I've thought about that, but for concrete use cases, it' would be nicer to have "file-such-and-such:10 conflict in obj blah" than "conflict", and the latter is the only one I think we could create upfront. 😬

Recently I've been thinking about Wasmtime's APIs, and this is definitely something I'd like to getting to fix. I've posted a proposal for changing APIs and this issue will be fixed as a side-effect of that.

Ok this was fixed in https://github.com/bytecodealliance/wasmtime-go/pull/81 where creating a trap no longer requires a store.


The plots in the paper

Hi, first of all thank you for this great work, and for providing the implementation.
I really liked the plots in the paper, and was wandering what package / setting was used to make them.
Please feel free to close this issue if this is not the right place to ask such questions.
Thanks.

We used matplotlib primitives plot for the lines and fill_between for the intervals (using alpha to make it transparent).


adapted opcua library to 0.2 open62541 and enabled the call service

also implemented translateBrowsePathsToNodeIDs as this is needed for UAExpert to correcty determine methodNodes arguments. This latter implementation is only roughly tested and does probably contain bugs.
In the future, the source for the services browse and translateBrowsePathsToNodeIDs should be consolidated as there is much overlap.

travis fails in opcuafb
this is because the client functionblocks use the old open62541-API. trying to work around that with old open62541.c and .h in the project dir

nope, that's just to get rid of excess data at the end of a message