OPNsense 23.7 randomly hangs up with out of SWAP

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ X ] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[ X ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

We have installed OPNsense 23.7 to an Sophos SG 125 Hardware Appliance. After random time a process is spawned x times
and let run the OPNsense in out of SWAP. So the appliance is chrashing.

Software version used and hardware type if relevant, e.g.:
OPNsense 23.7 (amd64, OpenSSL).
Intel® Atom 1.7 GHz Dual Core
12GB RAM

I think it's related: https://forum.opnsense.org/index.php?topic=35364.15
Same here we have tested the config ago in a VM without any problems.
I have removed Zenarmor and I will take a look again.

Problem is back, seams not related :(

We haved moved back to a VM, but the problem is always there.

I find out that are thousands of following processes:
86048  -  R        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86099  -  DE       0:00.29 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86121  -  D        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86164  -  R        0:00.12 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86204  -  D        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86224  -  D        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86274  -  RE       0:00.21 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86380  -  DE       0:00.20 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86475  -  D        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86578  -  RE       0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86579  -  R        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86626  -  D        0:00.15 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86636  -  D        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86678  -  R        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86718  -  D        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86746  -  D        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
86925  -  R        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87042  -  RE       0:00.24 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87056  -  R        0:00.30 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87102  -  DE       0:00.25 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87118  -  D        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87138  -  D        0:00.11 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87202  -  RE       0:00.20 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87219  -  R        0:00.10 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87264  -  D        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87331  -  R        0:00.20 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87386  -  D        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87440  -  RE       0:00.21 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87502  -  DE       0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87638  -  D        0:00.13 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87688  -  R        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87771  -  D        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87813  -  RE       0:00.25 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
87884  -  D        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88134  -  D        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88175  -  D        0:00.22 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88198  -  R        0:00.21 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88236  -  R        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88278  -  D        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88284  -  D        0:00.22 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88422  -  D        0:00.14 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88479  -  R        0:00.21 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88642  -  D        0:00.28 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88700  -  D        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88714  -  R        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88721  -  R        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88730  -  RE       0:00.22 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88747  -  R        0:00.25 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88751  -  R        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88793  -  D        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88919  -  D        0:00.23 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
88982  -  R        0:00.12 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89133  -  RE       0:00.21 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89170  -  D        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89225  -  R        0:00.27 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89277  -  D        0:00.15 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89428  -  D        0:00.19 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89517  -  R        0:00.15 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89611  -  RE       0:00.24 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89622  -  R        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89667  -  D        0:00.11 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89738  -  R        0:00.20 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89855  -  R        0:00.18 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89870  -  R        0:00.17 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
89899  -  R        0:00.12 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
90079  -  D        0:00.15 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
90181  -  DE       0:00.25 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
90252  -  RE       0:00.15 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
90372  -  R        0:00.22 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force
90419  -  R        0:00.16 /usr/local/bin/php /usr/local/etc/rc.newwanipv6 pppoe1 force

Did you update to 23.7.5? If not turn off IPv6 on your WAN. Your hardware could be too slow.

@fichtner We have replaced the hardware because we also think that it could be too slow.
But same problem comes back also on OpnSense Business.
We need IPv6, we can't disable it.
Actual hardware and versions:
CPU type | AMD Ryzen 3 PRO 4350G with Radeon Graphics (4 cores, 8 threads)
32GB DDR4 ECC RAM

OPNsense 23.4.2_1-amd64
FreeBSD 13.1-RELEASE-p8
OpenSSL 1.1.1v 1 Aug 2023
Licensed until 2026-09-09

23.4.x may have the same defect, that’s why I asked for 23.7.5 specifically.

23.10 business comes out on the 17th this month and is on par with 23.7.5 as far as rc.newwanipv6 script is concerned.

Hello everyone, the issue is back on OPNsense 24.4.1-amd64 any newes?


invalidcastexception initializing intput system

Does this affect the legacy HoloToolkit (master) or the Mixed Reality Toolkit (mrtk_release)?
Mixed Reality Toolkit
Describe the bug
Exception thrown: 'System.InvalidCastException' in Microsoft.MixedReality.Toolkit.dll
'MixedRealityToolkit.exe' (CoreCLR: CoreCLR_UWP_Domain): Loaded 'C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\Microsoft.MixedReality.ToolkitVS.Release_x86.davidkl\System.Diagnostics.StackTrace.dll'. Cannot find or open the PDB file.
InvalidCastException: Unable to cast object of type 'Microsoft.MixedReality.Toolkit.SDK.Input.MixedRealityInputManager' to type 'Microsoft.MixedReality.Toolkit.Core.Interfaces.IMixedRealityExtensionService'.
   at Microsoft.MixedReality.Toolkit.Core.Services.MixedRealityToolkit.RegisterService(Type type, IMixedRealityService service)
   at Microsoft.MixedReality.Toolkit.Core.Services.MixedRealityToolkit.Initialize()
   at Microsoft.MixedReality.Toolkit.Core.Services.MixedRealityToolkit.InitializeInternal()
   at Microsoft.MixedReality.Toolkit.Core.Services.MixedRealityToolkit.Awake()
   at Microsoft.MixedReality.Toolkit.Core.Services.MixedRealityToolkit.$Invoke2(Int64 instance, Int64* args)
   at UnityEngine.Internal.$MethodUtility.InvokeMethod(Int64 instance, Int64* args, IntPtr method)
(Filename: <Unknown> Line: 0)

To Reproduce
Steps to reproduce the behavior:

Checkout mrtk_development branch
Load one of the demo scenes (I used the standard materials scene)
Build and run (I deployed to a HoloLens using the .net backend)

Expected behavior
The system to be correctly initialized
Actual behavior
The above exception
Unity Editor Version
2018.2.13f1
Mixed Reality Toolkit Release Version
mrtk _development branch as of 10/25/2018 11am

It appears that we are landing in the else case of IsCoreSystem and attempting to cast to an IMixedRealityExtensionService on line 533
            MixedRealityComponents.Add(new Tuple<Type, IMixedRealityExtensionService>(type, (IMixedRealityExtensionService)service));

What about il2cpp builds?
.NET isn't officially supported.

I'm concerned by this line
Unable to cast object of type 'Microsoft.MixedReality.Toolkit.SDK.Input.MixedRealityInputManager' to type 'Microsoft.MixedReality.Toolkit.Core.Interfaces.IMixedRealityExtensionService'

Even more concerned as the same error isn't showing up in the Editor

Yeah I'm not sure how IsCoreSystem could be failing. Strange.

What about il2cpp builds?

Same behavior, system loading is getting aborted, HoloLens and UWP immersive,

.NET isn't officially supported.

It is supported as long as Unity supports it (2 years of 2018 LTS)

Can you also replicate this on Windows 10 .NET or IL2CCP builds @davidkline-ms ?

Yes, I can repro it on Windows 10 UWP (IL2CPP)

Does it break for PC OpenVR builds as well?

Does it break for PC OpenVR builds as well?

yes

I wasn't able to reproduce with the steps provided. Is there anything else we might be missing to reproduce this?

Those are the steps that repro'd for me. I have tried multiple (5+) clones and have hit this in each one. If I roll back prior to the rename, the errors do not occur. I am using the same version of Visual Studio and Unity. The only difference is whether or not I have the change.
Tested:

IL2CPP: HoloLens, WMR Immersive, OpenVR
.net: HoloLens, WMR Immersive, OpenVR,

I am going to continue investigating.
This must be fully understood before beta is declared.


Early Stopping in Prompt Tuning

Background
Currently, we have no early stopping added to the prompt tuning module, but we should! This issue covers adding it.
Acceptance Criteria

[ ] Prompt tuning can be run with early stopping
[ ] Tests added on tiny models validating early stopping via stubbed behaviors or with (fast) deterministic examples

This is related to https://github.ibm.com/ai-foundation/watson-fm-stack-tracker/issues/302

WCA for Red Hat Ansible Lightspeed has a need for this feature, with the clarification that the tests are performed on a validation test set that is distinct from the training data.


Faster Whisper sometimes stops running suddenly

So I have large quantity of short 10-60 seconds audio files. I try to transcribe them with faster whisper in a loop. But sometimes whisper just stops/freezes all of a sudden. I use debug mode but there is no error message, just the last info message that it started processing the file. If I repeat the run it sometimes fails on the same file, sometimes it goes a bit further and fails at another file. I looked into the audio files and they seem to work just fine in any media player. I call faster whisper (large-v1) like this:
res = []
        for p in audiopath:  # filepaths
            segments, info = model.transcribe(p,
                                           beam_size=5
                                           task="transcribe",
                                           without_timestamps=True,
                                           temperature=[0], # temp 0 to make benchmark fair
                                           language=lang
                                           )
            logging.debug("Detected language '%s' with probability %f" % (info.language, info.language_probability))
            segments = list(segments)
            res.append("".join([i[4] for i in segments]))  #only append text to the result list

Sometimes it stops without error when it's actually "out of memory".
How much VRAM there is in your GPU?

I am experiencing the same problem. If you are using Windows, it may be related to this issue.
https://github.com/SYSTRAN/faster-whisper/issues/620
This issue does not provide a solution, but it does provide some workarounds.

Not really, I use Ubuntu with an A100 and 80GB of RAM

I experience the same issue with a T4 and 16GB of Memory. Suddenly stops and says start processing but them hangs.
It does not matter which files I use (have videos with different lengths) multiple container running faster whisper stop randomly.

me too facing the same problem

Has anyone encountered this issue and fixed it?

Yes I have fixed it by checking every video via ffprobe and check if I get a duration. Basically we ignore all videos which would produce an error in ffmpeg and since then our service is super stable.

I found the simplest way to fix this issue is to clear the CMOS or reset the BIOS. I'm not entirely sure why this works, but recently I messed with the BIOS settings and my PC couldn't boot. After resetting the CMOS, the faster whisper error got fixed too.


Validator missing CI

The validator package at opentargets/validator should be updated with a CI testing configuration, and appropriate branch protection enabled.
This is also related to opentargets/platform#144 to Dockerize the validator as the Dockerized version should be tested as well as the python package version

Done as part of opentargets/validator#5


[Question] What is the proper way to make sure the editor canvas will translate on all directions with no limit?

I have everything working except the case when i want to drag the editor in unused zone, it translate to a certain distance then it stop, i feel like there is a maximum width while i did not set one....
https://github.com/jerosoler/Drawflow/assets/35831811/2f3cc08f-3db8-42e9-b41e-7f8c7bf17a90

That shouldn't be like that.
Look at the demo. This does not happen.
Make sure the drawflow container does not have any CSS classes.
It could be because of that:

https://github.com/jerosoler/Drawflow/issues/469

Nice, it worked when i set the first class to be parent-drawflow


Browser compatibility - MSIE versions

http://adripofjavascript.com/blog/drips/creating-unwritable-properties-with-object-defineproperty.html
the defineProperty was first implemented by IE9. IE8 supports it only by DOM object and there is no shim, so we can say that the lib supports IE from version 9. ofc I am not certain about this, since other ES5 related things can fail and the stack string can be different in older IE, so it is not necessary parsable with the current half implemented parsers #17

I am not sure whether IE9 is supported, since there are many ES5 features which are probably not supported without a shim. I should test this on the real browser, but without Saucelabs it does not seem to be possible. Probably if I manage to get XP from somebody.

Removing this from the milestone, it is not priority, so we can do it later after 1.0.

If it does not work because of ES5 features are missing, I could probably require a shim.


Does not lint deeply nested template paths

cfn-lint version: 0.9.2
Using ** path globs does not behave as expected. Assume the following directory structure
project:
  templates:
    - a:
      - b:
        - c:
          - foo.yaml
          - bar.yaml
        - d:
          - baz.yaml
          - quux.yaml
      - e:
        - ipsum.yaml
        - lorem.yaml
    - f:
      - zyx.yaml
      - quuz.yaml
    - main.yaml

If I use the glob format in .cfnlintrc:
templates:
- project/templates/**/*.yaml

The only files that are checked are project/templates/f/zyx.yaml and project/templates/f/quux.yaml. All others are ignored. I would expect project/templates/**/*yaml to match all deeply nested templates as well as project/templates/main.yaml.

The easy fix for Python 3.5 or higher is to add , recursive=True to https://github.com/awslabs/cfn-python-lint/blob/master/src/cfnlint/config.py#L439
I'm debating punting on the backwards compatibility of this and just saying we support what glob can do based on the version of Python available.

@phene What OS and what Python version are you running?

I like @kddejong's solution.  Based on my research, getting recursive globbing working on 3.4 would require moving to something like pathlib.  Adding recursive=True gets us compatibility back to 3.5 (which is pretty good) without the need for any significant code changes. I'm going to go ahead and approve it.

@phene could you try shopt -s globstar beforehand if using bash? Solved a similar issue

This shouldn't require bash to function. It should just work on systems that just have /bin/sh or use zsh.


Create bug_report_template.md (Issue #30)

Create Bug Report Template: PR to the Issue #30

@SvA1 I'm closing this for now. If you're able to sign of your DCO we can reopen and merge.


Status response: 403 Forbidden (SKILL_DISABLED_EXCEPTION)

Hi ,
I have successfully set up the skill and connected it to Alexa. I can add buttons that are also successfully dicovered by Alexa. Even if I change the state of a button, this is displayed correctly in the alexa app.
However, when I change the status, my routine for the sensor is not triggered. Instead, I see an error 403 (SKILL_DISABLED_EXCEPTION) in the log after "Pushing a notification to Alexa".
I have also already tried to disconnect and reconnect the skill, but there are no errors.
Does anyone have any idea what is wrong?
Here is the complete log for the state change:

START RequestId: 189c76d4-9038-4137-aded-5ca8a75904a9 Version: $LATEST
2023/11/11 14:38:17 Handler started
2023/11/11 14:38:17 Incoming data:  {     "version": "2.0",     "routeKey": "$default",     "rawPath": "/",     "rawQueryString": "",     "headers": {         "authorization": "zJ9z8us",         "content-length": "50",         "x-amzn-tls-cipher-suite": "ECDHE-RSA-AES128-GCM-SHA256",         "x-amzn-tls-version": "TLSv1.2",         "x-amzn-trace-id": "Root=1-654f91d9-1403f67622748cb23b2c13e0",         "x-forwarded-proto": "https",         "host": "7bdzfnjyeyyzwh6kjnefvz3kqy0leked.lambda-url.eu-west-1.on.aws",         "x-forwarded-port": "443",         "content-type": "application/json; charset=utf-8",         "x-forwarded-for": "<IP_ADDRESS>",         "accept": "application/json"     },     "requestContext": {         "accountId": "anonymous",         "apiId": "7bdzfnjyeyyzwh6kjnefvz3kqy0leked",         "domainName": "7bdzfnjyeyyzwh6kjnefvz3kqy0leked.lambda-url.eu-west-1.on.aws",         "domainPrefix": "7bdzfnjyeyyzwh6kjnefvz3kqy0leked",         "http": {             "method": "POST",             "path": "/",             "protocol": "HTTP/1.1",             "sourceIp": "<IP_ADDRESS>",             "userAgent": null         },         "requestId": "189c76d4-9038-4137-aded-5ca8a75904a9",         "routeKey": "$default",         "stage": "$default",         "time": "11/Nov/2023:14:38:17 +0000",         "timeEpoch":<PHONE_NUMBER>507     },     "body": "{"command":"setstate", "param1":"1", "param2":"0"}",     "isBase64Encoded": false }
2023/11/11 14:38:17 API call
2023/11/11 14:38:17 Body is: {     "command": "setstate",     "param1": "1",     "param2": "0" }
2023/11/11 14:38:17 Pushing a notification to Alexa
2023/11/11 14:38:17 No refresh needed
2023/11/11 14:38:17 {     "event": {         "header": {             "namespace": "Alexa",             "name": "ChangeReport",             "messageId": "89dbd8b1-d775-4577-8540-2f0993e33837",             "payloadVersion": "3"         },         "endpoint": {             "scope": {                 "type": "BearerToken",                 "token": "Atza|IwEBIBCzjAbEfMPNvkI728rhuFtgPtb6keOAMWwsgBRlupXLNJ4mL_Fk0-YIT_yfIoPvlUXLWRZLoqcg7KLBrQpwvMKi63RjlqEP5_ghY4nJPoWSkMmFzwM98Mx1iIC6BfNWHjLtaafwmBpRKNLAL-sa_Yr5isbVtwuOFq8J_m3OCRaSPdSVTeTbDCqleZMuH_MqI0mRuS1N8zL3u-V34aAA2TVD7ZOTxJpt4-L9Oz9SFq_UZJpGEF5DlB9_hm0IGKOzEoiQ2FVjRLxv80HvHI-oNEAj2jn260BcuVz3lp2WOJOXmA"             },             "endpointId": "switch-000001"         },         "payload": {             "change": {                 "cause": {                     "type": "PHYSICAL_INTERACTION"                 },                 "properties": [                     {                         "namespace": "Alexa.ContactSensor",                         "name": "detectionState",                         "value": "NOT_DETECTED",                         "timeOfSample": "2023-11-11T14:38:17.522468611Z",                         "uncertaintyInMilliseconds": 0                     }                 ]             }         }     },     "context": {         "properties": [             {                 "namespace": "Alexa.EndpointHealth",                 "name": "connectivity",                 "value": {                     "value": "OK"                 },                 "timeOfSample": "2023-11-11T14:38:17.522468611Z",                 "uncertaintyInMilliseconds": 0             }         ]     } }
2023/11/11 14:38:17 Status response: 403 Forbidden
2023/11/11 14:38:17 Body response: {     "header": {         "namespace": "System",         "name": "Exception",         "messageId": "f5946669-cc39-461b-8c03-75c9c1380ae4"     },     "payload": {         "code": "SKILL_DISABLED_EXCEPTION",         "description": "The user does not have a valid enablement for your skill."     } }
2023/11/11 14:38:17 Handler ended: {     "Answer:": "Sensor_Motion_Kitchen" }
END RequestId: 189c76d4-9038-4137-aded-5ca8a75904a9

Thanks in advance

I just found the following in the amazon developer forum:

Problem was that I assumed that us-west-2 (Oregon) is North America, whereas it represents "Far East". As a result, the 403 with a description of "The user does not have a valid enablement for your skill." actually means that asynchronous notifications are being sent to the wrong endpoint.
Solved the problem by sending async events to the "Far East" endpoint for users hitting the lambda function in us-west-2 with an AcceptGrant request
So if the user submits an accept grant in this region then the endpoint is as follows:
us-east-1 -> North America: https://api.amazonalexa.com/v3/events
eu-west-1 -> Europe: https://api.eu.amazonalexa.com/v3/events
us-west-2 -> Far East: https://api.fe.amazonalexa.com/v3/events

i have to register eu-west-1 myself, because i can't register the skill with us-east-1, because amazon probably checks what the nearest region is. so maybe you would have to make the event url definable via the database.

I changed the url in line
resp, err := http.Post("https://api.amazonalexa.com/v3/events", "application/json", bytes.NewBuffer(json))
in the push_update method to "https://api.eu.amazonalexa.com/v3/events", compiled and uploaded it and now my routines work.
maybe you can generalize the whole thing a bit so that not everyone has to recompile for their region.

@Thundras - you managed to find the same issue and developer article with the root cause as i did about 6 hours ago :)
Im in the UK and have configured the the Lambda and DynamoDB configured on eu-west-1.
I have successfully got the Skill added in the app, discovery has found and added my 3 switches. When I send state changes they reflect in the app but I think this is when Alexa makes the query back to Lambda routine. I think the push to Alexa isnt working correctly and routines are not being triggered.
I have spent the day trying a number of possible work arounds but without success.

I tried removing everything from eu-west-1 and installing again on us-east-1.  It will let me enable the skill, but wont find the devices.
Have even tried setting up a replicated DynamoDB between eu-west-1 and us-east-1. In the Smart Home page on the Alexa Developer put us-east-1 arn as the default and the eu-west-1 as the europe,india option. Allows me to join and discover the devices but getting the 401 errors. Also tried sending updates to apis in both locations.

Not sure how possible it is to the lambda function to detect where the function is running (eg us-east-1 or eu-west-1) and then choose the endpoint for sending based on that.

In the Incomming Request Json from the Gateway API there is a host section from which you can extract the region. Maybe that would be a possibility

Hmm.  I wasn't able to test in other regions (I'm in New Jersey so us-east-1).  I noted in the install readme that I wasn't sure where other regions should deploy to.
It's nice to know Alexa is just as messed up as AWS in general when it comes to regions!
I think a fix for this might be to document the three deployment areas, as per https://developer.amazon.com/en-GB/docs/alexa/custom-skills/host-a-custom-skill-as-an-aws-lambda-function.html#select-the-optimal-region-for-your-aws-lambda-function
NA | us-east-1 | US East (N. Virginia)
EU or IN | eu-west-1 | EU (Ireland)
FE | us-west-2 | US West (Oregon)

According to https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime  there's a runtime environment  variable which says what region we're running in.  I'll see if I can use that to select the right endpoint.  If I can't then I'll just define a new dummy button where an endpoint can be defined (maybe I'll allow that override, anyway).
Thanks for the detective work; I doubt I'd ever have found it myself!

i'll be happy when the project is up and running. then i can finally build my own motion detectors and door sensors without having to use the overpriced ones from hue or homematic. i'm happy to invest time in research to help you.

OK, so updates have been pushed.  It will automatically detect the region and if you deploy to one of  the 3 standard regions it should(!) pick the right endpoint automatically.
There's two new lines in the log when a notification is sent; e.g.
2023/11/11 22:23:27 Running in region: us-east-1
2023/11/11 22:23:27 Using API endpoint: https://api.amazonalexa.com/v3/events
2023/11/11 22:23:27 Status response: 202 Accepted

The install doc also has a new section: https://github.com/sweharris/Alexa-Smart-Home-VirtualButtons/tree/main/install#api-regional-endpoints which describes how to override these values if deployed to a different region.

That seems to work perfectly. Thank you so much!!
Detected my eu region, selected the eu endpoint and I got the 202 accepted.  Best of all the routine in Alexa picked it up and worked.

I can also confirm that everything is now working and the correct region is selected. Thank you very much.

Excellent.  Thank you both for your help!


Integrate with watchdog for daemon health

#10329
Added a new plugin type WatchdogPlugin
Load the plugin only when the service is running on a Linux machine and configured with WatchdogSec parameter
Added additional logs for debugging purpose
And I did not implement a interface as I'm not sure if notifySystemd needs to be invoked at a different place other than initialization
Environment :
WatchdogSec=30s
Linux ubuntu-dev-VirutalBox 6.8.0-35-generic (x86 arch)

I like that this will take advantage of a systemd feature, but I don't think it makes sense to add it in without having anything being checked internally.
Currently there is nothing that will block the ping from happening.

@cpuguy83 same comment :smile: https://github.com/containerd/containerd/pull/10623#discussion_r1726172036

@samuelkarp @cpuguy83 Just out of curiosity, would utilizing the health check plugin for a health status be sufficient here or is there a different specific set of health checks that should be done?


Is there a Forseti API ?

I have a question, is there a Forseti API ? Its existence will aid easy integration with other tools. Another option is if there is  a Java client ...maybe someone already built a Java wrapper around it.
Happy to hear any suggestions, feedbacks, possible approaches.
Thanks.

Hi, I want to follow-up here, to see if the response given in the email group was helpful.
In essence, forseti 2.0 will have a server component, which exposed via gRPC, but you will have to write a java client (the current client is python).  Would that work for you?
Alternatively, a lot of data are saved in the cloudsql (mysql) database, which again you can easily write a java client to retrieve.
Otherwise, I would be interested to learn the exact integration you need to do (inventory data, violations, etc), and with which kind of app or tool?


merge from arlac77/npm-package-template-esm-only

package.json

chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(engines<EMAIL_ADDRESS>

:tada: This PR is included in version 1.5.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add this to Dev console

see https://quarkusio-quarkusio-github-io-preview-pr-815.surge.sh/guides/dev-console

This project (Quarkus) is incredible!

This project (Quarkus) is incredible!

I am blocked due to an issue I am facing (described here as item 7).
My plan for the first version is to have a tile with a link to the UI and a link for the swagger. I am building my solution on top of yours in #26 , since I can reuse some stuff you are adding there (specially LoggingUiBuildItem)

I am blocked due to an issue I am facing (described here as item 7).
My plan for the first version is to have a tile with a link to the UI and a link for the swagger. I am building my solution on top of yours in #26 , since I can reuse some stuff you are adding there (specially LoggingUiBuildItem)


Missing tags for corner nodes in rectangular mesh generator

In the function _rectangle_quad_mesh (src/mesh/mesh_generator.jl), tags are assigned as follows :
if ix == 1 # West
    push!(tag2nodes[4], iglob)
elseif ix == nx # East
    push!(tag2nodes[3], iglob)
elseif iy == 1
    push!(tag2nodes[2], iglob)
elseif iy == ny
    push!(tag2nodes[1], iglob)
end

Nodes on the corners of the mesh should have two tags since they belong to both boundaries, which is not the case with the current implementation.
A possible solution would be :
if ix == 1 # West
    push!(tag2nodes[4], iglob)
end
if ix == nx # East
    push!(tag2nodes[3], iglob)
end
if iy == 1 # South
    push!(tag2nodes[2], iglob)
end
if iy == ny # North
    push!(tag2nodes[1], iglob)
end

It remains to find out how to deal with a superposition of Dirichlet boundaries conditions on these nodes.

I've proposed a PR with your fix.
Up to now, Dirichlet conditions are only implemented on "faces" (elements of codimension 1) and the API doesn't have any high-level-function to apply Dirichlet conditions on "nodes" (elements of codimension 2). But it is possible to develop such a function with what we have in Bcube.
@Galaxxy31 if you already have something like this, don't hesitate to propose a PR. On the other hand if need it but don't know how to do it, we can take a look at it together.

@Galaxxy31 could you tell us more about your intended use of these multiple tags please?

I don't really have a use for these multiple tags.
The point I was trying to make is that with the current implementation, some boundaries conditions might not be completely defined.
For example, I want to model heat diffusion in a rectangle at 300K, whose southern edge has an imposed temperature of 400K. Since the nodes in the corners don't have the "south" tag, the boundary condition I want to impose is not respected (see figure below).

Here, all the nodes on the south edge have a value of 400K, but those on the corners have a value of 300K (as if they didn't belong to the south edge). The problem would be the same with the north edge but wouldn't be the case if the boundary condition were imposed on the west (or east) edge.
Dealing with two potential boundaries conditions on the corners is another question...

the initial problem described has been solved in #59


Review 2.x.x

I've made headway on a complete re-write. It's still very WIP and some features are missing. It's checked in to the 2.x.x branch.
It's probably a good milestone to evaluate whether we want to keep specific features or not.

I'm very interested!
Is there an exec. available to test?
I'm not a developer and can't compile any code

I also noticed on github an exec.of latest version is missing while it's present on the website mameui.info

Is the 2.x.x version still being worked on since this is written in 2016!
Or is <IP_ADDRESS> the current version new features should be added to?
To be very sure: the current github version is <IP_ADDRESS>?

Updates continued on the main branch, have not heard from this branch in 7 years.  Closing.


invalid_grant :: AADSTS54005: OAuth2 Authorization code was already redeemed, please retry with a new valid code or use an existing refresh token on authorize request

Hi Everybody,
I am experiencing the title issue. I configured everything correctly, and this error occurs just before executing authorization. In Microsoft documentation, I found a similar error. They recommend changing the redirect URI, but I can't apply this solution because the entire process is automated by the library.
Does anyone know how to fix this?

the redirect_uri is a configuration parameter, see https://github.com/omniauth/omniauth_openid_connect?tab=readme-ov-file#usage , maybe share your config and some more details about the software you are using along with  omniauth_openid_connect

Hello @bufferoverflow,
Here is my configuration:
issuer: 'https://login.microsoftonline.com/{tenant}/v2.0'
scope:
    - openid
    - email
response_type: code
discovery: true
required_state: false
client_options:
    scheme: https
    port: 443
    host: 'login.microsoftonline.com'
    identifier: {identifier}
    secret: {secret}
    redirect_uri: {uri_to_redirect}

When the process starts, our platform calls /authorize, and it seems to work fine. However, I believe the problem occurs during the second call when the library calls /token, as referenced in this line.
I am receiving the following error:
invalid_grant: Rack::OAuth2::Client::Error, invalid_grant :: AADSTS54005: OAuth2 Authorization code was already redeemed, please retry with a new valid code or use an existing refresh token. Trace ID: 8e8ddd8d-e70e-4b9e-8d3
Please let me know if you need more information.

No idea why you mention https://github.com/nov/rack-oauth2/blob/70da234801c53a116c2d8e126bb09f237824af5a/lib/rack/oauth2/client.rb#L71, this gem is not depending on it https://github.com/omniauth/omniauth_openid_connect/blob/master/omniauth_openid_connect.gemspec#L30:L31 . maybe set all the endpoint explicit and disable discovery ?

Hello @bufferoverflow,
Rack OAuth2 is a requirement for omniauth_openid_connect. You can find more information in the openid_connect.gemspec.
Regarding setting all endpoints explicitly, I am still receiving the same error response.

not sure why you need required_state, I suggest removing that. A config that works: https://docs.gitlab.com/ee/administration/auth/oidc.html?tab=Azure+OAuth+2.0#configure-microsoft-azure


[WIP] Add tests for controllers

Fixes #137
Describe the changes you have made in this pr -
Initialized tests for controllers and added a few tests for assignments_controller
Tests to be added for the following controllers :

[ ] assignments
[ ] collaborations
[ ] group members
[ ] groups
[ ] logix
[ ] projects
[ ] simulator
[ ] stars

Gem ‘rails-controller-testing’

@danllin, reach out to us on gitter https://gitter.im/CircuitVerse for any help!

This is a large change! @vik-y @tachyons Is it possible to review the same?

@satu0king The good thing about the pr is that all the additions are for tests and the build ensures that all them are passing. 😅


Updates for Dart 2.0 core library changes (wave 2.2)

Change classes that implement StreamTransformer to extend StreamTransformerBase.

tests pass locally.

@kevmoo will handle publishing


Generate R.generated.swift file from terminal.

Could some one help me with this issue
I am doing like this now
./rswift -p /Users/path/Project/Project.xcodeproj

And get
error: [R.swift] Output folder for the 'R.generated.swift' file is mandatory as last argument.
I've try different scenarios ..but it doesn't work.

You should at least give the output directory where R.swift should put the generated file, for example: ./rswift -p /Users/path/Project/Project.xcodeproj  /Users/path/Project
See also the installation instruction, especially the build step you have to add.

I did exactly as you say but it didn't help me. I have add R swift previously as a script on this project but now I'm moving at swift 3 and need to regenerate file and because I have an errors it's not possible to run script at Xcode.

Are you using R.swift 3.0.0? You need the new version if you need Swift 3. I would advise running it from the Xcode build step instead from the command line yourselves, since that makes sure R.swift is using the same output folder and settings as before.

Downloading dependencies
...................
Using R.swift (3.0.0)
Using R.swift.Library (3.0.1)
To build project correctly and launch scripts I need to run it without errors but my project already use R.generated.swift file that was generated for Swift 2.3 Old methods bring me a conflicts. I'm trying to find a solution how to regenerated this file on a earlier stage, for example via terminal and just replace old one with a new one.

If you put the R.swift build step before the Compile Sources step in Xcode it will update the R.swift generated before the compiler will start. So you should always be able to run R.swift even if your code won't compile at the moment.
It is also possible to run the rswift binary from the commandline if you want to, but you will need to specify all the flags it needs, those are the mandatory flags:
rswift [-p|--xcodeproj] [-t|--target] [--bundleIdentifier]
    [--buildProductsDir] [--developerDir] [--sourceRoot] [--sdkRoot]
    [--productModuleName] outputDirectory

I think it would help if you share the exact errors you're getting at the moment, that would give me some context about what could be going wrong.

WOW... never know that scripts could be draggable .. thanks for help. I have dragged it on top and that solved my issue. Thanks again.

You're welcome, good to hear that fixes things!


Fix for circular descriptions

There seems to be an edge case when using refs in wsdls like this:
      <xsd:element name="ExampleContent" type="v1:ExampleContent"/>
      <xsd:element name="ExampleRequest" type="v1:ExampleRequestType"/>

      <xsd:complexType name="ExampleContent">
        <xsd:sequence>
          <xsd:element name="MyID" type="xsd:string" />
        </xsd:sequence>
      </xsd:complexType>

      <xsd:complexType name="ExampleRequestType">
        <xsd:sequence>
          <xsd:element ref="v1:ExampleContent"/>
        </xsd:sequence>
      </xsd:complexType>

The reference to ExampleContent would cause a circular description because there is an element and type of the same name.

Coverage decreased (-0.5%) to 94.522% when pulling 3c10601d30e3f32d73a9219768313fc3cb5daca5 on mastodon0:ref-type into af93a6f45720431371ab3f23866d3ad3f2efae1b on vpulim:master.

thanks @mastodon0 .  can you add more test cases to keep coverage up?

I could add an additional test but it would be unrelated to the fixed bug.
This looks like a problem with coveralls since it doesn't list any file that got decreased coverage.

yea, it does seem like something is up.  thanks!

actually, @mastodon0 could it be with this fix that we now have dead code elsewhere?

I looked into that and doubt it. I know it sounds like the classic "it works on my machine" but running npm run cover has higher coverage after the commit than before.


Support configuring server options for local Walrus

Is your enhancement related to a problem? Please describe.
Be able to configure server options when running walrus local install. e.g., set builtin-catalog-provider to gitee.

Environment

Walrus version: main bd8b2f4560a522fcfb061a081817869f1a088f3a
UI version: dev-95fef06

Test Result: pass
root@iZbp14mscl82upj4amm48eZ:~# walurs local install -e SERVER_BUILTIN_CATALOG_PROVIDER=gitee
Installing...
Checking readiness...
Walrus CLI is configured.

Note: The Docker extension is not available when using the -e flag.


Update Build Category

"Other" is no longer supported. We need to update the build category to "Build and Release"

completed by ededdcc44e03a14e0437abb02f4f0797923070c3


Add BITS queue manager DBs.

@joachimmetz

friendly ping

LGTM if you change the path to define "qmgr2.dat" as well. (I opt a glob)


  Even more so pissed as I committed to that library to help them which I would not have done had they been charging people.
Speaking of, I created a PR over there for a fix around their CategoryOrderAttribute and PropertyGrid BACK IN AUGUST, but they still haven't merged it.  I see your repo is also missing these fixes.
Here's the PR there...
https://github.com/xceedsoftware/wpftoolkit/pull/1523/commits
Not sure how I can point it at yours without downloading and recreating from scratch.  BUT... the time it'll take me to do that, you can probably fix this in five minutes.  It's adding a missing TypeID override for the attribute (required when AllowMultiple is set to true.  They missed that) and then updating the code to use TypeDescriptor.GetAttributes instead of Type.GetCustomAttributes as the latter doesn't take into consideration those attributes added at runtime via TypeDescriptor.AddAttributes.
Check it out, and hopefully, add it to your code, and I'll make the change from them to yours and I'll be happy to never support them again!

Sorry, but I‘ve not really time to look into this, but if you‘d create a pull, I will merge...

Will do.  Lemme take a crack at that later today.  Keep an eye our god it.


Sonic the Anonymous Hedgehog: Watch blendermarket.com

Sonic the Anonymous Hedgehog requests the watch of the watch_keyword blendermarket\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

blendermarket\.com has been seen in 7 true positives, 24 false positives, and 0 NAAs.

Due to the occasional true positives, I feel it's worth having on the watch list

Rejected by Mast in Charcoal HQ. Reason: 'FP to TP ratio is way too high.'


Fix when dropping a unique index in MSSQL

If an MSSQL unique index is created as an index https://github.com/wilsonge/knex/blob/156d1128de1f692dd6de2841198884deaa8276d8/src/dialects/mssql/schema/tablecompiler.js#L121-L125 it needs to be dropped as an index not as a constraint. You can also see in the tests that we are creating index's and dropping constraints.
https://docs.microsoft.com/en-us/sql/t-sql/statements/drop-index-transact-sql?view=sql-server-2017 isn't very clear - it says The DROP INDEX statement does not apply to indexes created by defining PRIMARY KEY or UNIQUE constraints isn't as clear as it should be - it basically says that you must drop a unique constraint as a constraint. But that means you should still drop unique index's as an index.
This is tested on a local mssql docker container

@smorey2 Ping?..

This is at least missing an integration test, which shows that query works as intented

The existing tests cover this already - I'm not exactly sure what extra tests you want added?

@wilsonge Integration test for dropping unique index that is failing without changes in this PR.

@wilsonge existing test checks that query is built as intended, which is no an integration test since it doesn't write anything to DB. In integration test that query is actually ran against real DB and then it should verify that the query indeed actually did drop the index correctly.

Yes I understand what an integration test is. But you don't have any mssql integration tests - all the integration tests run in sqlite - so for a simple bug fix - getting me to create a full set of mssql integration tests on travis - seems like a slightly harsh requirement?

@wilsonge Are you sure this is accurate? If you check test/knexfile.js, there is configuration for test mssql database, and it is my understanding that existing integration tests are also run on MSSQL already.

@wilsonge MSSQL-specific tests do not get executed in Travis, I think (set of databases for CI execution is "maria mysql mysql2 postgres sqlite3 oracledb"), but I don't think that there is an expectation of you building entire solution for running MSSQL tests in CI; just writing a test that would be passing for you locally and in CI after someone eventually adds dockerized mssql test execution would probably suffice.

OK where should this test live then? Because I read this https://github.com/tgriesser/knex/blob/master/test/integration/index.js as only having sqllite code in. And I don't see any place for tests of different dialects at a quick pass through? More than happy to write something if I'm pointed in the right direction tho :)

@wilsonge Check out test/integration/schema/index.js to see how testing for different databases is done, and it's probably appropriate place for your case as well.
There are also cases of db-specific tests there, e. g.
    describe('addColumn', function() {
      describe('mysql only', function() {
        if (!knex ||
            !knex.client ||
            (!(/mysql/i.test(knex.client.dialect)) && !(/maria/i.test(knex.client.dialect)))
        ) {
          return Promise.resolve();
        }

        before(function() {
          return knex.schema.createTable('add_column_test_mysql', function (tbl) {
            tbl.integer('field_foo');
            tbl.integer('field_bar');
          }).then(function() {
            return knex.schema.alterTable('add_column_test_mysql', function (tbl) {
              tbl.integer('field_foo').comment('foo').alter();
              tbl.integer('field_bar').comment('bar').alter();
              tbl.integer('field_first').first().comment('First');
              tbl.integer('field_after_foo').after('field_foo').comment('After');
              tbl.increments('field_nondefault_increments').comment('Comment on increment col');
            });
          });
        });

(not sure if you'd need something like that, presumably creating and dropping unique index is a universal thing with similar outcome, and how exactly it is done is beyond an integration test)

This PR is now irrelevant. In https://github.com/tgriesser/knex/pull/2653 I had to change the way how unique constraint is created to be always just an unique index instead of creating it as unique constraint (unique constraint didn't allow to create partial index which was necessary for constraint to work the same way with other dialects). I'll add integration test for create / drop / create unique constraint there too... that way at least if some query doesn't work some of the queries should throw an error.


Properly Scale Menu Assets (RenderTexture2D scaling)

The context for this PR is in issue #17. This PR seems to work in my testing, besides some minor visual issues that are not directly caused by RenderTexture2D. A quick example: https://youtu.be/RFTeLMdHlR8
At this point, it may be worth making some further changes, such as more verbose support for fRenTexResMultiX within the config file. (Though using fRenTexResMultiX may have bogus results at some point)
This could also use far more testing, as they may be issues that I have yet to see, which are related to how I chose to scale the RenderTexture2Ds.

Okay I think this all good to be merged now. I'll have a look at 1080p rect issue, I think I know where to possibly fix that.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vis-2-widgets-energy for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.vis-2-widgets-energy
   -
ERRORS:

[X] :heavy_exclamation_mark: [E204] Version "0.3.12" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E254] Version "0.3.12" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W184] "common.noConfig" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI.config":"none".
[ ] :eyes: [W523] "package-lock.json" not found in repo! Please remove from .gitignore!

SUGGESTIONS:

[X] :pushpin: [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
[ ] :pushpin: [S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Thu, 12 Sep 2024 05:45:00 GMT based on commit 1fefdf5dee22b7a9b98f8fd41a175d8e36f971ec
ioBroker.repochecker 3.0.2

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E204] Version "0.3.12" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[E254] Version "0.3.12" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Issue outdated due to RECREATE request. Follow up issue #299 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


TexIndy: unresolvable property or identifier: debug

I'm running arara 4.0 rev 1 and have the following arara chain in my tex file:
% arara: lualatex: { synctex: on, shell: true, draft: true, interaction: nonstopmode }
% arara: biber
% arara: makeglossaries
% arara: texindy
% arara: lualatex: { synctex: on, shell: true, draft: true, interaction: nonstopmode }
% arara: lualatex: { synctex: on, shell: true, interaction: nonstopmode }

And this gives me
[Error: unresolvable property or identifier: debug]
[Near : {...
d('texindy', quiet, debug, markup, modules, ....}]

                  ^
[Line: 6, Column: 41]

Is that an arara internal issue or due to my setup?
For completeness: I'm running archlinux (with arara-git installed) and calling arara from within texstudio via  arara-git -v -l "mydocument".tex

Hello!
It's an error in the rule. I also spotted the same issue in xindy as well. Thank you! I already fixed the rules in the repository and will submit a patch to CTAN as soon as possible!
All the best!

By the way, I don't know how to update your version. Perhaps @pat-s can help us? :wink:

Thanks, works now (I build directly from git again)!

Glad to hear it's working! I already submitted the fix to CTAN. Thank you!

Thanks, works now (I built directly from git again)!

Right, just re-install :+1:

I think there might be a similar error in indent.yaml
On Fri, 13 Jul 2018, 11:06 Patrick Schratz<EMAIL_ADDRESS>wrote:

Thanks, works now (I built directly from git again)!
Right, just re-install 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cereda/arara/issues/111#issuecomment-404788831, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACHxYDFdf_pWQzGqu5SQHyIztFwratttks5uGHEIgaJpZM4VOkyr
.

@cmhughes indeed, fixed and will submit yet another patch. :wink:

Ace, many thanks!
On Fri, 13 Jul 2018, 11:35 Paulo Cereda<EMAIL_ADDRESS>wrote:

@cmhughes https://github.com/cmhughes indeed, fixed and will submit yet
another patch. 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cereda/arara/issues/111#issuecomment-404795386, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACHxYNE7o_szMTdGtBHhG3wb-NNg9_FYks5uGHgKgaJpZM4VOkyr
.

Patch submitted to CTAN!

CTAN poked me back! The new version will be deployed in a day or two, then we will hit TeX Live.


Fixed Rate、Fixed Delay

Can you support something similar to Java fixed rate and fixed delay

The current schedule supports fixed rate. If you need fixed delay, you could implement that with a custom schedule relatively easily. Schedule is an interface so anyone can plug in their desired scheduling policy. For built-in schedules, I think it's important to stick to the "official spec".

Sorry, I responded too quickly. There's no way to implement a fixed delay because we do not track the time at which a job completes.


[$500]  Collect admin - Admin badge is not crossed out when removing admin offline

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.47-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

User is the owner of Collect workspace
The Collect workspace has admin

Launch New Expensify app
Go to workspace settings > Collect workspace
Go to Members
Go offline
Select an admin
Tap on the dropdown > Remove member
Remove the admin

Expected Result:
The admin badge will be crossed out (web behavior)
Actual Result:
The admin badge is not crossed out
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a65f30dbfbc53bd4
Upwork Job ID:<PHONE_NUMBER>509988864
Last Price Increase: 2024-03-12
Automatic offers:

mkhutornyi | Contributor | 0

@anmurali  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave8
CC @zanyrenney

Not reproduced it is working for Me IOS native

Proposal
Please re-state the problem that we are trying to solve in this issue.
Collect admin - Admin badge is not crossed out when removing admin offline
What is the root cause of that problem?
The strikethrough style from OfflineWithFeedback is not applied to text in the badge.
What changes do you think we should make in order to solve the problem?
If we want to give a badge special condition in OfflineWithFeedback, we can change const props: StrikethroughProps
To
                const style = StyleUtils.combineStyles(child.props.style, styles.offlineFeedback.deleted, styles.userSelectNone)
                const isChildBadge = isBadge(child);
                const props: StrikethroughProps = {
                    style: isChildBadge ? undefined : style,
                    textStyle: isChildBadge ? style : undefined,
                };

What alternative solutions did you explore? (Optional)

Crossing of the Admin badge works fine on web but not on native.
Substituting the Badge component with the returning node
<View/Banner><Text>....</Text></View>

of Badge at roleBadge in WorkspaceMembersPage works correctly on native as well.
Can we identify the exact RCA for why using Badge affects and it affects only for native?

Proposal
Please re-state the problem that we are trying to solve in this issue.
Collect admin - Admin badge is not crossed out when removing admin offline
What is the root cause of that problem?
Each item in the members list is wrapped by OfflineWithFeedback which will apply the line cross through to style prop here but the Badge is using passing textStyles prop to the Text.
Web works because if you apply a css higher in the tree it will be applied to the children, but React Native does not do that instead it strictly apply styles to individual views.
What changes do you think we should make in order to solve the problem?
In the OfflineWithFeedback.applyStrikeThrough we need to add extra checks and apply the styles correctly.
    if (child.type.displayName === 'Badge') {
        props.textStyles = StyleUtils.combineStyles(child.props.textStyles, styles.offlineFeedback.deleted, styles.userSelectNone);
    }

This is more flexible and can accommodate adding new components that will need to be styled.
What alternative solutions did you explore? (Optional)
Use more generic check when applying style in OfflineWithFeedback.applyStrikeThrough
if (child.props.textStyles) {
    props.textStyles = StyleUtils.combineStyles(child.props.textStyles, styles.offlineFeedback.deleted, styles.userSelectNone);
}

@mkhutornyi will takeover this issue as C+ as they worked on a similar issue and have better context.

Proposals are being discussed. @mkhutornyi will pick the best one shortly.

Hey @mkhutornyi would you mind linking other parts of the code where we do that?

So the idea is to use the same pattern and not just pass the entire styles, right?

Thanks assigned @apeyada

hmm I think we have a bug, @mkhutornyi was the C+ here.
Anyway, I will fill the checklist tomorrow.

@mkhutornyi @apeyada if you could continue the checklist.

friendly bump @mkhutornyi @apeyada

Still waiting on the checklist here. cc @mkhutornyi @apeyada

@mkhutornyi is OOO

I am moving to weekly until @mkhutornyi is back.

I paid @apeyada while we wait for @mkhutornyi to return and complete the checklist.

Still waiting ofr @mkhutornyi

@mkhutornyi has been paid and tests added.


Missing HTML escaping in advisory description

See https://osv.dev/vulnerability/GHSA-prc3-vjfx-vhm9 for example, the XSS example is actually interpreted as HTML and breaks the page.

Thanks a ton for reporting this! This will be fixed with https://github.com/google/osv.dev/pull/731


CLI Auto completion

Cobra supports auto completion, we should provide the command and docs on how to add changie auto completion to your environment.
https://github.com/spf13/cobra/blob/master/shell_completions.md

Auto-generated documentation is part of the gen CLI command which is already part of the docs, so nothing really is required here.


Add autoinstallers to guide

We need @samdivaio probably to properly add this to the guide, this being the main way for people to install, and then the long guide if it didn't work

Okiedokie. Working on more automation of it right now so this info is out of date.


Move number of split quantiles from hardwired to node class member

Context
Just wanted to make this change before I forget about it, related to https://github.com/cerlymarco/linear-tree/issues/41
Checklist

[x ] Change meets or does not compromise the Baseline Security Requirements

Merging can wait until we have some actually useful changes to deploy as well :)


Future of YakYak after hangouts is killed. Google Chat?

Hangouts is being shut down by the end of 2020
Are there plans to support Google Chat in the future?
Thanks

are you sure?. Maybe there are another plan after covid19
https://support.google.com/hangouts/thread/34051212?hl=en


I close this PR since we shouldn't publish API keys.


Add riemann output

whoa, something is wrong with your branch and/or fork, your change shouldn't include all of these commits. Please rebase your changes off of HEAD and try again.

Woops will do. Sorry

Hopefully that looks a little better.

Yes, much better! One thing is that it looks like your test is relying on a riemann docker container that you haven't added to the Makefile.
Could you try adding this:
docker run --name riemann -p "5555:5555" -d blalor/riemann

to the Makefile under docker-run and docker-run-circle?

@allenj It looks like we need a godep update as well, I'm going to push a separate PR with some minor code tweaks as well


[GOBBLIN-938] Make job-template resolution available in all JobLaunchers

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] https://issues.apache.org/jira/browse/GOBBLIN-938

Description

[x] Here are some details about my PR, including screenshots (if applicable):
Getting rid of duplicated gobblin.job.templates in GaaS code
Making the job-template resolution available in AbstractJobLauncher so that all its extensions will be able to resolve the template, including Helix JobLauncher. Once it is being resolved and added as part of JobContext, the Source will be added with this job properties so as passing-down to each workunits.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason: Unit tested in LocalJobLauncher

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2787 into master will increase coverage by 0.01%.
The diff coverage is 84.61%.

@@             Coverage Diff              @@
##             master    #2787      +/-   ##
============================================
+ Coverage     45.32%   45.34%   +0.01%
- Complexity     8858     8863       +5
============================================
  Files          1894     1894
  Lines         70874    70877       +3
  Branches       7794     7793       -1
============================================
+ Hits          32123    32138      +15
+ Misses        35788    35779       -9
+ Partials       2963     2960       -3

Impacted Files
Coverage Δ
Complexity Δ

...pache/gobblin/cluster/GobblinHelixJobLauncher.java
81.81% <ø> (ø)
26 <0> (ø)
:arrow_down:

...org/apache/gobblin/azkaban/AzkabanJobLauncher.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...rg/apache/gobblin/runtime/AbstractJobLauncher.java
59.13% <100%> (+1.01%)
33 <2> (+2)
:arrow_up:

...gobblin/service/modules/spec/JobExecutionPlan.java
75.8% <100%> (ø)
9 <0> (ø)
:arrow_down:

...odules/template_catalog/FSFlowTemplateCatalog.java
58.69% <50%> (ø)
8 <0> (ø)
:arrow_down:

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
63.42% <0%> (-1.39%)
27% <0%> (-1%)

...e/gobblin/runtime/locks/ZookeeperBasedJobLock.java
64.44% <0%> (+1.11%)
16% <0%> (+1%)
:arrow_up:

...lin/restli/throttling/ZookeeperLeaderElection.java
72.22% <0%> (+2.22%)
13% <0%> (ø)
:arrow_down:

.../limiter/RedirectAwareRestClientRequestSender.java
87.2% <0%> (+2.32%)
18% <0%> (+1%)
:arrow_up:

...he/gobblin/metrics/reporter/ScheduledReporter.java
63.63% <0%> (+3.03%)
15% <0%> (ø)
:arrow_down:

... and 2 more

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 d9e4f9a...799e932. Read the comment docs.


[AMORO-2938] Add common dependency chart

Why are the changes needed?

Close #2938.
Brief change log

Due to the network issue, it's very very hard for us to pull the common dependency from registry-1.docker.io. We can add the dependency to the project directly.
# helm dependency build
Error: no repository definition for oci://registry-1.docker.io/bitnamicharts. Please add the missing repos via 'helm repo add'

# ping registry-1.docker.io
PING registry-1.docker.io (<IP_ADDRESS>) 56(84) bytes of data.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

We cannot review the contents of the compressed package, which may be risky. Can we specify the pull this common method through http get it ?

We cannot review the contents of the compressed package, which may be risky. Can we specify the pull this common method through http get it ?

emm, it seems no other ways. I used gcp to download the dependency.

It's not a good idea to add a tgz file to git repo.
Maybe you can build the amoro helm package in an environment where the network allows it and then distribute it to the environment where it needs to be deployed

Or Amoro can maintain built helm charts.
Currently, the Amoro project provides packaged charts in gh-pages, but this branch is not maintained.
Perhaps you can add a workflow to maintain this distribution

It's not a good idea to add a tgz file to git repo.
Maybe you can build the amoro helm package in an environment where the network allows it and then distribute it to the environment where it needs to be deployed

ok, let me think again.

@baiyangtx @czy006
I copied some templates files from bitnami/charts repository.
like doris does.
https://github.com/apache/doris/blob/a831aabac493195d0048eaf8c0b21c77bb8bd674/be/src/vec/functions/function_quantile_state.cpp#L17

This problem has been bothering me for a long time, nice to see that this issue is resolving.

It's also difficult for me to download the common dependency.

Is it possible to put these files into a separate directory?

Good idea, updated.

Thanks for the work! @xleoken
Thanks for the review! @baiyangtx


Resizable right click options menu

Is your feature request related to a problem? Please describe.
The menu for right click should be resizable, independently of fixed or resizable mode.
Describe the solution you'd like
Have a plugin that allows for only right click option menu to be scaled up or down
Describe alternatives you've considered
Currently resizing the entire game using stretched mode accomplishes this, but the game also is stretched.

Because clicking menu options causes data to be sent to the server, I do not think we want to modify menu sizes.

Hmm, what exact data is being sent to the server that would be different if the menu were to be scaled up?


Add StatusCode, headers and error message fields to WebRequestResponse

Add helper method to convert String dictionary into QueryParameters string
Add StatusCode, headers and error message fields to WebRequestResponse
This allows us to access HTTP Status Code, headers from the response and also access the error if the request fails.
Tested on Unity 2021.3 (specially WebGL)

Thanks for your contribution! You changes have been pushed in version 1.2.0.

Small contribution to a important solution :)


EX4 submission

@ItamarShDev
Please review my submission.
Thanks , Shon

:+1:

@ItamarShDev  why i didn't dot a grade for this exercise ?

yes you did, 100


Infinite recursion introduced in 1.0.0

The change in #845 introduced a crash in Sourcery for me.
To reproduce:
$ swift --version
Apple Swift version 5.2.4 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.6.0
$ git clone https://github.com/krzysztofzablocki/Sourcery.git
$ cd Sourcery
$ git checkout 6f2c00fb4af7bc3d5022dff8336da9c40c40283c
$ swift build -c release
$ cd ..
$ git clone https://github.com/realm/SwiftLint.git
$ cd SwiftLint
$ git checkout 4083f1688556fb55c3a4972f69bb95ea0405ac96
$ ../Sourcery/.build/release/sourcery --sources Source/SwiftLintFramework/Rules --templates .sourcery/MasterRuleList.stencil --output .sourcery
No config file provided or it does not exist. Using command line arguments.
Scanning sources...
	loadOrParse: 1.1053340435028076
[1]    15167 bus error  ../Sourcery/.build/release/sourcery --sources Source/SwiftLintFramework/Rules

This crash doesn't happen with the previous commit on master: a441c57219fd933cd63ab49b162ad98cddfbda68
I think the crash is due to a stack overflow caused by infinite recursion.
Here's the backtrace I get when running Sourcery with Xcode:

Backtrace
* thread #12, queue = 'com.apple.root.user-interactive-qos', stop reason = EXC_BAD_ACCESS (code=2, address=0x70000a5a8ff8)
    frame #0: 0x00007fff713e1d36 libswiftCore.dylib`std::__1::pair<(anonymous namespace)::TupleCacheEntry*, swift::MetadataResponse> swift::LockingConcurrentMap<(anonymous namespace)::TupleCacheEntry, (anonymous namespace)::TupleCacheStorage>::getOrInsert<(anonymous namespace)::TupleCacheEntry::Key, swift::MetadataRequest&, swift::TargetValueWitnessTable<swift::InProcess> const*&>((anonymous namespace)::TupleCacheEntry::Key, swift::MetadataRequest&, swift::TargetValueWitnessTable<swift::InProcess> const*&) + 38
    frame #1: 0x00007fff713e18bc libswiftCore.dylib`swift_getTupleTypeMetadata + 140
    frame #2: 0x00007fff713e227e libswiftCore.dylib`swift_getTupleTypeMetadata2 + 30
    frame #3: 0x00007fff7112a9af libswiftCore.dylib`(extension in Swift):Swift.Collection.dropFirst(Swift.Int) -> A.SubSequence + 95
  * frame #4: 0x00000001000b6fb6 sourcery`String.drop(first=1, last=1, self="(T>(lhs: A<T>, rhs: A<T>) -> Bool {\n                    return false\n                }\n            \"\"\"),\n            Example(\"\"\"\n            public extension Array)") at Extensions.swift:56:28
    frame #5: 0x00000001000b6f06 sourcery`String.dropFirstAndLast(n=1, self="(T>(lhs: A<T>, rhs: A<T>) -> Bool {\n                    return false\n                }\n            \"\"\"),\n            Example(\"\"\"\n            public extension Array)") at Extensions.swift:51:16
    frame #6: 0x00000001000b7753 sourcery`String.isValidTupleName(self="(T>(lhs: A<T>, rhs: A<T>) -> Bool {\n                    return false\n                }\n            \"\"\"),\n            Example(\"\"\"\n            public extension Array)") at Extensions.swift:75:35
    frame #7: 0x000000010027890f sourcery`static Composer.actualTypeName(typeName=0x000000010644aea0, containingType=0x00000001017a87d0, unique=331 key/value pairs, typealiases=12 key/value pairs, self=SourceryFramework.Composer) at Composer.swift:348:34
    frame #8: 0x000000010027cd4f sourcery`static Composer.resolveType(typeName=0x000000010644aea0, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs, self=SourceryFramework.Composer) at Composer.swift:132:35
    frame #9: 0x0000000100281ec9 sourcery`closure #1 in static Composer.resolveType(typeName=0x000000010644aea0, self=SourceryFramework.Composer, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs) at Composer.swift:140:25
    frame #10: 0x00000001002832e4 sourcery`closure #3 in static Composer.resolveType(parameter=0x0000000106049fa0, resolveTypeWithName=0x000000010028a2d0 sourcery`partial apply forwarder for closure #1 (SourceryRuntime.TypeName) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.(resolveType in _8AFDFAE43BAEC17D714368D5062BEB48)(typeName: SourceryRuntime.TypeName, containingType: Swift.Optional<SourceryRuntime.Type>, unique: Swift.Dictionary<Swift.String, SourceryRuntime.Type>, modules: Swift.Dictionary<Swift.String, Swift.Dictionary<Swift.String, SourceryRuntime.Type>>, typealiases: Swift.Dictionary<Swift.String, SourceryRuntime.Typealias>) -> Swift.Optional<SourceryRuntime.Type> at <compiler-generated>) at Composer.swift:167:34
    frame #11: 0x00000001002833a2 sourcery`thunk for @callee_guaranteed (@guaranteed MethodParameter) -> (@error @owned Error) at <compiler-generated>:0
    frame #12: 0x000000010028a494 sourcery`thunk for @callee_guaranteed (@guaranteed MethodParameter) -> (@error @owned Error)partial apply at <compiler-generated>:0
    frame #13: 0x00007fff7120464d libswiftCore.dylib`(extension in Swift):Swift.Sequence.forEach((A.Element) throws -> ()) throws -> () + 381
    frame #14: 0x000000010027df0f sourcery`static Composer.resolveType(typeName=0x000000010163fb20, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs, self=SourceryFramework.Composer) at Composer.swift:166:32
    frame #15: 0x0000000100281ec9 sourcery`closure #1 in static Composer.resolveType(typeName=0x000000010163fb20, self=SourceryFramework.Composer, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs) at Composer.swift:140:25
    frame #16: 0x00000001002832e4 sourcery`closure #3 in static Composer.resolveType(parameter=0x000000010163fd90, resolveTypeWithName=0x000000010028a2d0 sourcery`partial apply forwarder for closure #1 (SourceryRuntime.TypeName) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.(resolveType in _8AFDFAE43BAEC17D714368D5062BEB48)(typeName: SourceryRuntime.TypeName, containingType: Swift.Optional<SourceryRuntime.Type>, unique: Swift.Dictionary<Swift.String, SourceryRuntime.Type>, modules: Swift.Dictionary<Swift.String, Swift.Dictionary<Swift.String, SourceryRuntime.Type>>, typealiases: Swift.Dictionary<Swift.String, SourceryRuntime.Typealias>) -> Swift.Optional<SourceryRuntime.Type> at <compiler-generated>) at Composer.swift:167:34
    frame #17: 0x00000001002833a2 sourcery`thunk for @callee_guaranteed (@guaranteed MethodParameter) -> (@error @owned Error) at <compiler-generated>:0
    frame #18: 0x000000010028a494 sourcery`thunk for @callee_guaranteed (@guaranteed MethodParameter) -> (@error @owned Error)partial apply at <compiler-generated>:0
    frame #19: 0x00007fff7120464d libswiftCore.dylib`(extension in Swift):Swift.Sequence.forEach((A.Element) throws -> ()) throws -> () + 381
...
931 stack frames omitted for brevity
...
    frame #950: 0x000000010027e174 sourcery`static Composer.resolveType(typeName=0x000000010132f760, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs, self=SourceryFramework.Composer) at Composer.swift:172:36
    frame #951: 0x0000000100281ec9 sourcery`closure #1 in static Composer.resolveType(typeName=0x000000010132f760, self=SourceryFramework.Composer, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs) at Composer.swift:140:25
    frame #952: 0x0000000100283854 sourcery`closure #4 in static Composer.resolveType(typeParameter=0x0000000101312780, resolveTypeWithName=0x000000010028a2d0 sourcery`partial apply forwarder for closure #1 (SourceryRuntime.TypeName) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.(resolveType in _8AFDFAE43BAEC17D714368D5062BEB48)(typeName: SourceryRuntime.TypeName, containingType: Swift.Optional<SourceryRuntime.Type>, unique: Swift.Dictionary<Swift.String, SourceryRuntime.Type>, modules: Swift.Dictionary<Swift.String, Swift.Dictionary<Swift.String, SourceryRuntime.Type>>, typealiases: Swift.Dictionary<Swift.String, SourceryRuntime.Typealias>) -> Swift.Optional<SourceryRuntime.Type> at <compiler-generated>) at Composer.swift:173:38
    frame #953: 0x0000000100283912 sourcery`thunk for @callee_guaranteed (@guaranteed GenericTypeParameter) -> (@error @owned Error) at <compiler-generated>:0
    frame #954: 0x000000010028a354 sourcery`partial apply for thunk for @callee_guaranteed (@guaranteed GenericTypeParameter) -> (@error @owned Error) at <compiler-generated>:0
    frame #955: 0x00007fff7120464d libswiftCore.dylib`(extension in Swift):Swift.Sequence.forEach((A.Element) throws -> ()) throws -> () + 381
    frame #956: 0x000000010027e174 sourcery`static Composer.resolveType(typeName=0x00000001017a8d10, containingType=0x00000001017a87d0, unique=331 key/value pairs, modules=0 key/value pairs, typealiases=12 key/value pairs, self=SourceryFramework.Composer) at Composer.swift:172:36
    frame #957: 0x000000010027c9e0 sourcery`closure #7 in static Composer.uniqueTypesAndFunctions(typeName=0x00000001017a8d10, containingType=0x00000001017a87d0, self=SourceryFramework.Composer, unique=331 key/value pairs, modules=0 key/value pairs, resolvedTypealiases=12 key/value pairs) at Composer.swift:81:25
    frame #958: 0x000000010027f6b6 sourcery`static Composer.resolveVariableTypes(variable=0x00000001017a1f30, type=0x00000001017a87d0, resolve=0x000000010027ca70 sourcery`partial apply forwarder for closure #7 (SourceryRuntime.TypeName, Swift.Optional<SourceryRuntime.Type>) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.uniqueTypesAndFunctions(SourceryRuntime.FileParserResult) -> (types: Swift.Array<SourceryRuntime.Type>, functions: Swift.Array<SourceryRuntime.Method>, typealiases: Swift.Array<SourceryRuntime.Typealias>) at <compiler-generated>, self=SourceryFramework.Composer) at Composer.swift:190:25
    frame #959: 0x000000010027f59d sourcery`closure #1 in closure #8 in static Composer.uniqueTypesAndFunctions($0=0x00000001017a1f30, self=SourceryFramework.Composer, type=0x00000001017a87d0, resolveType=0x000000010027ca70 sourcery`partial apply forwarder for closure #7 (SourceryRuntime.TypeName, Swift.Optional<SourceryRuntime.Type>) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.uniqueTypesAndFunctions(SourceryRuntime.FileParserResult) -> (types: Swift.Array<SourceryRuntime.Type>, functions: Swift.Array<SourceryRuntime.Method>, typealiases: Swift.Array<SourceryRuntime.Typealias>) at <compiler-generated>) at Composer.swift:88:17
    frame #960: 0x0000000100276392 sourcery`thunk for @callee_guaranteed (@guaranteed Variable) -> (@error @owned Error) at <compiler-generated>:0
    frame #961: 0x0000000100289a24 sourcery`partial apply for thunk for @callee_guaranteed (@guaranteed Variable) -> (@error @owned Error) at <compiler-generated>:0
    frame #962: 0x00007fff7120464d libswiftCore.dylib`(extension in Swift):Swift.Sequence.forEach((A.Element) throws -> ()) throws -> () + 381
    frame #963: 0x000000010027ece7 sourcery`closure #8 in static Composer.uniqueTypesAndFunctions(counter=38, types=331 values, self=SourceryFramework.Composer, resolveType=0x000000010027ca70 sourcery`partial apply forwarder for closure #7 (SourceryRuntime.TypeName, Swift.Optional<SourceryRuntime.Type>) -> Swift.Optional<SourceryRuntime.Type> in static SourceryFramework.Composer.uniqueTypesAndFunctions(SourceryRuntime.FileParserResult) -> (types: Swift.Array<SourceryRuntime.Type>, functions: Swift.Array<SourceryRuntime.Method>, typealiases: Swift.Array<SourceryRuntime.Typealias>) at <compiler-generated>, unique=331 key/value pairs) at Composer.swift:87:28
    frame #964: 0x00007fff71533181 libswiftDispatch.dylib`partial apply forwarder for reabstraction thunk helper from @callee_guaranteed (@unowned Swift.Int) -> () to @escaping @callee_guaranteed (@unowned Swift.Int) -> () + 17
    frame #965: 0x00007fff7152db94 libswiftDispatch.dylib`reabstraction thunk helper from @escaping @callee_guaranteed (@unowned Swift.Int) -> () to @callee_unowned @convention(block) (@unowned Swift.Int) -> () + 20
    frame #966: 0x0000000100e7f85b libdispatch.dylib`_dispatch_client_callout2 + 8
    frame #967: 0x0000000100e95f1d libdispatch.dylib`_dispatch_apply_invoke + 181
    frame #968: 0x0000000100e7f826 libdispatch.dylib`_dispatch_client_callout + 8
    frame #969: 0x0000000100e93573 libdispatch.dylib`_dispatch_root_queue_drain + 816
    frame #970: 0x0000000100e93e03 libdispatch.dylib`_dispatch_worker_thread2 + 127
    frame #971: 0x0000000100f0d31b libsystem_pthread.dylib`_pthread_wqthread + 220
    frame #972: 0x0000000100f0c49b libsystem_pthread.dylib`start_wqthread + 15

definitely the cause as when I revert that single function change it works properly, @asifmujteba any ideas on how to fix this?

it seems something wrong during parsing the Typename, not sure about the exact Typename which method is not able to parse, I'll try to investigate.
It would be really helpful if we could reduce the input range or may be adding exception break point and check the Typname value which is causing this.

Got the same situation with the release version trying to generate tests for SwiftLint:
artem@agarmash-MBP SwiftLint % brew info sourcery
sourcery: stable 1.0.0 (bottled), HEAD
Meta-programming for Swift, stop writing boilerplate code
https://github.com/krzysztofzablocki/Sourcery
/usr/local/Cellar/sourcery/1.0.0 (7 files, 8.8MB) *
  Poured from bottle on 2020-11-10 at 15:07:37
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/sourcery.rb
License: MIT
==> Requirements
Required: Xcode >= 10.2 ✔
==> Options
--HEAD
	Install HEAD version
==> Analytics
install: 821 (30 days), 3,217 (90 days), 14,445 (365 days)
install-on-request: 817 (30 days), 3,209 (90 days), 14,426 (365 days)
build-error: 0 (30 days)
artem@agarmash-MBP SwiftLint % swift --version
Apple Swift version 5.3 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.4.0
artem@agarmash-MBP SwiftLint % make sourcery
sourcery --sources Source/SwiftLintFramework/Rules --templates .sourcery/PrimaryRuleList.stencil --output .sourcery
No config file provided or it does not exist. Using command line arguments.
Scanning sources...
	loadOrParse: 0.2522190809249878
make: *** [Source/SwiftLintFramework/Models/PrimaryRuleList.swift] Bus error: 10

There is at least 2 places where the old method returns a different value than the new one with this command
sourcery --sources Source/SwiftLintFramework/Rules --templates .sourcery/PrimaryRuleList.stencil --output .sourcery
isValidClosureName is called on that string from StaticOperatorRule.swift
(T>(lhs: A<T>, rhs: A<T>) -> Bool {
                    return false
                }
            """),
            Example("""
            public extension Array)

the old method returns false, the new one returns true
isValidClosureName is called on that string from OperatorFunctionWhitespaceRule.swift
(A>(lhs: A, rhs: A) -> A {}\n"),
            Example("func abc(lhs: Int, rhs: Int) -> Int {}\n")
        ],
        triggeringExamples: [
            Example("↓func <|(lhs: Int, rhs: Int) -> Int {}\n"),   // no spaces after
            Example("↓func <|<<A>(lhs: A, rhs: A) -> A {}\n"),     // no spaces after
            Example("↓func <|  (lhs: Int, rhs: Int) -> Int {}\n"), // 2 spaces after
            Example("↓func <|<  <A>(lhs: A, rhs: A) -> A {}\n"),   // 2 spaces after
            Example("↓func  <| (lhs: Int, rhs: Int) -> Int {}\n"), // 2 spaces before
            Example("↓func  <|< <A>(lhs: A, rhs: A) -> A {}\n")    // 2 spaces before
        ]
    ))

the old method returns false, the new one returns true
Not sure how that all work, but the input string itself seems to be complete garbage. I wonder if #845 is the root cause of the issue, or if it just brought a bigger issue to light

I took a few more minutes to dig into it. I would say the issue comes from here
https://github.com/krzysztofzablocki/Sourcery/blob/master/SourceryFramework/Sources/Parsing/FileParser.swift#L495-L497
In both cases, the type of the variable public static let description = RuleDescription( is nil, and "<<unknown type, please add type attribution to variable \(declaration)'")>>" is used instead of the real type.
declaration here is the whole block of code that declare the variable. public static .... = RuleDescription( ........ )
That string is then parsed in Composer.swift, identified as a bunch of incorrect types (generic, closure, ...), and finishes into a loop.
I don't think the loop is the real issue here, the culprit is the huge blob of code incorrectly parsed as a type.
The question is, what typeName should be used when the type is unknown?

@DavidBertet If sourcekit can't parse type properly then probably just nil? or if not nil we can call it TypeUnknown so that it generates error when generating code depending on knowing that information, what do you think?

I did some digging and it seems that sourcery is really not handling well the multi-line var declarations because of this line of code https://github.com/krzysztofzablocki/Sourcery/blob/master/SourceryFramework/Sources/Parsing/FileParser.swift#L482 @ilyapuchka since you are the one that wrote that line, what was the thinking behind grabbing just first line ? this along with the code in inferType causes lots of types to not be recognized for SwiftLint codebase

Fixed in 1.0.1


Nicer automated snapshot of files from Verus + weekly auto-updates

This PR does a few things:

Moves away from the older snapshot of vstd (that collapsed all of vstd to a single file using inline-crate) to instead hold each file individually
Sets up a script that makes it easy to get the latest vstd from Verus (and also a helper script to format it)
Moves syntax.rs to be part of this automatically-get-this-from-Verus setup
Updates the snapshot tests to account for this move
Sets up a CI job that runs once every night (at UTC 00:00) to see if our snapshot has diverged from Verus's. If it has, then it opens up a PR to call our attention to it

To review this PR, it is likely easiest to look at each commit individually.
NOTE: This PR should not be merged into verusfmt main until https://github.com/verus-lang/verus/pull/1019 and an upcoming PR for syntax.rs have been merged. Thus, I am marking it as a draft, despite otherwise being ready to review.

Sounds reasonable, switched it to weekly, and if even that ends up too much, we can switch it out to monthly

Now that https://github.com/verus-lang/verus/pull/1019 is merged, we can merge this in. I will then manually trigger the workflow run (outside regular schedule, just to confirm it is working as expected), but after that, the weekly schedule should begin.

Heh, it detects the difference correctly (the part that I had tested before making the PR), but doesn't actually make the PR (the part that I could not test earlier). Turns out that this is because of an organization level permission:

For repositories belonging to an organization, this setting can be managed by admins in organization settings under Actions > General > Workflow permissions.

Will work on getting that set up, so that this starts working


DBZ-2211 Harden test against potential extra schema event

https://issues.redhat.com/browse/DBZ-2211

SQL Server failure tracked as https://issues.redhat.com/browse/DBZ-2231
MySQL failure tracked as https://issues.redhat.com/browse/DBZ-2269


Add synchronize call between MOFF and Save

I'll just copy-paste Jayce's explanation because I don't fully understand it.

The underlying problem was that all of the CUDA operations are done asynchronously.  Normally Bifrost forces a sync when the data cross a memory space boundary.  However, when using a CUDA-based ring you end up with data being written that isn't actually there until the memcpy completes.  The reserve on the ring doesn't know about this so when that reserve is released the next block starts to read.  That read can start before the copy finishes.

Yep.

If anyone wants a bit more info:  bifrost#138


MAINTAINERS.md: Add Max Inden

I would like to help out @stuartnelson3 as a second official maintainer of the Alertmanager project.
Let me know what you think.

Awesome. Thanks everyone!


Added support for QuantizedMatMul (uint8) with some unit tests.

Included a unit test to check conversion of quantized tf-to-coreml model having convolution operation and evaluated it against (non-quantized) base Tensorflow model with delta = 0.05
Added support for quantized inner_product layers along with some unit tests.

Looks good!


Error seen during 02_install.ps1

Enter target directory of WSL dist: C:\Users\bmurm\temp
Import in progress, this may take a few minutes.
The operation completed successfully.
<3>WSL (9) ERROR: CreateProcessEntryCommon:502: execvpe ./02_install.sh failed 2
<3>WSL (9) ERROR: CreateProcessEntryCommon:505: Create process not expected to return
The operation completed successfully.
Any idea on how to address these errors? Similar ones show up in later steps as well. Something to do with permissions?

Could be a new issue with WSL?
https://github.com/microsoft/WSL/issues/10767

Looks like a permission issue with the target directory, try a different one?
I will add a fix to elevate this script as well so it will not be an issue.

I tried a different directory and also running the script as admin, no success.
This runs fine: wsl.exe -d $DistName
But this fails with error 2 (file not found?): wsl.exe -d $DistName -e ./02_install.sh
The internet is full with reports of this error, see e.g.:
https://askubuntu.com/questions/1423048/i-am-getting-error-on-windows-subsystem
I tried setting the correct default distro, but that also didn't help.
Definitely an issue with WSL and not your script. I will try to start fresh with all distros deleted.


Add IsEnabled with a global predicate

Adds support for registering a predicate for a listener to handle
IsEnabled. This allows a listener to ignore events in a given context.

/cc @pranavkm
@avanderhoorn @nikmd23 FYI

:shipit:

Looks good to me!


(user) Edit profile page

Creating Edit page for the profile CRUD pages.

Description: We added 7 different example users profiles all with passwords of either "test" or "foo", and usernames and emails based on their pk (e.g. pk = 1 --> "User 1")
Progress: We have submitted a pull request for the code, which is waiting review.

Issue Score: Satisfactory
Comments:
I think the result of this issue was that you guys didn't end up needing to do anything, so I'll mark it as minor. Title is a bit too generic, and there's no summary goal in the description.


Update Composer dependencies (2021-01-25-00-08)

Visual regression test passed!
View the visual regression test report

Visual regression test passed!
View the visual regression test report


[cmt] Unable to extract mgid

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.09.27. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2016.09.27

Before submitting an issue make sure you have:

[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
E:\>youtube-dl --verbose http://www.cmt.com/shows/dallas-cowboys-cheerleaders/dallas-cowboys-cheerleaders-making-the-team-ep-1106-dance-intervention/1740045/playlist/#id=1740045
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.cmt.com/shows/dallas-cowboys-cheerleaders/dallas-cowboys-cheerleaders-making-the-team-ep-1106-dance-intervention/1740045/playlist/#id=1740045']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.09.27
[debug] Python version 3.4.4 - Windows-10-10.0.10586
[debug] exe versions: ffmpeg N-72383-g7206b94, ffprobe N-72383-g7206b94, rtmpdump 2.4
[debug] Proxy map: {}
[cmt.com] playlist: Downloading webpage
ERROR: Unable to extract mgid; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpaa64pv68\build\youtube_dl\YoutubeDL.py", line 694, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpaa64pv68\build\youtube_dl\extractor\common.py", line 355, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpaa64pv68\build\youtube_dl\extractor\mtv.py", line 230, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpaa64pv68\build\youtube_dl\extractor\mtv.py", line 224, in _extract_mgid
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpaa64pv68\build\youtube_dl\extractor\common.py", line 658, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract mgid; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://www.cmt.com/shows/dallas-cowboys-cheerleaders/dallas-cowboys-cheerleaders-making-the-team-ep-1106-dance-intervention/1740045/playlist/#id=1740045

Description of your issue, suggested solution and other information
It would appear that CMT has changed their mediagenerator format

Thanks for the report. CMT.com will be fixed in the next version.

Thanks, @yan12125 !