0.5.0 ERROR Failed to read config error=yaml: unmarshal errors:

The Homebrew test block fails for 0.5.0, but passed for 0.4.5
https://jenkins.brew.sh/job/Homebrew Core Pull Requests/15124/
Issue description

The test block should pass.
Context

I'm trying to get 0.5.0 green in Homebrew's CI and merged. See  https://github.com/Homebrew/homebrew-core/pull/22000.

Possible Solution

Probably we just need to update the test block with some tweak to the config file.

Steps to Reproduce (for bugs)

bash-3.2$ cat test.conf
- "consumer.Profiler":
    Enable: true
    Runs: 100000
    Batches: 100
    Characters: "abcdefghijklmnopqrstuvwxyz .,!;:-_"
    Message: "%256s"
    Stream: "profile"
bash-3.2$ /usr/local/Cellar/gollum/0.5.0/bin/gollum -tc /tmp/gollum-test-20171221-61659-1kkdhlq/test.conf
[2017-12-21 13:54:13 PST] ERROR Failed to read config error=yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into map[string]tcontainer.MarshalMap
bash-3.2$

brew pull https://github.com/Homebrew/homebrew-core/pull/22000
brew install -dvs gollum
brew test -vd gollum

Your Environment
Used versions

gollum version: 0.5.0
go version: 1.9.2
Operating System and version: macOS 10.11, 10.12, 10.13

Config:

- "consumer.Profiler":
    Enable: true
    Runs: 100000
    Batches: 100
    Characters: "abcdefghijklmnopqrstuvwxyz .,!;:-_"
    Message: "%256s"
    Stream: "profile"

The test block runs
  test do
    (testpath/"test.conf").write <<~EOS
      - "consumer.Profiler":
          Enable: true
          Runs: 100000
          Batches: 100
          Characters: "abcdefghijklmnopqrstuvwxyz .,!;:-_"
          Message: "%256s"
          Stream: "profile"
    EOS

    assert_match "parsed as ok", shell_output("#{bin}/gollum -tc #{testpath}/test.conf")
  end

As stated in the release notes the configuration format changed for gollum 0.5.0
Your config should now look like this
Profiler:
    Type: consumer.Profiler
    Enable: true
    Runs: 100000
    Batches: 100
    Characters: "abcdefghijklmnopqrstuvwxyz .,!;:-_"
    Message: "%256s"
    Streams: "profile"

also see https://github.com/trivago/gollum/blob/master/config/profile.conf

Also the result of gollum -tc should now be
Testing config testpath/test.conf
Config OK.

bash-3.2$ cat test.conf
Profiler:
    Type: consumer.Profiler
    Enable: true
    Runs: 100000
    Batches: 100
    Characters: "abcdefghijklmnopqrstuvwxyz .,!;:-_"
    Message: "%256s"
    Streams: "profile"
bash-3.2$ /usr/local/Cellar/gollum/0.5.0/bin/gollum -tc /tmp/gollum-test-20171221-61985-vge4co/test.conf
Testing config /tmp/gollum-test-20171221-61985-vge4co/test.conf
[2017-12-21 14:05:57 PST] ERROR Configure pass failed. error=No valid producers found
bash-3.2$

Ah - my bad. Please use the file I linked above or take the producer part from it.
P.s.: Additional answers from my side might be delayed until tomorrow morning (CET)

Works! Perfect. Thank you :)

:+1: thank you for keeping track of the homebrew package!

 :)


feat!: split Avro4s functionality into its own project

This does not decouple the core kafka4s from Avro, which I have tried to do in the past and gotten stuck. The purpose of this is not to allow for JSON or something, but to allow for Vulcan.
These changes are breaking, but all the same functionality that existed before is still supported in some form.

Spiking Vulcan before merging to ensure that this is the right seam.

Have spiked Vulcan. This looks like the right seam.


Make falco.httpOutput.url always take precedence. Fixes #280

What type of PR is this?
/kind bug
/kind chart-release
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart
/area falcosidekick-chart
What this PR does / why we need it:
When including the Falco helm chart inside a parent chart, that messes with the way the falcosidekick Service name gets generated, which in turn means falco can't send notifications. A user might expect that they could override this behavior by setting falco.httpOutput.url but currently that value is ignored if falcosidekick is enabled.
This PR fixes that issue by always allowing falco.httpOutput.url to override the auto-generated URL.
Which issue(s) this PR fixes:
Fixes #280
Special notes for your reviewer:
Quick way to test:
$ cd falco/
$ helm template . --set falcosidekick.enabled=true | grep -A 3 "http_output"
    http_output:
      enabled: true
      url: |
        http://RELEASE-NAME-falco-falcosidekick:2801

$ helm template . --set falcosidekick.enabled=true --set falco.httpOutput.url=http://customurl | grep -A 3 "http_output"
    http_output:
      enabled: true
      url: |
        http://customurl

Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mac-chaffee
To complete the pull request process, please assign bencer after the PR has been reviewed.
You can assign the PR to them by writing /assign @bencer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @mac-chaffee! It looks like this is your first PR to falcosecurity/charts 🎉

CC @Issif

LGTM label has been added.  Git tree hash: 6fe41eda128b3c1dcbc0e8e658fbd5e1ac944359

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, mac-chaffee
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

falco/OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Word wrap

Also tabulators causing problems.

Fixed. Still some other minor issues which will be fixed.


Dockerfile refers missing file

Dockerfile refers to /scs-commerce.nginx.now.conf but it doesn't exist!

see #2


Python interactive window does not start with conda virtual environment: error: Starting Jupyter has timedout. Please check the 'Jupyter' output panel for further details.

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

Ctrl + Shift + P , Python: Start interactive window
Or open ipynb notebook

Actual behavior
Message "waiting kernel to be idle" shown for several minutes, then times out.
Expected behavior
Python interactive window starts

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local

Extension version: 2020.4.76186

VS Code version: 1.44.2

Setting python.jediEnabled: false

Python and/or Anaconda version: Python 3.7.7 , Anaconda: 4.8.3

OS: Windows | Mac | Linux (distro): Windows

Virtual environment: conda

Developer Tools Console Output

Console output:
Kernel started: 1e003730-186e-4bb5-bbf2-225fa78bf1f1
_cffi_ext.c
C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\cffi\__pycache__\_cffi_ext.c(266): fatal error C1083: Cannot open include file: 'sys/un.h': No such file or directory
Traceback (most recent call last):
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel_launcher.py", line 15, in <module>
    from ipykernel import kernelapp as app
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel\__init__.py", line 2, in <module>
    from .connect import *
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel\connect.py", line 18, in <module>
    import jupyter_client
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\jupyter_client\__init__.py", line 4, in <module>
    from .connect import *
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\jupyter_client\connect.py", line 21, in <module>
    import zmq
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\__init__.py", line 47, in <module>
    from zmq import backend
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\__init__.py", line 40, in <module>
    reraise(*exc_info)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\utils\sixcerpt.py", line 34, in reraise
    raise value
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\__init__.py", line 27, in <module>
    _ns = select_backend(first)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\select.py", line 28, in select_backend
    mod = __import__(name, fromlist=public_api)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\cython\__init__.py", line 6, in <module>
    from . import (constants, error, message, context,
ImportError: DLL load failed: The specified module could not be found.
[I 00:26:24.654 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
_cffi_ext.c
C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\cffi\__pycache__\_cffi_ext.c(266): fatal error C1083: Cannot open include file: 'sys/un.h': No such file or directory
Traceback (most recent call last):
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel_launcher.py", line 15, in <module>
    from ipykernel import kernelapp as app
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel\__init__.py", line 2, in <module>
    from .connect import *
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\ipykernel\connect.py", line 18, in <module>
    import jupyter_client
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\jupyter_client\__init__.py", line 4, in <module>
    from .connect import *
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\jupyter_client\connect.py", line 21, in <module>
    import zmq
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\__init__.py", line 47, in <module>
    from zmq import backend
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\__init__.py", line 40, in <module>
    reraise(*exc_info)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\utils\sixcerpt.py", line 34, in reraise
    raise value
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\__init__.py", line 27, in <module>
    _ns = select_backend(first)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\select.py", line 28, in select_backend
    mod = __import__(name, fromlist=public_api)
  File "C:\Users\ARUN\Miniconda3\envs\dsenv\lib\site-packages\zmq\backend\cython\__init__.py", line 6, in <module>
    from . import (constants, error, message, context,
ImportError: DLL load failed: The specified module could not be found.

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

@karnn Thanks for reporting this and sorry about the issue. A couple of quick things to try:

If you start up a terminal with that dsenv conda env activated does running "python -m jupyter notebook" correctly start up a notebook server?
If you pick the command "Python> Select interpreter to start juypter server" do you have the same env selected there?

@IanMatthewHuff
Thanks for your response

Yes jupyter notebook opens normally

I hadn't checked this option before. I always do Python > select interpreter. Can these two be different?

Today when I redid Python > Select interpreter to start jupyter server, and Python > Open interactive window the kernel starts up normally in VScode. I would say in 70% of trials the kernel does not start up properly.

@karnn thanks for the response here. So that "Select interpreter to start juypter server" command is usually not needed. When we launch different notebook kernels we actually use the same jupyter to start them up. We usually set this for you so you don't need to see or change it. However we have seen some customers have issues with the selected jupyter interpreter so sometimes change it can help.
If you are still seeing this issue could you please save off the entire console log for when this repros? You had the errors above, but seeing the whole thing might help me diagnose this. If you right click on the log in the console tab of the developer tools you should get an option to save it. Then you can just drag that file onto a comment here and I can take a peek.

One more thing that might help. This looks like a conda environment which can sometimes be very finiky to work with. If you actually start up vscode from a conda command prompt with that dsenv environment activated that might help to pick up the correct environment for it to run.


[Identity] Migration guide (v1 to v2)

Feedback appreciated ✨
Eventually
Fixes #17490

@ramya-rao-a , @scottaddie I have meditated through the feedback you have both provided and now I have separated what goes on the CHANGELOG and what goes on the migration guide 🤔 I have the feeling this is still not perfect, but I’m sure your feedback will help me get closer to where we want this to go.


Keep rows opened

Hi,
Is there a way to keep the rows opened when clicking on other items? Instead of only one expansion at a time.
Thank you

Hi, did you find a way to do that?


fix: added arch to bpf download url

Signed-off-by: Eric Engberg<EMAIL_ADDRESS>
*What type of PR is this?
/kind bug

Any specific area of the project related to this PR?
/area build

What this PR does / why we need it:
The url for downloading the prebuild eBPF driver is missing the ARCH in the path
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

fix: Added ARCH to bpf download URL

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: eric-engberg
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Ok third time's the charm then

Yay!!
/ok-to-test

When might this get released and the helm chart updated?

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: eric-engberg, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash:<PHONE_NUMBER>7cfdfcdf661a8253bd36c042a4cb23

Next Falco release (0.33) is going to be released a couple of months from now, by the end of September!
@leogr @jasondellaluce wdyt?

Well can't really use eBPF until it's resolved.. can a patch release be done?

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: eric-engberg, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/remove-milestone 0.33.0
/milestone 0.32.2

Well can't really use eBPF until it's resolved.. can a patch release be done?

Hey @eric-engberg thank you for all your help, the patch release is finally here :loud_sound: !!
https://github.com/falcosecurity/falco/releases/tag/0.32.2


Api completion & parametrized XML tests

Added XML API specification
Added parametrized tests for API completeness
Fixed found issues

Thanks @ml31415 - A couple of tests failing on 3.9 but can fix on develop.

Thanks for merging. Well, how attached are you to 3.9 support? The parser makes heavy use of the typing, including internals of their implementation. As it turns out, there were some changes under the hood between 3.9 and 3.10, that now create that issue. 3.10 is the standard even in most distros now I guess. Also there is nothing stopping someone from moving from 3.9 to 3.10, as it was with py2 to py3. I'd be totally fine with supporting 3.10+ only.

Just checked https://peps.python.org/pep-0693/ py3.12 seems to be upcoming this summer, so that would probably replace 3.9 within the supported versions within a few months.

3.9 doesn't hit EOL for another 2+ years (https://endoflife.date/python) so I think it's a reasonable thing to strive for.

Alright, I'll see if there is a quick fix.
I'm personally a big fan of staying backwards compatible, if it's feasible and no extra burden. numpy_groupies e.g. still runs even with py2. But this project seems to me "fresh" enough, to not compromise too much with backwards compatibility. E.g. not using the newer pipe syntax for type unions. Or not to have to add some version forks for py3.9 for outdated typing internals. I'd rather have this lib using state of the art python, in order to avoid technical debt, that someone needs to clean up later on - and this someone possibly being me. So as long as you're not personally using it with py3.9, and no one else comes up and complains, I wouldn't bother too much about it. And if someone complains, py3.9 could easily be readded.


"Private identifers are only available when"... should not occur in .d.ts files

See https://github.com/microsoft/TypeScript/issues/60427#issuecomment-2460357068

All ambient contexts, not just .d.ts files


Please add me to the repository!

You should have an invite!

Great, I see the invite was accepted!


i18n breaks embedded viewer

Release 0.2.0 added i18n support, but this broke the unpkg script tag use of ohif.
You can replicate this in the code sandox linked from the docs:
https://codesandbox.io/s/ohif-viewer-script-tag-usage-svmm2
change line 98 from:
<EMAIL_ADDRESS>to
<EMAIL_ADDRESS>and the study list no longer loads (any version between 0.0.9 and 0.1.19 works).
code sandbox doesn't report anything specific, but when I test locally I get this message:
index.es.js:104 Uncaught ReferenceError: require is not defined
    at getLocales (index.es.js:104)
    at initI18n (index.es.js:123)
    at index.es.js:142
    at index.umd.js:4
    at index.umd.js:5

Looks like it's from here: https://github.com/OHIF/Viewers/blob/04e00fad20bbcacfc0eb9210c73ba907f2fc94bc/extensions/ohif-i18n/src/index.js#L41-L50


Reorder File menu

This PR will move Exit (previously Quit) item under Close Window (previously Close) item. It's now more logical order and renaming reflects better the commands. VS Code is using also Exit on windows instead of Quit.
This is now targeted to service-start-stop-telemetry branch but after #1414 is merged, we can re-target it to master

@nevalla conflicts needs to be resolved.

@nevalla conflicts needs to be resolved.

Done


Question: How to detect video is playing or paused

In documentation does not stated if there is API like this
this._vid = args.object;
If(this._vid.isPlaying()) {
this._vid.pause()
} else {
this._vid.play()
}

is there possibility to hook current video status.
NS7 + Vue
Thanks.

Late response but hope this might help someone.
There is not a property which is built into the plugin stating if a video is playing or paused. But as @andresilva-cc  suggest, you can make such a property yourself. Then set it based on the following callback functions:
This is the pure JS version:
const videoPlayer = page.getViewById('YourVideoPlayerID');
videoPlayer.on('playbackStartEvent', args => {
    // Your property here
});

videoPlayer.on('pausedEvent', args => {
  // Your property here
});


timeline and search

Codecov Report

Merging #58 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #58   +/-   ##
=======================================
  Coverage   89.15%   89.15%
=======================================
  Files          17       17
  Lines         295      295
=======================================
  Hits          263      263
  Misses         32       32

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 0bd721c...b56c3b5. Read the comment docs.


Blob -> String -> File

It would be nice to be able to produce a File object from a Blob object with File constructor.
https://developer.mozilla.org/en-US/docs/Web/API/File/File
Not sure if this should have Effect, but I don't think it should.

Can do without


(maintenance) Release automation broken

After merging PR from release-please, the CD action fails with this error:
> npm publish --access public --tag
npm ERR! Tag name must not be a valid SemVer range:

Looks like the "tag" is not being correctly set to latest after https://github.com/iTwin/iTwinUI/pull/766

pretty sure dont need to set the dist tag to latest explicitly for it to be tagged as such

pretty sure dont need to set the dist tag to latest explicitly for it to be tagged as such

Yeah but then it should not include --tag at all.
npm publish --access public

Currently it runs this:
npm publish --access public --tag


(PDB-5522) Docker custom entrypoint scripts

This adds a simple place to setup custom behavior

Can one of the admins verify this patch?

Containers are no longer in this repo.


Want to load commands only for specific pack aliases

This is issue which i solved. This is just info sharing. Please close this issue.
Currently stackstorm.js script loads all enabled aliases of all packs installed in st2. For scaling of hubot necessary to restrict specific packs to specific hubot instance. I might send PR if i have time but basically i did below changes to stackstorm.js . Hope its helpful for someone. Concept is inspired from new environment variable introduced here https://github.com/StackStorm/hubot-stackstorm/pull/133 ST2_ALIAS_PACK_RESTRICTION
In st2chatops.env file:
export ST2_ALIAS_PACK_RESTRICTION=packs,pack1Name,pack2Name
In scripts/stackstorm.js file:
// To restrict adding aliases from only specific packs.
env.ST2_ALIAS_PACK_RESTRICTION = env.ST2_ALIAS_PACK_RESTRICTION || null;
var loadCommands = function() {
robot.logger.info('Loading commands....');
api.actionAlias.list()
  .then(function (aliases) {
    // Remove all the existing commands
    command_factory.removeCommands();
    if (env.ST2_ALIAS_PACK_RESTRICTION) {
    robot.logger.info('Aliases only from following packs will be loaded: ' + env.ST2_ALIAS_PACK_RESTRICTION);
    var packs = env.ST2_ALIAS_PACK_RESTRICTION;
    var packsList = packs.split(",");
    _.each(aliases, function (alias) {
      if (packsList.indexOf(alias.pack) !== -1){
      var name = alias.name;
      var formats = alias.formats;
      var description = alias.description;

      if (alias.enabled === false) {
        return;
      }

      if (!formats || formats.length === 0) {
        robot.logger.error('No formats specified for command: ' + name);
        return;
      }

      _.each(formats, function (format) {
        var command = formatCommand(robot.logger, name, format.display || format, description);
        command_factory.addCommand(command, name, format.display || format, alias,
                                   format.display ? utils.DISPLAY : false);

        _.each(format.representation, function (representation) {
          command = formatCommand(robot.logger, name, representation, description);
          command_factory.addCommand(command, name, representation, alias, utils.REPRESENTATION);
        });
      });
    }});
    }
    else {
    robot.logger.info('Env variable ST2_ALIAS_PACK_RESTRICTION is not set. No aliases from any pack will be loaded ');
    }
    robot.logger.info(command_factory.st2_hubot_commands.length + ' commands are loaded');
  })
  .catch(function (err) {
    var error_msg = 'Failed to retrieve commands from "%s": %s';
    robot.logger.error(util.format(error_msg, env.ST2_API, err.message));
  });

};

It's possible to simply disable aliases individually, and I think that might be the "proper" way to do this.
Is there a particular reason you want to disable all aliases on a per-pack basis? Since this is already possible to do for individual aliases, this feature is a "nice to have", and we probably won't be able to put resources to it for awhile. We would be happy to review PRs implementing this if you can justify why it's important enough.

Here is related feature request about enabling/disabling specific pack content (incl. aliases) on st2 core level: https://github.com/StackStorm/st2/issues/3973
Filtering specific Aliases on Hubot level might be less popular functionality, comparing to ^^ that.


[FIX]:(PHP) Refactoring API Endpoint For Getting The Dashboard

Description
Endpoint for getting the dashboard
Route
GET/api/v1/Dashboards
Response Body
{
  "revenue": 0,
  "subscriptions": 0,
  "sales": 0,
  "activeSubscription": 0,
  "monthSales": [
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "user_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "product_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "subscription_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "type": "product",
      "status": "Pending",
      "partners": "Paystack",
      "amount": 0,
      "reference": "string",
      "created_at": "2024-08-24T16:28:19.305Z",
      "paid_at": "2024-08-24T16:28:19.305Z",
      "modified_at": "2024-08-24T16:28:19.305Z"
    }
  ]
}

@amowogbaje


Invariant Violation: Select2.render(): A valid ReactComponent must be returned.

I'm using React v0.13.3.  I install react-select2-wrapper from npm.  I follow the example exactly it seems, yet get this error.  Any ideas?
Invariant Violation: Select2.render(): A valid ReactComponent must be returned. You may have returned undefined, an array or some other invalid object.
<Select2
            multiple={false}
            data={[{text: 'Bug', id: 0}, {text: 'Feature', id: 1}, {text: 'Documents', id: 2}, {text: 'Discussion', id: 'UUID'}]}
            options={{
              placeholder: 'search by tags'
            }}/>

My imports:
import React from 'react';
import Select2 from 'react-select2-wrapper';

The current version uses React 0.14, v0.0.5 support React 0.13

I closed. Let me know if you have any problems.


Bluetooth: controller: Fix rx buffer leak for LL Version priority event

Fix leak of the node_rx buffer when processing the LL version ind as a
priority event. This leak meant being able to establish new connections
was no longer possible, because there weren't enough events to process
the all the events during connection establishment. And instead the LL
ignored the connection request sent by the peer.
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

Setting this bugfix to low. It is not required to backport I think because there is no infrastructure in the host to actually get this event yet.

Setting this bugfix to low. It is not required to backport I think because there is no infrastructure in the host to actually get this event yet.

We should backport this to cover controller only use by users. There will be leak?

We should backport this to cover controller only use by users. There will be leak?

For the controller-only use-case, there will be a leak if you enable the option and use it.

Yes but backport to what? 2.1?

This would affect the 2.1 release in a controller only build.

Changed the implementation here due to fact that the buffer should be released for all prio events processed this way.


docker-lambda error

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No steps to reproduce or information provided - Closing 😔


Update application.conf

Links added to https://confluence.tools.tax.service.gov.uk/pages/viewpage.action?pageId=536642588

rebuild

rebuild


"Feisa" is listed in the drop-down menu

Description:
"Feisa" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Feisa" in the search bar.

Expected results
The location is listed in the drop-down menu as "Feisa, Alba (Jidvei)".


Should MySQL be included in the options?

If so, then it should be updated on the following page.  https://cloud.google.com/php/getting-started/using-cloud-sql-with-mysql

I am unsure what you're referring to. "mysql" IS included in the options, and also the documentation in the page you linked to states "Set the value of bookshelf_backend to mysql."
What is the problem exactly?

@bshaffer The only options in the page are cloudsql, mongodb or datastore. Not mysql in the documentation.

Ahh yes, thank you for bringing this up. It used to be "mysql" but was changed to "cloudsql" when postgres support was added to cloudsql.

@jgacuca567 The option used to be cloudsql, but once postgres was added, we split this apart to be postgres and mysql. I believe the documentation and code are consistent with this.


Make everything const

similar to #15, but it makes more things const.

I don't think we need to take _layout: T, _set: S as args - they can be specified using a turbofish.

I merged a PR that adds Github Actions support (I don't think Travis CI works any more for free projects) so could you rebase on that?

I also had a play with the turbofish idea:
  16   │ --- a/src/lib.rs
  17   │ +++ b/src/lib.rs
  18   │ @@ -314,7 +314,7 @@ where
  19   │      S: ScancodeSet,
  20   │  {
  21   │      /// Make a new Keyboard object with the given layout.
  22   │ -    pub fn new(_layout: T, _set: S, handle_ctrl: HandleControl) -> Keyboard<T, S> {
  23   │ +    pub const fn new(handle_ctrl: HandleControl) -> Keyboard<T, S> {
  24   │          Keyboard {
  25   │              register: 0,
  26   │              num_bits: 0,
  27   │ @@ -564,9 +564,7 @@ mod test {
  28   │
  29   │      #[test]
  30   │      fn test_f9() {
  31   │ -        let mut k = Keyboard::new(
  32   │ -            layouts::Us104Key,
  33   │ -            ScancodeSet2,
  34   │ +        let mut k: Keyboard<layouts::Us104Key, ScancodeSet2> = Keyboard::new(
  35   │              HandleControl::MapLettersToUnicode,
  36   │          );
  37   │          // start

whoops.

could you reopen the pr?

No it won't let me. This might be because you closed it. Open another?
Also - pro tip: don't work on the main branch in your fork otherwise your fork will always have commits upstream does not. Instead, always do the work in a branch and open a PR from there. This will also make rebasing easier.

Okay, thanks for the tip. I'm not very experienced at git.


removes upper version bound in requirements

all tests run fine on my computer using a fresh install. could you please do the same on your machines including the mcmc tests:
pytest --run-mcmc tests

I did it and it works.

Just re-built the docs with this branch, everything looks fine there, too.


RL A1000 Malware Analysis Appliance

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.
[ ] Limit your pull request to one application and submit multiple pull requests if necessary.

Pull Request Type
Please check the type of change your PR introduces:

[x] New App
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)
supported actions:

local advanced search - Queries A1000 instance with a specified Advanced Search query.
get report - Get A1000 report for file
reanalyze file - Reanalyze the file in the A1000 Advanced Malware Analysis Appliance
detonate file - Analyze the file in the A1000 Advanced Malware Analysis Appliance and retrieve the analysis results
test connectivity - Validate the asset configuration for connectivity by attempting to log into the device

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Hello @ivukovicRL
Please convert this application to python version 3 if you have valid asset credentials with you. We strongly suggest using python 3 since python 2 support will be dropped in the near future.
Thanks!!!
Please refer to Convert apps from Python 2 to Python 3.

Hi @arathore-crest we are working on this and will soon open another PR with the updated app


Missing constructor GVRTextViewSceneObject(GVRContext, MainActivity, int, int, String)

Line 152 of VRBasketBallAndroid/src/com/cesarandres/vr/vrbbals/android/BallSpinnerScript.java refers to this missing consturctor
textPanel = new GVRTextViewSceneObject(context, core, 7, 4, "");

Thank you for the catch. Fixed in https://github.com/Samsung/GearVRf/pull/498.

Fix merged. Thanks again.

Thanks - Can someone please look at issue # 499. I could handle scene object's setPosition call. But need some guidance on getOwnerObject() call on GVRCameraRig (line 255 of MUNIVisualizer.java)
On Wednesday, April 13, 2016 2:01 PM, Mihail<EMAIL_ADDRESS>wrote:

Fix merged. Thanks again.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


not seem to work

I used ":HexDump" and it says "already dumped " but nothing seems to have changed.
I'm new to nvim so I don't know how to handle.

Try to toggle with :HexToggle, does this work?

Hi @Naturalifica could you provide your nvim version (nvim -v) and does this behavior occur on any file (try a .png)?

Thanks a lot, :HexToggle worked !

Try to toggle with :HexToggle, does this work?

my nvim version is 0.8.3 and this happened on a .img file

Try to toggle with :HexToggle, does this work?

Hi @Naturalifica could you provide your nvim version (nvim -v) and does this behavior occur on any file (try a .png)?

my nvim version is 0.8.3 and this happened on a .img file

This should be fixed, .img files auto dump on my end normally.
feel free to re-open this issue with a sample file if the issue persists


feat: cancel db query on stop

SUMMARY
This is addressing #15402
SQL Lab has Stop button but it only updates the state of superset without actually stopping the database query. Leaving the queries running in the background affect database performance. This PR is to stop running queries in the backend databases when:

The Stop button pressed in SQL Lab
Navigated to a new site, refreshed or closed the SQLLab browser window

It currently supports mysql, postgres and snowflake databases but new database support can be added easily. The PR is supporting sync and async query execution modes.
This is a refactored and extended version of the unmerged and inactive https://github.com/apache/superset/pull/7611
TESTING INSTRUCTIONS

Run a long running query in one of the supported drivers. For example MySQL:  SELECT sleep(60)
Press the Stop button, close the tab or navigate to another Superset page
Running query should get killed automatically in the backend database. For example MySQL SHOW PROCESSLIST should not show the query from point 1)

ADDITIONAL INFORMATION

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

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

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

Slightly off-topic:
How does the Stop button in Explore handle this situation?

Slightly off-topic:
How does the Stop button in Explore handle this situation?

It behaves the same and Stop button in Explore doesn't stop the query in the database. I'm planning to implement the same functionality for Explore as well and reuse some components once this PR get merged. This PR is focusing only on SQLLab.

This code looks good to me, thank you for the awesome contribution!
Would you mind adding a few tests for the new functionality?

@suddjian I added a few tests by https://github.com/apache/superset/pull/15403/commits/6d209378dca90d349b704d3ea05c7d17cd36ba52 and it's passing locally.
Can you please approve the CI workflow to run it?

@suddijan any chance to get this merged?

Huh, I'm pretty sure the stop button used to work with Hive/Presto, killing the query. I wonder if we had a regression at some point.

I'm not sure if navigating to another page should cancel the query - I can see wanting to navigate away from a long running query and coming back to it.

Huh, I'm pretty sure the stop button used to work with Hive/Presto, killing the query.

@betodealmeida I think you're right. Hive and presto drivers are running queries in async mode with custom cursor handlers. They periodically selects the query status from the superset db in every second and if the query status is STOPPED then it cancels the query by calling the cursor.cancel() function. Hive here, Presto here. This method unfortunately is not working for other db engines. Mysql, postgres and snowflake are running queries in sync mode where polling is not available so we can't check periodically the query status from the superset database. In case of mysql, postgres and snowflake the stop button sends a message to the corresponding db_engine_spec to cancel the query by calling DB specific kill commands.
The behaviour of Db engines that doesn't implement the cancel_query method remains the same, so no changes in hive and presto queries. They're still running in async mode, polling query statuses and terminating queries by cursor.cancel() whenever the stop button pressed.

I'm not sure if navigating to another page should cancel the query - I can see wanting to navigate away from a long running query and coming back to it.

@yousoph you can still keep running the long queries by not closing the browser tab. This is a very similar behaviour when running queries in a desktop SQL client. If we close a desktop SQL client then the running queries are terminated. I believe that SQL Lab should behave the same and running queries need to be terminated when navigating to another window or when closing the browser. This is a default behaviour in Looker (and maybe in Tableau?) as well.

A bit more context about this PR:
We're about to give SQL Lab access to 2000 registered users and expecting about 100 concurrent users in every hour. Manual queries accidentally will be be self joins, cross joins, ones with missing WHERE conditions or simple very long running queries. People will press the stop button or close the browser windows in the hope their queries got killed to let other people to run queries. In concurrency sensitive databases (like snowflake or redshift), stuck queries blocking people to run new queries and features like this PR is crucial.
Please let me know your thougs. :bowing_man:

@yousoph you can still keep running the long queries by not closing the browser tab. This is a very similar behaviour when running queries in a desktop SQL client. If we close a desktop SQL client then the running queries are terminated. I believe that SQL Lab should behave the same and running queries need to be terminated when navigating to another window or when closing the browser. This is a default behaviour in Looker (and maybe in Tableau?) as well.

I agree on ending the query when closing the browser, but I believe this will also end the query when you go to a different tab outside of sql lab as well.

I believe this will also end the query when you go to a different tab outside of sql lab as well.

That's true. Clicking on a non sqllab link (like Charts or Dashboards) is terminating the running query but opening a new tab in the browser should keep it running. What do you think is that acceptable and can it be the default behaviour? Or maybe we should make it configurable?

I believe this will also end the query when you go to a different tab outside of sql lab as well.

That's true. Clicking on a non sqllab link (like Charts or Dashboards) is terminating the running query but opening a new tab in the browser should keep it running. What do you think is that acceptable and can it be the default behaviour? Or maybe we should make it configurable?

I think configurable is a good approach, since it changes the current behavior. And just to confirm, when you leave the page it only cancels sync queries, not async?

I believe this will also end the query when you go to a different tab outside of sql lab as well.

That's true. Clicking on a non sqllab link (like Charts or Dashboards) is terminating the running query but opening a new tab in the browser should keep it running. What do you think is that acceptable and can it be the default behaviour? Or maybe we should make it configurable?

I think configurable is a good approach, since it changes the current behavior. And just to confirm, when you leave the page it only cancels sync queries, not async?

I only tested on sync queries so far, yes.

Also testing with Postgres, I'm seeing an error on a long-running query. Small nit, maybe @yousoph can comment, but on shorter queries, there's a bit of a race condition going on. I can hit "stop", see the confirmation that it was stopped but then a few seconds later, still see the results. LMK if you want a video.
But here's the error on the wb_health_population example data set, which is larger:

The popup appears only in Firefox. It's a little bit annoying indeed but looking into the beforeunload spec this is what might happen in Chrome as well soon.
:+1: I'll make killing queries on window close events configurable in the DB config window and setting it to False as default. I hope that's fine and will update this PRs soon.

@koszti if you want to look at the error above, I may have some simple workaround suggestions for the alert. Since FF is going to alert anyway with no real meaningful message, we could go ahead and put a confirm message for all browsers to ask the person if they want us to close their db connection when they leave. That also somewhat takes care of the configuration issue because people will have a choice. @betodealmeida @yousoph any thoughts on that?
For the race condition on the client side, I think a good solution would be to check the query status again before displaying the results, but that may be something that we can do in a followup PR.

also @graceguo-supercat and @etr2460 I wanted to flag these changes for you to be able to give any input on how this might affect your users.

Since FF is going to alert anyway with no real meaningful message, we could go ahead and put a confirm message for all browsers to ask the person if they want us to close their db connection when they leave. That also somewhat takes care of the configuration issue because people will have a choice

I like this idea!

Since FF is going to alert anyway with no real meaningful message, we could go ahead and put a confirm message for all browsers to ask the person if they want us to close their db connection when they leave. That also somewhat takes care of the configuration issue because people will have a choice

I like this idea!

I liked it too, it's elegant but turns out there are some problems.
We can't check what the user answered in the page leave confirmation popup hence we can't stop the query conditionally. Checking the user's answer requires to introduce the unload event but in the unload event the react props are no longer available so we can't call the this.stopQuery() function. :(
Using standard window.confirm would be a workaround but unfortunately we can't use window.confirm in beforeunload events. Using custom confirmation messages in the page leave popup is not allowed either.
I made the following changes in 54da5e42cb0bef9c2d9bc15a5ba1a0c6870ec4c3:

It's checking the the query status and it triggers the mechanism only if the query is still running. This is to eliminate some race conditions.

The only solution I can see to make the auto-kill optional is to introduce the "Cancel db query on window close" configurable option in the databases table but that'd require some changes in the core /api/v1/database/ endpoint. I can add a new property into the extra JSON field to avoid db migration. But please let me know if you can see any simpler solution, before I start doing it. Changes in the core database API endpoint response could affect many other things.

I'm not sure if navigating to another page should cancel the query - I can see wanting to navigate away from a long running query and coming back to it.

At the moment, editing a dashboard / chart and navigating away will prompt Changes that you made may not be saved. and not store a state that can be restored by going back to the same page.
I'm feeling it is not intuitive why the SQL Lab should behave differently, especially in a browser environment where opening a new tab is just a click away, and where BI end-users are cognizant of the fact that the processes are active while the browser tab is too. I personally did not even notice this was possible until you mentioned it.
Within the SQL Lab, it is possible to move between different query tabs without killing them, which is intuitive.

Added a new option to Database -> Performance to optionally cancel running queries when closing browser window or navigating to another site:

@koszti at Airbnb we predominantly use Presto (where only the system connector is able to kill queries) and though the new behavior is more reflective of what's actually happening, i.e., the query isn't stopped it does result in a subtle UX "regression". Specifically users have to wait for the query to complete before attempting to run another query, whereas previously hitting STOP would free up the UI (even though the query was actually never stopped).


Example?

I don't know if this a mistake but there is nothing in the example

test/fake_okhttp_test.dart

Oh ok. This one worked. Thanks :)
I am actually looking for something that can help me get the HTML response of https://www7.animeultima.eu/ . Unfortunately, fake_okhttp and many other plugins can't do that. Do you have any idea on how to achieve this?
I am closing the issue.


Stop from using addr_adv

Hello,
I'm making a plugin that needs to configure the endpoints, but since the path manager addr_adv listens to added local address events, it always configures the endpoints, even if I don't want it to happen.
That being said, is there a way to make mptcpd not use the addr_adv path manager, something else than removing addr_adv from the plugin directory?

Considering that I need this, do you mind if I take care of it?

Not at all.  Thanks for your help!


Port to latest holoviews

These changes allows togographia to run with the head version of holoviews. These requires my push request for featuremapper.
The one thing that that does not run correctly is the composition:
CoG_spec = "Image.X CoG * Image.Y CoG * Image.BlueChannel" XYCoG = chain.instance(group='XYCoG', name='XYCoG',                        operations = [image_overlay.instance(spec=CoG_spec), factory.instance()]) Compositor.register(Compositor("Image.X CoG * Image.Y CoG", XYCoG, 'XYCoG', 'display'))
defined in topo.analysis. As is, it causes an error when trying to display an overlay of CoGs.
If this is deleted overlays appear without an error. Any attempt that I made to fix this avoided the error, but only displayed outlines of the images.

The remaining issue is down to changes in the compositor in holoviews. For now, I would recommend deleting that line: the compositor is just a convenience and you can achieve the equivalent visualization manually. It is better to get the data out and visualize it the way you please than having to deal with an unnecessary error.
Updating that line to work with the current state of the compositor should be possible but that would require some thought and possibly some extra work too.

I added some more changes that I made. These solve:

Tk no longer crashes in Mac Seirra
Latest Jupyter 5.x for Python 2.7 runs.
Matplotlib correctly uses Tk.
Additional problems with the latest holoviews.
The unit tests all pass with nose if the path topo/tests/unit is explicitly provided.

Unfortunately there are still two serious problems that i do not know if I will have time to address:

The optimized code randomly generates FloatingPoint errors. These do not occur if the non optimized version is run.
All overlays in the GCAL_Tutorial.ipynb crash with a KeyError. This is probably a Holoviews incompatibility but the call stack is so long and convoluted, because of the deeply nested params that I did not have enough familiarity of the architecture to trace the problem.

what do you propose should happen to that type of plot?

@fcr I'll probably have a better idea how to resolve this if you could post the output of print around the object that is failing with the keyerrors (presumably during display).

@jlstevens. I simply run the GCAL_Tutorial.ipynb with the model = 'LISSOM'.
The cell, for example:
pref = data.OrientationPreference.V1  sel =  data.OrientationSelectivity.V1 (pref*sel).select(Time=max_time)
crashes with:
KeyError                                  Traceback (most recent call last)
/Users/fred/anaconda/envs/python2/lib/python2.7/site-packages/IPython/core/formatters.pyc in call(self, obj, include, exclude)
968                 d['include'] = include
969                 d['exclude'] = exclude
--> 970                 return method(**d)
971             return None
972         else:
/Users/fred/Development/topographica/external/holoviews/holoviews/core/dimension.pyc in repr_mimebundle(self, include, exclude)
1263         combined and returned.
1264         """
-> 1265         return Store.render(self)
1266
1267
/Users/fred/Development/topographica/external/holoviews/holoviews/core/options.pyc in render(cls, obj)
1287         data, metadata = {}, {}
1288         for hook in hooks:
-> 1289             ret = hook(obj)
1290             if ret is None:
1291                 continue
/Users/fred/Development/topographica/external/holoviews/holoviews/ipython/display_hooks.pyc in pprint_display(obj)
270     if not ip.display_formatter.formatters['text/plain'].pprint:
271         return None
--> 272     return display(obj, raw_output=True)
273
274
/Users/fred/Development/topographica/external/holoviews/holoviews/ipython/display_hooks.pyc in display(obj, raw_output, **kwargs)
243     elif isinstance(obj, (Layout, NdLayout, AdjointLayout)):
244         with option_state(obj):
--> 245             output = layout_display(obj)
246     elif isinstance(obj, (HoloMap, DynamicMap)):
247         with option_state(obj):
/Users/fred/Development/topographica/external/holoviews/holoviews/ipython/display_hooks.pyc in wrapped(element)
140         try:
141             max_frames = OutputSettings.options['max_frames']
--> 142             mimebundle = fn(element, max_frames=max_frames)
143             if mimebundle is None:
144                 return {}, {}
/Users/fred/Development/topographica/external/holoviews/holoviews/ipython/display_hooks.pyc in layout_display(layout, max_frames)
213         return None
214
--> 215     return render(layout)
216
217
/Users/fred/Development/topographica/external/holoviews/holoviews/ipython/display_hooks.pyc in render(obj, **kwargs)
63         renderer = renderer.instance(fig='png')
64
---> 65     return renderer.components(obj, **kwargs)
66
67
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/renderer.pyc in components(self, obj, fmt, comm, **kwargs)
327             plot = obj
328         else:
--> 329             plot, fmt = self._validate(obj, fmt)
330
331         widget_id = None
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/renderer.pyc in _validate(self, obj, fmt, **kwargs)
226         if isinstance(obj, tuple(self.widgets.values())):
227             return obj, 'html'
--> 228         plot = self.get_plot(obj, renderer=self, **kwargs)
229
230         fig_formats = self.mode_formats['fig'][self.mode]
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/renderer.pyc in get_plot(self_or_cls, obj, renderer)
209             plot_opts = self_or_cls.plot_options(obj, self_or_cls.size)
210             plot = self_or_cls.plotting_class(obj)(obj, renderer=renderer,
--> 211                                                    **plot_opts)
212             defaults = [kd.default for kd in plot.dimensions]
213             init_key = tuple(v if d is None else d for v, d in
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/mpl/plot.pyc in init(self, layout, keys, **params)
749         super(LayoutPlot, self).init(layout=layout, keys=keys, **params)
750         with mpl.rc_context(rc=self.fig_rcparams):
--> 751             self.subplots, self.subaxes, self.layout = self._compute_gridspec(layout)
752         if self.top_level:
753             self.comm = self.init_comm()
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/mpl/plot.pyc in _compute_gridspec(self, layout)
938                                                  layout_dimensions, frame_ranges,
939                                                  dict(zip(positions, subaxes)),
--> 940                                                  num=0 if empty else layout_count)
941             subplots, adjoint_layout, _ = subplot_data
942             layout_axes[(r, c)] = subaxes
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/mpl/plot.pyc in _create_subplots(self, layout, positions, layout_dimensions, ranges, axes, num, create)
1060                                       ranges=ranges, subplot=True,
1061                                       uniform=self.uniform, layout_num=num,
-> 1062                                       renderer=self.renderer, **plotopts)
1063             if isinstance(view, (Element, HoloMap, Collator, CompositeOverlay)):
1064                 adjoint_clone[pos] = subplots[pos].hmap
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/mpl/element.pyc in init(self, overlay, ranges, **params)
748         if 'projection' not in params:
749             params['projection'] = self._get_projection(overlay)
--> 750         super(OverlayPlot, self).init(overlay, ranges=ranges, **params)
751
752
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/mpl/element.pyc in init(self, element, **params)
60
61     def init(self, element, **params):
---> 62         super(ElementPlot, self).init(element, **params)
63         check = self.hmap.last
64         if isinstance(check, CompositeOverlay):
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/plot.pyc in init(self, overlay, ranges, batched, keys, group_counter, **params)
885
886         # Apply data collapse
--> 887         self.hmap = self._apply_compositor(self.hmap, ranges, self.keys)
888         self.map_lengths = Counter()
889         self.group_counter = Counter() if group_counter is None else group_counter
/Users/fred/Development/topographica/external/holoviews/holoviews/plotting/plot.pyc in _apply_compositor(self, holomap, ranges, keys, dimensions)
919         ranges = frame_ranges.values()
920
--> 921         return Compositor.collapse(holomap, (ranges, frame_ranges.keys()), mode='display')
922
923
/Users/fred/Development/topographica/external/holoviews/holoviews/core/options.pyc in collapse(cls, holomap, ranges, mode)
874         data = zip(ranges[1], holomap.data.values()) if ranges else holomap.data.items()
875         for key, overlay in data:
--> 876             clone[key] = cls.collapse_element(overlay, ranges, mode)
877         return clone
878
/Users/fred/Development/topographica/external/holoviews/holoviews/core/options.pyc in collapse_element(cls, overlay, ranges, mode, backend)
843             if applicable_op and all(el in processed[applicable_op] for el in items):
844                 return overlay
--> 845             result = applicable_op.apply(sliced, ranges, backend)
846             if applicable_op.group:
847                 result = result.relabel(group=applicable_op.group)
/Users/fred/Development/topographica/external/holoviews/holoviews/core/options.pyc in apply(self, value, input_ranges, backend)
1009                                if k in self.operation.params()})
1010
-> 1011         transformed = self.operation(value, input_ranges=input_ranges, **kwargs)
1012         if self.transfer_options:
1013             Store.transfer_options(value, transformed, backend)
/Users/fred/Development/topographica/external/param/param/parameterized.pyc in new(class_, *args, **params)
2047         inst = class_.instance()
2048         inst.param.set_name(class.name)
-> 2049         return inst.call(*args,**params)
2050
2051     def call(self,*args,**kw):
/Users/fred/Development/topographica/external/holoviews/holoviews/core/operation.pyc in call(self, element, **params)
161                                 operation=self, kwargs=params)
162         elif isinstance(element, ViewableElement):
--> 163             processed = self._apply(element)
164         elif isinstance(element, DynamicMap):
165             if any((not d.values) for d in element.kdims):
/Users/fred/Development/topographica/external/holoviews/holoviews/core/operation.pyc in _apply(self, element, key)
119         for hook in self._preprocess_hooks:
120             kwargs.update(hook(self, element))
--> 121         ret = self._process(element, key)
122         for hook in self._postprocess_hooks:
123             ret = hook(self, ret, **kwargs)
/Users/fred/Development/topographica/external/featuremapper/featuremapper/analysis/init.pyc in _process(self, overlay, key)
277         normfn = raster_normalization.instance()
278         if self.p.input_ranges:
--> 279             overlay = normfn.process_element(overlay, key, *self.p.input_ranges)
280         else:
281             overlay = normfn.process_element(overlay, key)
/Users/fred/Development/topographica/external/holoviews/holoviews/operation/normalization.pyc in process_element(self, element, key, ranges, keys, **params)
88         params = dict(params,ranges=ranges, keys=keys)
89         self.p = param.ParamOverrides(self, params)
---> 90         return self._process(element, key)
91
92
/Users/fred/Development/topographica/external/holoviews/holoviews/operation/normalization.pyc in _process(self, raster, key)
145             overlay_clone = raster.clone(shared_data=False)
146             for k, el in raster.items():
--> 147                 overlay_clone[k] =  self._normalize_raster(el, key)
148             return overlay_clone
149         else:
/Users/fred/Development/topographica/external/holoviews/holoviews/operation/normalization.pyc in _normalize_raster(self, raster, key)
154         if not isinstance(raster, Raster): return raster
155         norm_raster = raster.clone(raster.data.copy())
--> 156         ranges = self.get_ranges(raster, key)
157
158         for depth, name in enumerate(d.name for d in raster.vdims):
/Users/fred/Development/topographica/external/holoviews/holoviews/operation/normalization.pyc in get_ranges(self, element, key)
113                 specs = ranges[index]
114             except:
--> 115                 raise KeyError("Could not match element key to defined keys")
116         else:
117             raise ValueError("Key list length must match length of supplied ranges")
KeyError: 'Could not match element key to defined keys'
:Layout
.Orientation_Preference.V1.I  :HoloMap   [Time,Duration]
:Image   [x,y]   (Orientation Preference)
.Orientation_Selectivity.V1   :HoloMap   [Time,Duration]
:Image   [x,y]   (Orientation Selectivity)
.Orientation_Preference.V1.II :HoloMap   [Time,Duration]
:Overlay
.Orientation_Preference.V1  :Image   [x,y]   (Orientation Preference)
.Orientation_Selectivity.V1 :Image   [x,y]   (Orientation Selectivity)
Looking at the data with a breakpoint at the exception I had:
str: _fig_rcparams_param_value
element: Image: :Image   [x,y]   (Orientation Preference)
key: None
keys: <type 'list'>: [(mpq(100,1), mpq(7,40))]
ranges: <type 'list'>: [{('Image',): OrderedDict([('x', (-0.5, 0.5)), ('y', (-0.5, 0.5)), ('Orientation Preference', (0.0, 3.141592653589793)), ('Orientation Selectivity', (0.006849852636067116, 1.3778337397815732))])}]
self: raster_normalization: raster_normalization()
The key gets its None value as the default argument in the call to _apply(element) in line 163 of /Users/fred/anaconda/envs/python2/lib/python2.7/site-packages/holoviews/core/operation.pyc.
In all cases of Overlays, where there was a crash, the key was None.
Hope that this helps

Fred

BTW the problem does not rely on Compositor that was commented out.

I didn't study the entire traceback, but it does mention Compositor, so I would guess this error is just to do with Compositor not being defined (as it's commented out).

I made my previous comment after I restored the Compositor. Made no difference. Not surprizing since the Compositor is keyed to cog and this is a general problem.

I think this is too trick to debug from the traceback alone so I'll have a go at reproducing the bug soon. I suspect it might be to do with how normalization information used to be stored but I might be wrong about that...


Requirements to make it work on M1

While installing pip install imaginairy on Mac (M1) it needs a dependency basicsr, this will build from the source and fails: error: can't find Rust compiler
After installing rust on the recommended way and restarting the terminal it was able to install the package.
After successfully installing there was a runtime issue:
The protobuf version  3.19.5 has an issue. need to downgrade / pin protobuf (pip install protobuf==3.19.4)
Downloading,.... waiting for first image to appear… :)

Thanks for the feedback.  I'd love to know what compiled in rust. I don't have rust installed and that package is working for me 🤷♂ I'm trying to reproduce that issue.
What version of python are you on?

Ive updated the package to mitigate the protobuf issue.  I've been unable to find where the rust dependency came from thouh.

I'll close this for now but let me know if you have more info.

Resolved by running sudo pip3 install setuptools-rust first

Hit this next:
  Building wheel for tokenizers (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for tokenizers (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [53 lines of output]
      Error in sitecustomize; set PYTHONVERBOSE for traceback:
      AssertionError:
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.macosx-12-arm64-cpython-310
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers
      copying py_src/tokenizers/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/models
      copying py_src/tokenizers/models/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/models
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/decoders
      copying py_src/tokenizers/decoders/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/decoders
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/normalizers
      copying py_src/tokenizers/normalizers/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/normalizers
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/pre_tokenizers
      copying py_src/tokenizers/pre_tokenizers/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/pre_tokenizers
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/processors
      copying py_src/tokenizers/processors/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/processors
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/trainers
      copying py_src/tokenizers/trainers/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/trainers
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/byte_level_bpe.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/sentencepiece_unigram.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/sentencepiece_bpe.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/base_tokenizer.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/char_level_bpe.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      copying py_src/tokenizers/implementations/bert_wordpiece.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/implementations
      creating build/lib.macosx-12-arm64-cpython-310/tokenizers/tools
      copying py_src/tokenizers/tools/__init__.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/tools
      copying py_src/tokenizers/tools/visualizer.py -> build/lib.macosx-12-arm64-cpython-310/tokenizers/tools
      copying py_src/tokenizers/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers
      copying py_src/tokenizers/models/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/models
      copying py_src/tokenizers/decoders/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/decoders
      copying py_src/tokenizers/normalizers/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/normalizers
      copying py_src/tokenizers/pre_tokenizers/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/pre_tokenizers
      copying py_src/tokenizers/processors/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/processors
      copying py_src/tokenizers/trainers/__init__.pyi -> build/lib.macosx-12-arm64-cpython-310/tokenizers/trainers
      copying py_src/tokenizers/tools/visualizer-styles.css -> build/lib.macosx-12-arm64-cpython-310/tokenizers/tools
      running build_ext
      running build_rust
      error: can't find Rust compiler

      If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

      To update pip, run:

          pip install --upgrade pip

      and then retry package installation.

      If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
      [end of output]

Managed to get it working after installing Rust. Upgrading pip3 didn't help.

@abrambailey that's excellent info. it looks like I was mistaken about rust being installed on my system.  the tokenizer lib doesn't provide an osx arm wheel so it does have to be compiled.

I'll update the directions to include rust installation

I've updated the directions.

thanks - fixed.

I am getting this error on M1,
tried installing rust but still not working. Anyone else had this issue?
Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [40 lines of output]
      The Meson build system
      Version: 1.1.1
      Source dir: /private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b
      Build dir: /private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b/.mesonpy-3hg2rx_m/build
      Build type: native build
      Project name: SciPy
      Project version: 1.10.1
      C compiler for the host machine: cc (clang 13.0.0 "Apple clang version 13.0.0 (clang-13<IP_ADDRESS>)")
      C linker for the host machine: cc ld64 711
      C++ compiler for the host machine: c++ (clang 13.0.0 "Apple clang version 13.0.0 (clang-13<IP_ADDRESS>)")
      C++ linker for the host machine: c++ ld64 711
      Cython compiler for the host machine: cython (cython 0.29.35)
      Host machine cpu family: aarch64
      Host machine cpu: aarch64
      Compiler for C supports arguments -Wno-unused-but-set-variable: NO
      Compiler for C supports arguments -Wno-unused-function: YES
      Compiler for C supports arguments -Wno-conversion: YES
      Compiler for C supports arguments -Wno-misleading-indentation: YES
      Compiler for C supports arguments -Wno-incompatible-pointer-types: YES
      Library m found: YES

      ../../meson.build:63:0: ERROR: Unknown compiler(s): [['gfortran'], ['flang'], ['nvfortran'], ['pgfortran'], ['ifort'], ['ifx'], ['g95']]
      The following exception(s) were encountered:
      Running `gfortran --version` gave "[Errno 2] No such file or directory: 'gfortran'"
      Running `gfortran -V` gave "[Errno 2] No such file or directory: 'gfortran'"
      Running `flang --version` gave "[Errno 2] No such file or directory: 'flang'"
      Running `flang -V` gave "[Errno 2] No such file or directory: 'flang'"
      Running `nvfortran --version` gave "[Errno 2] No such file or directory: 'nvfortran'"
      Running `nvfortran -V` gave "[Errno 2] No such file or directory: 'nvfortran'"
      Running `pgfortran --version` gave "[Errno 2] No such file or directory: 'pgfortran'"
      Running `pgfortran -V` gave "[Errno 2] No such file or directory: 'pgfortran'"
      Running `ifort --version` gave "[Errno 2] No such file or directory: 'ifort'"
      Running `ifort -V` gave "[Errno 2] No such file or directory: 'ifort'"
      Running `ifx --version` gave "[Errno 2] No such file or directory: 'ifx'"
      Running `ifx -V` gave "[Errno 2] No such file or directory: 'ifx'"
      Running `g95 --version` gave "[Errno 2] No such file or directory: 'g95'"
      Running `g95 -V` gave "[Errno 2] No such file or directory: 'g95'"

      A full log can be found at /private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b/.mesonpy-3hg2rx_m/build/meson-logs/meson-log.txt
      + meson setup<EMAIL_ADDRESS>/private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b /private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b/.mesonpy-3hg2rx_m/build --native-file=/private/var/folders/ln/jyqplwh11tb1ql8rxlrp88280000gn/T/pip-install-f4urya0y/scipy_9fc0f8a3649f4b2591931528e757045b/.mesonpy-native-file.ini -Ddebug=false -Doptimization=2
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed


cli: Allow changing Kube Service type for connectivity tests

This PR replaces https://github.com/cilium/cilium-cli/pull/2653
Description
The goal of this PR is to allow users to change the type of Services created by automated connectivity tests.
The default type is hardcoded to NodePort which is not necessarily the best choice for everyone. For example, we are currently setting up a GateKeeper rule to block NodePort service creation in all of our clusters, mainly for security, performance and practicality reasons (for more context, see for instance https://oteemo.com/think-nodeport-kubernetes/).
The newly added parameter looks like this (and still has NodePort as the default):
      --service-type string             Type of Kubernetes Services created for connectivity tests (default "NodePort")

Testing

[x] Ran the tests without setting --service-type, verified that NodePort services were still being created
[x] Ran the tests with --service-type=ClusterIP, verified that ClusterIP services were properly created:

$ kubectl -n cilium-test get svc echo-other-node
NAME              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
echo-other-node   ClusterIP   10.x.x.x        <none>        8080/TCP   4m23s

[x] Ran the tests with an invalid value --service-type=FAIL, verified that the tests failed with a clear error:

connectivity test failed: Service "echo-same-node" is invalid: spec.type: Unsupported value: "FAIL": supported values: "ClusterIP", "ExternalName", "LoadBalancer", "NodePort"

cli: Allow changing Kube Service type for connectivity tests

/test

Looks like the required ci-eks test failed because of an unrelated issue:
The maximum number of VPCs has been reached. (Service: Ec2, Status Code: 400)

I filed an issue for this https://github.com/cilium/cilium/issues/34525

Looks like the required ci-eks test failed because of an unrelated issue:
The maximum number of VPCs has been reached. (Service: Ec2, Status Code: 400)

I've pinged the infrastructure folks and this issue should be resolved now. Re-triggering the respective test.


Autotune -> Save to Basals ... Zero's Basals

Just recording this ... David / Heather on Slack just found this:
Record your basal schedule before you do this. To reproduce… [Settings][Autotune][Run Now], choose [Save as your normal Basal rates], confirm [Yes], your saved basal rates are all now 0!

Do you have screenshots of your AT basals?

Sadly, 'Save to ...' doesn't even work on my phone, running dev ... my before and after basal rates are the same, even though I did tap 'Yes' when prompted ...
AT vs Basals:

I just ran a test and get the same zero basal on save. The recommended values look good but after hitting save everything saved to the pod is zero.  AT recommended[A screenshot of a phone  Description automatically generated]
After selecting “Save as your normal basal rates” the basal profile looks like this, all the AT
rates get zeroed.
[A screenshot of a phone  Description automatically generated]
From: Marc G. Fournier @.>
Date: Saturday, May 25, 2024 at 12:59 PM
To: Artificial-Pancreas/iAPS @.>
Cc: Subscribed @.***>
Subject: Re: [Artificial-Pancreas/iAPS] Autotune -> Save to Basals ... Zero's Basals (Issue #711)
Sadly, 'Save to ...' doesn't even work on my phone, running dev ... my before and after basal rates are the same, even though I did tap 'Yes' when prompted ...
AT vs Basals:
IMG_6494.PNG (view on web)https://github.com/Artificial-Pancreas/iAPS/assets/609712/2ce5fd68-7f8e-497c-a9f0-bcdad2c80a46
IMG_6493.PNG (view on web)https://github.com/Artificial-Pancreas/iAPS/assets/609712/46c20c28-0805-4090-98ff-2d1bb2bf6a39
—
Reply to this email directly, view it on GitHubhttps://github.com/Artificial-Pancreas/iAPS/issues/711#issuecomment-2131375253, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQUBHGUG2AXJFEQQDF3F5CTZEDGP3AVCNFSM6AAAAABIISD3KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGM3TKMRVGM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Im not sure yet why this is suddenly not working anymore. I’ll probably disable the save AT until this has been fixed.

Disabled in latest dev

I believe the issue is AT is recommending basals that aren’t multiples of 0.05. Ie a basal of 1.33 instead of 1.30. Omnipod delivers basals via 0.05 increments and so the basals saved from AT are listed as 0.0 in my basal profile if I save the basals from AT.  If I check the Debug menu “Basal Profile” then the basal rates are saved from AT but they are intervals of 0.01 instead of 0.05. The basals still work it’s just the Basal Profile menu can’t display basals that don’t end in 0.00 or 0.05.

Not sure if 722 for model variable matters but I am using Dash pods.

Resolved in dev branch


Not working with Safari Version 8.0.2 (10600.2.5)

Hi,
I am using the validator plugin and it works perfectly fine with Chrome but there seems to be some issue with Safari. The build is Version 8.0.2 (10600.2.5). Is there anything which I might be missing? It does not work at all with my Safari.
Thanks

Seems to be working for me when I visit the docs page.

I know, it should work. I thought I might be missing something, so posted. Anyways, I would be trying to resolve this on my own.
Thanks

Does the docs page work for you in Safari?


Bind this in transformed code.

We need to be binding this in all our depends in order to not break it.

No longer applicable, also fixed.


(tech-insights): Integrate notifications into the tech-insights backend

Hey, I just made a Pull Request!
Make the notifications available as part of the FactRetriever context. Now that this plugin is available, it would make sense to let users be able to use this service to trigger notifications when a check is failing.
The usage of this service will be up to the end user, and no logic has to be implemented into the tech-insights directly.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

please resolve conflicts.

please resolve conflicts.

Made a rebase with the main branch and updated the package versions :)

Hi @Xantier, can you give this a look, please?


Allow JDK23 compatibility for Subject#getSubject

As reported by JDK 23 release notes:

The terminally deprecated method Subject.getSubject(AccessControlContext) has been re-specified to throw UnsupportedOperationException if invoked when a Security Manager is not allowed.

The proposed change allows to run flawlessly under JDK 23.

@reta are there any plans to increase the Java baseline to 18 or newer? If so, we could start using Subject.current() instead of Subject.getSubject(AccessController.getContext()) and catching UnsupportedOperationException which may harm the performance.
Even before upgrading the baseline, we could perhaps avoid calling Subject.getSubject(AccessController.getContext()) if the current Java Runtime is 18+ and System.getSecurityManager() returns null. That might be faster. WDYT?

@reta are there any plans to increase the Java baseline to 18 or newer?

For 4.1.0, we are settled on JDK-17 at the moment, I think we could go with at least with JDK-21 for 4.2.0, but it is largely dictated by our dependencies (Spring, etc) and the projects that depend on us (fe Microprofile Rest client, etc), thank @ppalaga

Even before upgrading the baseline, we could perhaps avoid calling Subject.getSubject(AccessController.getContext()) if the current Java Runtime is 18+ and System.getSecurityManager() returns null. That might be faster. WDYT?

My apologies @ppalaga , took me a bit more time to look into it. AFAIK, there is no relation between  System.getSecurityManager() returning null and Subject.getSubject(AccessController.getContext()) . The only setting that matters is -Djava.security.manager=allow which is sadly is hidden inside System::allowSecurityManager() class, having access to it would have been helpful to not call Subject.getSubject() at all.


Flaky results for logcheck

Running logcheck seemingly spuriously fails. Happens both locally and in CI. An example of running locally:
$ logcheck -config scripts/test-infra/logcheck.conf ./cmd/... ./pkg/...  ./source/...
$ logcheck -config scripts/test-infra/logcheck.conf ./cmd/... ./pkg/...  ./source/...
$ logcheck -config scripts/test-infra/logcheck.conf ./cmd/... ./pkg/...  ./source/...
$ logcheck -config scripts/test-infra/logcheck.conf ./cmd/... ./pkg/...  ./source/...
/home/marquiz/go/git/node-feature-discovery/pkg/nfd-master/nfd-master.go:349:13: lis.Close undefined (type "net".Listener has no field or method Close)
logcheck: analysis skipped due to errors in package
logcheck: analysis skipped due to errors in package
logcheck: analysis skipped due to errors in package
logcheck: analysis skipped due to errors in package

This happens at least in the node-feature-discovery project.

I was able to reproduce the failure locally with Go 1.21rc. But golang.org/x/tools/go/analysis isn't part of the Go release and logcheck was using a pretty old version of it. Updating dependencies seems to have fixed this for me.
Before:
$ $GOPATH/bin/stress -p 1 /tmp/logcheck -config scripts/test-infra/logcheck.conf ./cmd/... ./pkg/...  ./source/...
...
15s: 12 runs so far, 6 failures (50.00%)
^C

After:
1m20s: 72 runs so far, 0 failures

Reminding me :smile:... done.


Adjust build-infra to accommodate Sysbox compilation on Fedora distro

As we did with CentOS couple of weeks ago, here we are just making the required adjustments to ensure Sysbox properly builds and passes all testcases when running on Fedora. There are few other minor adjustments needed to be able to claim Sysbox's preliminary support in Fedora though.

The failing testcase has been seen before -- apparently a hard-to-reproduce race condition in one of the concurrent test, it's in no way related to the chances made in this PR. Will go ahead and merge this PR now.


[WIP]fix travis nodejs heap oom

will this fix the oom? or should set the max_old_space_size instead?

Setting max_old_space_size to a fix number can be much trickier for 2 reason:

Need to make sure the flag pass the flag all the way down.
The available memory size might not be exactly the same for each run.

Hence, it'd be better use node 12, let it determine the maximum memory it can use at runtime.

I prefer to use Node.js 12 as it would provide performance improvement as well

ok got it!


drivers: wifi: uwp: Separate various wifi_rh header files

Separate various wifi_rh header files.
In uwp_tx function, remove unused variable 'data_len'
and take 'total_len' instead.

Signed-off-by: Bub Wei<EMAIL_ADDRESS>

This patch must be binding with https://github.com/unisoc/hwparam/pull/14.


Unable to connect to Blynk server across the internet...

Hi,
I am having trouble connecting to my own blynk server across the internet.
I have RPi running local blynk server on my own network at home (internal IP adress is <IP_ADDRESS>), here is the server.properties file:
server.zip
I have node-red running on a RPi that is not on my local network, but it needs to access the local blynk server across the internet and through port forwarding.
In node-red I have blynk ws node set up like this:

(I have scribbled the public IP address for security)
On my main router I have port forwarding set up like this: incoming port 9494 > local IP <IP_ADDRESS> local Port 8080
I would have expected this to work, but instead I am getting these errors:

And I am unable to get it to connect.
Am I missing something here? I did read that I might need a certificate, how do I set this up to work?
thanks!

Hi,
I don't know if you have already solved the problem, to me it would seem to be a problem of internet connectivity.
let me know
Regards


Stop button on Cocoapods

Hi,
i downloaded the cocoapods version and the stop button did not fount the function.
I could't use the cocoapods version.
Please fix it.
p

Hello @paoloandrea, what do you mean by

the stop button did not fount the function.

Can you precise a little more the context and give a code example please.

I believe what @paoloandrea is saying is that there is no .showStop member on KVNProgressConfiguration. I just ran into this.


window blind error

i get this error

for the following item

could you fix this?
thanks

Hi @TheSpirit,
sorry for the late response . Haven't seen this issue as I am not assigned to it.
I have checked the error message and this state (that the shutter is going down or up) seems not of interest. I would simply ignore the "UpDown" type message as the level.blind type in IOB should be percentage.
Currently (at least in my version) I am doing some modifications. I will add a fix for that.
Regards,
Sven

Hi @TheSpirit,
the issue should be solved using version 1.1.0. Please verify it.


274 convert hourly price to cents

Hi,
I have converted price into cents in the same manner as the other price references, however I have a concern I would like to clarify before merging:

if implemented, this will not function well with existing records, only new ones
would it be required to convert existing records in the database or...
rather use an if check against records created_at determining whether to convert output or not?

If you can let me know the preferred procedure I will be very happy to implement.
Closes #274
Thanks
Sam

Hello and thank you for your interest in the project. I think the best option is to convert existing records, using a simple SQL migration script. You're welcome to work on this issue if you'd like, and feel free to reach out to me if you need anything!
Best,

Thanks for pointing me in the right direction. I will work on the migration and push to this branch once complete and request your review.

Hi @thdebay,
All done and tested on my end. Giving desired results and no errors if column is empty.
Thanks again for the opportunity!

I reviewed and tested, it works just fine. A warm thank-you for this PR @MizouziE!

@all-contributors add @MizouziE for code,doc

https://github.com/all-contributors add @MizouziE for code and doc

@all-contributors add @MizouziE for code and doc

My pleasure! 🙏


using of road_edge in op_local_planner

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
When I used theop_loca_planner function for local path planning, the roadedge from the vector_map seemed to be ineffective, and the vehicle would ignore the roadedge when carrying out local planning and driving. I checked the code of op_local_planner, and it seemed that the roadedge information was not applied.

Expected behavior
 I hope the roadedge of vector_map can be effective in op_local_planner.

Actual behavior
 I hope the roadedge of vector_map can be effective in op_local_planner.

Steps to reproduce
I don't know.
Versions
No response
Possible causes
No response
Additional context
No response

Seems to be duplicated.
https://github.com/autowarefoundation/autoware/discussions/3065
Please refrain from opening an issue if it's not a bug.


get all new posts

how to get all new posts ? what endpoint address should be used?

See https://github.com/postaddictme/instagram-php-scraper/issues/1037


Support publish artifact to a special Azure Blob

Is there any plan about storage artifacts to private Azure Blob container?

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

ID: 0b3f565b-88e4-88d6-a534-48ec21e6e3d8
Version Independent ID: 9fca89ae-4a6e-a43a-2834-1a91ad44c256
Content: Publish Build Artifacts task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/publish-build-artifacts.md
Product: devops
Technology: devops-cicd
GitHub Login: @DavidStaheli
Microsoft Alias: dastahel

@zirain Thank you for the question!
The product team publishes the roadmap here.
If you can't find the information on the roadmap, please submit your idea here.


Already selected key-value pairs do not appear in selection menu

service:bicycle:repair and service:bicycle:retail don't appear in selection menu, even though they are in the key-value list for the node.
Problem appears on this node:
https://www.openstreetmap.org/node/371237899

It's already been fixed in https://github.com/openstreetmap/iD/issues/8155.

Thanks @maro-21! Gonna close the issue.

Yep, I'll push out a patch with this fix today or tomorrow.


Update Json-5 to latest version.

In this PR, I have bumped Json-5 to its latest version and have also bumped the version of the loader to RC-4. If I have missed anything, feel free to tell me and Ill fix it.

I will merge this if the workflow passes


Add sleep time to retries

I want to add a sleep or interval if a test fails with retries.
I.e.
tests:
    echo hello:
        config:
            retries: 4
            interval: 10s

Implemented interval in #71


Ability to map feature names

This PR adds the ability to map feature names to other names.
This introduces a new method, Feature::enforceNameMap(), which provides a customized string that will get saved to the database. This allows for easy refactoring of class based features and shorter strings in the name column.
Feature::enforceNameMap([
    'admin' => AdministrationFeature::class,
    'old-feature' => NewFeature::class,
]);

@ahinkle, I've created a PR to document the existing feature that supports doing this: https://github.com/laravel/docs/pull/9322

Thanks! I realized that as soon as I submitted this PR 😆


[Enquiry] How to use AsyncReaderWriterLock with Cancellationtoken

i am trying to use AsyncReaderWriterLock with Cancellationtoken, but i do not know if i use it correctly:
using (await the_lock.WriterLockAsync(cancellationtoken))
{
if (cancellationtoken.IsCancellationRequested)
{
return "cancelled';
}
else
{
return "lock acquired";
}
}

if the lock is not acquired due to cancellation token, is there any side effect dispose the awaitable handle?

The documentation indicates
"The cancellation token used to cancel the lock. If this is already set, then     this method will attempt to take the lock immediately (succeeding if the lock     is currently available)."
if the lock is acquired by others, will there be any blocking?

is there any side effect if the awaitable handle is disposed more than once.

Thank you very much.

First, let me recommend that you use AsyncLock instead. AsyncReaderWriterLock is almost never the appropriate primitive to use. I'm planning a blog post on this subject.
That said, the semantics of WriterLockAsync(CancellationToken) (and all other cancelable APIs) are that an OperationCanceledException is thrown if the operation is canceled. So, your test would look more like this:
try
{
  using (await the_lock.WriterLockAsync(cancellationToken))
  {
    return "lock acquired";
  }
}
catch (OperationCanceledException)
{
  return "cancelled";
}

To answer your specific questions:

if the lock is not acquired due to cancellation token, is there any side effect dispose the awaitable handle?

This is not a possible situation. If the lock attempt is cancelled, then the lock is not acquired, and you don't get a disposable object at all.

if the lock is acquired by others, will there be any blocking?

That documentation states "If this is already set..." So, if the cancellation token is already canceled, then there will not be any blocking.

is there any side effect if the awaitable handle is disposed more than once.

In AsyncEx versions 4 and earlier, yes; it's up to you to only dispose it once.
In AsyncEx versions 5 and later, no; you can dispose the disposable more than once without side effects.
AsyncEx v5 has not yet been released, but you can use the v5 synchronization primitives by uninstalling Nito.AsyncEx and installing Nito.AsyncEx.Coordination.

Thank you very much for your explanation, but why AsyncLock is better suited than AsyncReaderWriterLock? i need to support single writer and multiple readers.

An AsyncLock can handle both readers and writers - they both just take the lock.
AsyncReaderWriterLock should only be used when all of the following are true ("true" meaning "tested and proven by analysis", not "I think this might be the case"):

Some code paths are read-only and others are read/write.
Readers far outnumber writers.

If any of those are not true, then AsyncLock is the better choice.

When will AsyncEx v5 be stable? thx

The v5 release is tracked by #71. I'll post a current status update there.

AsyncReaderWriterLock should only be used when all of the following are true ("true" meaning "tested and proven by analysis", not "I think this might be the case"):
Some code paths are read-only and others are read/write.
Readers far outnumber writers.

If any of those are not true, then AsyncLock is the better choice.

It would be great to get that added to the AsyncReaderWriterLock docs.

Yes; I've been meaning to write a blog post (series?) about "which coordination primitive to use when", but haven't ever gotten around to it. I should add this to the AsyncEx docs in the meantime.


Accessing variable after panic can cause "Variable 'x' has gone missing"

If you try to access a variable immediately after a panic, then type :vars, the variable will come back from the dead. Then, trying to access it again will result in a panic "Variable 'x' has gone missing".
>> let x = 42;
>> panic!()
thread '<unnamed>' panicked at 'explicit panic', src/lib.rs:105:1
[...]
Child process terminated with status: exit code: 101
>> x
   ^ not found in this scope
cannot find value `x` in this scope
>> :vars
x: i32

>> x
thread '<unnamed>' panicked at 'Variable 'x' has gone missing', src/lib.rs:64:21
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:61
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1028
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1412
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:65
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:50
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:188
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:205
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:464
  11: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:373
  12: std::panicking::begin_panic_fmt
             at src/libstd/panicking.rs:328
  13: ctx::evcxr_internal_runtime::VariableStore::take_variable
  14: run_user_code_4
  15: evcxr::runtime::Runtime::run_loop
  16: evcxr::runtime::runtime_hook
  17: evcxr::main
  18: std::rt::lang_start::{{closure}}
  19: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:48
  20: std::panicking::try::do_call
             at src/libstd/panicking.rs:287
  21: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:78
  22: std::panicking::try
             at src/libstd/panicking.rs:265
  23: std::panic::catch_unwind
             at src/libstd/panic.rs:396
  24: std::rt::lang_start_internal
             at src/libstd/rt.rs:47
  25: main
  26: __libc_start_main
  27: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Child process terminated with status: exit code: 101

evcxr version: 0.4.7

This is expected. You can run :preserve_vars_on_panic 1 to keep them after a panic. This will be slower though.

Thanks for reporting that. The loss of the variable on panic is expected, but the subsequent panic on trying to access the variable isn't expected. The variable is supposed to be removed from the list of variables, so subsequent access attempts should result in a compilation error, not another panic.

Hmm, I'm having trouble reproducing. There must be something I'm missing, because I do get the compilation error that I'd have expected.
>> x
   ^ not found in this scope
cannot find value `x` in this scope

It turns out you don't need to try to access the variable; any compile error will do.
I'm running this on GNU/Linux, if that helps.
Here's a list of inputs to reproduce it:

let x = 42; (create a variable)
panic!() (panic)
? (any compile error)
:vars (list the variables; this is a necessary step)
x (access the variable again)

If you're still having trouble reproducing, try running evcxr with this Dockerfile:
FROM rust:1.40
RUN cargo install evcxr_repl
CMD ["evcxr_repl"]

(Run it with docker run -it image_id)

Ah, thanks. Yep, I can reproduce now. Pretty sure I know what's happening. The state (which includes which variables are defined) is copied when execution is successful, then when a compilation error is encountered, it rolls back to the last committed state. When a panic occurs, the variables are removed, but that change must not get committed.
I think I used to copy the current state at the start of execution then roll back to that copy on compilation failure, but for some reason I changed it to store the committed state. I should probably try to work out why I made that change to avoid regressing it. Hopefully I added a test. In any case, this probably shouldn't be too hard to fix. Thanks again for the report.