[Question] Is there a working windows vm example

Looking for a working yaml for windows. I tried the template, but it did not work when I handed it the following windows image:
windows_server_2012_r2_standard_eval_kvm_20170321.qcow2.gz
I tried the several yaml configurations for launching the windows vm both using the windows template and not. I also tried different boot orders for the windows template. If you have an example yaml for the following Kind that would be much appreciated!
apiVersion: kubevirt.io/v1
kind: VirtualMachine

windows_server_2012r2_essentail.iso + Harvester's built-in windows templates work fine

Thanks @futuretea, but what did you put into the form for the Image field for the basics section?
Can you get the output of the following kubectl command for me as I am more familiar with Kubernetes than Harvester itself:
kubectl get vm <-n namespace you deployed to>  name_of_vm -o yaml

You could also get this by copying and pasting the "Edit yaml" for an example machine you spun up.
This would help me greatly as the form just creates a yaml on the backend.

@futuretea harvester supports gziped format right?

^trying it with the qcow2.gz file since I already had that uploaded, will let you know if it works with qcow2.gz

I was able to verify that your yaml file worked. Thank you so much @futuretea. I am going to continue testing and will update here with what I find, if anything noteworthy.
As a follow up the tgz file did in fact work, and this did work with the rook-ceph storage class providing storage in block volume mode.
Here is my yaml for reference:
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
  annotations:
    kubevirt.io/latest-observed-api-version: v1alpha3
    kubevirt.io/storage-observed-api-version: v1alpha3
    networks.harvester.cattle.io/ips: '[]'
  finalizers:
  - wrangler.cattle.io/VMController.UnsetOwnerOfDataVolumes
  generation: 1
  labels:
    harvester.cattle.io/creator: harvester
  managedFields:
  - apiVersion: kubevirt.io/v1alpha3
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:networks.harvester.cattle.io/ips: {}
        f:finalizers: {}
        f:labels:
          .: {}
          f:harvester.cattle.io/creator: {}
      f:spec:
        .: {}
        f:dataVolumeTemplates: {}
        f:running: {}
        f:template:
          .: {}
          f:metadata:
            .: {}
            f:annotations:
              .: {}
              f:harvester.cattle.io/diskNames: {}
              f:harvester.cattle.io/sshNames: {}
            f:labels:
              .: {}
              f:harvester.cattle.io/creator: {}
              f:harvester.cattle.io/vmName: {}
          f:spec:
            .: {}
            f:domain:
              .: {}
              f:cpu:
                .: {}
                f:cores: {}
                f:sockets: {}
                f:threads: {}
              f:devices:
                .: {}
                f:disks: {}
                f:inputs: {}
                f:interfaces: {}
              f:resources:
                .: {}
                f:requests:
                  .: {}
                  f:memory: {}
            f:hostname: {}
            f:networks: {}
            f:volumes: {}
    manager: harvester
    operation: Update
  - apiVersion: kubevirt.io/v1alpha3
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:kubevirt.io/latest-observed-api-version: {}
          f:kubevirt.io/storage-observed-api-version: {}
      f:status:
        .: {}
        f:conditions: {}
        f:created: {}
        f:ready: {}
        f:volumeSnapshotStatuses: {}
    manager: virt-controller
    operation: Update
  name: win-1
  namespace: default
  selfLink: /apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachines/win-1
spec:
  dataVolumeTemplates:
  - apiVersion: cdi.kubevirt.io/v1alpha1
    kind: DataVolume
    metadata:
      annotations:
        cdi.kubevirt.io/storage.import.requiresScratch: "true"
        harvester.cattle.io/imageId: default/image-dks4b
      creationTimestamp: null
      name: win-1-disk-0-l8x5t
    spec:
      pvc:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 50Gi
        volumeMode: Filesystem
      source:
        http:
          url: http://minio.harvester-system:9000/vm-images/image-dks4b
  running: true
  template:
    metadata:
      annotations:
        harvester.cattle.io/diskNames: '["win-1-disk-0-l8x5t"]'
        harvester.cattle.io/sshNames: '[]'
      creationTimestamp: null
      labels:
        harvester.cattle.io/creator: harvester
        harvester.cattle.io/vmName: win-1
    spec:
      domain:
        cpu:
          cores: 4
          sockets: 1
          threads: 1
        devices:
          disks:
          - disk:
              bus: virtio
            name: disk-0
          inputs:
          - bus: usb
            name: tablet
            type: tablet
          interfaces:
          - macAddress: 02:00:00:07:9c:48
            masquerade: {}
            model: virtio
            name: default
        machine:
          type: q35
        resources:
          requests:
            memory: 8Gi
      hostname: win-1
      networks:
      - name: default
        pod: {}
      volumes:
      - dataVolume:
          name: win-1-disk-0-l8x5t
        name: disk-0
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-03-30T13:13:09Z"
    status: "True"
    type: Ready
  created: true
  ready: true
  volumeSnapshotStatuses:
  - enabled: false
    name: disk-0
    reason: No Volume Snapshot Storage Class found for volume [disk-0]
ubuntu@local-harbor:~/harvester/examples/vm/windows$ ls
internet-window.yaml  windows-2.yaml  windows-3.yaml  windows-4.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ vim internet-window.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ vim internet-window.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ kubectl create -f internet-window.yaml
virtualmachine.kubevirt.io/win-2 created
ubuntu@local-harbor:~/harvester/examples/vm/windows$ cp internet-window.yaml internet-window-1.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ vim internet-window
ubuntu@local-harbor:~/harvester/examples/vm/windows$ vim internet-window-1.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ ls
internet-window-1.yaml  internet-window.yaml  windows-2.yaml  windows-3.yaml  windows-4.yaml
ubuntu@local-harbor:~/harvester/examples/vm/windows$ cat internet-window-1.yaml
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
  annotations:
    kubevirt.io/latest-observed-api-version: v1alpha3
    kubevirt.io/storage-observed-api-version: v1alpha3
    networks.harvester.cattle.io/ips: '[]'
  finalizers:
  - wrangler.cattle.io/VMController.UnsetOwnerOfDataVolumes
  generation: 1
  labels:
    harvester.cattle.io/creator: harvester
  managedFields:
  - apiVersion: kubevirt.io/v1alpha3
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:networks.harvester.cattle.io/ips: {}
        f:finalizers: {}
        f:labels:
          .: {}
          f:harvester.cattle.io/creator: {}
      f:spec:
        .: {}
        f:dataVolumeTemplates: {}
        f:running: {}
        f:template:
          .: {}
          f:metadata:
            .: {}
            f:annotations:
              .: {}
              f:harvester.cattle.io/diskNames: {}
              f:harvester.cattle.io/sshNames: {}
            f:labels:
              .: {}
              f:harvester.cattle.io/creator: {}
              f:harvester.cattle.io/vmName: {}
          f:spec:
            .: {}
            f:domain:
              .: {}
              f:cpu:
                .: {}
                f:cores: {}
                f:sockets: {}
                f:threads: {}
              f:devices:
                .: {}
                f:disks: {}
                f:inputs: {}
                f:interfaces: {}
              f:resources:
                .: {}
                f:requests:
                  .: {}
                  f:memory: {}
            f:hostname: {}
            f:networks: {}
            f:volumes: {}
    manager: harvester
    operation: Update
  - apiVersion: kubevirt.io/v1alpha3
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:kubevirt.io/latest-observed-api-version: {}
          f:kubevirt.io/storage-observed-api-version: {}
      f:status:
        .: {}
        f:conditions: {}
        f:created: {}
        f:ready: {}
        f:volumeSnapshotStatuses: {}
    manager: virt-controller
    operation: Update
  name: win-1
  namespace: default
  selfLink: /apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachines/win-1
spec:
  dataVolumeTemplates:
  - apiVersion: cdi.kubevirt.io/v1alpha1
    kind: DataVolume
    metadata:
      annotations:
        cdi.kubevirt.io/storage.import.requiresScratch: "true"
        harvester.cattle.io/imageId: default/image-dks4b
      creationTimestamp: null
      name: win-1-disk-0-l8x5t
    spec:
      pvc:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 50Gi
        volumeMode: Filesystem
      source:
        http:
          url: http://minio.harvester-system:9000/vm-images/image-dks4b
  running: true
  template:
    metadata:
      annotations:
        harvester.cattle.io/diskNames: '["win-1-disk-0-l8x5t"]'
        harvester.cattle.io/sshNames: '[]'
      creationTimestamp: null
      labels:
        harvester.cattle.io/creator: harvester
        harvester.cattle.io/vmName: win-1
    spec:
      domain:
        cpu:
          cores: 4
          sockets: 1
          threads: 1
        devices:
          disks:
          - disk:
              bus: virtio
            name: disk-0
          inputs:
          - bus: usb
            name: tablet
            type: tablet
          interfaces:
          - macAddress: 02:00:00:07:9c:48
            masquerade: {}
            model: virtio
            name: default
        machine:
          type: q35
        resources:
          requests:
            memory: 8Gi
      hostname: win-1
      networks:
      - name: default
        pod: {}
      volumes:
      - dataVolume:
          name: win-1-disk-0-l8x5t
        name: disk-0
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-03-30T13:13:09Z"
    status: "True"
    type: Ready
  created: true
  ready: true
  volumeSnapshotStatuses:
  - enabled: false
    name: disk-0
    reason: No Volume Snapshot Storage Class found for volume [disk-0]

@futuretea, it would also be great if there was a "submit your own storage class section" with the caveat that the backup capability may not be supported if you do so.

Because I also have to yank the yaml out of kubernetes upon vm creation and remove that line to get it to work with rook-ceph (see above)

and I mean like, come on, you're all using kubevirt by redhat lol you should probably do your best to at least support partial usage of their storage provisioner :p

@mjschmidt  Since one of harvester's goals is to make it easy to use even for those without knowledge of k8s, the concept of storage class may be complicated for them.

can it just use the default storage class then? @futuretea it is currently hardcoded to use longhorn.

Since there will be more enhancements based on the new features of longhorn, perhaps you can fork harvester-ui yourself

close in favor of #640  (do not create a cloud-init disk when it has an empty value)


Replacing onBeforeAction for onRun for enrollAccount & resetPwd routes

I think this will fix issue #436.

Hello Francis!
not sure about it, but I think in the past was onRun and then we switched to onBeforeAction.
Could you please check the history and see wheter I'm right or wrong?
In any case, this PR should now be done for the iron-routing pacakge

Yes, I remember but I can't say why you did the switch. Using the onRun instead of onBeforeAction actually fixed #436 and it is a similar issue as #173 so I guess the onRun is the solution here.

could you please re-open this on the new useraccounts:iron-routing package?
We should test this as much as we can and provide reproductions for the problem...
Sorry for closing this so fast...


uget(-portable): Update to version 2.2.3-1

I don't know how to access their developer and their website has not been updated since 2.2.1. I don't know why. Is that a problem?

Yes it is. There is no official statement about this file and not even changelog, which indicates usesrs, should not update to this.

Their Ubuntu package has been updated to 2.2.3. Looks like their website is outdated. Here is the changelog. Since it the uget (stable) floder, it should be stable enough to use.

But the changelog do not mention the -1. What does it mean? Why the version format break?

I don't know... Hot fix I guess.

/verify


Clicking backgroundEvent triggers onSelectSlot

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/react-big-calendar-example-forked-vpt5d8
Bug description
Reproduction scenario:

Click BackgroundEvent
Expected: onSelectEvent is called
Actual: onSelectSlot is called, then onSelectEvent is called

This occurs when the calendar has prop selectable or selectable='ignoreEvents'
Expected Behavior
When clicking a backgroundEvent, do not trigger onSelectSlot.
Actual Behavior
When clicking backgroundEvent, first onSelectSlot is called, then onSelectEvent is called
react-big-calendar version
1.12.2
React version
18.3.1
Platform/Target and Browser Versions
Chrome latest
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

@DianaLaa Have a fix here: https://github.com/jquense/react-big-calendar/pull/2619
Root of the issue is that, when determining if onSelectSlot should be triggered, it uses the isEvent function, which only considers a node with class rbc-event as an event, and not rbc-background-event
Although I am not sure if this is actually a bug or working as expected, @jquense might need to chime in here.

This behavior has been in place since background events were introduces. Because there are people that use this we cannot change it to ignore it. However we did make changes to the onSelectEvent to provide details to differentiate if you need to ignore. As the documentation on that link states

Clicking on a backgroundEvent will also fire the onSelectEvent callback. It will also receive the backgroundEvent as the event object, but contain a isBackgroundEvent property set to true. This will allow you to distinguish between a background event and a regular event within your onSelectEvent handler.

@geraldhoxha95 And yes, onSelectSlot should fire, as events would overlay on top of background events. (such as using them to show availability time frames)

Hello, thank you for your investigation and quick replies. I understand your hesitation in introducing a breaking change.
I've digged some deeper into our production code and I have some follow-up questions I hope you're willing to provide a little support with:

Is there some way I can detect in my onSelectSlot handler that a backgroundEvent was clicked and that I can abort the handler because onSelectEvent is going to come to pass, too? (I.e. don't show a "Create new event" dialog, because the "Background event details" dialog needs to be shown)
Is there a scenario where onSelectEvent is not triggered after onSelectSlot was handled? Is there a check of detached handler? This seems to happen in our production code. However, in the codesandbox I created for this ticket (see above) both handlers are called. I've tried to look into react-big-calendar source code to find this answer but I'm not familiar with it so I haven't wrapped my head around how it all ties together.

Lastly, some curiosity: Could you help me understand with an example what is the use case for triggering both onSelectSlot and onSelectEvent when the user clicks a background event? (Not click-and-drag over a background event, not a background event with a regular event on top that is clicked, but just a regular click on a free-floating background event)
Thanks for your time.
Kind regards,
Diana

@DianaLaa I can't give you a lot of details unfortunately, as all of that functionality was written into RBC long ago. I can tell you that, personally, the product I work on uses timers and cancellation (like you see in many of our drag and drop examples in our documentation) to attempt to determine what the user's true intentions are, and only call the event it needs to in the end. My hope is that our next major version (which will be a complete rewrite and major breaking change) will address these sort of issues, but we do not have a solid timeline for that as yet.

@cutterbl  Thank you for your reply and suggestion. I've added a check to our onSelectSlot method that first searches through the list of backgroundEvents to see if any of them was clicked. If so, the handler is exited so that onSelectEvent is triggered.

Hi, I am encountering the same issue here because I am using both backgroundEvents and events, my logic was to use backgroundEvents to disable slots from being selected, while events would be actual reserved slots.
I was hoping onSelectSlot would not fire when clicking on backgroundEvents.
I noticed that we could pass ignoreEvents to selectable, I assumed it would not trigger onSelectSlot when clicking a background event, but unfortunately it doesn't and was wondering why.

From our documentation of onSelectEvent

Clicking on a backgroundEvent will also fire the onSelectEvent callback. It will also receive the backgroundEvent as the event object, but contain a isBackgroundEvent property set to true. This will allow you to distinguish between a background event and a regular event within your onSelectEvent handler.


Unable to create SAS token on storage explorer for objects

When creating SAS token for Objects on storage explorer on Mac, it isn't able to right click onn Objects under blob to create SAS token but on portal and windows, object-level SAS token can be created.
Resulting URL generated on MAC storage explorer doesn't work.
Error:

AuthenticationFailed
Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. RequestId:02648e6c-f01e-009a-2f0c-cde31b000000 Time:2020-12-08T02:48:19.9842391Z
Signature did not match. String to sign used was rl 2020-12-07T08:42:28Z 2020-12-08T08:42:28Z /blob/sqlvatlzxwebks5i3m/$root 2019-12-12 c

@prensoni043 Are you trying to generate the SAS for a blob in a regular blob container or an ADLS Gen2 blob container? We don't support generating SAS for ADLS Gen2 blobs for now. I know that portal supports it but there should be no difference between our Windows and Mac version. Let me know if you can see the "generate SAS" action in context menu from our Windows version but not on Mac for the same regular blob.
Where did you get the sas URL and how are you using it? The error messages suggests you are using a container level SAS to your $root container. On my Mac, I can generate a container sas for a $root container and connect to it.

Hi Jason,
I am trying to create SAS for objects under blob container but it doesn't allow right-click, I am not sure if it's regular or ADLS Gen2.
I have verified that windows based storage explorer app can right-click on the object and able to generate SAS url, whereas my Mac is unable to do it.

URL by windows machine:
https://sqlvatlzxwebks5i3m.blob.core.chinacloudapi.cn/jatin-blob/qqqq.png?sv=2019-02-02&st=2020-12-10T03%3A49%3A51Z&se=2020-12-11T03%3A49%3A51Z&sr=b&sp=r&sig=qsIZ7dtn40hwfGhI6qVT6eg3%2FkivhjysXhkeNBYhvlE%3D

@prensoni0143 on macOS, can you try using Shift+F10 to open the context menu?

@prensoni0143 on macOS, can you try using Shift+F10 to open the context menu?

My Mac keyboard doesn't have F10 but have F0(after F9) and pressing it with Shift or Shift+Fn doesn't happen anything while selecting an object under Storage Account app

@prensoni0143 your keyboard doesn't have F10, F11, or F12? What type of keyboard are you using lol? Can you get another keyboard that does have it?
Can you tell us how you're attempting to do a right click? Are you using a track pad or mouse?

@prensoni0143 your keyboard doesn't have F10, F11, or F12? What type of keyboard are you using lol? Can you get another keyboard that does have it?
Can you tell us how you're attempting to do a right click? Are you using a track pad or mouse?

@prensoni0143 your keyboard doesn't have F10, F11, or F12? What type of keyboard are you using lol? Can you get another keyboard that does have it?
Can you tell us how you're attempting to do a right-click? Are you using a trackpad or mouse?

This is how my Macbook Pro keyboard looks. (Right-click by: Ctrl + TouchPad)

@prensoni0143 your keyboard doesn't have F10, F11, or F12? What type of keyboard are you using lol? Can you get another keyboard that does have it?
Can you tell us how you're attempting to do a right-click? Are you using a trackpad or mouse?

This is how my Macbook Pro keyboard looks. (Right-click by: Ctrl + TouchPad)

The keyboard shares the function keys (f1-f12) with utility keys. If you press fn (the left bottom key) + f1-f2 (above the number keys, see the small label), you should be able to use the function keys. For shift + f10, now it will be shift + fn + f10.

The keyboard shares the function keys (f1-f12) with utility keys. If you press fn (the left bottom key) + f1-f2 (above the number keys, see the small label), you should be able to use the function keys. For shift + f10, now it will be shift + fn + f10.

Right-click by: Ctrl + TouchPad

Ah! Can you try doing a two finger click instead? I wouldn't be surprised if trying to use Ctrl to right click is broken due the same cause for this bug: https://github.com/microsoft/AzureStorageExplorer/issues/3230

Right-click by: Ctrl + TouchPad

Ah! Can you try doing a two finger click instead? I wouldn't be surprised if trying to use Ctrl to right click is broken due the same cause for this bug: https://github.com/microsoft/AzureStorageExplorer/issues/3230

Ok. Looked into the root cause more. This isn't related to that bug. But your method of opening context menu is valid:
https://support.apple.com/guide/mac-help/right-click-mh35853/mac
So we should fix this in the future. I'm going to move it to our 1.19 release for now. Until then, please try using two finger click and let us know if that works.

Ok. Looked into the root cause more. This isn't related to that bug. But your method of opening context menu is valid:
https://support.apple.com/guide/mac-help/right-click-mh35853/mac
So we should fix this in the future. I'm going to move it to our 1.19 release for now. Until then, please try using two finger click and let us know if that works.

Ok. Looked into the root cause more. This isn't related to that bug. But your method of opening context menu is valid:
https://support.apple.com/guide/mac-help/right-click-mh35853/mac
So we should fix this in the future. I'm going to move it to our 1.19 release for now. Until then, please try using two finger click and let us know if that works.

That's perfect, yes it works with 2 finger clicks but not with ctrl + TouchPad
And I can generate SASAccesToken with this.

Ok. Looked into the root cause more. This isn't related to that bug. But your method of opening context menu is valid:
https://support.apple.com/guide/mac-help/right-click-mh35853/mac
So we should fix this in the future. I'm going to move it to our 1.19 release for now. Until then, please try using two finger click and let us know if that works.

That's perfect, yes it works with 2 finger clicks but not with ctrl + TouchPad
And I can generate SASAccesToken with this.

The keyboard shares the function keys (f1-f12) with utility keys. If you press fn (the left bottom key) + f1-f2 (above the number keys, see the small label), you should be able to use the function keys. For shift + f10, now it will be shift + fn + f10.

Also works the same, thank you :)

The keyboard shares the function keys (f1-f12) with utility keys. If you press fn (the left bottom key) + f1-f2 (above the number keys, see the small label), you should be able to use the function keys. For shift + f10, now it will be shift + fn + f10.

Also works the same, thank you :)


fix: remove unnecessary linting

These checks don't really make sense, since they only look at the code (which isn't changing). Also, the full set of checks will be run when the PR is created (at the end of the action). That way we will get a more visible warning if something, somehow, goes wrong.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

can we be sure the downloads are not out of format for some reason?

I don't think we should worry about it, honestly. We deliberately don't run prettier on the challenges so that we can format the code as we want and the linting doesn't care about the language.
If we're concerned, we should run the node-js tests on more languages. That's the only meaningful automated testing we're doing, imo.

As far as I can see the goal is to try to catch problems with the translated .md files in CI. That's really all we're trying to do. Given that the full suite of tests run once the PR is created it follows that all these checks could possibly do is give us an early warning.
I don't think that's particularly useful, even if people saw the warning and the download was likely to generate warnings.

Yes, I believe this was an artefact left from when we did lint the curriculum. The format step was merely intended to catch small issues (such as a trailing space at the end of the translation) that would have tripped the linter, allowing the action to fix them prior to creating a PR.


Download Canyon from GitHub for final build

Canyon is on an indefinite hiatus, and a final build has been produced by @KoboDev for the meantime. This changes the default value for CANYON_BUILD to "final", and in the instance this is provided, we download this build from their GitHub provided build rather than the CI integration.
The CI server previously provided by Velocity is now 410 Gone, so individual build numbers are not available at present. A future PR may address this by them being made available by another provider, but for now I think this change is enough to keep Canyon servers functional for the meantime.

If I do find the other builds, I will provide them but for right now.
Its what I can give.
Build 6 being the last build before Tux left
and Build 26 & 27/latest being the last ones I have made for canyon.
When my brain is feeling the most healthiest I will continue pushing small patches.

https://jenkins.glass-launcher.net/job/Canyon/
new canyon builds are hosted here, along with #32


Use of camelCased properties importing from JSON

My model in Swift has property named isPromo.
In JSON, this property is named is_promo and this throws an exception when importing with createInDefaultRealmWithObject
Is there some way how to import this without changing the JSON dictionary?
It would be nice to have some function in model where we could define this transforms. Also if we have different property names in models.
For example something like this:
class MyModel: RLMObject {
    dynamic var isPromo = false
    dynamic var productDescription = ""

    override class func importPropertyNames() -> [String : String] {
        return [ "is_promo" : "isPromo", "description" : "productDescription" ]
    }

Incase someone comes across this, another person had issues using ObjectMapper https://github.com/realm/realm-cocoa/issues/1726

Closing as duplicate of #694


Possible to not search in Apple/recent items

There are a lot of objects in Apple/recents items which clutter the otherwise clean results of finbar. I don't search for these object when using finbar. How can I hide them?
Maybe the rule editor would be my solution. But I don't find a way how to access the rule editor.

Thank you for your help!
Would be great to have these included in the software as an option already
pre-installed.
For example during the installation process You asked:
“Where the rule editor, you can customise Finn Bar.
Hear an example which excludes the Apple menu with The Recently started
Programs as well as several browser history entries. Do you want to
activate them?”
Best,
Uli
Roey Biran @.***> schrieb am Mi. 16. Okt. 2024 um 10:25:

Hi and thanks for using the issue tracker!
The rule editor is accessible by in the settings:
@.*** (view on web)
https://github.com/user-attachments/assets/ad64b5b7-58a8-4b67-b6dd-6f4332da52ac
To exclude the Apple menu, define the following (taken from my own
configuration):
@.*** (view on web)
https://github.com/user-attachments/assets/5d6d26f8-d5f8-4ccb-98a9-a251ad73bde0
Message me if you need further help. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/roeybiran/finbar-issues/issues/20#issuecomment-2416073996,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYHNWMUSEZSLHNGJH4JYPTZ3YPC5AVCNFSM6AAAAABP6XRQXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGA3TGOJZGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add note to the doc about windowSize for mobile devices

// cc @j0tunn @tormozz48 @eGavr

Coverage decreased (-2.4%) to 78.162% when pulling 1672bea4a1eead36d32f7f3bcbfc1e7ecf0d08f2 on sipayrt.doc into 3a355eb63dd559a94a8f9e028f922b71b0ed081d on master.

Coverage decreased (-2.4%) to 78.162% when pulling d343812457f91ed56b7f1295f5fc7873b993c70a on sipayrt.doc into 3a355eb63dd559a94a8f9e028f922b71b0ed081d on master.


Connection error when listing targets in CLI

(Transferring issue reported by @giobb from https://github.com/microsoft/Quantum/issues/466.)
Hi everyone
I always get the issue below on my work machine. This machine is the standard issue that's connecting to corpnet via MS VPN from home. It doesn't happen on my personal machine though. If it's not Quantum-CLI related, I'm just wondering why it's only on this particular subcommand, (the workspace set obviously works)

Cheers!
gio

quantum

This is already working for me

Resolving this issue since it has been fixed with newer releases of the extension.


✨ [REQUEST] Whatsapper

Checked

[X] If a new addon, I have checked on  Google that such as addon doesn't already exists
[X] If a new feature, I have searched in the discussions & issues that it was not already covered

Which addon?
I created a mini web proxy for the whatsapp.js project. this could be useful to have a whatsapp bot in home assistant!
https://github.com/baldarn/whatsapper
what do you think?
Is your feature request related to a problem? Please describe
no
Describe the solution you'd like
add whatsapper to this addons list

Hi, it doesn't find the "latest" tag on dockerhub - is it public?
ERROR: failed to solve: whatsapper/whatsapper:latest: docker.io/whatsapper/whatsapper:latest: not found
https://github.com/alexbelgium/hassio-addons/actions/runs/7601097640/job/20700121870

mmm will see this today or worst case tomorrow

Just pull request a new config version (such as 0.02) and it will rebuild on the repo

let's try if this solves :/
https://github.com/alexbelgium/hassio-addons/pull/1196

Thanks, trying build

mmmm still something wrong :/

should fix
https://github.com/alexbelgium/hassio-addons/pull/1200

still not running. It works if docker run that... could you give me a hint @alexbelgium ?

not sure to understand, the addon doesn't run but docker run does ? I'll check on my system

yes, if you do
docker run --name whatsapper -p 3000:3000 baldarn/whatsapper
it works, but the addon starts and auto shutdown :/

this is the full log
-----------------------------------------------------------
 Add-on: Whatsapper
 Whatsapper for Home Assistant
-----------------------------------------------------------
 Add-on version: 2024.1.22
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 12 (bookworm)  (amd64 / qemux86-64)
 Home Assistant Core: 2024.1.5
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
/etc/cont-init.d/01-config_yaml.sh: executing
Setting permissions for the config.yaml directory

Load environment variables from /config/config.yaml if existing
If accessing the file with filebrowser it should be mapped to /addon_configs/db21ed7f-whatsapper/config.yaml
---------------------------------------------------------

Wiki here on how to use : github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables
... no env variables found, exiting
/etc/cont-init.d/01-custom_script.sh: executing
Execute /addon_configs/db21ed7f-whatsapper/whatsapper.sh if existing
Wiki here : github.com/alexbelgium/hassio-addons/wiki/Add-ons-feature-:-customisation

Starting the upstream container

Starting...

Starting the upstream container

yes exactly that ; your entrypoint is missing. I've pushed a new version without my entrypoint and we'll see how that goes

hi, why this?
https://github.com/alexbelgium/hassio-addons/commit/42dee1495057962b6cf3a44d928e2a3446054d37
I have an amd64 server :), can't test this :/

I removed the wrong one :) corrected

great! it works!
thanks for the assistance!
now I will work on the home assistant integration ;)

Hi, is it possible to support other architectures too?
I have a RP4 and this stuff sounds great ;)
Thanks

Hi @baldarn do you have a way to make dockerhub aarch64 builds?

@alexbelgium dunno, never did that. I can try, but tomorrow :)
if you have a quick solution is more that welcome!

Only did builds by using someone else code ;-) so not sure how to help here!

hopefully I did it ;)
@alexbelgium can you merge https://github.com/alexbelgium/hassio-addons/pull/1203 ?
@PiperNigrum can you try?

It seems to work.
Is it possible to Display the QR-Code in a normal way?

something should be coming ;)
https://github.com/alexbelgium/hassio-addons/pull/1204

@PiperNigrum done.
you can navigate to the path /qr and be linked to a qr code visualizer. ;)

let's close this. if more requests arrive other issues will be opened ;)


Container goes into restart loop immediately upon being started

docker logs shows me this:
Setting timezone to UTC
Initializing files and folders
Setting global configuration
Creating user nobody/nobody (1000:1000)
Add global option: force user = nobody
Add global option: force group = nobody
Creating share centauri
Creating share magellan
Creating share orion
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
Server role: ROLE_STANDALONE
Global parameters
[global]
disable netbios = Yes
disable spoolss = Yes
dns proxy = No
local master = No
map to guest = Bad User
.
.
.
.
[orion]
delete veto files = Yes
guest ok = Yes
path = /nfs/orion
read only = No
veto files = /._*/.apdisk/.AppleDouble/.DS_Store/.TemporaryItems/.Trashes/desktop.ini/ehthumbs.db/Network Trash Folder/Temporary Items/Thumbs.db/
vfs objects = recycle
recycle:versions = yes
recycle:keeptree = yes
recycle:repository = .recycle
smbd version 4.18.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023

Please create a proper bug report


Even if the parameter is not jwt, it is connected.

Hi everyone.
First of all I'm really appreciate this library.
when jwt is wrong it's working great.
But The situation is when input just string or something it does not prevent.
Is there any solution?

set EMQX_ALLOW_ANONYMOUS: 'false'

thanks, @andares
and left some tip for docker user.
add this code in your start.sh before dockerize
if [[ -z "$EMQ_MQTT__ALLOW_ANONYMOUS" ]]; then
    export EMQ_MQTT__ALLOW_ANONYMOUS="false"
fi

if [[ -z "$EMQ_LOADED_PLUGINS" ]]; then
    export EMQ_LOADED_PLUGINS="emq_recon,emq_modules,emq_retainer,emq_dashboard,emq_auth_jwt"
fi

if [[ -z "$EMQ_AUTH__JWT__SECRET" ]]; then
    export EMQ_AUTH__JWT__SECRET=some_secret
fi


feat(ipfs): ipfs-keychain implementation

Added

ipfs-keychain test case
ipfs remove functionality

@petermetz can you please review when you have some free time

@TonyRowntree Let me know if you need help with the conflict resolution.

Closing as inactive, we can reopen later as needed.


Not able to import xspec models

Describe the bug
While I try the command
import astromodels.xspec
I get the following error message
ImportError                               Traceback (most recent call last)
/var/folders/vq/jf14w4_j6n7_60zlyxzzkvg40000gn/T/ipykernel_10098/450884429.py in
----> 1 import astromodels.xspec
~/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/ROOT/_facade.py in _importhook(name, *args, **kwds)
119                 except Exception:
120                     pass
--> 121             return _orig_ihook(name, *args, **kwds)
122         builtin.import = _importhook
123
~/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/astromodels/xspec/init.py in
----> 1 from .factory import *
2 #from .xspec_settings import x
~/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/ROOT/_facade.py in _importhook(name, *args, **kwds)
119                 except Exception:
120                     pass
--> 121             return _orig_ihook(name, *args, **kwds)
122         builtin.import = _importhook
123
~/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/astromodels/xspec/factory.py in
16     pass
17
---> 18 from astromodels.xspec import _xspec
19
20 # When running in a Anaconda environment, the package xspec-modelsonly
~/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/ROOT/_facade.py in _importhook(name, *args, **kwds)
119                 except Exception:
120                     pass
--> 121             return _orig_ihook(name, *args, **kwds)
122         builtin.import = _importhook
123
ImportError: dlopen(/Users/shabnamiyyani/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/astromodels/xspec/_xspec.cpython-37m-darwin.so, 2): Symbol not found: _Z6tabintPfiS_iPKciS1_S_S
Referenced from: /Users/shabnamiyyani/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/astromodels/xspec/_xspec.cpython-37m-darwin.so
Expected in: /Users/shabnamiyyani/heasoft-6.29/x86_64-apple-darwin19.6.0/lib/libXSFunctions.dylib
in /Users/shabnamiyyani/opt/miniconda3/envs/threeML/lib/python3.7/site-packages/astromodels/xspec/_xspec.cpython-37m-darwin.so
Desktop (please complete the following information):

OS: MacOS Catalina version 10.15.7
Xcode version 12.4

I have also installed the heasoft package including the xspec models

Have you installed the conda package with XSPEC?

Yes, I have xspec-modelsonly          version=6.25

Likely you have both your local installed and the conda installed XSPEC in your paths and they are colliding.

Thanks for the reply. The issue has been solved. Before activating the conda environment for 3ML, I did
unset DYLD_LIBRARY_PATH
unset LD_LIBRARY_PATH
After that, the import of xspec models works fine.


ARM assembly syntax file using .s file extension conflicts with asm.yaml

Description of the problem or steps to reproduce
I would like to use micro for a project in ARM assembly language, and could contribute a syntax file for that instruction set. However, our source files use the extension .s, which is already used by the built-in syntax file for x86 assembly language. I looked at the detect/header syntax in YAML, but the Go code in ftdetect.go prefers the file extension to the firstLine header. I can see two cumbersome ways to make this work:

Make up a bogus file extension like .as for ARM assembly language
Type set filetype armasm every time I open a file this doesn't work

Is there a better way? If not, can we make something up, like maybe allowing the firstLine header to take priority over the file extension?
Specifications
Version: 2.0.2
Commit hash: c51f849
Compiled on February 26, 2020

If you take a look at the ftoptions plugin, you can use that as a template to write your own plugin that detects your filetype and changes the filetype option.
I think something like, if ft == "asm" then  if {custom detect code}  {filetype  = armasm}

Okay, I went ahead and wrote this for you.
function onBufferOpen(b)
    local ft = b:FileType()

    if ft == "asm" then
    	if string.find(b:Line(0), "armasm") then
    		b:SetOption("filetype","armasm")
    	end
    end
end

Not sure what your arm asm file looks like. If you add a comment to to the top of your file, containing the string "armasm" this will detect it. Or you can figure out something else.
You need a separate syntax file defining armasm syntax, of course.
To use this, mkdir -p ~/.config/micro/plug/armhelper
Store the function in ~/.config/micro/plug/armhelper/armhelp.lua

Thanks. I thought I would make it more readable by making the filetype arm-asm, and naming the plugin to match. However, my plugin never got called. It appears that this line of code does not permit dashes in the filenames of runtime files :-)
Now the filetype switch (to arm_asm) works, but that seems to break syntax highlighting. I will file a separate issue on that.

I would really like to see something like this:
/* micro:set filetype arm_asm */
as vim does
Want to repurpose this issue? Or close and open a new one?

By the way, it should be possible to achieve a similar effect to the plugin by adding the following to your settings.json:
{
...
    "*.s": {
        "filetype": "arm_asm"
    }
...
}

Does that approach lock users into a one-to-one relationship between file extensions and syntax files? I'm looking for an approach which allows file extensions to have a one-to-many relationship with syntax files. That's certainly the real-world scenario for .s files files representing completely different architectures.
I also imagine one-to-many would be useful for other languages as they evolve, gaining new syntax or deprecating old syntax. For example, one-to-many would allow Micro to edit python3 files with a .py extension, which might be nice too.


Dor 73 export contact info

rebased and force-pushed to resolve conflicts

@Tasmine10ten this should be now ready for review again


Merge ign-gazebo6 ➡  main (part 2)

➡  Forward port
Port ign-gazebo6  ➡  main
Branch comparison: https://github.com/gazebosim/gz-sim/compare/main...ign-gazebo6

Builds on top of https://github.com/gazebosim/gz-sim/pull/1630

@mjcarroll , I could use some help getting the changes from #1352  to play nicely with the reset stuff - #1390 is a nice reference.
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

CI result analysis:

Actions Focal: one failed INTEGRATION_odometry_publisher and the other INTEGRATION_scene_broadcaster_system - they're flakes
Actions Jammy: one failed INTEGRATION_odometry_publisher and the other INTEGRATION_scene_broadcaster_system - coincidentally the same flakes as in Focal
Windows: No failures, just pre-existing warnings (109 is less than the 157 currently on main)
Homebrew:

UNIT_SimulationRunner_TEST is a know failure
plugin_custom_sensor_system - new failure caused by https://github.com/gazebosim/gz-sensors/pull/254 and being fixed in https://github.com/gazebosim/gz-sim/pull/1634

I have on my list for this week:

INTEGRATION_scene_broadcaster_system - I have most of a fix for this, just working out a last timing kink on all platforms.
Windows: No failures, just pre-existing warnings - I have spun up a brand new Windows install to work through windows test failures and warnings throughout the stack.

I have tested the reset examples locally and this looks like a clean merge, functionality is intact.  I don't see any weird interactions here.

I have tested the reset examples locally and this looks like a clean merge, functionality is intact. I don't see any weird interactions here.

Thanks, @mjcarroll . I'll consider this an approval and merge this PR, we're way past feature freeze and need to branch off gz-sim7 asap.

I found some ign console loggers that should be updated. Should I open a separate PR for these?

Thanks, @jennuine ! Those are taken care of in #1633


Problem: can't determine database version from directory

Given a mina-indexer's database directory, one cannot determine what version of database it is. In other words, one cannot determine if a given version of the indexer is compatible with an on-disk version of the database.
One could query the running indexer about its version of database, but how do we know whether the running indexer is using the particular database directory that we are considering.
Also, it is often the case that the running indexer has no open socket for querying.
Further, the indexer that created (and expects to use) the database is not running.
So, we are left with no way to discover the version of a database.
This could be solved by, for example, writing a file with name "VERSION" inside the database directory as soon as it is created by an indexer. If this is done, then it also makes sense to, whenever an indexer launches, have it verify that the version matches its own.

The absence of this feature makes it very difficult to correctly write deployment software for the indexer, and negatively affects user experience.


[Feature Request] Customizing the RESTful API endpoints

For example, one may want to use plural endpoint names instead of singular ones.

We also need to think about how to synchronize the API runtime behavior and the specs generated by the openapi plugin.


preview BSC countries

Docs Build status updates of commit 628c8f5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/bingads-13/campaign-management-service/getbsccountries.md
:white_check_mark:Succeeded

Advertising/shopping-content/catalogs-resource.md
:white_check_mark:Succeeded

Advertising/shopping-content/products-resource.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Try adding InlineTimingFunctionEditor

Brackets has a default, built-in timing editor for bezier curves and css.  We should try turning it on, see how big it is, and how useful.
cc @Pomax.

This is possible now, via ?enableExtensions=InlineTimingFunctionEditor, closing.


rails-5.0-comment_spec

Issue is caused by different ways of triggering the after_commit hook in rails 4 and 5
In rails 4, running :run_callbacks would trigger the after_commit hook.
In rails 5 however, the after_commit is only triggered after the database transaction is completed and would not respond to :run_callbacks.
Relying on building a comment and saving to trigger the callback

See: https://stackoverflow.com/a/30901628/15768801 The change in behavior from Rails 4 to Rails 5  is due to tests running within transactional fixtures in Rails versions < 5. This behavior gets fixed in Rails 5+.
This is a pretty good candidate for version checks. I like what you have so far. We can add version checks for the specs that use trigger :commit via run_callbacks. One thing I do suggest is that you preface with a comment with a TODO so that once we are on Rails 5, we can ctrl+f all our TODOs and remove them.
eg.  comment_spec.rb L556 can look like
it 'should queue the notification' do
      # TODO: Once on Rails 5, Can Remove this Version Check
      # In Rails Versions < 5, commit callbacks are not getting called in transactional tests.
      # See https://stackoverflow.com/a/30901628/15768801 for more details.
      if Rails.version.starts_with?('4.2')
        expect(CommentSubscriptionWorker).to receive(:perform_async).with comment.id
        comment.run_callbacks :commit
      else
        allow(CommentSubscriptionWorker).to receive(:perform_async)
        expect(CommentSubscriptionWorker).to have_received(:perform_async).with comment.id
      end
end


add topk/bottomk that aggregates others

Fixes #1224.
Adds variants of topk/bottomk that in addition to computing
the highest priority values will also return an aggregate
time series that includes all of the other time series that
were not high enough priority. This can be useful to see
what proportion of the overall volume is represented by
the highest priority time series. The operators have the
same signature as :topk and :bottomk, but the
aggregation to use is specified in the operator name.
There are four aggregates supported:

min
max
sum
avg

Count was not included as an aggregate because it could be
ambiguous and does not seem useful.
As part of this work there was some refactoring of the
existing aggregation operations to make the count case
more consistent.

Note, this PR depends on #1247 and will need to be updated once that is merged.

Regarding count, the reason it was considered problematic is that it could mean the aggregate count across others or the count of how many others were present. For example:
Expr:
    Q,:count,(,foo,),:by

Output:
    foo1: 1
    foo2: 2
    foo3: 3 (means 3 time series had values for foo3)

Expr with priority operator:
    Q,:count,(,foo,),:by,max,1,:bottomk-others-count

Option 1:
    foo1:       1 (highest priority)
    --others--: 5 (cumulative number of input time series contributing to others)

Option 2:
    foo1:       1 (highest priority)
    --others--: 2 (number of time series that were not high enough priority)


Update issue templates to include proper formatting for device signature

These changes should avoid any confusion on whether removing and re-joining a device is required for just getting the device signature. It should also help with the proper formatting of the device signature.
(If further debug logs of a device working are required for a specific quirk, they can still be requested individually. I don't think it makes sense to include instructions to get debug logs in the issue template, as most simple quirks don't require these and grabbing them can be somewhat complicating for beginners. Just grabbing the device signature should be enough for a start.)
I'm open for changes of course.

Codecov Report

Merging #1508 (2e408e6) into dev (16f298e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1508   +/-   ##
=======================================
  Coverage   80.36%   80.36%
=======================================
  Files         227      227
  Lines        6704     6704
=======================================
  Hits         5388     5388
  Misses       1316     1316

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 16f298e...2e408e6. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.37%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5388

Relevant Lines:
6704

💛  - Coveralls

Awesome. Can you add a section for device diagnostics too please?

Right, I forgot we have these now.
Perhaps the device signature section could even be removed (in the future), since it should be included in the diagnostics. Personally, I'd probably still keep it around for a bit though, as some users may not be up-to-date and it's a little easier to get the signature on mobile/tablets or similar? (and the signature is also a bit more compact)
Should diagnostic information perhaps be "hidden" by default, so the issue doesn't get as long?
-> Which of the following "designs" would be better?

Diagnostic information - this can be acquired by clicking on the "Download Diagnostics" button in the device settings
Paste the diagnostic information here
somewhat long text here will be always visible

Diagnostic information - this can be acquired by clicking on the "Download Diagnostics" button in the device settings
Paste the diagnostic information here
somewhat long text here will be mostly hidden

I like the expandable one. Would it make sense to do that for the signature and the diagnostics data?

Like this:

Device Diagnostics
Put the Device diagnostics here

Code:
<details>
  <summary>Device Diagnostics</summary>
Put the Device diagnostics here
</details>

I like the expandable one. Would it make sense to do that for the signature and the diagnostics data?

Yeah, I think that's good. Maybe also do it for logs at this point (like below)?
The "code" isn't as nice with the expandable sections (updated PR) but I think it should be do-able for the average user. (The Home Assistant Core template doesn't look "easy" at first glance for example.)

Device signature - this can be acquired by clicking on the "Zigbee Device Signature" button in the device settings
Paste the device signature here.

Diagnostic information - this can be acquired by clicking on the "Download Diagnostics" button in the device settings
Paste the diagnostic information here.

Additional logs
Paste any additional debug logs here.

Also, apparently the Home Assistant core repo now uses the new GitHub issue forms.
That can probably be implemented for this repo or all zigpy repos at some point (but I don't have the time to do it atm).
These changes should still be a bit better than the current templates.


memory leak with MHR

when HMR open, memory usage will become more and more bigger when  modify file for many times.

Do you have any idea about how we can fix it ?

I found it's my mistake, because of I added hash to output file name  in dev config. so I think you can close this issue without fix anything


Unable to integrate with Disqus comment.

Disqus comment are working incorrect, it can't loading the current post's comments.
As https://ghost.org/integrations/disqus/ said, there is this.page.identifier = "ghost-{{comment_id}}" in the scripts but now {{comment_id}} return nothing.
From Theme Developing Doc https://ghost.org/docs/themes/contexts/post/ , {{comment_id}} must be inside the {{#post}} and {{/post}} block. But Alto's comment block is outside the post block (post.hbs).
Could you help to fixing it? Thanks.

This is a bug. You can fix manually by edit post.hbs and put the {{> comment}} right after {{> post-navigation}}.

Thanks, fixed in https://github.com/TryGhost/Alto/commit/b2fcb8f697d1378ff1b2afc7c21b8a206af9715b


Allow for setting any Postfix variables in the config file

Stolen from wader/postfix-relay, I propose to add the following line to your entrypoint.sh:
for e in ${!POSTFIX_*} ; do postconf -e "${e:8}=${!e}" ; done

This allows for setting up postfix in a Docker swarm / compose, without having to mount a whole configfile. Usage:
  mail_relay:
    image: zixia/simple-mail-forwarder:1.1
    networks:
      - traefik-public
      - default
    deploy:
      labels:
        - traefik.enable=true
        - traefik.docker.network=traefik-public
        - traefik.constraint-label=traefik-public
        - traefik.tcp.routers.mail_relay.rule=HostSNI(`*`)
        - traefik.tcp.routers.mail_relay.entrypoints=smtp
        - traefik.tcp.routers.mail_relay.service=mail_relay
        - traefik.tcp.services.mail_relay.loadbalancer.server.port=25
    environment:
      - SMF_DOMAIN=domain1.com
      - |
        SMF_CONFIG=
        sam<EMAIL_ADDRESS>        sam<EMAIL_ADDRESS>      - POSTFIX_myhostname=smtp.domain1.com
      - POSTFIX_relay_domains="domain1.com domain2.com"
      - POSTFIX_smtpd_recipient_restrictions=permit_mynetworks, permit_sasl_authenticated

(note the last three lines)

Please feel free to create a PR to implement it, and do not forget to add the related docs in README and unit tests as well.

@huan This issue can be closed. #92

@tamaro-skaljic @knipknap @dgraziotin thank your very much for the efforts to enhance SMF!


Replaced BigInteger methods to Kotlin operators

Describe your changes

Replaced BigInteger methods to Kotlin operators to replace .add(), .minus(), .mod() to +, -, %

Hey @ChielokaCode, formatting is still incorrect, please fix it.


How can I connect an embedding model (e.g m3e-base) at local directory by using TS embedding configuration?

To run local embedding models you can use Ollama (https://ts.llamaindex.ai/modules/embeddings/available_embeddings/ollama) or HuggingFace (see https://ts.llamaindex.ai/modules/embeddings/available_embeddings/huggingface)


jitterentropy: 3.4.1 -> 3.5.0

Changes:

add distinction between intermittent and permanent health failure
add compile time option to allow configuring a mask to reduce the size of the time stamp used for the APT

Upstream changelog: https://github.com/smuellerDD/jitterentropy-library/releases/tag/v3.5.0
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 316716 run on x86_64-linux 1

4 packages built:

esdm
jitterentropy
jitterentropy.dev
rng-tools


checkbox/radio issues

I am converting a project over from 3.1 to 3.3.1 and noticed my checkboxes were taking more height than they did previously.  Most were written before as:

      <input type="checkbox">
to

      <input type="checkbox">

In the cases I am looking at the checkboxes have no text, like is show in the example on the getbootstrap site ("Checkboxes and radios without label text")
But what I noticed in looking at the heights in Chrome, the label takes a height of 20px (follows the min-height), but the div takes 25px.  I added the rule below and then the div is equal to the label in height.  Not sure if this is a bug or this effect was desired.
.checkbox > label {
   display: block;
}

Thanks

block level s are undesirable as all the white-space in that block—the negative space to the right of a short label, for example—become clickable. Putting checkboxes within a button group is also not supported.

When I look at it on your site, this is where I see the issue, whether or not the checkbox is in a button group.  Should the div really be taller than the label?  Again I was using it without any label text.
Thanks for all your work.

Can't help you without a live example. Try getting your code to run in something like http://jsbin.com to show us what you're seeing.

On the page, getbootstrap.com/css, go down to where the page discussed checkboxes without label text (id=”blankcheckbox”).
If you look at the checkbox example below in a browser debugger, the input is 13px high, the label is 20px high (due to the min-height), but the div with the checkbox class is 25px high, but why is the div taking up extra space?
So to get around the space problem, I added the block on the label, but like you said that has other side effects.  It is probably I don’t understand the difference between inline-block vs block in this case, but I just wanted to understand what is going on and if it is expected.  It does it in IE and Chrome.  The extra height was causing me some layout issues, so that is why I even found it and figured their may be other people with the same issue.
Thanks.
From: Mark Otto<EMAIL_ADDRESS>Sent: Tuesday, January 20, 2015 4:29 PM
To: twbs/bootstrap
Cc: Juan Foegen
Subject: Re: [bootstrap] checkbox/radio issues (#15603)
Can't help you without a live example. Try getting your code to run in something like http://jsbin.com to show us what you're seeing.
—
Reply to this email directly or view it on GitHubhttps://github.com/twbs/bootstrap/issues/15603#issuecomment-70747312.

Let me know if you need a better or isolated example than the getbootstrap.com/css page
Thanks.


Fix autodetect arch for apple m1 cpu

Current autodetect Environment on macbook pro with M1 cpu:

Version:          2.*
Stability:        stable
Operating System: darwin
Architecture:     amd64

After patch:

Version:          2.*
Stability:        stable
Operating System: darwin
Architecture:     arm64

Thanks @alexpts


Add support for Nitrokey Storage

Hi!
This PR adds support for (un)locking the main encrypted volume, (un)locking and creating hidden volumes.

Ok, I've fixed the issues you raised, except the one about the password prompt, which likely needs a bit more discussion before fixing it.

Bumping

Bumping

The only remaining change request is the --pin argument, but I'm not sure I understand what the conclusion of the discussion was. I should change it to an env variable but which one?

@sgued Ok! Please ping me once you are ready.

Thanks for the update!  Looks good to me and works well with my Nitrokey Storage (except for the password argument in create_hidden).  I think we can merge this PR once that is fixed.
@szszszsz Do you know what happens if start >= end for the hidden storage creation?

I added a check to prevent having a volume with begin >= end.
Everything seems good to me to merge.

@sgued One last thing - can you squash the commits? So we could exclude fixups from the repo's history.

You want to squash all commits into one?

Yes, please. Given the total count I think it will be easier to make one than a couple. I can do that too, but we will lose your signature.

Oh right it's for the Signature. Done.

Force-pushed commit matches reviewed part. Merging!


[Storage] [Draft] Mocking Transport Tests & Fixes

API change check
API changes are not detected in this pull request.

/azp run python - storage - tests

/azp run python - storage - tests


Fix dangerouslySetInnerHTML in JSX mode (Fixes #42)

/cc @robthehall

this change works for me! thanks!


form表单进行excel导入 input的type为file 怎么实现？

ElementUI version

OS/Browers version

Vue version

Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?

element 无关问题


RFC 7: xplr

Tracking issue: #7
Rendered version

By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license

looks good 👀
re: post content — I'd love to read posts in the style of joe's website LMAO
would it also be possible for a post to be purely inspo? e.g. a collection of websites with liquid effects; or is a requirement that the person also attempts to implement it?

would it also be possible for a post to be purely inspo? e.g. a collection of websites with liquid effects;

Yes! That would be fantastic! Do you have a general flow of what these posts would look like @whgdk? Maybe we can add it to the RFC!

or is a requirement that the person also attempts to implement it?

No implementation necessary! (Unless the member wants to post some demo)
The core idea is exploration and finding cool things AND then being able to find them again when you do have an idea on how to use it!

@arjunr00 @whgdk @sriramb2000 i think i addressed all the comments?


Add regex validation to assignment field submissions

Assignment field submissions already have a foreign key that looks like this:
    FOREIGN KEY
        (assignment_field_slug, assignment_slug)
        REFERENCES assignment_field(slug, assignment_slug)
        ON UPDATE CASCADE,

I should add a "pattern" column to assignment field and then add that to the foreign key constraint. Then, I could create a constraint that submissions must match the pattern. I could also use client side html5 validation to prevent students from submitting crappy values. This would help because I had a number of students submit invalid github links last year and i didn't find out until later.

I want

validation: e.g. a URL has a particular domain, etc. I can likely get this through regular expression validation on text fields (high priority).
restricted choices: e.g. a dropdown. I could get that via the validation, but it is not super cool (less high priority).
multi-field validation: e.g. these numbers all sum to 1, like the case of a traffic distribution in the final project of 656 (least priority).


fix(flicking): Direction value not given during touch move

Issue
#35
Details
Handle direction value when hammerEvent value exists.
Adjust direction value when moves on diagonal direction.
Preferred reviewers
@sculove @taihoon-kim

@mixed TC's are already added and described as 'Custom events #8 - Check for touch direction during hold'. And it doesn't necessarily add when hammerEvent isn't, because that is the normal case which current TC's are targeting.

When I ran tescase in #8 It didn`t pass if-condition. if-condition is alway false.
Um... This case need to discuss with team.  Let talk to it next meeting.

Good Vacation~


ShadeJar: Use ClassRemapper instead of deprecated RemappingClassAdapter

Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[x] Ensured that basic checks pass: ./gradlew quickCheck

For all non-trivial changes that modify the behavior or public API:

[ ] Before submitting a pull request, I started a discussion on the
Gradle developer list
or can reference a JIRA issue.
[ ] I wrote a design document. A design document can be
brief but explains the use case or problem you are trying to solve,
touches on the planned implementation approach as well as the test cases
that verify the behavior. Optimally, design documents should be submitted
as a separate pull request. Samples
can be found in the Gradle GitHub repository. Please let us know if you need help with
creating the design document. We are happy to help!
[ ] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
I ran a build on your local machine via the command
./gradlew quickCheck <impacted-subproject>:check.
[ ] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

Thank you very much for your contribution!

For internal review: https://code-review.gradle.org/cru/REVIEW-6049

Thank you for merge!


tooltips not showing on initial load with start-opened and fixed-tooltip both set to true

My code:
  <fab
                main-tooltip="Actions"
...
                :start-opened="true"
                :position="position"
                :actions="fabActions"
                fixed-tooltip=true
...

        ></fab>

Expected behavior:

On first load the fab is opened
And  it shows the tooltip beside the actions

Current behavior

On first load the fab is opened
the tooltip is not showing up beside the actions

Note
I have to close the fab and reopen it to have the tooltip showing up beside the actions.
Sorry for my bad english. And thanks for the help!

Hi @legreco ,
I'll release a new package version covering this functionality probably tomorrow.
I'll drop you a message here once it's done :)

Hey @legreco ,
We've just released a new package version (2.3.1) which should fix this issue.
Hope that helps :)

Hey @legreco ,
I'm closing this issue since it should be fixed with the latest release.
Feel free to reopent it if needed.


Internal support for netlifyctl at Netlify

Does this project have much support at Netlify? Seems like the pace of adding basic features is pretty slow.
For example, having decent error messages #4 has been an issue for over 18 months.
Also, the docs encourage the use of this newer, undocumented cli tool, but it seems pretty flakey. Seems better to just point to this tool as a beta.

This does have support from our team. It is a replacement for the older netlify-cli tool that is linked in the docs. We are going to be updating the docs soon to reference this tool

Updating the docs is one thing, having to the tool you're going to reference in a usable state seems to be another. Not trying to be overly critical, just saying that it feels broken, and produces errors more than anything else.

If you'd ping our support team or file issues, we'll be able to try to get those fixed, @chrstphrknwtn .  This tool works well for several hundred customers in production, including folks who deploy huge sites frequently.
The are only two meaningfully broken things we know about right now in this list, one of which is a display-only bug:
https://github.com/netlify/netlifyctl/issues?utf8=✓&q=is%3Aissue+is%3Aopen+label%3Abug
We appreciate your help in reporting problems so we can get them fixed!


REID - Edit repo page (only you can do it cause its in your name)

Add MIT license

Add link into the about section to the deployed app


Speed up saving of > 2k nodes and > 4k relationships in a single tx

When saving the init node of a new complex model (>2k nodes and >4k relationships) in a single tx the method updateRelationships in RequestExecutor needs a moment. The reason is the nested loop. The refactoring of the nested loop to an index (map) seems to be a suitable way to speed up saving. In my case the refactored variant is ~28 percent faster.

Thanks @benataim. I will review and merge this soon.


Remove cloudinfo endpoints from Swagger

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?
Remove not supported /cloudinfo endpoints from Swagger
Why?
We removed /cloudinfo API endpoints earlier from pipeline

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


argo lint local mode

Summary
A means of specifying whether to fail validation for features that are not available locally, like
FATA[0000] cannot validate Workflow: templates.workflow.tasks.foo template reference RELEASE-NAME-templates.foo not found
Use Cases
Validating templates locally. Tested with 2.9.4

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

There's the runtimeResolution flag in the templateRef field for this

Simon has suggested one runtimeResolution. You can run the CLI in server mode with ARGO_SERVER if you are running Argo Server. I actually think this issue in a duplicate of #3209 .


Update neo4j docker entry to include the network info

As pointed out by @amweiss, the network info is removed from neo4j container in https://github.com/lyft/amundsenfrontendlibrary/pull/91. We should add it back to make the neo4j container accessible by other container(metadata).

PTAL @amweiss, @jhettler , @jinhyukchang, @ttannis, @danwom


Implement syscall replace_class

Add replace_class to State trait to enable replacing a contract because deploy_contract has a check that the address is free
Add implementation for syscall replace_class

I'm missing adding integration tests for this in syscalls.rs and syscalls.cairo, but not sure how to go about it, so any tips are welcomed

Codecov Report

Merging #245 (3f0a88b) into main (482e767) will decrease coverage by 0.64%.
The diff coverage is 19.35%.

@@            Coverage Diff             @@
##             main     #245      +/-   ##
==========================================
- Coverage   73.77%   73.13%   -0.64%
==========================================
  Files          40       42       +2
  Lines        2684     2714      +30
==========================================
+ Hits         1980     1985       +5
- Misses        704      729      +25

Impacted Files
Coverage Δ

crates/starknet-rs-py/src/cached_state.rs
0.00% <0.00%> (ø)

crates/starknet-rs-py/src/types/contract_class.rs
0.00% <0.00%> (ø)

src/business_logic/transaction/transactions.rs
83.33% <ø> (ø)

...rc/core/syscalls/business_logic_syscall_handler.rs
74.90% <0.00%> (-2.70%)
:arrow_down:

src/core/syscalls/os_syscall_handler.rs
83.33% <0.00%> (-0.83%)
:arrow_down:

src/core/syscalls/syscall_handler.rs
80.43% <0.00%> (-0.44%)
:arrow_down:

src/core/syscalls/syscall_info.rs
94.11% <0.00%> (-5.89%)
:arrow_down:

src/core/syscalls/syscall_request.rs
82.94% <0.00%> (-4.05%)
:arrow_down:

src/testing/starknet_state.rs
65.93% <ø> (ø)

src/testing/type_utils.rs
75.00% <ø> (ø)

... and 2 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


About the reproduced results

Can you share the training logs on Imagenet regarding the MONet_T model, I can't get 77.0 top-1 ACC in my replicated results. This could be a problem with inconsistent startup scripts.

Hi NieCha,
Since this work was done a long time ago and I am no longer working at EPFL, some files have been lost. However, fortunately, I found a backup of the MONet_T training logs on Wandb backup, which is split into two files corresponding to the purple and pink curves shown in the image, respectively.

output.log
output (1).log
One trick to get higher performance is not enable ema too early. For example, in the shown case I enable ema at 135 epoches.

Here's a detail hyperparameter setting json file from wandb I hope could help you get better performance
wandb-metadata.json

Thanks, that's very helpful!^o^


Fixing most of remaining broken links

Description
Please include a summary of the new content you're adding or the reason for the change. Please include relevant context.
Type of change
Please delete options that are not relevant.

[ ] New document(s)/updating existing
[x] Fixes
[ ] Styling
[ ] Bug fix (non-breaking change which fixes an issue)

#136


Fixed BIC (Swift code) numbers generation

Fixes #1577
Improved BIC-Swift numbers generation with country code

Maybe we should add a full test to check if the generated ibans are valid? Since there a clear validation rules to verify if an iban is actually valid:
https://en.wikipedia.org/wiki/International_Bank_Account_Number


document suggestion for trailing slash

hi thr,
great package
this issue is for those who use trailing slash (like me) in thr url ! in that case default nginx configure doesnt work (i don't why)
here is nginx config
location = / {
	try_files /page-cache/pc__index__pc.html /index.php?$query_string;
}

location / {
	try_files $uri $uri/ /page-cache/$uri/pc__index__pc.html /index.php?$query_string;
}

I don't understand what you're saying.

@deepaksp Nice fix, I had the same issue.
When the url structure of your website has trailing slashes ( e.g. /blog/this-is-my-blog-title/ ) the plugin creates this file: /page-cache/blog/this-is-my-blog-title/pc__index__pc.html so the nginx config has to be changed to the above.


feat(remix-dev): add providerImportSource to xdm compile step

Relates to: #2907

[ ] Docs
[ ] ~Tests~

Testing Strategy: I couldn't see any tests specifically around MDX so have not added a new one, if there's something i've missed then please, let me know and I will amend.

RE. Docs, I was thinking of adding some to mdx#Advanced-Configuration regarding this to match where you've highlighted adding your own remark / rehype plugins.

Hey @MichaelDeBoey this PR is really important for react-spring's doc site because Vercel now patch @remix-run/dev so I'm struggling to manage updating remix / keeping up to date with vercel etc.
Is there an estimation on when this PR might be merged or discussed further? I know there's also MDX 2 which is recommended over XDM but I also believe that would be a breaking change so this feature might be good in the interim...?

Hi @joshuaellis!
Are you still interested in getting this one merged?
If so, please rebase onto latest dev & resolve conflicts

With the forthcoming vite compiler, apps have complete control over how they want to handle non-javascript imports like MDX.
https://remix.run/docs/en/main/future/vite#add-mdx-plugin
Thanks for the PR @joshuaellis, sorry it didn't get our attention, we've been trying to get out of the compiler game, but should have at least told you that a long time ago 😅

Better to reply at some time rather than never! Thank you regardless 🤩


Adjust cell color programmatically

Is there a way to change the properties set in Interface Builder (such as the cell background color) programmatically?

Are a PR (https://github.com/gtsif21/UITags/pull/2) with conflicts waiting to be fixed and merged that add that feature. Convert to public some vars like the tagColor so you can change it from the outside.


NK-103 Camera rotation now working when parented

FIXED BUG 🐛🐛🐛🪓

Note: the last bug with this PR is that the camera gizmo is backwards, this can be fixed by updating the camera gizmo.
Will eventually move towards 2D sprites for representing cameras, so this is a non-issue for now.


Multimaps

Can possibly leverage delegating map to manage set/list backed multi-maps.

Normal idea:

SetMultiMap<K, Set<V>>
ListMultiMap<K, List<V>>

Goofy idea:

QueueMultiMap<K, Queue<V>>

Can have pollKey(K) to operate on queue associated with K

StackMultiMap<K, Stack<V>>

Same idea, but with stacks.


pair programming working on portfolio accessibility

Page titles - No issues found
Image text alternatives-No issues found
Text headings-No issues found
color contrast-No issues found
Resize-No issues found
Interactions-No issues found
Moving content-No issues found
multimedia-No issues found
The basic structure of the page-No issues found

@sja-thedude we went through the project together they could not get errors that is why there are no commits

@sja-thedude we went through the project together they could not get errors that is why there are no commits

@Bria222 this is pair programming project and it's mandatory for all the members of the pair programming group to commit.

@sja-thedude  and also this is my first submission I don't know why it's showing that I have submitted twice and I really haven't I don't know what the problem really is.

@sja-thedude  and also this is my first submission I don't know why it's showing that I have submitted twice and I really haven't I don't know what the problem really is.

Oh okay @Bria222 , I think some technical error maybe. You can submit with adding commits of both the members. If your project is not approved then let me know I will ask senior code reviewer about the error.

@sja-thedude Thanks so much for your feedback i will check do the required changes

@sja-thedude  i have made the changes required kindly check  thanks

@sja-thedude this is the error am getting on submission

I think some technical problem. I have informed about this , hopefully it will be solved soon.

@sja-thedude thanks


Add quick explanation of feature flags in documentation

As mentioned in the title, it would be extremely helpful to introduce the feature flags in the main page of the documentation.

This is an excellent suggestion. Interested into doing it? :)
Meanwhile I'm adding this issue for the next release.

Sure, but I guess I'll have to dig into the code a bit to make sure I write nothing wrong ;)

Don't worry, we can help too. I think it'll allow you to discover a few interesting things so it's always nice!

Great! I'll start to work on it in ~ 2 weeks :)


update console screenshots

fixes #347

@praneetloke is there a way to fake the cicd integration steps so i can advance without following all of the steps to get new screenshots? i wasn't letting me move forward and also wasn't reporting an error. or if you could possibly grab new screenshots for http://localhost:1313/images/docs/reference/console/pulumi-access-token.png and http://localhost:1313/images/docs/reference/console/add-workflow.png and add a commit itd super appreciate it

@susanev yep I can do that for sure but it won't be until tomorrow, though

@praneetloke no rush or urgency at all, next week is cool too


Pre-RFC: Add an Empty type to libcore. Use it to replace the fn() -> ! syntax.

Start Date: (fill me in with today's date, YYYY-MM-DD)
RFC PR: (leave this empty)
Rust Issue: (leave this empty)

Summary
Add an Empty type to libcore. Use it to replace the fn() -> ! sytax.
Motivation
See some previous discussion here: http://internals.rust-lang.org/t/should-be-a-type/1723 here: https://github.com/rust-lang/rust/issues/20172 and here: https://github.com/rust-lang/rust/issues/18414
A standard Empty type (ie. an enum with no variants) would be a useful addition to the standard library. One use case is if you need to implement a trait method that returns Result<_, Err> where Err is an associated type but you know that your implementation cannot fail. Currently, library authors can easily define their own empty types, but this will result in multiple libraries defining the same thing.
Making diverging functions ordinary functions also allows them to be used in generic code. For example, it would allow functions that diverge to be passed as arguments to higher-order functions.
Removing ! and replacing it with a plain ol' type will make Rust slightly simpler.
Detailed design
Add this to libcore:
[lang="empty"]
enum Empty {}

impl Empty {
    fn elim<T>(self) -> T {
        match self {}
    }
}

Add an empty lang item so that intrinsics like abort can return it.  Make all methods that are currently marked as diverging (eg. panic, abort) return Empty instead. Make the panic! macro expand to begin_unwind(...).elim() instead of just begin_unwind(...) to avoid users having to add the .elim() themselves.
Add a convenience method to Result<T, Empty>:
impl<T> Result<T, Empty> {
    fn to_inner(self) -> T {
        match self {
            Ok(x)  => x,
            Err(e) => e.elim(),
        }
    }
}

Drawbacks
This change will require typing .elim() where previously someone wouldn't have had to. But only when calling a diverging function from a non-diverging function without using one of the panic! family macros. In the future, Rust's type checker could be improved to allow any type which is isomorphic to Empty to unify with any other type.
It might make things like reachability checking more difficult. But it would be nice anyway if the compiler could detect unreachable code after code that produces an empty value.
! used to be treated as a type though, but this was removed due to maintenance difficulties.
Alternatives
Just add an Empty type to libcore but keep the seperate divergence syntax aswell.
Name it Never as in "this value can never exist" or "this function can never return". Name it Void. However this is likely to confuse programmers from a C-family language background as Void is not (). Name it Bottom. Name it something else.
Unresolved questions
Is there time to make this change before 1.0?

One other alternative is to keep the ! as syntactic sugar for the not-type.

Make the panic! macro expand to begin_unwind(...).elim() instead of just begin_unwind(...) to avoid users having to add the .elim() themselves.

The advantage of the current built-in support for ! is that it unifies with any other type automatically, without the need for explicit elim() calls, and this works for anything that returns !, not just panic! or other macros. (I.e. this is what would belong in the Drawbacks section.) Until/unless Rust is capable of representing it as for<T> T directly, I would be in favor of keeping this. It's nice.
If we do want to add a library type instead of or in addition to it, I think it should be called Never.

The bottom type was removed in rust-lang/rust#14973, because of maintenance difficulty?
I don't think it's very important for 1.0 though, requiring the user to provide a must-be-never-ending closure Fn() -> ! seems unusual.

The advantage of the current built-in support for ! is that it unifies with any other type automatically, without the need for explicit elim() calls

How often do you call a diverging function from a non-diverging function without using panic! or assert! et. al? Having a whole extra construct in the language which breaks the ability to use things like Fn() -> T traits seems like large price to pay to avoid having to type .elim() occasionally.

and this works for anything that returns !, not just panic! or other macros

And similarly .elim() will work on anything that returns Empty.

If we do want to add a library type instead of or in addition to it, I think it should be called Never.

I quite like this. Then the name Empty could be reserved for a trait of types that are empty.

I don't think it's very important for 1.0 though

It's only important because it would be a backwards-incompatible change.

From an optimization perspective, the implementation of elim can call intrinsics::unreachable to get LLVM in on the unreachability of calls to elim or any code following a call to elim.
Bikeshed: elim should be called unreachable, since that's what it means.
Note that there exists (disclaimer: I wrote it) a crate with a similar type and helpers called void, whose code is here: https://github.com/reem/rust-void

Also, a similar empty type used to exist in std::any.

@canndrew: Why would it not be backwards-compatible (provided we choose to keep ! as syntactic sugar)? Can you provide an example of a program that would break?

@llogiq I meant if the ! syntax was removed. Too late for that now though.

Too late for that now though.

Agreed. Well, I think the ! syntax is at least obviously confusing. Whereas any of the suggested names would have been confusing to some, but not all. And reem's implementation seems to handle the cases where the usefulness outweighs the confusion. :smile:

Triage: Superseded by #1216


remove libmagic as a malice engine requirement

This prevents me from easily cross compiling and making statically compiled binaries 😢

https://github.com/CenturyLinkLabs/golang-builder


Combine sends

Now we assign one CPU core + one card queue for one send.
However if we want to send more than 14Gb/S by 64 byte packets we need two sends and partition before them. Which will take + one core per second send and + some time for partition.
This limitation is card limitation - not CPU one. So we can use one CPU (one send) that will send packets to both card queues alternatively.

Done by https://github.com/intel-go/nff-go/commit/e1034dd41e4ba434a388939d08ab2862d3c910fd


Mealie - database not retained between restarts

I am experiencing that changes to the database is not committed, it seems to reside in memory only. I belive this started occurring after upgrading to 1.0.1 (03-01-2023) and doing the required backup/restore from within Mealie.
If I add something in Mealie, then restarts the addon, it just disappears and reverts to the old DB version. What could be the cause of this? Would the best resolution be to uninstall Mealie and restore from the in-app backup?
-----------------------------------------------------------
 Add-on: Mealie (Omni):
 Mealie is a self hosted recipe manager and meal planner built in Vue
-----------------------------------------------------------
 Add-on version: v1.0.0-beta-5
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.2  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.5.4
 Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
 Defining permissions for main user :
User UID: 0
User GID : 0
-----------------------------------------------------------
/etc/cont-init.d/01-custom_script.sh: executing
[15:40:44] INFO: Execute /config/addons_autoscripts/mealie.sh if existing
[15:40:44] INFO: ... no script found
/etc/cont-init.d/31-nginx.sh: executing
[15:40:44] INFO: Exporting variables
ALLOW_SIGNUP=true
PGID=0
PUID=0
certfile=fullchain.pem
keyfile=privkey.pem
ssl=false
[15:40:44] INFO: No config.yaml found in /config/addons_config/mealie/config.yaml, using default parameters
Permissions adapted
[15:40:44] WARNING: Data migration for amd64
[15:40:44] WARNING: Data migrated to /config/addons_config/mealie_data ; you can now use the new addons. For aarch64, you need to do a manual backup and restore
[15:40:45] INFO: Starting app
[15:40:45] INFO: Starting app

Indeed it seems that the argument I used to change data dir doesn't exist. I've set an env variable that should do the same

Awesome that you had time to look at this! I will have a look inside the data dirs and if I'm lucky, I will find my data there. Anyway, the most important is that I can get it working again.
I'll let you know how it goes 😊

Hope it will work... A key element is to have frequent backups I usually backup my whole HA system once per week to Google drive using an add-on. By having backups of add-ons and /config it significantly decreases any chance of data lost, and allows to downgrade when needed!

Tests done :

[ ] Installed current version, add recipe, restart, check recipe stays
[ ] Try to mimick upgrade process
[ ] ...

The data is retained after restarts now with the latest version 👍
I have tried to look through some backups, but none of them contain any updates after april or so. Seems like my suspicion was right - nothing has been committed to the database? Does that make sense?

No worries. It is only a few recepies and som config.
What you suggest was my first thought as well. I have already tried a couple of the weekly backups witout any luck.
Thanks for the quick response with this matter!


Mouse visibility not updating until mouse is out of window.

Operating system or device - Godot version:
Windows 10, Godot 3.0
Issue description:
Mouse did not become visible until i moved the mouse out of window
Steps to reproduce:
set mouse mode to visible after being previously confined.

May be related to #4596 but I cannot understand what do you mean with set mouse mode to visible after being previously confined. Can you provide an excample project or code?

Okay I know what you mean NullNeska.
So if you are in a scene that has default mouse mode, then switch to a scene that has MOUSE_MODE_CONFINED the cursor is no longer visible, though active.
What Null means by out of window is even if you set MOUSE_MODE_VISIBLE AFTER the set CONFINED instruction the mouse is still invisible though no longer captured so you can move it off screen to say a 2nd monitor and when the OS API picks it up it becomes visible again and when you move it back into game screen/window it is visible and functioning.
My solution was to make sure to Input.set_mouse_mode(Input.MOUSE_MODE_CONFINED) BEFORE get_tree().change_scene(new_scene_with_confined_mouse) and you won't need to set it as confined in the new scene you load, as it will stay confined.
my scenes were full screen and on windows 10 and I have 2 monitors

@NullNeska Can you (or anyone else) still reproduce this bug in Godot 3.2.1 or 3.2.2beta4?

Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.


[ARCTIC-326] Hotfix read fileoffset

fix #326
Why are the changes needed?
It may cause exception when read arctic table.
Brief change log

Fix the fileOffsetIndex
The flink 1.12 and 1.14, 1.15 versions are affected.

How was this patch tested?

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

[ ] Add screenshots for manual tests if appropriate

[X] Run test locally before making a pull request

Documentation

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

LGTM, @zstraw  I'll merge to master.


[SPARK-46033][SQL][TESTS] Fix flaky ArithmeticExpressionSuite

What changes were proposed in this pull request?
The pr aims to fix flaky ArithmeticExpressionSuite.
https://github.com/panbingkun/spark/actions/runs/6940660146/job/18879997046

Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Manually test.
Pass GA.

Was this patch authored or co-authored using generative AI tooling?
No.

cc @kazuyukitanimura

Merged to master/3.5/3.4.

Thank you, @panbingkun and @kazuyukitanimura .


2.a. Formal Approach

04/03/22 - 11:00
Brandon
Document previously contained an outline of what needed to be written in the document.
All of the points have been fully written up, once this document has been reviewed, it is pretty much ready for submission, unless any changes are required.

07/03/22 - 17:10
Made changes as requested by @YumisZyutyu and added the references to the bottom.


Max depths flag with connections

If I have the following schema and set the depth generation to 6. When I run the generated getUser query, I can't reach down to getUser.posts[0].votes. I only get to getUser.posts[0].id
Is it not possible to nest a schema like this and reach the objects in the connections?
I'm using amplify codegen for iOS Swift.
type User @model {
    id: ID!
    name: String!
    votes: [Vote] @connection(name: "UserVotes", sortField: "createdAt")
    posts: [Post] @connection(name: "UserPosts", sortField: "createdAt")
}

type Post @model {
    id: ID!
    createdAt: String
    user: User! @connection(name: "UserPosts", sortField: "createdAt")
    text: String
    votes: [Vote] @connection(name: "PostVotes", sortField: "createdAt")
}

type Vote @model {
    id: ID!
    createdAt: String
    user: User! @connection(name: "UserVotes", sortField: "createdAt")
    vote: Int!
    post: Post! @connection(name: "PostVotes", sortField: "createdAt")
}

Seems I didn't set the depth flag high enough, needs to be set 7  in this case...


Refactors

Thanks for contributing but the minor changes here contains format errors etc that in turn would need new refactoring. Also, since it's only in test classes it's not worth merging since it'll create merging needs for other "more important" PRs which costs time we dont' have.


Buy airtime for Others Option is missing

I noticed that the Buy airtime for Others option is missing from the app, and I believe this feature is essential for many of your users who often purchase airtime for their friends and family :wink:

I would appreciate it if you could check into this situation and provide a solution as soon as you can. I appreciate the prompt reply you provided to this matter.

Thanks for the feedback @Alfredbis29 , however, after research I found that not so many people perform such operations (buying airtime for other people), It is often a one-time thing that

Not enough feature requests


OceanBase Support

Search before asking

[x] I had searched in the issues and found no similar feature requirement.

Description
 In sql task nodes views，I can not select “OceanBase source” in  data source combobox . It means I could not use OceanBase sql in task nodes. But in data source views, I can create OceanBase data source.
Could the community solve my question just by  improving ui model adding “OceanBase source”  or  carrying out more improvements?
OceanBase support is  important to us and my company.We  will look forward to your help

Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Thanks for your helps