Question on Event Model

Hi everybody,
I have a question regarding the event model how Azure Functions get data from event sources such as Blob Storage or Event Hub.
Is there a push / pull event model similar to AWS Lambda, for example?
Example 1: Triggering an event based on a uploaded file on Blob Storage:
Is this event pushed to Azure Functions? Is there a retry limit in case the event gets lost or the Azure Functions fails to execute? Are events from Blob Storage ordered?
Example 2: Reading / Processing messages from EventHub
Are messages from EventHub pushed to Azure Functions or is the Azure Functions runtime actively pulling messages from the EventHub? Is this done in batches or is a function triggered for every message? Is there a retry limit in case the function fails to execute? Is message delivery in order?
Thanks!
--Oliver.

Azure Storage doesn't currently support a push model, so currently we rely on efficient polling algorithms. We're working with the storage team to get a push model in place, but those changes will be transparent to Functions users. To answer your question, our blob trigger ensures that the blob will eventually get processed - the blob event will not get lost.
For your EventHubs question, we're using the EventHubs Event. Details on the underlying EventHubs binding can be found here. We use the EventHubs EventProcessorHost to pull events, and we do checkpointing only when events are processed successfully. Code for that is here.


[FEATURE] move redis key creation to a common module

Feature Description
Few entities currently are stored in redis. We create a key for each entity. This key will be usually of the form {feature}_{merchant_id}_{extras}. The creation of this key is being done in multiple places. It will be better to move all of these functions to a common module, this will add uniformity and help someone to easily know the key format for a particular entity.
Possible Implementation
There can be a module that exports functions for each of the key creation. This function takes the dynamic variables ( like merchant_id and extra variables and build the key. The format of this function would be
fn create_access_token_key(arg1: String, arg2: String, ...) -> String {}

One may also think about using enums for this.
Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to submit a PR?
No, but I'm happy to collaborate on a PR with someone else

🙋🏻♂
I'd like to draft a solution for this issue for you 😄. I suspect based on the criteria that there could be quite a bit of workshopping involved to iron this out, but I thrive on feedback and would enjoy that greatly.
✅  I have read the contribution guidelines
👀  I saw this item linked in TWIR 491

Hey @IsaacCloos, I've assigned this issue to you.

Thanks @IsaacCloos for showing interest. Yes that would be great. We can discuss about the implementation.

I am interested in collaborating with someone on their project so I can learn the language while they get a  sidekick.
Let me Know if this is something that could work for you.
I Would need you to explain and guide me through my first steps in the language (I already started learning) and set the standard for me in code reviews but after a short while I'm sure I'll become an asset to the project.
(I have some experience in Typescript and Java and have learned C a few years ago).

I'm sorry for the delay! I have become busy with work and juggling a few other issues. Please feel free to reassign this issue as you see fit since I noticed it hasn't been labeled as low priority. I don't want to hold up any work by squatting on it.
I see @EliKalter is showing interest 👀

I'd be happy to share my experience with setting up the project for local development and testing if somebody else gets stuck 🙂

Thanks @IsaacCloos , I appreciate the response, Honestly I'm not sure it was a good idea for me to offer help because I've never contributed to an open source before (so I'd need help with the most basic of tasks in that regard) nor do I know rust even remotely well (so I'd need help on that from as well), I'm thinking maybe I should learn rust better by myself and start contributing on other beginner friendly projects first and get back to contributing to rust projects some day down the line, what are your thoughts?
(I don't like wasting peoples time...)

I'm sorry for the delay! I have become busy with work and juggling a few other issues.

@IsaacCloos No problem, we understand that contributors have a personal life, and contribute to our project during their free time and out of their own interest, not due to obligation.

Please feel free to reassign this issue as you see fit since I noticed it hasn't been labeled as low priority. I don't want to hold up any work by squatting on it.

I'm sorry for the confusion, this is indeed a low priority refactor and does not block any of our work. It's a good-to-have change, and not an immediate necessity. I've updated the labels on this issue to reflect the same.
Let us know if you're still interested in taking a look at this, we'll help @EliKalter with any if the other issues they've expressed their interest on.

[...] Honestly I'm not sure it was a good idea for me to offer help because I've never contributed to an open source before (so I'd need help with the most basic of tasks in that regard) nor do I know rust even remotely well (so I'd need help on that from as well), I'm thinking maybe I should learn rust better by myself and start contributing on other beginner friendly projects first and get back to contributing to rust projects some day down the line, what are your thoughts? (I don't like wasting peoples time...)

Folks being new to Rust and/or open source contributions is completely fine with us. We all started somewhere. Among the issues you expressed your interest on, #899 seems to be a pretty simple change. I can assign it to you and you can work on it at your own pace. Would that work for you? Feel free to ask any more questions you may have on that thread.

[...] Honestly I'm not sure it was a good idea for me to offer help because I've never contributed to an open source before (so I'd need help with the most basic of tasks in that regard) nor do I know rust even remotely well (so I'd need help on that from as well), I'm thinking maybe I should learn rust better by myself and start contributing on other beginner friendly projects first and get back to contributing to rust projects some day down the line, what are your thoughts? (I don't like wasting peoples time...)

Folks being new to Rust and/or open source contributions is completely fine with us. We all started somewhere. Among the issues you expressed your interest on, #899 seems to be a pretty simple change. I can assign it to you and you can work on it at your own pace. Would that work for you? Feel free to ask any more questions you may have on that thread.

Thanks @SanchithHegde , I assume this thread is being taken care of by @IsaacCloos and that's way you suggested #899?!
I'll take a look at #899 and hopefully feel comfortable taking care of it, anyway I'll move my comments to that thread now, thank you

@EliKalter I'll be assigning this to you, as discussed over Discord.

@EliKalter Please let us know if you're still working on this issue or still interested in working on it. There hasn't been any recent activity on this thread, or any open PRs.
We hope to hear from you by the end of June 2023, or we'll open this for other contributors to pick up.

I'll be opening this issue for other contributors to pick up.

@SanchithHegde ,I would like to work on this if this is free .

Sure @lokesh185, I'll assign this to you. You can reach out to us in case of any queries either on this thread, or on our Discord server.

Hey @lokesh185
Just checking in - are you working on it? Do you need help from our side?

yes i am still working on it .
this is the enum and impl that i was thinking of using , does this look good ?
pub enum RedisKey<'a> {
    // "access_token_{merchant_id}_{connector_name}"
    AccsesToken {
        merchant_id: &'a str,
        connector_name: &'a str,
    },
    // for "mcd_{merchant_id}_{creds_identifier}"
    MCDCredsId {
        merchant_id: &'a str,
        creds_identifier: &'a str,
    },
    // for "connector_resp_{merchant_id}_{payment_id}_{attempt_id}"
    ConnectionResponse {
        merchant_id: &'a str,
        payment_id: &'a str,
        attempt_id: &'a str,
    },
    // for "pi_{payment_id}"
    PaymentId {
        payment_id: &'a str,
    },
    // for "mid_{merchant_id}_pid_{payment_id}"
    MerchantPaymentIds {
        merchant_id: &'a str,
        payment_id: &'a str,
    },
    // for "whconf_{merchant_id}_{connector_id}"
    WhConf {
        merchant_id: &'a str,
        connector_id: &'a str,
    },
    // for "whsec_verification_{connector_label}_{merchant_id}"
    WhSecVerification {
        connector_label: &'a str,
        merchant_id: &'a str,
    },
}
impl ToString for RedisKey<'_> {
    fn to_string(&self) -> String {
        match self {
            Self::AccsesToken {
                merchant_id,
                connector_name,
            } => {
                format!("access_token_{merchant_id}_{connector_name}")
            }
            Self::ConnectionResponse {
                merchant_id,
                payment_id,
                attempt_id,
            } => {
                format!("connector_resp_{merchant_id}_{payment_id}_{attempt_id}")
            }
            Self::MCDCredsId {
                merchant_id,
                creds_identifier,
            } => {
                format!("mcd_{merchant_id}_{creds_identifier}")
            }
            Self::PaymentId { payment_id } => {
                format!("pi_{payment_id}")
            }
            Self::MerchantPaymentIds {
                merchant_id,
                payment_id,
            } => {
                format!("mid_{merchant_id}_pid_{payment_id}")
            }
            Self::WhConf {
                merchant_id,
                connector_id,
            } => {
                format!("whconf_{merchant_id}_{connector_id}")
            }
            Self::WhSecVerification {
                connector_label,
                merchant_id,
            } => {
                format!("whsec_verification_{connector_label}_{merchant_id}")
            }
        }
    }
}

this is how to make the redis key
    let key = RedisKey::AccsesToken {
        merchant_id: "abcd",
        connector_name: "efgh",
    }
    .to_string();
    assert_eq!(key, "access_token_abcd_efgh".to_string());

This seems right, good work @lokesh185, you will have to fix few of the spellings though!

Closing against #4462


CIP-???? | Deterministic universal almost-unique Plutus Constructors

OpShin has recently gone the path of redefining the way it uses constructor ids internally to distinguish types. Since the implementation is language agnostic, we provide the specification here for other languages or applications to adopt as they see suitable.

(rendered proposal in branch)

@nielstron I've put this on the agenda for initial review at next CIP meeting: https://hackmd.io/@cip-editors/76

Adding to https://github.com/cardano-foundation/CIPs/pull/608#issuecomment-1810601563 from CIP Editors' meeting today, where it was also brought up, that @nielstron we would be interested in seeing responses to the reviews already presented before we can more fully consider this as a CIP.  Until then it does seem like it could instead be a useful "best practice" document with a good idea that might not be compelling for others to adopt.

@nielstron as far as I can tell, the last 2 commits https://github.com/cardano-foundation/CIPs/pull/608/commits/5d7861c246610535ec0943d42e1b9394a5366d0f & https://github.com/cardano-foundation/CIPs/pull/608/commits/1723c1bb086d069ba1bbc856089c738fd8075528 haven't addressed the feedback that I tried to summarise in https://github.com/cardano-foundation/CIPs/pull/608#issuecomment-1811720014 9 months ago.
We are tagging some proposals Abandoned but we never tagged this one Waiting for Author first (I'm trying this week to overhaul our editing process with tagging stale PR's) so I'm applying that tag now.  I expect that you can address the review points above (please make some notes in the relevant conversations) or explain why the points have all addressed.
It's just a matter of explaining your points clearly I believe... once we see that this is done we can put it back on the CIP meeting agenda to look at promoting it to a candidate; if no further progress the next few weeks it will probably be moved onto the Abandoned list & closed soon afterward.

@nielstron let's make one last call for updates before closing this as "abandoned" but please if you are interested in pursuing this then respond to the last comment & we'll plug it back into the review process.

Hi @rphair ,
I don't have time to work on this CIP anymore, so feel free to tag it as abandoned.


Add configuration for whitelist-only methods

Context
Bigtable added EAP methods to their public protos. See: https://github.com/googleapis/googleapis/blob/546d3afd75187e65229a2670eb440e84a05f5d9d/google/bigtable/v2/bigtable.proto#L86
What
APIs may have features or methods in their IDL that are only accessible to certain, whitelisted users. In some cases, it may be desirable for client libraries to annotate such methods, or guard them with feature flags, etc. To do so, we should introduce an additional method annotation to the GAPIC config. The semantics of this annotation may vary based on what is idiomatic in a particular client library language.
Why
It is a poor user experience for methods to be available on the client object that generally do not work for most customers.

@hkdevandla It's somewhat related to how we are going to support googleapis_private... so bringing this to your attention for you to decide whether to proceed.

This will be not be supported.


Adding str method to every class

Made it so that when doing str(scene), it will return the scene name (:

Don't merge this rn, gonna add to more


Fedora installation

If someone wants to install this into a Fedora system he needs to copy the "go" file to
/usr/share/bash-completion/completions
as
/etc/bash_completion.d/go
is not used by Fedora

Hi, this directory is used on Fedora:
$ rpm -qf /etc/bash_completion.d/
filesystem-3.2-40.fc26.x86_64
bash-completion-2.6-1.fc26.noarch


Node 12 and set-output are being deprecated

I've noticed the following warnings in GitHub actions when using this action:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: shioyang/check-pr-labels-on-push-action, shioyang/check-pr-labels-on-push-action, shioyang/check-pr-labels-on-push-action

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

@kylegwalsh Thank you for the report. The latest release should fix the warnings.
Please use the latest version.

@shioyang Thanks for the update!
I just tried the fix in my own pipeline and see that the Node.js 12 actions warning has disappeared.
However, I still notice the set-output warning. Is the latest release leveraging $GITHUB_STATE or $GITHUB_OUTPUT now?
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/


updated documentation

Made some minor updates to the main documentation.

Where should those secret keys be implemented?

Pull Request Test Coverage Report for Build 829

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 61.994%

Totals

Change from base Build 820:
0.01%

Covered Lines:
4600

Relevant Lines:
6930

💛  - Coveralls

Thank you, merged!


support --value/--argument param for use with --execute

at the moment, there is no way to safely interpolate values into SQL that is passed into crash on the command-line for execution. the only way to do it is via shell string interpolation
it would be good if crash supported something like --variable=assignment ala the psql client (cf. https://www.postgresql.org/docs/9.5/app-psql.html)
at the moment, I have to warn users not to attempt something like this in production, even though it's handy for use in tutorials. see the WARNING note here: https://crate.io/docs/crate/tutorials/en/latest/generate-time-series/cli.html#record-the-iss-position

I think this'd be a nice idea, we could also support the \set syntax like psql does during an interactive session for a similar purpose.


Remove the FsToolkit.ErrorHandling.TaskResult dependency from the main test project to enable full backwards compat testing with FSharp.Core 6.0.1

Problem statement
The library FsToolkit.ErrorHandling.TaskResult is an excellent library, but recently they have introduced non backwards-compatible dependencies that limit our ability to continue using this library in our tests for obvious reasons: we want the tests to be as close to real-world as possible, using the lowest denominator FSharp.Core that the TaskSeq library supports.

The 4.x range, including the very first 4.0.0 requires FSharp.Core 7.x: https://www.nuget.org/packages/FsToolkit.ErrorHandling/
Versions 3.3.1-beta001-3.3.1 require FSharp.Core 7.0.0 or up
Version 3.2.0 (the one we have been using, but it is getting rather old) requires FSharp.Core 6.0.3

Since TaskSeq is backward compatible till FSharp.Core 6.0.1, we should try to test it with that version.
Simple solution
The simplest way is to move the dependent tests to SmokeTests (which is only the PoC, ironically showing the problems with lists of Tasks using an oversight of the TaskResult library, where it seems to support lists of Tasks, but not really if they're hot-started, and they always are).
Note that SmokeTests does the opposite, and tests the library, using a a pull of the actual NuGet lib, against recent versions of FSharp.Core.

Thanks for review @bartelink!! 👍
I've updated the code based on your suggestions and will merge to main. If you want, you can re-review :).

@bartelink you didn't click "approve", but your last comment suggests you approve these changes. If there's anything I missed, I'm sure you'll let me know ;).

(but I can unblock myself, of course).

Apologies; please put me on the drive by commenters list ;)
Your standards/judgement for what makes sense to merge are in excess of mine, and any comments can always be addressed in follow-ups

@bartelink I've given you Triage access, which, I think, allows you to basically do everything, accept for write access (that is, the final merge will have to be approved or done by me). I value your input, thanks! 👍


Ftp: certificate used by the test is generated with a very short validity

Bug description
My previous fix did not extend validity of the certificate. Therefore validity is 30 days. It should be regenerated and the commands for the certificate generation should be updated to use for example 10000 days,

@JiriOndrusek this could be fixed by

https://github.com/apache/camel-quarkus/pull/5523 ?

@zhfeng yes, I'm sorry I forgot to put this ticket into the summary, to autoclose

@zhfeng yes, I'm sorry I forgot to put this ticket into the summary, to autoclose

FYI it's better to put the Fixes # part into the commit comment as we have a GitHub workflow that can auto add the issue to the current milestone after merge.

@zhfeng yes, I'm sorry I forgot to put this ticket into the summary, to autoclose

FYI it's better to put the Fixes # part into the commit comment as we have a GitHub workflow that can auto add the issue to the current milestone after merge.

That's what I meant, sorry for confusion.


Optionally log to a file instead of stderr.

The file will be re-opened by SIGUSR1 just like access logs.
Signed-off-by: Greg Greenway<EMAIL_ADDRESS>

@mattklein123 I've addressed or commented on everything above.  Let me know if any other changes are needed.

@ggreenway thank you will look soon. Request: In the future please do not rebase a PR once it has been opened (just push commits / merge master) as it is much harder to review. Thank you. (No problem this time).

Is it possible to make stderr a special case of --log-path by using /dev/stderr or something like this? Would be nice to avoid having to maintain dual paths.

This would be cool but I wonder if this is too platform specific? Is there a general way to do this in the standard? (IIRC stderr gets opened on some fd so maybe it's possible somehow).

Stderr is at fd 2 when a process starts, aka STDERR_FILENO.

My only concern with merging the stderr and file writing code is that I think it might be a little awkward with how the access log manager stuff works. There is logging before all of that is available. It might still be doable, especially if the writing is done though an interface, but not sure. Let's see what @ggreenway thinks.

I like the idea of logging to STDERR_FILENO instead of having two paths, but we'd have to come up with a solution to the early-startup and late-shutdown log messages.
For early startup, we could just buffer any messages somewhere until the logfile is setup, but that's still a separate path we have to maintain, and if we crashed before the logfile is setup we'd have no output.  Could try to work around the crashing problem in a signal handler, but that's adding a lot more complexity.
Another approach would be to allow creating a FileImpl without its dependencies (mostly the dispatcher for creating the flush timer) and AccessLogManager, and then associate the FIleImpl with those things when they're setup later.
I think these approaches reduce complexity in the logger but adds it somewhere else.  I'm ok with doing that if you guys see it as substantially better.  Thoughts?  Or better ideas on how to deal with early/late logging?

Thinking out loud, what if we use tee(2) internally, always log to stderr and then later in init we can redirect to a file? I'm not a fan of doing anything that makes implementation more complex, so if this won't help, I'm good with two paths as exist today.

FWIW I think my vote is probably just to leave the PR as is WRT to different paths. I think the other options will add just as much complexity (more?) as it will remove.

@ggreenway unfortunately every commit has to have DCO. Can you fix? (You can either rewrite the commits that are missing and push to retain commit history or just squash and force push).

@ggreenway sorry can you merge master to run Circle tests

@mattklein123 Should be good to go now


uploading multipart form-data is giving invalid Media Type

We are using openapi as middle layer between Java REST API and Client.
Request flow: Client -> OpenAPI -> JAVA REST API
Response flow: JAVA REST API -> OpenAPI -> Client
We are getting invalid media type error while trying to upload a xlsx file through openAPI.
Swagger requestBody configuration
"requestBody": {
"required": true,
"content": {
"multipart/form-data": {
"schema": {
"type": "object",
"properties": {
"file": {
"type": "string",
"format": "binary"
}
}
}
}
}
}
java is expecting as
Content-Disposition: form-data; name="file"; filename="test.xlsx"
Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
can someone help us to identify the issue here?

@saravanavel891 this repository is for the specification.  Please raise tooling issues with the tooling vendor / repository.
But since I happened to have been working on that part of the spec this week, off the top of my head, assuming you're using OAS 3.0, while what you have probably ought to work as it expects application/octet-stream and literally any resource is technically a valid application/octet-stream, you might want to use the contentType field in an Encoding Object to explicitly set the file's Content-Type to application/vnd.openxmlformats-officedocument.spreadsheetml.sheet


Notebook integration tests: Element already has context attribute

For example: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=95890&view=logs&j=1c20ec05-7612-5293-9b87-7ea15c22422f&t=d9b931d5-6469-5709-27a9-2ddd8b3d265c&l=1210
[3851:1202/083542.312296:INFO:CONSOLE(1977)] "Element already has context attribute", source: file:///__w/1/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.desktop.main.js (1977)
    ✓ document open/close event (362ms)

I can also repro this in Insider's by trying to open the "endgame.github-issues" notebook, it prevents the notebook from rendering:

It's a noisy but harmless error, it shouldn't actually break anything
https://github.com/microsoft/vscode/issues/111280


Added an "ended" event when video ended

Added an "ended" event like in HTML5 Video, which is fired when the video has ended.

This is already supported via the onfinished option. I have updated the readme to include this option.


A way to either remove or style GDS render labels.

Produces clean GDS without the overload of labels.
Project class has a remove_all_labels_from_svg (bool) attribute, currently set to True, that flushes them all.  But went all out and have basis to allow us to choose how to style labels on a layer-by-layer basis.

I think you opened it against the wrong branch? It includes commit from tt03p5 which shouldn't go into the tt03 branch

Please update this against the new tt04 branch and open a new PR. Thanks!


Disable SO_REUSEPORT disabled test for uv tests

After the libuv/ custom server refactor, there isn't an easy way to disable the use of SO_REUSEPORT.
This disables the test for GRPC_ARG_ALLOW_REUSEPORT for libuv and fixes.
#14926
cc @jtattermusch

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences


Template parsing issue with handlebars in a string

This may be an odd edge case. But check this out...
~H"""

"""

This results the following compilation error.
== Compilation error in file lib/fe_web/views/editor/item.ex ==
** (TokenMissingError) lib/fe_web/views/editor/item.ex:74: missing terminator: " (for string starting at line 74)
    (eex 1.10.1) lib/eex/compiler.ex:45: EEx.Compiler.generate_buffer/4
    expanding macro: Surface.sigil_H/2
    lib/fe_web/views/editor/item.ex:73: FeWeb.Editor.Item.render/1
    (elixir 1.10.1) expanding macro: Kernel.if/2
    lib/fe_web/views/editor/item.ex:72: FeWeb.Editor.Item.render/1

Rewriting it this way fixed the issue.
style_text = "height: #{assigns.dragging_height}px;"
~H"""

"""

The issue appears to be when putting {{ @stuff }} inside a string it confuses the parser.

Fixed in https://github.com/msaraiva/surface/commit/170796626993ef98d973ebf7faa6280dce755d36
@brainlid thanks for reporting this.


Batch search

Resolving #12
Batch search capabilities added.
New method signature added to the client instance: batch_search(requests)
Requests argument is an array of hashes with following attributes: type, uuid and relationships.
Specs added and docs updated.
Open for any constructive comments/edits; my first contribution to open source.

Thank you @korac for the update! Your update looks great and merged into master.

Really happy to have you joined!

Awesome, thanks for the feedback @encoreshao !
Glad to have joined!

Hey @encoreshao when can we expect the latest changes to be pushed up to rubygems?
Thanks!

@korac - released new version on rubygems - crunchbase-ruby-library-0.3.2


CMSG_SPACE should be const

There was this: https://github.com/rust-lang/libc/issues/2087 but since https://github.com/rust-lang/libc/pull/2132 had no tests in it it either never worked or got broken at some point later:
use std::os::unix::prelude::RawFd;

const CONTROL_LEN: usize = unsafe { libc::CMSG_SPACE(std::mem::size_of::<RawFd>() as _) as _ };

t% cargo test
   Compiling libc v0.2.126
   Compiling asdf v0.1.0 (/home/pacak/rust/asdf)
error[E0015]: cannot call non-const fn `CMSG_SPACE` in constants
 --> src/lib.rs:3:37
  |
3 | const CONTROL_LEN: usize = unsafe { libc::CMSG_SPACE(std::mem::size_of::<RawFd>() as _) as _ };
  |                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: calls in constants are limited to constant functions, tuple structs and tuple variants

For more information about this error, try `rustc --explain E0015`.
error: could not compile `asdff` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

rustc 1.60.0 (7737e0b5c 2022-04-04)

You have to enable the const-extern-fn feature of the crate.

I see, and it's nightly only. That's sad.
Thank you.

I see, and it's nightly only. That's sad.

It'll be available from 1.62, thanks to https://github.com/rust-lang/rust/pull/95346 :)


Add input option to plugin-svelte

Changes
Adds an input option to plugin-svelte that modifies resolve.input. Enables non-standard file extensions such as .svx to be used
Testing
Roughly copied the related tests from plugin-babel. Had issues getting test to run properly locally, so opening the PR a bit early to see the results.
Docs
Roughly copied related docs from plugin-babel.

Test Passed. Ready for review

I use svelte, but haven't heard of the svx convention before. Out of curiosity, how common is this?

@canadaduane This PR adds ability to modify the file extensions we run on, primarily to add things in addition to .svelte. It add feature parity with the rollup and webpack svelte plugins.
Overriding extensions for plain svelte files is not a standard convention, but a couple of popular libraries do this. Namely the markdown preprocessor for svelte, pngwn/MDsveX, which uses .svx as its convention (but can be made to run on normal .svelte files as well)
There is also the storybook replacement, rixo/svench which runs on .svench (and also recommends using mdsvex for documentation).
Its worth noting that for mdsvex, using another file extension is sort of required since it treats the entire file as html enabled markdown without checking/needing a lang="md" attribute. Meaning <p> *words* <p> will italicize, something you probably dont want in a normal svelte file

Thinking about why he asked made me realize I put ['.svelte','.svx'] into the recommendation of the error output instead of just the default value ['.svelte'], as I did in the documentation. This was primarily to show it was an array of file extensions and to sort of to match what the babel plugin threw, but I can see how it could be confusing. Probably would have been better to just recommend the default

I think it's fine as-is. It would only show that to the user who's playing around with the input setting, so it's not necessarily the "default" user who would see that message.

Thanks, that makes more sense now.
On Sun, Oct 18, 2020, 1:35 AM Fred K. Schott<EMAIL_ADDRESS>wrote:

I think it's fine as-is. It would only show that to the user who's playing
around with the input setting, so it's not necessarily the "default" user
who would see that message.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snowpackjs/snowpack/pull/1347#issuecomment-711129496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAABAP73F6UJPLUKDLL5BTSLKLEZANCNFSM4SUTFRXA
.

Could this be defaulted to the extensions value in svelte.config.js to cut down on duplication?

https://github.com/sveltejs/rollup-plugin-svelte#usage

@techniq While I also use extensions in my svelte.config.js (since that is the name of the rollup plugin's option, and I need to keep my svelte.preprocess cli in sync with my builder/bundler), I believe the field is non-standard and not recommended in the language-tools docs. I am doubtful it will become a standard as well since iirc, webpack uses a different mechanism for matching files with loaders.


fix: let end user of presta handle output dir cleanup

@estrattonbailey why is it that coverage would decrease by removing code and corresponding test

got it, so amend the commit contained in the PR?fix: let end user of presta handle output dir cleanup

@estrattonbailey ok, the changeset should be added now


Coercion controls

The Slang language like HLSL, has silent coercions between certain built in type combinations.  Such coercions can be the source of bugs and can have significant performance implications.
On testing on Slang it seems...

u/int/64/32 <-> float/double
u/int64/32 <-> u/int64/32
float16/float64/double <-> float16/float64/double

Which seems to indicate that any float/integral built in type can silently coerce to any other built in type(!)
On DXC we do get some warnings.. (I didn't test this exhaustively)
D:\local\Temp\1980f0cd-8f60-495c-8061-54a9d0a38635.hlsl:16:9: warning: conversion from larger type 'uint64_t' to smaller type 'int', possible loss of data [-Wconversion]
    int h = f;
        ^
D:\local\Temp\1980f0cd-8f60-495c-8061-54a9d0a38635.hlsl:18:11: warning: conversion from larger type 'double' to smaller type 'float', possible loss of data [-Wconversion]
    float i = e;
          ^

I think it could be argued that Slang not have the warnings that DXC has is a bug.
That in the C based languages conversions with same sized integrals but signed/unsigned isn't typically an error. This can lead to some hard to find bugs.
So in terms of a way forward...

Slang should give (with a disable options) a warning in the same places DXC (and/or FXC does)
We can't rely on downstream compiler(!)
Arguably this should be default behavior
Should have an option to warn/silent/error for integral sign changes
Should have an option to warn/silent/error for floating point coercion's that lose information
Should have an option to warn/silent/error for float/int and int/float conversions

This might be a bit more subtle, as we might want to allow int32 -> double as no loss of information, but might be a perf hit

That coercion to larger types that that can hold without loss/sign issues work as normal (that is silently)...

float16 -> float -> double
int8->int16->int32->int64
uint8->uint16->uint32->uint64

As hinted at above integral to float conversions are more subtle. Is int -> float to silently coerce ok? It does lose some information (not every int is directly representable as float) but it's never going to inf/nan. That isn't it somewhat expected behavior that some information is lost when working with float? It may not be necessary to answer this other than making our default sensible, and having the option of warning/error on such conversions.
Where float16->double etc is ok too.

The part of this about emitting warnings is probably relatively easy to add to the current codebase. We already have a core function (_coerce()) that handles the details of implicit coercion of a value of one type to another type, and that function returns (via an output parameter) the "cost" of the conversion using the ConversionCost enumeration. These costs are what we use to rank different function overloads, when that is required.
The ConversionCost enumeration already partitions things so that the "safe" conversions (those guaranteed not to loose information) are ranked as lower cost than those that might lose information. The compiler logic currently only uses the actual values to issue an error when the cost is >= kConversionCost_Explicit which represents conversions which should not be performed implicitly. It should be a simple enough matter to pick another point on the ConversionCost scale where we start issuing warnings.
Note that the main cases of warnings called out here are already in the enumeration: we have SignedToUnsignedConversion to catch casts that preserve all bits but could change sign, IntegerToFloatConversion to catch all implicit conversions from integral to floating-point types (currently we don't distinguish cases where the integer's magnitude can be encoded losslessly in the mantissa bits), and GeneralConversion which should include all potentially-lossy conversions.
The harder bit of the proposed feature here would giving users fine-grained control over enabling/disabling the individual warnings. Part of the difficulty is that we don't really have a ton of infrastructure in place for enabling/disabling warnings yet, and the other part is that the single ranking of conversion costs we have today would make it a bit tricky to enable/disable the different cases of conversions separately.
A third issue we need to be aware of here is that enabling warnings for conversions like this is likely to produce a lot of "false positive" issues when it is applied to literals. By default, our literals have type int or float, so that initializing a variable of type half with half h = 0 or half h =0.0 technically involves an int->half or float->half conversion, and that might create warnings. My experience is that users would want this feature to not warn on "obviously correct" code involving literals (which is reasonable), which means we may need to greatly improve our handling of literals and constant folding before we can reliably add and enable these warnings.
If we decide to pursue this work and want the fine-grained enable/disable or warnings for specific kinds of conversions, it might make sense to push the details out to attributes used in the stdlib. We could define an attribute [implicitConversionWarning("...")] that we add to the functions representing implicit conversions, and then in the logic that introduces function calls to perform implicit conversion we could check if the callee function has an associated warning attribute, and then emit the given warning if it is not disabled. That would allow each conversion to be associated with whatever warning makes sense, independent of its numerical conversion cost.

Just a comment to flag that this is still and issue - and int64_t will silently coerce to int.

Closing this issue now.
We currently do diagnose on lossy conversions, except that we silently allow same-size signed->unsigned or unsigned->signed conversions to not being annoying.


Update porting guide to reflect switch to CMake and new repo structure

This adds 2 new sections to the guide that cover how to port to CMake. There are a lot of TODOs in this PR that are open questions which I'd like input on.
Closes #5

@Vyrastas Thanks for all the feedback. It was super useful and made sense. I just pushed the changes. Could you review again?
Also, a question for everyone: Would it be a good idea to have a markdown linter in ot-docs , like ./script/make-pretty in the openthread stack repo?

Also, a question for everyone: Would it be a good idea to have a markdown linter in ot-docs , like ./script/make-pretty in the openthread stack repo?

I'd have to look into this... these docs are imported into openthread.io with a script, and some of the special Markdown formatting we need might not align with make-pretty. I'm not familiar with it to know if it can be customized? If so, I'd be for it.

@jwhui Thoughts? I haven't worked with configuring the markdown formatter before, but I feel like it should be possible. The main thing that's bothering me is just that some lines are wrapped with a newline at 80 characters and other lines are not wrapped

I think it's a good idea to have a linter. We currently use Prettier in other repos for markdown. However, we do currently exclude doc/site in the core repo - see script/make-pretty#L68. As @Vyrastas , we'd have to make sure whatever configuration we use is compatible with the import script.

Also, a question for everyone: Would it be a good idea to have a markdown linter in ot-docs , like ./script/make-pretty in the openthread stack repo?

I'd have to look into this... these docs are imported into openthread.io with a script, and some of the special Markdown formatting we need might not align with make-pretty. I'm not familiar with it to know if it can be customized? If so, I'd be for it.

@jwhui Thoughts? I haven't worked with configuring the markdown formatter before, but I feel like it should be possible. The main thing that's bothering me is just that some lines are wrapped with a newline at 80 characters and other lines are not wrapped

I think it's a good idea to have a linter. We currently use Prettier in other repos for markdown. However, we do currently exclude doc/site in the core repo - see script/make-pretty#L68. As @Vyrastas , we'd have to make sure whatever configuration we use is compatible with the import script.

Ah yes I forgot that we had disabled it for the doc directory in the main repo.  I'll have to take a look and see if we can adjust the configuration accordingly.

@Vyrastas Thanks for opening the new issue. Just made last edits you requested so the PR should be good to go if @librasungirl and @jwhui don't have any other comments.

@Vyrastas Thanks for opening the new issue. Just made last edits you requested so the PR should be good to go

You'll need to rebase, we merged #11 on Friday that fixed some broken links... a couple are in the porting guide.  Otherwise LGTM

@jwhui This one should be good to merge


USB sound card is not detected after updating 19.09 channel

Describe the bug
I tried upgrading from 19.09.1172.2d896998dc9 to more recent 19.09.1254.9104be2ee08, but after the upgrade my usb sound card (EMU 0404) is not being detected as sound device.
It shows in dmesg and lsusb as USB device, but not as a sound device in /dev/snd/, /sys/class/sound, aplay -l, pactl list sinks.
Plugging it in to other USB port doesn't help.
I downgraded the kernel to LTS (4.19) to check if upgrade from 5.3.9 to 5.3.11 caused the problem, and the problem is still there with LTS kernel.
I've checked dmesg/journalctl -b and there are no obvious errors.
Rolling back to 19.09.1172.2d896998dc9 makes the sound card work again.
Metadata

system: "x86_64-linux"
host os: Linux 5.3.11, NixOS, 19.09.1254.9104be2ee08 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3
channels(root): "nixos-19.09.1019.c5aabb0d603"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Same issue with nixpkgs 19.09.1292.e1843646b04.
I've noticed this message in the log when I replug the device:
systemd-udevd[2620]: 3-1: Failed to process device, ignoring: No such file or directory

Btw, I have enableRedistributableFirmware = true, which should add alsa-firmware.

I've tried unstable 20.03pre201791.c1966522d7d and it has the same issue :/

Triage: still relevant?


Can't login with local accaunt

Hi, I integrated superset with the LDAP, and finally, it works. But now, I cannot log in with a local (admin) account, if I comment LDAP integration configuration in config.py then I can log in but with LDAP I can't.
Expected results
I expected to login with both, LDAP and local accaunts.
Actual results
I have to choose one of them.
Environment
(please complete the following information):

superset version: 0.38.1
python version: 3.6.8
node.js version: node -v

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Also, I want to configure multiple integrations with the same LDAP, for x group 1 role, for y group 2 role, etc... Which part is responsible for that??

Hi @fropa to be honest, this is probably a better question for Stack Overflow. You can use the apache-superset tag: https://stackoverflow.com/questions/tagged/apache-superset
Can you provide significantly more context on your setup so people here on Github or on StackOverflow can try to help?

Hi @fropa to be honest, this is probably a better question for Stack Overflow. You can use the apache-superset tag: https://stackoverflow.com/questions/tagged/apache-superset
Can you provide significantly more context on your setup so people here on Github or on StackOverflow can try to help?

Hi srinify, thank you for your answer, I'll ask on StackOverflow and provide more details here too.
I did that context :
from flask_appbuilder.security.manager import AUTH_OID
from flask_appbuilder.security.manager import AUTH_REMOTE_USER
from flask_appbuilder.security.manager import AUTH_DB
from flask_appbuilder.security.manager import AUTH_LDAP

#AUTH_TYPE = AUTH_LDAP
#AUTH_USER_REGISTRATION = True
#AUTH_USER_REGISTRATION_ROLE = "Public"

#AUTH_LDAP_SERVER = "ldap://<IP_ADDRESS>"
#AUTH_LDAP_USE_TLS = False
#AUTH_LDAP_BIND_USER = "CN=Administrator,CN=Users,DC=gru,DC=lab"
#AUTH_LDAP_BIND_PASSWORD = "password"
#AUTH_LDAP_SEARCH = "DC=gru,DC=lab"
#AUTH_LDAP_GROUP_FIELS="CN=linuxadmins,DC=gru,DC=lab"
#AUTH_LDAP_SEARCH = "DC=gru,DC=lab"
#AUTH_LDAP_UID_FIELD = "sAMAccountName"
#AUTH_LDAP_FIRSTNAME_FIELD = "givenName"
#AUTH_LDAP_LASTNAME_FIELD = "sn"

with that configuration I can log in to superset web, (I'm trying to split login roles with "AUTH_ROLES_MAPPING" but with no luck yet) but when I log in through LDAP users, I can't use local user such as admin (the user which created during installation).


Integration fails to load after upgrade from 2024.6.0 to 2024.6.1

System Health details
System Information

version
core-2024.6.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
6.6.33-haos

arch
x86_64

timezone
America/New_York

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4970

Installed Version
1.34.0

Stage
running

Available Repositories
1459

Downloaded Repositories
8

HACS Data
ok

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 12.4

update_channel
stable

supervisor_version
supervisor-2024.06.0

agent_version
1.6.0

docker_version
26.1.4

disk_total
116.7 GB

disk_used
9.4 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Studio Code Server (5.15.0), Matter Server (6.1.2), Z-Wave JS (0.6.2), ESPHome (2024.6.1), Mosquitto broker (6.4.1)

Dashboards

dashboards
3

resources
2

views
8

mode
storage

Recorder

oldest_recorder_run
June 17, 2024 at 12:02 PM

current_recorder_run
June 24, 2024 at 10:21 AM

estimated_db_size
225.41 MiB

database_engine
sqlite

database_version
3.44.2

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
After upgrading from 2024.6.0 to 2024.6.1 I get the error integration failed to load.  It appears to be related to climate
Reproduction steps

Install update from previous release

Debug logs
Logger: homeassistant.util.loop
Source: util/loop.py:84
First occurred: 10:21:54 AM (1 occurrences)
Last logged: 10:21:54 AM

Detected blocking call to import_module inside the event loop by custom integration 'pitboss' at custom_components/pitboss/__init__.py, line 57: await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1281: return importlib.import_module(f"{self.pkg_path}.{platform_name}")), please create a bug report at https://github.com/dknowles2/ha-pitboss/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/pitboss/__init__.py", line 57, in async_setup_entry await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)

Logger: homeassistant.loader
Source: loader.py:1249
First occurred: 10:21:54 AM (2 occurrences)
Last logged: 10:21:54 AM

Unexpected exception importing platform custom_components.pitboss.climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1249, in _load_platform
    cache[full_name] = self._import_platform(platform_name)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1281, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 131, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/pitboss/climate.py", line 34, in <module>
    class GrillClimate(BaseEntity, ClimateEntity):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 395, in __init__
    wrap_attr(cls, property_name)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 367, in wrap_attr
    raise TypeError(f"Can't override {attr_name} in subclass")
TypeError: Can't override _attr_max_temp in subclass

Logger: homeassistant.config_entries
Source: config_entries.py:594
First occurred: 10:21:54 AM (1 occurrences)
Last logged: 10:21:54 AM

Error setting up entry PBL-02143D8 for pitboss
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1249, in _load_platform
    cache[full_name] = self._import_platform(platform_name)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1281, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 131, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/pitboss/climate.py", line 34, in <module>
    class GrillClimate(BaseEntity, ClimateEntity):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 395, in __init__
    wrap_attr(cls, property_name)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 367, in wrap_attr
    raise TypeError(f"Can't override {attr_name} in subclass")
TypeError: Can't override _attr_max_temp in subclass

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/pitboss/__init__.py", line 57, in async_setup_entry
    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2031, in async_forward_entry_setups
    await integration.async_get_platforms(platforms)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1162, in async_get_platforms
    import_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1162, in async_get_platforms
    import_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1162, in async_get_platforms
    import_future.result()
  [Previous line repeated 2 more times]
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1150, in async_get_platforms
    platforms.update(self._load_platforms(platform_names))
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1075, in _load_platforms
    platform_name: self._load_platform(platform_name)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1269, in _load_platform
    raise ImportError(
ImportError: Exception importing custom_components.pitboss.climate

Diagnostics dump
No response

Same issue for me. Reverting to 2024.5.0 got me back and running.
My grill is the PB850PS2.

https://github.com/dknowles2/ha-pitboss/releases/tag/2024.6.2 should fix this


Add oauth2 support for gmail and outlook

This is an updated PR to fix the merge conflicts of the previous xoauth2 PR
Relates to #655
Note that Gmail support requires updating the google client id (and potentially package name) in common/build.gradle.
Use the google console to create OAuth 2.0 Client IDs: https://console.cloud.google.com/apis/credentials
Also worth considering this adds a dependency on retrofit which isn't used by k9 anywhere else.

Hi, any chance to see this merged ?

These changes aren't working for me currently. Tried a merge of it on main and adding an account gets stuck on the "Checking incoming server settings" screen for both incoming and outgoing. Testing this with an outlook university account. Settings are correct and it works in Thunderbird. Gmail doesn't work either, client ids are correct. Nothing stands out to me in the logs. I'll try to investigate more later.

Is this going anywhere? MFA/XOAUTH2 has become mandatory with my employer and so I can no longer use k9 mail.

For information, the use of webview for authentication is discouraged by google and could not work anymore in future.
https://developers.googleblog.com/2021/06/upcoming-security-changes-to-googles-oauth-2.0-authorization-endpoint.html
I make it work with https://github.com/openid/AppAuth-Android
If mainteners are interested in adding oauth2, I could do a PR and provide help for the google certification process

As has been mentioned in the corresponding issue (https://github.com/k9mail/k-9/issues/655#issuecomment-1057870347) already, using this authentication method will become mandatory by the end of this month. Therefore, it would be really awesome, if the work on this could be finished by then :rocket:

using this authentication method will become mandatory by the end of this month.

Please read carefully. It says May 30th, not March 31st.

Oops, my bad. Thanks for correcting me. The main argument stands though: if this is not merged in the near future, we'll have a problem with gmail.

Any updates on this topic?

Are there any updates on this topic?

Are there any updates on this topic?

Would you stop repeating yourself and spamming our inboxes, thank you.

@cketti Do you plan to finish #6013 and #6021 before you merge this? If so, do you think this is feasable before the deadline?

@cketti Looking at the commits you are doing: well done. Great work!
Now we are in May and Google's deadline is coming closer. Are the requisites done for merging this feature?

Superseded by #6082
A big thank you to everyone who worked on this :heart:
I was able to copy a few things. Some things I implemented differently.


SSMS Key Mapping Extension Author

Shouldn't this extension say it's from Microsoft and not Kevin? Again not taking away credit from Kevin just optics.

Azure Data Studio Version: Latest and Greatest

@alanrenmsft this is a non-Microsoft extension that Kevin published under his personal account.  In order to be published by Microsoft we'd want to revisit the scenario a bit.  I'll close as "By Design."


Issuing credits to Gisele

Issue 2000000 credits to @giselechou.

 Follow up
On Sunday, 10-Mar-24 05:39:29 UTC by Gov4Git dev
Issued 2e+06 credits to member @giselechou.


Switch to otlp exporter for all OTEL collector

As this is proved working, let's update the example yaml in the main repo doc, update all to otlp.

Which part do you mean? I think we don't have "example yaml" in main repo doc,

I remember we have, as those configurations in e2e testing, and referred from setup doc as examples.

I remember we have, as those configurations in e2e testing, and referred from setup doc as examples.

OK, if you mean configs in E2E, then we have those


sunflower-ofir

Hello,
I wanted to make a flower for my drawing and one of my favorites is a sunflower so i decided to code it.
For the middle of the sunflower i used a spiraling pattern made of two functions who draw arcs in a circle in opposite direction.
For the pedal i used turtle to select 5 points on the outline of each leaf and use them to generate a curve.
Both the amount of pedals and the amount of arcs are chosen randomly from the Fibonacci sequence and the size of each also pedal changes randomly.
Most of my experience coding is in python.
I hope you like my drawing :) i had fun creating it.

i decided to also vary the size of each pedal to try making to flower more realistic

I like how this has seeds but the drawing doesn't seem to be parametric. There should be some parameters to adjust or the ability to run it multiple times and get new flowers.

Hey thanks for you comment, I added 2 new variable that let you adjust the flower size and flower location to help bring more variation.
I hope this addressed your comment

Hey, I made some new changes,
there are now 7 different parameters you can change in order to generate different flowers.
the stem can curve now and you can change the amount/direction/ and thickness using parameters .
the petals and stems are colored and you can control their size/ and the amount they vary with parameters.

This is looking really close. Can you clip the stem so we can't see it in the center?

Fixed the stem in the middle issue.
added new variables that let you control the amount of variation of space between each petal, and arc thickness.
I also added a variable that lets you choose if you want to center colored to make sure it can be turned off if the blot can't draw it.

Nice congrats you've earned your Blot. You can order it here.


haskellPackages.basement: fix build on i686-linux

Description of changes
This package was broken on GHC 9.2+ on 32-bit Linux, because of a known issue with modules no longer exposed by GHC. The patch is taken from here but adapted according to the comments to also support GHC 9.2 (the original PR only supports GHC 9.4)
For ZHF #230712 at the #ZurichZHF hackathon.
Things done

Added a patch to the basement Haskell package which fixes a build error on 32-bit Linux systems - see this Hydra failure

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Oh, and one more thing, could you rebase this on haskell-updates?  We generally ask all haskell-related changes to be merged into haskell-updates.

@ofborg build haskell.packages.ghc92.basement

I'm working on a fix via #240387 which I plan to merge into master later today.

Superseded by #249170.


After update to 4.20.3 webpack configuration schema has changed

Bug report
Hello I had in my package.json
^4.17.2
It auto upgraded to 4.20.3 and then I get the error:
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module.rules[0].exclude should be one of these:
   RegExp | string | function | [(recursive)] | object { and?, exclude?, include?, not?, or?, test? } | [RegExp | string | function | [(recursive)] | object { and?, exclude?, include?, not?, or?, test? }]
   -> One or multiple rule conditions
   Details:
    * configuration.module.rules[0].exclude should be an instance of RegExp
    * configuration.module.rules[0].exclude should be a string.
    * configuration.module.rules[0].exclude should be an instance of function
    * configuration.module.rules[0].exclude[0] should be an instance of RegExp
    * configuration.module.rules[0].exclude[0]: The provided value "node_modules" is not an absolute path!
    * configuration.module.rules[0].exclude[0] should be an instance of function
    * configuration.module.rules[0].exclude[0] should be an array:
      [RegExp | string | function | [(recursive)] | object { and?, exclude?, include?, not?, or?, test? }]
    * configuration.module.rules[0].exclude[0] should be an object.
    * configuration.module.rules[0].exclude should be an object.
    * configuration.module.rules[0].exclude[0] should be an instance of RegExp
    * configuration.module.rules[0].exclude[0]: The provided value "node_modules" is not an absolute path!
    * configuration.module.rules[0].exclude[0] should be an instance of function
    * configuration.module.rules[0].exclude[0] should be an array:
      [RegExp | string | function | [(recursive)] | object { and?, exclude?, include?, not?, or?, test? }]
    * configuration.module.rules[0].exclude[0] should be an object.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>dist: `cross-env PRODUCTION=true node_modules/.bin/webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

What is the current behavior?
I downgraded to ~4.17.2
I didnt suppose you'd release a breaking change
and such one,
webpack.config.js
relevant part
exclude: ['node_modules']

Duplicate https://github.com/webpack/webpack/issues/8082

exclude: ['node_modules'] is not valid. It has to be either:
exclude: [/node_modules/] or exclude: [path.resolve(__dirname, 'node_modules')]


New offset-x behaviour

Until version 2.0 'offset_x = N' moved the panel N pixels from the left border of the screen. This allowed me to have 3 panels on top that looked like that: |_***_***********_***_ |,
Since version 2.0 new 'offset-x = N' moves the panel from the both sides of the screen at the same time, making my setup impossible to implement with the lemonbuddy.
My previols config of offset 20; panel 500; offset  540; panel 1480; offset 2040; panel 500 results in unusable middle panel and  an ''error: Failed to setup bar renderer: Resulting bar width is out of bounds' error for the right one.
Can you revert the change to the 'offset-x' behaviour or define offsets from the left and right separately?

Hi and thanks for reporting the issue.
This wasn't intended and I will revert to the old offset behaviour.


Images are not loading on iOS using SvgFromUri or SvgUri

Bug
Images are not loading using SvgFromUri or SvgUri on iOS. Android works fine.

Environment info
Run react-native info in your terminal and copy the results here. Also, include the precise version number of this library that you are using in the project
React native info output:
 System:
    OS: macOS 13.2
    CPU: (8) arm64 Apple M1
    Memory: 86.50 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.5.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.3.1 - /opt/homebrew/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 31, 33, 33
      Build Tools: 30.0.3, 31.0.0, 33.0.1
      System Images: android-33 | Android TV ARM 64 v8a, android-33 | Google TV ARM 64 v8a, android-33 | Google APIs ARM 64 v8a, android-33 | Google Play ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 17.0.6 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.0.0 => 18.0.0
    react-native: ^0.70.1 => 0.70.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: ^13.1.0
Steps To Reproduce
Simply import a SVG image from a URL.
This is the image: https://storagebekagm.blob.core.windows.net/app/avatars/Judge.svg
Describe what you expected to happen:

Image would show both in iOS and Android

Short, Self Contained, Correct (Compilable), Example
<SvgFromUri
            width={'30%'}
            height={'100%'}
            uri={urlToImage}
          />

Can you provide a simple reproduction of the issue? It would be easier to work on it then.

@WoLewicki all I did was use the component with the URL I provided on the issue. That's all I'm doing.

It also happens to me, some of urls not loaded on iOS,
       "react-native-svg": "^12.1.1",         "react": "^17.0.2",         "react-native": "^0.68.2"
example URL: https://cdn-staging.arabyads.com/boostiny-dev/categories/Food.svg

any solution ?

Did you get an error? When I try those examples I get [TypeError: Network request failed]. Is it the same with you?

@WoLewicki i got no errors.
sometimes the image would show up inverted and in a grid-like layout as well. for the moment we converted all remote svg images to png and used the default react-native Image component, which worked just fine.

So should we close this issue then? I am not sure what should we do with it.

I had the same problem yesterday. Update to version<EMAIL_ADDRESS>and it will work.

I am facing these issue in android getting [TypeError: Network request failed] as a result.

Hello @ankitk-nimblechapps,
Can you provide a simple reproduction of the issue?


Will this eventually allow custom fonts?

I'm curious if this app will ever allow custom fonts besides Lucida Grande? Is there any documentation on how to port fonts for macOS Sierra? I ported fonts before for iOS and wouldn't mind doing the hard work myself, not being able to use my own font in Sierra is why I'm sticking with Yosmite for the time being.

+1

+<IP_ADDRESS>.000.000.000

+<IP_ADDRESS>.000.000.000 + 1

I hear everyone loud and clear!
The ability to choose any custom font (such as Comic Sans!) as your Mac's system font is indeed in the works. No ETAs yet.

@HiKay How to modify?

Glad to see this happening!

Comic Sans, out of respect, should be the only one that's not available ;)

Any update? Hoping the same method will work on High Sierra

Just subscribed to this thread, totally wanna see support for custom fonts as well! Thanks for all the hard work!

Another font alternative here, https://github.com/jenskutilek/FiraSystemFontReplacement

I'm still investigating in the best way to allow custom font choices. For now, the latest version of macOSLucidaGrande (2017.11.10) has added support for macOS High Sierra and includes an updated UI for font switching.
Download macOSLucidaGrande for macOS High Sierra (2017.11.10)

I know you said no ETAs on this, but it's been a year since then. Any update on this?


support listening ipv6 address

Is your enhancement related to a problem? Please describe.

Currently, we only support listening ipv4 address in dual stack, failed to start with a ipv6 address.
Describe the solution you'd like

Describe alternatives you've considered

Additional context

verify --bind-address="ipv6", print a log: serving https on "ipv6" by "tcp".
verify --bind-address="ipv4", print a log: serving https on "ipv4" by "tcp".
verify --bind-address="ipv6" and --bind-with-dual-stack=false, print a log: serving https on "ipv6" by "tcp6".
verify --bind-address="ipv4" and --bind-with-dual-stack=false, print a log: serving https on "ipv4" by "tcp4".

Environment

Walrus version: main 7dddda0f4b8d278b4731528af87dbf93f8a17d97

Test Result: pass

--bind-address="ipv6":

2023-09-07T02:33:12.103Z	I	api	serving https on "[2001:db8:2::123]:443" by "tcp"
2023-09-07T02:33:12.103Z	I	api	serving http on "[2001:db8:2::123]:80" by "tcp"

root@9aec7df7a6a1:/# curl -k https://[2001:db8:2::123]:443
<!doctype html><meta charset="UTF-8"/><meta http-equiv="Cache-Control" content="no-cache, no-store must-revalidate"/><meta http-equiv="Pragma" content="no-cache"/><meta http-equiv="Expires" content="0"/><link rel="shortcut icon" type="image/x-icon" href="https://walrus-ui-1303613262.cos.ap-guangzhou.myqcloud.com/latest/assets/favicon.78a06b13.ico"><meta name="viewport" content="width=device-width,initial-scale=1"/><title>Walrus</title><link rel="modulepreload" crossorigin href="https://walrus-ui-1303613262.cos.ap-guangzhou.myqcloud.com/latest/assets/arco.f72cc0b6.js"><link rel="modulepreload" crossorigin href="https://walrus-ui-1303613262.cos.ap-guangzhou.myqcloud.com/latest/assets/vue.eaa04ebd.js"><link rel="modulepreload" crossorigin href="https://walrus-ui-1303613262.cos.ap-guangzhou.myqcloud.com/latest/assets/chart.ec082fa7.js"><link rel="stylesheet" href="https://walrus-ui-1303613262.cos.ap-guangzhou.myqcloud.com/latest/assets/index.5c6ba12d.css">

r

--bind-address="ipv4":

2023-09-07T02:40:10.505Z	I	api	serving https on "<IP_ADDRESS>:443" by "tcp"
2023-09-07T02:40:10.505Z	I	api	serving http on "<IP_ADDRESS>:80" by "tcp"

--bind-address="ipv6" and --bind-with-dual-stack=false: walrus can only be accessed via ipv6 address in this case.

2023-09-07T02:41:13.903Z	I	api	serving https on "[::]:443" by "tcp6"
2023-09-07T02:41:13.903Z	I	api	serving http on "[::]:80" by "tcp6"

--bind-address="ipv4" and --bind-with-dual-stack=false: walrus can only be accessed via ipv4 address in this case.

2023-09-07T02:47:51.318Z	I	api	serving https on "<IP_ADDRESS>:443" by "tcp4"
2023-09-07T02:47:51.318Z	I	api	serving http on "<IP_ADDRESS>:80" by "tcp4"


haproxy drain issues

Rancher versions:
rancher/server: v1.6.14
rancher/agent: v1.2.9
Infrastructure Stack versions:
healthcheck: v0.3.3-1
ipsec: v0.2.2
network-services: v0.2.8
scheduler: v0.8.3
Docker version: (docker version,docker info preferred)
1.12.6
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Ubuntu 16.04.1 LTS (4.4.0)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
aws
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Deploy a load balancer (with connection draining enabled) fronting two services.
send traffic to both services
upgrade one of the two services. (service one in this example)

Results:

service1 client does gets a:
HTTP/1.0 503 Service Unavailable
service2 client can see a blip as well:
curl: (56) Recv failure: Connection reset by peer

docker-compose.yml for test stack
version: '2'
services:
  service2:
    image: sangeetha/testhostrouting
    environment:
      asd: dddd
    stdin_open: true
    tty: true
    labels:
      io.rancher.container.pull_image: always
      svc: service2
  service1:
    image: sangeetha/testhostrouting
    environment:
      asd: '123'
    stdin_open: true
    tty: true
    labels:
      io.rancher.container.pull_image: always
      svc: service1
  lbme:
    image: rancher/lb-service-haproxy:v0.7.15
    ports:
    - 80:80/tcp
    labels:
      io.rancher.container.agent.role: environmentAdmin,agent
      io.rancher.container.agent_service.drain_provider: 'true'
      io.rancher.container.create_agent: 'true'

rancher-compose.yml for test stack
version: '2'
services:
  service2:
    scale: 1
    start_on_create: true
    drain_timeout_ms: 10000
  service1:
    scale: 1
    start_on_create: true
    drain_timeout_ms: 10000
  lbme:
    scale: 1
    start_on_create: true
    lb_config:
      certs: []
      config: |-
        defaults
        log <IP_ADDRESS>:8514 local0 debug
      port_rules:
      - hostname: service1.ahmad.rancher.space
        path: ''
        priority: 6
        protocol: http
        selector: svc=service1
        source_port: 80
        target_port: 80
      - hostname: service2.ahmad.rancher.space
        path: ''
        priority: 7
        protocol: http
        selector: svc=service2
        source_port: 80
        target_port: 80
    health_check:
      healthy_threshold: 2
      response_timeout: 2000
      port: 42
      unhealthy_threshold: 3
      initializing_timeout: 60000
      interval: 2000
      reinitializing_timeout: 60000

super awesome test client:
while true; do curl -i --header "Host: fqdn" http://<ip_of_host>/name.html ; done
Expected Result
No connection blips on either side.
*edited to enable drain settings on services as well as lb

curl: (56) Recv failure: Connection reset by peer```

Reading haproxy 1.8 feature, it seems like the error service2 receives above can be resolved by haproxy 1.8

However it will be still possible to get a 503 for service1
(when during upgrade we stop the backend container, haproxy's reload wont help here when the backend suddenly goes down)

```for service1, to not receive the 503's we will still need:
1) deploy service with scale>1 and upgrade in batches, possibly with start-before-stop
2) Also have our drain feature for services holding connections long```

@aemneina , I have not been able to reproduce this issue when testing with latest 1.6 build and haproxy version - rancher/lb-service-haproxy:v0.7.15
In above mentioned scenario, we do see the "503 Service Unavailable" error for the time when service1 is being upgraded when LB is accessing service1 instances which is expected.
I do not see the LB url accessing service2 instances have any issues . They continue to get to "200 OK" response when service1 is being upgraded.
Also tried the same use case with rancher/lb-service-haproxy:v0.9.0 which is the latest LB version.
We see the same behavior with this Lb version as well.


Input stream seekable requirement

"input stream must be seekable" requirement can be removed by maintatining a small in-memory window. This affects both reader and writer.

Unfortunately for reading we can't stream because file metadata is at the end of the file (


Definition of primitive type

This page covers the IsPrimitive property for types, but I haven't been able to find a definition anywhere of what a primitive type is. As far as I can tell primitive types are the value types built into .Net. Structs and Enums aren't primitive types (but are value types) as they can be user defined.
There was this discussion, that says that 'primitive' isn't defined in the specification, but there must be a reason why the types listed on this page are deemed primitive.
This site describes primitives as the main built-in types, but string, object, aren't primitive as per the list on the IsPrimitive page, but maybe this definition isn't specific to value types.
Is there a definition, and can it be added to this page, and maybe else where in the msdn documentation?
Here's some more links:
This page mentions simple types, which seems to be the same as primitive types, but there is once again no definition of what a simple type is other than the list of types.
Here's another page that talks about primitive types with respect to both C# and Java.

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

ID: dffb41b0-35d3-6ddc-7bfe-c162d1e32d45
Version Independent ID: 51569306-3108-5d27-466e-44aa6acb3514
Content: Type.IsPrimitive Property (System)
Content Source: xml/System/Type.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for pointing out our failure to define primitive, @robertlarkins.
A simple type (in C#) is the same as a primitive type (in .NET). While the CLI specification does not define primitive type, the C# specification does define simple type. A simple type is one of a predefined set of struct types that are identified by the compiler through reserved words. That is, a simple type is predefined type recognized by the language compiler that corresponds directly to a .NET type.
Object isn't a primitive type since it's a reference type. String isn't a primitive type both because it consists of cone or more Char instances (which are a primitive type) and because it's a reference type.
We'll add this issue to the backlog as well as to the Community Contributor's project,

Thanks for the description. By this definition is an enum not a simple type because you declare what types their members are (the default being int)?
Also, from the spec (9.3.5) it says

Most simple types permit values to be created by writing literals

which of the listed simple types can't be assigned by a literal?

Yes. An enum is not a primitive, since it has multiple fields that themselves are primitives.
The values of al the simple types in both C# and Visual Basic can be defined by using literal values, in a few cases along with a type identifier, as in float value = 12.3f; or with a special syntax, as in char ch = 'A';


Installation issue with Tensorflow

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 10
TensorFlow version: 2.2
Python version: 3.7
Installed using virtualenv? pip? conda?: pip
I have freezed a Tkinter-using GUI Python 3.7 app with cx_Freeze.On my laptop, the app works perfectly. But when I try on a laptop that doesn't have python, I have this error:

Is it possible to automatically install Microscoft C 2015 when the application is installed?

@Elona-marti
Can you please see link1 and link2 and see if it helps you.
This issue is more related to windows and cx_freeze .
This question is better asked on StackOverflow since it is not a bug or feature request related to Tensorflow. There is also a larger community that reads questions there and provide better and faster support for such issues. Thanks!

@ravikyram
If you don't have the answer to a question, don't answer in a vacuum. My application works without tensorflow, it is the only library that poses a problem.

Did you install MSVC 2019?
Also see https://www.tensorflow.org/install/pip#system-requirements


Funds Not Appearing After 30+ Hours

Funds Not Appearing After 24 Hours? Please release my funds so I can purchase more MonyX asap, thanks.
https://cl.ly/pMDo

@VM4ROI can you please post here the tx id?

@VM4ROI anyway we're still processing the backlog, it should be deposited soon.


docs: howto_ims.md: include disabling SQN without explanation why this is even needed.

Feature Request
Summary
https://github.com/omnt/OpenMobileNetworkToolkit/blob/main/docs/howto_ims.md
describes how to disable SQN checking.
However this is only needed if your core network doesn't contain a common HSS.
E.g. in early howtos this was required, because the howto required to have 2 HSS which doesn't share the
sequence numbers (e.g. open5gs-hss + pyhss).
However it is now possible to use either open5gs-hss or pyhss for both, the IMS authentication and the LTE core network authentication.
It would be great to mention the reason and describe this step doesn't hurt, but is only required if the core network uses a split brain HSS.

Any documentation recommending disabling a security feature should also give an explanation of the consequences of doing so, warn against doing it without fully understanding the consequences, and reference related documentation/publications about said security mechanism.
SQN checking protects against replay attacks. Disabling that check consequently exposes you to them.

Thank you both for the comments. @errdemk can i ask you to update the documentation?


SAK-41639 Fix remove peer attachment on Edge

This looks better but I haven't tested. Did you test it in multiple browsers to make sure it's still working? Thanks for the fix!

Yes, we've found quite a bit of similar issues lately, it's been causing problems on some versions of Edge (and sometimes also Firefox it seems).


Remove the kotlin-dsl plugin

Closes https://github.com/Yelp/swagger-gradle-codegen/issues/108
It turns out the kotlin-dsl plugin embeds code that's using Gradle 6.1 classes while we shouldn't really need this. Remove it and use the plain java-gradle-plugin instead.
Also add some checks and tests about Gradle version.

@martinbonnin I would personally prefer to use kotlin-dsl as far as possile.

+1

@macisamuele no problem if you want to keep it but as you said, it's bringing a downside and I don't see the upside. The amount of code is almost similar and it might bring things like HasImplicitReceiver to allow to use this instead of it but this almost sounds like a downside too. For someone used to Kotlin, this transformation looks a bit magic.
Or are there more advantages ?

Or are there more advantages ?

kotlin-dsl plugin allows us to use the precompiled plugins:
https://docs.gradle.org/current/userguide/kotlin_dsl.html#kotdsl:precompiled_plugins
(They actually added a note that covers exactly our scenario)
That is convenient as it simplifies our Gradle setup. I'll try to stick to it as long as it's possible. Although, I don't have a really strong opinion on this, we could even drop if you have a strong argument @martinbonnin 👍

Following up the discussions we had on Slack here
We decided for replacing kotlin-dsl plugin with java-gradle-plugin for the reasons aforementioned by @martinbonnin.
I'm merging this and will prepare an upcoming release soon 👍


0.5.0 compat

I am using this plugin in a project, and attempting to upgrade that project to bevy 0.5.0. It looks like the definition of a plugin has changed. I am happy to spend the time to submit a fix, if that is welcome :)

Hey, this crate (from version 0.3.0 onwards) actually is 0.5 compatible.  I'm using it with 0.5 now!  Would you be able to produce an example of what doesn't work?
https://github.com/Toqozz/bevy_debug_lines/blob/fd43df58d00b7f57b9d0b0632a1e4df31dad77cc/Cargo.toml#L20

Ah you are completely right, I should have looked for a new version. I think I am seeing a problem with the new version; I will file a separate issue after I've investigated a bit.

Please do, thank you.

Ah the other issue was due to the new duration paramater. I have updated my code and now everything works as expected. Thanks for everything!

Cool!  Sorry about the breaking change!


Metatags: add 'module' field in 'sys_objects_metatags' table.

Update Channels module. It should use data from this new module field instead of metatag object name to get module instance and necessary info out of it. May be module instance can be replaced with some service call.

implemented in #1661


Add domain policy

Fixes https://github.com/aspnet/Routing/issues/825
Note that this is based on https://github.com/aspnet/Routing/pull/799

We're merging Routing today into aspnet/AspNetCore. If you can merge this in the next 30 minutes or so, we can bring this along. Otherwise, you'll have to open a new PR against https://github.com/aspnet/AspNetCore.


add VentoyPlugson 64bit

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

/verify

Please read the Contributing Guide then tick the checkbox.

#10514


[KOGITO-2643] upgrade testcontainers version and add dependency management for the mongodb module

Jira: https://issues.redhat.com/browse/KOGITO-2643
The mongodb module was introduced to testcontainers since version 1.14.2.
So upgrade the testcontainers version and add new dependency management for the mongodb module.
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

This change is required by #591 and https://github.com/kiegroup/kogito-apps/pull/293

jenkins please retest this

jenkins please retest this


Doi redux

Attempt 2 to get the DOI service integrated, following the rebranding changes

Updated proxy to pass /journal requests
Update pass-auth to accept /journal requests, authenticate, and forward them to pass-core
Update pass-ui to use new env var vals
Changes were made in both demo.yml local env and eclipse-pass.base deployed envs

Weird, the UI should no longer be mocking the DOI service calls. My local testing shows different journals for different DOIs. Can you try fully refreshing the Docker env?
./demo.sh down -v && docker system prune -af
./demo.sh pull && ./demo.sh up -d && ./demo.sh logs -f

I've been using these two DOIs for local testing:
10.4137/CMC.S38446
10.1039/c7an01256j

ah, my mistake - i think it is in fact operating correctly, i misunderstood the message in the green box - we're good!


Error: [vite-node] Failed to load @remix-run/node/globals when trying to run tests

What version of Remix are you using?
1.6.5
Steps to Reproduce

Have "@remix-run/node": "1.6.5" set in your package.json dependencies
Have "vitest": "^0.12.8" set in your package.json dependencies
Run npx vitest

Expected Behavior
runs tests
Actual Behavior
Will throw error Error: [vite-node] Failed to load @remix-run/node/globals
When I change the version back down to 1.6.0 it is no longer a problem. It may be a reccurence of a Vitest issue as per this issue.

I ran into this issue as well with vitest, and fixed by removing /globals from @remix-run/node/globals
Before import { installGlobals } from '@remix-run/node/globals'
After import { installGlobals } from '@remix-run/node'
https://remix.run/docs/en/v1/other-api/node

@iamvictorli Perfect!


WIP: Create k3d templates for devs

Background
This is a continuation of this PR: https://github.com/medic/cht-core/pull/6876
Goal
This PR creates a dev environment that is similar to our medic-hosted kubernetes environment. The purpose of this environment is to allow devs to launch a local version of architecture v3, so they can understand the changes required for horti to continue functioning as an upgrade service inside arch v3.
We decided these templates belong in cht-infrastructure instead of cht-core as these are only temporarily required for the horti rewrite. We will discuss about merging our infrastructure deployment scenarios (medic-hosted and self-hosted)  into one solution (k3d) at a later release time.
Acceptance Criteria
TBD

Some errors,
$ kubectl -n cht get pods
NAME                                      READY   STATUS             RESTARTS   AGE
dev-v3-couchdb-85cdbd6b8f-f8z88           0/1     Pending            0          7s
dev-v3-medic-sentinel-5c69f759d-78rsx     1/1     Running            0          7s
dev-v3-horticulturalist-9f56cf64f-p2lzj   1/1     Running            0          7s
dev-v3-medic-api-5c9c556444-qh4sk         1/1     Running            0          7s
dev-v3-haproxy-79cfbfc56b-nd95j           0/1     ErrImagePull       0          7s
dev-v3-nginx-7d9d5b68f5-ckfdb             0/1     CrashLoopBackOff   1          7s

HAProxy
Some of the tags are wrong. haproxy only goes up to 1.17 in hub.docker.com
https://github.com/medic/cht-infrastructure/blob/b7f6b1f256c6f544b321d829d00e067ebd51efa8/arch-v3/k3d/dev-v3-haproxy-deployment.yaml#L25
I'm not sure how the images are built, but the latest tag is also behind the most rc-1.17 tag.
NGINX
Perhaps using the k8s ingress controller would be better https://kubernetes.github.io/ingress-nginx/user-guide/tls/. Might eliminate the need for a custom container.


[SEO Optimization] Huge LCP(Largest Content Paint) on Full Static rendering html with v-html

Versions

nuxt: v2.13.0
node: v12.18.0
target: static
mode: universal

Reproduction
We've created a blank rep with different ways to render the html to showcase the problem. IMO this is critical because it's super hard to optimize websites on mobile and get a rating over 90.
Sandbox: https://admiring-cray-777be5.netlify.app/
Rep: https://github.com/made2web/dummy

Additional Details

https://admiring-cray-777be5.netlify.app/ -> Simple component
https://admiring-cray-777be5.netlify.app/functional/ -> Functional component
https://admiring-cray-777be5.netlify.app/static -> With the html directly on the component (this is not a solution)
https://admiring-cray-777be5.netlify.app/content/ -> Using nuxt-content component
https://admiring-cray-777be5.netlify.app/lazy/ -> Using lazy-component
https://admiring-cray-777be5.netlify.app/static-render/ -> Using Nuxt Static Render Package (we lose the nuxt-link ability)

Steps to reproduce
Main issue is that when we try render a bigger html node or multiple nodes when the payload takes action it's counting like a new writting.
We've managed to get better results with nuxt static render package, but then the nuxt-link function doesn't work.
Using Page Speed Insights (mobile) and Performance on Dev Tools you can see that despite the content is there from the beggining, both tools consider that the LCP is way latter than it really is.
What is Expected?
No content as changed, so we don't need to hydration/write again. Payload should understand that, specially on the above the fold content.
What is actually happening?
Payload is writting again the content. It's taking 2/3 times longer than it should.
Simple Component
Page Speed Insights: https://mrkr.io/s/5f1ff6b9711cd17c08c51a73/0
Dev Tools: https://mrkr.io/s/5f1ff8fae713a45033ee018a/0
Functional Component
Page Speed Insights: https://mrkr.io/s/5f1ff744d4c6e47c65975be9/0
Dev Tools: https://mrkr.io/s/5f1ff8bd123b4b7c52b2ee9b/0
Static Component (no v-html)
Page Speed Insights:  https://mrkr.io/s/5f1ff753123b4b7c52b2ee93/0
Dev Tools: https://mrkr.io/s/5f1ff8cad4c6e47c65975bed/0
Nuxt Content Component
Page Speed Insights: https://mrkr.io/s/5f1ff7662e67e07c07fb35d6/0
Dev Tools: https://mrkr.io/s/5f1ff8d7d4c6e47c65975bee/0
Lazy Component
Page Speed Insights: https://mrkr.io/s/5f1ff7cbb418f75038d81a7e/0
Dev Tools: https://mrkr.io/s/5f1ff8cadcdbf37b8d71b41c/0
Static Render
Page Speed Insights: https://mrkr.io/s/5f1ff7d7e713a45033ee0183/0
Dev Tools: https://mrkr.io/s/5f1ff8ca711cd17c08c51a7d/0
Thanks in advance and congrats for the amazing work!

The reflow is caused by the fact that the CSS styles for container, title, subtitle and links are not being injected into the HTML on /content.

@danielroe i've updated the rep and removing all the css made nuxt-content work like expected!
But still, shouldn't v-html achive the same result? If we want to use an external API like Strapi or Directus we can't use in an easy way the nuxt-content, because we would need to generate a lot of json and md files.


Switch from zip to zippy

By using zippy instead of zip, the external zlib1 file dependency is no longer needed
I have tested that uncompress is called with the advanced.nim example and it seemed to work correctly

I will merge when I implement voice.

Since voice is taking longer I will merge soon atm.


Feature: Support static env config from file

What are you trying to do?
Add missing implementation of docker run --env-file <file> ...
Why should it be done this way?
Users should not be required to load each env var manually if they have an env file.
(this is the common case for quite a few services)
For example, if I would have an Redis service with some config:
# Redis Bike Commpany Demo Application: Example .env file.
REDIS_URL=redis://localhost:6379/?decode_responses=True
BIKE_INDEX_NAME="idx:bikes"
STORE_INDEX_NAME="idx:stores"
REDIS_KEY_BASE="redisbikeco"
BIKE_KEY_BASE="redisbikeco:bike"
STORE_KEY_BASE="redisbikeco:store"
FLASK_ENV=development

We would now be able to load it without evoking with_env 7 times + keeping a single source of truth for the env config.
Other references:
Docker official Docs

@Tranquility2 wanna work on this together?

@biniyam69 checkout https://github.com/testcontainers/testcontainers-python/pull/684 if you have any comment/ideas/remarks I'll be happy to update.


Update community_connectors.json

Coverage remained the same at 98.913% when pulling 6e76e2679b59f1a09e97824a5a46dfb443a4fdb9 on collinsteele:patch-1 into 9038a426422b30ed5c8a0407ad39deccc02cd0fd on tableau:master.


Microsoft Graph Attaching Power BI Tab is now disabled

[My code used to hang a  Power BI tab in every Team but now after this update now I can not do that. I am have to manually go and set up power tab on each and every teams]

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

ID: dd9c7dbe-8b03-52a9-b299-936856c89ba8
Version Independent ID: f4496816-b872-4541-4ad9-f3b323b8917f
Content: Collaborate in Microsoft Teams with Power BI - Power BI
Content Source: powerbi-docs/collaborate-share/service-embed-report-microsoft-teams.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @LukaszPawlowski-MS
Microsoft Alias: lukaszp

Thanks for the feedback, @ashoksubedi1. I'm assigning the issue to the author.

Hi, @ashoksubedi1 -- I've checked with folks. They say: "I looked at the update and the change shouldn't break creating PowerBI Tab with Graph." They ask that you open a support ticket so we can investigate why it's not working.
https://powerbi.microsoft.com/en-us/support/
Thanks!


Add JIT payment filter to list_payments

Closes #702. Let me know if you believe the filter should be part of the ListPaymentsRequest, or if it's better this way.
Edit: Since the PaymentTypeFilter is expected to match multiple cases (Sent, ClosedChannel etc.), I opted to move it inside the ListPaymentsRequest. If there are any suggestions on the naming, I'll gladly accept them. To note that, when specifying is_jit, the type filters are overridden by default, and will only match received payments (as there cannot be any other kind for jit matches)

As a side note, there seems to be an issue in RN CI where the ktlint version used fluctuates between 1.0.1 and 1.1.1 depending on the instance, resulting in the same code passing sometimes and failing others.

Let me know if you believe the filter should be part of the ListPaymentsRequest, or if it's better this way.

My main critique to the new ListPaymentsRequest field is that it basically overrides the filters, which can confuse the user.
Since this is a separate category of payments, IMO the cleanest way would be to add a new PaymentType:
pub enum PaymentType {
    Sent,
    Received,
    ClosedChannel,
    OpenChannelFee // or JitPayment, etc
}

and a corresponding PaymentTypeFilter.
Then ListPaymentsRequest wouldn't need a new field.
What do you think?

@ok300 It previously worked that way, but since the filters are supposed to match multiple cases (e.g. when a user looks for Sent and ReceivedJIT, they are expecting payments which match both, not just one), I opted for splitting it up. That way the user knows that, when is_jit is specified, the only results they can expect are only received payments.

I see, thanks, I wasn't aware of this previous version.

when a user looks for Sent and ReceivedJIT, they are expecting payments which match both, not just one

Match both = match either of them, right? Isn't that how the filter list is supposed to work? I may be missing something, but I don't see where the problem with that is.

After some thought I decided to opt for the alternative proposed by @roeierez, leaving the payer_bolt11 as part of the payment details and letting the user handle the filtering of such payments themselves.


Issues with Helix

We experienced an issue with Helix on 8/28 that prevented systems from provisioning correctly. This issue is for us to track the RCA associated with this interruption in service.

duplicate of issue https://github.com/dotnet/dnceng/issues/3900


Test and add to scripts

[x] http://www.sqlservercentral.com/blogs/sqlrnnr/2017/10/27/drop-that-schema/
[x] http://nedotter.com/archive/2017/10/in-memory-oltp-diagnostic-script/

Via https://github.com/ktaranov/sqlserver-kit/commit/26abde1a602d671728026f55eaecc46035655660