Exception: Could not find source plugin for ansible.eda.watchdog

While running ansible.eda.watchdog event listener, it's throwing following error
[root@localhost local-file-dir-example]# ansible-rulebook -r rulebook.yml -i inventory.yml --verbose
2023-04-07 15:43:19,654 - ansible_rulebook.app - INFO - Starting sources
2023-04-07 15:43:19,654 - ansible_rulebook.app - INFO - Starting rules
2023-04-07 15:43:19,654 - ansible_rulebook.engine - INFO - run_ruleset
2023-04-07 15:43:20,438 - ansible_rulebook.engine - INFO - ruleset define: {"name": "Local Test Runner Rules", "hosts": ["all"], "sources": [{"EventSource": {"name": "watchdog", "source_name": "ansible.eda.watchdog", "source_args": {"path": "/opt/test", "recursive": true, "ignore_regexes": [".*\\.pytest.*", ".*__pycache__.*", ".*/.git.*"]}, "source_filters": []}}], "rules": [{"Rule": {"name": "Directory change condition", "condition": {"AllCondition": [{"EqualsExpression": {"lhs": {"Event": "type"}, "rhs": {"String": "DirModifiedEvent"}}}]}, "actions": [{"Action": {"action": "run_playbook", "action_args": {"name": "playbook.yml"}}}], "enabled": true}}, {"Rule": {"name": "File change condition", "condition": {"AllCondition": [{"EqualsExpression": {"lhs": {"Event": "type"}, "rhs": {"String": "FileModifiedEvent"}}}]}, "actions": [{"Action": {"action": "run_playbook", "action_args": {"name": "playbook.yml"}}}], "enabled": true}}, {"Rule": {"name": "print output", "condition": {"AllCondition": [{"IsDefinedExpression": {"Event": "output"}}]}, "actions": [{"Action": {"action": "print_event", "action_args": {"var_root": "output"}}}], "enabled": true}}]}
2023-04-07 15:43:20,457 - ansible_rulebook.engine - INFO - load source
2023-04-07 15:43:21,093 - ansible_rulebook.engine - ERROR - Source error
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/ansible_rulebook/engine.py", line 93, in start_source
    raise Exception(
Exception: Could not find source plugin for ansible.eda.watchdog
2023-04-07 15:43:21,094 - ansible_rulebook.engine - ERROR - Shutting down source: ansible.eda.watchdog error : Could not find source plugin for ansible.eda.watchdog
2023-04-07 15:43:21,095 - ansible_rulebook.engine - INFO - Waiting for all ruleset tasks to end
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - Waiting for actions on events from Local Test Runner Rules
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - Waiting for events, ruleset: Local Test Runner Rules
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - Ruleset: Local Test Runner Rules, received shutdown: Shutdown(message='Shutting down source: ansible.eda.watchdog error : Could not find source plugin for ansible.eda.watchdog', delay=60.0, kind='graceful', source_plugin='ansible.eda.watchdog')
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - ruleset: Local Test Runner Rules shutdown no pending work
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - Action Plan Task Cancelled for ruleset Local Test Runner Rules
2023-04-07 15:43:21,095 - ansible_rulebook.rule_set_runner - INFO - Cleaning up ruleset Local Test Runner Rules
2023-04-07 15:43:21 097 [drools-async-evaluator-thread] INFO org.drools.ansible.rulebook.integration.api.io.RuleExecutorChannel - Async channel connected
2023-04-07 15:43:21 102 [main] INFO org.drools.ansible.rulebook.integration.api.RulesExecutor - Disposing session with id: 1
2023-04-07 15:43:21,121 - ansible_rulebook.rule_set_runner - INFO - {'asyncResponses': 0,
 'bytesSentOnAsync': 0,
 'end': '2023-04-07T10:13:21.107530673Z',
 'eventsMatched': 0,
 'eventsProcessed': 0,
 'eventsSuppressed': 0,
 'numberOfRules': 3,
 'permanentStorageSize': 0,
 'ruleSetName': 'Local Test Runner Rules',
 'rulesTriggered': 0,
 'sessionId': 1,
 'start': '2023-04-07T10:13:20.434142831Z'}
2023-04-07 15:43:21,121 - ansible_rulebook.engine - INFO - Cancelling all ruleset tasks
2023-04-07 15:43:21,121 - ansible_rulebook.engine - INFO - Waiting on gather
2023-04-07 15:43:21,121 - ansible_rulebook.engine - INFO - Returning from run_rulesets
2023-04-07 15:43:21,121 - ansible_rulebook.app - INFO - Cancelling event source tasks
2023-04-07 15:43:21,124 - ansible_rulebook.app - ERROR - Could not find source plugin for ansible.eda.watchdog
2023-04-07 15:43:21,124 - ansible_rulebook.app - INFO - Main complete
2023-04-07 15:43:21,126 - ansible_rulebook.cli - ERROR - Unexpected exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/ansible_rulebook/cli.py", line 196, in main
    asyncio.run(app.run(args))
  File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib64/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.9/site-packages/ansible_rulebook/app.py", line 122, in run
    raise Exception("One of the source plugins failed")
Exception: One of the source plugins failed

My rulebook.yaml
---
- name: Local Test Runner Rules
  hosts: all
  sources:
    - name: watchdog
      ansible.eda.watchdog:
        path: "/opt/test"
        recursive: true
        ignore_regexes: ['.*\.pytest.*', '.*__pycache__.*', '.*/.git.*']
  rules:
    - name: Directory change condition
      condition: event.type == "DirModifiedEvent"
      action:
        run_playbook:
          name: playbook.yml
    - name: File change condition
      condition: event.type == "FileModifiedEvent"
      action:
        run_playbook:
          name: playbook.yml
    - name: print output
      condition: event.output is defined
      action:
        print_event:
          var_root: output

Hi,
I am new to even driven ansible. So, most probably I am making some mistake.
webhook plugin is working fine. watchdog plugin is having this issue.
Do we need to explicitly install the plugin? Is it a known issue?
Thanks,
Shyam

Hi Shyam Biradar,
you have exception
Could not find source plugin for ansible.eda.watchdog
most likely you are running newer version of ansible.eda, try using ansible.eda.file_watch instead of ansible.eda.watchdog
Best wishes,
Milan


[Drupal] 7 extended support and update info

Added Extended support column for Drupal 7, information and links

Didn't realize the suggestion was applied completely. Will fix.


wrong apt keyserver parameter

In the "Add the Defender for Endpoint repository and key, add_apt_repo.yml:" section the apt key source is wrong:
WRONG:

name: Add Microsoft APT key
apt_key:
keyserver: https://packages.microsoft.com/
id: BC528686B50D79E339D3721CEB3E94ADBE1229CF
when: ansible_os_family == "Debian"

CORRECT:

name: Add Microsoft APT key
apt_key:
keyserver: https://packages.microsoft.com/keys/microsoft.asc
id: BC528686B50D79E339D3721CEB3E94ADBE1229CF
when: ansible_os_family == "Debian"

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

ID: c5b7c531-90a1-7f6b-4c1d-0a126cdea398
Version Independent ID: 5a10f1bb-6407-d706-0b79-bf448a8eda9d
Content: Deploy Microsoft Defender for Endpoint on Linux with Ansible
Content Source: microsoft-365/security/defender-endpoint/linux-install-with-ansible.md
Product: m365-security
Technology: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@lombardialess Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5220
Thanks
Sri

name: Add Microsoft APT key
apt_key:
keyserver: https://packages.microsoft.com/keys/microsoft.asc
id: BC528686B50D79E339D3721CEB3E94ADBE1229CF
when: ansible_os_family == "Debian"

This isn't actually correct, since https://packages.microsoft.com/keys/microsoft.asc isn't a keyserver. See https://docs.ansible.com/ansible/latest/collections/ansible/builtin/apt_key_module.html and a the PR https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4809/files
@msbemba @yogkumgit

@konstruktoid Thank you for the feedback. We have merged #4809 and the document is now updated.

@lombardialess Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Use GitHub mirror for FreeBSD bindists instead of FreeBSD distcache

I have double-checked each bindist's checksum, everything's matches.

I'm fine with this change, but I'm curious about the motivation.  In https://github.com/commercialhaskell/stackage-content/pull/82, we stopped using the Github mirrors for official bindists, since Github release assets don't actually perform all that well, so since then I've been sticking with the distcache assets for new FreeBSD bindists as well. Are there speed or reliability concerns about the FreeBSD distcache?

I'm fine with this change, but I'm curious about the motivation. In #82, we stopped using the Github mirrors for official bindists, since Github release assets don't actually perform all that well, so since then I've been sticking with the distcache assets for new FreeBSD bindists as well. Are there speed or reliability concerns about the FreeBSD distcache?

Oh, I see. In this case, I reverted all the changes except for GHC 8.6.5, because I removed it from the distcache already, so it needs to be pulled from GitHub.


contains in custom checks to have more power

Similar to #774 , but I would like to have control over the operation in question. In my case I would like isAny, but I can see regexMatches being powerful here too.
---
checks:
  - code: TAG_custom
    description: Custom check to ensure the Environment tag is applied
    errorMessage: The required Environment tag was missing or invalid
    matchSpec:
      action: contains
      name: tags
      value:
        Environment:
          action: isAny
          value:
          - dev
          - test
          - staging
          - production
    requiredTypes:
    - resource
    severity: ERROR
    requiredLabels:
    - aws_lb

I probably should have been more clear in #774 as this is what I was looking for as well (though even a single match used to fail).

Hey @robertstettner  - this is done, pretty much exactly as requested in #847 - checkout the example in the PR

@owenrumney I tested this out today and couldn't get it to work. I hacked together a quick test that shows it not matching when it should.
package custom

import (
	"testing"

	"github.com/stretchr/testify/assert"
)

func init() {
	givenCheck(`{
  "checks": [
    {
      "code": "CUSTOM_AWSTAG",
      "description": "AWS Environment tag is required",
      "requiredTypes": [
        "resource"
      ],
      "requiredLabels": [
        "aws_instance"
      ],
      "severity": "ERROR",
      "matchSpec": {
        "action": "contains",
        "name": "tags",
        "value": {
          "Environment": {
            "action": "isAny",
            "value": [
              "production",
	      "dev"
	    ]
          }
        }
      }
    }
  ]
}`)
}

func TestAWSTagSubMatchFailure(t *testing.T) {
	scanResults := scanTerraform(t, `
resource "aws_instance" "bastion" {
  metadata_options {
    http_endpoint               = "enabled"
    http_put_response_hop_limit = 1
    http_tokens                 = "required"
  }

  tags = {
    Environment = "test"
  }
}
`)
	assert.Len(t, scanResults, 1)
}

func TestAWSTagSubMatchSuccess(t *testing.T) {
	scanResults := scanTerraform(t, `
resource "aws_instance" "bastion" {
  metadata_options {
    http_endpoint               = "enabled"
    http_put_response_hop_limit = 1
    http_tokens                 = "required"
  }

  tags = {
    Environment = "production"
  }
}
`)
	assert.Len(t, scanResults, 0)
}

@owenrumney I'm not sure if that will fix my problem or not, for my manual tests I was using yaml but it still wasn't working. I just didn't see a quick helper method for creating a yaml check in the unit tests so I used json.
Here's what my yaml looked like:
---
checks:
  - code: TAG_Environment
    description: Custom check to ensure the Environment tag is applied
    errorMessage: The required Environment tag was missing
    matchSpec:
      action: contains
      name: tags
      value:
        Environment:
          action: isAny
          value:
            - production
            - development
    requiredTypes:
    - resource
    severity: ERROR
    requiredLabels:
    - aws_instance

@grantkl  - can you confirm which version you're using. If its a very recent one, can you update the severity to HIGH - if that fixes it then we've missed something in the rewriting of severities in custom checks

Oh I feel dumb. I thought I had updated tfsec via brew but it looks like it failed earlier. I just updated on my test yamls are working now.
Sorry about that!

Funny enough, if I change the severity to 'HIGH' I get a processing error on the yaml.
There were errors while processing custom check files. check json is not valid

Ah, I suspect you're on pre v0.46.x then, which was when we switched to high, medium and low. Don't worry, your custom checks won't be impacted once the next release is out.
You did us a favour, you highlighted an issue with the Json parsing of custom checks 👍🏼


Dynamic autoplaySpeed

Only for share this.
To get a dynamic autoplaySpeed, just change "_.options.autoplaySpeed" to the value of each delay.
In this case, i have a attribute "delay" on each image.
In the method "Slick.prototype.autoPlayIterator" and in the method "Slick.prototype.slideHandler", in the final of both, i put the code ".options.autoplaySpeed = $(.$slides[_.currentSlide]).find('img').attr('delay');" and each image got it's own delay to slide.
Sorry for my bad english :D
That's all, guys!

Closing in that this is just some helpful information and not an issue


add extra text options

This would give more flexibility for a description, enabling counters with complex titles or descriptions to be better displayed

Added: superText, subText and textSpacing

@snirp thoughts?


Trigger and labels for warnings

The tool needs to provide feedback to users when their responses indicate a risk. This feedback will appear at recap pages (#44) and in the pdf report (#43) but we need the tools to create the triggers.

The quickest option for this is to write the trigger expressions into table in a google doc and I'll translate them into code to run during the recap and recap PDF generation.  The trigger expressions table should look something like:
slide  |  field name  | condition                                   | alert level          |   message text
       |              |  (checked/selected for check/radio boxes)   | (info/warning/error) |

Otherwise, to get a control panel, editor and database together would take a few days.

These have been programmed in, but will need some more testing.

Using warning triggers on custom forms (like 2.2 or 2.3) is quite tricky, since we don't know the field names until they've completed 2.1.  I'll need to thing about that a bit.


inline: true

If i add
const config = {
inline: true,
The inline doesn't render.

Thanks for the feedback!
Problem is fixed in #1.3.2

Thanks, I tried the demo at https://codepen.io/Eazymov/pen/MEzGYv with inline: true. It did not work.

It's just jsdelivr caching, I changed version in codepen settings and now it works

Perfect, thanks!

If setting inline: true then when typing the cursor goes to the beginning of the textbox

Fixed in 1.3.3


Allow partial offline usage

Offline needs to be reconsidered/refactored to allow users to only download what they want and what they have access to.  The original approach pouchdb of pulling down the whole DB just doesn't scale.

@jkleinsc given recent work, is this issue still relevant.

@tangollama yes this issue is still relevant.  We need to do some server work for HospitalRun/hospitalrun-server#5 but then we also need to update the frontend to work with per-role databases.

@jkleinsc removing Help Wanted on this for now. This feels like a conversation between us before we ask for more help. Assigning to you for the time.

Using https://github.com/cloudant-labs/envoy could be a possibility here.  Something to investigate at some point.

FYI.  When considering off-line, we need to nail the issue of generating patient IDs while off-line.   @jkleinsc and I kicked this around a bit.   Just noting it here for a reminder.


Failed Startup Error

Describe the bug
After grill failed to ignite/startup then failed to reignite an error was shown on screen. Problem is after a couple seconds the error cleared and the screen went back to reignite but nothing was actually running.

To Reproduce
Steps to reproduce the behavior:

Start Grill
Grill does not meet startup temp
Reignite is tried
Reignite fails
Error is displayed
Screen goes back to Reignite

Expected behavior
Should stay on error screen I believe
PiFire Version:

v1.3.6 Development

Additional context
Creating this issue so I do not forget. I am not sure I can look into this until next week and by then I will probably forget this ever happened lol

Oh no!  I've had several igniters fail on me - the seem to be so dang cheap and easily broken.  I wonder if anyone makes any more robust igniters that would last longer.  Anyway, I'll keep this one in the back of my mind, and we'll see who can get to it first. :P

I think this should be fixed with one of the last updates.  In an error state, we were keeping the screen on to show the error message, but we never cleared it afterwards which means the screen stays in an active state.  I simply introduced a short delay before clearing the screen when an Error state is selected.  Anyway, give it a try and let me know if you are able to reproduce anymore.

I think this is fixed. Will close this issue and open a new one if it crops up again in the future.


Uber Ludwig not training my model.

I did everything like it was shown in the video: https://www.youtube.com/watch?v=uSOsos2eKHI. But as soon as i'll try to train the model and run the command "ludwig train -md model_definition.yaml --data_csv Tweets.csv " it says AssertionError: Model definition does not define any input features and doesn't train my model. Even though i have defined the input features.
Thanks for the help.
Archiv.zip
(YAML and csv files)

OS: MacOS 10.14.5
Python 3.74
Ludwig 0.2.1

Terminal Output:
https://github.com/TannerGilbert/Tutorials/files/3596076/Terminal.Output.txt

@doedelsnj  Two things:

the input_feature name needs to match the column name in the csv. same for output features. change the input feature name to 'text' and output to 'airline_sentiment'
you're using the wrong command line argument for model_definition. Since you're providing model definition in a file, you should use '-mdf' instead of '-md'.

I verified model training works with these changes.


Added missing Articulation type ('other-articulation') and added parse for notes with type print-Object

Some songs which have Articulation type with name 'other-articulation', currently the library still missing this type, so the app will crash if not parse this type(crash exception:Invalid articulation type...).
In music XML, some song have notes with type print-object must treat as rest notes. Ex:

<measure number="3" width="379">
      <print new-system="yes">
        <system-layout>
          <system-distance>147</system-distance>
        </system-layout>
      </print>
      <note print-object="no">
        <rest/>
        <duration>1</duration>
        <voice>1</voice>
      </note>
      <barline location="right">
        <bar-style>none</bar-style>
      </barline>
    </measure>

With the commit to parse print-object will fixed some kind of bugs like that:

After added missing parse for print-object. The music xml will display properly:


fix some error for velacp server

The type of "UpdatedAt" shoule be int64 to string.
fix "Kubecofig" to "Kubeconfig".
When kubeconfig is "IsNotFound" the "err != nil" is true .

@lic17 velacp has been changed to velaux as the code repo for the front-end project.
For the apiserver implementation, please go to:
https://github.com/oam-dev/kubevela/blob/master/pkg/apiserver


Formatting Issue

Issue Description ❗
When using the extension command in VS Code, it only applies to the copied text in the clipboard and not the selected text in the VS Code window.
Steps to Reproduce 🔄

Open any code file in VS Code.
Select text within the code file.
Open the command palette (e.g., by pressing Ctrl + Shift + P).
Type the extension command in the command palette.

Actual Results 🚫
The formatting is applied to the copied text from the clipboard, but not to the selected text in the VS Code window.
Expected Results ✅
The formatting should be applied to the selected text within the VS Code window, not just the copied text.
Additional Information ℹ

This issue affects the current version of the extension.
Reproducible on multiple operating systems (Windows, macOS, Linux).
This issue might be related to how the extension interacts with the VS Code editor.

Fixed in commit "https://github.com/MohamedSawahZC/code_scenery/commit/cd168361d7070d12c3f44b5fe56a8003850f2929"


Looking for maintainers

Basically, I don’t have the time to actively work on this plugin anymore. Issues are coming in faster than I’m able to get to them. I was kinda hoping Obsidian would build in a better implementation of this by now 😄.
At this point, I don’t know when or if I will be able to make any meaningful updates to this plugin in the future. I think this plugin has a lot of value, and I don’t want to just leave it here, withering away until it stops working completely. So I’m hoping someone (or a couple someones) will be interested in taking this on and helping expand and improve it.
If you’re interested, or have any questions, you can respond here. I will do my best to document architecture, processes, whatever else, and help out as I can.

@NomarCub or @udbhav-s either of you interested by chance? No pressure at all

Hey!
Thank you for considering. Unfortunately I don't think I'll have the time for this anytime soon.
I don't know how it works exactly, but you can try getting this into the Obsidian Hub repo, that has a Plugins seeking help page.
Do you plan on handling pull requests still?

Thanks, wasn't aware of that page. Looks like it's updated automatically, so I think this issue will get picked up next time it builds.
As far as PRs, yes for the time being, still planning on looking at them and merging them. But I may get to a point where I feel archiving this repo is my next move.

Hey, thanks for asking! I can help with some of the current open issues but I don't know if I can be a maintainer because I don't have the setup to test it on all platforms like iOS, and I'm also kinda busy with college. I don't think the plugin would necessary wither away, though, because afaik there were only breaking changes in plugins recently because of v1.0 and it should be more stable going forward.


Auto Generate Plain Text Content from HTML

Add plain text converter using xpath and libxml2
Close #437

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Working on adding some tests

@thinkingserious Excellent, I still have some work to do. The xpath query doesn't work for deeply nested content. I appreciate the swag!

No worries @cmckni3. Thanks for taking your time to contribute!

Hi,
Would like to consider adding a regex version of this to your class. Referenced here.
Thanks

Hi @cmckni3,
Are you still interested in completing this one? No worries, if not.
With Best Regards,
Elmer


Bluetooth: Mesh:  Mesh Model State Binding.

In zephyr/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/
According Mesh Model Spec.
Generic Power OnOff Server has Generic Power Actual state bindings with the Generic OnOff State.
Light Lightness Server has Light Lightness Actual State also bindings with the Generic OnOff State.
https://github.com/zephyrproject-rtos/zephyr/blob/c0c4ba85164e7ba2351315e763f0c3b9a0473ac9/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/src/mesh/state_binding.c#L284-L288.
As shown in the code above,
When the state of lightness actual state changes, we will also change Generic OnOff States. But I did not find any changes to the Generic Power OnOff State.

@vikrant8051 any comments on this?

I'm mistake. But I still think that the coupling of this example is too big to be tailored. I think it would be better if you could make state bindings more abstract.

Generic Power OnOff Server has Generic Power Actual state bindings with the Generic OnOff
State
Light Lightness Server has Light Lightness Actual State also bindings with the Generic OnOff
State.

Generic Power OnOff Server has Generic OnPowerUp state.

A Generic Power OnOff Server shall use the Generic OnPowerUp state to determine the behavior after a node is powered up.

Value of Generic ONPowerUp state should not get vary as we vary Gen. OnOff stae or Light Lightness Actual State. Because only user can change it (for e.g via SmartPhone Mesh App which supports  Generic Power OnOff Client) or manufacturer fixed it any value out of 0x00, 0x01 or 0x02.

Genric OnOff & Light Lightness Actual State are bounded bidirectinally.
But same is not true for Generic OnPowerUp state with any other state.
It is only one directional binding which execute only when device Boot up or get power.
For details, please refer Table 3.6 of Mesh Model Specification.
As per it, after device gets power on, algorithm reads value of Generic OnPowerUp state from persistence storage, & adjust all states associated with Lightness (Genric OnOff -> Generic Level -> Light Lightness Actual -> Light Lightness Linear -> Light CTL Lightness).

So it is not a bug.

I'm mistake. But I still think that the coupling of this example is too big to be tailored. I think it would be better if you could make state bindings more abstract.

@menglingao1997
It is already represented in most simplified way compared to what Bluetooth Mesh Model Specification has stated. Architecture has designed with lots of care & thorough testing (including PTS tests). Several times I had reorganized the things to make it more simple, robust & bug free implementation. There was/is no reference openly available since all available stacks from various Semiconductor Vendors are closed source/black box.
Kindly understand full implementation first & help me to optimized it further. But condition are, it should not add unnecessary burden on algorithm & bug free.
Because personally I am not happy with Bluetooth Mesh's Group of Nodes performances (This is true even with any available Market Solutions based on Bluetooth Mesh ).
Regards,
Vikrant

Hi @menglingao1997,
https://github.com/vikrant8051/zephyr/tree/fix_bugs32/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app
Please go through with above project which is improved version of onoff_level_lighting_vnd_app.
(https://github.com/zephyrproject-rtos/zephyr/pull/20170 this is PR which will merged soon to reflect the changes.)
Hope you will like it. Any feedback or suggestions are highly welcome.
Thank You !!


Incorrect Gas price

Description
We use the Besu node, and during the process we understood that the gas price is calculated wrongly.
The OpenEthereum’s value is changing from block to block, but for Besu it is the same.
Method that we use: eth_gasPrice
Can you please check, if everything works correct?
Request:
{
    "id": "blockNumber",
    "jsonrpc": "2.0",
    "method": "eth_gasPrice",
    "params": []
}

Response(OpenEthereum):
Response:
{
    "jsonrpc": "2.0",
    "result": "0xcce416600",
    "id": "blockNumber"
}

Response(Besu):
Response
{
    "jsonrpc": "2.0",
    "id": "blockNumber",
    "result": "0x3e8"
}

@wetryingtodorock thanks for raising this! Indeed, the JSON RPC spec is quite vague about this call:

Returns the current price per gas in wei.

We currently interpret that as returning the minimum gas price allowed on the network (set by the min-gas-price flag). It seems that OE and Geth use the median/average gas price over a range of previous blocks, which produces some ok but not great estimates
(see this Geth issue, for example).
Is this what you would like to see from the endpoint? If you have any specific requirements, we'd love to hear them and are open to adapting the endpoint.

@timbeiko  thanks for the answer!
Probably OpenEthereum and Geth do not always effectively make an estimate, but some of our users expect exactly the same response when calling a method, as in the OpenEthereum client.
Since we are considering Besu as an alternative to OpenEthereum and Geth for our users, we would be happy to expect this in future Besu releases.

The best documentation I've found on what OE does is this comment - https://github.com/openethereum/parity-ethereum/issues/1265#issue-159997710

In the event of zero transactions in the last 100 blocks we should fall back to our current behavior (return the CLI set value)

Would love to see Hyperledger does exactly what Geth and OpenEthereum do too. Extra config parameters specifying the X-percentile of the last Y blocks would be nice.

@sammy1991106 should the defaults be OE values (100 blocks, 50%), or Geth's documented defualts (20 blocks, 60%)?

@shemnon Personally, I'd prefer the default to be 100 blocks and 50% if pulling 100 blocks of data wouldn't affect the performance (basically the more blocks are considered the better?). Another thing to note is that on chains such as Ethereum Classic, a lot of blocks are empty. So maybe it would make sense to only consider the last X blocks that actually have some transactions in there?

I think 100 and 50% make sense as defaults FWIW. A lot of people are coming from OE, so keeping the same ones will result in similar behaviour which is nice. These estimates are not as reliable as 3rd party estimates, so their use is somewhat limited anyways.
Agreed that empty blocks should be part of the calculation and if the last 100 blocks are empty, then reverting to the minimum makes sense.

If there are a lot of empty blocks I don't think transaction inclusion will be a big issue.
The downside of too much of a windows is (a) performance and (b) it hides local spikes.  I think 100 blocks (~20 minutes) is about as far back as one would want to go for an on-chain oracle.  Like Tim said 3rd parties are the best because they take into consideration the entire mempool.

@wetryingtodorock this should be fixed by @shemnon's PR above. We'll be releasing a new version of Besu today which will contain the new behaviour. I'll close this issue for now, but please reopen if needed. Thanks again for flagging this!


WIP: Ruby 2.7.0 compat fix

Just playing around, not ready yet

I just released 1.1.1 which fixes support for Ruby 2.7.0.


Phasing uses pyephem for lst

Should switch to astropy and use Bryna's IERS_A table fix

this needs to be re-avaluated.  Now we're also using ephem.Observer which also doesn't have the current leap second table.

Too many questions about how pyephem works, including lack of leap seconds and concerns about which ra/dec values to use. Consider switching to skyfield.

Astropy may provide the functionality needed.

should be addressed as part of fixing phasing, see issue #148.


LiveObjectDetection not working

Step 1: Describe your environment

Android device: Android Emulator
Android OS version: 10
Google Play Services version: 12451000

Step 2: Describe the problem:
I get the following a lifecycle and observer related error in console/logcat while launching the LiveObjectDetection Activity. In result the Object detection is not working.
Steps to reproduce:

Merge Barcode detection related code into LiveObjectDetection Activity
Delete all un-used resources and classes
run the app and launch the LiveObjectDetection Activity
You will see the mentioned error in logcat and console of debug view

Observed Results:

Logcat outout
Error preloading model resource
com.google.mlkit.common.MlKitException: Internal error has occurred when executing ML Kit tasks
at com.google.mlkit.common.sdkinternal.ModelResource.zza(com.google.mlkit:common@@16.1.0:32)
at com.google.mlkit.common.sdkinternal.zzl.run(Unknown Source:10)
at com.google.mlkit.common.sdkinternal.zzp.run(com.google.mlkit:common@@16.1.0:3)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzd(com.google.mlkit:common@@16.1.0:24)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zza(com.google.mlkit:common@@16.1.0:30)
at com.google.mlkit.common.sdkinternal.zzh.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.IllegalStateException: Method addObserver must be called on the main thread
at androidx.lifecycle.LifecycleRegistry.enforceMainThreadIfNeeded(LifecycleRegistry.java:317)
at androidx.lifecycle.LifecycleRegistry.addObserver(LifecycleRegistry.java:172)
at com.google.android.libraries.intelligence.acceleration.ProcessStateObserver.zza(com.google.mlkit:vision-internal-vkp@@17.0.0:10)
at com.google.mlkit.vision.vkp.PipelineManager.start(com.google.mlkit:vision-internal-vkp@@17.0.0:128)
at com.google.mlkit.vision.objects.defaults.internal.zzd.load(com.google.mlkit:object-detection@@16.2.0:74)
at com.google.mlkit.common.sdkinternal.ModelResource.zza(com.google.mlkit:common@@16.1.0:24)
at com.google.mlkit.common.sdkinternal.zzl.run(Unknown Source:10)
at com.google.mlkit.common.sdkinternal.zzp.run(com.google.mlkit:common@@16.1.0:3)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzd(com.google.mlkit:common@@16.1.0:24)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zza(com.google.mlkit:common@@16.1.0:30)
at com.google.mlkit.common.sdkinternal.zzh.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)

@yasiralijaved the best place to file MLKit issues is now here, that's where the MLKit team is watching:
https://github.com/googlesamples/mlkit
I can't transfer this issue automatically since GitHub doesn't allow cross-organization transfers.

@samtstern thanks. The issue has been moved to the suggested place.


💅 generic function with any parameters

Environment information
CLI:
  Version:                      1.5.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.11.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.2.4"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Rule name
lint/suspicious/noExplicitAny
Playground link
https://biomejs.dev/playground/?code=ZgB1AG4AYwB0AGkAbwBuACAAZgBvAG8APAAKACAAIAAgACAAVAAgAGUAeAB0AGUAbgBkAHMAIABSAGUAYwBvAHIAZAA8AHMAdAByAGkAbgBnACwAIAAoAC4ALgAuAGEAcgBnAHMAOgAgAEEAcgByAGEAeQA8AGEAbgB5AD4AKQAgAD0APgAgAHUAbgBrAG4AbwB3AG4APgAsAAoAPgAoAGYAdQBuAGMAdABpAG8AbgBzADoAIABUACkAOgAgAFQAIAB7AAoAIAAgACAAIAByAGUAdAB1AHIAbgAgAGYAdQBuAGMAdABpAG8AbgBzAAoAfQA%3D
Expected result
In this case, I expect no errors on the generic or to be able to dissociate it with a commentary.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

You could use unknown here?

I cannot use unknown in the Array or instead for the array because I use in another part of my project Parameters<T[K]>.
The file where you can find the code and see the error it can give : https://github.com/hanako-eo/neige/blob/main/packages/http/src/ffi.ts

for never it works (which seems a bit odd to me, but I'm not going to complain) and I'm well aware that the use of any can be dangerous, but it's one of the rare cases where any really reflects the type of give. And in this case, if I replace the any with never I've got a semantic problem, even if in fact it works, never doesn't mean that, it's misused. I would have liked to use Function but it doesn't have the same meaning as (...args: any) => any for TypeScript (and I understand why) and I think the only way to describe any function while remaining flexible is with (...args: any) => any and any. I share your opinion on the unsafety of any but without losing the semantics, it seems sensible to me to use any. (I don't know if I've made myself clear enough ^^', sorry if I haven't)

for never it works (which seems a bit odd to me, but I'm not going to complain)

It is not so easy to get because you dive into type realm.
never is a subtype of all types, also called the bottom type.
unknown is a super-type of all types, also called the top type.
any is any type.
For type safety, you have to use unknown or never where appropriate.
This depends on type variance.
Basically if you expect a function (B) => A and B is a subtype of A, then you can use a function (A) => B.
The return type is covariant, and the parameter type is contravariant.
Let's take an example:
class Entity {
  constructor(readonly name: string) {}
}
class B extends Person {
  constructor(name: string, readonly age: number) { super(name); }
}

declare let f: (b: Person) => string;
declare let g: (b: Entity) => string;

// valid because `g` expects an`Entity` and `f` ensures to provide a `Person` that is a subtype
f = g;
f(new Person("anonymous". 30));

// invalid because `f` expects a`Person` and `f` doesn't ensure that
g = f; // compile error
g(new Entity("entity"));

In your case you just say that T is a subtype of (extends) (...args: never[]) => unknown, meaning that you accept a function with a return type that is a subtype of unknown and the type of the parameters that are a super-type of never.
never is the safe choice here.
I think we could improve the rule to propose never when it makes sense.

Ok, I see. Variance isn't a subject I've mastered to perfection yet, I'm familiar with it in Rust, but I've never seen it in TypeScript. Or maybe I just haven't made the mental connection yet. It still disturbs me a bit to have to use never because even though I understand what you're saying, I really have the impression that never isn't made for that.


Bugfix CSVLogger Callback separator and append parameters, added tests

CSVLogger callback did not regard separator value and prepended header to existing files although append argument was specified.
Also, added tests to confirm functionality.

@fchollet Sorry for that, should be fixed

LGTM.


Benchmarks use PyParser_ASTFromStringObject, which is removed from Python 3.10

Benchmarks fail to compile on a system with Python 3.10, in my case, Fedora 35.
[dalley@localhost RustPython]$ cargo bench
   Compiling rustpython v0.1.2 (/home/dalley/Devel/rustpython-dev/RustPython)
error[E0425]: cannot find function, tuple struct or tuple variant `PyParser_ASTFromStringObject` in crate `python3_sys`
  --> benches/execution.rs:82:32
   |
82 |         let ret = python3_sys::PyParser_ASTFromStringObject(
   |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in `python3_sys`

For more information about this error, try `rustc --explain E0425`.
error: could not compile `rustpython` due to previous error

https://github.com/python/cpython/pull/25001
https://github.com/dgrunwald/rust-cpython/commit/7bcf2d305851b5bd22f20c070e0dd75e71ebd388#diff-3a5720e55119ee77dd2db4a0e191e513099d227760a8c40891a9f78872b46982R91

git-blame suggests @coolreader18

What is the status on this? The benchmarks are still failing . . .


Fix some tests, because of not being able to mem::take net.rdex

Related to https://github.com/HigherOrderCO/hvm-core/pull/42

Not valid anymore after https://github.com/HigherOrderCO/hvm-lang/pull/194


handle changeListener inputs in transactions correctly

This is something that would help us in handling the changes made by transactions and lessen the amount of updates that take place.
Currently, database changes made in @transaction functions immediately notify the changeListener and start to update the table in streams. This has the following problems:

The tables are updated, even if the transaction is not finished yet (and therefore no changes have been persisted yet)
If a transaction e.g. deletes some entries in a table and immediately inserts them again, two notifications are put inside the changeListener, adding unnecessary refresh cycles.
When a stream (e.g. on joins) has to listen on multiple entity names at once, even more unnecessary refreshes happen.
If the transaction fails, the streams will get updated even if nothing happened.

Because of the reasons above, I propose to change the type of the changeListener from Stream<String> to Stream<Set<String>> and put a proxy changeListener into the transaction generation (Line 32, see below), which buffers all changes and then submits them together once the transaction was completed successfully. This adds some overhead into transactions (for the proxy) and some smaller overhead for streams, which now have calculate an intersection, instead of a simple contains calculation for filtering relevant updates.
I want to hear your input first, @vitusortner and I think that I probably won't start to work on this soon. (I'm currently having more fun with the sqlparser :wink: )
https://github.com/vitusortner/floor/blob/18117ed397b5787905576aedad90e0f347931792/floor_generator/lib/writer/transaction_method_writer.dart#L27-L36
A small note: I was surprised to see that adding this to transactions is far easier than I imagined.

Ah right, one more thing:

Is there a reason why the transaction currently only returns void? Afaict it should be able to return anything (wrapped inside a Future, obviously).

Ah right, one more thing:
* Is there a reason why the transaction currently only returns void? Afaict it should be able to return anything (wrapped inside a Future, obviously).

was adressed in #381


dev/guion-bluford regression: allow ref's in dbt_project.yml var configs

Issue
Issue description
The vars config in a models: block of dbt_project.yml should support ref() functions, but they currently fail with the error: 'ref' is undefined. I think this indicates that the compilation context for these vars configs has changed, though I'm not sure exactly in which branch that occurred.
In addition to the ref function working, we sure be sure to maintain parity with the context provided in 0.11.x, unless we explicitly choose to make breaking changes.
The error message here is pretty sparse -- it took me a while to track down the source of this issue. @beckjake - are you separately working on related code here? Something about error handling for jinja code sounds familiar, but I might be misremembering things. The actual error reads:
$ dbt -d run
Encountered an error:
Compilation Error
  'ref' is undefined

with no further info about it in the logs.
Results
'ref' is undefined (see example below)
System information
The output of dbt --version: dev/guion-bluford
Steps to reproduce
# dbt_project.yml

models:
    vars:
        abc: '{{ ref("some_model") }}'

$ dbt compile

vars + project.yml + new bug = Almost certainly caused by PR #1033


Would it be okay to create a fork?

Hi @prc5. It seems that this repository hasn't received much attention lately, and I think that's a big shame because it's really great. We are planning on using it in our upcoming product at my work place.
Would it be okay if I create a fork and release as @company/react-zoom-pan-pinch? First and foremost the fork would fix the issue with the missing source files (#266), update dependencies to fix some of the security issues reported by Dependabot, and finally to ensure it works with React 18 and update the peer dependency (#292).

I have released @pronestor/react-zoom-pan-pinch fork. So far it's just fixing #266.

I will leave this issue open for while, so that @prc5 has a chance to see it.

Thank you @janaagaard75. I'm still learning React and I really did not want to work this bug out :)
I think what you propose should be good because it's under the MIT license

Thank you so much for doing this @janaagaard75! A real shame that this library has not been given much attention.

You're all welcome. I will pass it along to my boss for allowing me to use some of my time on open source.
There are two things that you can do to help:

See if there are any of the open pull requests to this repo that should be carried over to the fork. I believe that I have made a comment in here, in the ones that have been ported.
There are some bugs that have been reported, that I have yet had time to dig into. If you spend some time on a bug, and only find a partial solution, feel free to comment on the bugs, because your findings might make it easier to create a pull request with a fix.

@janaagaard75 I'm back with maintenence, thanks for helping! If you're interested in working on this, or merging your changes, we can talk about it 🙌🏻

So great to hear that you're back, @prc5. I hope you're well. I would gladly help here, but I all honesty, the only real thing that I managed to change in the fork that I created, was to improve the parameters used in the Storybook stories a bit. It shouldn't be that hard to port these changes to this repo - I'll create a pull request.


fix: test out pipeline catalog changes

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan 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

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
1dd9bfe6bb0af3fe6fefa71bbc345e464f17139f
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Switch to using HTTP POST

This changes from using net/http get to post, this makes it a bit simpler to construct the parameter JSON string, and follows the aria2 doc's suggested method more closely. (python's urllib2 will use POSTs instead of GETs for the HTTP protocol when provided data)
Built off of my previous two PR's.

Thanks a lot for these PRs! Really appreciated ;)

Thanks for the gem! I'm gonna be using it a lot this week so I might come back with some more!
Sent from my iPhone

On Jan 20, 2016, at 1:02 AM, Jiahao Li<EMAIL_ADDRESS>wrote:
Thanks a lot for these PRs! Really appreciated ;)
—
Reply to this email directly or view it on GitHub.

No prob! Definitely come back with whatever changes you need. Also feel free to add yourself to the list of authors in the gemspec ;)


numpy.power on sparse matrix attempts to do matrix power not elementwise

numpy power seems to go to a matrix power routine for sparse matrices.
Reproducing code example:
    import scipy.sparse as sps
    import numpy as np
    a = np.array([[1,2,3],[4,0,0]])

    np.power(a,2)

    np.power(sps.csr_matrix(a),2) # this fails

    sps.csr_matrix(a).power(2).todense()

Error message:
Traceback (most recent call last):

  File "<ipython-input-7-513a059a6886>", line 1, in <module>
  np.power(sps.csr_matrix(a),2)

  File "/home/sean/anaconda2/lib/python2.7/site-packages/scipy/sparse/base.py", line 539, in __pow__
raise TypeError('matrix is not square')

TypeError: matrix is not square

Scipy/Numpy/Python version information:
('0.19.0', '1.12.1', sys.version_info(major=2, minor=7, micro=13, releaselevel='final', serial=0))

This is intentional, as the spmatrix class mimics the API of np.matrix, not np.ndarray. I agree that it's not ideal, but until we get a new sparse ndarray-like, it's working as intended.

Even when m is a numpy.matrix, numpy.power(m, 2) is computed element-wise:
In [36]: m
Out[36]:
matrix([[ 1,  0,  0, -1],
        [ 0,  0,  0,  0],
        [ 3,  2,  0,  0],
        [ 0,  0,  5,  0]])

In [37]: np.power(m, 2)
Out[37]:
matrix([[ 1,  0,  0,  1],
        [ 0,  0,  0,  0],
        [ 9,  4,  0,  0],
        [ 0,  0, 25,  0]])

Because numpy knows nothing about scipy's sparse arrays, all it can do with them is dispatch the call to the __pow__() method of the argument.  And for scipy's sparse arrays, that implements matrix multiplication.  So even though the docstring for numpy.power() says it computes the power element-wise, once it dispatches, it has no control over the calculation.
Note, however, that sparse arrays also have a power() method that operates element-wise:
In [43]: from scipy.sparse import csr_matrix

In [44]: s = csr_matrix(m)

In [45]: s.A
Out[45]:
array([[ 1,  0,  0, -1],
       [ 0,  0,  0,  0],
       [ 3,  2,  0,  0],
       [ 0,  0,  5,  0]], dtype=int64)

In [46]: s.power(2).A
Out[46]:
array([[ 1,  0,  0,  1],
       [ 0,  0,  0,  0],
       [ 9,  4,  0,  0],
       [ 0,  0, 25,  0]], dtype=int64)

The __pow__() method, on the other hand, does a matrix power:
In [47]: s.__pow__(2).A
Out[47]:
array([[ 1,  0, -5, -1],
       [ 0,  0,  0,  0],
       [ 3,  0,  0, -3],
       [15, 10,  0,  0]], dtype=int64)

__pow__() is the implementation of the ** operator:
In [49]: (s**2).A
Out[49]:
array([[ 1,  0, -5, -1],
       [ 0,  0,  0,  0],
       [ 3,  0,  0, -3],
       [15, 10,  0,  0]], dtype=int64)

Should numpy check for a power() method before attempting to use the __pow__() method?  I don't know, but I suspect there are (or should be) some API guidelines written down somewhere for this type of dispatching.

Sorry, I see that I was too hasty in my response.
Maybe this is something that the new __array_ufunc__ logic will help clear up?

AFAICS, __array_ufunc__ cannot be used for sparse matrices.

AFAICS, __array_ufunc__ cannot be retrofit on scipy's current sparse matrices, it's not compatible with the multiplication semantics and breaks backward compat.

Hmm, I'm puzzled now, didn't see that expressed before. IIRC __array_ufunc__ was originally written to make scipy.sparse matrices more interoperable with ndarrays and ndarray-like types.

Are there any workarounds for taking scalar powers of matrices, which avoid this bug?


Refactoring exec doc to new pattern

The doc refactor merged before exec. Change to bring exec into alignment.

IGTM - will do so when regression test finishes.


I couldn't find AppsFlyerLib.getInstance().sendPushNotificationData(this) in the sdk.

I cant use sendPushNotificationData in Flutter sdk.
# Appsflyer SDK
  appsflyer_sdk: 6.2.3+1

I found this in ReactNative plugin:
https://github.com/AppsFlyerSDK/appsflyer-react-native-plugin/blob/master/index.js#:~:text=appsFlyer.-,sendPushNotificationData,-%3D (pushPayload) %3D> {
Thanks for attetion!

API added


Fix a misspelling

Thank you for the PR! I've applied the suggested reviewer fix and will merge this.


README.md Update Yarn Command

Updated Version Number in Yarn Command String.
The Current v20.3.0 seem to throw Sigfaults when sending.

outdated


Vue Integration

Fixing #1 and #2.
We are 99% there.
We are just missing something about vue template compilation.
Also we would like to have:

JSX support - not sure if this is possible with Vue, seems like Vue prefers to use its own syntax style... if so, oh well
Just need to optimize some options in webpack.config.js. The output and devserver options have always been a bit confusing for me
Eventually get the actual full hello world going.

This deviates from master which @DrFacepalm was using the vue2 CLI for. This is actually using vue3, from first principles.

Webpack
Typescript

That's it. No babel.
More things to read here: https://v3.vuejs.org/guide/installation.html#from-cdn-or-without-a-bundler
To run this.
npm run server

For @DrFacepalm to continue.
Also @robert-cronin you should watch this as well, as this will be relevant for Polykey GUI. And also... that one will be even more complex as that's using Electron for Desktop and NativeScript for Mobile.

Key thing to understand about this SPA demo, is that it's a demo of SPA. An SPA app is not npm installable unlike typescript-demo-lib. An SPA app actually needs to be "hosted" by a web server.
The more sophisticated one is typescript-demo-iso which will then need to have both frontend and backend done.
Whereas Polykey is none of these, but will use some of the ideas from iso (involving multiple webpack targets) and this one.

Key thing to realize with spa demo. There are NO dependencies. Everything is in devDependencies. All libraries are bundled. Although the bundler may choose to alias certain libraries to CDN links.

Just pushed up changes to webpack.config.json, i've added an exports default app in index.js (tryign to get it to work with testing). The main change here is that:

in the appConfig, in resolve, I've added: alias: { 'vue': 'vue/dist/vue.esm-bundler.js' }
in plugins: ive added:

new webpack.DefinePlugin({
      __VUE_OPTIONS_API__: true, // enable/disable Options API support,
      __VUE_PROD_DEVTOOLS__: false // enable/disable devtools support in production
})

sourced from: https://github.com/vuejs/vue-next/tree/master/packages/vue#bundler-build-feature-flags

No extra dependencies needed?
On 9/24/20 8:52 PM, DrFacepalm wrote:

Just pushed up changes to |webpack.config.json|, i've added an exports
default app in index.js (tryign to get it to work with testing). The
main change here is that:

in the |appConfig|, in |resolve|, I've added: |alias: { 'vue':
'vue/dist/vue.esm-bundler.js' }|
in plugins: ive added:

new  webpack.DefinePlugin({
VUE_OPTIONS_API:true,  // enable/disable Options API support,
VUE_PROD_DEVTOOLS:false  // enable/disable devtools support in production
})
sourced from:
https://github.com/vuejs/vue-next/tree/master/packages/vue#bundler-build-feature-flags
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MatrixAI/Typescript-Demo-Spa/pull/3#issuecomment-698269421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE4OHIPPTXAEX2HPM2NPHDSHMQGHANCNFSM4RXASLHQ.

No extra dependencies needed?
…
On 9/24/20 8:52 PM, DrFacepalm wrote: Just pushed up changes to |webpack.config.json|, i've added an exports default app in index.js (tryign to get it to work with testing). The main change here is that: * in the |appConfig|, in |resolve|, I've added: |alias: { 'vue': 'vue/dist/vue.esm-bundler.js' }| * in plugins: ive added: new webpack.DefinePlugin({ VUE_OPTIONS_API:true, // enable/disable Options API support, VUE_PROD_DEVTOOLS:false // enable/disable devtools support in production }) sourced from: https://github.com/vuejs/vue-next/tree/master/packages/vue#bundler-build-feature-flags — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE4OHIPPTXAEX2HPM2NPHDSHMQGHANCNFSM4RXASLHQ.

No, webpack's DefinePlugin is built in so i just had to bring in webpack. which we already have. Didn't have to do any extra installs

So that enables dynamic compilation? What if we want webpack to compile the vue templates ahead of time assuming we aren't using JSX. But I'm still interested in seeing if JSX can still be used.

I think the .vue files are done such that their render() function is compiled at build time, so if that's what you're talking about then there's an extra webpack dependency: https://vue-loader.vuejs.org/guide/#vue-cli. I'll have to make and play around with some .vue files to se how it works.

So vue SFC is now working with the latest vue-loader. However the index.ts had to be changed to index.js. So please investigate how to use index.ts instead. Or to make our ts-loader work properly with vue-loader.
So it seems like something needs to be done to the vue-loader in order for it make understanding of the typescript files.

Following:

https://dev.to/lmillucci/building-a-vue-3-component-with-typescript-4pge
https://blog.logrocket.com/new-features-in-vue-3-and-how-to-use-them/

The index.ts now works.
@DrFacepalm needed the sfc to compile the SFC.
The last thing is to check how to bring in CSS into the vue.
At this point you may need the CSS loader. But try it anyway.

Now we can use ts inside the SFC, and that required the:
        options: {
          appendTsSuffixTo: [/\.vue$/]
        }

So @DrFacepalm needs to test 2 things:

Bringing in CSS
Bringing in images

These may require extra loaders. Not sure. Just test them.
It looks like we are not using JSX at all. That's fine. It seems vue is meant to be using these kinds of SFCs.

Note that it's important to realize that https://www.npmjs.com/package/vue-loader is needed, but atm it requires a 16.0.0 version which then supports the "@vue/compiler-sfc": "^3.0.0".
Atm, it's not yet released. It's still under the next alias. But we are pinning it in the package.json. When 16.0.0 is properly released, then we can actually just use it normally.

Using this repo: https://github.com/vuejs/vue-next-webpack-preview as a base, there is now a css loader.
We're using MiniCssExtractPlugin and we've also had to install css-loader

https://webpack.js.org/guides/asset-management/#loading-images
webpack has a file-loader so we just have to npm install -D file-loader and then add a rule to use file-loader for (png|svg|jpg|gif) files.

So this should be ready for merge soon?
Only thing is:

Testing
Storybook

For testing, there's a framework @vue/test-utils: https://vue-test-utils.vuejs.org/guides/#getting-started. Going to bring that in to try out.

I've changed the jest config:
Added:
  "transform": {
    "^.+\\.vue$": "vue-jest",
   ...
  },
  moduleFileExtensions: ['vue', 'js', 'json', 'jsx', 'ts', 'tsx', 'node'],

Also added to package.json:

"@vue/test-utils": "^2.0.0-beta.5"
"vue-jest": "^5.0.0-alpha.4"

There are some problems however. The index.test.js imports App, and tries to mount it using @vue/test-utils's mount but it throws an error when it encounters the image. Removing the image from the component's template runs the test, but still has a warning in index.ts saying "Failed to mount app: mount target selector returned null".

I've looked into storybook but for vue3, it seems like the support is still being developed.

https://github.com/storybookjs/storybook/issues/10654

This issue goes into the progress of that.
There is a work in progress package released here: https://www.npmjs.com/package/@andoshin11/storybook-vue3 though.

This should be ready to merge.

Tests should still be written in typescript. Are you sure the test are written properly?

Can you ignore the .vscode stuff.

No commonjs is only for library. For spa es6 is fine.
On 28 September 2020 11:22:47 pm AEST, DrFacepalm<EMAIL_ADDRESS>wrote:

@DrFacepalm commented on this pull request.

 "esModuleInterop": true,

"allowSyntheticDefaultImports": true,
"moduleResolution": "node",

"module": "CommonJS",
"target": "ES2016",

"module": "esnext",

Changed the module back to ComonJS.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/MatrixAI/Typescript-Demo-Spa/pull/3#discussion_r495934518

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Yea.
On 28 September 2020 11:28:04 pm AEST, DrFacepalm<EMAIL_ADDRESS>wrote:

@DrFacepalm commented on this pull request.

   test: /\.vue$/,

   loader: 'vue-loader'

 },

 {

   test: /.tsx?$/,

   loader: 'ts-loader',

   options: {

     appendTsSuffixTo: [/\.vue$/]

   }

 },

 {

   test: /\.css$/i,

   use: [ MiniCssExtractPlugin.loader, 'css-loader' ]

 },

 {

   test: /\.(png|svg|jpg|gif)$/,

I just did some quick reading, it seems like local font files should
work with file-loader, thought it would need some more config:
https://chriscourses.com/blog/loading-fonts-webpack
Shall i add that in too?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/MatrixAI/Typescript-Demo-Spa/pull/3#discussion_r495938220

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

in tsconfig.json:
    "module": "es6",
    "target": "ES2016",

in webpack.config.js:
      {
        test: /\.(woff|woff2|eot|ttf|otf)$/,
        use: [
          'file-loader'
        ]
      },

This handles font files.


Move CI to GitHub actions

@fungiboletus gave an example GitHub action workflow for building this image:
https://github.com/SINTEF/octant-dashboard-turnkey/blob/1dc9048028295a9265c5d4356cf6585af13acdde/.github/workflows/docker-images.yaml
Having GitHub action could help contributors see how the Docker image is really built and how the Helm package is deployed. It could also automate the action of publishing a new version which is, for the Helm package part, manual for now.

Octant has been deprecated by WMware/Tanzu, so we are closing all issues.


fix(events): Fix unexpected indent

Types of changes
Thanks for sending a pull request! Please fill in the following content to let us know better about this change.
Please put an x in the box that applies

[x] Bugfix
[ ] New feature
[ ] Refactoring
[ ] Breaking change (any change that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Other (please describe)

Description
Describe what the change is
Fix unexpected indent
Steps to Test This Pull Request
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Related Issue
If applicable, refernce to the issue related to this pull request.
More Information
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here. You may also want to refer
to how to wirte the perfect pull request

Codecov Report

Merging #1017 (2388c5e) into master (f42d727) will decrease coverage by 0.07%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##           master    #1017      +/-   ##
==========================================
- Coverage   70.11%   70.04%   -0.08%
==========================================
  Files          81       81
  Lines        3142     3151       +9
==========================================
+ Hits         2203     2207       +4
- Misses        939      944       +5

Impacted Files
Coverage Δ

src/events/api/urls.py
100.00% <ø> (ø)

src/events/api/views.py
56.00% <44.44%> (-6.50%)
:arrow_down:

Continue to review full report at Codecov.

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


Update openSenseMap Block

Update openSenseMap Block to bypass ratelimit
Update the openSenseMap Block according to the ratelimit. Send all Values in one Request and not every single value as a separate request.
ToDo:

[ ] Update the senseBox Library
[ ] Update Block
[ ] Provide a warning if a there is a conflict between the selected time and the ratelimit.

closes via #159


Consider fixing warnings emitted by ShellCheck

ShellCheck is a static analysis tool for shell scripts. I ran it on this codebase and here's the list of warnings emitted run through uniq. We can decide individually what warnings we care about and don't.
SC2007: Use $((..)) instead of deprecated $[..]
SC2016: Expressions don't expand in single quotes, use double quotes for that.
SC2034: attempt appears unused. Verify use (or export if used externally).
SC2044: For loops over find output are fragile. Use find -exec or a while read loop.
SC2046: Quote this to prevent word splitting.
SC2048: Use "$@" (with quotes) to prevent whitespace problems.
SC2078: This expression is constant. Did you forget a $ somewhere?
SC2086: Double quote to prevent globbing and word splitting.
SC2146: This action ignores everything before the -o. Use ( ) to group.
SC2153: Possible misspelling: BUCKET_NAME may not be assigned, but bucket_name is.
SC2155: Declare and assign separately to avoid masking return values.
SC2156: Injecting filenames is fragile and insecure. Use parameters.
SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.
SC2166: Prefer [ p ] && [ q ] as [ p -a q ] is not well defined.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.
SC2196: egrep is non-standard and deprecated. Use grep -E instead.
SC2230: which is non-standard. Use builtin 'command -v' instead.

Notes:

We probably want to ignore unused warnings for instances like TESTBENCH_DUMP_LOG. The warning complaining about attempt (where attempt is just a dummy variable) suggests renaming it to _ instead.

Bash is perfectly OK with nested quotes. Where we are using dirname $0, the $0 should also be enclosed in quotes.

Is it possible to run this as part of check-style.sh or something like it?

Also, there are services, like codacy that run things like this:
https://github.com/codacy/codacy-shellcheck
maybe we can just turn on codacy and we do not need to configure a lot of stuff?

Is it possible to run this as part of check-style.sh or something like it?

Yes. We can just install it like any other tool in the docker files. It looks like it's available for Debian-based distros, Fedora, OSX (via homebrew) and openSUSE and probably CentOS too. Then we can just add this to check-style.sh:
find . -type f -iname '*.sh' -exec shellcheck --exclude=SC1090 '{}' \;

SC1090 is an extraneous warning that complains about annotating lines that source scripts, so I just disable it.

I'm not sure if addressing the "SC2155: Declare and assign separately to avoid masking return values." warnings will be worth the annoyance of writing:
foo="$(mycmd)"
local foo

instead of
local foo="$(mycmd)"

I'm curious what others think.

As I said in #2475 it depends on whether or not we care about the return values. set -eu is being set at the top of the scripts, and according to SC2155's page set -e doesn't work properly unless you split the lines. If we decide in the lines I changed we don't care about the return values, we can either make it read-only (silences the warning) or exclude the warning.

What @remyabel said, this program exists successfully, and we probably wanted the error:
/bin/bash -c "f() { local foo=$(/bin/false); } ; set -e; f;"

Yep, I understand the concern about missing failed subcommands in command substitutions on the same line as a local or readonly. Here are some reasons still questioning the value of this check:

Usually when local and readonly (and export) are used, the stdout of the subcommand is what's important, not the return value. So typically, the string output of the variable will be subsequently checked in in the script. For example, local x=$(dirname ...); if [[ -d "$x" ]], or something. I think this is the typical use case.

Most of our uses of local should really be local -r, and those aren't flagged by shellcheck because they have to be on one line.

Overall, I don't think the value we'll get out of this particular check will be worth the hassle of us trying to remember when we need to split local/export/readonly into two lines. But this is just my opinion. I can see that there's already at least two votes in favor of this and only my one vote against it :-), so I'm happy to admit that I'm outvoted and enable this.
However, if we enable this, I think we should encourage our two-line initialization to be written with the local var declared first, then assigned to:
local foo
foo="$(mycmd)"

I think this looks less weird, and seems to make sense since foo never exists as a non-local variable.

But this is just my opinion. I can see that there's already at least two votes in favor of this and only my one vote against it :-)

FYI, I'm not voting either way. I agree with all your stated points and I'm happy to revise the PR with whatever the consensus is. Currently, most of the warnings emitted so far are in the tests for lines like this:
local token
token="$(./table_admin_snippets generate-consistency-token ${project_id} ${INSTANCE} ${TABLE} | awk '{print $5}')"

Unlike the examples run by run_example, the return value is not checked. run_example does explicitly check the return value. We just assume that these lines always succeed, but by coincidence if these lines fail, the subsequent examples will probably fail too. By splitting it into two lines, any failure will be caught by set -e. I think if we're going to change it, we should explicitly check the output like you suggested.

FTR: Enabling the SC2155 warning seems like the safer option. So I'm happy to move forward with enabling it and revisit that decision IFF it actually proves to be annoying.


Organizers

I added some modularity for the organizers #10.

Co-chairs can be added as additional json files in data/organizers/cochairs.
Members of the organizing committee can be added as additional json files in data/organizers/committee.

I started by adding the co-chairs and a few members #9. Please check and let me know if I got something wrong.
Note: I still have to fix the fluid behavior when minimizing the window (names move out of place a little).

Text is centered now and the sizes have been optimized for smaller screen sizes as well. I had to use a little bit more space, so there would be four people per row instead of five/six.


[MRG] Remove duplicate URL from BibTex reference

Removing the duplicate URL for the reference StenroosHauk2013 used in mne.simulation.metrics.peak_position_error.

style failing because of codespell, as noticed here #11248


Lucene string searches are case-sensitive on newer Elasticsearch

Describe the bug
When using lucene search parameter indexing, /Patient?name=kelly produces different results that /Patient?name=Kelly.
To Reproduce

Enable lucene indexing and lucene search parameter indexing, configured to use Elasticsearch 7.17 or newer.
Insert a Patient named Kelly Smith
Search for /Patient?name=kelly and /Patient?name=Kelly and compare results.

Expected behavior
These searches should return the same results
Environment (please complete the following information):

Hapi 6.0.0-SNAPSHOT
jpa-serverstarter built from the rel_6_0_0 branch
Elasticsearch 7.17

Additional context
The wildcard query is considered a term query, which means it isn't filtered by the analyzer.  Consider using a simple query instead.

We observed the issue with Elastic 7.17 but not sure when did the default behavior change (between 7.9 and 7.17). Here is a discussion related to the issue (not related to HAPI FHIR):
https://discuss.elastic.co/t/search-returning-no-results-after-upgrade-from-7-9-3-to-7-15-0/286739

Fixed in #3596.


Fix typos in README.md

Codecov Report

Merging #93 (e6fcf79) into main (e04492e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage   89.63%   89.63%
=======================================
  Files          74       74
  Lines        2412     2412
  Branches      305      305
=======================================
  Hits         2162     2162
  Misses        183      183
  Partials       67       67

:mega: Codecov can now indicate which changes are the most critical in Pull Requests.


IPv6 fragmentation: don't leak memory/packets

Besides comment, LGTM.

Frags is essentially a local in the caller that is never used again after the call to clean the packet cache. We could explicitly nil frags in the caller, but nil-ing elements of it strikes me as a bad idea.

Sounds reasonable, LGTM.

Merging as per jabber discussion.

Reatroactively LGTM :wink:


Inlining expected files to pass the 0-test, import feature and hk-maple

As per https://github.com/hakaru-dev/hakaru/pull/154
The issues with failing the 0-test were solved by inlining everything. Most of the tests I've written related to the exponential distribution had the same issues and I solved them same way.
Ideally, we would have used an import feature to call distributions directly from stdlib to write these test case files. I'd expect the exact same issues to arise in this case, making import useless for writing expected files. Isn't this inability to automatically in-line a problem then?
Not an issue for our project, but something I wanted to bring up in case it hasn't been considered.

Writing expected test files is inherently a manual thing. You're testing that Simplify does all sorts of operations correctly, including inlining.  So you need to write the expected 'by hand'.  You can, of course, use some machine assistance in deriving things.


⚠ Fortnite has degraded performance

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

HTTP code: 200
Response time: 1538 ms

Resolved: Fortnite performance has improved in 47f1b03.


[BUG] "request contains an invalid parameter value" error code: 2

When trying to play with my android app the video getting below error;
"request contains an invalid parameter value" error code: 2
It was working fine yesterday and I didn't change anything on code..

It was temporary thing I think, it works now, sorry for false alarm.

I am having the same issue & it is not resolving. What should I do?

@YashMakan  could you solve the problem? I am also facing the same problem. Please help
Thanks

This is usually a temporary issue and solved by itself in time.

My issue is I was using url as ID. make sure to do initialVideoId: YoutubePlayer.convertUrlToId(url)

@goatandsheep @sarbagyastha when I'm using the youtube shorts video URL in initialVideoId: YoutubePlayer.convertUrlToId(url) this section then I'm getting the  error code: 2

Check url protocol. Instead of http change to https


Browsersync ignores host config, starts on localhost

Not a major issue, just something that I noticed. It appears that when I start up webpack, browsersync ignores the host setting in the BrowserSyncPlugin and instead opens a new tab in my internet browser at: localhost:4200 (note it doesn't appear to ignore the port).
sample config:
new BrowserSyncPlugin({
  host: 'local.example.com',
  port: 4200,
  proxy: 'http://local.example.com:3000/'
})

Hey!
Hm, let me check this out.

@Va1 Thank you so much for looking into this, if you need any other details as well I'd be happy to help.

@mealeyst
Sorry for the delay, having too much stuff happening. However, I did look into issue and here's what I found:

yes, it does open localhost with the config you provided
no, it does not ignore host option, it just uses it for the external url. I guess, this is the proper behavior, as browser-sync server is being hosted on your localhost anyways, and can have aliases (I might be wrong about this, did not find anything related in browser-sync docs)
there is a way to do what you want. you should specify your desired host and it will be used as external url host, then you should add an option property (docs), and set it to external, and it will open your host in the browser

What I put in config:
var BrowserSyncPlugin = require('browser-sync-webpack-plugin');

module.exports = {
    entry: './src/entry.js',
    output: {
        path: './public',
        filename: 'bundle.js'
    },
    plugins: [
        new BrowserSyncPlugin({
            host: 'abrahadabra.foobar.com',
            port: 3030,
            server: { baseDir: ['public'] },
            open: 'external'
        })
    ]
};

What I see in console:
[BS] Access URLs:
 -----------------------------------------------
       Local: http://localhost:3030
    External: http://abrahadabra.foobar.com:3030
 -----------------------------------------------
          UI: http://localhost:3001
 UI External: http://abrahadabra.foobar.com:3001
 -----------------------------------------------
[BS] Serving files from: public

What I see in browser:
http://abrahadabra.foobar.com:3030/

I assume, the issue is closed.


Update the supported annotations in Chaise per the revised guidelines in ERMrest docs

This primarily refers to the chaise/search page.

We need to get to this one.
See ermrest doc:
https://github.com/informatics-isi-edu/ermrest/blob/master/user-doc/annotation.md
Having these lined up with the new annotations is important to our active use cases that now have to set the old annotations and the news ones so that different pages in chaise will display consistently.

@hongsudt this should be prioritized

We plan to deprecated this app with recordset app. So I am putting this in the wishlist and close the issue fo rnow.

We should discuss branding.  Are we actually deprecating the name Chase in favor of the other names?
Carl

Dr. Carl Kesselman
Dean’s Professor, Epstein Department of Industrial and Systems Engineering
Fellow, Information Sciences Institute
Viterbi School of Engineering
Professor, Preventive Medicine
Keck School of Medicine
University of Southern California
4676 Admiralty Way, Suite 1001, Marina del Rey, CA  90292-6695
Phone:  +1<PHONE_NUMBER>
Email:  carl<EMAIL_ADDRESS>Web: http://www.isi.edu/~carl
On May 9, 2016, at 10:15 AM, Hongsuda <notifications<EMAIL_ADDRESS>wrote:
We plan to deprecated this app with recordset app. So I am putting this in the wishlist and close the issue fo rnow.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/129#issuecomment-217927933

On 5/9/16, 10:20 AM, "Carl Kesselman" <notifications<EMAIL_ADDRESS>wrote:
We should discuss branding. Are we actually deprecating the name Chase in favor of the other names?
Chaise should still refer to the overall suite of UI components. Something like “search” is just one of its component.

That is what I was thinking.
Carl

Dr. Carl Kesselman
Dean’s Professor, Epstein Department of Industrial and Systems Engineering
Fellow, Information Sciences Institute
Viterbi School of Engineering
Professor, Preventive Medicine
Keck School of Medicine
University of Southern California
4676 Admiralty Way, Suite 1001, Marina del Rey, CA  90292-6695
Phone:  +1<PHONE_NUMBER>
Email:  carl<EMAIL_ADDRESS>Web: http://www.isi.edu/~carl
On May 9, 2016, at 2:09 PM, robes <notifications<EMAIL_ADDRESS>wrote:
On 5/9/16, 10:20 AM, "Carl Kesselman" <notifications@github.commailto:notifications<EMAIL_ADDRESS>wrote:
We should discuss branding. Are we actually deprecating the name Chase in favor of the other names?
Chaise should still refer to the overall suite of UI components. Something like “search” is just one of its component.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/129#issuecomment-217990724


Open Editor refactors

This PR is part of the work for https://github.com/microsoft/vscode/issues/100281
The main work of this PR includes:

Renaming IEditorInputFactory -> IEditorInputSerializer as it doesn't actually create an editor input at all
Move the override logic into the editor service and away from the editorGroupView. This involved removing the onEditorWillOpen event as it wasn't really necessary. An improvement here might be to have the overrides return editor inputs to prevent circular openEditor calling
Create an onWillMoveEditor event so things like notebooks can properly handle moving between groups

@bpasero This is ready for review again. The one issue @rebornix and I ran into is that on editor startup / restore there is no way for something to know about all the groups that exist on startup. I changed the editor part restore to fire the onAddGroup event for all the restored groups so any subscribers would be aware of them but I want to get your input as this causes active editor tests to fail so I'm not sure if they should be updated or what the best solution is.

Thanks for the review. The 💄 looks good too, sorry about forgetting to rename the areas around IEditorInputSerializer. I talked to Kai a bit and he said we should probably hold off on merging this until next iteration just due to how little testing time we would have with these changes. This should give us time to come up with a good solution for your issue that also unblocks notebooks. I don't want to merge this yet as notebooks not knowing about all groups causes the re-rendering issue we were trying to avoid with onWillMoveEditor.
Here you can see that notebooks binds event listeners to all groups, but due to not knowing about groups on startup / restore reloading the window is enough to cause all existing listeners to be lost and not rebound.
https://github.com/microsoft/vscode/blob/a3d388ed8169edb1f3de9b5ec3b15819020f8d1c/src/vs/workbench/contrib/notebook/browser/notebookEditorServiceImpl.ts#L40-L64

@lramos15 I don't really understand why notebooks cannot do this:
editorGroupService.whenRestored.then(() => editorGroupService.groups.forEach(onNewGroup));

There should always be a way to track editor groups, in the end that is what EditorsObserver does, which is a core thing crucial for many features we built on top:
https://github.com/bpasero/vscode/blob/763e089ae54efdc3e6382699e7391c6df8b6f2be/src/vs/workbench/browser/parts/editor/editorsObserver.ts#L67-L73

@bpasero I have fixed the tests and adjusted the notebook's way of listening for groups to the way you suggested and that seems to work.
I noticed you renamed the notebook and custom editor input factory files to input serializer files. I'm not sure what we could call those as they have both an IEditorInputSerializer and a ICustomEditorInputFactory

@lramos15 very cool! yeah feel free to revert my rename, I didn't see they include the actual custom factories too 👍


KOGITO-7589 & KOGITO-7707: Product name changes and sanity check fixes

JIRA:
https://issues.redhat.com/browse/KOGITO-7589
https://issues.redhat.com/browse/KOGITO-7707

Description: Product name changes and sanity check fixes

Please make sure that your PR meets the following requirements:

[x] You have read the contributions doc
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] The nav.adoc file has a link to this guide in the proper category
[ ] The index.adoc file has a card to this guide in the proper category, with a meaningful description

@hmanwani-rh, great work! Now we need to come clean with these terms:

workflow application
workflow project
Serverless Workflow *
Kogito *
OpenShift Serverless Logic *
CNCF Serverless Workflow specification

For "[Kogito] Serverless Workflow", I understand the name of the project/product these guides are about. "Kogito" is the upstream name of the implementation, so we can keep using it when referring to the engine or any libraries. "OpenShift Serverless Logic" fits perfectly for the project/product naming IMO.
That being said, I think we need a few tweaks in the guides. wdyt?
Feel free to take this conversation offline and/or include more people.

@ricardozanini Thanks for reviewing the changes and sharing your suggestions. I've created two new attributes as follows:
#in Downstream product_name: OpenShift Serverless Logic
product_name: Kogito
#in Downstream context: OpenShift Serverless Logic
context: Serverless Workflow

and made the changes in the guides accordingly. Please take a look one more time and let me know what you think.


Compatability issue with System Customizer Module

Foundry - v11.315
D&D5e - 3.1.2
AS - 1.0
System Customizer - 2.0.7
Modules - Only modules enabled are AS and System Customizer
Steps to recreate the issue:

Activate both modules
Modify Settings for System Customizer

Create new actor, option to fill in ability scores is missing:

Unfortunately that is a premium module (System Customiser) so I can't install it to have a look.
If you open the browser inspector you can screenshot any errors in the console. Might be a simple fix. Don't know.
Also try enabling all the rolling options and see if you get different behaviour.

Presents the same, and cannot make any selections in the dropdown.

I noticed these:

Also get this:

Which browser?

Edge

Check the Network tab of the inspector for any 404 errors.
Also try browse to https://foundryvtt.3dmentia.com/modules/foundryvtt-actor-studio/dist/ManualEntry-Cencm6oc.js (replace the domain with your domain).

Try it without the premium module, that way we can at least rule that in or out.

Yeah when System Customizer is disabled it works fine.

If I do:
http://localhost:30000/modules/foundryvtt-actor-studio/dist/ManualEntry-Cencm6oc.js
It works okay

Very strange. I don't know what System Customiser does but from the error message you showed it looks like it's preventing the required Actor Studio .js files from being imported. I'm not even sure how it's able to do that.

I'll check with Ripper

I've pinged him too, with a link to this ticket.

@ChobitsCrazy any news on this?

Not yet, Ripper has pushed out updates and the latest is on v12 however I cannot move over to v12 yet due to other modules lagging behind. Once I'm able to move over to v12 I'll be able to update and make sure this is still an issue and then report it to Ripper.

I can confirm the same error when adding this to my DnD 5e variant "Lord of the Rings" from Free League. There is a community plugin that implements the major rule changes (but no backgrounds, classes etc.) - https://github.com/ZWinther/lotr5e-module
If I deactivate it, Actor Studio works like a charm. Not sure if that is helpful to trace down the issue.

Fixed in https://github.com/geoidesic/foundryvtt-actor-studio/releases/tag/1.3.3


Added support for configuration file

(looks like I can't reopen the old PR after rebasing... oops. good to know for future cleanliness)
import.js

added support for retrieving "config.txt" files
appended configuration to "importFromFilePath" output
separated importConfigFromFilePath from importFromFilePath

preprocesser.js

added config preprocessor
-- has default config
-- import rest from file, fills empty fields with default options
-- added null checking, and error handling

unit tests:

various states of completeness and emptiness

bump package version number

Added unit tests, doubled checked for blank files and missing files, added warnings

I have since overhauled the config system in a different branch (one that is properly rebased as well). As a result, this PR should be closed and I will be making a new one from that branch.


Add support for multiple systems

Thanks for this flake, it's really helped me out.
This PR adds support for linux-aarch64, darwin-x86_64, and darwin-aarch64.
It also adds go-turbo to the installation, since it's needed by 1.7.0 to do the things the new Rust CLI isn't able to do yet. I ran into this running a turbo prune command.

Awesome! Thanks a lot for your PR @joedevivo. Now I can use this on my Macbook as well :)


Document sudo/su interaction

Order in which they are called is super important to the result when using both. Add documentation on this.

Not entirely sure how the documentation would look like, but don't forget doas if it's relevant!


Image size rules--investigate for HackAThon

Do we want to restrict image sizes and if so, what is the size limit? Andrew to investigate with Doug and let us know of any restrictions so researchers can prep for HackAThon.

Note: Image max size was set to 10 MB for the Hackathon.

Image size limit on dev is currently set to 15MB.
Should I set to 10MB?

15 is good
Get Outlook for Androidhttps://aka.ms/ghei36

From: NoisyFlowers @.>
Sent: Friday, July 21, 2023 12:50:06 PM
To: paleobot/pbot-dev @.>
Cc: Zaffos, Andrew - (azaffos) @.>; Assign @.>
Subject: [EXT]Re: [paleobot/pbot-dev] Image size rules--investigate for HackAThon (Issue #110)
External Email
Image size limit on dev is currently set to 15MB.
Should I set to 10MB?
—
Reply to this email directly, view it on GitHubhttps://github.com/paleobot/pbot-dev/issues/110#issuecomment-1646170518, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPQSQ22DTSSC2R2BGAUOSLXRLMO5ANCNFSM6AAAAAAZYTIEZI.
You are receiving this because you were assigned.Message ID: @.***>


Example of working launch.json?

Could you give an example of how to add it to launch.json?
I tried this:
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Run File",
            "program" : "${config:debug-current.file}"
        }
    ]

but it just complains about attribute program not being absolute. I tried passing it in the args too, but didn't work either.
Thanks.

Hi @thunderkid, sorry I just realised this was posted. I've updated the README with an example.
Basically, ${config:debug-current.file} will be replaced with the filename of the currently focused file when executing the command Debug Current File.
Note the filename doesn't exclude the path or extension - this was specific for my use case.
If you just need the full file name, you can use ${file} and you don't need to use this extension.


Moving the cursor down when writing text in demo-github.io

Hi. First of all, I want to say thank you for the wonderful package.
In general, there is a problem that when I write some text in https://yikoyu .github.io/vuetify-pro-tiptap / ,
then in the process of writing , the cursor throws down

I would like you to comment on this behavior

When I change the value to 20, the cursor does not drift, but long press continuous input will be a bit laggy, I will try some other methods.
https://github.com/yikoyu/vuetify-pro-tiptap/blob/4c898095d7b8350fd96eb0306779cd173d21217e/src/constants/define.ts#L3

:tada: This issue has been resolved in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hub sync isn't very effective when squashing and merging commits

I want to use hub sync to update local branches but more importantly delete branches that have been merged already via the Github UI. The problem is, when running hub sync I get many warnings like the following:
warning: 'sean/branch_name' was deleted on origin, but appears not merged into master.
I'm assuming this is because the PR opened for this branch was merged using the "Squash and Merge" option so the SHA no longer matches. Is there a way to force hub sync to still delete branches in this case?

Sorry, hub sync still doesn't recognize squash-merged branches! I'm not sure what would be the best way to support this, since it's not trivial to detect just by looking at git objects.
If anyone has any ideas, I'm all ears.

Is there a command I can run to get rid of that issue?

I copied a complicated git alias from somewhere that helps clean up squashed branches.  It may or may not work for your use case:
[alias]
  cleanup = "!git remote prune origin && git checkout -q master && git for-each-ref refs/heads/ '--format=%(refname:short)' | while read branch; do mergeBase=$(git merge-base master $branch) && [[ $(git cherry master $(git commit-tree $(git rev-parse $branch^{tree}) -p $mergeBase -m _)) == '-'* ]] && git branch -D $branch; done"

In my case, I run hub sync followed by git cleanup.
I am not familiar at all with hub's code, but perhaps this logic of looping over refs and comparing merges could be integrated into the sync command?


Form buttons disappeared in CloudInteligence->Reports->Schedule form

closing because this issue is already exist here: #4386


add the opposite blockstate + add documentation and/or example

Hey!
Just saw your mod on Modrinth. This is very close to what I was looking for a few months back. I am dissapointed, that vanilla features no snow layer on top blockstate, which I needed it to add some snowy leave textures. As I understand it right now, your mod does add the opposite and gives snow access to a blockstate of leaves below. Is there a way you could integrate the opposing blockstate as well?
Also, this would still be very useful for making the snow wave in the shader I am using, but the issue is, that I have no clue how to implement it properly and would love to see an example and/or a documentation of a kind. I tried using Bliss shaders, because you called it compatible, but I had no luck with it.

Hi!
I can try to add snow_on_top blockstate to leaves after I finish adding the config and carpet support.
Also small clarification, the blockstate added to snow, vines and carpets is called is_on_leaves as in is it based no leaves, for snow and carpet it in fact does mean is snow below, but for vines it means if it is growing from leaves.
I've added documentation to the README, you can check it out, if you have any questions or suggestion on how can I improve it, feel free to tell me :)
As for Bliss, the support was officially added, but the Bliss version with the support did not have any public releases yet, there were also some conflicts with internal Bliss branches...
The only Bliss version you can download with the support in it is, official main branch and my fork of the shader.
To add the support for any other Bliss version, you need to copy the block.properties file from the supported version to the unsupported one.
I hope this answers all your questions, feel free to ask if you have more

I guess you want to do something like that: https://www.reddit.com/r/Minecraft/comments/yj4juk/snowy_bushy_leaves/
I wounder though how was this done before

Done, I've added snow_on_top blockstate to leaves.
Currently only to the GitHub version, but I will release a version on Modrinth soon

You want is_ice_on_top too?

New version released on Modrinth.
I will close this issue, but feel free to reopen it or open new one if you want.
Also if you're resourcepack with Boe's Earth support is/will be available on Modrinth, I can link it in the Boe's Earth if you would like to, as an example working resourcepack similar to how Bliss is linked


Check if it works on iOS devices

@jvandemo told us it didn't work for his iPhone. We should check this.

Here is what happens on my iPhone 6:

I tap "Login" and "Twitter" and it just returns to the same page.

Cleared the Safari cache and then it was okay! 👍


Question/feature Carla 0.9.X (5) building .pyd for python 2.7 on Windows

VERSION : Carla 0.9.5 , Windows experimental version
My issue is related to the fact that I would like to use IronPython in C# application to control Carla Client Python Api.
To do this I need to build .pyd library to be able to run Client with python 2.7  ( IronPython works only with 2.7 python version)
I have found in your BuildPythonApi.bat comment:
"rem We don't provide support for py2 right now"
Question:
I hope it mean that it is possible to build carlib .pyd file with python 2.7 on Windows??
Do you have any instruction or tips for me what should I do to properly build .pyd file?
( build boost python for 2.7 ?? Something else? :} )
I know that there are already build version for Linux ( python 2.7) but haven't seen any for windows.
Thank you for help !

Hey Jabkowsky, did you get your Windows Carla Client working on Python 2.7? I need to do the same thing here because I am running ROS for Windows and it only runs on Python 2.7. My Carla does not have an egg file for it. Not sure how to generate one.

No i did not managed to do this,
Basically issue I found is that there is no c++14 compiler to build correct .pyd file from source code ( python 2.7)
https://wiki.python.org/moin/WindowsCompilers

Visual C++
CPython

14.X
3.5, 3.6, 3.7, 3.8

10.0
3.3, 3.4

9.0
2.6, 2.7, 3.0, 3.1, 3.2

If you want to created .egg file you need to compile source c++ library with Visual studio compiler. ( on windows of course )

Probably that is why Carla Developers are giving for windows version only .egg file for py36,

i did manage only to build for 3.7 python version.


Modules should be properly destructed on reload

...so when a module spawns a thread, it doesn't spawn more and more and more on reload.

Fixed by 75400f8a , added deconstructors to the module API.


Upgrade RabbitMQ

On EL8 distributions we use the latest RabbitMQ and Erlang from the rabbitMQ repos, but for all other distributions we use what is bundled with the O/S. Update all installations to use latest RabbitMQ.
Changes required for 3.6 release:

[x] st2-packages - bash installer
[x] st2docs

[x] installation and upgrade changes

[x] st2ci/cd - don't think necessary as in docs said was optional

Changes that can be done post 3.6 release:

[x] ansible installer - in progress @amanda11
[x] puppet installer https://github.com/StackStorm/puppet-st2/

@rush-skills Just created an issue for puppet-st2, https://github.com/StackStorm/puppet-st2/issues/340 if you'd like to take a look at updating RabbitMQ for https://github.com/StackStorm/puppet-st2/.

Thanks everyone :+1:
The inconsistent RabbitMQ version shipped by default with the various distros was a bit of a security issue reported before by our users and so this definitely makes the project more secure.


Convenience methods for getting data as numpy arrays.

Partially addressing #36 (no methods to store image arrays yet).

Adds methods to get data directly in numpy arrays for tomograms, features, segmentations and picks

tomogram.numpy(
        zarr_group: str = "0",
        x: slice = slice(None, None),
        y: slice = slice(None, None),
        z: slice = slice(None, None),
    ) -> np.ndarray:

`segmentation.numpy(
        zarr_group: str = "0",
        x: slice = slice(None, None),
        y: slice = slice(None, None),
        z: slice = slice(None, None),
    ) -> np.ndarray:

features.numpy(zarr_group: str = "0", slices: Tuple[slice, ...] = None,) -> np.ndarray

picks.numpy() -> Tuple[np.ndarray, np.ndarray] #[N, 3] positions and [N, 4, 4] transforms

These apply slices to the underlying Zarr to avoid reading the whole array when trying to obtain subregions. No shape is prescribed for features.

Adds method for storing picks from a numpy array

picks.from_numpy(positions: np.ndarray, transforms: Optional[np.ndarray] = None) -> None

@kephale Curious to hear what your opinion on methods for storing images would be? This would require additional dependency on scikit-image for the rescaling functions.

Will tomograms always be small enough that a numpy array is sufficient?