Add benchmark test suite

Sending this mainly as a starting point for discussion on how and what should be benchmarked in Redux & react-redux.
Few points to begin with:

The production builds should be used for benchmarking
It should not be required to open devtools when running the bench

Wow, thank you! It's a great start.

@epeli I know it's been a while, but any progress on this?

Unfortunately no. Better close this for now.


I get this error too often: "Blocked: too many filters"

I get the above error whenever I request an event from booger.pro. Here was the text of the first request in that image:
["REQ","004d18b901c500bb",{"authors":["d211d062fc8a2accedc03f5af50c11a84b3eb02c86676333a0ec78edf7516f7c"],"kinds":[12196,42199]},{"authors":["d211d062fc8a2accedc03f5af50c11a84b3eb02c86676333a0ec78edf7516f7c"],"kinds":[42198],"since":1691265024},{"#p":["d211d062fc8a2accedc03f5af50c11a84b3eb02c86676333a0ec78edf7516f7c"],"kinds":[4]},{"authors":["d211d062fc8a2accedc03f5af50c11a84b3eb02c86676333a0ec78edf7516f7c"],"kinds":[42197]}]

That request has 4 filters, which other relays are fine with, so I don't know why booger thinks it's too many.
But it gets worse. Here is the text of the second request in that image:
["REQ","fccea3cb93ee9509c6722f74",{"ids":["abababababababababababababababababababababababababababababababab"],"kinds":[1]}]

This request only had one filter and booger still said "too many filters." So I think booger is currently unusable for making requests.

Thanks for reporting!
This could be a bug (I wouldn't be surprised).
If this isn't a bug it would mean your web socket OR ip has >=1000 filters already pending. Just to double check, it doesn't?


HTML5 validation failures

Just having a play with this theme (thanks for your work, it looks awesome!) and spotted a couple of minor things are currently being flagged by the W3C HTML Validator:

It's apparently invalid to use http-equiv for any HTTP header, only those listed in the Pragma directives here
Use of the itemprop attribute requires the itemscope and itemtype to be defined.

I'm happy to pop some PRs up for these but I also wondered if you'd like the idea/would accept a PR to add a Github Action to automatically validate the build of the example site with the checker going forward?

Hi @dijitali, thank you for getting in touch 👋.
http-equiv
This might not be »valid«, but it's just a fun meta-tag we inherited from the original bearblog. See

Original: https://bearblog.dev/accounts/login/?next=/dashboard/
Example blog: https://herman.bearblog.dev

The source code is here: https://github.com/HermanMartinus/bearblog/blob/master/templates/base.html#L5.
ℹ Here's the story behind this non-standardised HTTP header: https://xclacksoverhead.org/home/about
itemprop
This one baffles me a little bit. We are using Hugos very own _internal/schema.html-template here. The code is over at https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/schema.html.
I went and checked what's up on the Hugo News-blog and they actually use it just in exactly the same way we do. Thus they get the same error on the w3c-validator, see https://validator.w3.org/nu/?doc=https%3A%2F%2Fgohugo.io%2Fnews%2F
If you want to persue this further I'd suggest opening up an issue on the main Hugo repo, which includes the _internal/schema.html-template, so this can be fixed centrally.
➡ Thus - I think - we'll just have to live with these errors on the validator (for now?).

If you have a requirement for your personal website to be 100% valid against the w3c-validator you may overwrite the

baseof.html (This includes the non-valid header) and
seo_tags.html (This includes the non-valid item props)

templates locally.
I hope that helps 🙏.
Kind regards and have a good weekend 🏝.

Thanks for such a considered response!  Totally on board with you on both these points, I just hadn't realised how much was inherited by this repo.
The first one would be ideal if it could be set as an actual HTTP response header but totally outside the scope of this and it looks like the second point has already been raised as a Hugo bug in https://github.com/gohugoio/hugo/issues/7431.
Hope you have a great weekend too!


Add Warning for playlist as it may violate GitHubs tos

Running this tool on an entire playlist is likely to trigger github to automatically suspend the users account as it violates the tos.

I asked a github staff member, I will let you know the answer!

Any updates?

It would seem to be a case that should not generate problems, but in my opinion we should still leave the warning


Issue #3: Include hashes of both old and new file

Rather than only including the hash of the old file, it might be a good idea to also include the hash of the new file so that we can check that the application of the patch creates the desired file.

Added in https://github.com/1f604/diffpatchlib/commit/f233011bbbbabf6ffa7359b0931b5adefbc3f089


Added Grady Booch books

The most complete software architecture books collection

Hi @zarya-gh thank you for your contribution.
I have 2 small requests.

The Grady Booch collection seems like a great resource. My only concern is that it isn't super curated. Do you think you could pick just a couple books from that list that you've personally read or would recommend that way someone could just direct link straight to that one without needing to do research on their own?
Could you explain a bit more about what the "Coders at work: Reflections on the Craft of Programming" teaches? I want to make sure it gets put in the correct category. The "Learn from the top programmers" section has a chance of only having that book in it for awhile

hi, Jordan!
Grady Booch's book collection impressed me as a whole. It showed me what depth of knowledge is required to become a truly professional at what you do.
"Coders at work" book presents creative thinking and working habits of the most successful software engineers. It can help senior engineers to learn and improve by watching others.


The import java.nio.file cannot be resolved

import java.nio.file.Files;
In android studio, the import is Ok. But when I use j2objc to translate I get an error:
The import java.nio.file cannot be resolved

The java.nio.file package has been supported since version 2.7. You'll need to download and install either that release or better yet, the latest release.


NIFI-12402 add option to user can avoid an inactive indicator is crea…

…ted even if there is no actual activity when processor is started

Summary
NIFI-12402
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Hi @dan-s1,
Codes were updated. Please help to review it again.
Thank you!

LGTM +1


[Added] Few more common regex patterns

I added some commonly used regex like Email, URL, Map co-ordinates validation.
Thanks for such a great compilation of the resource & codes. Whenever I'll be free, I'll try contributing more to this repository.

Well I didn't saw it, my mistake. You can delete this pull request!


purchase() error: Can only use lower 16 bits for requestCode

Hi,
After upgrading react native to v 0.59.10, purchase() method doesn't work anymore. it results with following message:
E_PURCHASE_ERROR Can only use lower 16 bits for requestCode

I solved it. in case if you faced it too:
i implemented purchase method with this line of code:
InAppBilling.purchase(item.sku, 'someText', 123456)
and it was working before upgrading react native.
then i just lower the developer_payload from 123456 to 123 and the error gone.
Good_Luck.


Enum with Description(s) mapping

I would like to map the values in a column to an enum by way of the enum DescriptionAttribute. Is there a way to do this?
Looking for how to map the value 'Bar Baz' in column n to MyEnum.BarBaz (not the space in the description)?
public enum MyEnum
{
    [Description("Foo")]
    Foo,
    [Description("Bar Baz")]
    BarBaz
}

Currently don't support custom values through attributes.
One option is to define a mapping class.
E.g.
private class CustomClass
{
    public MyEnum EnumField { get; set; }
}

public class CustomClassMap : ExcelClassMap<CustomClass>
{
    public CustomClassMap()
    {
        Map(c => c.EnumField)
            .WithColumnName("EnumFieldColumnName")
            .WithMapping(new Dictionary<string, MaritalStatus>
            {
                { "Bar Baz", MyEnum. BarBaz    }
            });

            // Map everything else
    }
}

Hopefully this helps

I'm going to close this as I think the suggestion above solves the question.


Remove boilerplates and fix bugs

Requires: https://github.com/jsinger67/parol_runtime/pull/2
I removed the boilerplates by using re-exports from parol_runtime.
Also, I fixed two bugs:

parol generates a comment like /* */ */ for token '*/', and this causes a compile error.
#![allow(unused_imports)] generated by parol causes a compile error when using import!() macro. https://github.com/google/flatbuffers/issues/6261

Thanks a lot for your great work 🥇

I have problems with generated crates via parol new subcommands that relate to the removal of dependencies in user crates.
error[E0433]: failed to resolve: could not find derive_builder in the list of imported crates

parol_runtime is updated to version 0.9.0
parol's changes are on main branch

Please have a look at this.
To reproduce this, please issue the command
parol new -b -p .\my-grammar
then
cd .\my-grammar\
and
cargo build

Thanks for merging!

Please have a look at this.

I'll try to fix that as soon as possible.

Fixed in https://github.com/jsinger67/parol/pull/24

@ryo33, I experienced a problem with features of crates that are re-exported for reuse from parol_runtime crate.
I used to enable the feature fancy of miette to get useful error reports in crates generated by parol new like this:

Error: parol_runtime::parser::unprocessed_input
× Failed parsing file ./test.txt
╰─▶ Unprocessed input is left after parsing has finished
╭─[./test.txt:5:1]
5 │
6 │ # End
· ───┬──
·    ╰── Last processed token
╰────
help: Unprocessed input is left after parsing has finished

But currently I get this:

Error: Diagnostic { message: "Failed parsing file ./test.txt", code: "parol_runtime::parser::unprocessed_input", help: "Unprocessed input is left after parsing has finished", labels: "[LabeledSpan { label: Some("Last processed token"), span: SourceSpan { offset: SourceOffset(86), length: SourceOffset(5) } }]" }
NOTE: If you're looking for the fancy error reports, install miette with the fancy feature, or write your own and hook it up with miette::set_hook().

The feature fancy is not enabled in parol_runtime itself, because it is not needed there, which explains the changed behavior.
I think that it isn't possible to use a re-exported crate and thereby changing the used feature set.
Do you have any idea how to deal with that?
I could simply add the line
miette = { version = "5.2.0", features = ["fancy"] }

to the crate's Cargo.toml but this seems awkward.

I tried it and found it difficult at present.
https://github.com/rust-lang/cargo/issues/674

You are right.
miette gave me the opportunity to get quickly to a result. For instance, I used support from miette like miette::protocol::SourceSpan to covey the error position to the caller.
This can surely be redesigned to emphasize the role of parol_runtime and also the generated parsers as libraries.
I think it should be possible to use e.g., thiserror or anyhow as a substitution and miette, if desired, as error wrapper in applications using those parsers.
This choice should be given to the user.


buildkite build premerge-checks 63150

Describe the bug
Sanitizing the compiler creates bugs
To Reproduce
Steps to reproduce the behavior:

Submit

Expected behavior
No crashing
Screenshots
If applicable, add screenshots to help explain your problem.

Can you please give us more context? Do you have an example of a failing
build?
swang206 @.***> schrieb am Mo., 1. Nov. 2021, 00:25:

Describe the bug
Sanitizing the compiler creates bugs
To Reproduce
Steps to reproduce the behavior:

Submit

Expected behavior
No crashing
Screenshots
If applicable, add screenshots to help explain your problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/llvm-premerge-checks/issues/363, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYJMCHL73V34ANEHFK34BTUJXF7FANCNFSM5HC2PDRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


User Retention Feature

Dashboard Issues

rancher/dashboard#11303

Ran backend automation tests(validation) on v2.9-d2fa8a7d6116c48a814ee7983af522d614461e49-head & looks good.

Dashboard card is closed and BE validations looks good & closing this card.


Docs

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

ID: 1f4fe06e-d692-c330-a651-d51fec279a6a
Version Independent ID: ec4c836d-f1a4-e6c1-59c1-14fce62bc2ec
Content: What is Azure Sentinel?
Content Source: articles/sentinel/overview.md
Service: azure-sentinel
Sub-service: azure-sentinel
GitHub Login: @yelevin
Microsoft Alias: yelevin

@Kalakaarboyz1 Thanks for reaching here! could you please elaborate your query to help you better on this.

Since more information is needed in order to take action, we will now proceed to close this thread. @Kalakaarboyz1 please create a new issue detailing the desired changes for the document.

I think i did a very bad mistake to informed you guys. You just closed this
without asking me anything i did not know that indians handling these issues
On Wed, Jul 21, 2021, 8:50 PM Marilee Turscak - MSFT <
@.***> wrote:

Since more information is needed in order to take action, we will now
proceed to close this thread. @Kalakaarboyz1
https://github.com/Kalakaarboyz1 please create a new issue detailing
the desired changes for the document.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/78626#issuecomment-884296912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AURHMGYA3WDGKIRZYBKISRTTY3UFFANCNFSM5AXDRJCQ
.


Support for greedy layer-wise pretraining

I'm trying to build a deep-belief network. Is there a way to use a set of pretrained weights to initialize the parameters of the MLP? Is there plan to implement RBMs and autoencoders?

I believe PyLearn2 supports auto-encoders, or would require minor additions to do so.  However, I believe those architectures are being deprecated in the code...
My biggest question is, what problem are you trying to solve?  Conventional wisdom for "modern" NN training is that you're probably better off doing supervised only, either with your own dataset or a related one if necessary.

I am using an autoencoder because I only have a portion of my dataset which is labeled. I want to use the unlabeled portion of my dataset to do unsupervised training and then finetune using the labeled portion.
Pylearn2 does support autoencoders and RBMs, however, since they are trained using the TransformerDataset, I am not sure how to do this in scikit-neuralnetwork.

Ah, I see. Thanks for clarifying!
sknn so far wasn't implemented with this in mind, so I'm not sure how this would be integrated yet... I think we'll keep this feature back for after the 0.1 release, but if you have any more information/prototypes they'd be very welcome.

Thank you for the quick answer.
I think I will try to do a prototype. I will do a pull request if I have something.

@leconter: Started looking into this... I presume the code will need to create a separate AutoEncoder model, train that, then extract the weights into a MLP model?

That is what I have so far. Pylearn2 has a pretrained layer type in mlp. I created a separated class to train the autoencoder layers which returns the pretrained layer, and I use those layers in the mlp constructor. The only addition to the mlp class is to add a condition in the _create_layer method to call the pylearn2 pretrained layer constructor.

@leconteur: I found your branch, did you commit those changes to it?

Not yet, I have to clean up my code. I plan to do this next week.

I can cope with messy code, ask @ssamot :-) Just let me know when you're ready!

For reference: prototype by @leconter available as #50 and first-pass integration of just the auto-encoder in #52.

OK, #52 has landed and going to prototype the pre-training code.

Added new PR #58 that does weight transfer from the existing auto-encoder module.  See the PRETRAIN conditional in bench_cifar10.py.
@leconteur If you have any feedback about the API or functionality, let me know.

To continue the discussion from the previous pull request, I'm not using the pylearn2 PretrainedLayer type because it doesn't play well with serialization, and neither of us wanted to sacrifice that core feature.
I think support for Rectifiers would be very welcome here, but it can be a separate PR.

Closed by #58.


How to set minimum date in calendar?

In my app, there's 2 option to pick date. 1. From date and 2. To date.
both options are different and action is also different. Now i want something like this.
When user pick from date then i want to allow the user to select the date between From Date to Current Date.
I have review all available option but wasn't found any property that will set minimumDate in calendar.

In above screenshot you can see i have selected 06-05-2020 as From Date now i want the user to select To Date between 06-05-2020 to 20-05-2020.
Will you please guide me how can i do that?
Thanks

Hi, If you still need a solution for this, just use the following datasource method from the protocol.
func WWCalendarTimeSelectorShouldSelectDate(_ selector: WWCalendarTimeSelector, date: Date) -> Bool {
        if date <= maxDate{
            return true
        }else if date >= minDate{
            return true
        }
        return false
    }

@sibahota059 , Thanks for your help. let me try this.


Typo

Oh dear I'm sorry I missed this! Turns out I accidentally stopped following this repository awhile ago :(
In any case, in the meantime, this has since been removed so I'm going to close. Thanks for the PR though!


mismatched types when attempting to import helios and ethers into the same project

Trying the sample code in the README leads me to a few compilation errors such as this:
error[E0308]: mismatched types
   --> /home/naps62/.cargo/git/checkouts/helios-b3bc464b79507b80/e4071fe/execution/src/evm.rs:256:13
    |
255 |         Ok(Some(AccountInfo::new(
    |                 ---------------- arguments to this function are incorrect
256 |             account.balance,
    |             ^^^^^^^^^^^^^^^ expected struct `primitive_types::U256`, found struct `ethers::types::U256`
    |
    = note: struct `ethers::types::U256` and struct `primitive_types::U256` have similar names, but are actually distinct types

I tried overriding ethers to use the same fork specified in this repo, but that seems to have changed nothing

Fixed in #129


FindBI role (looks like) not working with Find 12.0.0

Dear Sirs,
looks like the FindBI Idol role is no more working in Find 12.0.0
see the attached image

Also I attach my (unchanged, since Find 11.6) config.json
config.json.zip
My launching command is as follows:
java -Dserver.reverseProxy=true -Dfind.reverse-proxy.pre-authenticatedroles=FindUser,FindBI -Dfind.reverse-proxy.pre-authenticated-username=sascuser -Didol.find.home=.\home -Dserver.port=15080 -jar find.war_12.0
where 'sascuser' is a mamber of both FindBI and FindUser roles
I do not see some familiar UI items anymore, such as:

a text input field for filtering database and parametric fileds names
SAVE and SAVE SNAPSHOT buttons
Share Saved Searches link
and so on...

All the UI options you mention are controlled by the presence of the FindBI role on the user. It's because you have a typo, there's a missing '-' between 'authenticated' and 'roles' in your
-Dfind.reverse-proxy.pre-authenticated-roles=FindUser,FindBI

If you stop the existing server, add the missing '-' to the your launch command and run it again it should work.

You are right,
closing...


Removing duplicate project.

Noticed a duplicate project listing, so I removed it.

@bonniewhy Thank you!

@bonniewhy I have sent an invite, so if you are interested in being a collaborator of this project, please accept it. Then you can merge PR's by yourself.


Cutting edge theme->>merge to main

Summary by Sourcery
This pull request introduces new tools for QR code generation and ASCII art conversion, enhances the README and 'About' page with more detailed information, and improves navigation and styling across the project.

New Features:

Introduced a new QR Code Generator tool with customizable options for size, error correction, colors, and rounded corners.
Added an ASCII Art Converter tool that transforms text into ASCII art.

Enhancements:

Updated the README.md with detailed project information, repository stats, themes, features, and usage instructions.
Enhanced the 'About' page with additional sections on mission, current services, upcoming features, and community involvement.
Improved the navigation bar generation logic in common.js to dynamically adjust links based on the current path.
Updated the color-palette.js to use a more descriptive ID for the uploaded image element.
Added new styles to color-palette.css for better image display and text color.

Documentation:

Expanded the README.md to include comprehensive details about the project, including themes, features, and usage instructions.

Updating main with branch


fix spacing and modal width

In this PR:

Task: https://trello.com/c/s7o93mGt/47-update-spacing-on-alert-and-tooltip-component
Tooltip: padding: 11px SPACING.small;
Alert: top and bottom padding = 7px | from icon to left edge SPACING.small and from icon to text SPACING.small

Task: https://trello.com/c/9dLnuhhq/80-update-immersive-modal-width-on-desktop-to-616px
Added size documentation, adjusted default size from 576px to 616px

File using "medium" for width prop was removed from PocketDerm. We can just remove the size option here so we provide more friction to deviate from the design system

@benkolde @snags88 Ok removed the size prop option from ImmersiveModal and related docs


fix: evasion suffix must be the same everywhere

Looks good. Is this related to an issue, or do we want to add more tests for the additional chars?

This is an oversight that I should have fixed a month ago.

This PR and #3328 are preparations for the removal of the *-with-params.ra files.

@fzipi I still need your approval here.


bug: Setting css height on

Type: bug
Platform: ios 6,7,8 webview
When i set the height of text input with css(i need big input), this input becomes uneditable in iOS6,7,8. It gets focus but typing does not produce any result. Removing height setting from it in safari dev tools - immediately fixes it.

Little demonstration:

Greetings @anri-asaturov!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


[BUG] Cannot Create a VM using the API (DataVolume api is not present in cluster)

Describe the bug
I want to create a new VM using the API. But when I run my command it already fails at:
{
    "type": "error",
    "links": {},
    "code": "Invalid",
    "message": "admission webhook \"virtualmachine-validator.kubevirt.io\" denied the request: DataVolume api is not present in cluster. CDI must be installed for DataVolume support., DataVolume api is not present in cluster. CDI must be installed for DataVolume support.",
    "status": 422,
    "type": "error"
}

To Reproduce
I use this as a post request on postman. I know it is not really configured yet, but I already get an error.
It would be great to have better docs on this:
{
   "apiVersion": "kubevirt.io/v1",
   "kind": "VirtualMachine",
   "metadata": {
      "name": "test",
      "namespace": "default"
   },
   "spec": {
      "dataVolumeTemplates": [
         {
            "apiVersion": "cdi.kubevirt.io/v1beta1",
            "kind": "DataVolume",
            "metadata": {
               "annotations": {
                  "harvesterhci.io/imageId": "default/image-mxqpm"
               },
               "creationTimestamp": null,
               "name": "gc-harv-disk-0-fzopl"
            },
            "spec": {
               "pvc": {
                  "accessModes": [
                     "ReadWriteMany"
                  ],
                  "resources": {
                     "requests": {
                        "storage": "10Gi"
                     }
                  },
                  "storageClassName": "longhorn-image-mxqpm",
                  "volumeMode": "Block"
               },
               "source": {
                  "blank": {}
               }
            }
         },
         {
            "apiVersion": "cdi.kubevirt.io/v1beta1",
            "kind": "DataVolume",
            "metadata": {
               "creationTimestamp": null,
               "name": "gc-harv-disk-1-bquaq"
            },
            "spec": {
               "pvc": {
                  "accessModes": [
                     "ReadWriteMany"
                  ],
                  "resources": {
                     "requests": {
                        "storage": "200Gi"
                     }
                  },
                  "storageClassName": "longhorn",
                  "volumeMode": "Block"
               },
               "source": {
                  "blank": {}
               }
            }
         }
      ],
      "running": true,
      "template": {
         "metadata": {
            "annotations": {
               "harvesterhci.io/diskNames": "[\"gc-harv-disk-0-fzopl\",\"gc-harv-disk-1-bquaq\"]",
               "harvesterhci.io/sshNames": "[]"
            },
            "creationTimestamp": null,
            "labels": {
               "harvesterhci.io/creator": "harvester",
               "harvesterhci.io/vmName": "gc-harv"
            }
         },
         "spec": {
            "domain": {
               "cpu": {
                  "cores": 8,
                  "sockets": 1,
                  "threads": 1
               },
               "devices": {
                  "disks": [
                     {
                        "bootOrder": 2,
                        "cdrom": {
                           "bus": "sata"
                        },
                        "name": "disk-0"
                     },
                     {
                        "bootOrder": 1,
                        "disk": {
                           "bus": "virtio"
                        },
                        "name": "disk-1"
                     },
                     {
                        "disk": {
                           "bus": "virtio"
                        },
                        "name": "cloudinitdisk"
                     }
                  ],
                  "inputs": [
                     {
                        "bus": "usb",
                        "name": "tablet",
                        "type": "tablet"
                     }
                  ],
                  "interfaces": [
                     {
                        "bridge": {},
                        "macAddress": "ea:d6:55:49:a0:5e",
                        "model": "virtio",
                        "name": "default"
                     }
                  ]
               },
               "machine": {
                  "type": "q35"
               },
               "resources": {
                  "requests": {
                     "memory": "10Gi"
                  }
               }
            },
            "evictionStrategy": "LiveMigrate",
            "hostname": "gc-harv",
            "networks": [
               {
                  "multus": {
                     "networkName": "vlan1"
                  },
                  "name": "default"
               }
            ],
            "volumes": [
               {
                  "dataVolume": {
                     "name": "gc-harv-disk-0-fzopl"
                  },
                  "name": "disk-0"
               },
               {
                  "dataVolume": {
                     "name": "gc-harv-disk-1-bquaq"
                  },
                  "name": "disk-1"
               },
               {
                  "cloudInitNoCloud": {
                     "userData": "ssh_authorized_keys:\n  - 'github:test'\nwrite_files:\n  - path: /etc/conf.d/qemu-guest-agent\n    content: GA_PATH=/dev/vport2p1\n    owner: root\n    permissions: '0644'\n"
                  },
                  "name": "cloudinitdisk"
               }
            ]
         }
      }
   }
}

Expected behavior

Environment

Harvester ISO version: 1.1.1

Can we please provide the support for DataVolume on harvester?  Otherwise we will not be able to use the provided API to create the VM.
CDI must be installed for DataVolume support., DataVolume api is not present in cluster. CDI must be installed for DataVolume support.

I am running into the same error when trying to use the API.

I am running into this same issue.  Maybe @guangbochen could give some guidance here?

We removed CDI support from https://github.com/harvester/harvester/issues/1058. May you try to transfer dataVolumeTemplates to harvesterhci.io/volumeClaimTemplates annotation? For example:
metadata:
  annotations:
    harvesterhci.io/volumeClaimTemplates: '[{"metadata":{"name":"source-vm-disk-0-d8w5q","annotations":{"harvesterhci.io/imageId":"default/image-bd6vb"}},"spec":{"accessModes":["RedWriteMany"[],"resources":{"requests":{"storage":"10Gi"}},"volumeMode":"Block","storageClassName":"longhorn-image-bd6vb"}}]'

We removed CDI support from #1058. May you try to transfer dataVolumeTemplates to harvesterhci.io/volumeClaimTemplates annotation? For example:
metadata:
  annotations:
    harvesterhci.io/volumeClaimTemplates: '[{"metadata":{"name":"source-vm-disk-0-d8w5q","annotations":{"harvesterhci.io/imageId":"default/image-bd6vb"}},"spec":{"accessModes":["RedWriteMany"[],"resources":{"requests":{"storage":"10Gi"}},"volumeMode":"Block","storageClassName":"longhorn-image-bd6vb"}}]'

can you post a whole working request with example data?

I had posted in a related issue #4470 before seeing this one. I had installed the CDI manually, and things are working to use dataVolumeTemplate, but the volumes don't show up as being linked to the VMs. Editing the VM shows it has no Volumes, and the Volume shows no attached VM, but my data seems to be persisting through shutdowns.
If using this harvesterhci.io/volumeClaimTemplates is the supported way to do this, I'd like to switch to that, but I'm unclear how to use it. In the posted example, it looks like you already have a reference to existing volumes. The way I have things set up, the volumes get created so I don't have anything to reference. Here is what I'm doing right now with dataVolumeTemplate
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: k8s-control1
spec:
  runStrategy: RerunOnFailure
  dataVolumeTemplates:
  - metadata:
      name: k8s-control1-volume
    spec:
      storage:
        volumeMode: Block
        resources:
          requests:
            storage: 20Gi
        accessModes:
          - ReadWriteOnce
      source:
        registry:
          url: "docker://quay.io/fedora/fedora-coreos-kubevirt:stable"
  template:
    spec:
      .......
      volumes:
      - dataVolume:
          name: k8s-control1-volume
        name: k8s-control1-root

How can I rewrite this to use the harvesterhci.io/volumeClaimTemplates with the same functionality?

It is also unclear to me how I would use the volumeClaimTemplates to create multiple virtual machines via a VirtualMachinePool object since the template has a name associated to it so all vms would try to get the same volume claim. I am trying to deploy some VMs using FluxCD and I would like to use a VirtualMachinePool as opposed to creating the individual VMs manually.


IzPack Installer

The installation of a sample SolRDF is too much technical, regardless the two ways described in the "Get me up and running" page.
Building things from source [1] is useful in case you've a bit of familiarity with Java, Maven: it will download all required software and dependencies but at the same time you could meet some annoying Maven related things. This is probably what happened to the user who opened the issue #75.
Installing the download bundle [2] (Solr home + dependencies) provided in the GitHub still requires some manual step and that could be a boring thing for a non technical user who would like simply to have a quick and first taste of SolRDF.
IzPack could be an ideal choice for supplying an easy installer for a sample SolRDF instance. The installer is a single jar that will automatize the whole installation process.

[1] https://github.com/agazzarini/SolRDF/wiki/User Guide#if-you-dont-have-solr-installed
[2] https://github.com/agazzarini/SolRDF/wiki/User Guide#if-you-already-have-solr-installed

Maybe using Docker could be another route for us to investigate. Perhaps we should look into how the Solr-Dockerfile https://github.com/makuk66/docker-solr has to be modified to make things work for SolRDF...

Yes yes absolutely, this morning Martin send a post about this thing and
I completely agree. I don't know IzPack and that "non functional" thing
would require some time. Instead using a VM image or something like that
could be the best option, as it's just matter to install the software
and put the VM somewhere (I  created a dropbox account so we could use
links coming from public folder)
On 05/19/2015 03:40 PM, Andre Hagenbruch wrote:

Maybe using Docker could be another route for us to investigate.
Perhaps we should look into how the Solr-Dockerfile
https://github.com/makuk66/docker-solr has to be modified to make
things work for SolRDF...
—
Reply to this email directly or view it on GitHub
https://github.com/agazzarini/SolRDF/issues/76#issuecomment-103498568.


Heroku API

🎯 Title and Issue Number
Heroku API
Fixes #358 issue
Closes #358<issue_no>

🗒 Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x]  I have gone through rules of when PR will get merged.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have followed proper file structure.
[x] I have gone through CONTRIBUTING GUIDELINES.md.

Thank you for contributing!❤
Don't forget to show some love by ⭐ the repository!
@dishamodi0910, view this PR and if any changes required let me know, otherwise kindly merge into main.

Hey @sreevidya-16, Thank you for creating PR! We will review it super soon. 😇❣
As we continue to evolve and innovate, we encourage you to share your ideas, feedback, and code to help us push the boundaries of what's possible in the world of APIs🚀.
We hope you have followed CONTRIBUTING GUIDELINES.
Thank you for being an essential part of our community. Together, we'll keep building amazing things!
Don’t forget to ⭐ our repository!
Happy Coding!✨
Will See you soon❣

@sreevidya-16 We're thrilled to inform you that your pull request has been successfully merged into the APIverse🚀🎁
Your hard work, dedication, and expertise have made a significant impact on our project, and we couldn't be more grateful for your contributions.😇
Your code will now be a part of our growing ecosystem, helping developers worldwide to create exceptional APIs.❣🔥
Happy Coding! ✨
Will See you soon❣

Thank you @Kritika30032002, @dishamodi0910


SeqLengthWarmup for non-HuggingFaceModel?

Currently, the SeqLengthWarmup algorithm requires the model to be a HuggingFaceModel. Is this restriction necessary?
RuntimeError: SeqLengthWarmup requires state.model to be of type HuggingFaceModel, not of type <class 'project.composer_model.Model'>

Thanks!!

I believe the actual requirement is actually that the batch is in the expected format of a huggingface model, and it likely works with any model (except for the runtimeerror you hit).

If you'd like to test this out and open a PR, we're always happy to take contributions :)

Closing. Tracking elsewhere as low pri. We're open to community suggestions!


chore: linting experiment

See the added README.md

@alexeagle this is old and untouched so I'm closing for now...


Fix: Poller stops forever when max_task_count reached

Changes
If max_task_count is exceeded, the poller will wait for 5 seconds before polling again for that task type. The time to wait is also configurable.
API Updates
New Features (required)
Added optional argument for ZeebeWorker: poll_retry_delay. Defaults to 5 seconds.
Deprecations
No Deprecations
Checklist

[x] Unit tests
[x] Documentation

References
Fixes #201

Ready for review @JonatanMartens


Missing jquery file

The source code tries to get jquery-3.4.1.min.js but it is not in that folder under master branch.
Error thrown in django:
"GET /static/nextbox_ui_plugin/jquery/jquery-3.4.1.min.js HTTP/1.1" 404 1758
I think it needs to be added to the specified directory.

shouldn't that be 3.6 if is is needed?

I don't know much about jquery but It seems 3.6 is the latest version and I guess it would be great to have it. I though maybe the code uses v3.4 for backward-compatibility.

This is cleaned up and deprecated now.


Use SceneId enum

Renames System::RKSceneId to EGG::SceneId and uses it more. This also replaces a couple of pointer arguments with references for safety reasons, but that could be easily reverted if disliked.

It's likely that we do not want to move the game-specific scene IDs out of host_system and into EGG as the library is not game-dependent.

Nice work!


Automatically build and push the docker image when tagging a new version

This closes #1246

Thanks all, merging...
@caipengbo Can help to push a new tag to have a try, the DOCKER_USERNAME and DOCKER_PASSWORD had existed before if my memory serves.

This is already discussed at:

https://github.com/apache/incubator-kvrocks/pull/588#issuecomment-1131320266
https://github.com/apache/incubator-kvrocks/pull/752#issuecomment-1194936068

OK, let's reverse this change and do them manually.


Target temp increment settings

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
My thermostats only support 1degree increments for their targets, so the mapping from the group to the items can be a little off.
Describe the solution you'd like
Either add a setting to control the increment levels OR detect the increment levels supported by the items and automatically set the group to the most precise value among them.  Bonus points for both as it would let users configure things to work how they want, but make things match the items out of the box.
Describe alternatives you've considered
None, just ignore it and know the temps will be set to the next degree up when on a .5.
Additional context

Confirmed, the new feature works great - thanks!


[Feature] Option to adjust video playback speed

Is your feature request related to a problem? Please describe.
It'd be nice to be able to adjust video playback speed.
Describe the solution you'd like
Perhaps a "settings" button in the video player and speed options there (0.25x, 0.5x, 0.75x, 1x, 1.5x, 2x, etc).
Describe alternatives you've considered
Additional context

See comment in #353


Asset Crashing Site on iOS

We have an animated asset that has a pretty large export from Adobe Animate.
.js file - 700k
shapes file - 3megs
When we use it in our site, it works fine on desktop, but when we load the asset on iOS devices the site crashes shortly after the page loads.
We're assuming, given that it's only happening on iOS that this is most likely a memory issue. Would that be a fair assessment? Are animations loaded when they are played? Does the memory consumption increase with time? We tried reducing the number of animations it played and that seems to increase the time before the crash.
Do you have any recommendations on the best way to handle this? The asset is composed of vector shapes in Animate as opposed to bitmaps, would converting it to bitmaps help?
Thanks!

Vectors are generally a terrible idea for lots of complex things. Allocating all that memory with PIXI.Graphics objects is kinda of a mess. My suggestion is that you use this JSFL script (https://github.com/springroll/flashtoolkit#utilitiescopy-layers-to-bitmap) this will convert each frame to a bitmap (non-destructively). It's a little time consuming to convert complex animation, but makes a big difference.

Thanks! We'll try this out.

Any follow-up on this @GopherwoodTodd? Feel free to close if you're satisfied.

@bigtimebuddy, yeah that worked. It was a bit of work to get things converted, and the script seemed to fail semi-randomly when trying to convert certain pieces, but we eventually got there. Thank you for the help.


Remember source string for empty/null nodes

Hi there, I can't seem to be able to stringify null as expected, any idea what can be wrong?
repro:
const YAML = require('yaml')

let doc = YAML.parse('hi:')

console.log(doc) // 'Object {hi: null}'

// expected string: 'hi:'
console.log(YAML.stringify(doc)) // '? hi'

YAML.scalarOptions.null.nullStr = ''

console.log(YAML.stringify(doc)) // '? hi'

YAML.scalarOptions.null.nullStr = '~'

console.log(YAML.stringify(doc)) // '? hi'

The option to do what you want is { simpleKeys: true }. This isn't the first time this is asked, so I think I need to find a way to improve the docs on this, to make it clearer/more discoverable.

Also, this is a bit besides what you're reporting, but the string representation of the null value isn't being retained at the AST level like it really ought to. Should fix that too.

Hi, thanks for your advice and for your library. :-)

Fixed in #193.


Some 2.5 content (text) in dark mode difficult to distinguish from background colour

Some text presented in iframes (2.5 content), in dark mode, is difficult to distinguish from the background colur.
Example 1 - Node Template

Example 2 - Node/Cluster Drivers

Related: rancher/dashboard#3713

Issue is fixed in v2.6-head (25d39aa)

But overall black theme could use redesign, for example:

random mix of grey/white/black text (Clusters -> Create -> DO RKE1)

some inputs have no border, it's hard to distinguish them from labels (Cluster Management -> Drivers)


Kindly Update

Kindly add our distro in neofetch. Thanks
Description
New linux distro Laxer OS
Features
Issues
TODO
Update

you can find more details here https://www.laxeros.com/


GENERAL QUESTION - Parallelcluster 3.1.1 AMI to ParallelCluster 3.4.1 AMI upgrade Possible ?

We are trying to move our pcluster environment to version 3.4.1 from 3.1.1.  We have a hardened 3.1.1 AMI which we took from the AWS AMI marketplace that contains all of our tools that we we would like to use with 3.4.1.  Is there an option available to update this AMI to version 3.4.1.  I am talking about the AMI not the CLI.  Any help you can provide would be appreciated.

Hi @datechnic,
you cannot reuse the existing 3.1.1 AMI. Anyway the 3.1.1 AMI has been created starting from your base AMI.
You should restart the AMI creation process starting from your base AMI, not from the 3.1.1 AMI.
Here you can find the steps to create a new ParallelCluster AMI for 3.4.1.


Platform.locale doesn't always point to the requested locale as speced.

This happens when a language pack can't be found.

To verify

start code with --locale=xx
open developer tools
var p = require('vs/base/common/platform');
ensure p.locale points to english
ensure p.language points to xx


Bump sbt-slamdata to 0.5.1 and SBT to 1.0.2

Pending slamdata/sbt-slamdata#31

@alissapajer Ready. Should be quick.


Add ability to redirect generator outptut to file

This introduces two cli parameters, log_mode and log_file. The first
gives the user the ability to choose whether to write the ouptut to
stderr, to a file or to both. In case file is selected, the log_file
parameter selects the path to write to.

I have updated the PR with a new version, with log mode "both" as default, a "znoyder_output.log" as default log file and the parameters can be passed either as a general znoyder option or as an option for the command


icons not showing

Issue in materialize: https://github.com/Dogfalo/materialize/issues/1079

Fixed in 0.8.1

What is 0.8.1 referencing?

Fixed with a workaround: https://github.com/sgasser/ember-cli-materialize/commit/82e094c23e2a3ab88cf6e60dd3dea0b0f53abfa8
Version 0.8.1 of ember-cli-materialize

This fix no longer works with current version of materialize.

@brendanoh the demo app uses the current version of materialize (0.96.1), and icons appear to be showing up. What leads you to believe that there's a problem?


Device polling misses midnight boundaries. Workaround casues error.

To get this integration to work correctly with the energy dashboard it is necessary to disable polling in the integration system options and to update the sensors manually using an automation. Otherwise the sensors do not reset exactly at midnight, creating havoc with the energy dashboard.

- id: 35371357-1c5e-41f3-9ab8-7084865d4a66
  alias: 'Poll IoTaWatt'
  trigger:
  - platform: time_pattern
    hours: "*"
    minutes: "*"
    seconds: "/30"
  action:
  - service: homeassistant.update_entity
    entity_id:
    - sensor.downstairs_hp_power
    - sensor.downstairs_hp_energy
    - sensor.export_power
    - sensor.export_energy
    - sensor.import_energy
    - sensor.import_power
    - sensor.self_solar_power
    - sensor.self_solar_energy
    - sensor.self_total_power
    - sensor.self_total_energy
    - sensor.solar_production_power
    - sensor.solar_production_energy
    - sensor.stove_power
    - sensor.stove_energy
    - sensor.upstairs_hp_power
    - sensor.upstairs_hp_energy

While this is working well it generates an error every night at midnight:
This error originated from a custom integration.

Logger: custom_components.iotawatt.coordinator
Source: helpers/update_coordinator.py:318
integration: IoTaWatt (documentation)
First occurred: 00:00:00 (1 occurrences)
Last logged: 00:00:00

Unexpected error fetching <IP_ADDRESS> data: list index out of range
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 318, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/iotawatt/coordinator.py", line 76, in _async_update_data
    await self.api.update(lastUpdate=self._last_run)
  File "/usr/local/lib/python3.12/site-packages/iotawattpy/iotawatt.py", line 76, in update
    await self._refreshSensors(timespan, lastUpdate)
  File "/usr/local/lib/python3.12/site-packages/iotawattpy/iotawatt.py", line 264, in _refreshSensors
    sensor.setValue(values[0][idx + 1])
                    ~~~~~~^^^
IndexError: list index out of range

Thanks Tomlut. I was having the same issue, although not every night. The automation works fine. Once the power sensors are polled HA calculates the energy usage,

I don't use this any more. It was causing other issues. I've gone back to using the core integration and just putting up with the outputs not being shown on the device card.

After working smoothly for a few hours I started getting an error message every minute:
"Nothing to query, update() called too soon, must wait {timespan}"
So I disabled the automation and turned polling back on in the integration. One error around midnight seems less of an issue after that. Maybe the core integration is a better solution but I will stick with this for a while.

There is always an option to use REST integration, pull json and parse.


Multi connection DB, Python (databaseRouting)

Multi connection DB, Phython (databaseRouting)

@guregini : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Merged into consolidated PR: https://github.com/MicrosoftDocs/dataexplorer-docs-pr/pull/2917


Response of issueDeviceCommand is not providing CBOR Content-Type header

🐞 Bug Report
Affected Services

 The issue is located in: command
Is this a regression?

 No
Description and Minimal Reproduction
Function issueDeviceCommand and issueDeviceCommandByNames is still applying the application/json Content-Type header when the response body is a CBOR event.

@tsconn23 We don't have use cases so far.  The purpose here is to implement the binary support in Virtual Device Service for user test, and we found out this limitation.  We can tweak the Virtual Device Service to work only with the current supported behaviors on binary data.

We can tweak the Virtual Device Service to work only with the current supported behaviors on binary data.

Reclassifying as unscoped enhancement, unassigning Akram, and dropping into icebox.

@tobiasmo1 and @lenny-intel do you have any requirement from you side to access binary data through Core Command?  It can work well only with AutoEvent or async reading now.

I will defer to @lenny-intel on the priority for resolving requirements and just provide a couple thoughts below.
A device service that uses AutoEvent to send/push binary data can be paired with a listening application service to store/cache a recent snapshot of binary payloads. This would resolve many use cases; where the snapshot data can be reasonably stale.
The value of direct Core Command support comes into play when we need to handle event fusion, such as when sensors emit events that should trigger a command to pull nearly immediate binary data (such as an image snapshot from camera device in response to motion). This activity would likely be initiated by Rules Engine, so I suspect it may be more relevant/prioritized alongside other Rules Engine features.
-------- Original message --------
From: Cloud Tsai<EMAIL_ADDRESS>Date: 2/2/20 10:18 PM (GMT-08:00)
To: edgexfoundry/edgex-go<EMAIL_ADDRESS>Cc: "Mosby, Tobias"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [edgexfoundry/edgex-go] Response of issueDeviceCommand is not providing CBOR Content-Type header (#2272)
@tobiasmo1https://github.com/tobiasmo1 and @lenny-intelhttps://github.com/lenny-intel do you have any requirement from you side to access binary data through Core Command? It can work well only with AutoEvent or async reading now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/edgexfoundry/edgex-go/issues/2272?email_source=notifications&email_token=AEAJEVJ5K2J4UN2VIXBI7LTRA6ZJPA5CNFSM4KFC3UM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKSUIWA#issuecomment-581256280, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEAJEVI52MCAUPDGTSVH3U3RA6ZJPANCNFSM4KFC3UMQ.

I've always viewed the command channel as a mechanism to actuate a device or provide an asynchronous prompt to a device service for it to take an action and return the relevant data via the normal manner (i.e. via core-data).
I may be misinterpreting; it sounds like you want to obtain data from a device service as a direct reply to a command request sent via core-command.  If this is the case, this would effectively create a new data path within the system.
Given the design and intent of the system in general and core-command specifically, I'd be interested in @jpwhitemn's take on whether or not this is desirable.

The value of direct Core Command support comes into play when we need to handle event fusion, such as when sensors emit events that should trigger a command to pull nearly immediate binary data (such as an image snapshot from camera device in response to motion). This activity would likely be initiated by Rules Engine, so I suspect it may be more relevant/prioritized alongside other Rules Engine features.

@tobiasmo1 how would this work?  In the scenario you describe, the rules engine -- based on a trigger -- would initiate a specific command to a specific device service to obtain some binary data.  What would the rules engine to do with that binary data?

A simple use case in my mind is that when a motion sensor detects something, Get commands would be invoked to retrieve videos or snapshots from the cameras in a specific area.

A simple use case in my mind is that when a motion sensor detects something, Get commands would be invoked to retrieve videos or snapshots from the cameras in a specific area.

Why wouldn't the video/snapshot data be forwarded into core-data by the device service as usual?

A simple use case in my mind is that when a motion sensor detects something, Get commands would be invoked to retrieve videos or snapshots from the cameras in a specific area.

Why wouldn't the video/snapshot data be forwarded into core-data by the device service as usual?

Since the binary data is large, users might not want to collect it constantly.  Through rules engine and get command, users could retrieve the binary data when it is necessary.
@SteveOss @andyf1967 @iain-anderson could you please share your opinions or use cases you know?
Thanks for the effort, @michaelestrin @akramtexas @tsconn23 , we will implement the binary support in virtual device service with the current implementation first anyway.

Since the binary data is large, users might not want to collect it constantly. Through rules engine and get command, users could retrieve the binary data when it is necessary.

I don't think I'm communicating clearly.
In your scenario, it could be the data is sent only when the rules engine triggers the command to instruct the device service to gather and send it.  There's nothing about the existing data path that requires data to be sent constantly.
Assuming the rules engine -- based on a trigger -- initiated a specific command to a specific device service to obtain some binary data in-band, what would the rules engine to do with that binary data?
I'm still not clear on the value of creating a separate path (via core-command or otherwise) to receive and process data from device services.

Why wouldn't the video/snapshot data be forwarded into core-data by the device service as usual?

I got your point now.
My understanding was that the usual way to send binary data to core-data is to use AutoEvent, and it will constantly send data to core-data.
It can work by ignoring the response received by the trigger.

@SteveOss @andyf1967 @iain-anderson could you please share your opinions or use cases you know?

One suggestion that has been floated before is to allow control of the destinations for event data on a per-request basis by use of query parameters.
So the normal operation of the device service is to generate an event and post it to core-data, and to return the same event as the result of the http request (the latter then being passed-through by core-command). But either of these paths could be disabled, by appending something like ?ds-post-event=no or ?ds-return-event=no to your URL.
But this seems orthogonal to the issue here, which as I read it is that in the case of CBOR data the return path is being corrupted by using a wrong Content-Type

But this seems orthogonal to the issue here, which as I read it is that in the case of CBOR data the return path is being corrupted by using a wrong Content-Type

I concur -- orthogonal.

the normal operation of the device service is to generate an event and post it to core-data, and to return the same event as the result of the http request (the latter then being passed-through by core-command)

With this additional clarity, it seems as if the initial CBOR implementation missed the real possibility of binary data being included in a command response.  It sounds like this needs to be addressed.  In your opinion (@jpwhitemn @iain-anderson ), is this a forward-facing change (i.e. in master only) or something we should fix in prior releases?

“Why wouldn't the video/snapshot data be forwarded into core-data by the device service as usual?
If there is no application subscribed to receive the data. I suspect most workflows will AutoEvent or manually trigger an event using a command. But this leaves the third flow we discussed and implemented; legacy command/response behavior that conforms to usual device service behavior for non-binary payloads.
Assuming EdgeX will continue to support command/response for device services (to query and/or actuate a device), it is consistent to facilitate binary/CBOR data alongside other readings (numeric, strings, json, etc.). I suppose there are alternatives to routing the information back to the caller (e.g., using correlation ID, etc.), even to RESTful services that call a device service to “get” a response.
I filed an issue during initial CBOR implementation that the command handling was “overloaded”. (ref: https://github.com/edgexfoundry/device-sdk-go/issues/240). I also reported that Core Command wasn’t reflecting this Content Type header in the response; I don’t find a reference yet. Trevor may recall, I believe we decided to consider supporting this via Accept header.
Toby
From: Cloud Tsai<EMAIL_ADDRESS>Sent: Monday, February 3, 2020 11:43 PM
To: edgexfoundry/edgex-go<EMAIL_ADDRESS>Cc: Mosby, Tobias<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [edgexfoundry/edgex-go] Response of issueDeviceCommand is not providing CBOR Content-Type header (#2272)
A simple use case in my mind is that when a motion sensor detects something, Get commands would be invoked to retrieve videos or snapshots from the cameras in a specific area.
Why wouldn't the video/snapshot data be forwarded into core-data by the device service as usual?
Since the binary data is large, users might not want to collect it constantly. Through rules engine and get command, users could retrieve the binary data when it is necessary.
@SteveOsshttps://github.com/SteveOss @andyf1967https://github.com/andyf1967 @iain-andersonhttps://github.com/iain-anderson could you please share your opinions or use cases you know?
Thanks for the effort, @michaelestrinhttps://github.com/michaelestrin @akramtexashttps://github.com/akramtexas @tsconn23https://github.com/tsconn23 , we will implement the binary support in virtual device service with the current implementation first anyway.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/edgexfoundry/edgex-go/issues/2272?email_source=notifications&email_token=AEAJEVKJSRGFJZ7HDG4YXKLRBEMBZA5CNFSM4KFC3UM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKWUTIQ#issuecomment-581781922, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEAJEVNPDH5NRJVM5HBUQ3TRBEMBZANCNFSM4KFC3UMQ.

Discussed in February 13th Core WG meeting; community decided to move ahead with correcting this in Geneva release.  Re-categorized and assigned @akramtexas.

Discussed in February 13th Core WG meeting; community decided to move ahead with correcting this in Geneva release. Re-categorized and assigned @akramtexas.
@tsconn23

@michaelestrin @tsconn23 I will work this for the Geneva release 👍

Following updates to restDevice.go (i.e. edgex-go/internal/core/command/restDevice.go) on a feature branch (WIP and for which a PR will be prepared and submitted), and for which unit testing has been created, a CBOR result is now handed back as bytes, and the appropriate content-type is sent to the caller as well. This complements the already-existing capability for handling a JSON result.
As for functional testing, I created another CBOR payload (much smaller than the one previously used, which was blowing the golang runtime stack, and for which an issue has been created).
Used this payload for the PUT command for core-command. Also tested with the GET commands for core-command. Using GoLand debugger, I traced through the command.go code (in device-sdk-go/internal/handler/) as well as the restfuncs.go code (in device-sdk-go/internal/controller/)
The need has been identified to update the following function in device-sdk-go, which is currently hard-coded to handle JSON only, and needs to have support added for handling CBOR as well:

func parseParams(params string) (paramMap map[string]string, err error) { ... }

However, for such an updated, we would also need to propagate the content type (JSON or CBOR) from the request header through a deep nesting of function calls:

github.com/edgexfoundry/device-sdk-go/internal/handler.parseParams at command.go:408
github.com/edgexfoundry/device-sdk-go/internal/handler.parseWriteParams at command.go:356
github.com/edgexfoundry/device-sdk-go/internal/handler.execWriteCmd at command.go:308
github.com/edgexfoundry/device-sdk-go/internal/handler.CommandHandler at command.go:87
github.com/edgexfoundry/device-sdk-go/internal/controller.commandFunc at restfuncs.go:108
net/http.HandlerFunc.ServeHTTP at server.go:2007

And which can be seen initiating with the call to the core-command function at the bottom of the call hierarchy below:

paramMap, err := parseParams(params)
in: func parseParams(params string) (paramMap map[string]string, err error) {

cvs, err := parseWriteParams(device.Profile.Name, ros, params)
in: func execWriteCmd(device *contract.Device, cmd string, params string) common.AppError {

appErr := execWriteCmd(&d, cmd, body)
in: func CommandHandler(vars map[string]string, body string, method string, queryParams string) (*dsModels.Event, common.AppError) {

event, appErr := handler.CommandHandler(vars, body, req.Method, req.URL.RawQuery)

func commandFunc(w http.ResponseWriter, req *http.Request) {

c.addReservedRoute(common.APIIdCommandRoute, commandFunc).Methods(http.MethodGet, http.MethodPut)
c.addReservedRoute(common.APINameCommandRoute, commandFunc).Methods(http.MethodGet, http.MethodPut)

After examining the edgex-go code-base, I see that a cleaner approach (which would avoid us having to propagate the content type from the request header through a deep nesting of function calls) could use (for core-command) the following function or something very similar, defined in edgex-go/internal/core/data/io.go:

// NewCborReader creates a new instance of cborReader.
func NewCborReader(configuration *config.ConfigurationStruct) cborReader {
  return cborReader{configuration: configuration}
}

// NewJsonReader creates a new instance of cborReader.
func NewJsonReader() jsonReader {
  return jsonReader{}
}

And which is used in the following switch statement, again in edgex-go/internal/core/data/io.go:

// NewRequestReader returns a BodyReader capable of processing the request body
func NewRequestReader(request *http.Request, configuration *config.ConfigurationStruct) EventReader {
  contentType := request.Header.Get(clients.ContentType)

  switch strings.ToLower(contentType) {
  case clients.ContentTypeCBOR:
    return NewCborReader(configuration)
  default:
    return NewJsonReader()
  }
}

And invoked in edgex-go/internal/core/data/router.go:
reader := NewRequestReader(r, configuration)

Should we split out handling CBOR for write commands (enhancement) from this issue of missing content-type in result of read command (bug)


ChestShop 1.12?

Is chestshop going to be compatible with 1.12? For now it has an instantcrash of the server xD

Which version are you using?
The latest version (1.11.1) is not causing the server to crash for me, but it does not support item names from 1.12. If you are using a developer build from here, this plugin should work stable on 1.12. The next official update of ShopChest will be released very soon after the official release of Minecraft 1.12.

Oh weird. using the # 11 build.

Oh wait..... using the wrong issue tracker o_O
my plugin is chestshop and not shopchest xD

Was about to say that ✌


Build locally with Hunter fork

I'm attempting to build using only local packages. I've cloned hunter and modified the hunter.cmake for all the projects I'm using. I want to use a relative directory in the URL strings. I attempted to use both CMAKE_SOURCE_DIR, HUNTER_ROOT, and my own variable.
However, they all break down when adding recursive dependencies. For example, myRepo depends on package1 (works fine) but when package1 depends on package2, these variables are no longer set correctly. Is there any variable I could use that is set consistently?
I see two options, if the above doesn't work.

Call hunter_add_package() on the lowest dependencies first.
Use an environment variable.

Thoughts on getting around this issue?

I attempted to use both CMAKE_SOURCE_DIR, HUNTER_ROOT, and my own variable.

It is not designed to be used this way. Full path in URL or using environment variable will do the trick. Just for your info feature request:

https://github.com/ruslo/hunter/issues/521

Closing inactive discussion.


rubyのバージョンを2.7にあげる

https://github.com/voyagegroup/ingred-ui/runs/4545032051?check_suite_focus=true

ERROR:  Error installing github_changelog_generator:
	The last version of activesupport (>= 0) to support your Ruby & RubyGems was <IP_ADDRESS>. Try installing it with `gem install activesupport -v <IP_ADDRESS>` and then running the current command again
	activesupport requires Ruby version >= 2.7.0. The current ruby version is <IP_ADDRESS>.

ingred-ui  🍣 fix-release-workflow via  on ☁
🕙 13:31:16 ❯ruby -v
ruby 2.6.9p207 (2021-11-24 revision 67954) [x86_64-darwin21]

ruby 2.6.9で実行すると
ingred-ui  🍣 fix-release-workflow via  on ☁
🕙 13:31:19 ❯gem install github_changelog_generator
Fetching fiber-local-1.0.0.gem
Fetching concurrent-ruby-1.1.9.gem
Fetching activesupport-7.0.0.gem
Fetching timers-4.3.3.gem
Fetching i18n-1.8.11.gem
Fetching console-1.14.0.gem
Fetching tzinfo-2.0.4.gem
Fetching nio4r-2.5.8.gem
Fetching protocol-hpack-1.4.2.gem
Fetching protocol-http2-0.14.2.gem
Fetching async-1.30.1.gem
Fetching async-io-1.32.2.gem
Fetching async-pool-0.3.9.gem
Fetching protocol-http-0.22.5.gem
Fetching protocol-http1-0.14.2.gem
Fetching async-http-0.56.5.gem
Fetching faraday-em_http-1.0.0.gem
Fetching faraday-em_synchrony-1.0.0.gem
Fetching faraday-excon-1.1.0.gem
Fetching faraday-httpclient-1.0.1.gem
Fetching faraday-net_http-1.0.1.gem
Fetching faraday-net_http_persistent-1.2.0.gem
Fetching faraday-patron-1.0.0.gem
Fetching multipart-post-2.1.1.gem
Fetching faraday-rack-1.0.0.gem
Fetching faraday-http-cache-2.2.0.gem
Fetching multi_json-1.15.0.gem
Fetching public_suffix-4.0.6.gem
Fetching ruby2_keywords-0.0.5.gem
Fetching sawyer-0.8.2.gem
Fetching faraday-1.8.0.gem
Fetching async-http-faraday-0.11.0.gem
Fetching rainbow-3.0.0.gem
Fetching github_changelog_generator-1.16.4.gem
Fetching addressable-2.8.0.gem
Fetching octokit-4.21.0.gem
Successfully installed concurrent-ruby-1.1.9
Successfully installed i18n-1.8.11
Successfully installed tzinfo-2.0.4
ERROR:  Error installing github_changelog_generator:
	The last version of activesupport (>= 0) to support your Ruby & RubyGems was <IP_ADDRESS>. Try installing it with `gem install activesupport -v <IP_ADDRESS>` and then running the current command again
	activesupport requires Ruby version >= 2.7.0. The current ruby version is <IP_ADDRESS>.

再現

ingred-ui  🍣 fix-release-workflow via  on ☁
🕙 13:44:31 ❯ruby -v
ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-darwin21]

2.7.5で実行すると
ingred-ui  🍣 fix-release-workflow via  on ☁
🕙 13:44:33 ❯gem install github_changelog_generator
Fetching tzinfo-2.0.4.gem
Fetching activesupport-7.0.0.gem
Fetching console-1.14.0.gem
Fetching concurrent-ruby-1.1.9.gem
Fetching i18n-1.8.11.gem
Fetching fiber-local-1.0.0.gem
Fetching timers-4.3.3.gem
Fetching nio4r-2.5.8.gem
Fetching async-1.30.1.gem
Fetching async-io-1.32.2.gem
Fetching async-pool-0.3.9.gem
Fetching protocol-http-0.22.5.gem
Fetching protocol-http1-0.14.2.gem
Fetching protocol-hpack-1.4.2.gem
Fetching protocol-http2-0.14.2.gem
Fetching async-http-0.56.5.gem
Fetching faraday-em_http-1.0.0.gem
Fetching faraday-em_synchrony-1.0.0.gem
Fetching faraday-excon-1.1.0.gem
Fetching faraday-httpclient-1.0.1.gem
Fetching faraday-net_http-1.0.1.gem
Fetching faraday-net_http_persistent-1.2.0.gem
Fetching faraday-patron-1.0.0.gem
Fetching faraday-rack-1.0.0.gem
Fetching multipart-post-2.1.1.gem
Fetching ruby2_keywords-0.0.5.gem
Fetching faraday-1.8.0.gem
Fetching async-http-faraday-0.11.0.gem
Fetching faraday-http-cache-2.2.0.gem
Fetching multi_json-1.15.0.gem
Fetching public_suffix-4.0.6.gem
Fetching addressable-2.8.0.gem
Fetching sawyer-0.8.2.gem
Fetching octokit-4.21.0.gem
Fetching rainbow-3.0.0.gem
Fetching github_changelog_generator-1.16.4.gem
Successfully installed concurrent-ruby-1.1.9
Successfully installed i18n-1.8.11
Successfully installed tzinfo-2.0.4
Successfully installed activesupport-7.0.0
Successfully installed fiber-local-1.0.0
Successfully installed console-1.14.0
Building native extensions. This could take a while...
Successfully installed nio4r-2.5.8
Successfully installed timers-4.3.3
Successfully installed async-1.30.1
Successfully installed async-io-1.32.2
Successfully installed async-pool-0.3.9
Successfully installed protocol-http-0.22.5
Successfully installed protocol-http1-0.14.2
Successfully installed protocol-hpack-1.4.2
Successfully installed protocol-http2-0.14.2
Successfully installed async-http-0.56.5
Successfully installed faraday-em_http-1.0.0
Successfully installed faraday-em_synchrony-1.0.0
Successfully installed faraday-excon-1.1.0
Successfully installed faraday-httpclient-1.0.1
Successfully installed faraday-net_http-1.0.1
Successfully installed faraday-net_http_persistent-1.2.0
Successfully installed faraday-patron-1.0.0
Successfully installed faraday-rack-1.0.0
Successfully installed multipart-post-2.1.1
Successfully installed ruby2_keywords-0.0.5
Successfully installed faraday-1.8.0
Successfully installed async-http-faraday-0.11.0
Successfully installed faraday-http-cache-2.2.0
Successfully installed multi_json-1.15.0
Successfully installed public_suffix-4.0.6
Successfully installed addressable-2.8.0
Successfully installed sawyer-0.8.2
Successfully installed octokit-4.21.0
Successfully installed rainbow-3.0.0
Successfully installed github_changelog_generator-1.16.4
Parsing documentation for concurrent-ruby-1.1.9
Installing ri documentation for concurrent-ruby-1.1.9
Parsing documentation for i18n-1.8.11
Installing ri documentation for i18n-1.8.11
Parsing documentation for tzinfo-2.0.4
Installing ri documentation for tzinfo-2.0.4
Parsing documentation for activesupport-7.0.0
Installing ri documentation for activesupport-7.0.0
Parsing documentation for fiber-local-1.0.0
Installing ri documentation for fiber-local-1.0.0
Parsing documentation for console-1.14.0
Installing ri documentation for console-1.14.0
Parsing documentation for nio4r-2.5.8
Installing ri documentation for nio4r-2.5.8
Parsing documentation for timers-4.3.3
Installing ri documentation for timers-4.3.3
Parsing documentation for async-1.30.1
Installing ri documentation for async-1.30.1
Parsing documentation for async-io-1.32.2
Installing ri documentation for async-io-1.32.2
Parsing documentation for async-pool-0.3.9
Installing ri documentation for async-pool-0.3.9
Parsing documentation for protocol-http-0.22.5
Installing ri documentation for protocol-http-0.22.5
Parsing documentation for protocol-http1-0.14.2
Installing ri documentation for protocol-http1-0.14.2
Parsing documentation for protocol-hpack-1.4.2
Installing ri documentation for protocol-hpack-1.4.2
Parsing documentation for protocol-http2-0.14.2
Installing ri documentation for protocol-http2-0.14.2
Parsing documentation for async-http-0.56.5
Installing ri documentation for async-http-0.56.5
Parsing documentation for faraday-em_http-1.0.0
Installing ri documentation for faraday-em_http-1.0.0
Parsing documentation for faraday-em_synchrony-1.0.0
Installing ri documentation for faraday-em_synchrony-1.0.0
Parsing documentation for faraday-excon-1.1.0
Installing ri documentation for faraday-excon-1.1.0
Parsing documentation for faraday-httpclient-1.0.1
Installing ri documentation for faraday-httpclient-1.0.1
Parsing documentation for faraday-net_http-1.0.1
Installing ri documentation for faraday-net_http-1.0.1
Parsing documentation for faraday-net_http_persistent-1.2.0
Installing ri documentation for faraday-net_http_persistent-1.2.0
Parsing documentation for faraday-patron-1.0.0
Installing ri documentation for faraday-patron-1.0.0
Parsing documentation for faraday-rack-1.0.0
Installing ri documentation for faraday-rack-1.0.0
Parsing documentation for multipart-post-2.1.1
Installing ri documentation for multipart-post-2.1.1
Parsing documentation for ruby2_keywords-0.0.5
Installing ri documentation for ruby2_keywords-0.0.5
Parsing documentation for faraday-1.8.0
Installing ri documentation for faraday-1.8.0
Parsing documentation for async-http-faraday-0.11.0
Installing ri documentation for async-http-faraday-0.11.0
Parsing documentation for faraday-http-cache-2.2.0
Installing ri documentation for faraday-http-cache-2.2.0
Parsing documentation for multi_json-1.15.0
Installing ri documentation for multi_json-1.15.0
Parsing documentation for public_suffix-4.0.6
Installing ri documentation for public_suffix-4.0.6
Parsing documentation for addressable-2.8.0
Installing ri documentation for addressable-2.8.0
Parsing documentation for sawyer-0.8.2
Installing ri documentation for sawyer-0.8.2
Parsing documentation for octokit-4.21.0
Installing ri documentation for octokit-4.21.0
Parsing documentation for rainbow-3.0.0
Installing ri documentation for rainbow-3.0.0
Parsing documentation for github_changelog_generator-1.16.4
Installing ri documentation for github_changelog_generator-1.16.4
Done installing documentation for concurrent-ruby, i18n, tzinfo, activesupport, fiber-local, console, nio4r, timers, async, async-io, async-pool, protocol-http, protocol-http1, protocol-hpack, protocol-http2, async-http, faraday-em_http, faraday-em_synchrony, faraday-excon, faraday-httpclient, faraday-net_http, faraday-net_http_persistent, faraday-patron, faraday-rack, multipart-post, ruby2_keywords, faraday, async-http-faraday, faraday-http-cache, multi_json, public_suffix, addressable, sawyer, octokit, rainbow, github_changelog_generator after 16 seconds
36 gems installed

無事インストールできた


feat: add direct url repodata building

Implements:

[x] Creating "virtual" repodata from a single package file
[x] Makes the matchspec parsing invalid if the url is not a conda archive style name. e.g. foo-1.2.3-bsle9f2_0.conda
[x] Matches a matchspec on: Matchspec::url == PackageRecord::direct_url
[x] Adds a "fake" entry in the PackageRecord for a direct_url to keep track in the record that it came from a direct url and which one.

Future improvements:

We now fetch the required package to the cache and then read the index.json from there. We could possible stream the package in and only get what we need before we do the solve.
It would be great to support "any" name package file. e.g. /home/user/pacakge/test.bla and read the info from it as part of the matchspec generation.
We don't have all information in the package record from the index.json, issue: #742

This doesn't build ontop of main yet. Let me fix that later

Added a test to see if there is only one direct url and that it is located in the first subdir: https://github.com/mamba-org/rattler/pull/725/commits/4cc3c508fd47f3c7b34bd67be83571e3f1cab89


Video Message bug

When I send a video message 5~7 MB to multicable  recipients. I can send few messages then FrmConsole disconnected and I get an error (Service Server is not Connected)

In the current version I did not identify the problem, if you send videos, for many simultaneous contacts use the option to send a link to a video published on YouTube or forward a video already sent


Create no nonsense complete system demo runner

Done as of https://github.com/nearform/vidi-concorda-nodezoo-system


[question] Is it normal to recreate a controller for each build?

I have some widgets that should not be displayed in full screen mode of the application, so I have to recreate the controller on each build. Is it normal to do this and will this behavior be supported in the future?

I hadn't thought of this use-case; I'll look into a better solution!

Hi @ivanmem, I am releasing a beta version that addresses your concern by moving the ResizableChild items back into the ResizableController. Are you interested in testing things out before I make a full release?

@andyhorn thanks, that's what I need. Only the controller seems like it should be optional, as its functionality is not always needed.


[popover] suffix style units with px expclitly

Otherwise it simpy doesn't work

Codecov Report

Merging #264 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #264   +/-   ##
=======================================
  Coverage   95.86%   95.86%
=======================================
  Files          70       70
  Lines        1499     1499
  Branches      222      222
=======================================
  Hits         1437     1437
  Misses         62       62

Impacted Files
Coverage Δ

src/components/Popover.vue
96.55% <100%> (ø)
:arrow_up:

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 e2c15c6...273ea0e. Read the comment docs.


Dev branch opened again

I merge both pull request into a new dev-branch. I would suggest to create a new branch for a new feature or edit and merge the new code into the dev branch.

Since active development stopped, this is no longer needed.


Specify the target os/arch for build and deploy

/kind feature
Which functionality do you think we should add?
When building and deploying images with odo there should be a way to specify the target os/arch similar to the --platform option for podman build.
Why is this needed?
It should be possible to build and deploy from arm64 local systems (like Mac M1) to Kubernetes clusters that do not have the corresponding arch.

Grooming call (2022-10-06)

Also applicable to odo dev
Best option to add a flag
Should be handled the same way as #6200 (related to #6185)

/close
Duplicate of #6421
Feel free to reopen if you think otherwise.


Task11,Task12,Task13,Task14,Task15,Task20,Task21

{
"Flowchart Switch.xaml":  [
{
"Activity Input Dialog has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Excel.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Log Message not used in workflow Main.":  "Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Excel.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Log Message not used in workflow Main.":  "Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause. "
},
{
"Variable variable1 is not used.":  "Remove variables that are not used. "
},
{
"The sequence Main Sequence is redundant.":  "Redundant sequences should not be used, since they only make the workflow cluttered. For removing redundant sequences, use the Remove Surrounding Sequence option of the Context Menu in UiPath Studio. "
},
{
"Assign display name is defined many times. Current allowed threshold is 1. Code contains 4.":  "Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. "
},
{
"Activity Assign has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Assign has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity For Each has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Assign has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity If has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Assign has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Message Box has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Log Message not used in workflow Main.":  "Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause. "
},
{
"Variable StrData doesn\u0027t have DataTable prefix.":  "DataTable Variable should start with a dt_ prefix. "
},
{
"Variable StrData2 doesn\u0027t have DataTable prefix.":  "DataTable Variable should start with a dt_ prefix. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Variable LowerDatatable doesn\u0027t have DataTable prefix.":  "DataTable Variable should start with a dt_ prefix. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Variable DataTable doesn\u0027t have DataTable prefix.":  "DataTable Variable should start with a dt_ prefix. "
},
{
"Activity For Each Row in Data Table has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Log Message has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
],
"Main.xaml":  [
{
"Log Message not used in workflow Main.":  "Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause. "
},
{
"Variable ResultDataTable doesn\u0027t have DataTable prefix.":  "DataTable Variable should start with a dt_ prefix. "
},
{
"Activity For Each Row in Data Table has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
},
{
"Activity Assign has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
]
}

@ramkumar566
Task -11
Code verified. Default activity names

Task -12
Code verified. Default activity names

Task -13
Code verified.
Task -14
Code verified.
Task -15
Code verified. Default activity name

Task -20
Code verified.
Task -21
Code verified.


#include error

I built the f2c dynamic library successfully and install the lib, and then I would like to integrate it into my project like this #include<fields2cover.h>. However,when I catkin_make my project,error occur:
/usr/local/include/fields2cover.h:11:10: fatal error: fields2cover/types.h: No such file or directory
11 | #include "fields2cover/types.h"
|          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
I am puzzled what's wrong.

different version f2c head and lib directory conflict.Only keeping one works.


docs: Modifying Readme file

Contribution description
This is a PR to update the README, document
fix #38

I've been modifying the document, this is aesthethic model that I built it. Take a look and tell me what you think about?

What do you think about the following header style?

M4a Firmware

M4a Firmware

Well recently. I added the changes suggested, if you can see another detail, please make me know.


Implement base SnowflakeClient

Based on PR from @peytonrunyan https://github.com/fugue-project/fugue-warehouses/pull/7

It looks good in general. Let's merge this to unblock the next step (dataframe and engine implementation)


Request for Next.js.13 (App) router + Prisma documentation

Discussed in https://github.com/prisma/prisma/discussions/20762

Originally posted by GavinSalcedo August 21, 2023
Question
Is there an existing documentation for Next.js using the app directory integrating Prisma?
I understand this should be straightforward for Next.js developers to understand and migrate from pages to app, however, I think it would also benefit other developers if given more reference.
App router is becoming more stable and evidently effective than pages, so I would like to request to update the Prisma website documentation.
Thanks for the considering this post.
reference: https://www.prisma.io/docs/concepts/overview/prisma-in-your-stack/fullstack
How to reproduce (optional)
Click on this link to access the existing documentation

https://www.prisma.io/docs/concepts/overview/prisma-in-your-stack/fullstack

No response
Expected behavior (optional)
No response
Information about Prisma Schema, Client Queries and Environment (optional)
No response
### Tasks

Hello
I have a working Next app router with Prisma: https://github.com/carvalhochris/pure-ts

Hello
I have a working Next app router with Prisma: https://github.com/carvalhochris/pure-ts

I think the problem starts when you have to use common scenarios like add, delete, or fetch conditional data by clicking a button. The only way is to create API (route.ts) in the app folder and call them on the client side

👋 Hi there,
We’re taking some time to organize our backlog and focus on the most relevant and impactful issues. As part of this effort, we’re closing some issues that haven’t seen much recent activity or don’t align with our current focus.
We do have an example of using Prisma with Next.js App Router, which you can check out here. While this example uses Prisma Accelerate with Prisma ORM, you can easily use just Prisma ORM in the same way.
 We truly value your feedback and are always here to help ensure our docs continue to improve.
Thank you for your understanding and for being part of our community!


Partial fix for ENYO-2796

We need to ensure that containers that are ancestors of the previous spotted control are not receiving the onSpotlightContainerLeave event when it isn't actually being exited.
Enyo-DCO-1.1-Signed-Off-By: Cole Davis<EMAIL_ADDRESS>

This has been included in a different branch (https://github.com/enyojs/spotlight/pull/229).


Traefik do not get frontend/backend from traefik.toml

What version of Traefik are you using (traefik version)?
Morbier
What is your environment & configuration (arguments, toml...)?
docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik
traefik.toml
################################################################
# Global configuration
################################################################
defaultEntryPoints = ["http"]
[entryPoints]
  [entryPoints.http]
  address = ":80"
################################################################
# Web configuration backend
################################################################
# Enable web configuration backend
# Optional
	[web]
# Web administration port
# Required
	address = "8080"
################################################################
# File configuration backend
################################################################
# Enable file configuration backend
# Optional
	[file]
	filename = "servers.toml"

# Enable watch file changes
	watch = true

servers.toml
[backends]
## Traefik WebUI
[backends.traefik]
        [backends.traefik.servers.server1]
            url = "http://<IP_ADDRESS>:8080"
## Router
[backends.router]
        [backends.router.servers.server1]
            url = "http://<IP_ADDRESS>"
## Plex
[backends.plex]
        [backends.plex.servers.server1]
            url = "http://<IP_ADDRESS>:32400"
## External sites
[backends.pastebin]
        [backends.pastebin.servers.server1]
            url = "http://www.google.com"

[frontends]
## Traefik WebUI
[frontends.traefik]
    backend = "traefik"
    entrypoints = ["http"]
        [frontends.traefik.routes.traefik_1]
        rule = "Host:traefik.mydomain.com"
## Router
    [frontends.router]
    backend = "router"
    entrypoints = ["http"]
        [frontends.router.routes.router_1]
        rule = "Host:router.mydomain.com"
## Plex
[frontends.plex]
    backend = "plex"
    entrypoints = ["http"]
        [frontends.plex.routes.plex_1]
        rule = "Host:plex.mydomain.com"
## External sites
[frontends.pastebin]
    backend = "pastebin"
    entrypoints = ["http"]
        [frontends.pastebin.routes.pastebin_1]
        rule = "Host:pastebin.mydomain.com"

What did you do?
What did you expect to see?
To access to the backends using the rules/
What did you see instead?
404 page
If applicable, please paste the log output in debug mode (--debug switch)
How to setup the log?

Are you sure that the servers.toml file can be loaded by traefik? It looks like you are not mounting the file into the docker container. Re the debug log, you can also set logLevel = "DEBUG" in the traefik.toml.

sorry,where do I find the debug file?
thanks

debug:time="2017-05-07T13:17:24Z" level=info msg="Traefik version v1.2.3 built on 2017-04-13_07:21:10PM"
time="2017-05-07T13:17:24Z" level=info msg="Using TOML configuration file /var/traefik/traefik.toml"
time="2017-05-07T13:17:24Z" level=debug msg="Global configuration loaded {"GraceTimeOut":10,"Debug":false,"CheckNewVersion":true,"AccessLogsFile":"","TraefikLogsFile":"","LogLevel":"DEBUG","EntryPoints":{"http":{"Network":"","Address":":80","TLS":null,"Redirect":null,"Auth":null,"Compress":false}},"Cluster":null,"Constraints":[],"ACME":null,"DefaultEntryPoints":["http"],"ProvidersThrottleDuration":2000000000,"MaxIdleConnsPerHost":200,"InsecureSkipVerify":false,"Retry":null,"Docker":{"Watch":true,"Filename":"","Constraints":null,"Endpoint":"unix:///var/run/docker.sock","Domain":"fr.to","TLS":null,"ExposedByDefault":true,"UseBindPortIP":false,"SwarmMode":false},"File":{"Watch":true,"Filename":"servers.toml","Constraints":null},"Web":{"Address":":8080","CertFile":"","KeyFile":"","ReadOnly":false,"Statistics":null,"Metrics":null,"Auth":null},"Marathon":null,"Consul":null,"ConsulCatalog":null,"Etcd":null,"Zookeeper":null,"Boltdb":null,"Kubernetes":null,"Mesos":null,"Eureka":null,"ECS":null,"Rancher":null}"
time="2017-05-07T13:17:24Z" level=info msg="Preparing server http &{Network: Address::80 TLS: Redirect: Auth: Compress:false}"
time="2017-05-07T13:17:24Z" level=info msg="Starting provider *provider.Docker {"Watch":true,"Filename":"","Constraints":null,"Endpoint":"unix:///var/run/docker.sock","Domain":"fr.to","TLS":null,"ExposedByDefault":true,"UseBindPortIP":false,"SwarmMode":false}"
time="2017-05-07T13:17:24Z" level=info msg="Starting provider *provider.File {"Watch":true,"Filename":"servers.toml","Constraints":null}"
time="2017-05-07T13:17:24Z" level=info msg="Starting provider *main.WebProvider {"Address":":8080","CertFile":"","KeyFile":"","ReadOnly":false,"Statistics":null,"Metrics":null,"Auth":null}"
time="2017-05-07T13:17:24Z" level=info msg="Starting server on :80"
time="2017-05-07T13:17:24Z" level=error msg="Error opening fileopen servers.toml: no such file or directory"
time="2017-05-07T13:17:24Z" level=error msg="Error starting provider open servers.toml: no such file or directory"
time="2017-05-07T13:17:24Z" level=debug msg="Docker connection established with docker 17.03.1-ce (API 1.27)"
time="2017-05-07T13:17:24Z" level=debug msg="Load balancer method '' for backend backend-portainer-app: Invalid method, using default. Using default wrr."
time="2017-05-07T13:17:24Z" level=debug msg="Load balancer method '' for backend backend-traefik-proxy-1: Invalid method, using default. Using default wrr."
time="2017-05-07T13:17:24Z" level=debug msg="Configuration received from provider docker: {"backends":{"backend-portainer-app":{"servers":{"server-portainer-app":{"url":"http://<IP_ADDRESS>:9000","weight":0}},"loadBalancer":{"method":"wrr"}},"backend-traefik-proxy-1":{"servers":{"server-traefik_proxy_1":{"url":"http://<IP_ADDRESS>:80","weight":0}},"loadBalancer":{"method":"wrr"}}},"frontends":{"frontend-Host-portainer-app-fr-to":{"entryPoints":["http"],"backend":"backend-portainer-app","routes":{"route-frontend-Host-portainer-app-fr-to":{"rule":"Host:portainer-app.fr.to"}},"passHostHeader":true,"priority":0},"frontend-Host-traefik-proxy-1-fr-to":{"entryPoints":["http"],"backend":"backend-traefik-proxy-1","routes":{"route-frontend-Host-traefik-proxy-1-fr-to":{"rule":"Host:traefik-proxy-1.fr.to"}},"passHostHeader":true,"priority":0}}}"
time="2017-05-07T13:17:24Z" level=debug msg="Last docker config received more than 2s, OK"
time="2017-05-07T13:17:24Z" level=debug msg="Creating frontend frontend-Host-portainer-app-fr-to"
time="2017-05-07T13:17:24Z" level=debug msg="Wiring frontend frontend-Host-portainer-app-fr-to to entryPoint http"
time="2017-05-07T13:17:24Z" level=debug msg="Creating route route-frontend-Host-portainer-app-fr-to Host:portainer-app.fr.to"
time="2017-05-07T13:17:24Z" level=debug msg="Creating backend backend-portainer-app"
time="2017-05-07T13:17:24Z" level=debug msg="Creating load-balancer wrr"
time="2017-05-07T13:17:24Z" level=debug msg="Creating server server-portainer-app at http://<IP_ADDRESS>:9000 with weight 0"
time="2017-05-07T13:17:24Z" level=debug msg="Creating frontend frontend-Host-traefik-proxy-1-fr-to"
time="2017-05-07T13:17:24Z" level=debug msg="Wiring frontend frontend-Host-traefik-proxy-1-fr-to to entryPoint http"
time="2017-05-07T13:17:24Z" level=debug msg="Creating route route-frontend-Host-traefik-proxy-1-fr-to Host:traefik-proxy-1.fr.to"
time="2017-05-07T13:17:24Z" level=debug msg="Creating backend backend-traefik-proxy-1"
time="2017-05-07T13:17:24Z" level=debug msg="Creating load-balancer wrr"
time="2017-05-07T13:17:24Z" level=debug msg="Creating server server-traefik_proxy_1 at http://<IP_ADDRESS>:80 with weight 0"
time="2017-05-07T13:17:24Z" level=info msg="Server configuration reloaded on :80"

I have changed the docker-compose.yml like following:
version: '2'
services:
proxy:
image: traefik
command: --configFile=/var/traefik/traefik.toml
ports:
- "80:80"
- "8080:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- $PWD/servers.toml:/var/traefik/servers.toml
- $PWD/traefik.toml:/var/traefik/traefik.toml
But no change

@comprateur some news about volumes with traefik.toml ?

@comprateur Your Traefik instance runs into a Docker container registred on a by default Docker network. That's why it can only contact others containers from the same Docker network.
Are your backends into Docker containers too? Are they in the same Docker network than traefik?

I'll close the issue due to inactivity but feel free to re-open if needed.


recast / detour upgrade

Upgrade to recast / detour version from 12/2022 with additional navigation tests (should work with old version also)
There have been some bugfixes and updates in the last few years

@rokups we probably want to fork Detour/Recast as well because we patch it too
I think we can do that afterwards.
@WyrdanGames can you please link the commit of Detour/Recast you used?

https://github.com/recastnavigation/recastnavigation/tree/d0b2ed8ff5d371f375cf49dad7ca96e8b22142d0

@WyrdanGames FYI: if you ever consider updating 3rdparties again -- check if there's repo in rbfx org and ping us if there's none.
For patched 3rdparties we keep forks, it makes updating easier. You just rebase "rbfx" branch and fix conflicts if any...