Should delete the old recurring task when the task changed key, or removed

When the key of a recurring task is changed or the task is removed, should the old task be automatically deleted? This is to ensure that outdated tasks do not continue to run.

I was wondering the same thing.
We had a recurring task defined in recurring.yml. After deploy it began running on the regular schedule.
I added three more recurring tasks and removed the original task. However, in the recurring tasks, it is still being executed.
I'm about to look into the internals now, but I'm assuming that the yml file is being read and creating records in the DB. We probably need to remove the DB entry manually for now but wondering if this is a known issue.

Hey! Are you sure the removed task is still running or just listed in Mission Control but not running? See

https://github.com/rails/solid_queue/issues/359
https://github.com/rails/solid_queue/issues/310

Got it, thanks a lot! @rosa

@rosa I can confirm the removed task is indeed running.

@antulik how can you confirm this? Do you have examples of solid_queue_recurring_executions records created after you've deleted the task from the config and redeployed, restarting the processes?

My apologies, I didn't look deep enough. Execution is not scheduled. To be more specific for a removed cron task:

Mission Control -> Recurring tasks -> Next: column IS updated
Mission Control -> Recurring tasks -> Last enqueued: column is NOT updated
Job execution is NOT scheduled

Updated Next column threw me off as I expected it to not change as well. TIL

Ahhh, makes sense. I'm going to fix this confusion in any case very soon, making sure recurring tasks that are removed from the config are also removed from the DB.

Actually going to reopen this one to track that.


loveroms ripper now properly names files

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[x] a bug fix (Fix #...)

Description
The ripper now adds the "7z" extension to files
Testing
Required verification:

[ ] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[ ] I've verified that this change works as intended.

[ ] Downloads all relevant content.
[ ] Downloads content from multiple pages (as necessary or appropriate).
[ ] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[ ] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

Coverage decreased (-0.03%) to 38.544% when pulling 1cf4aba2abd0324b3305b43eaf89e609cbb161a7 on cyian-1756:loveromRipper into cbfd3638425282eeb4cadc15747ff04315486400 on RipMeApp:master.

Coverage decreased (-0.03%) to 38.544% when pulling 1cf4aba2abd0324b3305b43eaf89e609cbb161a7 on cyian-1756:loveromRipper into cbfd3638425282eeb4cadc15747ff04315486400 on RipMeApp:master.


Reference to undefined maven_version global variable causes failure when strict_variables is true

with strict_variables = true.
Triggers following error:
Error: Evaluation Error: Unknown variable: '::maven_version'. at /etc/puppet/modules/maven/manifests/maven.pp:42:6 on node centos-7-x64

Yes, the strict_variable parameter controls whether use uninitialized variable in puppet,  Googled around, there is no elegant solution. I had issue withe getvar also, guess different version of puppet may behave differently, it may also depends on whether you use future_parser.

Are we the only ones have the issues? Look at the puppet forge, this module is the most popular maven one, wondering what others experienced.

I have seen this type of thing with a few modules now.
Although I am relatively new to puppet, from what I can see is that the problem is related to "strict variables" as a new approach and defining the scope of a variable properly when accessed. This seems to become more important when referencing facts.
I often see errors as well as it relates to $schedule when trying new modules.  I hope that helps.
I have learned to start being careful about using ::  when needed to reference higher level variables when needed. Could it simply be related to variable scope?
Sorry I can't help more.. maybe this weekend I might do a fork and play around a bit  to see if I can figure it out.

I have created a pull request that should ensure module's compliance with strict_variables=true. I had same trouble with Puppet 3.5.0 and Puppet 3.6.0, but now the change passes all tests.


Update AssemblyScript and rebuild

While the perf difference for ASTC and RGBA32 modules is mostly within 1% margin, BC7 shows up to 4% slowdown on some inputs

Hmm, basically all this changes should speedup execution time. But it really depends on VM (turbofun in v8) as well. So it guess it could be better in future with newier v8.

In the interest of moving this project further, I did a few more benchmarks.
There are 76 ASC versions in the [0.15.0 .. 0.19.22] range. I compiled the BC7 transcoder with all of them. After removing duplicates, only 9 unique variants left.

v0.15.0
v0.15.2
v0.17.2
v0.18.0 - the only difference from v0.17.2 is the order of exports; also --runtime none -> --runtime stub
v0.18.27 - .wat is identical to v0.18.0 but .wasm is different
v0.19.0
v0.19.12
v0.19.19
v0.19.21

Here are some perf results on Node.js 17.4, x86-64 (lower is better):

Mode 8 shows a strange regression with v0.19.x but it does not seem critical on real numbers:

For completeness, here's how the binary size changes (also a regression with v0.19.0.x but it's fine for now):

@MaxGraey
I'm going to update this PR to v0.19.22 and merge it asap.


remember last vehicle displayed and show on startup

If I open connect.comma.ai multiple times and have access to multiple vehicles, it seems random which vehicle is loaded, which is annoying.  I think it would be best to show the last vehicle you looked at (or something that at least makes it consistent).

The "random" ordering I believe is the same as what you see in useradmin. Devices are shown in descending order of their last athena ping. And yes, it would be amazingly helpful if my two personal vehicles weren't pseudo-randomly interspersed among the (checking) 133 dongle IDs I currently have access to.
If I may propose an ordering:

Open directly to the last vehicle we were looking at, THEN
Sort the list by owned (vs readonly) devices, THEN
Further sort by any reasonable consistent criteria (alphabetic by device nickname, and then by dongle ID?)


link invalid

[Enter feedback here]
Hi,
The link for OpenAPI specification is invalid, could you please help to update this one?
Thank you in advance!

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

ID: b6271060-4e62-bf22-3f63-1d6596d6079b
Version Independent ID: 8a9cd4a0-e494-d7b9-1804-b50d82b0a4a5
Content: Queries, Dashboards, and Alerts API 2.0 - Azure Databricks - Databricks SQL
Content Source: databricks/sql/api/queries-dashboards.md
Service: azure-databricks
Sub-service: databricks-sql-analytics
GitHub Login: @mssaperla
Microsoft Alias: saperla

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

@cchenshu
Thank you for bringing this to our attention. I've assigned this issue to the author who will investigate and update as appropriate.

@leifbro
Could you please review add comments on this, update as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7198) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Fatal Python error: Segmentation fault - test_arpack.py::test_symmetric_modes

My issue is about a segmentation fault when trying to run tests.
Reproducing code example:

python runtests.py -v -s  sparse

Error message:

scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py::test_symmetric_modes Fatal Python error: Segmentation fault

Current thread 0x00007fe14f9fa740 (most recent call first):
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/_lib/_util.py", line 121 in _aligned_zeros
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/arpack.py", line 518 in __init__
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/arpack.py", line 1681 in eigsh
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py", line 244 in eval_evec
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py", line 404 in test_symmetric_modes
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/python.py", line 184 in pytest_pyfunc_call
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/python.py", line 1479 in runtest
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 135 in pytest_runtest_call
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 217 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 244 in from_call
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 217 in call_runtest_hook
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 186 in call_and_report
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 100 in runtestprotocol
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/runner.py", line 85 in pytest_runtest_protocol
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/main.py", line 272 in pytest_runtestloop
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/main.py", line 247 in _main
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/main.py", line 191 in wrap_session
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/main.py", line 240 in pytest_cmdline_main
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/home/kaleab/.conda/envs/scipy/lib/python3.7/site-packages/_pytest/config/__init__.py", line 125 in main
  File "/home/kaleab/Documents/Code/scipy/build/testenv/lib/python3.7/site-packages/scipy/_lib/_testutils.py", line 67 in __call__
  File "runtests.py", line 313 in main
  File "runtests.py", line 525 in <module>
Segmentation fault (core dumped)

Scipy/Numpy/Python version information:
Python 3.7.7/python 3.6.0, pytest-5.4.1/ pytest 4.0.0 , py-1.8.1, pluggy-0.13.1, numpy 1.18.1

I also tested this on google colab and this resulted in the same issue, meaning it is not a local problem.

This may be related to gh-11773, based on the colab failure you mentioned. Can you try running tests again from the current master branch?

@perimosocordiae No luck, I just did a build from master with the latest changes.

@KaleabTessera what version of OpenBLAS, MKL or ATLAS are you using here?

The output of conda list may be useful here. Also OS and compiler versions.

This test is also failing on master intermittently, but not a segfault.
_____________________________ test_symmetric_modes _____________________________
[gw1] linux -- Python 3.7.9 /home/travis/virtualenv/python3.7.9/bin/python
/home/travis/virtualenv/python3.7.9/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py:404: in test_symmetric_modes
    None, sigma, mattype, None, mode)
        D          = <std-symmetric>
        k          = 2
        mattype    = <function aslinearoperator at 0xffff8b48c9e0>
        mode       = 'buckling'
        modes      = ['normal', 'buckling', 'cayley']
        params     = <scipy.sparse.linalg.eigen.arpack.tests.test_arpack.SymmetricParams object at 0xffff41cb9e90>
        sigma      = 0.5
        symmetric  = True
        typ        = 'f'
        which      = 'LA'
/home/travis/virtualenv/python3.7.9/lib/python3.7/site-packages/scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py:261: in eval_evec
    assert_allclose(LHS, RHS, rtol=rtol, atol=atol, err_msg=err)
E   AssertionError:
E   Not equal to tolerance rtol=0.00178814, atol=0.000357628
E   error for eigsh:standard, typ=f, which=LA, sigma=0.5, mattype=aslinearoperator, OPpart=None, mode=buckling
E   Mismatched elements: 4 / 12 (33.3%)
E   Max absolute difference: 0.01493526
E   Max relative difference: 0.01093912
E    x: array([[-1.072405,  0.563614],
E          [-1.455584, -0.239151],
E          [-1.004519, -0.42866 ],...
E    y: array([[-1.073047,  0.563611],
E          [-1.456878, -0.239156],
E          [-0.998997, -0.428643],...
        LHS        = array([[-1.0724047 ,  0.56361365],
       [-1.4555839 , -0.23915069],
       [-1.0045193 , -0.42866027],
       [-1.0440447 , -0.32811955],
       [-1.5183451 , -0.34796414],
       [-1.4869674 ,  0.7027782 ]], dtype=float32)
        OPpart     = None
        RHS        = array([[-1.0730466 ,  0.56361085],
       [-1.4568783 , -0.23915628],
       [-0.998997  , -0.42864323],
       [-1.0327474 , -0.32808444],
       [-1.5052823 , -0.3479238 ],
       [-1.4720322 ,  0.7028245 ]], dtype=float32)
        a          = array([[1.7170051 , 1.3009547 , 0.9104259 , 0.97003126, 1.4632134 ,
        1.8256624 ],
       [1.3009547 , 2.253338 ...  1.9766154 ],
       [1.8256624 , 2.0743165 , 1.1501507 , 1.3169256 , 1.9766154 ,
        2.8176725 ]], dtype=float32)
        ac         = <6x6 MatrixLinearOperator with dtype=float32>
        atol       = 0.00035762786865234375
        d          = <std-symmetric>
        eigenvalues = array([9.827495 , 1.2812405], dtype=float32)
        eigs_func  = <function eigsh at 0xffff8b5077a0>
        err        = 'error for eigsh:standard, typ=f, which=LA, sigma=0.5, mattype=aslinearoperator, OPpart=None, mode=buckling'
        evec       = array([[-0.10918821,  0.43989468],
       [-0.14824514, -0.18665995],
       [-0.10165327, -0.3345533 ],
       [-0.10508756, -0.2560678 ],
       [-0.1531705 , -0.2715523 ],
       [-0.14978713,  0.54855   ]], dtype=float32)
        exact_eval = array([9.884308+0.j, 1.281241+0.j], dtype=complex64)
        general    = False
        ind        = array([1, 0])
        k          = 2
        kwargs     = {'mode': 'buckling', 'sigma': 0.5, 'tol': 3.5762786865234375e-06, 'v0': None, ...}
        mattype    = <function aslinearoperator at 0xffff8b48c9e0>
        mode       = 'buckling'
        ntries     = 0
        rtol       = 0.0017881393432617188
        sigma      = 0.5
        symmetric  = True
        typ        = 'f'
        v0         = None
        which      = 'LA'


Zarf package file is set to 0 bytes on disconnect from install\update session

Environment
Device and OS: EC2\Amazon Linux 2
App version: 0.31.2
Kubernetes distro being used: EKS
Other:
Steps to reproduce
Run Zarf deployment and have session disconnected before completion
Expected result
After disconnection from deploy\update the package file is in place with proper size.
Actual Result
After disconnection from deploy\update the package file is 0 bytes
Visual Proof (screenshots, videos, text, etc)

Severity/Priority
Low (We have work around)
Additional Context
I noted when doing an initial zarf deploy, or a zarf version update,  the total time of the deployment will sometimes exceed whatever SSM console or SSH timeout value that we might be working with
When the deployment is interrupted by one of these timeouts the concatenated zarf package deployment file which should be ~12GB will have a zero byte value and the engineer will need to pull the part files to their local filesystem to rerun deployment, which then invariably succeeds.
We work around this issue by running deploys in screen or tmux but I was curious if this is know bug

@tmahalligan By concatenated zarf package are your referring to split packages via --max-package-size?

Am sorry for late reply @Noxsios we have a multi-part package that is joined together on successful deploy leaving a single large package file which we the use for deployments to other clusters. We had noticed that on a timeout (SSM or SSH) during deploy when we reestablished as session there would be a single 0 byte file and we were forced to pull the parts again.
I have been thinking on it and I am wondering if this might be an ID10T error where upon reestablishing connectivity the user up arrows to the last command which references the part000 file that is no longer in place and that zeros out the big single file. I will test that and follow back up if that is the case or not.
Thanks for the follow-up


Windows Desktop & Mac Os Desktop

do you have any plan to support Winodws and Mac OS support

Can you be more specific?

i want protect my application from any recording and screenshot on windows and mac os application
https://github.com/akinbicer/screen-capture-protector
https://github.com/FabriBertani/Plugin.Maui.ScreenSecurity


How to set language from frontend?

How to set language from frontend?
This don`t work
$translator = Translator::instance();
$translator->setLocale($locale, true);

Why not use the localeSwitcher component?

Why not use the localeSwitcher component?

No, I am using personal language for each user. And need to change language after user login.

Then you need to redirect to the right location

look at how the localeSwitcher does it.

look at how the LocalePicker component does it. ref. https://github.com/wintercms/wn-translate-plugin/blob/main/components/LocalePicker.php#L75-L92
  public function onSwitchLocale()
  {
      if (!$locale = post('locale')) {
          return;
      }

      // Remember the current locale before switching to the requested one
      $this->oldLocale = $this->translator->getLocale();

      $this->translator->setLocale($locale);

      $pageUrl = $this->withPreservedQueryString($this->makeLocaleUrlFromPage($locale), $locale);
      if ($this->property('forceUrl')) {
          return Redirect::to($this->translator->getPathInLocale($pageUrl, $locale));
      }

      return Redirect::to($pageUrl);
  }

This work so good! Thanks


Feature Request: Draggable Dashboard Items Component

Hello Radzen Team,
I would love to see a component or feature that allows for handling dashboard items in a drag-and-drop view. This feature would enhance the flexibility and customization of dashboards, allowing users to rearrange items easily to suit their preferences.
Use case:

Users could organize their dashboard widgets by dragging and dropping them into different positions.
The layout would persist between sessions, remembering the user's configuration.

This would be an excellent addition to Radzen's component library and improve the user experience for applications with dynamic dashboard requirements.
Thank you for considering this feature request!
Best regards,
Gurjeet

There is already such component that can be used for dashboards as well:
https://blazor.radzen.com/dropzone


use ofa.js in React

Please refer to this repository.
Create a new repository.

https://github.com/ofajs/ofa.js-in-react


[backport] Fix FunctionNode.retained_outputs

Backport of #5424

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 373670f035e8ae5e4a3b400092844cc621268163, target branch v5) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins failure (tests.chainer_tests.links_tests.normalization_tests.test_batch_normalization.BatchNormalizationTest_param_7.test_forward_gpu) is unrelated to the PR.


Create an issue

I get a segmentation fault in the Dart VM when I try to build my Flutter app in profile mode (debug mode works fine). Reproducibility is 100%.
Launching lib/main.dart on Pixel 7 Pro in profile mode...
Building with Flutter multidex support enabled.

===== CRASH =====
si_signo=Segmentation fault(11), si_code=1, si_addr=0x7fcee9b88080
version=3.1.3 (stable) (Tue Sep 26 14:25:13 2023 +0000) on "linux_x64"
pid=561051, thread=561058, isolate_group=main(0x5649f364a6d0), isolate=(nil)((nil))
os=linux, arch=x64, comp=no, sim=no
isolate_instructions=7fcee10e0000, vm_instructions=5649f2031d20
fp=7fcec71feca0, sp=7fcec71fec70, pc=5649f22ce527
  pc 0x00005649f22ce527 fp 0x00007fcec71feca0 dart::MarkingVisitorBase<true>::VisitPointers+0x67
  pc 0x00005649f22ce913 fp 0x00007fcec71fece0 dart::MarkingVisitorBase<true>::DrainMarkingStackWithPauseChecks+0x193

  pc 0x00005649f22ce6bf fp 0x00007fcec71fed50 dart::ConcurrentMarkTask::Run+0x5f
  pc 0x00005649f22abc7b fp 0x00007fcec71fedd0 dart::ThreadPool::WorkerLoop+0x14b
  pc 0x00005649f22abf18 fp 0x00007fcec71fee00 dart::ThreadPool::Worker::Main+0x78
  pc 0x00005649f2235956 fp 0x00007fcec71feec0 dart::ThreadStart+0xd6

  pc 0x00007fcee3f92947 fp 0x00007fcec71fef70 /lib64/libc.so.6+0x8c947
-- End of DumpStackTrace
Target kernel_snapshot failed: Exception

FAILURE: Build failed with an exception.

* Where:
Script '/opt/flutter/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy' line: 1297
* What went wrong:
Execution failed for task ':app:compileFlutterBuildProfile'.
> Process 'command '/opt/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s
Exception: Gradle task assembleProfile failed with exit code 1
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:512:9)
<asynchronous suspension>
#2      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:242:5)
<asynchronous suspension>
#3      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:578:7)
<asynchronous suspension>
#4      FlutterDevice.runCold (package:flutter_tools/src/resident_runner.dart:534:33)
<asynchronous suspension>
#5      ColdRunner.run (package:flutter_tools/src/run_cold.dart:57:28)
<asynchronous suspension>
#6      AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:649:9)
<asynchronous suspension>
#7      AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:647:5)
<asynchronous suspension>
#8      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:641:15)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#17     main (package:flutter_tools/executable.dart:90:3)
<asynchronous suspension>

Exited

flutter doctor -v output:
$ flutter doctor -v
[✓] Flutter (Channel stable, 3.13.7, on Fedora Linux 38 (Workstation Edition) 6.5.6-200.fc38.x86_64, locale en_US.utf8)
    • Flutter version 3.13.7 on channel stable at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2f708eb839 (6 days ago), 2023-10-09 09:58:08 -0500
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /home/luke/Android/Sdk
    • Platform android-UpsideDownCake, build-tools 33.0.1
    • Java binary at: /opt/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 16.0.6 (Fedora 16.0.6-3.fc38)
    • cmake version 3.27.7
    • ninja version 1.11.1
    • pkg-config version 1.8.0

[✓] Android Studio (version 2022.2)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 73.0.2
    • Dart plugin version 222.4582
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.83.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.74.0

[✓] Connected device (4 available)
    • Pixel 7 Pro (mobile)       • 29161FDH300BLP • android-arm64  • Android 13 (API 33)
    • sdk gphone x86 64 (mobile) • emulator-5554  • android-x64    • Android 13 (API 33) (emulator)
    • Linux (desktop)            • linux          • linux-x64      • Fedora Linux 38 (Workstation Edition) 6.5.6-200.fc38.x86_64
    • Chrome (web)               • chrome         • web-javascript • Google Chrome 118.0.5993.70

[✓] Network resources
    • All expected network resources are available.

• No issues found!

This only happens in the stable channel, it doesn't happen with the beta channel. (I didn't check main or master.)

/cc @rmacnak-google @a-siva

GC crashes are not debuggable from stack traces. Please provide a reproduction.


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thank you. I'm merging this right away.


Migrate to trivy-operator from starboard-operator and remove starboard-exporter

When https://github.com/aquasecurity/trivy-operator/pull/96 get's merged and get's released, we will be able to depricate the usage of https://github.com/giantswarm/starboard-exporter.
Other then update the helm charts we also need to update the grafana dashboard to use the new metrics.

Starboard is being deprecated as we know and now when we want to upgrade to 1.25 we need to patch it since it contains old PDB/HPA versions.


Some examples don't work in version 0.6.0

Describe the bug
mesa runserver doesn't work in example rainfall  and population.
dependencies' version: mesa_geo = 0.6.0, mesa = "^2.1.2"
rasterio = "1.3.8.post2"
Traceback (most recent call last):
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/examples/rainfall/run.py", line 1, in <module>
    from rainfall.server import server
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/examples/rainfall/rainfall/server.py", line 46, in <module>
    server = mesa.visualization.ModularServer(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/.venv/lib/python3.11/site-packages/mesa_viz_tornado/ModularVisualization.py", line 354, in __init__
    self.reset_model()
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/.venv/lib/python3.11/site-packages/mesa_viz_tornado/ModularVisualization.py", line 381, in reset_model
    self.model = self.model_cls(**model_params)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/examples/rainfall/rainfall/model.py", line 77, in __init__
    self.space.set_elevation_layer("data/elevation.asc.gz", crs="epsg:4326")
  File "/Users/songshgeo/Documents/VSCode/mesa_geo/examples/rainfall/rainfall/space.py", line 37, in set_elevation_layer
    with gzip.open(elevation_gzip_file, "rb") as elevation_file:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/gzip.py", line 58, in open
    binary_file = GzipFile(filename, gz_mode, compresslevel)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/gzip.py", line 174, in __init__
    fileobj = self.myfileobj = builtins.open(filename, mode or 'rb')
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'data/elevation.asc.gz'

Expected behavior
Open website and run server.
To Reproduce
It occurs when I run the example in a new virtual env:
pip install mesa-geo
mesa runserver rainfall

Additional context
It works when I switch to 0.5.0 version.

Sorry about this. This is probably because all examples have been moved from this repo (https://github.com/projectmesa/mesa-geo/issues/128) to the mesa-examples repo under its gis folder.
However these gis examples are not yet updated to mesa-geo v0.6.0 (https://github.com/projectmesa/mesa-examples/issues/59). There is a small issue with the old mesa-via-tornado visualization that labels and colors are missing (https://github.com/projectmesa/mesa-viz-tornado/issues/26).

Should be fixed now that https://github.com/projectmesa/mesa-examples/pull/66 is merged.


Hi @UsulPro, I'm sorry I missed that thing:fearful:.
Thank you for giving me an issue BTW~ :grin:
You can contribute it or just waiting for my fixing....

Thank you, i will wait))

https://github.com/BosNaufal/react-scrollbar/pull/4


Bulk editor causes annotations to disappear

When you select all annotations, go to bulk editor, refresh, then change them to a different activity or group, hit enter; all of the annotations disappear. A refresh in the main window does not work to display then. Re-loading the file does not work to display them. If you re-start VARS and re-open the video, they are there (and changed).

Yep. Confirmed this bug. Not sure what's going on yet.

Fixed the bulk editors rename annotation. However, using undo on it also causes the annotations to disappear.

I changed the mechanism that refreshes the view after bulk edit changes. Appears to work fine now.


[Question] Show Fajr for the next day after Isha

Please follow the general troubleshooting steps first:

[x] I've Read the official README v1 or README v2?
[x] I've Read the official API reference?

Question related to which version: Common
Description
I have a question about Isha prayer exactly after Isha prayer.  So once Isha is done I'm getting a none enum case and I want to show Fajr for the next day.. I tried with:
 void _getPrayersForTomorrow() {     var newDate = new DateTime(nextPrayerTime.value.year,         nextPrayerTime.value.month, nextPrayerTime.value.day + 1);     nextPrayer.value = prayerTimes.value.nextPrayerByDateTime(newDate);   }
but I still get none as praying time... is there any workaround to archive that?
Selam

Yes, I've implemented a workaround for this scenario, but that's in Kotlin.
You may get ideas from Kotlin codes too.
Workaround: https://gist.github.com/iamriajul/2cdbc15d4fd0e8bad203205c9302a54b

Oh, thanks for it :) it helps a lot 👍🏻


perf(ui/steps): add class

Codecov Report

Merging #378 (17d4943) into dev (6b40718) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev     #378   +/-   ##
=======================================
  Coverage   96.39%   96.40%
=======================================
  Files         209      209
  Lines        4915     4922    +7
  Branches     1034     1032    -2
=======================================
+ Hits         4738     4745    +7
  Misses        177      177

Impacted Files
Coverage Δ

packages/varlet-ui/src/steps/Steps.vue
100.00% <100.00%> (ø)

packages/varlet-ui/src/icon/Icon.vue
100.00% <0.00%> (ø)

packages/varlet-ui/src/image/Image.vue
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[ASCII-1875] Fix flaky e2e subcommand check test

What does this PR do?

Wrap the flaky test in an Eventually, as this seems to fail due to running the command too soon.
Motivation

The test should not flake.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

It was not a race, the command was fixed by https://github.com/DataDog/datadog-agent/pull/26482


User feedback for a feature

User - "Very unnerving scanning a qr code and then not seeing the address. I don't see the address until AFTER I've sent it"
Anant's reply: "Good point - though new users dont worry abiut that, we should find a way where you can see the address if you want to. Makes sense."

@cakesoft-swati This is a development issue. From the screen above at the @ button, that's where the wallet address is supposed to be.


Add new tests for CVE list table

Codecov Report
Patch coverage has no change and project coverage change: +1.60 :tada:

Comparison is base (6e2479f) 81.83% compared to head (6862ae9) 83.44%.

:exclamation: Current head 6862ae9 differs from pull request most recent head e5edc50. Consider uploading reports for the commit e5edc50 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #99      +/-   ##
==========================================
+ Coverage   81.83%   83.44%   +1.60%
==========================================
  Files          34       34
  Lines         622      622
  Branches      157      157
==========================================
+ Hits          509      519      +10
+ Misses        113      103      -10

see 4 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Context - Access commit history

Issue
It would be nice to be able to ask something based on previous commit:

do the same changes as the last commit, but for euros instead of dollars

Version and model info
No response

Thank you for filing this issue.
The last changes should be part of the chat history and get send to the LLM again, so you do not need last diffs while the chat history is available.
If you start aider fresh and want to have the last diff in the chat history, you can try ->
/run git diff HEAD~1

That should produce the last commit diff and it should get included in the chat history, so the LLM sees it. Increase the number after the tilde get include more past commits.

This is a very handy trick, thank you!

As this issue appears to be resolved, I'm closing it.
If any new related concerns arise, please feel free to comment, and I'll reopen the issue.

The /help command does not know this /run trick apparently.
Maybe the aider doc online could also benefit of this example as a way to add context?

PR with new tips section is out

Thank you! 🙏


bug (core): pop-checkbox value does not show up in formData on submit

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I agree to follow the Code of Conduct.
[X] I have searched for existing issues that already report this problem, without success.

Poppy UI Version
v1.x
Current Behavior
When a form is submitted, the pop-checkbox name and value are not in form data
Expected Behavior
have the name and value in form data
Steps to Reproduce

create form with a pop-checkbox in it
check the pop-checkbox
submit
log the formData
no pop-checkbox in form data

Code Reproduction URL
No response
Additional Information
No response

In addition, the name is not reflected in the pop checkbox instance.


Some images fail to display in  generated PDF

I am generating pdf from a docusaurus v2 site that contains many large images. I have not been able to generate a pdf where all images are displayed.
Found this: https://stackoverflow.com/a/24685599. Could this be the source of the problem?

Same here.

@dannief I managed to resolve the issue, you can try and see if that helps in your case as well.

@lidkxx The fix described in pull request https://github.com/kohheepeace/mr-pdf/pull/36, doesn't work for me. See Issue https://github.com/kohheepeace/mr-pdf/issues/46


Build the structure and handle the task input

Hello 😊,
In this Pull request, I have made the following:-

Create the app using CRA
Add main components like Header, containers, to-do Item
Add style to these components

Thanks 😇

Very good job, your app looks great, it runs and everything works.
Though, there are some things that need changes - according to the instructions:

Your README file should be descriptive - Yours is the one from CRA;
Linters are not set up in your project - Check this link for the react projects Linters.


Added typescript prompt for keepmetadata

This PR adds keepMetaData type to Sharp instance.
See #3908 for more context.

Thank you for the PR, please can you add a test case to sharp.test-d.ts for this to help prevent regression.

Thank you!


JSX: Add support for JSXSpreadAttribute

This allows spreading an object into props/attributes

// same as (except the expansion happens at runtime

Last JSX PR for this time. I think everything should be implemented after this.

LGTM

Thanks. I'll clean up the comments.


[$250] Standardize Error Periods

I noticed some of our error messages have periods, and some don't. Let's standardize the rule here.
Tagging marketing for confirmation on the rule!
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bae2463fd69274c1
Upwork Job ID:<PHONE_NUMBER>343596032
Last Price Increase: 2024-03-27

Let's standardize on using periods for all error messages please!

Proposal
Please re-state the problem that we are trying to solve in this issue.
Standardize Error Periods
What is the root cause of that problem?
As mentioned here by @NickTooker , we need to add periods for all the error messages. we can do it for all the error messages here :
https://github.com/Expensify/App/blob/d8361eee3486ccb5472060f2af7655e96461471e/src/languages/en.ts#L222-L237
What changes do you think we should make in order to solve the problem?

We can add . to the end of all the error messages here like this :
error: {
    invalidAmount: 'Invalid amount.',
    acceptTerms: 'You must accept the Terms of Service to continue.',
    phoneNumber: `Please enter a valid phone number, with the country code (e.g. ${CONST.EXAMPLE_PHONE_NUMBER}).`,
    fieldRequired: 'This field is required.',
    requestModified: 'This request is being modified by another member.',
    characterLimit: ({limit}: CharacterLimitParams) => `Exceeds the maximum length of ${limit} characters.`,
    characterLimitExceedCounter: ({length, limit}) => `Character limit exceeded (${length}/${limit}).`,
    dateInvalid: 'Please select a valid date.',
    invalidDateShouldBeFuture: 'Please choose today or a future date.',
    invalidTimeShouldBeFuture: 'Please choose a time at least one minute ahead.',
    invalidCharacter: 'Invalid character.',
    enterMerchant: 'Enter a merchant name.',
    enterAmount: 'Enter an amount.',
    enterDate: 'Enter a date.',
}

Similarly, we can do this for es.ts file as well like this :
        error: {
            invalidAmount: 'Importe no válido.',
            acceptTerms: 'Debes aceptar los Términos de Servicio para continuar.',
            phoneNumber: `Introduce un teléfono válido, incluyendo el código del país (p. ej. ${CONST.EXAMPLE_PHONE_NUMBER}).`,
            fieldRequired: 'Este campo es obligatorio.',
            requestModified: 'Esta solicitud está siendo modificada por otro miembro.',
            characterLimit: ({limit}: CharacterLimitParams) => `Supera el límite de ${limit} caracteres.`,
            characterLimitExceedCounter: ({length, limit}) => `Se superó el límite de caracteres (${length}/${limit}).`,
            dateInvalid: 'Por favor, selecciona una fecha válida.',
            invalidDateShouldBeFuture: 'Por favor, elige una fecha igual o posterior a hoy.',
            invalidTimeShouldBeFuture: 'Por favor, elige una hora al menos un minuto en el futuro.',
            invalidCharacter: 'Carácter invalido.',
            enterMerchant: 'Introduce un comerciante.',
            enterAmount: 'Introduce un importe.',
            enterDate: 'Introduce una fecha.',
        },

What alternative solutions did you explore? (Optional)
N/A

@getusha only gotcha that comes to mind is how should we approach testing for this?

Updated Proposal

@getusha only gotcha that comes to mind is how should we approach testing for this?

@grgia the idea of having a lint rule for it sounds good.

I understand your reasoning @ShridharGoel, but the bounty reflects the priority of this issue. $250 is fair as it's low priority and does not impact any user flows. Are you still interested in taking this on?

PR in review

@ShridharGoel it looks like the automatic offer failed for some reason - I just created a manual offer for this issue  I'll pay out once you accept!

Payouts due:

[ ] Contributor: $250 @ShridharGoel Upwork
[ ] Contributor+: $250 @getusha Upwork


Using ansible-nas without the "nas" / share creation

Is your feature request related to a problem? Please describe.
I am looking for a project to help streamline the deployment of many of these media server / htpc apps (primarily the downloading-focused apps). This appears to be one of the most active and well-documented of the ones I've found. Unfortunately, I haven't been able to tell if this can be used easily in a configuration like mine where I have a dedicated NAS and a dedicated application/service server. I mount the NAS via NFS to the VMs on my application server.
Describe the solution you'd like
I would like to be able to tell ansible-nas how to access my existing file storage (via NFS mount) and then have it skip the deployment/creation of any storage or shares of its own. It should continue to perform all other responsibilities like docker configuration but just point everything at my existing storage.
Describe alternatives you've considered
Mounting my storage on the system/VM that I will target with ansible-nas and letting it make a share on top of a share (this feels very wrong)
Additional context
Maybe ansible-nas can already do what I'm looking for and I just haven't figured that out yet. In that case, I'd like to request better documentation that supports this use-case. Fwiw, I am very new to ansible and I recognize that if I had more experience, I could likely answer this question by digging through the configuration files. I am going to attempt to do this anyway but I wanted to leave a record of this request in case it results in a quicker answer and a better reference for those who follow.
Thanks for this awesome project!

Answering my own question here, this appears to be possible by appending --skip-tags "nfs,samba" to the ansible-playbook command like so: ansible-playbook -i inventories/my-nas/inventory nas.yml --skip-tags "nfs,samba"
This results in ansible skipping the installation of the samba and nfs role but it still attempts to use the samba_shares_root var to mount inside the various containers. As far as I can tell, this is the behavior I want since I can now manually mount an external share at the path that I will point samba_shares_root at.
I will leave this open for now, pending review from Dave just in case I am making an assumption that might tragically break things down the road. Based on my limited review of the code though, it doesn't seem that any of the containers are mounting the share via samba. They all appear to bind mount the local path so I think I'm in the clear. Please confirm.


CMS文章管理-点击无法新增新文章

Bug Report or Feature Request (mark with an x)

[ ] Bug report -> please search issues before submitting
[X] Feature request
[ ] Documentation issue or request

What is expected?

CMS文章管理-点击无法新增新文章

What is actually happening?

功能待开发

It's working in progress

done


simplify snap packaging configuration.toml processing during buildtime

🚀 Feature Request
Relevant Package

 This feature request is for the snap packaging
The current snapcraft.yaml is quite duplicative in processing the configuration.toml files, doing each one after the other. We should refactor this to do this in a for loop

I'm working on this now, and will include it as a part of my PR which removes most, if not all of the snap configuration edits applied to services sourced from edgex-go, in favor of environment variable overrides as used in our docker-compose files.

I'm working on this now, and will include it as a part of my PR which removes most, if not all of the snap configuration edits applied to services sourced from edgex-go, in favor of environment variable overrides as used in our docker-compose files.
Just pushed a branch with all the changes made. Needs a bit more testing before I submit the PR.
https://github.com/tonyespy/edgex-go/tree/snap-issue2051

Fix was merged, but typo in my commit message prevented this issue from being automatically closed.
https://github.com/edgexfoundry/edgex-go/pull/2487


Quant: fold FP16 tensors into FP32

TFLite has FP16 quantization which includes graph pattern such as
FP16 tensor -> Dequantize -> FP32 tensor -> Conv. As ONNX doesn't
take FP16 as a quantization data type, we are not folding that pattern
into FP32 tensor -> Conv where the FP32 tensor is cast from
the original FP16 tensor. The Dequantize -> FP32 tensor in the
original pattern is removed from the graph.

This should work now, but our test tool shrub should be improved to protect our code before merging this.

This should work now, but our test tool shrub should be improved to protect our code before merging this.


Feature: Crafting Manual

Description
The crafting manual is a book that displays the different recipes for crafting.

The student will use the crafting manual to select which item to craft

Functional Requirements

[x] It should be able to display the materials needed to craft an item
[x] It should be able to allow the student to proceed to the minigame when they have the required amount of materials

Acceptance Criteria

[x] It should use recipes from the crafting system
[x] It should use the material system to track materials
[x] It should use a button to confirm the choice

Dependencies

#111
#109

Definition of Done

[x] Follows the naming conventions
[x] Follows the coding conventions
[x] Meets the acceptance criteria
[x] Pull request has been opened

Missing in-between screen


Mouse over instead of click to select terminal

OS version and name: OSX 10.11.6 (15G1108)
Hyper.app version: Version 1.0.0 (<IP_ADDRESS>3)

Having to click to select a different terminal is somewhat anoying, i think mouse over should be implemented and enabled by default

I assume you mean the split panes? I don't think this is a good idea. Terminals are based a lot on the text input of users. Mouse hover to change focus could be extremely annoying.

I highly doubt this would be an expected interaction for the majority of users. I don’t like it.

Well thats my default config in all my machines and i use the shell everyday for already so many years. Its the behaviour for plan9, and its a feature supported in iterm, twm, dwm, terminator and many other window managers and terminal apps.
Despite not liking you its a useful feature already used by tons of users. But maybe i'm too old and doing unnecessary steps to achieve something bores me

On 13 Dec 2016, at 08:43, Philipp Rudloff<EMAIL_ADDRESS>wrote:
I highly doubt this would be an expected interaction for the majority of users. I don’t like it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

doing unnecessary steps to achieve something bores me

Then don't use the mouse at all, in favour of the keyboard shortcuts. (cf. #828)
I tried mouseover to switch pane for a while, but found it happening accidentally far too often, and if I'm already moving my finger adding a tap at the end isn't a big deal.

you dont have keybindings in plan9. and yes, keybindings will be nice too, but im used to the touchpad because im 99% of my time in a laptop and find it handier to use hover than having to click all the time. i don’t see why this is a problem at all for all you. even having this feature as an option even if not enabled by default.

On 13 Dec 2016, at 14:50, Ollie Ford<EMAIL_ADDRESS>wrote:
doing unnecessary steps to achieve something bores me
Then don't use the mouse at all, in favour of the keyboard shortcuts. (cf. #828 https://github.com/zeit/hyper/issues/828)
I tried mouseover to switch pane for a while, but found it happening accidentally far too often, and if I'm already moving my finger adding a tap at the end isn't a big deal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/zeit/hyper/issues/1143#issuecomment-266743075, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-luElryBXOijRAScEIh6nVvz6p5p2ks5rHqKygaJpZM4LLGSF.

I started using mouseover focus in my OS recently, and quickly learned to love it. Having the ability to mouseover a pane to focus it would be a nice to have, but it should not be enabled by default. As far as I'm aware, most people don't use that behavior.
Is this perhaps a feature that could be implemented via a plugin?

dont implement this pls

@iamstarkov There's no harm in it being implemented as an option or plugin, but I agree it would be a surprising default.

I agree, this is much better supported as a plugin. The reason for Hyper having plugins is so that use-cases like this can exist without extending Hyper's codebase and not bloating all user's config files with an extra option.

I agree, doable as plugin 👍

Yeah, this should definitely be a plugin 👍

@OJFord such default is not good, but as a plugin its totally fine 🎉

@radare I think the people that have commented here can clearly represent the Hyper community. Are you happy with it being a plugin? @albinekb's offer is amazing 🙌

I dont care if its a plugin or an option disabled by default. I just think this is a vital feature for my workflow in all machines i use. And was the first complain after testing it.
I will obviously prefer this behaviour as an option rather than a plugin and i dont think implementing this could take more than 10 lines of js. And i dont think this should be any problem for hyper which is already bloated in design already.
Up to you

On 14 Dec 2016, at 20:20, Timothy<EMAIL_ADDRESS>wrote:
@radare I think the people that have commented here can clearly represent the Hyper community. Are you happy with it being a plugin? @albinekb's offer is amazing 🙌
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I will obviously prefer this behaviour as an option rather than a plugin and i dont think implementing this could take more than 10 lines of js. And i dont think this should be any problem for hyper which is already bloated in design already.

@radare Why are you "obviously prefer[ing]" this as an option instead of a plugin? The outcome for you would be virtually the same. The argument to not bloat the code base with all kinds of features is a sensible one. The argument that an already bloated app is safe to bloat even more is not.

@kleinfreund @radare also, would like to know what is bloated about the design @CodeTheory could give insight into it 👍
On topic: I don't like the I want this. I want it now. And I'm not going to build it myself attitude, we're all doing this for fun, not profit. We're not getting paid to work on Hyper, but we still do out of passion for the software and the ideas behind it. When you're saying it will not take more than 10 lines of code to implement, why haven't you done so already in a plugin? 🤔
Just my thoughts on the subject. ❤

@radare
To add to @timneutkens's answer:

.. and i dont think implementing this could take more than 10 lines of js.

If we thought that for every little thing like this, it will end up bloated/even more bloated.

And i dont think this should be any problem for hyper which is already bloated in design already.

We're actually going to have most of the functionallity in core:plugins, like atom does
Therefore, it's a smart move to start doing stuff like this as plugins now, and not needing to take it out and then we need to make it a plugin later.
Does that answer your question(s)?

So, I think we've gathered the majority opinion from those who want to respond to this issue and I believe we'll just argue about it more if we continue to go on.
As @albinekb said; Hyper is starting to go into the direction of core plugins, like atom. So, in the future, we will push for any functionality to be inside a plugin. For things as this suggestion, which is apparently a uncommon preference, we're going to suggest that they be third party plugins since that's why we have a plugins system in the first place.
If you say that Hyper's code is bloated, why even add 10 lines of JS rather than trying to contribute with a third party package that's entirely optional? That's nonsensical to me.
What I suggest is that you either create the plugin yourself, if you know it's going to take only 10 lines of JS, or accept the very kind offer from @albinekb to create the plugin for you.
Thanks for your issue, please submit another if you have any more and we will take it into consideration just like this one.

And as i said, I'll happily make this plugin for you! 🎉  no hard feelings 💓

Also a way to visually determine which terminal have focus (with a colored border or a dimmed/greyedout filter on the non focused ones) will be good. The cursor is not the best way for the eye to find which terminal is focused

On 14 Dec 2016, at 20:20, Timothy<EMAIL_ADDRESS>wrote:
@radare I think the people that have commented here can clearly represent the Hyper community. Are you happy with it being a plugin? @albinekb's offer is amazing 🙌
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Why is this issue closed now? Is there another repository to hold the issues for plugins? should i assume @albinekb is working on this? because he hasn't been assigned to the issue? no hard feelings, im just shocked by the way you manage issues.

Why is this issue closed now?

Because it's a plugin request that @CodeTheory decided should be third-party - which I take to mean "PR welcome, but no need to keep this issue open".
@albinekb has very kindly to be said third-party for you; I for one am very appreciative of the work he and others put into Hyper, even if some of it's on plugins for features I won't use.

Also a way to visually determine which terminal have focus (with a colored border or a dimmed/greyedout filter on the non focused ones) will be good. The cursor is not the best way for the eye to find which terminal is focused
should i assume @albinekb is working on this? because he hasn't been assigned to the issue? no hard feelings, im just shocked by the way you manage issues.

You'd do well to say 'thank you', and keep quiet while waiting patiently now.

We're working on creating a GitHub project to hold the plugin ideas. We'll update the README when we do so ❤

@radare For terminal focus it was already addressed:  https://github.com/zeit/hyper/pull/905

@albinekb just reading about this discussion now, would love to have this functionality be available as a plugin! perfect 😄
is it already available?

i have downloaded latest Hyper and checked all the HPM plugins, but i can't find the plugin that allows to change focus on mouse over instead of having to click to select a different panel. Am I missing something?

Hello. Just a post-mortem point on this conversation, about the “I don't think users will agree with this feeling”.
Mouse focus is the standard behaviour in many windowed environments, unix being the first of one, but so is NeXTstep (and openstep of course), MacOS beautiful iTerm2, and even Windows with the X-Mouse microsoft supported registry hack.
So, every shell user would be able to use, at least once in his computer life, a mouse focus aimed environment.
So, regarding those historical en environmental considerations, the mouvever trick would be a great default feature.
Regards,

hyper-pane have this feature now with its config param: focusOnMouseHover
Enjoy


Problem trying to use StoryblokComponent when following tutorial

Describe the issue you're facing
I'm following the Storyblok Astro tutorial, and it looks like there's an issue in the latest version with StoryblokComponent.astro.

Reproduction
N/A
Steps to reproduce
Follow the tutorial here: https://www.storyblok.com/tp/add-a-headless-cms-to-astro-in-5-minutes
The example Page.astro and Grid.astro both import this component that doesn't seem to exist.
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 26.60 GB / 31.31 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.17.1 - ~/.asdf/installs/nodejs/18.17.1/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 10.1.0 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 8.6.11 - ~/.asdf/shims/pnpm
  Browsers:
    Chrome: 115.0.5790.110

  "devDependencies": {
    "@astrojs/cloudflare": "^7.2.0",
    "@astrojs/tailwind": "^5.0.0",
    "@storyblok/astro": "^3.0.1",
    "@vitejs/plugin-basic-ssl": "^1.0.1",
    "astro": "^3.1.2",
    "prettier": "^3.0.3",
    "prettier-plugin-astro": "^0.12.0",
    "prettier-plugin-tailwindcss": "^0.5.4",
    "tailwindcss": "^3.3.3",
    "vite": "^4.4.9"
  }

Used Package Manager
npm
Error logs (Optional)
No response
Validations

[X] Follow our Code of Conduct

Just started using StoryBlok and it happened to me also.
Could it be because I'm using pnpm?

Yeah, I'm having the same issue as well. I'm just using regular old npm.

I'm experiencing this too, both with and without '/components' in the file path. Any idea on how to get past this?

I got the same error again. Can we reopen this issue?


Add a Bookings Page for mentor/mentee

Bookings Page is where a mentor gets notified about all the new bookings and he/she could confirm cancel or reschedule a meeting.
It is also the place from which you join the meeting, and have the option to notify no-show to admin!

The no-show also can be cross-verified with vita meet, by checking if the mentor joined or not.

Hello @Rishabh-malhotraa. Can you assign me this Issue. I would like to work on this


Implement Breadcrumbs Component

Description
Implement a Breadcrumbs component in the fifth theme. So that users can navigate between pages easily.
Reference: https://www.figma.com/file/rX1jl4pa04VD9itnzneeih/Webiu?node-id=190%3A687
Changes proposed in the pull request

Implement breadcrumbs component
Implement the story for the component
Create documentation for the component

Screenshots (In case of UI changes):

Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests have passed and it does not give any unexpected error for the same.

Steps to test

npm i
npm run storybook (story will be displayed in InventoryManagementSystem/Breadcrumbs )

Resolves https://github.com/scorelab/Webiu/issues/367

@dinithminura can you review the PR please :)


Extract helper functions. Fix docstrings to reflect correct operator behavior.

Minor refactoring to make future work easier.

Coverage decreased (-0.07%) to 94.087% when pulling d2d98d00656b98705335038e4ced095dd911cf8f on cleanup_and_helpers into c1e0ce65070f8034e5b55e529d5f5f6365f055f3 on master.

Looks okay to me.


BUG: Extension doesn't pick up .trivyignore file

The extension doesn't seem to find a .trivyignore file in the root of the workspace. If I run the extension with DEBUG enabled I don't see a mention that it found the .trivyignore.

However if I run the command in the terminal for the same location, it behaves as expected.

Just confirming that i also am experiencing the same behavior.
trivy 0.49.1
vs code 1.86.2

I am experiencing the same. I am using a workspace of several repos where each has a trivyignore file.
version 0.52.2
No mentions of trivyignore here either.

We use things like Terraform modules which have embedded examples which Trivy will flag as security issues even though they're not used or referenced by our code in any way. Our CLI usage uses a trivy.yaml file (along with a .trivyignore file) which I was hoping to be able to configure the extension to use as well.


Update index.md

Updated with w3s specification

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Sorry, this doesn't improve the text whatsoever.

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


Fixed the limitation when "no of Workloads" become greater than "no o…

Fixed the limitation when "no of workloads" become greater than "no of performance matrics / no of features". Now, It will work for similarity analysis of any "no of workloads".

Removed the extra comments.


Screen goes blank when switching between tabs

I encountered a very, very odd bug. In an app with a tab bar, when I switch to the second tab, the screen flashes the contents of the tab and then goes blank. However, it only happens under very specific situations:

Only on my iPhone, i.e., not in the simulator
Only when debugging with Chrome is turned off
When I tap on a TouchableHighlight to make the transition, it seems to always happen; when I tap on the tab bar, it happens only sometimes

I know this sounds odd but I can recreate the issue reliably. Here's a screencast:

I also put together a barebones example here: https://github.com/lrettig/router-tab-bug-example
I can still interact with the blank screen. If there's a button there, I can still tap it, which leads me to believe that opacity is going to zero somewhere. My best guess is that it's a non-deterministic issue with animations, probably with the default Animations.None and NoTransition defined in Animations.js. If I set a sceneConfig on the routes in question to use a different animation--any animation--the issue appears to go away.
Here's some other things I noticed, in case it helps. If I change:
<Schema name="tab" type="switch" icon={TabIcon} />
to
<Schema name="tab" type="replace" icon={TabIcon} />
the problem goes away. If I instead change it to "push", the problem gets worse, affecting both screens. Also, in this code:
class TabIcon extends React.Component {
  render () {
    return (
      <Text
        style={this.props.selected ?
        {color: 'red'} : {color: 'black'}}>
        {this.props.title}
      </Text>
    );
  }
}

If I simplify the style code, removing this.props.selected, or remove the style code entirely, it happens much less often, but it still happens sometimes.
Note that it happens when running from packaged JS code, making this a serious production issue.
I'm completely stumped.
Here's the packages I'm running:
$ npm -v
3.3.6
$ node -v
v5.0.0
$ react-native -v
react-native-cli: 0.1.10
react-native: 0.19.0
$ grep version node_modules/react-native-router-flux/package.json
  "version": "2.1.8"

TabBar is not 'core' of this component and provided more for reference as example. It has known problems with performance (for example some methods are called several times, etc.) Any improving PR would be appreciated.

Hi Pavel, thanks for taking a look at this. I would love to try to fix it, but I don't understand the interactions among the tab bar + router + animations well enough. And I'm really struggling to understand why this issue only happens when Chrome debugging is turned off, which as you can imagine makes debugging very hard!

Could you check with latest version? I've done some changes into TabBar recently

I just tried to recreate this, using both the older (2.1.8) and latest version of the library, and I couldn't recreate it on either of two devices. No idea what happened. I'll close this.

Seeing this issue.  It happens on my iPad but not in Simulator.


updated readme for new laravel polymorphic snippets

Hi @mhmdomer, I missed out the docs in the previous PR.
Please have a look.

Also @mhmdomer , Did you release a new version after acception PR#2?

Also @mhmdomer , Did you release a new version after accepting PR2?

No, I didn't do another release yet, but I am planning to do it after merging this PR.

@chinmaypurav The README.md is listing 8 snippets but there is actually 11 snippets. could you please add the other snippets to the README.md file?


Pull coinDecimals from BitGoJS.statics

Overview
If you look at sign.js, it defines a configuration constants for each coin that the library supports.
These constants are already defined in the upstream library, BitGoJs; there is no need to create two sources of the truth.
The task: Update this library to leverage the existing constants in BitGoJS.statics.
Definition of Done

Refactor all coins to fetch their constants from BitGoJS.statics.
All tests should still pass after these changes.

Extra Credit
Are there any other constants in this library that have already been defined in BitGoJS.statics? If so, please add or create a new issue to track it -- if not, do you see any constants that might be useful to move upstream?

#65

#65

https://github.com/BitGo/key-recovery-service-v2/pull/65


drag & drop not update view or model on drag end

drag & drop not update view or model on drag end

Duplicate of #17


Query API more often than once per second

Describe the bug
I'm not sure whether this has to do with the "high load" performance issues.. but my use case demands to get, e.g. the last 10 values of an attribute more often than once per second.
Let's say my device sends values every 0.1 seconds (and that is actually a slow device). Let's assume I need to query the last 10 values of that device (ofc an attribute of that device) every 0.5 seconds.
So If I query lastN=10 values for the first time (t0) I get the correct (I assume) last 10 values. For the second query (t0+0.5s) that I get the same 10 values.
To Reproduce
As described:
Push a new value for an attribute every 0.1 seconds to orion (subscription for QL already created) - well, I used a complete chain from MQTT broker to QL but that should not matter since all the values reach cratedb.
While the device sends data continiously query QL with lastN=10 (or whatever number) more often than once a second, e.g. every 0.5s.
Expected behavior
That QL throws the actual last 10 values. In this case this would be the last 5 values of the query before plus 5 new values.
Environment (please complete the following information):
OS: Orion:2.5.2, mongoDB:4.2.2, QL:fix-256 and crateDB:4.2.2 run in docker on Ubuntu 18
A real device or a script as device simulator to send data; in my case a python file.
Some script that queries QL; in my case a python file.
Additional context
As the last time every help is much appreciated :)

few hints:

are you sure orion is sending notifications for all received data? be aware that if an update comes before the notification is queued, it will actually send only the new update.
did you try to query after more than 0.5s and see if the data were updated correctly? there is a processing time to store data, ql is not meant to be a real time api. the real time api is context broker :)

few hints:

are you sure orion is sending notifications for all received data? be aware that if an update comes before the notification is queued, it will actually send only the new update.
did you try to query after more than 0.5s and see if the data were updated correctly? there is a processing time to store data, ql is not meant to be a real time api. the real time api is context broker :)

@SBlechmann thank you so much for the detailed report!
also, w/r/t the comments above:
Notification throttling
When you create an NGSI notification there's an optional throttling field that lets you specify a notification interval in seconds. If my memory serves me well, Orion defaults it to 1 second. In practice this may result in some updates being lost in cyberspace---e.g. if you send 10 entity updates to Orion within 1 second, not all 10 of them might get notified to QuantumLeap. Can do a GET onhttp://your-orion:1026/v2/subscriptions and tell us what's the value of the throttling field in your QuantumLeap subscription?
Doing real-time
I don't think it's a good idea to use QuantumLeap for real-time processing and the whole FiWare stack for that matter, but of course YMMV. By real-time I mean the ability of a system to satisfy time constraints. If your system must meet processing deadlines (e.g. get an accurate query result every 0.5 seconds) then REST microservices aren't your friend, IMO :-)
Reproducing the bug
I tried to reproduce by taking a shortcut, by POSTing entities directly to QuantumLeap, bypassing Orion, but I had no luck reproducing the issue---yep, I suppose I took too much of a shortcut :-)

I used a complete chain from MQTT broker to QL but that should not matter since all the values reach cratedb

I'm assuming you checked all your values are in the QuantumLeap entity table, e.g. SELECT count(*) FROM .... Can you confirm that? The reason why I'm asking is that I'm trying to narrow this issue down. As it stands now it could be either a bug in QuantumLeap's query subsystem (if all entity values are in Crate) or it could be a problem with notifications, either Orion or QuantumLeap---see #416, even though I never experienced myself any data loss with the kind of load you're using. Either way we'll look into this :-)

@SBlechmann thank you so much for the detailed report!
also, w/r/t the comments above:
Notification throttling
When you create an NGSI notification there's an optional throttling field that lets you specify a notification interval in seconds. If my memory serves me well, Orion defaults it to 1 second. In practice this may result in some updates being lost in cyberspace---e.g. if you send 10 entity updates to Orion within 1 second, not all 10 of them might get notified to QuantumLeap. Can do a GET onhttp://your-orion:1026/v2/subscriptions and tell us what's the value of the throttling field in your QuantumLeap subscription?
Doing real-time
I don't think it's a good idea to use QuantumLeap for real-time processing and the whole FiWare stack for that matter, but of course YMMV. By real-time I mean the ability of a system to satisfy time constraints. If your system must meet processing deadlines (e.g. get an accurate query result every 0.5 seconds) then REST microservices aren't your friend, IMO :-)
Reproducing the bug
I tried to reproduce by taking a shortcut, by POSTing entities directly to QuantumLeap, bypassing Orion, but I had no luck reproducing the issue---yep, I suppose I took too much of a shortcut :-)

I used a complete chain from MQTT broker to QL but that should not matter since all the values reach cratedb

I'm assuming you checked all your values are in the QuantumLeap entity table, e.g. SELECT count(*) FROM .... Can you confirm that? The reason why I'm asking is that I'm trying to narrow this issue down. As it stands now it could be either a bug in QuantumLeap's query subsystem (if all entity values are in Crate) or it could be a problem with notifications, either Orion or QuantumLeap---see #416, even though I never experienced myself any data loss with the kind of load you're using. Either way we'll look into this :-)

hey there, thanks for your questions :)
regarding @chicco785 's comment:
I just reset everything, so here's what I got:
I sent 27 values in a simple loop from 1 to X, increasing by 1, one value every 0.5s. Orion shows 28 sent notifications (since 1 is created at the creation of the subscription that's the correct amount).
When I query QL for those values, they are all there and displayed correctly ordered by time_index.
In parallel to the data stream I queries QL's api also every 0.5s and here's what I got:
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:50.133'], 'values': [2.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:50.133'], 'values': [2.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:51.140'], 'values': [4.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:51.140'], 'values': [4.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:52.141'], 'values': [6.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:53.172'], 'values': [8.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:53.172'], 'values': [8.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:54.178'], 'values': [10.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:54.178'], 'values': [10.0]}
Querrying Orion in parallel gives me the correct values.
Could you please explain your 2nd point? I don't understand.
Regarding @c0c0n3 's comment:
Throttling is set to 0 - seems to work since all the data is correctly stored in crate.
Mhm.. so QL seems to be slower in this matter? But both (fiware in general) are not suupposed to serve real time applications / under high frequencies? I guess they are out of the question for electric use cases then?
I hope I didn't forget anything and my data helps in this matter :)

hey there, thanks for your questions :)
regarding @chicco785 's comment:
I just reset everything, so here's what I got:
I sent 27 values in a simple loop from 1 to X, increasing by 1, one value every 0.5s. Orion shows 28 sent notifications (since 1 is created at the creation of the subscription that's the correct amount).
When I query QL for those values, they are all there and displayed correctly ordered by time_index.
In parallel to the data stream I queries QL's api also every 0.5s and here's what I got:
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:50.133'], 'values': [2.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:50.133'], 'values': [2.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:51.140'], 'values': [4.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:51.140'], 'values': [4.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:52.141'], 'values': [6.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:53.172'], 'values': [8.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:53.172'], 'values': [8.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:54.178'], 'values': [10.0]}
{'attrName': 'presentValue', 'entityId': 'urn:ngsi-ld:Sensor:Temperature:001', 'index': ['2021-01-20T18:24:54.178'], 'values': [10.0]}
Querrying Orion in parallel gives me the correct values.
Could you please explain your 2nd point? I don't understand.
Regarding @c0c0n3 's comment:
Throttling is set to 0 - seems to work since all the data is correctly stored in crate.
Mhm.. so QL seems to be slower in this matter? But both (fiware in general) are not suupposed to serve real time applications / under high frequencies? I guess they are out of the question for electric use cases then?
I hope I didn't forget anything and my data helps in this matter :)

I actually forgot something.
So if querrying crate I get the same results as querrying QL.
And I guess for time sensitive use cases the data should be grabbed from e.g. the MQTT broker directly then?

I actually forgot something.
So if querrying crate I get the same results as querrying QL.
And I guess for time sensitive use cases the data should be grabbed from e.g. the MQTT broker directly then?

@SBlechmann context broker is the real time component of FIWARE architecture.
QuantumLeap is a Timeseries API that stores values forwarded by the Context Broker, and due to the nature of its backends as well, there is always some synch latency between the data writing and the time the data is available for reading.
In first instance you have QL takes around 80 msec to process a single message (on my machine) and store it in the database. Especially in the case of crate, indexing may take a bit, so this means that there is additional latency between when the a message is stored in crate, and when it is actually available for querying. In case of distributed deployment this can take even more because QL writes on Crate node A, first the data is indexed in node A, and then replicated on node B. So if you issue a query right after writing a message and QL picks node B, probability to find the data you just pushed is even lower.
Also, fast data indexing in the database behind QL largely depend on its configuration.
Bottomline:

real time reading? Orion
long term historical data persistency? QuantumLeap

@SBlechmann context broker is the real time component of FIWARE architecture.
QuantumLeap is a Timeseries API that stores values forwarded by the Context Broker, and due to the nature of its backends as well, there is always some synch latency between the data writing and the time the data is available for reading.
In first instance you have QL takes around 80 msec to process a single message (on my machine) and store it in the database. Especially in the case of crate, indexing may take a bit, so this means that there is additional latency between when the a message is stored in crate, and when it is actually available for querying. In case of distributed deployment this can take even more because QL writes on Crate node A, first the data is indexed in node A, and then replicated on node B. So if you issue a query right after writing a message and QL picks node B, probability to find the data you just pushed is even lower.
Also, fast data indexing in the database behind QL largely depend on its configuration.
Bottomline:

real time reading? Orion
long term historical data persistency? QuantumLeap

@SBlechmann thanks so much for the analysis and time you put into this, it really helps!

But both (fiware in general) are not suupposed to serve real time applications / under high frequencies?

It depends on what your definition of real time is and how high is a high frequency in your case :-) In general, I reckon the whole FiWare architecture was built more with extensibility, ease of use and openness in mind than high performance. Witness the extensive use of HTTP, JSON, microservices, etc. none of which are really a good option for high performance computing. As for real time, if we took Wikipedia's definition of real time

software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines".

then my conclusion would be: FiWare is not suitable for real time applications. In general, microservices architecture are ill suited for real time applications since there's no way you can guarantee any deadline will be met---e.g. think how the proliferation of networked processes required to carry out a task affects latency.

I guess they are out of the question for electric use cases then?

It depends. If you don't have strict real time requirements, then FiWare could well be an option. I would test at scale though since things will likely be very different than the happy laptop scenario the moment you have hundreds of devices pumping data through agents, context broker, etc.

I guess for time sensitive use cases the data should be grabbed from e.g. the MQTT broker directly then?

That would definitely help performance as well as batching.

@SBlechmann thanks so much for the analysis and time you put into this, it really helps!

But both (fiware in general) are not suupposed to serve real time applications / under high frequencies?

It depends on what your definition of real time is and how high is a high frequency in your case :-) In general, I reckon the whole FiWare architecture was built more with extensibility, ease of use and openness in mind than high performance. Witness the extensive use of HTTP, JSON, microservices, etc. none of which are really a good option for high performance computing. As for real time, if we took Wikipedia's definition of real time

software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines".

then my conclusion would be: FiWare is not suitable for real time applications. In general, microservices architecture are ill suited for real time applications since there's no way you can guarantee any deadline will be met---e.g. think how the proliferation of networked processes required to carry out a task affects latency.

I guess they are out of the question for electric use cases then?

It depends. If you don't have strict real time requirements, then FiWare could well be an option. I would test at scale though since things will likely be very different than the happy laptop scenario the moment you have hundreds of devices pumping data through agents, context broker, etc.

I guess for time sensitive use cases the data should be grabbed from e.g. the MQTT broker directly then?

That would definitely help performance as well as batching.

All right then.
Then the application needs to take care of some kind of stash itself, thanks 👍 that's already a good output of this discussion :)
I will conduct some further "performance tests" in regards to lots of devices sending data then with a clustered setup soon.

All right then.
Then the application needs to take care of some kind of stash itself, thanks 👍 that's already a good output of this discussion :)
I will conduct some further "performance tests" in regards to lots of devices sending data then with a clustered setup soon.

@SBlechmann

I will conduct some further "performance tests" in regards to lots of devices sending data then with a clustered setup soon.

Cool, good idea! There's a couple of things I'd mention based on our experience running FiWare stacks in a cluster just in case. In general, you should be able to get good performance out of the box---some components like Orion can handle loads of requests per second without a glitch. Like I said hard real time may not be FiWare's forte but you can still get very good performance out of a FiWare stack which brings me to the next point.  I've experienced myself situations where I initially thought FiWare was the bottleneck meanwhile my cluster configuration was preventing containers from being scheduled properly. (D'oh!

Cool, good idea! There's a couple of things I'd mention based on our experience running FiWare stacks in a cluster just in case. In general, you should be able to get good performance out of the box---some components like Orion can handle loads of requests per second without a glitch. Like I said hard real time may not be FiWare's forte but you can still get very good performance out of a FiWare stack which brings me to the next point.  I've experienced myself situations where I initially thought FiWare was the bottleneck meanwhile my cluster configuration was preventing containers from being scheduled properly. (D'oh!


SSL fails on the 0.7.xx

This is what i get on 0.7.xx - but 0.6.22 works fine. I need it to connect to heroku pg.
{ [error: no pg_hba.conf entry for host "<IP_ADDRESS>", user "fedgqabajgfoik", database "dbrqbkbd9pmvci", SSL off]
  name: 'error',
  length: 160,
  severity: 'FATAL',
  code: '28000',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  file: 'auth.c',
  line: '486',
  routine: 'ClientAuthentication' }

// The way i connect is:
  var knex = require('knex')({
    client: 'pg',
    debug: true,
    connection: 'postgres://user:pass@host:5432/db?ssl=true'
  });

I seem to be having this issue as well in version 0.8.6.

I am also on 0.8.6 and also getting the same issue.

For now, this works:
var Knex = require('knex');
var URL = require('url');
var pg_server = URL.parse(process.env.DATABASE_URL);
var knex = Knex({
  	client: 'pg',
  	connection: {
		host: pg_server.hostname,
		port: pg_server.port,
		user: pg_server.auth.split(':')[0],
		password: pg_server.auth.split(':')[1],
		database: pg_server.path.substring(1),
		ssl: true
	}
});


Unset value (for --sim)

X is the default, unset value.  It may be nice to be able to set something to this as well.

After thinking about this more, I don't think its something we should implement right now until more people request it.


fix: remove unused 'django-celery-results' to prevent WALs problems

Remove the unused 'django-celery-results' from dependencies to prevent WALs problems in storages like postgresql. The module isn't used and we need to any ressources usages if we don't need to.
Also, this MR bump cryptography for safety:
-> Vulnerability found in cryptography version 39.0.0
Vulnerability ID: 53048
Affected spec: >=1.8,<39.0.1
ADVISORY: Cryptography 39.0.1 includes a fix for CVE-2023-23931: In
affected versions 'Cipher.update_into' would accept Python objects which
implement the buffer protocol, but provide only immutable buffers. This would
allow immutable objects (such as 'bytes') to be mutated, thus violating
fundamental rules of Python and resulting in corrupted output. This issue has
been present since 'update_into' was originally introduced in cryptography
1.8.https://github.com/pyca/cryptography/security/advisories/GHSA-w7pp-m8wf-vj6r
CVE-2023-23931
For more information, please visit https://pyup.io/v/53048/f17

Codecov Report
Patch and project coverage have no change.

Comparison is base (e5da490) 100.00% compared to head (c9f57ce) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##             alpha       #31   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          608       608
  Branches        48        48
=========================================
  Hits           608       608

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


DOCS: add sphinx theme

This PR adds the sphinx theme to the docs.
At the moment it does not build properly but, I am putting it here so David Garcia our contractor can look it over.
I will send him the link to this repo.
For now this PR is a draft

@dgarcia360 thank you for the review. can you please check once more?

@lauranovich  Looks good to me. However, the build fails because cannot build the previous book. To solve this, please remove this file .github/workflows/book.yml

We would like to keep the book job, because building mdbook also runs compile checks for all the examples, which is important for preventing regressions. Also, mdbook is a standard docs format for Rust, so it makes sense to keep it in parallel to the unified sphinx format that Scylla uses. Please copy all the files needed for sphinx instead of moving them to keep the book building job operable.

Please copy all the files needed for sphinx instead of moving them to keep the book building job operable.

Would it be possible to keep the files with content in one place? If we copy the files, we will have to remember to do the same changes for both rust book and sphinx docs, and we risk that they become out of sync.

Please copy all the files needed for sphinx instead of moving them to keep the book building job operable.

Would it be possible to keep the files with content in one place? If we copy the files, we will have to remember to do the same changes for both rust book and sphinx docs, and we risk that they become out of sync.

That would be even better, yes. I assumed that both sphinx and mdbook expect the files to be in a specific directory structure, but if they can be unified, it would be best.

We should be able to keep both builds. Instead of moving the original MarkDown files under the docs/source folder, we could:

Move back the MarkDown files to book/src, where they were initially.
Add soft links in docs/source to the original folder to avoid having duplicated contents.

We are following a similar approach in https://github.com/scylladb/java-driver. In this other repository, the original docs are defined outside the docs folder.
How to create symbolic links
@lauranovich After moving back the MD files to book/src, we can create the symbolic links. To create them, I'd enter the following instructions within the command line prompt (within the docs/source) folder:
ln -s ../../README.md index.md
ln -s ../../book/src/quickstart quickstart
ln -s ../../book/src/connecting connecting
ln -s ../../book/src/queries queries
ln -s ../../book/src/data-types data-types
ln -s ../../book/src/load-balancing load-balancing
ln -s ../../book/src/retry-policy retry-policy
ln -s ../../book/src/metrics metrics
ln -s ../../book/src/logging logging
ln -s ../../book/src/tracing tracing
ln -s ../../book/src/SUMMARY.md SUMMARY.md
ln -s ../../book/src/title-page.md title-page.md

@lauranovich We should be able to keep both builds. We could:

Move book.yaml under docs.
In book.yaml, change src = "src" to src = "source" (L7).
Change the GitHub Action .github/workflows/book.yml to build the book from the docs folder. Replace:

L30: mdbook build book -> mdbook build docs
L32 run: SCYLLA_URI=scylladb:9042 mdbook test -L target/debug/deps book -> run: SCYLLA_URI=scylladb:9042 mdbook test -L target/debug/deps docs

@psarna if you want me to reinstate the book directory let me know.

Github reports that this series adds 284 files, most of which are in _build directory, which was also (later) added to .gitignore. Perhaps you need to remove them manually from the git tree?

could you review and verify if these additions interact with book generation? Will mdbook be able to process them without issues?

@psarna The MD book will the RST text in raw, but it does not prevent the build from building for validation purposes:

@dgarcia360 and @psarna - I implemented the changes. Please let me know if something else needs to be done.

@cvybhu would it be hard to add a small script to book generation which goes over all files and removes all the ```eval_rst blocks? We certainly don't want these blocks to be visible in the book.

I am a bit confused here.
The idea of this PR is to replace https://cvybhu.github.io/scyllabook/index.html with the branded docs that use the Scylla theme.
Why do we need to build a book?
once this is merged, we can change the link in the readme

mdbook is the standard way of producing Rust docs, so there's value in maintaining a working version of it, side by side with branded Scylla docs. If the whole cost of maintaining a fully working mdbook build is to add a script which drops ```eval_rst, then I think it's worth it. For instance, external pages which gather and present docs for Rust projects won't be interested in branded Scylla documentation, but they will be in a standard mdbook format, which would help the driver gain more traction.

ok so let's do that. @psarna if the rest of the PR is good and all we need is this script can we merge and then add the script afterwards?

@lauranovich There is still a minor comment open from my side: https://github.com/scylladb/scylla-rust-driver/pull/215/files#r616040702

@dgarcia360 thanks David - done!

I created a script which takes these .md sources, removes ```eval_rst parts and builds the documentation book:
https://gist.github.com/cvybhu/3874df86a64d146645d13d48fe389e37
To use it just run:
python3 build_book.py

In the base directory
The generated HTML will be in docs/book/scriptbuild/book
Original files are not changed by this script, all changes are done on copies

@dgarcia360 - all changes are in
@psarna I can't fix this conflict as I don't have write access.

@psarna - if you're happy we can merge this and make the rest of the corrections in a different PR.


Retain RenderMaterialInstances and RenderMeshMaterialIds from frame to frame.

This commit makes Bevy use change detection to only update RenderMaterialInstances and RenderMeshMaterialIds when meshes have been added, changed, or removed. extract_mesh_materials, the system that extracts these, now follows the pattern that
extract_meshes_for_gpu_building established.
This improves frame time of many_cubes from 3.9ms to approximately 3.1ms, which slightly surpasses the performance of Bevy 0.14.

CI is failing

Maybe #16825 should land first, so we can make sure meshlets don't regress.

I don't know what happened to this branch, but I needed to force-push to fix it, sorry.

@tychedelia Done

I'm going to close and resubmit this so that the commit history is cleaned up.