Regression: profit simulator reports zero value when logging

Initial: 0.010 BTC, 0.000 ETC
git checkout stable:
2016-12-07 14:10:00: Profit simulator got advice to short       0.010 BTC <= 0.000 ETC
2016-12-07 14:32:00: Profit simulator got advice to long        0.010 BTC => 9.562 ETC
                                                                ^^^^^

git checkout develop:
2016-12-07 17:10:00: Profit simulator got advice to short       0.010 BTC <= 0.000 ETC
2016-12-07 17:32:00: Profit simulator got advice to long        0.000 BTC => 9.523 ETC
                                                                ^^^^^

From value is always zero in both directions.

darn.. I just wrote a comment about how old that module is and how bad it needs refactoring..
Nice find, I think it only displays wrong numbers, but I'll recheck.

From value is always zero in both directions.

What do you mean? Isn't the behaviour in develop how it should behave?

It only displays wrong numbers.
It depends.
If was expected "all assets (now 0) converted to currency (now Y), then it is ok    <- in develop
If was expected "assets (was X) converted to currency (now Y), then it is not     <- in stable
Did you change you preferences?
The module might be old, but when I change something I try do not break what worked. Maybe you have another idea. Sorry, I think I should not bother you anymore.

Sorry, I think I should not bother you anymore.

You found a bug, I am happy that you reported it (but not happy that there was a bug, my fault).

If was expected "all assets (now 0) converted to currency (now Y), then it is ok <- in develop
If was expected "assets (was X) converted to currency (now Y), then it is not <- in stable
Did you change you preferences?

It is supposed to display how it now displays in develop, but that means that in stable it is wrong. I'll fix this asap!

I have rewritten the profitSimulator (now called paperTrader) and I've considered this 0 logging expected behaviour. If you still want to see this fixed reply here and I'll re-open.


Jurst "Sized arrays are only supported as class members."

The following is valid vJass:
library Shit
    globals
        private integer array s[12]
    endglobals
endlibrary

But in Jurst it is not. The problem can be side-stepped by enclosing every library's global block into a struct with static variables:
library Shit
    struct MyShit
        static integer array s[12]
    end
end

But clearly this is tedious and not valuable.

I think the vJass code would be equivalent without the size, except for the fact that there is a .size member for the array. I think the array size is only relevant in vJass, when the size is > 8190. So is this ticket a request to have big arrays or what should be the purpose of this?
Btw: It is a bug that you can give the size for static array members. The behaviour should be the same as for global variables.

I think I might not fully understand you.
It was my understanding that pre-defining array sizes in jass caused them to have upper limits, as in:
local integer array f[12]
f[50] = 51
would break something. Am I wrong?
I am not asking for large arrays, just asking that jurst equivalent of valid vJass is equally valid.
I think that integer array f[12] is valuable in either case - it describes that the developer intends the array to be fixed size, which has implications on testing etc.

Why do you make wild assumptions when you can test it faster than writing the comment?
The vjass manual doesn't mention anything about checking the size on set/get, it simply allows for larger arrays and the use of a .size member.
Also, vjass doesn't support local, sized arrays.
At least the manual says so.

http://www.wc3c.net/vexorian/jasshelpermanual.html#storarray

@Frotty thanks for the response.

Why do you make wild assumptions when you can test it faster than writing the comment?

I tend to guess that I'm correct with overly high confidence - it's a personality flaw, I apologize.
I couldn't have tested it faster than this comment though (even compensating for both of your time) as I don't develop wc3 stuff on my primary work environment.

The vjass manual doesn't mention anything about checking the size on set/get, it simply allows for larger arrays and the use of a .size member.

My previous comment doesn't say anything about vJass - I actually thought sized arrays were a feature of plain jass. Actually, I'm still not convinced otherwise.

Also, vjass doesn't support local, sized arrays.  \ At least the manual says so.

Can you show me where it says that? The link you provided seems a bit ambiguous. It doesn't seem like a flaw at all that local sized arrays are allowed.
As far as I can tell, sized arrays are perfectly valid in vjass.

Seriously coke monkey, are you on coke?
Normal Jass doesn't support any sizing.
How is my link ambiguous??
The first word in the paragraph is "GLOBAL".
As far as I can tell, all you're saying is invalid, therefore I'm closing this ticket until you have done some research.

You need to re-open this, or I will make a new issue. If you're not interested in supporting backwards compatibility with vJass in this instance, fair enough, but right now you're just being a hot head. (and an asshole)
The section you've sent me says "Sized Arrays", not "Global Sized Arrays". The sentence that follows is poor english and says:

Global arrays might sometimes require more index space, jasshelper introduces syntax for sized arrays, it serves two purposes: It will allow you to request more space, and it also allows you to place a .size field on global arrays.

From my understanding:

The first clause introduces the problem (it would be unusual that local arrays require more index space)
The second clause explains the solution (jasshelper supports sized arrays - nothing about global being a requirement)
The final clause explains an additional supporting feature.

And, regardless of all this discussion about arrays in jass vs vjass, it's all irrelevant minutiae:

vJass supports sized arrays in globals and locals (and I'm not even asking for locals!)
Jurst does not.

Nah bro. Provide working vjass codes with compiled code then we talk.

@peq can you keep your dog on a leash?

@frotty here you go:
Seamless sized arrays for big and small sizes - the vJass appears to the user as equivalent, but the compiler only generates getters and setters for the large ones:
http://peeeq.de/code.php?id=9043
And the generated code with getters and setters. Observe that accessing data in the else branch of the getters and setters actually writes to an index rather than throwing an error:
http://peeeq.de/code.php?id=9044
And note also that I was mistaken about local sized arrays. My recollection was being polluted by the valid, but unrelated code:
struct braap
    integer array sized[10]
endstruct

Sorry that you have zero experience in ticket systems coke, it really shows your polluted an arrogant way of being.
The ticket creator has to do something called specification.
Look it up.
I blocked you now and won't respond anymore, cya.

It is not a goal of Jurst to be 100% vJass compatible. The aim is more like this:
If there is a feature which is both in vJass and in Wurst, then Jurst should support the vJass Syntax  to make porting code easier.
I suggest you make a new ticket for a feature request of sized global arrays if you want this feature, and in there also suggest whether there should be bound checks and so on. Then we have a basis for discussion.
However, I don't see so many use cases for really big arrays, so I think it would be a low priority feature. You can give use cases in your new ticket, to convince me otherwise.

@Frotty I'm sorry you feel that way.
@peq Okay, I've tried to provide more context this time. In my opinion, syntax errors as a result of extracting vJass to Jurst should be treated as bugs and handled on a case-by-case basis, but I think you're right that presenting this as a feature request is also valid.

There is no such feature as "extracting vJass to Jurst", there is only a feature to extract custom scripts from a map file. It is completely independent from the used language.

Aha! That explains the confusion. I guess I just got lucky that much of my code was valid Jurst.
So is "jurstifying" extracted code something we're actively against?

Well, it would be a different feature and much more complicated. At least if you want it to work correctly. It would basically require to reimplement vJass with all its bugs and glitches in order to get a vJass->Jurst compiler.
Of course it would be possible to work with heuristics which work 90% correctly, but I think that would be more pain to use than the current porting process.

Of course it would be possible to work with heuristics which work 90% correctly, but I think that would be more pain to use than the current porting process.

Well, rather than following heuristics, it would be nice to just support some mainline features.
The bugs/features I've been raising about Jurst are really only related to translating code.
I don't think anyone writes Jurst from scratch. This eclipse feature is really a great tool, and for me it's the main use for Jurst in general.


Example with regex in path

Related to https://github.com/ReactTraining/react-router/issues/391 and this example https://github.com/ReactTraining/react-router/issues/391#issuecomment-294237556

Since this example will show up on the site as-is, do you mind adding some comments to the code to better explain this?

That works for me. Thanks!


base AMI is broken

For two months now.
https://ci.openshift.redhat.com/jenkins/view/AMIs/job/ami_build_origin_int_rhel_base/473/consoleFull#161232730158b6e51eb7608a5981914356
@stevekuznetsov seems like the docker registry is not built correctly for the integration test?
cc: @dmage @legionus

That's a new failure -- the bigger issue has been the Idling thing with no network plugin that Ben was looking into. There's a PR open to Origin to fix that.


fix: xhr.withCredentials is initially false

According to the XMLHttpRequest2 spec,
xhr.withCredentials should be initially false. http-browserify sets this
flag to true by default which disobeys the spec. This leads to browser errors when
making CORS requests to domains that have wildcards in their
Access-Control-Allow-Origin header.
http-browserify should attempt to follow the spec by default. In this case,
that means setting withCredentails to false initially, and then allowing
the user to override that in the passing in params.
Maybe it is possible to auto-detect when user credentials
are being sent and then set the withCredentials flag from there.
Somewhat related to #35 (the committer there expressed concern about
withCredentials being true when unintialzed as well).

similar to #90


adding the concatenated bufferData to the emit event

I needed this because i have to parse a post with a mix of encodings.

Can you share a test case where strings are not being decoded properly for you?

Hi.
Sry about the late reply. We use this library to decode some stuff that comes from sendgrid.
They post a multipart request with varying encoding.  And with it a list telling the receiver what encoding each field has.
Here is a simplified ruby-script showing the case. Take note of the text field and the corresponding charset field.
RestClient.post 'myexample.com/',
{
from: "My From Name",
to: to,
html: "<div dir="ltr">This is a testCheers\n",
text: "This is a _test\r\n\r\nCheers åååååååååå ".encode("ISO-8859-15"),
senderIp: "<IP_ADDRESS>",
envelope: "{"to":["okok<EMAIL_ADDRESS>attachments: "0",
subject: "Hi new version 2000",
charsets: "{"to":"UTF-8","html":"UTF-8","subject":"UTF-8","from":"UTF-8","text":"ISO-8859-15"}",
SPF: "pass",
multipart: true
}

The strings emitted are already binary/latin1 strings, so there is no data lost in a conversion anywhere. If you need a Buffer from that, you can simply do Buffer.from(str, 'binary').


[Microsoft.Insights/dataCollectionRules]: kind "All" not available via Bicep, but available via azure portal

Resource Type
Microsoft.Insights/dataCollectionRules
Api Version
All available versions tested
Issue Type
Missing property(s)
Other Notes
Testing some Data Collection Rules, the property "kind: 'All'" is not Available using Bicep. Documentation says it could either be "Windows" or "Linux" https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/datacollectionrules?pivots=deployment-language-bicep.
Error output says:   "message": "'Kind' must have one of the allowed values: Direct,Linux,Windows,WorkspaceTransforms,AgentDirectToStore,AgentSettings
From portal we could choose "platformType" with options "Windows", "Linux" or "All". But the property platformType does not exist in bicep. Exporting a portal made DCR with Kind 'All' does not show property "kind" or "platformType"
tested alle published API's, same result.
Bicep Repro
No response
Confirm

[X] I have read the troubleshooting guide and looked for duplicates.

found the way to set platformType to All. Please update documentation regarding this option.


fix(features): override parts not shown when editing and view schedule

:tada: This PR is included in version 2.24.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Test issue: only for demonstration

Please ignore. This will be closed soon.
https://forum.snapcraft.io/raw/7818/1

I'm really interested in taking on this task. I hope it will take me 10 minutes.

Hey I'm interested.


Not working with aws-sdk-core 3.0

We need to install both aws-sdk-dynamodb and aws-sdk-s3 where s3 particulary requires aws-sdk-core version  to be ~> 3.0 however dynamoid v2 requires the aws-sdkcore to be ~> 2
Also, if we just do gem install dynamoid it install an old version ~0.7. You should update the default version to either the most recent or most stable.

gem install dynamoid installs ver 0.7 which doesn't have any conflict however that version is not even listed here - https://rubygems.org/gems/dynamoid

There are a lot of changes on the master branch that are unreleased.
The next release should be soon, perhaps within the next month or so.
The next release will still be on aws-sdk-core v2.
There are open PRs to upgrade Dynamoid to aws-sdk-core v3, but none of them are complete.  If you would like to help us with testing, or work on any open issues to move us toward a release faster, it is appreciated.
The release after the next release, will be a major release version upgrade, and will include breaking changes, with aws-sdk-core v3 compatibility.

Done https://github.com/Dynamoid/Dynamoid/pull/267


Add an option to sqlmesh plan to use rendered model queries for diffing

This should help investigate issues which occur due to non-deterministic nature of some macros which result in unexpected creation of new model snapshots.

Should we automatically diff the rendered models if there is no diff between the raw models? And say something like raw models match, showing rendered diff.

@VaggelisD this seems pretty easy.
we need to add an option to sqlmesh plan
in render_definition.py, we need the option to propagate to call render_query() and render_pre/post_statements


can not run in ObjC

CocoaPods * pod 'FloatingPanel','~>2.0.0-beta.1'. or pod FloatingPanelObjC support

iOS version(s) 13.0
Xcode version 11.5

use. use_frameworks! fix this issue .


set up https using cloudflare

and forwarding for act.vegfest.org

and forwarding for act.vegfest.org

[ ] be sure to search the entire project for any links to http pages

[ ] be sure to search the entire project for any links to http pages

can't set it up for a sub domain. so instead of act.vegfest.org I'm trying it with vegfest.org

set this in motion, it's propogating. I hope it doesn't break email and other subdomains

solved by 57d2a1e


no batch run when using openai's format for calling.

I just use this command to start the server
CUDA_VISIBLE_DEVICES=0 python -m sglang.launch_server --model-path LLMs/Qwen-14B-Chat --port 30000 --trust-remote-code --stream-interval 1 --enable-flashinfer --schedule-conservativeness 50
and using the following code to test the concurrent capability.
It can only generate code with ~10tokens/s whereas the vllm can be ~30tokens/s. it seems the call method does not support batch inferencing. the logs show as below:

there is always 1 runnning_req.
The question is should we do it myself to support the batch inferencing when API calling or is something wrong with my setup?
BTW, I also tried the batching example from the README, and it works fine and running faster then I expected!!!
Thank you so much ahead.
SCRIPTS
def run(ds):
    winner = "a" if "_" not in ds["winner"] else ds["winner"].split("_")[1]
    conversation = ds[f"conversation_{winner}"]

    st = time.time()
    answer = []
    for i in range(ds["turn"]):
        current_msg_start_time = time.time()
        query = conversation[i * 2]
        history = conversation[: i * 2]
        messages = history + [query]
        assert query["role"] == "user"
        resp = requests.post(
            "http://localhost:30000/v1/chat/completions",
            data=json.dumps(
                {
                    "messages": messages,
                    "stream": True,
                    "temperature": 0,
                    "stop": [
                        "<|endoftext|>", "<|im_end|>",
                    ],
                    "model": "Qwen-14B-Chat",
                    "max_tokens": "2048",
                }
            ),
            headers={"accept": "application/json"},
            timeout=600,
            stream=True,
        )

        client = sseclient.SSEClient(resp)
        data = ""
        for i, event in enumerate(client.events()):
            if event.data != "[DONE]":
                if i == 1:
                    first_packet_time = time.time() - current_msg_start_time
                data = event.data
        data = json.loads(data)

if __name__ == "__main__":
    for N in [5, ]:
        user_pool = []
        for i in range(N):
            th = Thread(target=run, args=(ds[random.randint(0, 32999)],))
            user_pool.append(th)
        for t in user_pool:
            t.start()
        for t in user_pool:
            t.join()

Hello! Have you solved this problem? This problem also occurred when I tested multiple concurrency. runnning_req always 1, I feel that there is no concurrency.

Any updates on this issue?

you can check this issue #1947


Errors and SIGTERM After Updating to 0.4.50

After updating to 0.4.50, Homebridge suddenly stopped functioning, was seamlessly working prior. Ran debug in terminal and log produced these findings. First time to encounter them, no clue what to do being a relative beginner. Highlighted these errors, help would be much appreciated. @nfarina @ebaauw
Homebridge: 0.4.50
Node Version: 10.16.0
NPM Version: 6.4.1
OS: Raspbian
Description: Raspbian GNU/Linux 9.9 (stretch)
Release: 9.9
Codename: stretch
Errors:
1. Homebridge-Apple TV: NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing.
[6/10/2019, 10:21:21 AM] ====================
[6/10/2019, 10:21:21 AM] ERROR LOADING PLUGIN homebridge-apple-tv:
[6/10/2019, 10:21:21 AM] Error: The module '/usr/lib/node_modules/homebridge-apple-tv/node_modules/sodium/build/Release/sodium.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:805:18)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-apple-tv/node_modules/sodium/lib/sodium.js:16:15)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
[6/10/2019, 10:21:21 AM] ====================

2. Homebridge-DACP: NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing.
[6/10/2019, 10:21:23 AM] ====================
[6/10/2019, 10:21:23 AM] ERROR LOADING PLUGIN homebridge-dacp:
[6/10/2019, 10:21:23 AM] Error: The module '/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/build/Release/dns_sd_bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:805:18)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/lib/dns_sd.js:24:20)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/lib/mdns.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/src/dacp/DacpBrowser.js:6:14)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/src/index.js:8:21)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:72:23)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:153:14)
    at Array.forEach (<anonymous>:null:null)
    at Server._loadPlugins (/usr/lib/node_modules/homebridge/lib/server.js:145:22)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:24)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:32:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[6/10/2019, 10:21:23 AM] ====================

3. Homebridge-ZP: Cannot find module 'hblib'
[6/10/2019, 10:21:29 AM] ====================
[6/10/2019, 10:21:29 AM] ERROR LOADING PLUGIN homebridge-zp:
[6/10/2019, 10:21:29 AM] Error: Cannot find module 'hblib'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-zp/lib/ZpPlatform.js:12:23)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-zp/index.js:8:26)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:72:23)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:153:14)
    at Array.forEach (<anonymous>:null:null)
    at Server._loadPlugins (/usr/lib/node_modules/homebridge/lib/server.js:145:22)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:24)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:32:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[6/10/2019, 10:21:29 AM] ====================

SIGTERM: Cannot find module '../build/Debug/pty.node'
[6/10/2019, 10:21:29 AM] Got SIGTERM, shutting down Homebridge...
[6/10/2019, 10:21:30 AM] [Config] Error: Cannot find module '../build/Debug/pty.node'
[6/10/2019, 10:21:30 AM] [Config] [node-pty] Node.js v10.16.0
[6/10/2019, 10:21:30 AM] [Config] [node-pty] Failed to load node-pty module
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This could be because the installation of this plugin did not complete successfully or you may have recently upgraded Node.js to a new major version and have not reinstalled or rebuilt this plugin.
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This can usually be fixed by uninstalling and reinstalling this plugin (exact command may vary based on your platform and setup):
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm uninstall -g homebridge-config-ui-x
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm install -g --unsafe-perm homebridge-config-ui-x

Complete Debug Results
pi@raspberrypi:~ $ DEBUG=* homebridge -D
[6/10/2019, 10:21:17 AM] Loaded config.json with 0 accessories and 10 platforms.
[6/10/2019, 10:21:17 AM] ---
[6/10/2019, 10:21:20 AM] Loaded plugin: homebridge-alexa
[6/10/2019, 10:21:20 AM] Registering platform 'homebridge-alexa.Alexa'
[6/10/2019, 10:21:20 AM] ---
[6/10/2019, 10:21:20 AM] Loaded plugin: homebridge-ambiclimate
[6/10/2019, 10:21:20 AM] Registering accessory 'homebridge-ambiclimate.AmbiClimate'
[6/10/2019, 10:21:20 AM] ---
[6/10/2019, 10:21:21 AM] Loaded plugin: homebridge-ambiclimate-thermostat
[6/10/2019, 10:21:21 AM] Registering accessory 'homebridge-ambiclimate-thermostat.AmbiClimateThermostat'
[6/10/2019, 10:21:21 AM] ---

[6/10/2019, 10:21:21 AM] ====================
[6/10/2019, 10:21:21 AM] ERROR LOADING PLUGIN homebridge-apple-tv:
[6/10/2019, 10:21:21 AM] Error: The module '/usr/lib/node_modules/homebridge-apple-tv/node_modules/sodium/build/Release/sodium.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:805:18)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-apple-tv/node_modules/sodium/lib/sodium.js:16:15)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
[6/10/2019, 10:21:21 AM] ====================

[6/10/2019, 10:21:21 AM] Loaded plugin: homebridge-automation-switches
[6/10/2019, 10:21:21 AM] Registering platform 'homebridge-switches.AutomationSwitches'
[6/10/2019, 10:21:21 AM] ---
[6/10/2019, 10:21:22 AM] Loaded plugin: homebridge-broadlink-rm
[6/10/2019, 10:21:22 AM] Registering platform 'homebridge-broadlink-rm.BroadlinkRM'
[6/10/2019, 10:21:22 AM] ---
[6/10/2019, 10:21:22 AM] Loaded plugin: homebridge-config-ui-x
[6/10/2019, 10:21:22 AM] Registering platform 'homebridge-config-ui-x.config'
[6/10/2019, 10:21:22 AM] ---

[6/10/2019, 10:21:23 AM] ====================
[6/10/2019, 10:21:23 AM] ERROR LOADING PLUGIN homebridge-dacp:
[6/10/2019, 10:21:23 AM] Error: The module '/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/build/Release/dns_sd_bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:805:18)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/lib/dns_sd.js:24:20)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/lib/mdns.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/src/dacp/DacpBrowser.js:6:14)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-dacp/src/index.js:8:21)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:72:23)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:153:14)
    at Array.forEach (<anonymous>:null:null)
    at Server._loadPlugins (/usr/lib/node_modules/homebridge/lib/server.js:145:22)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:24)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:32:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[6/10/2019, 10:21:23 AM] ====================

[6/10/2019, 10:21:23 AM] Loaded plugin: homebridge-dyson-link
homebridge API version: 2.4
[6/10/2019, 10:21:23 AM] Registering platform 'homebridge-dyson-link.DysonPlatform'
[6/10/2019, 10:21:23 AM] ---
[6/10/2019, 10:21:23 AM] Loaded plugin: homebridge-homesung
[6/10/2019, 10:21:24 AM] Registering platform 'homebridge-homesung.SamsungTV'
[6/10/2019, 10:21:24 AM] ---
[6/10/2019, 10:21:25 AM] Loaded plugin: homebridge-hue
[6/10/2019, 10:21:25 AM] Registering platform 'homebridge-hue.Hue'
[6/10/2019, 10:21:25 AM] ---
[6/10/2019, 10:21:26 AM] Loaded plugin: homebridge-mqttthing
[6/10/2019, 10:21:26 AM] Registering accessory 'homebridge-mqttthing.mqttthing'
[6/10/2019, 10:21:26 AM] ---
[6/10/2019, 10:21:26 AM] Loaded plugin: homebridge-music
[6/10/2019, 10:21:26 AM] Registering platform 'homebridge-music.Music'
[6/10/2019, 10:21:26 AM] ---
[6/10/2019, 10:21:26 AM] Loaded plugin: homebridge-people
[6/10/2019, 10:21:26 AM] Registering platform 'homebridge-people.People'
[6/10/2019, 10:21:26 AM] Registering accessory 'homebridge-people.PeopleAccessory'
[6/10/2019, 10:21:26 AM] Registering accessory 'homebridge-people.PeopleAllAccessory'
[6/10/2019, 10:21:26 AM] ---
[6/10/2019, 10:21:26 AM] Loaded plugin: homebridge-platform-ring-video-doorbell
[6/10/2019, 10:21:26 AM] Registering platform 'homebridge-platform-ring-video-doorbell.ring-video-doorbell'
[6/10/2019, 10:21:26 AM] ---
[6/10/2019, 10:21:26 AM] Loaded plugin: homebridge-plex-sensors
[6/10/2019, 10:21:26 AM] Registering platform 'homebridge-plex-sensors.Plex'
[6/10/2019, 10:21:26 AM] ---
[6/10/2019, 10:21:27 AM] Loaded plugin: homebridge-samsung-tizen
[6/10/2019, 10:21:27 AM] Registering platform 'homebridge-samsung-tizen.SamsungTizen'
[6/10/2019, 10:21:27 AM] ---
[6/10/2019, 10:21:28 AM] Loaded plugin: homebridge-sonos-schmittx
[6/10/2019, 10:21:28 AM] Registering accessory 'homebridge-sonos.Sonos'
[6/10/2019, 10:21:28 AM] ---
[6/10/2019, 10:21:28 AM] Loaded plugin: homebridge-spotify
[6/10/2019, 10:21:28 AM] Registering accessory 'homebridge-spotify.Spotify'
[6/10/2019, 10:21:28 AM] ---
[6/10/2019, 10:21:28 AM] Loaded plugin: homebridge-synology
[6/10/2019, 10:21:28 AM] Registering accessory 'homebridge-synology.Synology'
[6/10/2019, 10:21:28 AM] ---
[6/10/2019, 10:21:29 AM] Loaded plugin: homebridge-weather-plus
[6/10/2019, 10:21:29 AM] Registering platform 'homebridge-weather-plus.WeatherPlus'
[6/10/2019, 10:21:29 AM] ---
[6/10/2019, 10:21:29 AM] Loaded plugin: homebridge-yeelight-platform
[6/10/2019, 10:21:29 AM] Registering platform 'homebridge-yeelight-platform.Yeelight-Platform'
[6/10/2019, 10:21:29 AM] ---
[6/10/2019, 10:21:29 AM] Loaded plugin: homebridge-yeelight-wifi
[6/10/2019, 10:21:29 AM] Registering platform 'homebridge-yeelight.yeelight'
[6/10/2019, 10:21:29 AM] ---

[6/10/2019, 10:21:29 AM] ====================
[6/10/2019, 10:21:29 AM] ERROR LOADING PLUGIN homebridge-zp:
[6/10/2019, 10:21:29 AM] Error: Cannot find module 'hblib'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-zp/lib/ZpPlatform.js:12:23)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-zp/index.js:8:26)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/coffeescript/lib/coffee-script/register.js:45:36)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Plugin.load (/usr/lib/node_modules/homebridge/lib/plugin.js:72:23)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:153:14)
    at Array.forEach (<anonymous>:null:null)
    at Server._loadPlugins (/usr/lib/node_modules/homebridge/lib/server.js:145:22)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:24)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:32:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[6/10/2019, 10:21:29 AM] ====================

[6/10/2019, 10:21:29 AM] Loading 10 platforms...
[6/10/2019, 10:21:29 AM] [Config] Initializing config platform...
[6/10/2019, 10:21:29 AM] [Config] Spawning homebridge-config-ui-x with PID 27849
[6/10/2019, 10:21:29 AM] [homebridge-plex-sensors.Plex] Initializing homebridge-plex-sensors.Plex platform...
[6/10/2019, 10:21:29 AM] Error: The requested platform 'ZP' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

[6/10/2019, 10:21:29 AM] [homebridge-plex-sensors.Plex] Homebridge Plex Sensors listening for webhooks on: http://<homebridge ip>:22987

[6/10/2019, 10:21:29 AM] Got SIGTERM, shutting down Homebridge...
[6/10/2019, 10:21:30 AM] [Config] Error: Cannot find module '../build/Debug/pty.node'
[6/10/2019, 10:21:30 AM] [Config] [node-pty] Node.js v10.16.0
[6/10/2019, 10:21:30 AM] [Config] [node-pty] Failed to load node-pty module
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This could be because the installation of this plugin did not complete successfully or you may have recently upgraded Node.js to a new major version and have not reinstalled or rebuilt this plugin.
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This can usually be fixed by uninstalling and reinstalling this plugin (exact command may vary based on your platform and setup):
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm uninstall -g homebridge-config-ui-x
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm install -g --unsafe-perm homebridge-config-ui-x

[6/10/2019, 10:21:23 AM] Error: The module '/usr/lib/node_modules/homebridge-dacp/node_modules/mdns/build/Release/dns_sd_bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using npm rebuild or npm install).

[6/10/2019, 10:21:30 AM] [Config] [node-pty] Failed to load node-pty module
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This could be because the installation of this plugin did not complete successfully or you may have recently upgraded Node.js to a new major version and have not reinstalled or rebuilt this plugin.
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This can usually be fixed by uninstalling and reinstalling this plugin (exact command may vary based on your platform and setup):
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm uninstall -g homebridge-config-ui-x
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm install -g --unsafe-perm homebridge-config-ui-x[6/10/2019, 10:21:30 AM] [Config] [node-pty] Failed to load node-pty module
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This could be because the installation of this plugin did not complete successfully or you may have recently upgraded Node.js to a new major version and have not reinstalled or rebuilt this plugin.
[6/10/2019, 10:21:30 AM] [Config] [node-pty] This can usually be fixed by uninstalling and reinstalling this plugin (exact command may vary based on your platform and setup):
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm uninstall -g homebridge-config-ui-x
[6/10/2019, 10:21:30 AM] [Config] [node-pty] sudo npm install -g --unsafe-perm homebridge-config-ui-x

Did you upgrade NodeJS as well?  Plugins using C modules need to be recompiled after upgrading to another major version of node.  You might need to un-install the module before re-installing it, to force compilation.

[6/10/2019, 10:21:29 AM] ERROR LOADING PLUGIN homebridge-zp:
[6/10/2019, 10:21:29 AM] Error: Cannot find module 'hblib'

I was messing up this weekend, sorry.  Please install the latest version of homebridge-zp by sudo npm -g i homebridge-lib homebridge-zp.

Thank you for the quick response, @ebaauw!

"Did you upgrade NodeJS as well? Plugins using C modules need to be recompiled after upgrading to another major version of node. You might need to un-install the module before re-installing it, to force compilation."

How exactly do you go about that? Forgive me, quite unfamiliar as a beginner.

I was messing up this weekend, sorry. Please install the latest version of homebridge-zp by:
sudo npm -g i homebridge-lib homebridge-zp

This is the output upon trying to do so:
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

How exactly do you go about that?

Normally by:
sudo npm -g un homebridge-...
sudo npm -g i homebridge-... --unsafe-perm

sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

Never seen that one before.  Looks like your Raspbian installation is broken.  You’re not running in a docker container or something, are you?  What does ls -a /usr/bin/sudo show?  And uname -a?

Says the same thing whenever I try
sudo npm -g un homebridge
sudo npm install -g --unsafe-perm homebridge

sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

ls -a /usr/bin/sudo

/usr/bin/sudo

uname -a

Linux raspberrypi 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux

Sorry, I meant ls -l /usr/bin/sudo.  Haven’t had my first coffee yet ;-(

Haha no worries
ls -l /usr/bin/sudo
-rwxrwxrwx 1 root root 135376 Jun  5  2017 /usr/bin/sudo

Linux raspberrypi 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux

That's looking good, latest version of Raspbian Stretch.  Same version as I have.

-rwxrwxrwx 1 root root 135376 Jun 5 2017 /usr/bin/sudo

Not good, it should be:
-rwsr-xr-x 1 root root 135376 Jun  5  2017 /usr/bin/sudo

I have no idea how this could have changed.  Can you double-check the checksum to make sure the file hasn't been compromised:
$ md5sum /usr/bin/sudo
e6a11c46bed327e58f21afbe5b0cdb1e  /usr/bin/sudo

And the other SUID files in /usr/bin?
$ find /usr/bin -perm /4000 -exec ls -l {} \;
-rwsr-xr-x 1 root root 40324 May 17  2017 /usr/bin/chfn
-rwsr-xr-x 1 root root 33348 Mar 13 14:41 /usr/bin/gpio
-rwsr-xr-x 1 root root 45648 May 17  2017 /usr/bin/passwd
-rwsr-xr-x 1 root root 30900 May 17  2017 /usr/bin/newgrp
-rwsr-xr-x 1 root root 135376 Jun  5  2017 /usr/bin/sudo
-rwsr-xr-x 1 root root 57820 May 17  2017 /usr/bin/gpasswd
-rwsr-xr-x 1 root root 18288 Dec  6  2018 /usr/bin/pkexec
-rwsr-xr-x 1 root root 1423400 Mar 13 17:50 /usr/bin/Xvnc
-rwsr-xr-x 1 root root 31452 May 17  2017 /usr/bin/chsh
-rwsr-xr-x 1 root root 1423216 Mar 13 17:50 /usr/bin/vncserver-x11

I have no idea how this could have changed. Can you double-check the checksum to make sure the file hasn't been compromised:
$ md5sum /usr/bin/sudo
e6a11c46bed327e58f21afbe5b0cdb1e  /usr/bin/sudo

Entering $ md5sum /usr/bin/sudo gives me the same output e6a11c46bed327e58f21afbe5b0cdb1e  /usr/bin/sudo

And the other SUID files in /usr/bin?

I don't quite know how or what you mean by this.

I've done some searching regarding sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set and one possible cause is running chmod -R 777  on root which I did last night?
Would and how could I reverse this?

one possible cause is running chmod -R 777 on root which I did last night

That would mess things up brilliantly, indeed.  That has changed the permissions of every folder and file in the system.

Would I be able to/how could I reverse this?

You would have to restore the permissions of each individual folder and file in the system.  With over ~290,000 of these, that would take forever, even if you would have another Raspberry to check what the permissions should be.
Restore a backup.  Or re-install Raspbian.


highliting breaks 'if' on command line

Type 'if ['
This is the output:
% if [
_zsh_highlight_buffer_modified:2: bad pattern: if [
% if [
%

Not reproducible. Must have been fixed sometime in the last four years.


Rename project

This project will be renamed to helx-search to be published on the PyPI repo with a more descriptive name. We will also organize it into a namespace repository, with "helx" as the parent namespace (other helx projects will subsequently be moved under this namespace).
Whereas currently users access it as
from dug import ...

The namespace will change to
from helx.search import ...

Likewise CLI tooling will change, from
dug crawl ...
dug search ...

to
helx crawl ...
helx search ...

Thats also entails archiving this repo and migrating the code to a new one

Marking this task as closed, since the install from source is easy and the Docker image is what we're really interested in anyway


Determine which CI provider to use

Description of Problem
See this comment in #6 for more context. We're currently using GitHub CI. I'm not sure I want to continue using that because of being less familiar with that. However, I also don't want to use Travis because "everyone does that."
I'd like to discuss this further as to which one we should use and why.

No qualms with giving travis another shot. This is the .travis.yml that I was attempting to use earlier:
dist: bionic
language: node_js
node_js: 12
install:
  - npm install
script:
  - npm run build

Based on the file I use for my learning reference, maybe this would suffice?
dist: bionic
language: minimal
  # Use `nvm` to install latest version of NodeJS

# Unless we specify "sudo: false", build runs in VM, not container

# Limit the number of commits it will clone
git:
  depth: 3

# Only do CI for the default branch
branches:
  only:
  - master

before_install:
  - nvm install node
  - npm i -g npm

install:
  - npm i

script:
  - npm run build

cache:
  directories:
    - .spago
    - node_modules


Please update the notification payload to support the latest iOS

Context
We have successfully installed react-native-mixpanel on our project, it works perfectly for sending events and displaying push notifications. We also have FCM push notifications installed and running perfectly for either displaying or handling the push notification payload in this same project.
We are using the versions below:
"react": "16.10.2",
"react-native": "0.61.5",
"react-native-mixpanel": "^1.2.0",
"@react-native-firebase/messaging": "^7.2.1",

This is how our AppDelegate is looking with all its push notification listeners:
#import <React/RCTBridgeDelegate.h>
#import <UIKit/UIKit.h>
#import <UserNotifications/UNUserNotificationCenter.h>

@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, UNUserNotificationCenterDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

#import "AppDelegate.h"
#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
#import <Firebase.h>
#import "RNSplashScreen.h"
#import <UserNotifications/UserNotifications.h>
#import <RNCPushNotificationIOS.h>
#import <Mixpanel/Mixpanel.h>

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [FIRApp configure];
  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"vega"
                                            initialProperties:nil];
  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

  [RNSplashScreen show];

  [Mixpanel sharedInstance].enableLogging = YES;

  UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];
  center.delegate = self;

  return YES;
}

-(void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler
{
   // Only listener called for Mixpanel pushes (apparently used only for displaying)
  completionHandler(UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionBadge);
}

- (void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings
{
   // Called only for FCM pushes
}

- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
   // Called only for FCM pushes
}

- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler
{
   // Called only for FCM pushes
}

- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
   // Called only for FCM pushes
}

- (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(void (^)(void))completionHandler
{
   // Called only for FCM pushes
}

- (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification
{
   // Called only for FCM pushes
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

@end

Issue
We need to be able to catch and read the Mixpanel notification payload when the app is either on foreground, background or closed. But apparently none of the iOS listeners catch the notification payload UNLESS we tap on it. So the notification is just displayed on device screen and that is all. On the other hand, the listeners work perfectly with our FCM push notifications WITHOUT needing to tap on them.
Below are the automatically generated Xcode logs we get when enabling [Mixpanel sharedInstance].enableLogging = YES;:

When receiving FCM push notification either on Foreground or Background (without needing to tap on it):

2020-07-30 11:25:22.390205-0300 AppName[7755:2802652] [Mixpanel] <Info>: <Mixpanel: 0x102521520 - Token: c1fcf34573e2ac7f62b4d63fa7c7a94a> tracking push payload {
    aps =     {
        alert =         {
            body = “message body”;
            title = “message “title;
        };
        "content-available" = 1;
    };
    "gcm.message_id" =<PHONE_NUMBER>068077;
    "google.c.a.e" = 1;
}

When receiving Mixpanel push notification, but ONLY AFTER tapping on it:

2020-07-30 11:31:13.146485-0300 AppName[7765:2809203] [Mixpanel] <Info>: <Mixpanel: 0x1090093e0 - Token: c1fcf34573e2ac7f62b4d63fa7c7a94a> tracking push payload {
    aps =     {
        alert =         {
            body = “message “body;
            title = “message “title;
        };
        "mutable-content" = 1;
        sound = default;
    };
    mp =     {
        c = 5239768;
        "distinct_id" = "D24C66B1-F5BE-404E-8481-F625CB2052D8";
        m = 3586124;
        token = c1fcf34573e2ac7f62b4d63fa7c7a94a;
    };
}

Proposed solution
Looks like Mixpanel push notifications only allows for notification displaying, which means it probably does not contain the latest APNS headers that need to be sent to the device in order for the device to receive the payload. You can check Apple Documentation here: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns/
We had similar issue with FCM payload, and we solved it by using the block below including the contentAvailable and the correct apns-headers:
{
   "notification”:{
      "title":"Notification title",
      "body":"Notification body"
   },
   "apns":{
      "payload":{
         "aps":{
            "contentAvailable":true
         }
      },
      "headers":{
         "apns-push-type":"alert",
         "apns-priority":"5",
         "apns-topic": // your app bundle identifier
      }
   },
}

Could you please advise or update the notification payload to support the latest iOS?
Thanks!

Just discovered that adding a custom JSON for iOS (while creating the notification on Mixpanel Messages panel) like this solves this issue:

it's important to mention that we should not add commas at the end of the last value like we normally do in javascript. If we add that little comma Mixpanel will silently ignore the custom JSON content.

The app now successfully reacts to the push notification whenever it's running on Foreground or Background. But I still don't know how to make things work if the app is quit (not running).


Logging

As we continue to grow Daphne's code base, I think it's time to think about a good logging mechanism. To not invent that wheel for the 12345th time I strongly recommend introducing another external dependency and use a library for that. I've made a quick survey with my favorite search engine and came up with a blog that threatens to use Boost and this list of logging libraries where the highest ranking entry looks promising. sbdlog is under MIT license, seems to have quite a user base according to github fork/star score and an active development community. It's fast©, supports multiple sinks and can be integrated in header only or compiled form (can be built using cmake, which fits nicely to our environment).
Hoping for a fruitful and not too lengthy discussion ;-)

We are using spdlog internally in other larger C++ codebases since almost two years and liked it so far. Easy to use and quite flexible with many configuration parameters (e.g., sinks, threading, etc.). So overall recommendation from my side!

Thank you for your feedback @MarcusParadies.
I will give sbdlog a try and go forward with an initial integration to our code base. My thoughts about doing that:

Making a log facility available to all parts of the code
Support configuring the logger in our config file { verbosity levels, sinks }

After that initial functionality we will think about:

logging in a distributed setting
log configs for sub sections of DAPHNE ( e.g., configuring verbosity of compiler passes differently from local kernels or I/O etc)


Worked on Video Authentication and Empty text field then also moving …

…to next Screen
Please Verified and merged with the master.

Verified and merged with the master.


XGBoost wrappers parameters missing

Resolves #336 by adding full XGBoost params for GBM impl along with **kwargargument.
Resolves https://github.com/h2oai/h2o4gpu/issues/493 by setting n_estimators to 100 by default in RF impl.

TODO: Update R wrappers.

@terrytangyuan I have updated it to account for **kwargs in the R API.

@terrytangyuan Adjusted the R API to follow the Google R style guide.
@mdymczyk Yes, but I think we can add more on a case by case basis. I do not fully understand XGBoost in terms of Random Forest, but the impl is more "Random Forest like" in a sense. The main parameter I can see guiding a Random Forest type impl is num_parallel_tree,which is described here:
num_parallel_tree Experimental parameter. number of trees to grow per
round. Useful to test Random Forest through Xgboost (set colsample_bytree < 1,
subsample < 1 and round = 1) accordingly. Default is 1.

Also, here is a R code snippet from XGBoost's R documentation that describes how to run a RF like model:
## random forest-like model of 25 trees for binary classification:
set.seed(11)
bst <- xgboost(data = train$data, label = train$label, max_depth = 5,
nthread = 2, nrounds = 1, objective = "binary:logistic",
num_parallel_tree = 25, subsample = 0.6, colsample_bytree = 0.1)


Data discrepancy for row 170 in reporting dairy herds (timeline)

@julianasopko commented: "noting a discrepancy here in a previous count we seem to have omitted backyard producers but in this count we appear to have included them"
@JacqSauer commented: "I was doing some digging and I found a weekly report by the community for emerging and zoonotic diseases (CEZD) that has a weekly count of impacted dairy herds reported by the USDA. It might be a good source to check/validate our counts. Here's an example of a [report](file:///C:/Users/asjac/AppData/Local/Temp/MicrosoftEdgeDownloads/2dfb7e6f-70b9-4550-aa91-33025f5315ac/CEZD%20Weekly%20Intelligence%20Report%2017%20%E2%80%93%2023%20June%202024.pdf), other weekly intelligence reports can be found at https://cezd.ca/reports"
How should we go about this data discrepancy? Should we include backyard producers? Should we create a "data dictionary" that defines the types of herds we are including?

@jackie-powers do you feel comfortable closing this issue?

The team is not retrospectively reviewing and updating entries. Entries that are posted to the public are not changed/updated later on to reflect data reconciliation


feat: Compatible with python 312

I thought python 3.12 was already officially supported (see here). Is that not the case, @simjak?


Feature/#75: Improved unpublished node styling ensuring high-contrast visibility (Drupal 9-10)

This pull request relates to BOSA_0100-196 (JIRA issue) and contains styling updates improving the default Drupal behavior when a node is unpublished by ensuring high-contrast visibility.
This pull request will be merged with the 3.0.x (Drupal 9-10) branch.

I need to recreate a clean new branch for this issue from the latest update of the 3.0.x branch.


Added bower.json.

Added bower.json to enable developers to easily integrate OpenFB as a dependency using Bower.

+1

Implemented in 0.5


perf: preinitialize typeCheck RegExp

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: Performance improvement

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
After looking at the performance of one of my apps, I noticed, the function, that took the most time summed up was getType() , defined in [1] taking 200ms. I noticed the regular expression getting created for each call and measured again including the proposed improvement, which took the time down to 150ms. To make sure I changed it back to confirm and it again timed at 200ms.
[1]
https://github.com/vuejs/vue/blob/b07087deae060244fe5d9651b38dc5f1e79667a9/src/core/util/props.js#L182-L185

Maybe further improvements could be made by removing the regular expression completely and using standard string manipulation methods.

Is there anything else, that needs to be done before merging? @posva

@SebastianSpeitel You don't need to do anything else, thank you :)

I made this PR 2 months ago. Is there a reasons for this taking so long?

@SebastianSpeitel   cached it may be better ?
  const getType = cached(function getType (fn) {
    var match = fn && fn.toString().match(/^\s*function (\w+)/);
    return match ? match[1] : ''
  })

@SebastianSpeitel   cached it may be better ?
  const getType = cached(function getType (fn) {
    var match = fn && fn.toString().match(/^\s*function (\w+)/);
    return match ? match[1] : ''
  })

Both could be optimal.
Compile the regex only once and compute the type of each object only once.

but the fn.toString is a expense also, for every function  @SebastianSpeitel   sorry my later comment


Check if labels are added to PR

Fixes/Closes

Closes #
Description

This PR adds a check if one of bugfix, feature, documentation, performance, enhancement, maintenance is added to PR.
As in last time, we regularly forget to add such labels, which increases the time required to prepare the release.
References

Type of change

[x] Maintanence

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

If there are no objections raised here before the Eurasia community meeting (in ~7h) I think we'll merge it live during the meeting! 😂 🚀 I'm personally really excited about this one. 🙏


Feature #8: allow columns to be arbitrarily ordered, and Feature #20: use a builder pattern.

Feature #20
Use a builder pattern for table creation.
This proposed solution provides two improvements in the API.

The process of selecting a column for 'hiding' is streamlined into the construction process for the Table<T>.
Columns can be identified for hiding by property name rather than index.

var table = TableBuilder<DemoAnimals>
                .Initialize(animalData)
                .HideColumn("Name")
                .Build();

NOTE: Build() returns Table<T>.
Feature #8
Allow columns to be arbitrarily ordered
This solution was also integrated into the builder pattern. This allows for a very streamlined table construction process. Simply passing a preferred index and the name of the target Column allows for the position of the targetColumn and the Column occupying the destination index to be swapped.
var table = TableBuilder<DemoAnimals>
                .Initialize(animalData)
                .SetColumnIndex("IntCol", 0)
                .Build();

Example class
public class DemoAnimals
    {
        public string Species { get; set; }
        public string Color { get; set; }
        public string Name { get; set; }
        public int IntCol { get; set; }
    }

Default ordering of columns (based on relative property position).
+----------+-------+-------+--------+
| Species  | Color | Name  | IntCol |
+----------+-------+-------+--------+
| Cats     | Gray  | Joe   | 2      |
| Dogs     | Red   | Billy | 1      |
| Chickens | Green | Jill  | 3      |
+----------+-------+-------+--------+

New ordering of columns after IntCol was explicitly set to location with index of 0.
+--------+-------+-------+----------+
| IntCol | Color | Name  | Species  |
+--------+-------+-------+----------+
| 2      | Gray  | Joe   | Cats     |
| 1      | Red   | Billy | Dogs     |
| 3      | Green | Jill  | Chickens |
+--------+-------+-------+----------+

Chainable
Because these two features are part of the same builder class, they can be chained.
HideColumn(name) and SetColumnIndex(name, index) methods can be chained in a highly streamlined table creation process, for example:
var table = TableBuilder<DemoAnimals>
                .Initialize(animalData)
                .SetColumnIndex("IntCol", 0)
                .HideColumn("Name")
                .Build();

Hi @rahl0b10.
There's a lot to like here:

The builder syntax is really "fluent"
The ability to address columns by property name is loads better than their index
Being able to reorder columns is a huge win

That said, it's not quite there yet.
For me, the most fundamental concern is that the new functionality has been built into the new builder. This breaks the equivalence of the two APIs. What I like about the addition of the builder class is that it provides choice, but at the moment that choice is limited because the new features are only supported in one of the two APIs.
I don't think there's any fundamental reason why access via property names or column reordering couldn't be offered via the old-style syntax. Is there any way we could move it into the core and provide access to it via the builder class? In other words, I suppose I'm asking if we could simplify things by using the builder class as a wrapper around the core API?
Some other (more minor) feedback:

To me, the reordering behaviour should be more of an insert than a swap. So if I specify that the  column in 4th position should move to the 1st position, I would expect to see the column that has been in 1st position move to 2nd position, the one in 2nd position to move to 3rd, etc.
The test coverage of your new builder class seems (from my eyeballing) to be quite low.
I'm not sure how I feel about the addition of yet another type of test data class. In fact, I think we need to address this question in it's own issue. (So let's leave DemoAnimals in there for now.)

To reiterate, I think you're on to a winner here. We just need to iron out a few of the details. As ever, thanks for your contributions!
Tom
PS Are @geekmdio another of your accounts?

@tdwright - Thanks for all the feedback :) Those are great points, and I will implement in that way. It'll be quite a bit more work, so give me a bit of time.
As for the @geekmdio account, yes it's mine. I'm working on something proprietary under that account. It's all in it's infancy. It's showing up because OS X is doing something strange when I push. The push goes to the correct account, but under the wrong username no matter what I do with the local and global settings. I found out that if I push via HTTPS I get the desired behavior, my local git config is respected, and the correct account is credited with the push. Not a huge inconvenience, but still annoying.

Great stuff! And don't sweat it if it takes a while - we're doing this in our free time, remember? 😉
I'll leave this functionality to you, but I may do some stuff elsewhere, so be sure to merge the develop back into your repo from time to time.

Ha, ha. Yes, good point. In our free time. ;)
I'm a self-taught amateur (who works in an entirely different profession), so I don't get to work in a team environment. This is as close as I've been so far, so I may be over-eager at times.

Think we should probably close this one now.


Update empty modules page to point to repo

Currently if there are no modules we tell the user to open the modules folder and download and install some modules.  This should instead point to that -and- point to the module repo.  This page has not been updated since the module repo was added.

See #948 for some additional context.


[Bug] Model asana__task failed to build due to timezone-related function error.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
The asana__task failed to build due to a function error.
Relevant error log or model output
2022-06-27T16:08:09.021458Z: 16:08:09  Postgres adapter: Postgres error: function pg_catalog.date_diff("unknown", timestamp with time zone, timestamp without time zone) does not exist
HINT:  No function matches the given name and argument types. You may need to add explicit type casts.

2022-06-27T16:08:09.021614Z: 16:08:09  On model.asana.asana__task: ROLLBACK
2022-06-27T16:08:09.024195Z: 16:08:09  finished collecting timing info
2022-06-27T16:08:09.024348Z: 16:08:09  On model.asana.asana__task: Close
2022-06-27T16:08:09.024829Z: 16:08:09  Database Error in model asana__task (models/asana__task.sql)
  function pg_catalog.date_diff("unknown", timestamp with time zone, timestamp without time zone) does not exist
  HINT:  No function matches the given name and argument types. You may need to add explicit type casts.
  compiled SQL at target/run/asana/models/asana__task.sql
2022-06-27T16:08:09.025035Z: 16:08:09  Sending event: {'category': 'dbt', 'action': 'run_model', 'label': 'bf6e271a-c2b1-4828-a0e6-718d5819cfa4', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x7fd198544d60>]}
2022-06-27T16:08:09.025364Z: 16:08:09  23 of 28 ERROR creating table model dev_asana.asana__task....................... [ERROR in 0.14s]
2022-06-27T16:08:09.025479Z: 16:08:09  Finished running node model.asana.asana__task
Database Error in model asana__task (models/asana__task.sql)
  function pg_catalog.date_diff("unknown", timestamp with time zone, timestamp without time zone) does not exist
  HINT:  No function matches the given name and argument types. You may need to add explicit type casts.
  compiled SQL at target/run/asana/models/asana__task.sql

Expected behavior
The model asana__task should build successfully without error(s).
dbt Project configurations
version: '1.0.0'
config-version: 2

profile: 'default'

model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"
clean-targets:
  - "target"
  - "dbt_packages"

models:
  my_new_project:
    example:
      materialized: view

vars:
    fivetran_log_using_transformations: false # this will disable all transformation + trigger_table logic
    fivetran_log_using_triggers: false # this will disable only trigger_table logic
    fivetran_log_using_account_membership: false # this will disable only the account membership logic
    fivetran_log_using_destination_membership: false # this will disable only the destination membership logic
    fivetran_log_using_user: false # this will disable only the user logic

Package versions
packages:

package: fivetran/fivetran_log
version: [">=0.6.0", "<0.7.0"]
package: fivetran/klaviyo_source
version: [">=0.4.1", "<0.5.0"]
package: fivetran/klaviyo
version: 0.4.1
package: fivetran/asana_source
version: [">=0.5.0", "<0.6.0"]
package: fivetran/asana
version: [">=0.5.0", "<0.6.0"]

What database are you using dbt with?
redshift
dbt Version
1.0.8
Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @shreveasaurus thanks so much for opening this issue. This is a type of issue we have actually seen quite a bit of within a few of our other packages. The primary reason is due to Fivetran syncing the timestamp fields for Redshift warehouses as timestamptz which does is not able to be leveraged within downstream date functions.
Within other packages we have resolved this by casting the timestamp fields in the staging models with {{ dbt_utils.type_timestamp() }} to safely convert to timestamp that may be used in those downstream date functions. See here for how we recently addressed this within our dbt_greenhouse_source package.
I noticed you mentioned you would be open to creating a PR! If that is still of interest to you, then all that would need to be done is to convert the staging models that use timestamp fields with the dbt_utils.type_timestamp() macro. Let me know if you would still be interested in opening a PR! Otherwise, my team can tackle this in our next sprint. Thanks!

Thanks @fivetran-joemarkiewicz for the thoughtful response and nudging me in the right direction! I tested casting the timestamps as you suggested locally and all models in the package are building as expected. I'll give opening a PR a go and let you know if I have any questions. Thanks again!

Hello @shreveasaurus ! I've just cut the release for your PR, you should see it within the next hour or so. Thank you again for your awesome work on this PR and looking forward to new PRs in the future! 🥳


IMAP: Add support for delimiter value NIL in LIST response

Expected behavior
K9 should list all IMAP folders. This worked OK with version 5.0, so I guess it is a regression.
Actual behavior
K9 only lists the standard folders and then throws an exception.
Steps to reproduce

IMAP server uw-imap
Refresh IMAP folders

Environment
K-9 Mail version: 5.201
Android version: 6.0.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP
IOException: Expected 0022 (") but got 004e (N)
com.fsck.k9.mail.MessagingException: Unable to get folder list.
at com.fsck.k9.mail.store.imap.ImapStore.getPersonalNamespaces(ImapStore.java:156)
at com.fsck.k9.controller.MessagingController.refreshRemoteSynchronous(MessagingController.java:430)
From the log, it seems that it does get the folders before the error and I also do not see the actual exception in the log:
01-03 09:16:11.352 I/k9      (8350): Running command 'doRefreshRemote', seq = 7(foregroundpriority)
01-03 09:16:11.464 D/k9      (8350): Connecting to sidamos.de as sidamos.de/<IP_ADDRESS>
01-03 09:16:11.465 I/XiaomiFirewall(3882): firewall pkgName:com.fsck.k9, result:0x0
01-03 09:16:11.749 V/k9      (8350): conn265707776<<<#null# [OK, [CAPABILITY, IMAP4REV1, I18NLEVEL=1, LITERAL+, SASL-IR, LOGIN-REFERRALS, AUTH=PLAIN, AUTH=LOGIN], Backend.fritz.box IMAP4rev1 2007f.404 at Tue, 3 Jan 2017 09:16:08 +0100 (CET)]
01-03 09:16:11.749 D/k9      (8350): Saving [AUTH=LOGIN, LOGIN-REFERRALS, SASL-IR, IMAP4REV1, LITERAL+, I18NLEVEL=1, AUTH=PLAIN] capabilities for conn265707776
01-03 09:16:11.750 V/k9      (8350): conn265707776>>> 1 AUTHENTICATE PLAIN
01-03 09:16:11.807 V/k9      (8350): conn265707776<<<#+# []
01-03 09:16:11.875 V/k9      (8350): conn265707776<<<#1# [OK, [CAPABILITY, IMAP4REV1, I18NLEVEL=1, LITERAL+, IDLE, UIDPLUS, NAMESPACE, CHILDREN, MAILBOX-REFERRALS, BINARY, UNSELECT, ESEARCH, WITHIN, SCAN, SORT, THREAD=REFERENCES, THREAD=ORDEREDSUBJECT, MULTIAPPEND], User thomas authenticated]
01-03 09:16:11.875 D/k9      (8350): Saving [NAMESPACE, SCAN, WITHIN, BINARY, IMAP4REV1, ESEARCH, LITERAL+, MULTIAPPEND, MAILBOX-REFERRALS, IDLE, THREAD=REFERENCES, I18NLEVEL=1, SORT, UNSELECT, THREAD=ORDEREDSUBJECT, UIDPLUS, CHILDREN] capabilities for conn265707776
01-03 09:16:11.876 V/k9      (8350): conn265707776>>> 2 LIST "" "*"
01-03 09:16:11.945 V/k9      (8350): conn265707776<<<#null# [LIST, [\NoInferiors, \Marked], /, mythtv-dev]
01-03 09:16:11.945 V/k9      (8350): conn265707776<<<#null# [LIST, [\NoInferiors, \UnMarked], /, Entw&APw-rfe]
01-03 09:16:11.945 V/k9      (8350): conn265707776<<<#null# [LIST, [\NoInferiors, \UnMarked], /, eBay]

[...]

01-03 09:16:11.977 V/k9      (8350): LockableDatabase: Transaction ended, took 11ms / com.fsck.k9.mailstore.LocalFolder.appendMessages(LocalFolder.java:1218)
01-03 09:16:11.980 I/k9      (8350):  Command 'doRefreshRemote' completed

Looks like the response parser chokes on a line of the LIST response. Can you manually issue the command (LIST "" "*") and record the full response from the server?

list.txt
Output attached.
Is it OK that I can not see the Exception in logcat? I only see it in the "K9mail.error" folder.

Thanks for the output. I'm guessing we're currently not supporting NIL in this line:
* LIST (\NoInferiors) NIL INBOX

I'll also check why the exception doesn't show up in logcat.

https://github.com/k9mail/k-9/blob/406fd6b93d8a29b3df22fad529765024e094a2e7/k9mail-library/src/main/java/com/fsck/k9/mail/store/imap/ImapResponseParser.java#L197 :smile:

;-)
I wonder why it worked with the previous version (5.0). I guess, this is new code.
Hopefully this will be fixed soon.
Thanks!


JwtAuthProvider needs to load JWK keys lazily

JwtAuthProvider verification keys should be downloaded upon the first request and not during the server startup and security creation.

This has been fixed in 2.4.1.


OCPBUGS-38129: [release-4.16]  Update junit report file name to show spec results on Test Grid

NO-ISSUE: Update junit report file name to show spec results on Test Grid

/jira cherrypick OCPBUGS-38119

/cherry-pick release-4.15

/jira refresh

/jira refresh

/retest

/retest

/retest

/jira refresh

/label backport-risk-assessed

/override ci/prow/e2e-gcp-olm-flaky

/jira refresh

/jira refresh

/lgtm
/label qe-approved
/label cherry-pick-approved


Update run_envoy_docker.sh

duplication environment variable
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/wait

if you can lmk what issue you are trying to resolve i would be happy to help

reopening i see that its a duplicate
for future ref please dont resolve PR feedback without some explanation unless the issue is obviously resolved


Fix pipx command in README

The pipx upgrade command is slightly different from the one used by pip. Current command results in an error.

Whoops, there is a duplicate of this PR already:
https://github.com/godaddy/aws-okta-processor/pull/56
Let's merge that one instead. Closing.


Move applications out of the "doesn't use buildProject" block

We're slowly changing some of the apps in the "doesn't use buildProject" block of our Jenkinsfile so that they do use buildProject.  In most cases they don't use it because the job and repo names don't match.  This has been fixed in buildProject so we can upgrade those apps.  This PR is for tracking those changes as they are merged.  Each commit will be a different app.

Reminder to self: downstream projects that have been fixed need to be deployed to production before we'll start seeing them self report on github as it's the deployed-to-production branch that is built by this job.

Oops, I should have marked this as [WIP] because I hope to do a few more before merging (licence-finder and smart-answers).  Thanks for the pre-emptive approve though 😉 !

Merging because it's valuable to have these switched, even if it's not all of the apps.


[locale] Fix Serbian locale (sr, sr-cyrl)

This fixes some login and grammatical errors in Serbian locales (sr, sr-cyrl) and their tests.
Two major problems were logic for getting grammatical cases. It was flawed because it didn't consider special cases for multi-digit numbers, just for single digit special cases.
Along with this, some grammar fixes were made because of different writing of nouns in different tenses (past and future) alongside those without tense (without prefix). Here is some info about that on Wiki. If that's not enough, I'll try to find something that has specific rules about that but I think it's better that other locale contributors look over this.
The tests are adapted to check for new grammar and logic fixes.

approval @crnjakovic ?

I'd have to take a look at this later, I'm at work atm. @marwahaha


Extension not working

The extension does not want to work (chrome).

The float inspect API has become much more stable in the last few weeks, you're unlikely to encounter this.


Customer Self Service Portals

I need to edit the web form of case creation by deleting and adding new fields, I created a new web form and web form steps in them but nothing is reflecting in the portals ? Is there step I missed? Do I need some extra configuration?
Could you guide through some steps for setting up account  scope and  scope for a particular customer or any related docs related to this would be a big help?

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

ID: a0f78157-6d85-d438-2dd3-deeded19612b
Version Independent ID: 9c08bf4d-ca4f-0055-dfcb-042b26efa9cb
Content: Create a portal in Power Apps - PowerApps
Content Source: powerapps-docs/maker/portals/create-portal.md
Service: powerapps
GitHub Login: @tapanm-MSFT
Microsoft Alias: tapanm

Hi @samikshashetty, thank you for reaching out. Please check case entity permissions and see if clearing the cache helps. If the problem persists, suggest to please work with the support team by creating a service request for further investigation.


In CKAN, listed as being 1.1.2 compatible

This prevents anything which depends on it from being installable in 1.1.3

Please put this on NetKAN where it will get the right attention.

It's a problem in the netkan file.  I can fix it for you, but need you to confirm it is compatible with 1.1.3 (and say it's ok for me to update the file).
Thx

It works fine, you can update it.

Ok, thanks


Cascaded delete in MapDB

All of the delete controllers need to handle cascaded delete, which is hard because there is some cross-dependency between unversioned and versioned data (e.g. deleting a stop requires also deleting things from particular agency feeds, but we don't know which ones, etc.) Or maybe you just shouldn't be able to delete route types and stops.
We could do crude reference counting by keeping a long referenceCount in unversioned objects, but that seems prone to errors. Also, when can you delete a stop - when it's used in no agency's master, or when it's used in no agency snapshot?
Perhaps we just mark things as "deleted" and hide them from the UI. We could have a warning on export if we're exporting things that have been deleted.

Related to #166.


feat: Enable autostart on Linux

Addressing autostart configuration on linux reported in #82
And perhaps fixing #529

I found that this approach is not working with the .deb install. I will further debug to find out why.

It looks like the library it's failing to identify the standard implementation that it should be using.

My bad. It was a mistake I introduced before pushing, and it went unnoticed 🫠

Nice!


EN-5227 : Session Logs Upload from Client

Description
Whenever a terminal is opened, script starts capturing the session logs.

When the user types exit or close the window, the script session log file becomes available. It will be stored at /var/unskript/sessions/logs/<sessiod_id>.log

We need to upload these logs to RTP via the ovpn tunnel.

Write a standalone python script which creates a tar of the logs in the /var/unskript/sessions/logs/ directory and calls the RTP upload endpoint.

Its possible that some file get added into this directory after the tar is done and while upload is happening, so to cover that case, move the files (not copy) in this directory in some other directory (name it like upload ) and do the tar of that.

If the upload succeeds, delete the files in the upload directory.

If the upload fails, keep the files in the upload directory.

We SHOULD not delete upload directory. The idea is if lets on one scheduled run, upload fails, then on the next schedule, we move more files from the /var/unskript/sessions/logs/  to this upload directory and try uploading that. This way we dont lose any log files.

The script should log errors or other info in a directory /var/log/unskript/upload_script.logs

Logs should capture the following:

start time

num of files uploaded

end time

obviously errors if any

Now, regarding the trigger for the above script. there will be 2 triggers for it

a new cron job will run the above script at a configured cadence

The cron schedule should be read from unskript_ctl_config.yaml file. Add a new field upload_session_logs_cadence in the remote_debugging section, something like this

remote_debugging:
  enable: false
  # ovpn file location
  ovpn_file: ""
  # Cadence at which tunnel needs to be brought up.
  # Cadence is specified in cron syntax. More information about the syntax can
  # be found in https://crontab.guru
  # minute  hour  day (of month)  month  day (of week)
  #   *      *          *           *        *
  # Example: "*/30 * * * *"   <= This will run every 30 Minutes
  #
  tunnel_up_cadence: ""
  # Cadence at which tunnel needs to be brought down.
  # Cadence is specified in cron syntax. More information about the syntax can
  # be found in https://crontab.guru
  # minute  hour  day (of month)  month  day (of week)
  #   *      *          *           *        *
  # Example: "*/30 * * * *"   <= This will run every 30 Minutes
  #
  tunnel_down_cadence: ""
  upload_session_logs_cadence: ""

Need to add support in unskript_ctl_config_parser.py to parse the above field and set the cronjob, specifically parse_remote_debugging

Its always possible that the ovpn tunnel might be down whenever the cronjob runs, so to cover that case, we should run the above script when the unskript debug start --config command is run, once the tunnel has come up.

Testing
Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested helm chart locally.
root@129031600ae7:~# python /usr/local/bin/unskript_ctl_upload_session_logs.py

2024-01-11 17:11:53,021 - INFO - Start Time: 2024-01-11 17:11:53.020758
2024-01-11 17:11:53,026 - INFO - Num files uploaded: 1
2024-01-11 17:11:53,028 - DEBUG - Starting new HTTP connection (1): <IP_ADDRESS>:6443
2024-01-11 17:11:53,585 - DEBUG - http://<IP_ADDRESS>:6443 "POST /v1alpha1/sessions/logs HTTP/1.1" 204 0
2024-01-11 17:11:53,586 - INFO - File uploaded successfully.
2024-01-11 17:11:53,586 - INFO - End Time: 2024-01-11 17:11:53.586790
2024-01-11 17:50:47,055 - INFO - Start Time: 2024-01-11 17:50:47.055095
2024-01-11 17:50:47,058 - INFO - Num files uploaded: 3
2024-01-11 17:50:47,079 - INFO - {'test':<PHONE_NUMBER>, 'test2':<PHONE_NUMBER>, 'f4ed3529-a9c2-4444-af5a-d104f4d6ecec':<PHONE_NUMBER>}
2024-01-11 17:50:47,080 - INFO - End Time: 2024-01-11 17:50:47.080241

Checklist:

[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published.

Documentation
Make sure that you have documented corresponding changes in this repository.

Need to remove hard coded cadance


Missing semicolon in xy-grid/_classes.scss

How to reproduce this bug:

Step one
Compile Foundation scss with xy-grid enabled.

What should happen:
Css should generate properly.
What happened instead:
error  (Line 415 of foundation-sites/scss/xy-grid/_classes.scss: Invalid CSS after "...grid-margin-y')": expected "}", was ".grid-frame.gri...").
At Line 414 a Semicolon is missing.
Foundation Version(s) you are using:
6.4.2

@Siqu Thanks for pointing this out. I've added a PR to fix this here: https://github.com/zurb/foundation-sites/pull/10531


Failed to delete deployment

When agents have been idle for enough time they should be deallocated, but the agent enters an Error state:
Failed to delete deployment buildagent-1 in resource group TeamCity: null: jetbrains.buildServer.clouds.CloudException: Failed to delete deployment buildagent-1 in resource group TeamCity: null (enable debug to see stacktrace)
[2017-11-30 13:51:10,611]   INFO [onPool-worker-1] - uds.base.AbstractCloudInstance - Changing buildagent-1(7cedc0) status from Scheduled to stop to Error

It seems it's trying to delete totally the deployment even if the 'Reuse allocated virtual machines' option is set.
TeamCity version: 2017A
Plugin Version: 0.6.4

A more precise stackframe
jetbrains.buildServer.clouds.CloudException: Failed to delete deployment buildagent-1 in resource group TeamCity: nulljetbrains.buildServer.clouds.CloudException: Failed to delete deployment buildagent-1 in resource group TeamCity: null
at jetbrains.buildServer.clouds.azure.arm.connector.AzureApiConnectorImpl$deleteDeploymentAsync$1.doResume(AzureApiConnectorImpl.kt:599)
at kotlin.coroutines.experimental.jvm.internal.CoroutineImpl.resume(CoroutineImpl.kt:54)
at kotlinx.coroutines.experimental.DispatchTask.run(CoroutineDispatcher.kt:120)
at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Caused by: java.lang.NullPointerException
at jetbrains.buildServer.clouds.azure.arm.connector.AzureApiConnectorImpl$deleteDeploymentAsync$1$doResume$$inlined$withLock$lambda$1.doResume(AzureApiConnectorImpl.kt:567)
at kotlin.coroutines.experimental.jvm.internal.CoroutineImpl.resume(CoroutineImpl.kt:54)
at kotlinx.coroutines.experimental.DispatchTask.run(CoroutineDispatcher.kt:120)
at kotlinx.coroutines.experimental.EventLoopBase$QueuedRunnableTask.run(EventLoop.kt:189)
at kotlinx.coroutines.experimental.EventLoopBase.processNextEvent(EventLoop.kt:129)
at kotlinx.coroutines.experimental.BlockingCoroutine.joinBlocking(Builders.kt:225)
at kotlinx.coroutines.experimental.BuildersKt.runBlocking(Builders.kt:150)
at kotlinx.coroutines.experimental.BuildersKt.runBlocking$default(Builders.kt:142)
at jetbrains.buildServer.clouds.azure.arm.connector.AzureApiConnectorImpl$deleteDeploymentAsync$1.doResume(AzureApiConnectorImpl.kt:561)
...

@thinkbeforecoding, thanks for reporting. Could you please also specify what type of image you use: template, VHD or image?

It's a template.
The template deployment was successfully  deployed.
I don't use agent push, the arm template use the arm CustomScript extension to install the agent after the machine is built. The agent is installed, started and authorized correctly.

I installed the snapshot.
The error disappeared, and the agent have been deleted.
But is it expected when the 'Reuse allocated virtual machines ' box is checked ? Shouldn't they be only deallocated instead of deleted ?

Another strange thing.
I put a limit of 5 for the image.
When 4 agents have been depolyed, the 'start' button is still enabled, but when I press it, it add a new 'build agent' line but no actual deployment is started. When I refresh the page, this fifth agent doesn't appear anymore.

@thinkbeforecoding, could you please share the teamcity-clouds.log server log file for investigation?
GitHub does not have secure attachments, so could you please file an issue in the TeamCity tracker and attach it there?

Ah.. looking at the teamcity-clouds.log I see that the 5th is not allocated because I reached the core limit on the subscription. My bad 😁

But stopping the agent still delete the VM instead of just stopping them...

The log says:
Removing virtual machine buildagent-3 due to cloud image settings

Which, in the code seems to indicate that behaviour.isDeleteAfterStop is true, which is only the case for
FRESH_CLONE(true, false).
but in AzureCloudDetails.kt', getBehaviour()` is implemented as:
 if (myReuseVm) CloneBehaviour.ON_DEMAND_CLONE else CloneBehaviour.FRESH_CLONE

So it seems that myReuseVM is false, even if the check box is checked.
Is there a name mismatch in parameters  for const val REUSE_VM = "reuseVm" ?
I cannot find on the server where the cloud profile + template parameters are stored ? any clue ?

I found the parameter in the config and it is true...
       <param name="reuseVm" value="true" />

So.... Don't know what is the source of the problem... 🤔

I'll create a specific issue for this

@thinkbeforecoding, great thanks for investigation, will take a look at the issue #80.