All tasks are executed in parallel although they should run in sequence

the watch:
  gulp.watch(paths.index, {debounceDelay: 1000}, function (cb) {
    runSequence('index', 'injectFilters', 'injectStyles', 'injectModels', 'injectDirectivesCoffee', 'injectVCSCoffee', 'injectServices', 'wiredep', cb);
  });

the log:
[15:02:18] Starting 'index'...
[15:02:18] Starting 'injectFilters'...
[15:02:18] Starting 'injectStyles'...
[15:02:18] Starting 'injectModels'...
[15:02:18] Starting 'injectDirectivesCoffee'...
[15:02:18] Starting 'injectVCSCoffee'...
[15:02:18] Starting 'injectServices'...
[15:02:18] Starting 'wiredep'...
[15:02:18] gulp-inject Nothing to inject into index.html.
[15:02:18] gulp-inject 1 files into index.html.
[15:02:18] gulp-inject 1 files into index.html.
[15:02:18] gulp-inject Nothing to inject into index.html.
[15:02:18] gulp-inject 2 files into index.html.
[15:02:18] gulp-inject 5 files into index.html.
[15:02:18] Finished 'wiredep' after 46 ms
[15:02:18] Finished 'injectFilters' after 67 ms
HTML changed: www/index.html
[15:02:18] Finished 'injectStyles' after 65 ms
[15:02:18] Finished 'injectModels' after 62 ms
[15:02:18] Finished 'injectDirectivesCoffee' after 59 ms
[15:02:18] Finished 'injectServices' after 50 ms
[15:02:18] Finished 'index' after 72 ms
[15:02:18] Finished 'injectVCSCoffee' after 56 ms

tasks:
gulp.task('index', function () {
  return gulp.src(paths.index)
    .pipe(debug())
    .pipe(haml().on('error', gutil.log))
    .pipe(gulp.dest(dests.main));
});

gulp.task('injectFilters', function () {
  return gulp.src(dests.index)
    .pipe(inject(
      gulp.src(dests.filters + ext('js'), {read: false}).pipe(uniqueFiles()),
      {name: 'filters', ignorePath: 'www'})
    )
    .pipe(gulp.dest(dests.main));
});

gulp.task('injectStyles', function () {
  return gulp.src(dests.index)
    .pipe(inject(
      gulp.src(dests.styles + ext('css'), {read: false}).pipe(uniqueFiles()),
      {name: 'styles', ignorePath: 'www'})
    )
    .pipe(gulp.dest(dests.main));
});

gulp.task('injectModels', function () {
  return gulp.src(dests.index)
    .pipe(inject(
      gulp.src(dests.models + ext('js'), {read: false}).pipe(uniqueFiles()),
      {name: 'models', ignorePath: 'www'})
    )
    .pipe(gulp.dest(dests.main));
});

I don't see anything wrong.  Are you sure the code above is what you typed in?  If you passed in an array of tasks, they run in parallel.

I'm going to close this as I haven't heard back from you.  Please re-open it if you have new information.


Tensorflow 1.5.0 manylinux binary requires Numpy 1.14.1

On Travis-CI using Python 3.6 Numpy 1.13.2 is installed. Trying to use the tensorflow manylinux binary from PyPi will result in:
RuntimeError: module compiled against API version 0xc but this version of numpy is 0xb

A log from a broken build is here:
https://travis-ci.org/TwentyBN/ionn/jobs/344881411
Fixing the .travis.yml like so:
https://github.com/TwentyBN/ionn/commit/24ced51bb26d78aa5fed265ed9196f47da4d7d6d
Produces a green build like here:
https://travis-ci.org/TwentyBN/ionn/jobs/346796560
Reading the build log, Numpy is updated like so:
$ pip install -U numpy
Collecting numpy
  Downloading numpy-1.14.1-cp36-cp36m-manylinux1_x86_64.whl (12.2MB)
    100% |████████████████████████████████| 12.2MB 57kB/s
Installing collected packages: numpy
  Found existing installation: numpy 1.13.3
    Uninstalling numpy-1.13.3:
      Successfully uninstalled numpy-1.13.3
Successfully installed numpy-1.14.1

Please set the minimum version for Tensorflow 1.5.0 on Python 3.6 to Numpy 1.14.1. Thanks!

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Have I written custom code : no
OS Platform and Distribution : Linux - Travis-CI - Trusty
TensorFlow installed from : PyPi
TensorFlow version: 1.5.0 (Python 3.6)
Bazel version : N/A
CUDA/cuDNN version : N/A
GPU model and memory : N/A
Exact command to reproduce : N/A

Nagging Assignee @bignamehyp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I'm not sure we are officially support travis-CI. So what's the current minimum version for Tensorflow 1.5.0 on Python 3.6?

1.14.1

@yifeif  can you please take a look? Thanks

Nagging Assignee @bignamehyp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Thanks for reporting @esc. Sorry missed this one. From TF 1.6+, we have updated the numpy dependency to >=1.13.3. Closing this.


依赖包找不到，求大神指导！！！！！！！！！

compile group: 'javax.servlet', name:'javax.servlet-api', version:'3.1.0'
compile group: 'nl.flotsam', name:'xeger', version:'1.0.0-SNAPSHOT'
compile group: 'com.alibaba', name:'buc.sso.common', version:'0.4.4'
compile group: 'com.alibaba', name:'buc.sso.client', version:'0.3.9'

Sorry, but I don't speak Chinese - could you explain your problem in English?
Google Translate says you have some dependency resolution issues: did you try installing this library into your local Maven repository by using mvn install, and then using it from your Gradle build?

I don't find the dependency(xeger),but now I find the source code.
I don't find  dependencies(buc.sso.common, buc.sso.client),  can you help me?

Those are Alibaba libraries, which are not related to this project. I am afraid you will have to look elsewhere for them.

Closing as unrelated.


Consider the location implementation

I'm not sure we need the global loc var as the scheduler itself stores location and the scheduler runs jobs.
Is there a need to have jobs have a separate location? Would someone ever run a scheduler in say UTC and then want to trigger a job at say 10:00AM UTC +2?
To solve this you could create multiple schedulers for the different time zones.

I agree... We should consider timezones by schedulers only. Time no clean up this codebase :) I'm preparing another PR soon


zencoder: set progress to 100 when job status is finished (fixes #170)

Current coverage is 84.88% (diff: 100%)

Merging #171 into master will increase coverage by 0.01%

@@             master       #171   diff @@
==========================================
  Files            28         28
  Lines          1963       1965     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1666       1668     +2
  Misses          195        195
  Partials        102        102

Powered by Codecov. Last update c0d1580...c60a8f3


Refactoring code for modern react techniques

I am working at this code as well and thought it would be helpful to share

Merged to dev branch for testing, looks good otherwise!! Thanks, this improves code readability and keeps up to the standard!

This will not be merged to master right now, it has breaking changes as I see it right now, not drop in replacement. Will look into it more later!

@fernando-RA Hi Fernando! Sorry for not looking into this earlier, it's been a hectic spring and summer for us. We are currently looking into refactoring our library to be component based and have been looking at this PR as inspiration for some parts.
The changes you proposed with this PR did not work for us, but we have been able to get a modified version working! 😄 However, there are still some parts of the code that crashes, sometimes when prevProps from your hook usePrevious is used. You mentioned that you were also working on the code, have you been able to get everything to work? Could you share your results with us, or take a look at the code on the next branch?


Remove obsolete TOML code

This PR aims to remove obsolete TOML related code and also resolve incompatibilities with the latest lightning device versions.

The verifier is relaxed to only test agreement of basic gates (no adjoint/control) between the toml and python device spec.

This is needed to resolve the overlapping gate issue introduced by https://github.com/PennyLaneAI/pennylane-lightning/pull/743

and also allows removing the patch for Lightning Kokkos that exists solely to satisfy the verifier.

The obsolete toml files in the catalyst repo for lightning devices is also removed.

MCMs are marked as un-invertible and un-controllable, since they are non-unitary.

Requires: https://github.com/PennyLaneAI/pennylane-lightning/pull/758
[sc-65114]
[sc-#####]

The current development version of Lightning-Kokkos does not pass the runtime tests:
catalyst/runtime/tests/Test_LightningMeasures.cpp:1386: FAILED: due to unexpected exception with message:
  [catalyst/runtime/lib/backend/lightning/lightning_kokkos/LightningKokkosSimulator.cpp][Line:303][Function:PartialProbs]
  Error in Catalyst Runtime: Invalid size for the pre-allocated partial-probabilities


Upgrade flutter_bugfender to 3.0.0

We should upgrade the flutter_bugfender dependency. The updated library includes updated iOS SDK which removes bitcode from builds. When building with XCode 16 builds with bitcode cannot be uploaded to the AppStore.
There is a workaround for that (https://medium.com/@abdulahad2024/fixing-bitcode-issues-in-xcode-16-how-to-resolve-invalid-executable-errors-when-uploading-ios-da07a5a39c7c), but it's better to rely on the updated version.

The dependency got upgraded in https://github.com/leancodepl/logging_bugfender/pull/13


Can

I add flutter_picker to pubspec.yaml and  flutter packages get, I got the following error:
Running "flutter packages get" in anicare...
Could not find a file named "pubspec.yaml" in git://github.com/yangyxd/flutter_picker.git 5e24669acaf18fb4073856f22527191a0ef69288.
pub get failed (1)

Try adding the dependency in pubspec.yml the formal way:
dependencies:
  flutter_picker: ^1.0.10


[marketing] homepage updates

Just throwing something up to facilitate high-level discussion. There's obvious polish that will be needed, but just trying to figure out a high-level direction first
Resurrection of the work I started last year in https://github.com/sveltejs/sites/pull/72
Incorporating Figma design from @vedam: https://www.figma.com/file/f87psJnCeqMbUPAQABmCrN/svelte?node-id=0%3A1

Oh that's a very neat looking improvement!

This is a great addition to the website! Good work!

Yeah, my plan was to put the video elsewhere once the content is finalized. I just put it here temporarily for ease of development and sharing

I like the changes, I know it's a not related to this PR but is there a plan to add some dope dark theme support for the official website and documentation? I'm sure that will have great unsubconsious positive impact , especially for new developers

No plans at the moment. I like dark theme, but it's a big change to make sure all of our assets display well on light and dark

closing as the homepage has been updated


unhandled exception when services are removed

Seems like a small bug -
DeviceEventEmitter.addListener('RNZeroconfRemove', service => {
if (!service || !service.name) { return }
const { name } = service
  delete this.services[name]  <--- this should be _services

  this.emit('remove', name)
  this.emit('update')
})

Thanks, sorry about that, this should not have happened.

The fix is now available on npm as the 0.3.1 release


There should be an option to prevent screen suspension

It may be desirable to prevent the screen from suspending. For example, if a replay is being watched or if a long break is entered.
Should be provided at a GameHost level as a BindableBool, which is referenced in both iOS and Android projects.

Merged. :)

If you use Closes #issuenumber in your PRs it will automatically close the issues, for what it's worth.
Also this function isn't yet implemented osu!-side, we may want to look at that.


Scrolling does not work when zoomOnScroll=false

Describe the Bug
I'm facing an issue when trying to scroll a page, if the mouse position is over ReactFlow, the scroll does not work. ReactFlow has the zoomOnScroll={ false } property.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Create react-flow component
Put it in the scrollable container
Set zoomOnScroll property to false
Try to scroll the page over react-flow component
Scrolling does not work

Expected behavior
Scrolling should work when zoomOnScroll={ false }
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 119.0.6045.159

Additional context
No response

This is not a bug but the expected behavior.
To allow for scrolling, you need to use the preventScrolling prop and set it to false, that way you can scroll the container again without ReactFlow catching the events and blocking the page scroll.

Thanks a lot, @bcakmakoglu! Didn't notice this property.


SSIV for a game board + animated pieces

I wonder if a extended version of this would work for displaying a boardgame with game pieces on it (that may be moved and "animated" in the opposing players turn). Have this feeling that trying to invalidate a full-screen imageview 30-60 times a second wouldn't work out all that well, but the animation demo suggests that it should be possible to run it that way. Any thoughts on this?

It's worth trying, but my experience has been that the view with no overlays drawn on top performs very well, and once you start adding overlays it takes a lot longer to render. I never worked out why.

I already have a DIY view component based on SurfaceView (though I'll not take credit for it - much is inspired by WorldMap), but I'm impressed with how smooth you managed to make this ImageView work which is why I'm thinking of looking into this (Good job, btw). I do worry what the fps will be like with overlay draws - will have to find some time for experimentation. Thanks for the feedback.


code uses all available ram memory and blocks computer

VSCode Version:  code --version
1.41.0
9579eda04fdb3a9bba2750f15193e5fafe16b959
x64

OS Version:
System:    Host: ms Kernel: 4.15.0-54-generic x86_64 bits: 64 compiler: gcc v: 7.4.0
Desktop: Cinnamon 4.2.4 wm: muffin dm: LightDM Distro: Linux Mint 19.2 Tina
base: Ubuntu 18.04 bionic

Steps to Reproduce:
Happens when I run ng serve.
ng --version
Your global Angular CLI version (8.3.3) is greater than your local
version (8.1.0). The local Angular CLI version is used.
node --version
v10.16.3

Does this issue occur when all extensions are disabled?: Not sure
code --list-extensions
Angular.ng-template
chrmarti.regex
dbaeumer.vscode-eslint
eamodio.gitlens
esbenp.prettier-vscode
ghaschel.vscode-angular-html
johnpapa.vscode-peacock
mhutchie.git-graph
ms-vscode.sublime-keybindings
ms-vscode.vscode-typescript-tslint-plugin
msjsdiag.debugger-for-chrome
quicktype.quicktype
rbbit.typescript-hero
streetsidesoftware.code-spell-checker
wayou.vscode-todo-highlight

@zeljkoantich can you please provide more information about why Code is involved into this. You say to reproduce run ng serve.
And can you please provide the information from Help > Open Process Explorer so that we can see what process might cause this?

I was using VSCode, ng-serve and on a separate monitor I was monitoring system process.
So I was working and computer froze, then I saw that code process was listed on top of System Monitor, taking more than 5 GB of RAM. Unfortunately I don't have that screenshot.
I downgraded VSCode to previous version now, and will let you know if the problem reappears:
code --version
1.40.2
f359dd69833dd8800b54d458f6d37ab7c78df520
x64

Also I was not using integrated terminal to run ng-serve, I was using terminator terminal emulator.

@zeljkoantich if you can reproduce it please provide the output from Help > Open Process Explorer. This helps us to identify the code process that causes this.

I tried to repoduce but without any sucess. So I will close this issue.
I will reopen this issue if the problem reappears and If I can collect all necessary data.

It happened again.
code --version
1.41.0-1576089540
Full crash report
I have updated to version: 1.41.1-1576681836

This time with code --version
1.40.2
f359dd69833dd8800b54d458f6d37ab7c78df520
x64
Process ID 2630, electron_node tsserver.js

Looks more like a TypeScript problem.

Almost certainly a duplicate of https://github.com/microsoft/vscode/issues/86707


deme

issue 1
issue 2

    let i = String::new("hello");

ref #60

https://github.com/trustnote/rust-trustnote/commit/ebd774e43ae01adf4b52d6f90489fafca08592b0
this is where the feature added


hackage-db 2.0

hackage-db-2.0 (Peter Simons<EMAIL_ADDRESS>@peti) is out of bounds for:

[ ] cabal2nix-2.5 (< 2). Peter Simons<EMAIL_ADDRESS>@peti. @nixos. Used by: library, executable, test-suite

Fixed by http://hackage.haskell.org/package/cabal2nix-2.6.

It seems not
hackage-db-1.22 (Peter Simons<EMAIL_ADDRESS>@peti) is out of bounds for:

[ ] cabal2nix-2.6 (>2). Peter Simons<EMAIL_ADDRESS>@peti. @nixos. Used by: library, executable, test-suite

@juhp, I don't understand why now both cabal2nix and hackage-db are restricted to older versions. Shouldn't Nightly use the latest version of both of them?

Hmm, let me check I thought there was reason but maybe I was tired

Thanks @peti for pointing that out - should be in the next Nightly


Add Java package smoketest

Description
Adds smoke test to verify the built jar works.
Also updates lombok and graddle

General Checklist

[ ] Tests added for this feature/bug
if it was a bug, test must cover it.
[ ] Conform by the style guides, by using formatter
[ ] Documentation updated
[ ] (optional) Please add a label to your PR

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 82.531%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4739

Relevant Lines:
5594

💛  - Coveralls


dnsmasq role is not run on CoreOS

For an unknown reason, the role dnsmasq which creates a daemonSet is not included when running a deployment on CoreOS.

Running a second deployment works, i've to figure out the problem


Apply the date histogram rewrite optimization to range aggregation

Description
Background
Previously we optimized date histogram aggregation by utilizing the index structure of date field — BKD tree/Points to provide the documents count of date histogram buckets results. We first build date ranges from the date histogram query input like daily interval histogram. Then we "query" the index of date for how many documents are in these date ranges.
Idea
Date is actually saved as numeric data of long data type. This leads to the idea that we can extend the optimization to the RangeAggregator which also perform ranges aggregation on numeric data.
Implementation
The core optimization algorithm remains the same. (Details #13317)
Note the algorithm has a hidden pre-condition: all the ranges are not overlapping (because date interval cannot produce overlapping date ranges)
Another difference is that range aggregation buildRange method won't be built from segment level match all path. The ranges are provided by user directly, not like date histogram needs to check the boundaries of shard or segment or accommodate top level range query. (Details #12073)
Changes

Covering all numeric types
buildRanges method now return a generic Ranges type instead of long[]
The ranges built now will be same as what provided by customer, meaning it's lower inclusive, upper exclusive. The multi range traversal logic is refactored to fit that. The refactor also include some readability improvements.
tryFastFilterAggregation common logic is extracted, and AggregationType should implement its own special logic.

Possible Follow Ups

Geo distance range query
Overlapping ranges
We notice scaled float doesn't seem to belong in the module, as it's not experimental anymore. So better to just move it along with NumberType in the server.
Currently the rewrite helper class is becoming huge, also the workflow to do the optimization (isRewriteable, buildRanges, tryxxxRewrite...) needs refactor. Tracking task

Benchmarks

New operations added into noaa and big5 workloads: https://github.com/opensearch-project/opensearch-benchmark-workloads/pull/310
Confirmed no obvious regression on date histogram optimization. Only on pmc workload I'm saying consistently slower performance

|                                                        Metric |                          Task |    Baseline |   Contender |     Diff |   Unit |
|                                       50th percentile latency | articles_monthly_agg_uncached |      7.2067 |     9.99465 |  2.78795 |     ms |
|                                       90th percentile latency | articles_monthly_agg_uncached |      7.9746 |     11.4022 |  3.42756 |     ms |
|                                       99th percentile latency | articles_monthly_agg_uncached |      12.822 |     16.0743 |  3.25229 |     ms |
|                                      100th percentile latency | articles_monthly_agg_uncached |     24.4897 |      36.373 |  11.8833 |     ms |

However, considering this is already ~10ms. We can look into the reason later as a follow up. For the other workloads, big5, nyc, http, they are all even faster.

Performance gain on the range aggregation.
big5

|                                                        Metric |                          Task |    Baseline |   Contender |     Diff |   Unit |
|                                       50th percentile latency | range-agg-1 | 1.23376e+06 |     4.74459 | -1.23376e+06 |     ms |
|                                       90th percentile latency | range-agg-1 | 1.42868e+06 |     5.14212 | -1.42867e+06 |     ms |
|                                       99th percentile latency | range-agg-1 | 1.47254e+06 |     5.32877 | -1.47253e+06 |     ms |
|                                      100th percentile latency | range-agg-1 | 1.47741e+06 |     5.58408 |  -1.4774e+06 |     ms |
|                                  50th percentile service time | range-agg-1 |     5420.99 |     3.49232 |      -5417.5 |     ms |
|                                  90th percentile service time | range-agg-1 |     5433.47 |     3.63754 |     -5429.83 |     ms |
|                                  99th percentile service time | range-agg-1 |     5440.81 |     3.73967 |     -5437.07 |     ms |
|                                 100th percentile service time | range-agg-1 |     5443.22 |     4.11546 |      -5439.1 |     ms |
|                                                    error rate | range-agg-1 |           0 |           0 |            0 |      % |

|                                       50th percentile latency | range-agg-2 | 1.20783e+06 |     6.01016 | -1.20782e+06 |     ms |
|                                       90th percentile latency | range-agg-2 | 1.39873e+06 |     6.42305 | -1.39872e+06 |     ms |
|                                       99th percentile latency | range-agg-2 | 1.44164e+06 |     6.69281 | -1.44163e+06 |     ms |
|                                      100th percentile latency | range-agg-2 | 1.44642e+06 |     6.69403 | -1.44641e+06 |     ms |
|                                  50th percentile service time | range-agg-2 |     5317.48 |     4.86202 |     -5312.62 |     ms |
|                                  90th percentile service time | range-agg-2 |     5333.16 |     4.94407 |     -5328.21 |     ms |
|                                  99th percentile service time | range-agg-2 |     5367.61 |     5.09159 |     -5362.52 |     ms |
|                                 100th percentile service time | range-agg-2 |     5417.87 |     5.11181 |     -5412.76 |     ms |
|                                                    error rate | range-agg-2 |           0 |           0 |            0 |      % |

noaa
|                                       50th percentile latency | range-aggregation |     1484.37 |     10.8027 | -1473.56 |     ms |
|                                       90th percentile latency | range-aggregation |     1489.36 |     11.3409 | -1478.02 |     ms |
|                                      100th percentile latency | range-aggregation |     1493.02 |     14.9022 | -1478.12 |     ms |
|                                  50th percentile service time | range-aggregation |     1481.79 |     6.98101 | -1474.81 |     ms |
|                                  90th percentile service time | range-aggregation |     1486.58 |     7.40678 | -1479.17 |     ms |
|                                 100th percentile service time | range-aggregation |     1490.47 |      10.768 |  -1479.7 |     ms |
|                                                    error rate | range-aggregation |           0 |           0 |        0 |      % |

Related Issues
Resolves #13531

Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[x] New functionality has javadoc added

[ ] API changes companion pull request created.
[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Seems the code coverage upload failed
https://github.com/opensearch-project/OpenSearch/actions/runs/9353214333/job/25743216901
Want to check if we can just retry the upload without rerun the gradle check.

❌ Gradle check result for 9c1ea13: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

#13968

@github-actions commented on Jun 13, 2024, 7:22 PM PDT:

❌ Gradle check result for fe85ad3: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/12788#issuecomment-2168174168

@github-actions commented on Jun 14, 2024, 8:06 AM PDT:

:x: Gradle check result for fe85ad3a366c0f5f62827df6f58e4db8542ec40d: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
Originally posted by @github-actions[bot] in https://github.com/opensearch-project/OpenSearch/issues/13865#issuecomment-2168235668

https://github.com/opensearch-project/OpenSearch/issues/14263#issuecomment-2168342461

@github-actions commented on Jun 18, 2024, 3:53 PM PDT:

:x: Gradle check result for cb8cbbfbae3b9bab5e107b32d43a5ca289feb007: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
Originally posted by @github-actions[bot] in https://github.com/opensearch-project/OpenSearch/issues/13865#issuecomment-2177217043

https://github.com/opensearch-project/OpenSearch/issues/9589#issuecomment-2177254086
#13828

@github-actions commented on Jun 18, 2024, 11:17 PM PDT:

:x: Gradle check result for 07a52936fbf36282079b08c96a58ffefa3baa33f: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
Originally posted by @github-actions[bot] in https://github.com/opensearch-project/OpenSearch/issues/13865#issuecomment-2177835661

#14292

@bowenlan-amzn Maybe a test failure here related to this change: https://build.ci.opensearch.org/job/gradle-check/41411/consoleText
./gradlew ':rest-api-spec:yamlRestTest' --tests "org.opensearch.test.rest.ClientYamlTestSuiteIT" -Dtests.method="test {p0=search.aggregation/40_range/Double range profiler shows filter rewrite info}" -Dtests.seed=2F3C46DA8CEB59E9 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=hu-HU -Dtests.timezone=America/Montreal -Druntime.java=21

That will reproduce for me, though not every time


[C API] macos arm64 platform not support

require macos arm64 platform dynamic library

Hello @wgx954418992, this issue is already being tracked at #186. Closing as a duplicate.


Docs/update theme

Updated docs theme to sphinx_book_theme~=1.0.1
Also done the same for the manual.
Theres some CI nastiness as I had to change the base branch to develop from main. Let me know if you want me to just make a fresh PR.

@sjdilkes what do you think I should do about the 0.4.0 commit?

@sjdilkes what do you think I should do about the 0.4.0 commit?

I believe @daniel-mills-cqc is going to take a look at https://github.com/CQCL/Qermit/pull/81 and fix the issues. I think we're good to leave this PR open for now and pick it up again once that fix is made.

You should be able to continue working on this now that https://github.com/CQCL/Qermit/pull/82 is in. Rebasing on develop should get the tests passing.
https://github.com/CQCL/Qermit/pull/89 is also relevant but doesn't need to go in first.
A couple of things:

Would it be possible to clear up the git history a little, just to clarify what has changed?
Have these changes also been applied to the manual or just the docs?

Giving that this docs theme change is a 5-10 minute job - would it be alright to just make a fresh PR (branching off develop) making this change rather than trying to tidy up this messy PR?


newer constellation doesn't work with the 7nodes example

I'm trying to figure out how to run the 7nodes example with a new constellation release 0.1.0 and it seems that the existing configuration files break the example, as well as my best guess at changing the config files to the new format.
With the existing config files, the node crashes with an error message like
"encrypt: Sender cannot be a recipient", and with the new ones I get something like
Errors while running sendPayload: [Left "Unknown recipient\nCallStack (from HasCallStack):\n  error, called at ./Constellation/Node.hs:157:21 in constellation-<IP_ADDRESS>-6e8lqFuBPtzCz3iEft1Zk0:Constellation.Node"]

here's what I'm using for the config file for node 1 for example
url = "http://<IP_ADDRESS>:9001/"
port = 9001
socket = "qdata/tm1.ipc"
othernodes = []
publickeys = ["keys/tm1.pub"]
privatekeys = ["keys/tm1.key"]
alwayssendto = []
storage = "qdata/constellation1"
verbosity = 3

I'm not really sure what I'm doing wrong, any comments would help.

I can't reproduce this. Works as expected with both the new and old configuration format.
Could you provide a reproducible example?

@RaziAbbas Please test the latest updates as we introduced a few fixes.


Support for PostgreSQL

What about support for Postgres? Any hints are welcomed and I will do the customization.

I believe there are some issues using PostgreSQL with Talend.  Specifically, there are additional features like Kibana and some of the error reporting that assume MySQL exists and creates the relevant tables, ect..  I was never able to successfully get it working in PostgreSQL, only MySQL.  That being said, the instructions should be similar with the changes being changing credentials where needed and adding the additional PostgreSQL jar for connections.


Nuxt instance unavailable on all pages

Environment

Operating System: Darwin
Node Version:     v16.14.0
Nuxt Version:     2.15.8
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      modules, buildModules, dev, build, css, meta, app, runtimeConfig
Runtime Modules<EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS>~/modules/pages

Reproduction
Start dev environment via yarn dev
Describe the bug
On every page I get the error
nuxt instance unavailable

  at useNuxtApp (./.nuxt/dist/server/server.mjs:587:13)
  at Module.useRuntimeConfig (./.nuxt/dist/server/server.mjs:595:10)
  at $id_bbf8dc5e (./.nuxt/dist/server/server.mjs:41284:38)
  at async __instantiateModule__ (./.nuxt/dist/server/server.mjs:42697:3)

Additional context
I use useNuxtApp in app.vue
./app.vue
const nuxtApp = useNuxtApp()

nuxtApp.hook('page:finish', () => {
    window.scrollTo(0, 0)
})

Logs
No response

useNuxtApp() and useRuntimeConfig() can currently be defined freely outside of the setup function, making it difficult to notice errors.
Due to this error, accidents have occurred in my team.
In the future, it would be desirable to be able to detect such errors with Nuxt-specific ESLint or similar tools.

Can we run `useRuntimeConfig` in `useAsyncData`, since I also got the error `nuxt instance unavailable`

You should run it outside of useAsyncData and use the configuration within it.


Lightspeed Service to prevent users from submitting invali

This PR contains the VSCode changes in support of https://github.com/ansible/ansible-ai-connect-service/pull/1286

codecov/patch coverage is misleading:-
src/features/lightspeed/api.ts#L148
Added line #L148 was not covered by tests

Formatting change.
src/features/lightspeed/errors.ts#L94-L98
Added lines #L94 - L98 were not covered by tests

https://github.com/ansible/vscode-ansible/pull/1528/files#diff-8a6d69931c7dbe81d0aabfeb890b06da1517559d995c004c9af9d17ce2e11232R106-R118
src/features/lightspeed/errors.ts#L100-L101
Added lines #L100 - L101 were not covered by tests

Formatting changes.


Add support for flagging redemptionperiod domain status

Overview
Snippet of the metadata included in a recent domain expiration notification:

Status: clienttransferprohibited, redemptionperiod
Creation Date: 2009-05-15 14:18:25 +0000 UTC
Updated Date: 2024-06-27 22:50:42 +0000 UTC
Expiration Date: 2024-05-15 14:18:25 +0000 UTC

The redemptionperiod status should be flagged regardless of the expiration date and should probably be considered a CRITICAL state.
Per domain.com:

When your domain is in Redemption status, you may still redeem the domain by paying a redemption fee in addition to the normal domain renewal rate. The redemption fee may be up to USD 160.00, depending on your registrar.

References

https://www.domain.com/help/article/what-is-domain-redemption
https://www.domain.com/help/article/domain-registration-the-life-cycle-of-a-domain
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Additional states to flag (worth tracking separately via dedicated GH issues):

pendingDelete
pendingRestore
pendingTransfer
serverHold
transferPeriod
clientHold

When a domain is locked (e.g., GoDaddy), these states are commonly seen:

clientDeleteProhibited
clientRenewProhibited
clientTransferProhibited
clientUpdateProhibited

It's probably worth looking for those specific states and barring any known problem states, explicitly label the domain as locked as a FYI item.

Additional status to watch for:

autoRenewPeriod

This grace period is provided after a domain name registration period expires and is extended (renewed) automatically by the registry. If the registrar deletes the domain name during this period, the registry provides a credit to the registrar for the cost of the renewal.

refs: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

From https://opensrs.com/blog/what-do-domain-status-codes-mean/:

You can view a domain’s status codes by doing a Whois lookup on the domain and looking for the “Domain Status” fields. Status codes set by the Registrar begin with “client.” All other status codes are set by the registry.


Undefined index: dh

I'm using 2.2 version of your extension.
If I browsed the image in my form and click on save button without clicking on crop button, I got this error Undefined index: dh,
There should be some kind of handler , if crop button not clicked, then upload only image don't create thumbnail or create thumbnail of original image.
Thank you.

You need check at uploading file. If image not exists then why it need saving?

Hi
Image exist but I tried to save image without click on Crop button and got this error.

Cropping is required.

Sometime if some one don't want to crop the image :)

@shahzadthathal Then check crop info field at information about crop. If

okay Thanks :+1:

why Setting unknown property: bupy7\cropbox\Cropbox::optionsCropbox?

write me version of cropbox
—
С ув., Василий.
14 янв. 2016 г., в 20:11, 小酒酒<EMAIL_ADDRESS>написал(а):

why Setting unknown property: bupy7\cropbox\Cropbox::optionsCropbox?
—
Reply to this email directly or view it on GitHub.

"bupy7/yii2-widget-cropbox": "*",

{
"name": "bupy7/yii2-widget-cropbox",
"description": "This is widget wrapper of https://github.com/bupy7/jquery-cropbox. This widget allows crop image before upload to server and send informations about crop in JSON format.",
"keywords": ["yii2", "extension", "widget", "crop image", "image"],
"homepage": "https://github.com/bupy7/yii2-widget-cropbox",
"version": "4.0.0",
"type": "yii2-extension",
"license": "BSD 3-Clause",
"authors": [
{
"name": "Vasilij Belosludcev",
"email"<EMAIL_ADDRESS>"homepage": "http://mihaly4.ru"
}
],
"minimum-stability": "stable",
"require": {
"yiisoft/yii2-bootstrap": "",
"bower-asset/jq-cropbox": "1.0."
},
"autoload": {
"psr-4": {
"bupy7\cropbox\": ""
}
}
}

4 version different between 3 version. You need rewrite configuration in call widget or use 3 version.
—
С ув., Василий.
14 янв. 2016 г., в 20:11, 小酒酒<EMAIL_ADDRESS>написал(а):

why Setting unknown property: bupy7\cropbox\Cropbox::optionsCropbox?
—
Reply to this email directly or view it on GitHub.

谢谢！

When I save the message 'File D:\xampp\tmp\php95FA.tmp doesn't exist', please help.

@tedyonly check availability enctype to your a form
$form = ActiveForm::begin([
    'options' => ['enctype'=>'multipart/form-data'],
]);


Plugins

Are plugins or server software that utilise Serialisation at risk? What specific versions of Minecraft and/or java are affected?
These things are not specified in the README.md

Are plugins or server software that utilise Serialisation at risk?

Uhh, technically yes? Everything that uses serialization in a networking context could be at risk, lots of popular software fell for that trap in the past. But to give a more serious/accurate answer: We're not aware of any and the chances are slim enough to basically answer with a simple "no". But we haven't actually looked at any so don't take my word for it.

What specific versions of Minecraft and/or java are affected?

None. Specific mods for specific versions are affected, but with our current data it's impossible to give an actual range As written here the most affected mods so far are available for mc version 1.7.10 and 1.12.2 but we also found a mod for 1.4.7 that could be exploited in the same way.

I too would like to know if this can affect plugins on server software such as Bukkit/Spigot/Paper/Purpur/etc.
Although it's my understanding that these server software don't alter the networking between the client and server, I'm not 100% sure on that, and there are plugins such as ProtocolLib that I figure could potentially be affected.


Apply changes to Database Encryption API

Applied changes to Database Encryption API.
Kept encryptionKey inside CBLDatabase for returning it back when calling CBLDatabase_Config.
Added a test for testing database encryption.
Fixed EE exported symbol file settings.

Windows test hang is fixed in https://github.com/couchbaselabs/couchbase-lite-C/pull/108.

I have made changes as suggested by the code review. I have also reverted CBLEncryptionAlgorithm to the original which includes kCBLEncryptionNone which helps simplifying CE and EE availability of the functionality as well as some part of the implementation.

@borrrden @snej Can you review this PR again?


fixed single event bug issue 233

-fixed single event bug.

added some functionality to plotting script plot_CCDimage

This fixes issue #233

yes, it is just a very minor bug.


Can I introduce support for LLMs via Amazon Bedrock?

This would allow users/developers to consume it while using Amazon Bedrock calls.

Yes of course!


HDDS-4408: Datanode State Machine Thread needs handle OutOfMemoryError

What changes were proposed in this pull request?
In Tencent internal production environment, we got several dead DNs which can never come back without a restart.

We found that the thread "Datanode State Machine Thread - 0" does not exist in the output of jstack, thus no HeartbeatEndpointTask will be created,  this DN will soon become dead and can not recover unless being restarted.

After checked the .out log, we saw that OOM occurred in thread "Datanode State Machine Thread", which should be responsible for this issue:
300010.579: Total time for which application threads were stopped: 3.0848769 seconds, Stopping threads took: 0.0000943 seconds
Exception in thread "Datanode State Machine Thread - 0" java.lang.OutOfMemoryError: Java heap space
300010.579: Application time: 0.0001554 seconds
300010.580: Total time for which application threads were stopped: 0.0015600 seconds, Stopping threads took: 0.0002747 seconds
300010.581: Application time: 0.0004684 seconds
{Heap before GC invocations=13766 (full 11664):
 PSYoungGen total 3441664K, used 3388416K [0x000000072ab00000, 0x0000000800000000, 0x0000000800000000)
 eden space 3388416K, 100% used [0x000000072ab00000,0x00000007f9800000,0x00000007f9800000)
 from space 53248K, 0% used [0x00000007fcc00000,0x00000007fcc00000,0x0000000800000000)
 to space 53248K, 0% used [0x00000007f9800000,0x00000007f9800000,0x00000007fcc00000)
 ParOldGen total 6990848K, used 6990848K [0x0000000580000000, 0x000000072ab00000, 0x000000072ab00000)
 object space 6990848K, 100% used [0x0000000580000000,0x000000072ab00000,0x000000072ab00000)
 Metaspace used 55150K, capacity 57816K, committed 59224K, reserved 1101824K
 class space used 5922K, capacity 6372K, committed 6744K, reserved 1048576K

The purpose is, we need make this thread lives as long as DN.
BTW, after running DN for more than a week, we see a lot of "java.lang.OutOfMemoryError: GC overhead limit exceeded" in DN's log. Since we configured a dead Recon, we guess this could an evidence for HDDS-4404.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4408
How was this patch tested?
CI

-1, lets analyze the heapdump to understand the root cause of the memory consumption.

@mukul1987 I consider the previous description for this PR/Jira is not properly, I've updated them.
First of all, the key point here is not about OOM. The key point is Datanode State Machine Thread should keep alive during the whole lifetime of Datanode. Without this thread, DN is just a zombie.
Let's talk about the OOM. The root cause for OOM is quite straightforward: as explained in HDDS-4404, we have a dead Recon, the report for Recon is blocked in StateContext, after running for more than 1 week, the DN finally suffers from continually OOM.

@GlenGeng thank you for the patch.
This can be addressed in other ways also

let the datanode die and restart
handle this at recon end. Identify this at recon and get it restarted. Why are other data nodes not exhibiting the same behavior ? it should be same for other data nodes as well eventually.
do not cache reports if the queue exceeds some limit.

Overall this is an unhealthy situation for the whole cluster. How would keeping the datanode state machine thread alive help this situation ? Instead it would keep reporting in heartbeat that data node is healthy.

@prashantpogde

Why are other data nodes not exhibiting the same behavior ? it should be same for other data nodes as well eventually.
You are right. All DNs in our cluster are eventually affected by this OOM issue.

let the datanode die and restart
Agree. Restarting the thread will not help DN to recover to a healthy state, for this OOM issue.
This is just a defensive strategy: there might be other runtime exception like NPE or error that DN is still in a healthy state.

The last patch LGTM + 1.
I will merge it soon since we need this patch in our production environment.
Thanks @GlenGeng  for the contribution,  @mukul1987 @arp7 @prashantpogde for the review and suggestion.


Add files via upload

大佬开源的这个项目很不错，但里面好像没有加Python的依赖文件，给大佬添加了一个，希望可以被Merge进来~

Dear @GT-AcerZhang,
Thanks for your nice words!
There are a few dependencies before PaddlePaddle can be installed on the Jetson Nano.
I've have added them in the README. The website is now updated with Paddle-Lite, PaddlePaddle, PaddleHub and the conversion tools.
The requirement.txt is updated.
Many thanks!


screenB reset TabNavigator, I cann‘t get  the value of the past

const resetAction = NavigationActions.reset({
index: 0,
actions: [
NavigationActions.navigate({routeName: 'ScreenA', params: { foo: 'bar' }})
]
})
this.props.navigation.dispatch(resetAction);
It can  get the value by the way of 'this.props.navigation.state.params.foo'
But ?
if screenA in tab, that is, screenB reset TabNavigator, I cann‘t get  the value of the past

you haven't followed the issue template
duplicate of https://github.com/react-community/react-navigation/issues/2073

MainStackNavigator
ScreenB
TabNavigator
it does not work for me  ScrenB reset TabNavigator by the "The way?"
reset: (props, routeName, paramsValue) => {
console.log(The params--------->${JSON.stringify(paramsValue)});
const resetAction = NavigationActions.reset({
index: 0,
actions: [NavigationActions.init({
routeName: routeName,
params: paramsValue
})]
})
props.navigation.dispatch(resetAction);
}
it‘s wrong
屏幕快照 2017-11-16 下午7.50.11.png

@Mscynol do you solve it？


Esp32 Wroom board

Have you ever tested arduino-dw1000-ng with ESP32 WROOM board? Do you think it can work?
Thank you

Hi @Balabiot, never tested but it should work.
All tested boards are on this wiki page. Probably some users have tested other hardware board without notifying it to us.

I was able to test some functionality via slave select. Did not attempt to use interrupts.
I was able to get the basic msg send and rcv working. But the ranging was not working.


Total energy usage sensor does not update

Does somebody know why the total energy used sensor does not update and stays 0.00 kWh?
Do I need to change the update interval or something?

AFAIK the internal energy consumption counter updates only per x kwh of energy consumed, and also resets on power loss/counter wrap. If you use the AC a lot it should eventually start increasing, but very slow.
It is not a really reliable/precise way of measuring. If you're really looking for a power measurement, you can use volts * current reported as a better rough real-time estimate, or use CT clamps/other energy monitoring solution.

Thanks for clarifying! Ended up making my own sensors with volts (DSMR5 source) * current. Works perfectly.
Only downside is that i have a setup with one outside unit and two inside splits. When I turn on one AC unit, the other draws power as well because they are connected to the same outside unit right? There is no way to tackle this so I can individually monitor the usage?

Thanks for clarifying! Ended up making my own sensors with volts (DSMR5 source) * current. Works perfectly. Only downside is that i have a setup with one outside unit and two inside splits. When I turn on one AC unit, the other draws power as well because they are connected to the same outside unit right? There is no way to tackle this so I can individually monitor the usage?

That's a good question. I'm guessing it is indeed because the energy consumption values are actually coming from the outside unit, not the inside unit (in terms of measurement), same as compressor frequency is the same for both.
You could maybe come up with some creative way, e.g. do some math on the composite value. If one unit on, then consumption = for that unit alone. If both units on, consumption divided by 2. It's still not precise, but at least gives some idea of where the consumption went to (the total is still somewhat precise).

Good options indeed! That's pretty advanced and not super accurate I guess... I'll leave it for now and maybe just make two sensors for both my outdoor units. (I have three indoor units with two outdoor units). Thanks for sharing your ideas!

Thanks for clarifying! Ended up making my own sensors with volts (DSMR5 source) * current. Works perfectly. Only downside is that i have a setup with one outside unit and two inside splits. When I turn on one AC unit, the other draws power as well because they are connected to the same outside unit right? There is no way to tackle this so I can individually monitor the usage?

Can you make a pull request of this code, or share the code so we can include this?

Thanks for clarifying! Ended up making my own sensors with volts (DSMR5 source) * current. Works perfectly. Only downside is that i have a setup with one outside unit and two inside splits. When I turn on one AC unit, the other draws power as well because they are connected to the same outside unit right? There is no way to tackle this so I can individually monitor the usage?

Can you make a pull request of this code, or share the code so we can include this?

It all happens in Home Assistant itself. So no adjustments made on the ESPHome side.
I made a template sensor for each inside unit:
template:     sensor:       - name: 'Stroomverbruik Airco Woonkamer'         unit_of_measurement: W         device_class: power         state_class: measurement         state: "{{ ( states('sensor.voltage_phase_l1') | float * states('sensor.airco_woonkamer_current_power_usage') | float ) | round(0) }}"         availability: "{{ has_value('sensor.voltage_phase_l1') and has_value('sensor.airco_woonkamer_current_power_usage') }}"
Once these are created, I created some helpers. First a couple of Riemann Sum Integral sensors and after that some Utility Meter sensors to collect data over a period of time. I have automated these sensors to reset to 0 after a week or a month for example. Works pretty well!
I'm no programmer or Github expert by any means. I cherry pick some bits and pieces and ask around for some best practices. Normally I just figure it out with some willpower and imagination 😃

AFAIK the internal energy consumption counter updates only per x kwh of energy consumed, and also resets on power loss/counter wrap. If you use the AC a lot it should eventually start increasing, but very slow.
It is not a really reliable/precise way of measuring. If you're really looking for a power measurement, you can use volts * current reported as a better rough real-time estimate, or use CT clamps/other energy monitoring solution.

Hi. is it possible for you to provide a template guide to do this? many thanks


Bad link to Bot Framework Telephony project

The link to the Bot Framework Telephony project returns a 404 from github.  Bot Framework Telephony project.
The project repo itself seems to have gone missing, or is not available to the public.
Please fix the repo / link.
If this is under a controlled preview, please provide details how to signup for preview.

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

ID: 176c6ffa-093d-88bc-cc6c-1d17c6c6ee42
Version Independent ID: bac9d6af-5a47-6eb4-0114-2a20e031b03a
Content: Connect a bot to Telephony in Bot Framework SDK (Preview) - Bot Service
Content Source: articles/bot-service-channel-connect-telephony.md
Service: bot-service
GitHub Login: @JonathanFingold
Microsoft Alias: iawilt

@mladewig -- that is odd. Following up internally. Will let you know when I find something out.

@mladewig -- this channel never made it out of preview. I'll update the docs.

PS. The channel is not accepting new bot development at this time.

Documentation updated. Changes should be live in a few hours.


How to start up?

I have download it! But have no clue or idea from the readme how to open or install or something else this project. Can the upset or installing be more specific?

I understand that not everyone has technical background, but starting the application is very much described in the readme.

After downloading the archive (zip or tar), the application can be started using the bin/vigilant-bands.bat file.

It's really just that. Once you've downloaded and extracted the release archive, there's only this one batch file to launch and you're guided through the installation.
Or are you just unfamiliar with GitHub and don't know what to download? In that case, just head over to the releases page and download the latest vigilant-bans-X.X.X.zip (which at this time is vigilant-bans-1.0.2.zip.

Since I did not hear back from you, I'm going to assume this issue is resolved.


5028 name translations UI updates

Issue #: /bcgov/entity5028#
Description of changes:
Name translation ui updates based on feedback for both alterations and corrections
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Please fix the ticket link in this PR's description block.

You should be able to fix some of the code coverage annotations by expanding the respective unit tests.

Please update the app version by 0.0.1 (in package.json and package-lock.json). That way, we can check the version of a deployed app and determine if it includes your code or not.
Basically, most PRs should update the app version.

I also upped the version & added to the tests


Adds disable camera reset

Offset taken from https://github.com/techiew/EldenRingMods/tree/master/CameraFix
I didn't include the disable camera rotate one, because I don't use it, but I would be happy to. Also, I didn't include a short param because -c and -r were already taken.

Seems that this might disable dismount as well. Closing for now.

Hi, thanks for your contribution. We had a camera reset patch before, but it was removed after the option was officially added to the settings menu of the game. Does this work differently than the ingame setting?

I would love to be wrong about this, because I hate it so much, but I think they only added an option for specifically the camera auto-rotating on move, which is annoying with M+KB input. I think this is the camera "wall" setting.
This patch disables the camera reset when using the enemy lock on command (R3 on controller) when there is no enemy in range or not in front of you (eg, during a fight if you run away from the enemy and try to lock on, the camera instantly resets to the direction the character is facing).
Looking through recent comments on the mod page (https://www.nexusmods.com/eldenring/mods/118?tab=posts) suggests that the lock on fix is not in the settings, even though the sticky comment suggests it's obsolete.
Do you know what setting turns that binging off? If I am wrong, go ahead and close.


Fix Issue 14156 - buffer overflow in LibELF

A single call to printf is performed instead of several overlapping calls.
I checked that it indeed fixes the issue and that the test suite still pass.
I also checked separately that Headers generated with both versions are bitwise equivalent.

which line of the original was the buffer overflow on?

I assume that this pull request is for:
https://issues.dlang.org/show_bug.cgi?id=14156
-> https://github.com/D-Programming-Language/dmd/blob/047d0de680c32f5b7ce746e6de574698898535b7/src/libelf.c#L214
Kind of OT. Do we have any process for handling security issues? I personally like how Apache Tomcat publishes them: https://tomcat.apache.org/security.html

I believe this is this line with user_id = 199658 which is 6 characters long.
Printf is adding a seventh '\0' which overruns h->user_id.
This is fine since Header is wide enough but it definitely writes to h->group_id.
I don't understand how it's detected by libc though.

I'm going to have to object to the very first change in that list. Although yes, Header is a thin value wrapper around the characters, we should not be writing against it as if it were a single static char[], not without good reason anyways. It pointlessly hides what the code actually does.

@Orvid : I understand your concern about code obfuscation but then the only way we can be safe here is to first allocate a wide enough buffer and then copy it. It is a bit wasteful to me but I guess that's ok.
How about something like that :
namespace {
template <size_t SIZE, typename T>
void FormatWithoutTrailingZero(char(&destination)[SIZE], const char *format,
                               T value)
{
  char buffer[SIZE + 1];
  const int length = snprintf(buffer, sizeof(buffer), format, value);
  assert(length <= SIZE);
  memcpy(destination, buffer, length);
  memset(destination + length, ' ', SIZE - length);
}
}

void OmToHeader(Header *h, ObjModule *om)
{
    if (om->name_offset == -1)
    {
        const size_t len = strlen(om->name);
        memcpy(h->object_name, om->name, len);
        assert(len < OBJECT_NAME_SIZE);
        h->object_name[len] = '/';
    }
    else
    {
        FormatWithoutTrailingZero(h->object_name, "/%d", om->name_offset);
    }

    FormatWithoutTrailingZero(h->file_time, "%llu", (longlong)om->file_time);
    if (om->user_id > 999999)
        om->user_id = 0;
    FormatWithoutTrailingZero(h->user_id, "%u", om->user_id);
    if (om->group_id > 999999)
        om->group_id = 0;
    FormatWithoutTrailingZero(h->group_id, "%u", om->group_id);
    FormatWithoutTrailingZero(h->file_mode, "%o", om->file_mode);
    FormatWithoutTrailingZero(h->file_size, "%u", om->length);

    h->trailer[0] = '`';
    h->trailer[1] = '\n';
}

I believe this is this line with user_id = 199658 which is 6 characters long.

You are correct, though the comments on lines 203..207 explain it. Apparently, a hardened libc doesn't like it, which is fair. Although I wrote that code, I now consider the practice unacceptable and needs to be corrected.

@gchatelet Yes, that looks much better to me, because, although yes, it is longer, it's still immediately clear what is being put where without having to know the inner layout of Header.

I think the buffer cast is ok, and the result is clearer and simpler than the template version. You could make a union with Header and char[OBJECT_NAME_SIZE], but it seems to be more lines of code for little value. If you fix the } else thing, I'll pull it.

As Sobira pointed out on the bug. It exists a version of printf like this which would deduce buffer's size.
template <size_t size>
int sprintf(char (&buffer)[size],const char *format [,argument] ... ); // C++ only

So the bug might not be related to hardened libc but simply to the user_id 6 digits.
The templated version I proposed looks safer to me but also more wasteful. I can go either way, just tell me what you think. I amended the pull request with the style issues and the use of more secure snprintf instead of sprintf.

Your latest LGTM. The template version seemed over-engineered for this straightforward task.

Auto-merge toggled on


Removed DLWBouncyView

Lib has a poor README, almost 2 years with no PR, few stars, 1 issue closed and no PR was ever made

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks: )

Link issues by awesome_bot

Line
Status
Link

313
Error
http://oclint.org/  getaddrinfo: Name or service not known

2446
Error
https://iconresizer.com/  Connection refused - connect(2) for "iconresizer.com" port 443

  Generated by :no_entry_sign: Danger


Needs Run As account update

Docs state Run As accounts will be discontinued in 2023 but the Prerequisites of this page do not state any workarounds or warnings of discontinuation. How-To needs to be updated with using Managed Identities

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

ID: 225c9d05-83dd-b006-0025-3753f5ab25bf
Version Independent ID: 9eecef0c-b1cb-1136-faf7-542214492096
Content: Azure Automation Start/Stop VMs during off-hours overview
Content Source: articles/automation/automation-solution-vm-management.md
Service: automation
Sub-service: process-automation
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

@oPhreak
Thanks for your feedback! We will investigate and update as appropriate.

@oPhreak, thank you for reporting it. This is under review/update, and it will be added to the doc soon.


Fix cassettes after URI escaping fix

Coverage increased (+10.2%) to 52.364% when pulling 3153fc303fafe60bb19158d410db2c8102b41167 on gmile:fix-tests-after-uri-change into 7a09ab8bc03468d6c7a5e32905b6e269da21c5f5 on robconery:master.

Coverage increased (+33.5%) to 75.636% when pulling 0cbeef4910bd612780c248528775617ce5048b5b on gmile:fix-tests-after-uri-change into 7a09ab8bc03468d6c7a5e32905b6e269da21c5f5 on robconery:master.

Coverage increased (+34.2%) to 76.364% when pulling 54e8f1e666dc03d4513e4ca43de09d485c007ac5 on gmile:fix-tests-after-uri-change into 7a09ab8bc03468d6c7a5e32905b6e269da21c5f5 on robconery:master.

Coverage increased (+34.2%) to 76.364% when pulling 54e8f1e666dc03d4513e4ca43de09d485c007ac5 on gmile:fix-tests-after-uri-change into 7a09ab8bc03468d6c7a5e32905b6e269da21c5f5 on robconery:master.

@robconery finally a green build :)

YEsssssssss


Not working with ejabberd-15.07

I tried running it with latest ejabberd and getting following error
2015-10-06 17:36:03.565 [info] <0.440.0>@ejabberd_listener:accept:299 (#Port<0.3928>) Accepted connection <IP_ADDRESS>:58997 -> <IP_ADDRESS>:52802015-10-06 17:36:03.566 [debug] <0.803.0>@ejabberd_http:init:153 S: [{[<<"websocket">>],ejabberd_http_ws},{[<<"admin">>],ejabberd_web_admin},{[<<"http-bind">>],mod_http_bind}]2015-10-06 17:36:03.566 [info] <0.803.0>@ejabberd_http:init:157 started: {gen_tcp,#Port<0.3928>}2015-10-06 17:36:03.568 [debug] <0.803.0>@ejabberd_http:process_header:279 (#Port<0.3928>) http query: 'GET' <<"/websocket">>2015-10-06 17:36:03.568 [debug] <0.803.0>@ejabberd_http:process:357 [<<"websocket">>] matches [<<"websocket">>]2015-10-06 17:36:03.568 [debug] <0.803.0>@ejabberd_websocket:connect:122 Sent handshake response : [<<"HTTP/1.1 101 Switching Protocols\r\n">>,<<"Upgrade: websocket\r\n">>,<<"Connection: Upgrade\r\n">>,[<<"Sec-Websocket-Protocol:">>,<<"xmpp">>,<<"\r\n">>],<<"Sec-WebSocket-Accept: ">>,<<"VfCGdCiNTlrHasFY7XYEFFssdsY=">>,<<"\r\n\r\n">>]2015-10-06 17:36:03.568 [debug] <0.804.0>@ejabberd_http_ws:init:125 Client connected through websocket {http_ws,<0.804.0>,{{115,99,236,138},58997}}2015-10-06 17:36:04.039 [info] <0.440.0>@ejabberd_listener:accept:299 (#Port<0.3932>) Accepted connection <IP_ADDRESS>:58998 -> <IP_ADDRESS>:52802015-10-06 17:36:04.039 [debug] <0.807.0>@ejabberd_http:init:153 S: [{[<<"websocket">>],ejabberd_http_ws},{[<<"admin">>],ejabberd_web_admin},{[<<"http-bind">>],mod_http_bind}]2015-10-06 17:36:04.039 [info] <0.807.0>@ejabberd_http:init:157 started: {gen_tcp,#Port<0.3932>}2015-10-06 17:36:04.283 [debug] <0.337.0>@ejabberd_odbc:sql_query_internal:473 MySQL, Send query[<<"select password from users where username='">>,<<"arbit6">>,<<"';">>]2015-10-06 17:36:04.936 [info] <0.806.0>@ejabberd_c2s:wait_for_sasl_response:932 ({socket_state,ejabberd_http_ws,{http_ws,<0.804.0>,{{115,99,236,138},58997}},<0.805.0>}) Accepted authentication for arbit6 by undefined from <IP_ADDRESS>2015-10-06 17:36:04.938 [debug] <0.804.0>@ejabberd_http_ws:terminate:256 C2S Pid : <0.805.0>2015-10-06 17:36:04.938 [debug] <0.803.0>@ejabberd_http:send_text:179 Error in gen_tcp:send: {error,closed}

There was a similar issue opened with ejabberd - https://github.com/processone/ejabberd/issues/488
Any  idea on how to debug it. Latest stanza.io is able to connect session properly.

Kaiwa now uses stanza.io 7


README Clarifications

Sorry got to ask...
In the README you say in the Prepare section:

Rename hosts.example.json to hosts.json and fill it up

Not having used json much in the past where do I put this hosts.json file?
Then you say...

You can use * if you want to cross-connect to everything else

So I made my hosts.json file look like:

{
"vm1":{"Targets":[]},
"vm2":{"Targets":[]},
"vm3":{"Targets":[*]},
}

If I want everyone to connect to everyone is the above syntax correct?
Thanks
Brian

That's incorrect.
First you specify the Node, then with Targets you specify the Targets.
You can either use:
"vm1":{"Targets":["vm2","vm3"]},
or In your case:
"vm1":{"Targets":[""]},
"vm2":{"Targets":[""]},
"vm3":{"Targets":["*"]},
Which cross-connects everything with everything.
You could also use:
"vm1":{"Targets":[""]},
"vm2":{"Targets":[""]},
"vm3":{"Targets":["*","vm4"]},
etc..

Thanks so much.   I guess json is added to my list of 1000 things to learn :+1:

Yeah, they work together, one does the network setup, the other one takes care of the routing.

ReadMe has been updated.


Implement Server Actions for Vendor CRUD Operations with Error Handling

PR: Implement Server Actions for Vendor CRUD Operations with Error Handling
Description
This pull request addresses the need for robust server-side actions to manage vendor data, including creating, reading, updating, and deleting vendor records in the database. Each action is implemented with comprehensive error handling to address potential issues, such as database connectivity problems, invalid data, or permission-related errors. This setup ensures the reliability and security of vendor data management.
Features Implemented
1. Create Vendor

Adds a new vendor to the database.
Validates all required fields to prevent incomplete data entry.

2. Read Vendor

Retrieves vendor information based on a unique identifier (e.g., vendor ID).
Supports optional filtering to refine vendor data retrieval.

3. Update Vendor

Modifies existing vendor data with the provided information.
Includes validation checks to ensure updates are only applied when data is valid.

4. Delete Vendor

Safely removes a vendor record from the database.
Includes checks to handle cases where the vendor does not exist or cannot be deleted due to constraints.

Error Handling
Each server action includes detailed error handling to manage:

Database Connectivity or Transaction Failures: Graceful handling and logging of database connection issues or failed transactions.
Invalid or Missing Data: Validation checks ensure required fields are present and data format is correct.
Unauthorized Access or Permission Issues: Includes logic to restrict access based on permissions, preventing unauthorized data modifications.
Non-Existent Records: Ensures actions like update or delete only occur when records exist, and provides informative feedback if records are not found.

Summary
These server actions establish a secure and efficient foundation for vendor data management. With enhanced error handling, the implemented CRUD operations maintain data integrity and provide meaningful feedback to developers and users in the case of any issues.
closes #193

@Vimall03 please check now


Merge to publish

Docs Build status updates of commit a5729a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Successfully multiply Q_8 loaded weight matrix

As quantisation is going to be the primary mode in which models are run, we need to design for it from the ground up.
We will add the ability to do a quantized matmul from day 1, whilst we are still in this fluid design phase.

#6 completed


楼主好，部署时遇见了问题pysqlite2找不到

File "/usr/local/lib/python3.6/site-packages/sqlalchemy/dialects/sqlite/pysqlite.py", line 334, in dbapi
from pysqlite2 import dbapi2 as sqlite
ModuleNotFoundError: No module named 'pysqlite2'
我查了一下，说是：
The module is called sqlite3. pysqlite2 was the module's name before it became part of the Python standard library.
You probably want to use this in your code:
import sqlite3
And the standard documentation is here: http://docs.python.org/library/sqlite3.html
edit: And just to cover all the bases:
The sqlite3 module also has a dbapi2 sub-member, but you don't need to use it directly. The sqlite3 module exposes all the dbapi2 members directly.
本人不是搞python开发，不太明白，我的python环境是linux 3.6.0

可以尝试一下安装pysqlite库: pip3 install pysqlite2

@cowthan 今天有空尝试了在Ubuntu16.04下部署，确实存在这样的问题
经过一番尝试，发现是系统没有安装sqlite3相关的东西，解决方案如下：

sudo apt install sqlite3 libsqlite3-dev # 安装sqlite3
下载python3源码，解压，cd到该目录
./configure --with-ssl --enable-loadable-sqlite-extensions && make && sudo make install # 重新编译安装

可以尝试import sqlite3，没有报错就可以了


Pass timer data to a sharepoint list column - 2228715

How do you pass the timers data

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

ID: b11a9f1d-da5c-f25b-2b48-eddc4c4a6cc5
Version Independent ID: 1c0f1c98-8bf0-320d-74e8-434e816a4222
Content: Timer control: reference - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/controls/control-timer.md
Service: powerapps
GitHub Login: @fikaradz
Microsoft Alias: fikaradz

Hi there, sorry for the late reply.  What are you trying to do?

Hi there, I don't understand the use case.  Can you explain what you're trying to do here?


Split string validation into names or identifiers and enforce

Testing with Oozie 4.1.0 shows that identifiers (e.g. workflow action names) need to follow the regex ^[a-zA-Z_][\\-_a-zA-Z0-9]{0,38}$, however names (e.g. workflow and coordinator names) do not need to adhere to that regex (e.g. can contain spaces/punctuation) but are limited to 255 chars by Oozie's backing database and are limited to printable ASCII characters.
Creating a workflow with a really long action name results in:
org.apache.oozie.command.CommandException: E0724: Invalid node name, name [action-ppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp] must be 50 chars or less
        at org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:272)

Creating a workflow with a very long name results in:
2017-02-27 17:35:36,418 ERROR SubmitXCommand:538 - SERVER[oozie] USER[root] GROUP[-] TOKEN[] APP[aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa] JOB[0000019-170227162353067-oozie-root-W] ACTION[-] XException,
org.apache.oozie.command.CommandException: E0803: IO error, E0603: SQL error in operation, <openjpa-2.2.2-r422266:1468616 fatal store error> org.apache.openjpa.persistence.RollbackException: The transaction has been rolled back.  See the nested exceptions for details on the errors that occurred.
FailedObject: org.apache.oozie.WorkflowJobBean@27d6d59
...
Caused by: <openjpa-2.2.2-r422266:1468616 fatal general error> org.apache.openjpa.persistence.PersistenceException: A truncation error was encountered trying to shrink VARCHAR 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&' to length 255.

@honkfestival @kmtaylor-github this should add the necessary safety for names and IDs while being more permissive than before.


UI Re-Assign interface request - UI crashes on stest machine

2024-10-18T12:23:40.024690+02:00 lxm02199 fworch-ui:  2024-10-18T12:23:40+02:00 Debug - API call (GraphQlApiConnection.cs in line 129), Sending API call  in role implementer: query getRuleActions {  stm_action {    action_id    action_name ...
2024-10-18T12:23:40.027493+02:00 lxm02199 fworch-ui:  2024-10-18T12:23:40+02:00 Debug - API call (GraphQlApiConnection.cs in line 129), Sending API call  in role implementer: query getTracking {  stm_track {    track_id    track_name  }}...
2024-10-18T12:23:40.029594+02:00 lxm02199 fworch-ui:  2024-10-18T12:23:40+02:00 Debug - API call (GraphQlApiConnection.cs in line 129), Sending API call  in role implementer: query getIpProtocols {  stm_ip_proto {    ip_proto_id    ip_proto_...
2024-10-18T12:24:40.810326+02:00 lxm02199 fworch-ui:  Process terminated. Assertion failed.
2024-10-18T12:24:40.810388+02:00 lxm02199 fworch-ui:  The assigned value is null but the Nullable option is not enabled.
2024-10-18T12:24:40.810421+02:00 lxm02199 fworch-ui:     at FWO.Ui.Shared.Dropdown`1.set_SelectedElement(ElementType value) in /usr/local/fworch/ui/files/FWO.UI/Shared/Dropdown.razor:line 151
2024-10-18T12:24:40.810450+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Reflection.PropertySetter.CallPropertySetter[TTarget,TValue](Action`2 setter, Object target, Object value)
2024-10-18T12:24:40.810477+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.<SetProperties>g__SetProperty|3_0(Object target, PropertySetter writer, String parameterName, Object value)
2024-10-18T12:24:40.810515+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.SetProperties(ParameterView& parameters, Object target)
2024-10-18T12:24:40.810542+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.ComponentBase.SetParametersAsync(ParameterView parameters)
2024-10-18T12:24:40.810572+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)
2024-10-18T12:24:40.810600+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
2024-10-18T12:24:40.810630+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
2024-10-18T12:24:40.810666+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
2024-10-18T12:24:40.810693+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
2024-10-18T12:24:40.810720+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
2024-10-18T12:24:40.810881+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
2024-10-18T12:24:40.810950+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)
2024-10-18T12:24:40.810989+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
2024-10-18T12:24:40.811023+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs, Boolean waitForQuiescence)
2024-10-18T12:24:40.811053+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs)
2024-10-18T12:24:40.811086+02:00 lxm02199 fworch-ui:     at InvokeStub_WebRendererInteropMethods.DispatchEventAsync(Object, Span`1)
2024-10-18T12:24:40.811123+02:00 lxm02199 fworch-ui:     at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
2024-10-18T12:24:40.811229+02:00 lxm02199 fworch-ui:     at Microsoft.JSInterop.Infrastructure.DotNetDispatcher.InvokeSynchronously(JSRuntime jsRuntime, DotNetInvocationInfo& callInfo, IDotNetObjectReference objectReference, String argsJson)
2024-10-18T12:24:40.811258+02:00 lxm02199 fworch-ui:     at Microsoft.JSInterop.Infrastructure.DotNetDispatcher.BeginInvokeDotNet(JSRuntime jsRuntime, DotNetInvocationInfo invocationInfo, String argsJson)
2024-10-18T12:24:40.811283+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost.<>c__DisplayClass45_0.<BeginInvokeDotNetFromJS>b__1()
2024-10-18T12:24:40.811312+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<InvokeAsync>g__Execute|8_0(ValueTuple`3 state)
2024-10-18T12:24:40.811358+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.InvokeAsync(Action action)
2024-10-18T12:24:40.811386+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost.BeginInvokeDotNetFromJS(String callId, String assemblyName, String methodIdentifier, Int64 dotNetObjectId, String argsJson)
2024-10-18T12:24:40.811420+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811460+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Server.ComponentHub.BeginInvokeDotNetFromJS(String callId, String assemblyName, String methodIdentifier, Int64 dotNetObjectId, String argsJson)
2024-10-18T12:24:40.811489+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811517+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.Components.Server.ComponentHub.BeginInvokeDotNetFromJS(String callId, String assemblyName, String methodIdentifier, Int64 dotNetObjectId, String argsJson)
2024-10-18T12:24:40.811555+02:00 lxm02199 fworch-ui:     at lambda_method52(Closure, Object, Object[])
2024-10-18T12:24:40.811583+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.ExecuteMethod(ObjectMethodExecutor methodExecutor, Hub hub, Object[] arguments)
2024-10-18T12:24:40.811607+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811633+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.ExecuteHubMethod(ObjectMethodExecutor methodExecutor, THub hub, Object[] arguments, HubConnectionContext connection, IServiceProvider serviceProvider)
2024-10-18T12:24:40.811666+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.<Invoke>g__ExecuteInvocation|18_0(DefaultHubDispatcher`1 dispatcher, ObjectMethodExecutor methodExecutor, THub hub, Object[] arguments, AsyncServiceScope scope, IHubActivator`1 hubActivator, HubConnectionContext connection, HubMethodInvocationMessage hubMethodInvocationMessage, Boolean isStreamCall)
2024-10-18T12:24:40.811698+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811728+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.<Invoke>g__ExecuteInvocation|18_0(DefaultHubDispatcher`1 dispatcher, ObjectMethodExecutor methodExecutor, THub hub, Object[] arguments, AsyncServiceScope scope, IHubActivator`1 hubActivator, HubConnectionContext connection, HubMethodInvocationMessage hubMethodInvocationMessage, Boolean isStreamCall)
2024-10-18T12:24:40.811764+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.Invoke(HubMethodDescriptor descriptor, HubConnectionContext connection, HubMethodInvocationMessage hubMethodInvocationMessage, Boolean isStreamResponse, Boolean isStreamCall)
2024-10-18T12:24:40.811794+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811821+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.Invoke(HubMethodDescriptor descriptor, HubConnectionContext connection, HubMethodInvocationMessage hubMethodInvocationMessage, Boolean isStreamResponse, Boolean isStreamCall)
2024-10-18T12:24:40.811846+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.ChannelBasedSemaphore.RunTask[TState](Func`2 callback, TState state)
2024-10-18T12:24:40.811872+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
2024-10-18T12:24:40.811897+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.ChannelBasedSemaphore.RunTask[TState](Func`2 callback, TState state)
2024-10-18T12:24:40.811923+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.ChannelBasedSemaphore.RunAsync[TState](Func`2 callback, TState state)
2024-10-18T12:24:40.811953+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.ProcessInvocation(HubConnectionContext connection, HubMethodInvocationMessage hubMethodInvocationMessage, Boolean isStreamResponse)
2024-10-18T12:24:40.811982+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher`1.DispatchMessageAsync(HubConnectionContext connection, HubMessage hubMessage)
2024-10-18T12:24:40.812010+02:00 lxm02199 fworch-ui:     at Microsoft.AspNetCore.SignalR.HubConnectionHandler`1.DispatchMessagesAsync(HubConnectionContext connection)
2024-10-18T12:24:40.812035+02:00 lxm02199 fworch-ui:     at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
2024-10-18T12:24:40.812065+02:00 lxm02199 fworch-ui:     at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AsyncStateMachineBox`1.MoveNext(Thread threadPoolThread)
2024-10-18T12:24:40.812090+02:00 lxm02199 fworch-ui:     at System.Threading.ThreadPoolWorkQueue.Dispatch()
2024-10-18T12:24:40.812116+02:00 lxm02199 fworch-ui:     at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

Global Error Handling in your UI framework, which ensures that unexpected exceptions are caught and handled gracefully, without crashing the entire application. Depending on the framework you're using, the implementation details can vary. In your case, since the context seems to be Blazor (a .NET web framework), Blazor provides specific ways to handle errors at a global level using ErrorBoundary components.
Blazor's ErrorBoundary for Global Error Handling
The ErrorBoundary component in Blazor allows you to catch and manage unhandled exceptions within the UI. Instead of allowing an error to crash the whole application or leave the UI in an inconsistent state, you can present a user-friendly message, log the error, or attempt a recovery strategy. This feature improves the robustness of your application, ensuring users don’t face a broken or unresponsive interface when something goes wrong.
Here’s a more detailed breakdown of how it works and how you can implement it in Blazor:
1. Basic ErrorBoundary Usage
An ErrorBoundary wraps around your components and catches any unhandled exceptions that occur within them. When an error occurs, Blazor will display the fallback content you provide.
Example:
<ErrorBoundary>
    <ChildContent>

        <Dropdown SelectedElement="..."/>
    </ChildContent>
    <ErrorContent>

An error occurred while loading the dropdown. Please try again later.

    </ErrorContent>
</ErrorBoundary>

ChildContent: This contains the components that are being monitored for exceptions.
ErrorContent: This is the fallback content that will be displayed if an error occurs.

2. Catching and Displaying Errors
When an exception is thrown inside any of the components wrapped in the ErrorBoundary, the ErrorContent will be displayed instead of the component’s original content. This gives you a controlled way to communicate to the user that something went wrong.
Example UI Handling for Dropdown:
<ErrorBoundary>
    <ChildContent>
        <Dropdown SelectedElement="selectedElement" />
    </ChildContent>
    <ErrorContent>

Oops! Something went wrong while loading the dropdown. Please refresh the page.

    </ErrorContent>
</ErrorBoundary>

This setup prevents the dropdown component from crashing the entire UI, and instead shows the user-friendly message.
3. Logging Errors Globally
While displaying error messages to users is important, it's often essential to log errors for debugging and troubleshooting purposes. You can handle error logging inside the OnError event of the ErrorBoundary.
Here's how you might capture and log the error:
Custom ErrorBoundary with Logging:
@inherits ErrorBoundary
@inject ILogger<CustomErrorBoundary> Logger

<ChildContent>
    @ChildContent
</ChildContent>

<ErrorContent>

Something went wrong! Our team has been notified.

</ErrorContent>

@code {
    protected override void OnError(Exception exception)
    {
        // Log the error or send it to an external service
        Logger.LogError(exception, "An unhandled exception occurred in the UI.");

        // Optionally reset the error boundary
        // Recover();
    }
}

In this example:

You inject an ILogger instance and use it to log the exception details.
You override the OnError method, which gets called whenever an unhandled exception occurs within the ErrorBoundary.

4. Error Boundary Reuse (Centralized Error Handling)
You can create a reusable ErrorBoundary component that wraps around other UI components in your app. This centralizes error handling across your application, reducing boilerplate code and ensuring consistent error messages.
Reusable ErrorBoundary Component (CustomErrorBoundary.razor):
@inherits ErrorBoundary

<ChildContent>
    @ChildContent
</ChildContent>

<ErrorContent>

An unexpected error occurred. Please contact support.

</ErrorContent>

@code {
    protected override void OnError(Exception exception)
    {
        // Log the error, notify an admin, etc.
        // For example, sending logs to an external service
    }
}

Then, you can wrap any component or page with this reusable ErrorBoundary:
<CustomErrorBoundary>
    <YourComponent />
</CustomErrorBoundary>

5. ErrorBoundary in Layouts
You can also place the ErrorBoundary in layout files to catch errors across larger portions of your application, such as entire sections or pages.
Example (MainLayout.razor):
<ErrorBoundary>
    <ChildContent>
        @Body
    </ChildContent>
    <ErrorContent>

An error occurred in the layout. Please refresh the page or contact support.

    </ErrorContent>
</ErrorBoundary>

In this example, if any error happens while rendering a page inside the layout, the fallback content will be displayed, and the entire layout won’t crash.
6. Handling Cascading Errors
If your application has cascading errors that need to bubble up to a higher-level error handler, you can nest ErrorBoundary components at different levels to ensure you handle errors at the appropriate scope.
Benefits of Global Error Handling

User Experience: Prevents your users from seeing broken UI or encountering application crashes.
Debugging and Logging: Logs errors for later analysis, making it easier to troubleshoot.
Granularity: You can wrap individual components, pages, or entire layouts to handle errors at the appropriate level.
Consistency: Ensures a uniform error-handling approach across your app.
Recovery: Provides a way to recover from errors (e.g., allow the user to retry an operation or refresh the page).

By using ErrorBoundary in Blazor, you can significantly enhance the reliability and user experience of your UI, preventing unexpected crashes and ensuring that your application continues to function even when individual components fail.


TypeError: Expression.mean() got an unexpected keyword argument 'dtype'

Describe the bug
In numpy 2+ there is dtype argument for mean (and other similar functions), but in cvxpy Expression.mean() there is no such a parameter:
Numpy
@array_function_dispatch(_mean_dispatcher)
def mean(a, axis=None, dtype=None, out=None, keepdims=np._NoValue, *,
         where=np._NoValue):
    kwargs = {}
    if keepdims is not np._NoValue:
        kwargs['keepdims'] = keepdims
    if where is not np._NoValue:
        kwargs['where'] = where
    if type(a) is not mu.ndarray:
        try:
            mean = a.mean
        except AttributeError:
            pass
        else:
            return mean(axis=axis, dtype=dtype, out=out, **kwargs)

    return _methods._mean(a, axis=axis, dtype=dtype,
                          out=out, **kwargs)

cvxpy
    def mean(self, axis=None, *, keepdims=False):
        """
        Equivalent to `cp.mean(self, axis, keepdims)`.
        """
        from cvxpy import mean
        return mean(self, axis, keepdims)

And
riskConstraints = [ Z >= -X - np.mean((X2 - X3 @ X4)) ]

produces

TypeError: Expression.mean() got an unexpected keyword argument 'dtype'

Version
numpy==2.1.2
pandas==2.2.2
cvxpy==1.5.3
Additional context
There were no such problems with numpy < 2.0

we generally don't support dtype parameters for cvxpy expressions (for example, the numerical values of variables are numpy arrays, which you could change its dtype after the problem has been solved).
I am not able to reproduce your specific error since I don't know what your variables Z and X are. Could you please send a full reproducible example? It would also help to know what is the expected behavior that you want, thanks!


Fix python3 print statements

Closes # for release #.

@agconti +1 for this.

@CoreyAR Thanks for contributing! ✨ 💖
@CoreyAR @jonathan-s since fabric only supports python 2.7, how you guys using this with python 3?

I wasn't using this with Fabric. I used cookiecutter-django-rest to scaffold a couple projects and then customize from there.

Ahh, and the fabfile prevented you from running it?

Hey @CoreyAR, @jonathan-s -- with #324 the project was moved entirely to Python 3.6 and the fabfile was removed. ✨ 🎉
Thank you for opening up this issue originally. Closing this now since it was solved by #324


Fix ipmitool version and build directory missing issues

Issues @clintonskitson ran into trying to get this off the ground with a fresh system.
@heckj @DavidjohnBlodgett

+1

:+1:


Annotation Viewer/Editor

Client-side annotation viewer/editor implementation
TODO:

[x] Add SpectroInfo properties to the spectrogram endpoint.  This provides the width/height of the image plus the start/end points for the time and the frequencies.  Also may want to include the freq scale for rendering the annotations differently in the future.  For now lets just go with a standard linear scale.
[x] Implement API calls for getting annotations from the server, this includes the GET/PUT/PATCH endpoints.  Possible the DELETE endpoint as well
[x] testing and drawing of a simple annotation on the image utilizing the new LayerManager and Rectangle Layer.  Create a simple sample annotation and ensure it can be drawn on the image and viewed properly.
[ ] Implement the callback events for selecting annotations and editing annotations.
[ ] Add TextLayer for rendering of the text of an annotation to give it some type of label
[ ] Add an editor to the SpectroViewer so that when an annotation is selected the user can edit the species list that is attached to the annotation.
[ ] Save functionality for adding new annotations to the system.  These needs to PUT/PATCH annotations that are available.

Having an issue where I can draw an annotation fill but can draw an outline for some reason.  Not sure what is happening with it.


Stuck on block #60032

Node v<IP_ADDRESS> is stuck on block #60032
Tried to reindex, still cannot get passed this block.

same here

I as well get stuck on block #60032 running v<IP_ADDRESS> Macintosh, I have even installed fresh on another Windows 7 PC only to get stuck on that block again. Here is the last few lines in the debug log. My ISP does not provide IPv6 addressing, but I don't see why the software cant just do a 6to4 conversion.. I was able to sync 100% just fine before the fork.  Do I now need a IPv6 WAN address?  Let me know if it works. Make sure to delete peers and banlist


Block requests by IP, only allow requests with proper host header

Task linked: QF-1779 Block requests by IP, only allow requests with proper host header


Paste Does Not Work (Firefox)

On Firefox, paste functionality does not work.  On Edge and Chrome, this is not an issue. Also, copy and cut are working as expected, so it appears as it's only paste that is not functional.

This is a duplicate of #395. The root cause is that Firefox puts restrictions on clipboard access that make Flutter's Clipboard.getData not work. Flutter's default text fields work around the issue with some relatively complex trickery to manipulate contenteditable HTML elements into focus to keep Firefox happy. It's not clear if it's possible to implement something similar outside the engine, and if it is it won't be a simple fix.

Based on the comment from @jmatth I'm going to close this as a duplicate.