Ghosting

Stratux version:1.5b2

Stratux config:
SDR

[ ] single
[X ] dual

GPS

[ ] yes
[X ] no
type:

AHRS

[X ] yes
[ ] no

power source:
usb cable:hard wired

EFB app and version: (e.g., WingX Pro7 8.6.2) FltPlan Go 4.7.22
EFB platform: (e.g., iOS 9.2) iOS 12
EFB hardware: (e.g., iPad Mini 2) iPad Mini 2

Description of your issue: I have a Garmin GDL-82 out, and I'm still seeing a ghost of my aircraft.  Is there a way to rectify this?  I read that once the ADS-B out was installed, the issue would be resolved.  Thank you!

If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://<IP_ADDRESS>/logs/stratux/ and http://<IP_ADDRESS>/logs/stratux.log.

If your ownship isn't being picked up you can force it by entering your aircrafts hex code into the Stratux web interface.
Just look up your hex code on the aircraft register and enter it into the settings tab of the web interface.

Thank you!

TOPNOTCH AERO, INC.
Michael Sawyer
<EMAIL_ADDRESS><EMAIL_ADDRESS>512.708.8000
800.395.8386
"The master in the art of living makes little distinction between his work and his play, his labor and his leisure, his mind and his body, his information and his recreation, his life and his religion. He hardly knows which is which. He simply pursues his vision of excellence at whatever he does, leaving others to decide whether he is working or playing. To him, he's always doing both."   James Michener
===================================================================================
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this email in error, please notify the sender immediately and delete the original message. Neither the sender nor the company for which he or she works accepts any liability for any damage caused by any virus transmitted by this email.
From: Helno<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 4:35 PM
To: cyoung/stratux<EMAIL_ADDRESS>Cc: topnotchaero<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cyoung/stratux] Ghosting (#779)
If your ownship isn't being picked up you can force it by entering your aircrafts hex code into the Stratux web interface.
Just look up your hex code on the aircraft register and enter it into the settings tab of the web interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/779?email_source=notifications&email_token=AMMGLOS7UA5AWKCH4CWHOATP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI#issuecomment-503755405 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMMGLOUVNZQ74HAULO4N4CLP3KQ7VANCNFSM4HY2AS3A .  https://github.com/notifications/beacon/AMMGLOTNQ6YPO6XRE4DLZDTP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI.gif

Where would I find the option within the Stratux web interface?

TOPNOTCH AERO, INC.
Michael Sawyer
<EMAIL_ADDRESS><EMAIL_ADDRESS>512.708.8000
800.395.8386
"The master in the art of living makes little distinction between his work and his play, his labor and his leisure, his mind and his body, his information and his recreation, his life and his religion. He hardly knows which is which. He simply pursues his vision of excellence at whatever he does, leaving others to decide whether he is working or playing. To him, he's always doing both."   James Michener
===================================================================================
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this email in error, please notify the sender immediately and delete the original message. Neither the sender nor the company for which he or she works accepts any liability for any damage caused by any virus transmitted by this email.
From: Helno<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 4:35 PM
To: cyoung/stratux<EMAIL_ADDRESS>Cc: topnotchaero<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cyoung/stratux] Ghosting (#779)
If your ownship isn't being picked up you can force it by entering your aircrafts hex code into the Stratux web interface.
Just look up your hex code on the aircraft register and enter it into the settings tab of the web interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/779?email_source=notifications&email_token=AMMGLOS7UA5AWKCH4CWHOATP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI#issuecomment-503755405 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMMGLOUVNZQ74HAULO4N4CLP3KQ7VANCNFSM4HY2AS3A .  https://github.com/notifications/beacon/AMMGLOTNQ6YPO6XRE4DLZDTP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI.gif

Settings tab.
Mode S hex code.

I don’t have a mode S.  Will entering the hex code in that field keep my GDL-82 from ghosting?

TOPNOTCH AERO, INC.
Michael Sawyer
<EMAIL_ADDRESS><EMAIL_ADDRESS>512.708.8000
800.395.8386
"The master in the art of living makes little distinction between his work and his play, his labor and his leisure, his mind and his body, his information and his recreation, his life and his religion. He hardly knows which is which. He simply pursues his vision of excellence at whatever he does, leaving others to decide whether he is working or playing. To him, he's always doing both."   James Michener
===================================================================================
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this email in error, please notify the sender immediately and delete the original message. Neither the sender nor the company for which he or she works accepts any liability for any damage caused by any virus transmitted by this email.
From: Helno<EMAIL_ADDRESS>Sent: Thursday, June 20, 2019 3:48 PM
To: cyoung/stratux<EMAIL_ADDRESS>Cc: topnotchaero<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cyoung/stratux] Ghosting (#779)
Settings tab.
Mode S hex code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/779?email_source=notifications&email_token=AMMGLOUX43ANJ7PD5NETARTP3PUIBA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGSDUQ#issuecomment-504177106 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMMGLOSK2R6SXKGFSMOEJSTP3PUIBANCNFSM4HY2AS3A .  https://github.com/notifications/beacon/AMMGLOWPTGPFM2UNKXK2AGDP3PUIBA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGSDUQ.gif

All aircraft have a mode S code assigned to them even if they do not have the hardware to broadcast it.
The shop that installed your GDL82 would have entered your hex code into it. This is what is broadcast along with your position to have ADS-B OUT. The only time this is not broadcast is when you use UAT anonymous mode.

I know what the hex code is.  I just wasn’t sure entering it into the Mode S field would solve my ghosting issue.  I’ll be at the airport this weekend and give it a try.  Thank you!

TOPNOTCH AERO, INC.
Michael Sawyer
<EMAIL_ADDRESS><EMAIL_ADDRESS>512.708.8000
800.395.8386
"The master in the art of living makes little distinction between his work and his play, his labor and his leisure, his mind and his body, his information and his recreation, his life and his religion. He hardly knows which is which. He simply pursues his vision of excellence at whatever he does, leaving others to decide whether he is working or playing. To him, he's always doing both."   James Michener
===================================================================================
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this email in error, please notify the sender immediately and delete the original message. Neither the sender nor the company for which he or she works accepts any liability for any damage caused by any virus transmitted by this email.
From: Helno<EMAIL_ADDRESS>Sent: Thursday, June 20, 2019 3:55 PM
To: cyoung/stratux<EMAIL_ADDRESS>Cc: topnotchaero<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cyoung/stratux] Ghosting (#779)
All aircraft have a mode S code assigned to them even if they do not have the hardware to broadcast it.
The shop that installed your GDL82 would have entered your hex code into it. This is what is broadcast along with your position to have ADS-B OUT. The only time this is not broadcast is when you use UAT anonymous mode.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/779?email_source=notifications&email_token=AMMGLOTFKBOKV46XA3UYXOLP3PVCPA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGSUTI#issuecomment-504179277 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMMGLOWTFPQID65B76IHTUDP3PVCPANCNFSM4HY2AS3A .  https://github.com/notifications/beacon/AMMGLOUKBJABCNEIRDXAUJ3P3PVCPA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGSUTI.gif

It worked.  Thank you!

TOPNOTCH AERO, INC.
Michael Sawyer
<EMAIL_ADDRESS><EMAIL_ADDRESS>512.708.8000
800.395.8386
"The master in the art of living makes little distinction between his work and his play, his labor and his leisure, his mind and his body, his information and his recreation, his life and his religion. He hardly knows which is which. He simply pursues his vision of excellence at whatever he does, leaving others to decide whether he is working or playing. To him, he's always doing both."   James Michener
===================================================================================
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not review, copy or distribute this message. If you have received this email in error, please notify the sender immediately and delete the original message. Neither the sender nor the company for which he or she works accepts any liability for any damage caused by any virus transmitted by this email.
From: Helno<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 4:35 PM
To: cyoung/stratux<EMAIL_ADDRESS>Cc: topnotchaero<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cyoung/stratux] Ghosting (#779)
If your ownship isn't being picked up you can force it by entering your aircrafts hex code into the Stratux web interface.
Just look up your hex code on the aircraft register and enter it into the settings tab of the web interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/779?email_source=notifications&email_token=AMMGLOS7UA5AWKCH4CWHOATP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI#issuecomment-503755405 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMMGLOUVNZQ74HAULO4N4CLP3KQ7VANCNFSM4HY2AS3A .  https://github.com/notifications/beacon/AMMGLOTNQ6YPO6XRE4DLZDTP3KQ7VA5CNFSM4HY2AS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDLFDI.gif


set type of variable in for-in loop

Suggestion

🔍 Search Terms

for in
type in for in
set type of for in
auto in type
for type
for in type

✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

In short, my question/suggestion is that for ... in expressions should automatically set the type of the variable to keys of the object being iterated.
📃 Motivating Example

Here's a snippet from a project I'm working on.

const eventsWhichCauseStateChanges = [
    'add-components',
    'delete-components',
    'rotate-component',
    'flip-components',
    'move-component',
    'connect-components',
    'disconnect-components',
    'move-wire-node',
    'add-wire-node',
    'remove-wire-node',
    'import-document',
    'change-label',
    'cut',
    'copy',
    'paste',
] as const;
type val = typeof eventsWhichCauseStateChanges[number];

const burst: Record<val, boolean> = {
    'add-components': false,
    'delete-components': false,
    'rotate-component': false,
    'flip-components': false,
    'move-component': false,
    'connect-components': false,
    'disconnect-components': false,
    'move-wire-node': false,
    'add-wire-node': false,
    'remove-wire-node': false,
    'import-document': false,
    'change-label': false,
    'cut': false,
    'copy': false,
    'paste': false,
};

for (const i in burst)
    console.log(burst[i as keyof typeof burst]);

💻 Use Cases
Notice that on the last line, I must explicitely state the type of i. I think that should be obvious. Considering we're iterating over burst. The way it is at the moment, i has a type of string. Which is of course entirely true, but in my opinion, not as specific as it can be.

See #44706, #44535, #35847, etc.


VirtualMachineReplicaSet to scale VMs

Initial simple implementation of a VirtualMachineReplicaSet.
Usage:
apiVersion: kubevirt.io/v1alpha1
kind: VirtualMachineReplicaSet
metadata:
  name: myrs
spec:
  replicas: 3
  selector:
    matchLabels:
      myselector: myselector
  template:
    metadata:
      name: test
      labels:
        myselector: myselector
    spec:
      domain:
        devices:
          consoles:
          - type: pty
        memory:
          unit: MB
          value: 64
        os:
          type:
            os: hvm
        type: qemu

TODO:

[x] proposal
[x] logging
[x] events
[ ] graceful delete

@fabiand yes i considered reusing it. It is not yet fully from the table. So this can also be seen as a POC for the completely layered approach. Regarding to not having our own cluster level object, I think no matter if we reuse ReplicaSets, or not, we need that.

@rmohr I agree that a having a VM specific cluster object to represent the replica set makes sense. I also like the idea of calling it a VirtualMachineReplicaSet. That naming convention makes it pretty obvious what the object does within the context of k8s.
I'm still contemplating the approach of implementing our own replication logic instead of leveraging the k8s controllers to do this for us.
For the sake of argument, how would it work if we re-used the k8s replica set behind the scenes? Below are my thoughts on how I'd approach it..

Creating a VirtualMachineReplicaSet (VMRS) would generate an internal k8s replica set
The k8s replica set would start the VM pods.
The VMRS controller would watch for pods related to itself and dynamically introduce VMs for each pod using the spec in the VMRS. These VMs should have a flag on them that prevents the VM controller from ever generating a POD for them.
The VM controller would then see a VM got created, that corresponding POD already exists, and then proceed with assigning the VM to the node.
When a POD related to a VMRS is completed/terminated/failed/whatever, the VMRS controller handles cleaning up the corresponding VM definition associated with it.

Basically, with this design the VMRS controller would just do these things.

create/update/delete replica sets for corresponding VMRC objects.
dynamically generate VM objectes as VMRS related pods appear
remove VM objects as VMRC related pods disappear.

Thoughts on the Pros/Cons of something like what I've outlined above vs rolling out our own replication logic?

retest this please

retest this please

retest this please

retest this please

retest this please

I've seen the cloud-init tests timeout occasionally. I've increased the timeouts to match that of the console functional tests over here in this pr #444.

retest this please

Was there any reply to https://github.com/kubevirt/kubevirt/pull/453#issuecomment-330629711 ?

So regarding to the approach: I think we are talking about potentially reusing three controllers ReplicaSet, StatefulSet and Deployment. The outlined steps above
Regarding to pros/cons of reusing existing controllers:
pro:

In some cases it might mean a little less controller code
Initial code writing, like a VirtualMachineControllerRefManager can be delayed (however there already exist abstractions in client-go for most thinks)

con:

Loose control on what happens. E.g. a replicaset creates another pod already when a pod is marked for deletion. No matter if we want that, we just can't decide it.
Custom strategies for deletion orders, like mentioned by @davidvossel  are impossible to implement then
We would loose the ability to treat the VM as our atomic entity, if we change something internal to the VM, we have to go through each controller to see if it will work
If controllers have revisions, we still need to duplicate the revision logic
Listeners are still required, you would even have to listen to more entities. The base controller and pods, instead of just the VM.
Duplicating  the state to our controller from the k8s controller is still requried
Would we have to actually re-test every VM lifecycle feature to make sure that it works for each controller?
OwnerReferences still need to be maintained (pointing to the k8s core controller instead of the VMs).

At the end I have the feeling that it might be a little less code if we wrap around these three controllers, but to a high price. Since in both scenarios we need a lot of controller logic, I would actually prefer to keep a clear stacking at least for the ReplicaSet. If it turns out that it is an extreme amount of work to create something like a StatefulSet purely based on VMs, and therefore we create the infra to wrap around k8s core controllers, I would be open to discuss the VirtualMachineReplicaSet implementation again.

If it turns out that it is an extreme amount of work to create something like a StatefulSet purely based on VMs, and therefore we create the infra to wrap around k8s core controllers, I would be open to discuss the VirtualMachineReplicaSet implementation again.

With this understanding, I'm in support @rmohr's initial approach to vm replica sets.
My biggest concern was that we were trivializing the amount of work to provide the kind of consistency the pod StatefulSets are aiming for. If we find that we're hitting some complex edge conditions that K8s already solves in their controllers, we should re-evaluate our implementation and see what we can reuse.

State: Everything except graceful deletes and owner references is implemented. graceful deletes are generally not yet supported and tracked by #454. I want to add owner references in a follow up PR.
@davidvossel there is one surprise hidden in the new patches. I though that the expectation manager (https://github.com/kubevirt/kubevirt/pull/453/files#diff-aea407b8c3b5cc0af5f852ae77b4c54c) is already part of client-go. It was not. As a workaround I copied it over. It only depends on client-go and apimachinery dependencies. Will investigate if it can be exported to apimachinery.

Everything except copying the unit test, and updating the proposal itself should be done now. Will update the proposal itself asap, including a justification for not just wrapping around the replication controller.

Live migrations are an area where the VM replica set use case diverges from the container use case.
I don't think we have to have live migration completely solved within the context of replica sets before this work can be merged, but it would be great if we had a general idea of how we plan to approach that problem. @rmohr Maybe you could put your thoughts on this topic in the proposal?

@smarterclayton added some justifications  why this implementation was chosen. Looking forward to hear your thoughts.

@davidvossel  added the explanation how I plan that we support live migrations for all types of controllers to the proposal. If we follow the currently layed out architecture (independent of the new discussion on the mailing list https://groups.google.com/forum/#!topic/kubevirt-dev/4XBlPPEcIq4), the live migration story is in my opinion solid an solved, or am I missing something?

@davidvossel added the tests for the expectations apart from the the discussion if we should keep the name for the controller, I think everything which should be here right now is there.

@davidvossel added the tests for the expectations apart from the the discussion if we should keep the name for the controller, I think everything which should be here right now is there.

Really great work Roman!  This is solid.
Code and testing wise, everything looks in order to me at this point. I'm going to wait until we conclude the controller naming discussion before marking "approved"

If you want to merge and continue the naming discussion that's fine - I
don't know that you have to do them in order as long as you think you can
resolve that concern before you get locked into supporting the API
On Tue, Sep 26, 2017 at 1:22 PM, David Vossel<EMAIL_ADDRESS>wrote:

@davidvossel https://github.com/davidvossel added the tests for the
expectations apart from the the discussion if we should keep the name for
the controller, I think everything which should be here right now is there.
Really great work Roman! This is solid.
Code and testing wise, everything looks in order to me at this point. I'm
going to wait until we conclude the controller naming discussion before
marking "approved"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/pull/453#issuecomment-332272139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_p1r5aRaezvLJ-0qFE1rFaVX2SJWkks5smTLRgaJpZM4PcKXf
.


Add a native ParquetIO.ReadRows transform

ParquetIO today uses Avro's GenericRecord to materialize reads from Parquet records, this implies an extra conversion from GenericRecord to Beam's Row. We can 'push' this conversion into the source read process by implementing a RecordMaterializer that builds Rows at read time xtending Parquet's ReadSupport.
Imported from Jira BEAM-12306. Original Jira may contain additional context.
Reported by: iemejia.

any updates here?


Split a policy rule into Openflow rules based on resolved ports

A policy rule can be split into multiple Openflow rules based on the
named port resolving result. Pods that have same port numbers for the
port names defined in the rule will share an Openflow rule.
Fixes #122

/test-all

/test-all

/test-all

/test-all

/test-all

/test-e2e

LGTM


supports for torch 1.5?

torch 1.5 build (nightly) got error :
mmdet/ops/nms/src/nms_cuda.cpp:4:23: error: ‘AT_CHECK’ was not declared in this scope
 #define CHECK_CUDA(x) AT_CHECK(x.type().is_cuda(), #x, " must be a CUDAtensor ")

Thanks for your bug report. For now, we mainly support pytorch 1.1-1.4. We will support Pytorch 1.5 in the future ASAP.

#2513


Hardcode characters

Describe your problem here.
How can I hardcode characters?
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

check Character.hx, there's a comment in there somewhere depicting where you are able to hardcode your characters

Ohh ok thanks


Custom text editors: dirty write prevention actions do not appear properly

In the context of https://github.com/microsoft/vscode/issues/117873 I was investigating how text based custom editors behave today and tried the Draw.IO extension (https://marketplace.visualstudio.com/items?itemName=hediet.vscode-drawio) for that matter.
My setup is:

2 windows open on the same file (draw IO)
making first window file dirty
making the second window file dirty and save it
in the first window try to save

You end up in the dirty write prevention flow:

Selecting "Overwrite" works fine, but "Compare" misses the toolbar actions to resolve the conflict:

I have to say, I wasn't even expecting the diff editor to work properly but this is a very cool experience because I seem to be seeing the left hand side (modified on disk) as readonly preview and my changes on the right 👏
But what is missing are these actions to resolve the conflict:

Any existing issues for this or am I the first to find out?

The origin of this seems to be a context key we only set for file editors:
https://github.com/microsoft/vscode/blob/5a8936ae639316163e89e08920d2120515ab55e6/src/vs/workbench/contrib/files/browser/editors/textFileSaveErrorHandler.ts#L77-L90

I pushed a change to let the actions appear:

And now the save/revert is properly going through the editor API. I verified this fixes the issue. However I found https://github.com/microsoft/vscode/issues/119060 as a follow up.


Add typescript support

This update installs and adds the TypeScript plugin to VSCode extension.

This looks ok, but should wait until #5 is merged. After which we should test again if the extension works with the new setup


test: add complex gemini tests

Add complex gemini tests. Manually ran these tests to ensure they pass.
TODO: Add these to the CI once Charles is back to inject env vars.

small PR - just adds in the rest of the complex e2e tests


patching doesnt appear to work

Thank you for creating this.  When I follow the directions given, the patcher throws an error message that it can't find  part of the path ( steam\steamapps\common\cattails\speed increase\install speed increase mod\obj )  .  Is there something I'm doing incorrectly?

Hey there, I haven't worked on this since my academic year started unfortunately. IIRC it worked perfectly then to install mods, but something may have changed. I just wanted to let you know that I will peek at this today and get back to you on it! Thank you for your message and I hope I can get back to you soon with some news.

Alright, so the issue is with the HgPatcher tool and the use of GitHub to share mods. GitHub apparently strips all empty directories from uploads, which ended up breaking the Patcher Script.
I went ahead and edited the script myself, which you can find here in my fork: https://github.com/Erik-Debye/HgPatcher/tree/main/Scripts
I also went ahead and created a pull request to the original repository as well. I am not a C# developer at all, so there may be bugs but I seem to have it working. Remember to always backup your original file before using a script on it.
Let me know how it goes! I will keep this issue open in the mean time.


Add Windows CI

We should make sure it always works on Windows too.

I added CI for windows module, the core still has some problems related to dependencies not compatible on windows. I will fix this as I move those modules.


Doesn't work well with Pwsh

When I use New-SSHSession, It occurs:
New-SSHSession: Could not load type 'System.Security.Cryptography.HMACRIPEMD160' from assembly 'mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Because the modules is for Windows PowerShell and not Core or 7

On Dec 22, 2020, at 9:18 AM, Foobar<EMAIL_ADDRESS>wrote:
When I use New-SSHSession, It occurs:
New-SSHSession: Could not load type 'System.Security.Cryptography.HMACRIPEMD160' from assembly 'mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/360, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHV35EJL7YWRKFB2YITSWCMC7ANCNFSM4VFT7TOA.


Mob Programming 16th March, 2023

Hi @otmanTR  and @TamaraDimov, Great work you have in here. However, I would like you to check the images of your rockets. They are not currently being displayed. Also check your profile page as it is not currently displaying the list of joined missions. Once again, great work you have in here 👍

Thank you for your good advices.


Added breakpoint to stiches and made login page buttons responsive

Description
Please describe your changes. Be descriptive enough to reduce churn for review process.
Checklist

[x] discord username: Aksel#7033
[x] Closes #372
[x] PR must be created for an issue from issues under "In progress" column from our project board.
[x] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules, and should include the app/package/service name in the title. For example, a title like "docs(@kampus-apps/pano): Add README.md" can be used.
[x] Related file selection: Only relevant files should be touched and no other files should be affected.
[x] I ran npx turbo run at the root of the repository, and build was successful.
[ ] I installed the npm packages using npm install --save-exact <package> so my package is pinned to a specific npm version. Leave empty if no package was installed. Leave empty if no package was installed with this PR.

How were these changes tested?
tested with chrome developer tools

Good job, though the code still needs to be formatted. Please run prettier on the changes you've sent, though please don't open another PR, just send a commit to this one. TY.

Good job, though the code still needs to be formatted. Please run prettier on the changes you've sent, though please don't open another PR, just send a commit to this one. TY.

done

@akselsaatci great job. ty so much.


[stable/external-dns] Add support for istio gateways

What this PR does / why we need it:
Allows external-dns to be configured to use the istio-gateway source as described by this tutorial.
Setting istio.enabled=true will create the appropriate RBAC rule as well as adding the source arg to use it.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

👍  I did the same thing last week.


fix showing yaml fn args re #98

Ensures the content is escaped before printing to the terminal to preserve function args in []. See https://rich.readthedocs.io/en/stable/markup.html#escaping for the rich documentation on the subject. Closes #98.

Codecov Report

Merging #100 (de6f52b) into main (7c2c938) will decrease coverage by 0.02%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##             main     #100      +/-   ##
==========================================
- Coverage   83.68%   83.66%   -0.03%
==========================================
  Files          37       37
  Lines        1318     1322       +4
==========================================
+ Hits         1103     1106       +3
- Misses        215      216       +1

Impacted Files
Coverage Δ

src/cirrus/core/components/files/base.py
83.63% <0.00%> (ø)

src/cirrus/core/utils/console.py
83.33% <75.00%> (-16.67%)
:arrow_down:

Continue to review full report at Codecov.

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


dnsmasq: Upgrade to 2.78

This version includes several important security fixes.
Change-type: minor
Changelog-entry: Update dnsmasq to 2.78
Signed-off-by: Will Newton<EMAIL_ADDRESS>

Closing this PR in favour of https://github.com/resin-os/meta-resin/pull/870 which does a full backport of the latest recipe rather than re-using dnsmasq.inc which seems to cause problems with cross version compatibility.


Create --macro-state-in-respective-node option

resolves #5922

Description
Add an optional field in ParsedNode called dependent_macro_state that will be referenced for the model's dependent macro's definitions when --state parameter is used with new parameter --macro-state-in-respective-node. The --select state:modified selector will read the macro_sql from dependent_macro_state field instead of the existing macros field in manifest when parameter --macro-state-in-respective-node is provided

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Closing because ticket has been closed as stale.


refactor(storage): refactor compaction task heartbeat

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This pr refactors the structure of the compaction task in memory, and the trigger pattern, as follows

remove the design of binding the compaction task to context_id, remove all context_id mapping and checking logic, and keep only the task id for task assignment in the system
ensure the atomicity of task and task assignment (use single transaction), remove the separate assign process (non-atomic)
refactor the task cancellation process to not rely on context_id

Cancel the failed task in the compactor according to the task progress report
The backend periodically scans for tasks without progress reporting and cancels failed tasks on the meta side

Introduce a new Pull-Based trigger model to replace the original Push-Based model.

Remove SchedulerPolicy
Compactor pulls a specified number of tasks to Meta via HeartBeat
Manage the task count of compactor requests in memory, and introduce CompactorPullTaskHandle to handle tasks
Scheduler sends tasks to the corresponding compactor based on the pending pull task in memory

The Compactor side calculates the required task count and sends it to Meta via HeartBeat to pull the specified number of tasks

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

Documentation

[ ] My PR contains user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

I will review this PR as soon as possible❤

nexmark-q7  1cn-1compactor baseline

nexmark-q7  1cn-1compactor branch

nexmark-q7  1cn-2compactor branch

Conclusion

The branching change does not bring any significant performance regression
The single compactor scenario can exhaust cpu load
The multi compactor scenarios cpu load is balance

We ran nexmark-benchmark against all the queries and found no significant performance regression,  so we don't think there are too many negative performance gains from this pr change.
Refer to the nexmark-bs-15-105-affinity-heartbeat image for the results.


Actions added to items

Different items Hybrid/Magic/Tech/Goods can have need for the actions item menu, to track active state, or to track usage.
Also there are some items that have both passive and active effects, and currently there aren't modifiers that can remain on while an item is inactive
Actions menu should be added to said items, including the consumable usage settings that consumables have.
A new modifier type that can be constant even if an active feature/item is off, would solve passive effects that should remain even while a item's active state is off.

This is partially implemented in https://github.com/foundryvtt-starfinder/foundryvtt-starfinder/pull/1108

Gonna assume this was closed by #1108


dns/bind: Fix multiple select on Recursion field

The Recursion field on the Configuration page does not allow multiple selections. This was added in 1.26 for Transfers and Queries but is broken for Recursion. The model already has <Multiple>Y</Multiple> and this PR fixes the controller.

Merged, thanks! ❤


Question about access modifier

Hi. I have a question. When I am trying to use any access modifier for an explicit interface, I'm getting an error: "The modifier <modifier_name> is not valid for explicit interface implementation".
As I understand, I should not try to do so, but. What is the access modifier used implicitly?
Logically, there must be only one valid access modifier - "public". But it does not work either.

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

ID: bda601c2-3dbe-4ad1-db39-670cff3b654c
Version Independent ID: 092fce57-ea16-c7a6-c85d-f6c111eba4eb
Content: Explicit Interface Implementation (C# Programming Guide)
Content Source: docs/csharp/programming-guide/interfaces/explicit-interface-implementation.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for your comment, @vladkolodka. An explicit interface implementation does not have an access modifier since it is not accessible as a member of the type in which it is defined. Instead, it is only accessible when called through an instance of the interface. Interface members are always public.
Attempting to define an access modifier results in compiler error CS0106. This is the same compiler error that results when you attempt to attach an access modifier to a member in an interface definition -- and it is produced for the same reason.
I hope that this helps to answer your question.
I'm closing this issue, since it doesn't have a documentation impact.

Hi,
See the below program. How should I access the I2 and I3 interface methods?
using System;
namespace InterfaceExmple
{
interface I1
{
void Show();
}
interface I2 : I1
{
    new void Show();
}

interface I3 : I2
{
    new void Show();
}

class Test : I3
{
    public void Show()
    {
        Console.WriteLine("I1 Show");
    }

   void I2.Show()
    {
        Console.WriteLine("I2 Show");
    }

    void I3.Show()
    {
        Console.WriteLine("I3 Show");
    }
}
class Program
{
    static void Main(string[] args)
    {
        Test obj = new Test();
        obj.Show();
        obj.I2.Show();
        Console.ReadLine();
    }
}

}


Add hops-template-graphql

This PR adds the new hops-template-graphql to enable quick
set-up of graphql clients.
It also changes the order in which getTemplateData and
ReactDOM.renderToString is called, to enable other implementations
to do additional tasks in getTemplateData which will prepare the
render tree.

This is an alternative implementation to the proposed API change in #305


Only re-layout when required

Often, a redraw is enough.
Goal: improve performance, reduce flickering when only a small window is changed.

Latest improvements to wide-characters meant computing the width of text, which makes layout more expensive. The lorem example is now slow to scroll, so this becomes a priority.

Actually, an alternative would be to make the layout phase much faster, by having each view type cache its result.
Pro: less architecture work, caching is local to each view
Con: still call clear() on every frame, needs caching in many views.

Anyway, things that should not require a re-layout:

Operations affecting a different layer in a StackView
Selection change
Scrolling

Things that do require re-layout:

Window resize event
View modification

More than a localised re-layout detection, we may want to localise the layout itself, so that in the event of a large textView, we don't relayout it every time we add of modify a popup over it.

On the other hand, many computations are duplicated between get_min_size and layout.
Caching the results (so that layout can reuse the results from get_min_size) could bring some additional speedups?

So let's aim for zero work duplication:

TextView will keep in memory the last size request. It will only recompute the layout if the request change.

This means get_min_size must take a &mut self, or use some trick for interior mutability. Since the UI is single-threaded, a refcell may suffice...

Actually, this will already remove most of the slow-down with layout... LinearLayout is another potentially slow one that we'll need to take care of next.

So TextView now caches its row after either get_min_size or layout will keep the result to avoid recomputation. The lorem example is now much faster to scroll (though it still clears the screen a bit too much).

Formally, there are two solutions:

Add a method to the View trait to detect need for re-layout. View groups use this to selectively relayout their children.
Add an implicit contract to the layout and get_min_size methods: when called successively with the same parameters, they are fast.

The cache implemented in the TextView is part of the second solution. In this situation, view groups have to be careful how they measure their children.
In a stable scrolling situation, we want to avoid any re-layout. This means view groups can only call their children's get_min_size with the same parameter.
Let's now say deep down the tree, a children was changed (his text content got updated, children got added, ...). Without a separate channel to invalidate the layout, the only communication possible is through the get_min_size (or layout) methods, which becomes quickly impractical.
This means the second solution is not sufficient. Damn.
Let's do the first one then.

needs_relayout has been added to the View trait.


Crackling sounds when changing params using Worldline (Mac?)

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
Editing parameters using the Classic render seems to be working fine, but if I have either edited any pitchbends or changed certain parameters using Worldline-R some notes seem to only produce scratcy and crackly sounds. If I haven't edited any parameters or changed pitchbends, it seems to work as normal.  Stuff like velocity that both renderers can handle seem to also work as normal.
I can tell when this is happening without listening when I turn on the audio waveform (saves my ears, lol)

Changing the pitchbends even the slightest amount seems to change the sound completely. I clicked one pitchbend and now it looks like this.

Still not making good sounds, but different.  Any help is appreciated!
Explains how to reproduce the bug

Open any ustx file, with any voicebank, any phenomizer
Set renderer to WORLDLINE-R
Edit a few pitchbends and a parameter (such as TENC or GENC)
Turn on audio waveforms, editing pitch points will change sound drastically

OS & Version
macOS 13.6.7
Logs
Sorry this was really long so I trimmed it. This seems to be a point where I am changing pitch points and the audio gets messed up and fixed and messed up again. I can add more from the logs if needed, I don't know what to look for.
2024-08-12 22:57:20.068 -04:00 [INF] ExecuteCmd Add pitch point
2024-08-12 22:57:20.097 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.148 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.251 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.279 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.307 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.334 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.364 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.392 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.421 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.448 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.478 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:20.505 -04:00 [INF] undoGroup ended
2024-08-12 22:57:20.505 -04:00 [INF] SchedulePreRender
2024-08-12 22:57:20.505 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:57:20.757 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:20.757 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:26.735 -04:00 [INF] undoGroup started
2024-08-12 22:57:26.735 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:26.793 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:26.823 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:57:26.850 -04:00 [INF] undoGroup ended
2024-08-12 22:57:26.850 -04:00 [INF] SchedulePreRender
2024-08-12 22:57:26.850 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:57:27.092 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:27.092 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:32.139 -04:00 [INF] StartPlayback at 00:00:54.8437500
2024-08-12 22:57:38.605 -04:00 [INF] Autosave /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:57:38.919 -04:00 [INF] Autosaved /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:57:39.381 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:39.390 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:39.428 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:39.436 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:39.517 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:39.517 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:39.574 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:39.574 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:40.741 -04:00 [INF] StartPlayback at 00:00:00.7812500
2024-08-12 22:57:41.653 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:41.653 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:41.674 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:41.674 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:41.712 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:41.712 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:57:41.715 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:57:41.715 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:06.018 -04:00 [INF] undoGroup started
2024-08-12 22:58:06.019 -04:00 [INF] ExecuteCmd Add pitch point
2024-08-12 22:58:06.050 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:06.080 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:06.118 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:06.151 -04:00 [INF] undoGroup ended
2024-08-12 22:58:06.151 -04:00 [INF] SchedulePreRender
2024-08-12 22:58:06.151 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:58:06.401 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:06.405 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:06.890 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:06.891 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:07.375 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:07.375 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:07.535 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:07.535 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:08.920 -04:00 [INF] Autosave /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:58:09.203 -04:00 [INF] Autosaved /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:58:11.802 -04:00 [INF] undoGroup started
2024-08-12 22:58:11.802 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.018 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.054 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.088 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.137 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.189 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.222 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.256 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.287 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.320 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.418 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:12.451 -04:00 [INF] undoGroup ended
2024-08-12 22:58:12.451 -04:00 [INF] SchedulePreRender
2024-08-12 22:58:12.451 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:58:12.698 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:12.698 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:13.146 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:13.146 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:13.636 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:13.637 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:13.814 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:13.814 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:14.563 -04:00 [INF] StartPlayback at 00:00:22.7343750
2024-08-12 22:58:15.470 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:15.471 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:15.525 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:15.525 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:15.528 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:15.529 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:15.572 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:15.573 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:39.204 -04:00 [INF] Autosave /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:58:39.474 -04:00 [INF] Autosaved /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:58:46.936 -04:00 [INF] undoGroup started
2024-08-12 22:58:46.936 -04:00 [INF] ExecuteCmd Add pitch point
2024-08-12 22:58:46.972 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:47.035 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:47.067 -04:00 [INF] ExecuteCmd Delete pitch point
2024-08-12 22:58:47.091 -04:00 [INF] undoGroup ended
2024-08-12 22:58:47.091 -04:00 [INF] SchedulePreRender
2024-08-12 22:58:47.092 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:58:47.338 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:47.339 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:47.510 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:47.510 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:48.017 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:48.017 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:48.190 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:48.191 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:48.403 -04:00 [INF] undoGroup started
2024-08-12 22:58:48.403 -04:00 [INF] ExecuteCmd Add pitch point
2024-08-12 22:58:48.435 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:48.518 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:48.551 -04:00 [INF] undoGroup ended
2024-08-12 22:58:48.551 -04:00 [INF] SchedulePreRender
2024-08-12 22:58:48.551 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:58:48.818 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:48.818 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:52.484 -04:00 [INF] undoGroup started
2024-08-12 22:58:52.484 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:52.600 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 22:58:52.626 -04:00 [INF] undoGroup ended
2024-08-12 22:58:52.626 -04:00 [INF] SchedulePreRender
2024-08-12 22:58:52.626 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 22:58:52.875 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:58:52.875 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:58:57.051 -04:00 [INF] StartPlayback at 00:00:54.8437500
2024-08-12 22:59:04.559 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:59:04.559 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:59:04.635 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:59:04.635 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:59:04.736 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:59:04.736 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:59:04.801 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 22:59:04.802 -04:00 [INF] Publish notification Part rendered.
2024-08-12 22:59:09.474 -04:00 [INF] Autosave /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:59:09.790 -04:00 [INF] Autosaved /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 22:59:39.791 -04:00 [INF] Autosave skipped.
2024-08-12 23:00:09.792 -04:00 [INF] Autosave skipped.
2024-08-12 23:00:39.794 -04:00 [INF] Autosave skipped.
2024-08-12 23:01:09.795 -04:00 [INF] Autosave skipped.
2024-08-12 23:01:39.796 -04:00 [INF] Autosave skipped.
2024-08-12 23:02:09.452 -04:00 [INF] undoGroup started
2024-08-12 23:02:09.518 -04:00 [INF] undoGroup ended
2024-08-12 23:02:09.518 -04:00 [INF] SchedulePreRender
2024-08-12 23:02:09.518 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 23:02:09.570 -04:00 [INF] undoGroup started
2024-08-12 23:02:09.571 -04:00 [INF] Publish notification Select expression tenc
2024-08-12 23:02:09.571 -04:00 [INF] Publish notification Select expression brec
2024-08-12 23:02:09.574 -04:00 [INF] Publish notification Select expression genc
2024-08-12 23:02:09.574 -04:00 [INF] Publish notification Select expression eng
2024-08-12 23:02:09.575 -04:00 [INF] Publish notification Select expression vel
2024-08-12 23:02:09.632 -04:00 [INF] Publish notification Load part
2024-08-12 23:02:09.633 -04:00 [INF] Publish notification Select expression brec
2024-08-12 23:02:09.633 -04:00 [INF] Publish notification Select expression genc
2024-08-12 23:02:09.653 -04:00 [INF] undoGroup ended
2024-08-12 23:02:09.653 -04:00 [INF] SchedulePreRender
2024-08-12 23:02:09.653 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 23:02:09.797 -04:00 [INF] Autosave skipped.
2024-08-12 23:02:09.918 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:09.918 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:10.145 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:10.145 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:10.676 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:10.676 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:10.862 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:10.862 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:13.739 -04:00 [INF] StartPlayback at 00:00:54.8828125
2024-08-12 23:02:14.512 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:14.513 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:14.591 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:14.591 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:14.708 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:14.709 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:14.777 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:14.777 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:29.062 -04:00 [INF] StartPlayback at 00:00:49.3750000
2024-08-12 23:02:29.901 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:29.902 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:29.954 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:29.955 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:30.062 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:30.064 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:30.139 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:30.140 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:35.685 -04:00 [INF] undoGroup started
2024-08-12 23:02:35.750 -04:00 [INF] undoGroup ended
2024-08-12 23:02:35.751 -04:00 [INF] SchedulePreRender
2024-08-12 23:02:35.751 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 23:02:35.819 -04:00 [INF] undoGroup started
2024-08-12 23:02:35.820 -04:00 [INF] Publish notification Select expression tenc
2024-08-12 23:02:35.821 -04:00 [INF] Publish notification Select expression brec
2024-08-12 23:02:35.821 -04:00 [INF] Publish notification Select expression genc
2024-08-12 23:02:35.822 -04:00 [INF] Publish notification Select expression eng
2024-08-12 23:02:35.822 -04:00 [INF] Publish notification Select expression vel
2024-08-12 23:02:35.886 -04:00 [INF] Publish notification Load part
2024-08-12 23:02:35.886 -04:00 [INF] Publish notification Select expression brec
2024-08-12 23:02:35.886 -04:00 [INF] Publish notification Select expression genc
2024-08-12 23:02:35.900 -04:00 [INF] undoGroup ended
2024-08-12 23:02:35.900 -04:00 [INF] SchedulePreRender
2024-08-12 23:02:35.900 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 23:02:36.176 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:36.178 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:36.410 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:36.411 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:37.019 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:37.021 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:37.235 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:37.236 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:39.799 -04:00 [INF] Autosave skipped.
2024-08-12 23:02:41.768 -04:00 [INF] undoGroup started
2024-08-12 23:02:41.768 -04:00 [INF] ExecuteCmd Add pitch point
2024-08-12 23:02:41.799 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:41.901 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:41.937 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:41.972 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:42.005 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:42.053 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:42.108 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:42.144 -04:00 [INF] ExecuteCmd Move pitch point
2024-08-12 23:02:42.174 -04:00 [INF] undoGroup ended
2024-08-12 23:02:42.174 -04:00 [INF] SchedulePreRender
2024-08-12 23:02:42.174 -04:00 [INF] Publish notification Pre-render notification.
2024-08-12 23:02:42.426 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:42.426 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:44.179 -04:00 [INF] StartPlayback at 00:00:59.1015625
2024-08-12 23:02:51.591 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:51.592 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:51.649 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:51.652 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:51.755 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:51.756 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:02:51.831 -04:00 [WRN] Part rendered. not on main thread
2024-08-12 23:02:51.832 -04:00 [INF] Publish notification Part rendered.
2024-08-12 23:03:09.800 -04:00 [INF] Autosave /Users/admin/Documents/utau projects/magical girl-autosave.ustx.
2024-08-12 23:03:10.098 -04:00 [INF] Autosaved /Users/admin/Documents/utau projects/magical girl-autosave.ustx.

This is unfortunately on the Known Bugs page. That means the error is known, but the cause isn't and there hasn't been much headway in it being fixed. Part of that is due to a lack of Mac contributors or testers at the moment, making it pretty hard to investigate.
There are other issues about this, but it may be helpful if you could potentially attach a video of you reproducing the error, ideally with sound, so we can understand a bit more about it.

@BagelHero Ah I guess I didn't read it too closely, thank you for letting me know. I can get a video of it though, sure.


XA failure of PostgreSQL

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
4.0.0-RC3-SNAPSHOT
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-Proxy
Expected behavior
XA transaction succeed for PostgreSQL
Actual behavior

Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).

I have found the root cause. postgreSQL needs to config max_prepared_transactions in postgresql.conf.  since default value is zero, XA feature have been disabled.

when I test Sharding-JDBC using Postgresql XA, another problem have occurred. I will submit a PR to fix it as soon as possible

see #3825


Re-configuration of bitcoin-bot-buy-if-elon-tweets for a Telegram group

Hello CyberPunkMetalHead, I just found your GitHub profile and got interested in a script based on Elon's Tweets. However, he's being quite unreliable recently... how about if I would like to connect Binance to Telegram account with your bitcoin-bot-buy-if-elon-tweets and execute buy/sell orders according to a message from a certain group? Could you help me to re-design you script for that?
Thank you very much!
Simon

Telegram RPC commands could be a good idea - but I doubt it is a high priority for Andrei - dm me @apminner on tg if want to collaborate


IP override for Google Analytics 4

The IP override works fine on Google Analytics but not on GA4.
All hits are shown from the server IP.

Hello! That’s because Google’s measurement protocol v2 does not yet support
&uip URL parameter. However, with some magic applied, location override
already works in dataunlocker.com for GA4 as well.
On Mon, 15 Feb 2021 at 17:42, Ronen Teva<EMAIL_ADDRESS>wrote:

The IP override works fine on Google Analytics but not on GA4.
All hits are shown from the server IP.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dataunlocker/save-analytics-from-content-blockers/issues/25,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGCCSA5CYQGCCMAVU4UIJ3S7E6FVANCNFSM4XU4TQKQ
.

Can't this magic be a open-sourced? Or is that a selling point for the paid version?

Not a selling point. I feel uncomfortable open-sourcing things which will change just tomorrow (read: which are in alpha) and which will be removed from the API completely at some point. Within DataUnlocker, we just can afford experimenting, as once it changes there will be an immediate fix from our side.
The latest Measurement Protocol spec should very soon transition to beta with uip parameter supported. Please wait and take it as "there is no way to do it before MPv2 goes beta". That's Google's problem that they push GAv2 to their customers before updating the protocol at the end of the day :P
P.S. DataUnlocker isn't the paid version of this open sourced app/container; it uses a principally different and a better approach to proxy "everything", without any common code.

Got it, that makes sense.
Thanks for explaining!

Regarding this issue, I understand your comments, @ZitRos, how https://developers.google.com/tag-manager/serverside manage to accomplish this task then?

In fact, I've never tried Google's server-side tagging solution. From here I can see that it doesn't solve the ad blocking problem (replacing the domain isn't enough).
To answer your question, @julesGoullee, did you try server-side GTM with GA4? Does it work with locations?

I didn't try it too. I thought the purpose of this is to bypass adblocker following the explanation schema. Do you have any private info about when the new GA4 will support uip params ? Seems this issue is open for months, I guess the GA4 homepage show alpha for months as well

I can't share the release dates nor any other related info (obviously because of the company's policies and the common sense).
Though to answer the original question of this issue, I think it is no secret now that Google tends to prefix alpha/beta URL parameters with underscore _, so does &_uip=x.x.x.x work well for Google Analytics 4. I am pretty sure server-side GTM uses it as well if it works with GA4.
I would hold from updating the code of this open-sourced container with _uip, however, given that the new protocol release already takes months we can do it I think. Does it sound good?

Wow. Didn't know it before, was a secret at least for me! I've tried it out, works perfectly! I can make a pr for this repo, definitely not a big deal to prefix the parameter, I guess everyone will appreciate having it right now when it goes officially released reverting these changes should be smooth IMO.
Thx for your help

Yes please go ahead and contribute! I wish I have added some very basic tests to this repo when I started it (I test it manually) but this should be a very straightforward fix.

Let's go! https://github.com/dataunlocker/save-analytics-from-content-blockers/pull/28

This is now deployed. @julesGoullee are you using the container? Please confirm it works, I didn't run it.

I started with the container, work perfectly then I faced issues, I went to deployment from source, I think now I will consider moving back to the container bundle

Let me know how it goes - I'll keep the issue open for now.

I assume it's verified now. Thanks!

The changes work well, the container I didn't test it yet. I will contact you later if I have any issue with the container

Thanks!
On Tue, 29 Jun 2021 at 07:51, jules goullée @.***>
wrote:

The changes work well, the container I didn't test it yet. I will contact
you later if I have any issue with the container
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/dataunlocker/save-analytics-from-content-blockers/issues/25#issuecomment-870233170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGCCSHN4RYFCEJBHQAFPITTVFGN3ANCNFSM4XU4TQKQ
.

Can someone confirm if _uip is still working?

Hi @wilsonpage! You should be able to confirm it easily by making a hit. Then, in GA realtime panel you'll see the location corresponding to that IP.

Hi @wilsonpage! You should be able to confirm it easily by making a hit. Then, in GA realtime panel you'll see the location corresponding to that IP.

Ah, it's working for me now! I was trying to use the official GA4 Measurement Protocol, but the API seems half-baked and doesn't have all the options the unofficial/private API (used in gtag.js) has.

Could you document it?

@iammattmartin this is my test script I was using:
/* eslint-disable no-console */
import fetch from 'node-fetch';

(async () => {
  const url = new URL('https://google-analytics.com/g/collect?v=2');

  url.searchParams.set('tid', 'G-BLVBF7CC76');
  // url.searchParams.set('gtm', '2oe6t0');
  url.searchParams.set('_z', 'ccd.v9B');

  // client id
  url.searchParams.set('cid', '1656610788');

  // session id
  url.searchParams.set('sid', '1656610180');

  // user language
  url.searchParams.set('ul', 'en-gb');

  // screen resolution
  url.searchParams.set('sr', '1440x900');

  //
  url.searchParams.set('_s', '1');

  // Count of sessions recorded by GA4. This value increases by one each time a new session is detected ( when the session expires )
  url.searchParams.set('sct', '1');

  // session engagement
  url.searchParams.set('seg', '1');

  // document location
  url.searchParams.set('dl', 'https://example.com/3');

  // document referrer
  url.searchParams.set('dr', 'https://google.com/');

  // document title
  url.searchParams.set('dt', 'Example title');

  // event name
  url.searchParams.set('en', 'page_view');

  // ?
  url.searchParams.set('_nsi', '1');

  // user id (determines location)
  url.searchParams.set('uip', '<IP_ADDRESS>');
  url.searchParams.set('_uip', '<IP_ADDRESS>');

  // event parameters
  url.searchParams.set('epn.artistId', '123');

  // ?
  url.searchParams.set('_ee', '1');

  // first_view
  // url.searchParams.set('_fv', '1');

  // session_start
  // url.searchParams.set('_ss', '1');

  console.log(url);
  // console.log(
  //   'https://google-analytics.com/g/collect?v=2&tid=G-QS6H9Y8HYR&gtm=2oe6t0&_z=ccd.v9B&cid=1656610787&ul=en-gb&sr=1440x900&_s=1&sid=1656610180&sct=1&seg=1&dl=https%3A%2F%2Fsongwhip.com%2Fbat&dr=https%3A%2F%2Fsongwhip.com%2F&dt=Songwhip%20Bat&en=page_view&_nsi=1&_uip=<IP_ADDRESS>&_ee=1'
  // );

  // console.log(url.toString());

  const res = await fetch(url.toString(), {
    method: 'POST',
    headers: {
      Accept: '*/*',
      'Cache-Control': 'no-cache',
      Pragma: 'no-cache',
      'Sec-Ch-Ua-Mobile': '?0',
      'Sec-Fetch-Dest': 'empty',
      'Sec-Fetch-Mode': 'no-cors',
      'Sec-Fetch-Site': 'cross-site',
      'User-Agent':
        'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36',
    },
  });

  console.log(res.status);
})();

This cheatsheet is also handy:
https://www.thyngster.com/ga4-measurement-protocol-cheatsheet/

Thanks but in terms of integration within this specific project. Did you make changes to the .js? Would be good if you could submit  or fork it so people can use :)

Ah ok, thanks.

I'm making requests to www.google-analytics.com/mp/collect with the following parameters:
Query:

_uip
uip

Header:

X-Forwarded-For
User-Agent

Body:

user_id (unique for each user, custom value)

Despite these details, Google Analytics is only recording hits from my server as a single user.
I made sure that all IP values are the IP of the user.
I'm using the same value for client_id as I am for user_id.
Is there a step or setting I'm overlooking?

@ThiloReintjes IP overrides work at least for /g/collect endpoint (it follows almost the same spec as /mp/collect). I doubt that /mp/collect specifically supports IP overrides, as even this issue is P4.


[ISSUE #2811] Fix the wrong topic was consumed in the DefaultMessageStoreTest test program

for issue #2811

Coverage decreased (-0.07%) to 51.823% when pulling 0b6bd183bfffb17f8cb112ae6d080e908ebbca1e on BurningCN:fix_test_consume_wrong_topic into ba74c497fa180499f4ab7a727f03776caa61a637 on apache:develop.

Coverage decreased (-0.07%) to 51.823% when pulling 0b6bd183bfffb17f8cb112ae6d080e908ebbca1e on BurningCN:fix_test_consume_wrong_topic into ba74c497fa180499f4ab7a727f03776caa61a637 on apache:develop.

Codecov Report

Merging #2824 (0b6bd18) into develop (1fbccd1) will increase coverage by 0.02%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2824      +/-   ##
=============================================
+ Coverage      46.74%   46.76%   +0.02%
+ Complexity      3441     3438       -3
=============================================
  Files            307      307
  Lines          29055    29056       +1
  Branches        4171     4172       +1
=============================================
+ Hits           13581    13588       +7
+ Misses         13636    13627       -9
- Partials        1838     1841       +3

Impacted Files
Coverage Δ
Complexity Δ

...ketmq/client/impl/consumer/PullMessageService.java
75.55% <0.00%> (-4.45%)
9.00% <0.00%> (-1.00%)

...a/org/apache/rocketmq/filter/util/BloomFilter.java
59.13% <0.00%> (-2.16%)
25.00% <0.00%> (-1.00%)

...mq/client/consumer/store/LocalFileOffsetStore.java
56.86% <0.00%> (-1.97%)
19.00% <0.00%> (ø%)

...che/rocketmq/namesrv/kvconfig/KVConfigManager.java
59.18% <0.00%> (-1.03%)
11.00% <0.00%> (-1.00%)

.../rocketmq/client/impl/consumer/PullAPIWrapper.java
50.42% <0.00%> (-0.86%)
12.00% <0.00%> (-1.00%)

...org/apache/rocketmq/store/DefaultMessageStore.java
55.61% <0.00%> (-0.85%)
110.00% <0.00%> (ø%)

...etmq/client/latency/LatencyFaultToleranceImpl.java
50.00% <0.00%> (ø)
8.00% <0.00%> (ø%)

...ain/java/org/apache/rocketmq/store/MappedFile.java
50.90% <0.00%> (+0.36%)
52.00% <0.00%> (+1.00%)

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
74.11% <0.00%> (+0.50%)
17.00% <0.00%> (ø%)

.../rocketmq/broker/filter/ConsumerFilterManager.java
73.99% <0.00%> (+1.79%)
33.00% <0.00%> (ø%)

... and 2 more

Continue to review full report at Codecov.

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


Is circular-json suitable for websocket instances?

Let's say we have websocket websocket.on('connection', ws=> bla bla the code ...
Is it possible to serialize ws instance with circular-json? And after deserialization will be ws instance usable?
ws is a nested object with lot of functions and events.

you need to answer these two questions first:

does a websocket contains circular references?
if previous answer is yes, is a websocket serializable as JSON?

But since you asked about this later on

after deserialization will be ws instance usable?

I guess you need to understand what is JSON about, and how it works.
It's not an equivalent of php serialize/unserialize, it represents 4 primitives (string, number, boolean, null) and 2 data structures (objects with string-key/json-value pairs or arrays of json values).
You can, however, use its extra utilities to create your own revival logic and generate new instances while deserializing (assuming you have also a logic to serialize them).

I don't know. Not on comp yet. Just thought about this. A little experiment. If one could complex nested objects to save into any database. And then reuse all that stuff.

You need a mechanism to serialize the instance class, which has to be reachable through a global scope, and deserialize it keeping its state preserved so that all internals should be exposed or JSON will miss that.
This is a different issue than circular references, which is the only thing that CircularJSON solves.


JOB-89 Finished first iteration of slurp

What
Adds a script to pull data from legacy jobbergate database into next-gen database.
Why
In order to move users from the legacy jobbergate apps into Armada, we need to be able to move the data seamlessly.
Task: https://app.clickup.com/t/18022949/JOB-89

Peer Review
Please follow the upstream omnivector documentation concerning
peer-review guidelines.

Really nice work here! Give me the weekend to look it over.

does this code work in case the databases are in different VPCs?

does this code work in case the databases are in different VPCs?

The code-base itself is agnostic of where the upstream databases are. You would have to set up a connection to an RDS instance in a VPC via an openvpn connection. If you needed to connect to a legacy database in one VPC and the nextgen database in another, you would have to configure openvpn client to connect to multiple vpns. I'm not sure how to do that, but this might be a start: https://forums.openvpn.net/viewtopic.php?t=22036

What a useful tool this will be! Really nice work here!

I would like to see some docstrings, other then that I'm +1

I will add some docstrings and then merge. Thanks for taking a look!

This is really awesome @dusktreader. Nice work here!! In the future I think this can be a powerful open source tool as well


fix(can): modify TipActionResponse message order to match the expected order on python-side

Overview
Unfortunately the ordering of the tip action response got messed up somewhere along the way. This caused the ack id to never return anyting other than the default state of 1 for the tip/gear motors.

Codecov Report

Merging #669 (9092719) into main (843296f) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #669   +/-   ##
=======================================
  Coverage   84.69%   84.69%
=======================================
  Files          87       87
  Lines        3751     3751
=======================================
  Hits         3177     3177
  Misses        574      574

Impacted Files
Coverage Δ

include/can/core/messages.hpp
99.22% <100.00%> (ø)

...ttes/core/tasks/gear_move_status_reporter_task.hpp
100.00% <100.00%> (ø)


add snake casing skill

Describe the contribution to the taxonomy
Inspired by https://github.com/instruct-lab/taxonomy/pull/106, added new skills to convert text to

snake case

Input given at the prompt
Convert this text into its Camel case form: congratulation interventionism
blah psychoanalyse idiots chromatics evangelistically interchangeability intercommunicating mickle

Response that was received
A correct answer but with a lot of explanation:
| Snake case, also known as "lowercase" or "kebab-case", is a style of writing where   │
│ all words in a phrase are written in lowercase, with the space removed between the   │
│ words and underscores inserted between each word. This format is commonly used in    │
│ programming languages, file systems, and database schema to make the names of        │
│ variables, functions, directories, and tables more consistent and easier to parse.   │
│ In the given example,                                                                │
│ "CongratulationInterventionismBlahPsychoanalyseIdiotsChromaticsEvangelisticallyInter │
│ changeabilityIntercommunicatingMickle" would be in snake case as                     │
│ "congratulation_interventionism_blah_psychoanalyse_idiots_chromatics_evangelisticall │
│ y_interchangeability_intercommunicating_mickle". Here's how the conversion can be    │
│ done for the given text:                                                             │
│                                                                                │
│ 1. Lowercase all the letters in the phrase.                                          │
│ 2. Remove the spaces between the words.                                              │
│ 3. Insert underscores between each word.                                             │
│                                                                                │
│ Applying these steps to the given text, we get                                       │
│ "congratulation_interventionism_blah_psychoanalyse_idiots_chromatics_evangelisticall │
│ y_interchangeability_intercommunicating_mickle". This format is useful for making    │
│ the names of variables, functions, directories, and tables more consistent and       │
│ easier to parse, especially in programming languages and file systems where the      │
│ length of the names is limited.

Response that is now received instead
TODO: lab generate says Nothing to generate. Exiting.
  ...

Contribution checklist
TODO

[ ] tested contribution with lab generate
[ ] lab generate does not produce any warnings or errors
[x] all commits are signed off (DCO)
[x] the qna.yaml file was linted

Resurrect snake case skill in #224 (and #626) from @juandspy. Testing has shown that this skill did improve the full model performance.

@instructlab-bot precheck

@instructlab-bot generate

To fix this PR run git rebase -i upstream/main and set the operations to:
drop 1966cef feat(synthetic data): Add script to generate synthetic data readme (#650)
drop cc381ec Updating org name from instruct-lab to instructlab (#711)
pick 8bebf9b add snake casing skill

The SDG sample shows the teacher model is not generating correct snake case to train the model.
e.g.
artificial\_intelligence\_applications
human\_computer\_interaction\_design
new_york_city_is\_the\_most\_populous\_city\_in\_the\_united\_states

So this skill does not appear to be a good candidate.


cocoapods？

wish DJI-Mobile-SDK can add cocoapods version

+1

Hi! Thanks for your suggestions, we will consider to add cocoapods support for iOS SDK soon.

Hi, DJI iOS SDK 3.1.1 is now available on Cocoapods, here is the link: https://cocoapods.org/pods/DJI-SDK-iOS

Since the problem is fixed, I will close this issue. Thanks!


Update MLT

Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name: mlt

current version: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/mlt/default.nix#L9
desired version: https://github.com/mltframework/mlt/releases
Notify maintainers
maintainers: @peti @tohl
Note for maintainers
Please tag this issue in your PR.

The weird state is now that we have nixpkgs/pkgs/development/libraries/mlt/default.nix on version 6.26 (not very up to date), and a (cleaner?) nixpkgs/pkgs/development/libraries/mlt/qt-5.nix which was more recently updated to 7.0 by @ttuegel . Latest released version is 7.2.
Where do we go from there? Can we drop the 6.* versions?

CC @goibhniu (maintainer of mlt-qt5)

I see both mlt and libsForQt5.mlt are on 7.20 in stable and 7.22 in unstable, so this issue looks like it can be closed.

Close this  as mlt package is updated.


st2chatops cannot be installed without st2 repo on a separate instance

We allow installation of st2chatops on a separate instance : https://github.com/StackStorm/st2chatops/blob/master/st2chatops.env#L23.
However, it depends on st2 package as st2 creates /var/log/st2/.
Discovered here : https://github.com/StackStorm/ansible-st2/pull/125#discussion_r105504625
RUNNING HANDLER [st2chatops : restart st2chatops] ******************************
fatal: [centos6]: FAILED! => {"changed": false, "failed": true, "msg": "touch: cannot touch `/var/log/st2/st2chatops.log': No such file or directory\nrunuser: group st2 does not exist\n"}

Saying that, st2chatops package should try to create /var/log/st2/ dirs as well as st2 user if it doesn't exists yet.

It's actually the same (duplicate) as 1 yr. ago reported Issue: https://github.com/StackStorm/st2chatops/issues/31

Resolved by https://github.com/StackStorm/st2chatops/pull/114


Raycast 3d

Godot version
v3.5 RC 3
System information
Windows 10, Nvidia Geforce gtx 560
Issue description
get_name not working
Here Is The Code I Use
extends RayCast

func _physics_process(delta):
	if Input.is_action_just_pressed("interact"):
		if is_colliding():
			var obj = get_collider()
			print(obj.get_name())

Steps to reproduce
I Tried Printing The Raycast Collider But It DInt Worked
Minimal reproduction project
No response

Collider is the physics body. Most likely you want their parent.
Not a bug and shouldn't be reported here but asked on the forums.

K Try My Best Not To Post Again Here


Scooter has been deprecated

Scooter has been deprecated
http://dropbox.github.io/scooter/index.html

I added a note about Scooter being depracated. Thank you!


error since few weeks

Hi,
since few weeks, this error occured for this entry.

Others have no problem to download, it's the only one and until few weeks ago there was no error on it.
Could you take a look at it, please ? :)
Thanks :)

There seems to be a problem with the node-pureimage library. I have reported the problem and will apply it here as soon as it is fixed.
If it is not fixed after a few days (or weeks), the library may be changed.


Attempt login to MosAPI via all available TLDs

There's no reason why we should need a TLD as input here because it doesn't actually matter which one we use (they all have the same password).

This change is

If we do this, we don't need to pass the TLD in when running the cron job like in #139

Lai, I think we should be good for a review here. PTAL, thanks.

Note: I will need to modify this to hard-code the password, deploy to alpha and test it, then remove the alpha-specific cron.xml file change before merging

Testing is done and it worked, see https://pantheon.corp.google.com/logs/viewer?expandAll=false&project=domain-registry-alpha&minLogLevel=0&timestamp=2019-07-03T15:27:10.770000000Z&customFacets=&limitCustomFacetWidth=true&advancedFilter=protoPayload.taskName%3D"20641833e37c58d8071412cb23e44c54"
protoPayload.taskQueueName%3D"__cron"
&dateRangeStart=2019-07-03T14:27:12.193Z&dateRangeEnd=2019-07-03T15:27:12.193Z&interval=PT1H&scrollTimestamp=2019-07-03T15:26:29.552140000Z


workaround for removing dynamic states

creating dynamic states based on roles on login
.config
sfa.sfastates = $stateProvider;

Under Loginj Ctrl
response after login base on user
response.data = {
  "menu":[
    {
      "NAME":"Dashboard",
      "URL":"parts/dashboard.html"
    },
    {
      "NAME":"Inner Page 1",
      "URL":"parts/innerpage1.html"
    },
    {
      "NAME":"Inner Page 2",
      "URL":"parts/innerpage2.html"
    }
  ],
  "startuppage":"Dashboard"
};

 var menuObj = {};
	   var counter = 0;
	   $rootScope.menus = [];
	   angular.forEach(response.data.menu, function(item) {
	 	  sfa.sfastates.state('side.'+item.NAME, {
	 	        url: '/'+item.NAME,
	 	        templateUrl: item.URL
	 		  });
	 	  counter++;
	   });
	   $state.go("side."+response.data.startuppage);

Everything works perfect but, when once login and logout , it wont login again showing state already defined at
sfa.sfastates.state(....)

only way is to login and let the error comes and then  refresh page and again login
Can we create above steps from code or can we handle its exception ?
searched everywhere , waiting from last 2-3 months , application is in production with over 4 months of development almost had lost angular just because of this, but somehow convinced my manager to stick to angular:P
anyway to reload angular again when coming on login state
Or empty the stateprovider or check if state exist or not , after logout i can empty everything and start fresh
Any work around , anything
Thank You

Why create "dynamic states"? Why not use permissions instead? like have your response define what areas the user can access and then define all the states and add data: acl: something and in the stateChangeStart: if toState.data.something is user.acl.something (not exact code but gives a general idea)

Implemented your idea previously but it didn't suite our needs,
We have separate access control module  only for creating , giving roles to users to access specific pages, assign pages to a user, a department , or a group, or to add pages to the app.  So in future if there are any pages needed to be add , we can add it in the specific folder then just give it the path and assign it to the user.
i am writing inline script and using $controllerProvider.register to register controller when partial pages load with theiir controllers.
Like this
app.js
var sfa =  angular.module('xta', [])
.config(function($controllerProvider){
sfa.registerCtrl = $controllerProvider.register;

// Access stateprovider to add states outside config i.e loginCtrl
sfa.sfastates = $stateProvider;
})

dashboard.html (after login)