Second Swiper initiates 2 instances of itself to the variable

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: Swiper 4.3.3

Platform/Target and Browser Versions: macOS Chrome

What you did
I'm initiating a second swiper like that:
  var swiperTwo = new Swiper('.swiper-container-kieztour', {
    direction: 'vertical',
    slidesPerView: 'auto',
    init: false,
    wrapperClass: 'swiper-wrapper-kieztour',
    slideClass: 'swiper-slide-kieztour',
    slideActiveClass: 'swiper-slide-kieztour-active',
    centeredSlides: true,
    // slidesOffsetAfter: 120,
    // slidesOffsetBefore: -140,
    // spaceBetween: 30,
  });

Expected Behavior
swiperTwo would hold one instance of the vertical slider.
Actual Behavior
Actually swiperTwo weirdly holds two instances: [t, t]. They are exactly identical from the data inside, but only the seconds instance [1] is linked to the slider visible. (the first one is somehow off and can't be inited)
I'm initiating both sliders at the same time. Without waiting for the first one to be finished. Could it have something to do with that?

It means that you have 2 .swiper-container-kieztour elements on the page

Ouch!
Sorry, for this mistake, you're right.


Added IDisposable to distribution classes.

Per request in #1158, adding IDisposable to all the distribution classes.

Oops! This wasn't the PR I intended to merge...


documentation for building

Hi, Can you provide documentation for building and runing PN531
Thanks

my bad. PN532

Add a Getting Started in README.md.


breaking changes with typst 0.7.0

I didn't find the problem directly in the change log but there are some problems rendering graphs
main.pdf

The place function changed a bit. Should be fixed now, pinning it for some time for people to see the problem.


DCOS-14890: Always keep the http health checks scheme

This PR ensures that the scheme property is always present in the resulting JSON. This fixes cases where the "scheme" property was initially present in the JSON, since the default behaviour was to remove it.
Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[x] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

🥑 👏

Shall we merge it to the release as well?

Yes, yes, yes

@nLight addressed 👍

LGTM 💯  👍  @nLight I am going to merge this for now.


Is it possible to select a different workdir instead of ~/.furyctl ?

It can be a good idea to make the folder customizable. This is a feature request that came from multiple people during testing

--outdir flag feature released on version 0.25.1


ActiveDirectoryDsc.Common: Fix Test-DscPropertyState Failing when Comparing $Null and Arrays

Pull Request (PR) description
This PR fixes the Test-DscPropertyState function in the ActiveDirectoryDsc.Common module so that it correctly handles comparing $null and arrays.
This Pull Request (PR) fixes the following issues

Fixes #513

Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in resource directory README.md.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Conceptual help topic added/updated (cultureFolder\about_ResourceName.help.txt).
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #514 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff          @@
##            dev   #514    +/-   ##
====================================
+ Coverage    98%    98%   +<1%
====================================
  Files        23     23
  Lines      3114   3117     +3
  Branches     10     10
====================================
+ Hits       3070   3073     +3
  Misses       34     34
  Partials     10     10

@X-Guardian Sorry it took so long to review this. Have been a lot of PRs to review over in xWebAdministration for hacktoberfest.

@X-Guardian Thank you for this! Great work! 😃


Initial FLOPs support

This PR adds a new entry into the turnkey_stats file called 'onnx_flops_counter' which holds the total number of FLOPs found in a given ONNX model. It is important to be very specific in how we are defining FLOPs:

1 multiply-accumulate or MAC is a*x + y
2 floating-point operations or FLOPs are a*x + y, i.e., FLOPs == 2 * MACs
There are several repositories that do not make this distinction clearly:

fvcore
flops-counter (reports MACs)
mmcv also has a flop counter where they consider 1 flop a mac.
model-summary (in the readme they call these FLOPs)
etc...

The concern here is that it appears FLOP is used synonymously with MAC, but most understand the ambiguity and comment their code appropriately.

After the latest commit I have verified the following models and will update once I have some transformers added:

All of the 3rd party flops were calculated by using fvcore except for LSTM due to lack of support. I used THOP for the LSTM models but not the others due to inconsistency with THOP (note the issues on their repo including one from yours truly). Both libraries actually calculate MACs and so I simply multiplied by 2 to get a ballpark of FLOPs.
The generic LSTM tests changed various parameters like hidden dim, input dim, bidirectional, and num layers.
Let me know if there are other model candidates to add to the tests. I have a local script that runs the tests and updates the table.


making the website compatible with mobile

Can I get assigned @nilisha-jais to these?

Can you assign me with this issue @nilisha-jais

There are some other issues that are opened related to the same. Please try to find those @theSumeetGithub , @utkarshgoel10


Base64#urlsafe_encode now works as in ruby, fixed #3394

Looks good, thanks! I added a small question.


Remove adding /opt/mssql-tools/bin to PATH in .bash_profile for Ubuntu (maybe other distros too)

The current documentation has the following commands for installing on Ubuntu
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc

This causes problems on Ubuntu because by default, a user does not have ~/.bash_profile, but does have ~/.profile and ~/.bashrc.  Also, by default, ~/.profile loads ~/.bashrc.
Therefore it is only necessary to add to PATH in ~/.bashrc.
Adding to ~/.bash_profile actually causes problems because when it exists, bash stops loading ~/.profile and loads ~/.bash_profile instead.  This causes ~/.bashrc to no longer be loaded automatically and also skips running the other commands in the users' ~/.profile, such as adding $HOME/bin to PATH if it exists.
Please remove the command that creates/modifies ~/.bash_profile -- adding to ~/.bashrc alone is sufficient.
This could very well apply to other distros too.

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

ID: 0fc3da20-7ab2-d20f-4d29-4664d3183b57
Version Independent ID: 986d25d9-5d2e-5154-39ea-3b683faf2264
Content: Install the Microsoft ODBC driver for SQL Server (Linux) - SQL Server
Content Source: docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

@jgilles -- Jesse, thank you for your considered feedback.  I am looking into this article.

The current documentation has the following commands for installing on Ubuntu
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc

This causes problems on Ubuntu because by default, a user does not have ~/.bash_profile, but does have ~/.profile and ~/.bashrc. Also, by default, ~/.profile loads ~/.bashrc.
Therefore it is only necessary to add to PATH in ~/.bashrc.
Adding to ~/.bash_profile actually causes problems because when it exists, bash stops loading ~/.profile and loads ~/.bash_profile instead. This causes ~/.bashrc to no longer be loaded automatically and also skips running the other commands in the users' ~/.profile, such as adding $HOME/bin to PATH if it exists.
Please remove the command that creates/modifies ~/.bash_profile -- adding to ~/.bashrc alone is sufficient.
This could very well apply to other distros too.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0fc3da20-7ab2-d20f-4d29-4664d3183b57
Version Independent ID: 986d25d9-5d2e-5154-39ea-3b683faf2264
Content: Install the Microsoft ODBC driver for SQL Server (Linux) - SQL Server
Content Source: docs/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

Operations assistant


Fix: Reject rule-sets referencing unknown layers

This PR

[x] rejects rule sets referencing unknown layers

💁♂ During the weekend I ran into an issue because I had a typo in a ruleset.

Build failure appears to be unrelated.

Thank you, @localheinz!

Thank you, @smoench!


Pin dependencies in setup.py and separate dev deps

This PR pins the dependencies versions in setup.py. These dependency versions are generated by pip-compile.
This PR separates the dev dependencies into a separate dev.txt file. This file is generated by using the pip-compile command on the dev.in file.
This PR introduces a script to generate the list of dependencies in requirements.txt with  their versions pinned to be copied into the setup.py file.
This PR modifies the push GHA to use dev.txt instead of requirements.txt to install dependencies
Fixes: https://github.com/codecov/codecov-cli/issues/189

could you update README.md to tell folks to run pip install -r dev.txt instead of requirements.txt?
(i'm reading PRs here and there to ramp up, don't mind me)

Not sure I follow the need for requirements.in/txt vs dev.in/txt.  Can what you currently have in dev.in be our requirements.in?  When would we need to run generate_reqs.py again in the future?  I was thinking we'd just update what's in setup.py since those should only be direct dependencies (not transitive dependencies).  Ideally those versions in setup.py would also be looser (i.e. something like click==8.1.x).

Not sure I follow the need for requirements.in/txt vs dev.in/txt. Can what you currently have in dev.in be our requirements.in? When would we need to run generate_reqs.py again in the future? I was thinking we'd just update what's in setup.py since those should only be direct dependencies (not transitive dependencies). Ideally those versions in setup.py would also be looser (i.e. something like click==8.1.x).

My thought process was that since we are using pip-compile for requirements.txt that the deps in setup.py should match that. The reason for having dev.in and requirements.in is because of the use of pip-compile. generate_reqs.py is there to take the output of pip-compile that is the .txt file and make it easy to copy that into setup.py. I guess I thought the idea was to take whatever we currently have in requirements.txt and put that into setup.py. I think I get now that we want just loose version requirements that match up loosely with what we currently have in requirements.txt

Looks good.  I think it'd still make sense to replace some of the dependencies in requirements.in with . to reference those specified in setup.py


[ENH] Lower Bounding Distances for SAX and SFA

What does this implement/fix? Explain your changes.
This implements four Euclidean lower bounding distances - two for SFA and two for SAX:

dft_sfa_mindist: compare dft to sfa words
paa_sax_mindist: compare paa to sax words
sax_mindst: compare two sax words
sfa_mindst: compare two sfa words

These can be used for indexing.
Further changes:

The PR adds a test case, too.
It fixes two bugs in PAA/SAX for z-normalization with 0 std (dividing my 0) and for segments of size 0.

Great ! An alternative to squeeze, if you are sure that there is only 1D might be to use ravel, which should be supported.

Great ! An alternative to squeeze, if you are sure that there is only 1D with "empty" subdimensions might be to use flatten or ravel, which should both be supported.

ravel() and flatten() would turn any 2d array to a 1d array, right? For this to work, the input must be 1d with one empty subdimension. Otherwise, I kind of break the logic. Might be better to just leave it and throw the ValueError.

Didn't find much to say on the distance themselves, looks good to me. Some comment on possible typos.
Additionally, more out of curiosity than for this PR, would a multivariate version of the lower bounds where you consider each channel independently and sum the result work, as we are working with (squared) Euclidean distance ?

Very Interesting research question! I am not aware of a multivariate lower bounding distance measure. Yet, as you suggest, it should be possible to transform each channel ro SFA/SAX and sum up the lower bounds on each channel.


[FIX] Sublist: Committed solution in the exercise!

duh, committed the solution in the exercise. removed...

I should also have caught that!


nmodl::parser::location class is defined more than once

I wanted to extend the format library to deal with nmodl::parser::location as instructed here but realized that every bison parser in NMODL has its owned location.hh file:

${CMAKE_BINARY_DIR}/src/parser/diffeq/location.hh
${CMAKE_BINARY_DIR}/src/parser/nmodl/location.hh
${CMAKE_BINARY_DIR}/src/parser/unit/location.hh

Each of them defines a location class, all in the same nmodl::parser namespace. There should be either one single nmodl::parser::location class used by all parsers or they should all be declared in a dedicated namespace. This is an issue that should be addressed before considering extending the format to deal with nmodl::parser::location.
Originally posted by @tristan0x in https://github.com/BlueBrain/nmodl/pull/372#discussion_r463422929

@tristan0x : I had trouble with this as well! Last time I checked this (~18 months ago) and it was not possible to share location.hh from different parsers. I would be curious to know if you have / find any elegant solution.


All the configs are down in IRAN

I've been trying to establish a connection with configs for a few days. Since 04 Dec 2024, nearly all the configs have been down.
*- Real delay test shows no connection or ping speed (-1)
I have tried all the subscriptions, but they are all down. If anyone has a solution or updates about this issue, please comment with your insights or solutions.


Dropdown without jQuery

Hey...
This is an interim PR.    There shouldn't be any bugs or cruft, though.
The rewrite thus far is >600 lines in the Dropdown and >700 lines in Dropdown tests.  I want to get some eyes and feedback on the functionality and approach thus far before cleaning up and abstracting things.
The multiple feature will be added in the next Dropdown PR.
Areas of concern
These are the areas to watch and comment on.    They've been added as TODOs to the main PR #206.
Events
We have two event systems at play, React synthetic events and real DOM events.  You'll see lots of document.add/removeEventListener calls.  This is necessary for keyboard and mouse events that are dispatched on the document.  Example, clicking outside the dropdown or pressing escape to close an open dropdown.  Ideally, we'll write a clean abstraction for handling these.  Considering that we need to:

prevent duplicate handlers
cleanup all events on unmount
provide once() functionality
add/remove events at any time (not just lifecycle methods)

Debug / Logging
Currently, nearly every method has a console.debug() when called and a console.log() for any relevant debugging data.  This would be pulled into an actual debug util.  Consider:

debug module
removal in production code
runtime flag to enable/disable by module

Spreading Consumer Props
Stardust components should spread the consumer's props.  We've experimented with a couple patterns for doing this effectively, though they each beak down.  Consider:

every prop not defined in propTypes (public interface) is a consumer prop
propTypes may be stripped from production code in the future
using ...props in render() isn't sufficient when breaking down many render methods

If it weren't for stripping propTypes in production we may be able to naively:
const getConsumerProps = (self) => _.omit(self.props, _.keys(self.constructor.propTypes))

Lots of code in here, but I passed over and nothing other than the required options attribute stood out at me. Sweet looking tests! 🍶


Fix csv writing of timestamps to show timezone.

Which issue does this PR close?
Closes #778
What changes are included in this PR?

Round-trip test of csv writing and reading of timestamps
Fix to csv writer so that timestamps are written out in UTC.

Are there any user-facing changes?
Yes. This changes the behaviour of the csv writer.
// @alamb @bjchambers

@alamb @bjchambers I have made changes to the csv writer according to the proposal.
While doing so, I have noticed what I think is a bug in the temporal utilities in the kernel. Essentially, variations relating to daylight savings are not recognised at the moment. I have a failing test on a branch here. I came up across this issue during this work as and had to implement https://github.com/novemberkilo/arrow-rs/blob/master/arrow/src/compute/kernels/temporal.rs#L98-L110 to correctly derive the offset for a timezone.
I figure I should fix this bug separately -- should I file an issue to describe it and then put up a fix against that? Thanks.

I figure I should fix this bug separately -- should I file an issue to describe it and then put up a fix against that? Thanks.

I think that would make the most sense to me @novemberkilo  -- thanks

Thanks @novemberkilo  -- I plan to review this more carefully hopefully today

Thanks much for the feedback @alamb -- I have reviewed your comments and made changes accordingly.
Something to note, instead of adding Z to indicate UTC, we now consistently use the same format string and show UTC as +00:00

Thanks @alamb - once this is merged I will put up a PR for this https://github.com/apache/arrow-rs/issues/901

I'll plan to merge this tomorrow morning unless anyone else has any comments

Thanks again @novemberkilo


ISO boot: frequent graphics problems

People tend to report they fail to boot unless with nomodeset flag in grub. As modesetting is hardly important during installation, I think this should be the default.
I don't know why this happens. Maybe due to kernel being too old (for the HW in question).

Is this still an issue?

I'm not knowledgeable at all in these things, but it seems possible the issues will get resolved by #8173.

The ISOs now have nomodeset and blacklist the nouveau kernel module (6948c3ab80797770bc584e521b5c5a8ca02b495e).

I assume these problems are gone. Feel free to reopen.


Frontend KYC validation for affiliate application

Users can apply as an affiliate only if they have completed KYC.

you can also apply to be an affiliate even if you already are an affiliate

we need to include an additional validation to only allow accounts that are not currently affiliates to apply.

@xavier506 if we do it in this way, then this is not going to be needed, I mean, that scenario described on the card never gonna happen, is it?


Design circuit for use with Nano Every

Should be able to remove the 74LS20.

Overcome by events (b362454)


Increment the number of failed login attempts atomically in AxesCacheHandler

AxesCacheHandler has a chance to increment failures_since_start badly where multiple worker processes receive many concurrent login attempts during the short period (e.g., DDoS). It requires to use of the atomic counter functionality inherent in the caching mechanism like INCR in Redis, instead of implementing it ourselves:
https://github.com/jazzband/django-axes/blob/ac86d4b2139f632cee972e874984982a9628ab27/axes/handlers/cache.py#L100
Ref. #777.

This would be a very nice improvement if we could implement it in a way that is supported by at least the most common cache backends.
It is worth considering through that the users utilizing the cache handler due to number or volume of requests or DDoS resistance will likely use a specific cache such as Memcached or Redis, which are likely to support atomic incrementation of the cache values.
The Django cache framework does provide a cache.incr method:
https://docs.djangoproject.com/en/3.2/topics/cache/#django.core.caches.cache.incr
This is atomic on select backends which support the atomic incrementation and have implemented the correct logic in the cache layer.

Added 6.x label for reference, can also be implemented in 5.x.

This should be implemented by #1048


Fix the behavior of require_delimiter

Y'know, you could just update #677...

@nabijaczleweli true, but my git-foo isn't up to par, and it was easier to just create a new branch and cherry-pick without having to google :stuck_out_tongue_winking_eye:

@homu r+

:pushpin: Commit 8cd120c has been approved by kbknapp

:hourglass: Testing commit 8cd120c with merge 42d8aba...

:sunny: Test successful - status


Can't use terminal to pod

Describe the bug
When I try to connect to pod - a window with text "Connecting ..." is appear and stuck.
I have tryed to setup another "TERMINAL SHELL PATH" in Preferenses and try with empty field - no changes.
To Reproduce
Steps to reproduce the behavior (in my environment):

Open Lens
Connect to cluster
Choose any pod and click "Pod Shell"
See error

Expected behavior
Obviously - connected shell at pod)
Screenshots

Environment (please complete the following information):

Lens Version: 5.3.3-latest.20211223.1
OS: Windows 10
Installation method (e.g. snap or AppImage in Linux): default - AppData folder. (I have checked path: AppData\Roaming\Lens\binaries\kubectl - have files)

Logs:
I don't understand how get it..
Kubeconfig:
VScode with Kubernetes extension works (including shell to pod) with this config.

Does Lens terminal open properly? And does kubectl exec ... work on Lens terminal?

I'm sorry, I don't know what it was, now it's working. Probably a tough day :)
I will reopen the issue if I find something to show

Does Lens terminal open properly? And does kubectl exec ... work on Lens terminal?

I realise this answer comes a year after the question but for anyone stumbling around trying to fix this I had the same issue.
It turned out (Open)Lens was trying to source a file that did not exist when starting the terminal, ie the invocation command was pre-set to /bin/zsh ~./foo - iirc foo looked valid enough, as in I think it was zshrc but as soon as I just pointed to the shell binary itself at /bin/zsh in the app settings the terminal sprang to life.
You can also edit the relevant config file at ~/Library/Application\ Support/OpenLens/lens-user-store.json (obviously substitute OpenLens with Lens if using the commercial. builds).
Maybe foo had a typo like zsh_rc or something, or maybe the shell expansion wasn't working on the tilde, I don't recall; anyway it wasn't something I'd knowingly touched.
I think this is a macOS specific thing relating to the order of precedence zsh is configured - I vaguely recall reading something odd in that regard a while back - but I could be wrong.

I'm having the same issue on Windows 11 after the latest update to Stable. When I attempt to run shell on pod, i see the Connecting... text just like it was mentioned in the original post.

I'm having the same issue on Windows 11 after the latest update to Stable. When I attempt to run shell on pod, i see the Connecting... text just like it was mentioned in the original post.

does the target pod actually exist?
I had a case when a deployment process was running in the background and after updating the list of pods, a pod with a different identifier appeared in its place.

Yes, this happens on every pod I've tested. Those pods are reported by others as working.

@OndrejKu @Inetov  as a temporary solution I just downgraded to 2023 version
Go to https://api.k8slens.dev/binaries/Lens Setup 2023.9.290703-latest.exe
Or fine the patch you need
https://forums.k8slens.dev/t/lens-2023-9-290703-latest-patch-release/1589/1

@OndrejKu running Lest as admin user helps me to resolve it.


PR is all green and submitted by authorized user, but not merged

I have a PR that shows all tests passing (everything is green), contains a signed commit, and was submitted by an authorized user. However, for some reason the PR was not automatically merged like it has always done in the past.
Is there a problem with auto-merge?
This PR is the one that is not merging: https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/3254

This is the expected behaviour when an update to an existing bundle is non-trivial.

This is the expected behaviour when an update to an existing bundle is non-trivial.

no a problem with auto-merge.. apparently that PR was changing things that forbid it from being auto-merged.


New org: LEV Foundation; also, update SENS Research Foundation alongside

https://www.levf.org/team
This looks like it was started by Aubrey de Grey after he was kicked out of SENS: https://www.fiercebiotech.com/biotech/anti-aging-foundation-sens-turfs-de-grey-after-allegations-he-interfered-investigation-into
So it seems worthwhile to also update SENS Research Foundation along with this update, so that we don't have incorrect overlapping tenure for Aubrey de Grey (and anybody else he may have poached from SENS).
It may also be worth adding some organization documents related to de Grey's firing from SENS.

ready https://github.com/riceissa/aiwatch/commit/6123c1560b5d3a8e0ac00309f30a7442489bf46e


Implement pagination for the orders table

Specs:

with maximum 25 rows per page
a Next and Previous button to navigate through the table

This now will display only 25 entries per page :


add producer consumer interceptors

Add producer and consumer interceptors that can intercept messages at different points on producer and consumer in order to trace the path of individual messages across the cluster.

inspired in KIP-42
intercepts produced messages before they are sent to the brokers
intercepts consumed messages before are returned to the client
does not intercept the broker's acknowledgement
does not intercept when the consumer commits

ping @dasch to see if he can schedule some time to review this, thanks!

We already use ActiveSupport::Notifications to provide granular pub/sub hooks – what is the use case for introducing this new mechanism?

@dasch with interceptors we can add the span and trace ID to the message headers so that traces emitted by producers can be linked by the consumer.
Interceptor API will allow mutate the records to support the ability to add metadata to a message for auditing/end-to-end monitoring.

@vvuibert ah OK, that’s a good use case, and something we need at Zendesk as well. I’ll review this then.

Thanks!

Thanks @dasch for the detailed review!
I wonder what are the plans for an upcoming release that includes this change.
Is ruby-kafka using some kind of release cycle?
I see there are some issue with the concurrent dependency https://github.com/zendesk/ruby-kafka/pull/835 that might need to be addressed first before a new release.
We'll keep and 👀 on new releases!
Thanks

Yeah, hoping to get that resolved before issuing a new release. There’s no firm cycle.

Addressing that issue would certainly expedite a new release :D


CARBON-15909: Added a property to decide the case of permissions before saving.

Reviewed. Can merge.


Signature catchup if mis-matching Coinbase

The validator reward payouts are reduced for blocks where the signature count is less than 100%. This means that if nodes have a different number of signatures for those blocks then the Coinbase payouts will be different. To help recover from this we can trigger signature catchup when this happens.

Now included in https://github.com/bosagora/agora/pull/3000


Flicker When Setting WindowState.size to DpSize.Unspecified

Describe the bug
Setting WindowState.size to DpSize.Unspecified after a window has been created often results in a brief flicker, in which the window seems to expand to fill the screen before resizing to fit its children.
Affected platforms
Select one of the platforms below:

Desktop

Versions

Kotlin version*: 1.9.10
Compose Multiplatform version*: 1.5.2
OS version(s)* (required for Desktop and iOS issues): Windows 10
OS architecture (x86 or arm64): x86_64
JDK (for desktop issues): 17

To Reproduce
fun main() = application {
    val state = rememberWindowState(size = DpSize.Unspecified)

    Window(
        onCloseRequest = ::exitApplication,
        state = state,
        title = "Adaptive Sizing Flicker Bug",
        resizable = false,
    ) {
        var width by remember { mutableStateOf(480.dp) }

        LaunchedEffect(width) {
            state.size = DpSize.Unspecified
        }

        Box(
            modifier = Modifier
                .background(Color.Red)
                .requiredWidth(width)
                .requiredHeight(width / 2)
        )

        MenuBar {
            Menu("View") {
                Item(text = "480x240", shortcut = KeyShortcut(Key.F1)) { width = 480.dp }
                Item(text = "800x400", shortcut = KeyShortcut(Key.F2)) { width = 800.dp }
                Item(text = "1024x512", shortcut = KeyShortcut(Key.F3)) { width = 1024.dp }
            }
        }
    }
}

Press F1/F2/F3 to change the window size (or interact with the menu bar items) and observe. The flicker does not always occur - it may take multiple resizes to reproduce.
Expected behavior
The window resizes to contain the child Box element without any intermediate sizing steps.
Screenshots
Here's a GIF with the frame time extended so we can see what's happening (in real time, the flicker is nearly instantaneous):

Reproduced on macos with compose=1.5.10-beta02:
sometines the windows becomes completely white, and sometimes we can see red box shifted to the bottom
Tried on Ubuntu 22.04 - worked fine without flickering.
I'll check on windows 11 soon.
MacOs:
https://github.com/JetBrains/compose-multiplatform/assets/7372778/8c758aaf-3c35-4d43-b7b3-4d6b9f091c54

Reproduced the flickering on Windows 11 too.
But frequent white screen after resize issue seems to affect only MacOs.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


The "BaseTripletDataset"

thanks for your contribution

Thank you for the that! :) Has the problem with self.current_class resolved itself for you? If so, feel free to close this issue!


Inference time.

What is the inference time for this model?

Hey! This is a good question. I theory the inference time should be super fast because the model consists only of Convolutional Layers. However, because the models tend to be quite deep it is usually only fast on GPU.


[PERSISTENCE] Fix for #603 after_find callback

Fix for #603 after find callback

This appears to include the changes from #599 as well.

Closing and new pull-request with only relevant commit. Thanks!


Last Inserted Key

In most databases there is a way to retrieve the key of the last item that was inserted into the store. I propose a property to the Lawnchair class called 'lastKey' or something similar that is set to the key of the last item that was inserted or updated is easily accessible.
this.lastKey would simply be set before the save method returns this.
Is there a good reason this hasn't been done already?

I think this is what you are looking for:

db.save({foo:'bar'}, function(new_data) {
  alert(new_data.key);
});


Proposal: Parent-Children Relationship of Plugins

(... since django-CMS Google groups are not used any more, and since they don't support markup, I'll post this proposal here. The GitHub Wiki might be a better place, but I don't have any write access on it.)
Preambel
We should rethink the way how to handle the methods to determine which Plugin is eligible to become a child of another plugin.
Currently, when we open the CMS in structure mode, the Placeholder and its attached Plugins know which plugins may be added as children to an existing plugin. This is determined by each plugin through its attributes parent_plugins and child_plugins. These attributes may be either None or a list of strings. In the former case, all plugins are allowed as parent/children,
whereas in the latter case, only the named plugins are eligible as parents/children.
This static assignment has some drawbacks

In an ecosystem of plugins from different vendors, beforehand we don't know, who may want to become the child of a plugin from another vendor. This could cause one vendor having to as another vendor to add his plugin to the list of allowed children.

Computing the eligible parent-children relationships is time consuming. Therefore django-CMS caches this information internally, which removes the possibility to determine dynamically, for instance by evaluating the current context, which children plugins can be added to an existing plugin.

In structure mode, when rendering a deep tree of plugins, each plugin comes with its own list of eligible children plugins. This can add many kilobytes of additional data to the payload, when transferring a CMS page in structure mode.

This rigid system of parent-children relationships, does for instance not allow to add kinds of intermediate plugins, such as wrappers or logical segments.

Therefore I want to propose a different method to determine which plugins are allowed as children of another plugin. Instead of computing this list statically before the CMS page is rendered, we should add a REST endpoint, which computes this relationship dynamically and based on the current context.
This list then is transferred from the server to the client and is used to render a list of possible
children plugins. The computation of this list should work as follows:

The plugin being asked for, iterates over all plugins registered in the pool.
It then invokes a method, say allowed_as_child_of() for each of the plugins of the pool,
passing its own instance and the current context.
Based on the given parameters, this method returns a boolean, which determines, whether a plugin can be added to the current plugin or not.

This computation can now be much more time consuming. This is because we only have to do it
whenever the user clicks on the + symbol inside the plugin editor, rather than having
to do it for all plugins inside the pool. Even if such a computation requires 200 milliseconds,
since this it is part of the user's interaction, this would disturb.
Possible new Features
Plugin systems, which map the Bootstrap grid, usually encounter the following problem:
A row may be part of a container, and columns may be part of that row. An accordion, carousel,
panel and similar elements can either be children of the container, the row or the column.
Depending below which of these elements an accordion panel is placed, its own children then
shall either be either rows, columns or plain content. This means that whenever
allowed_as_child_of() of an element is invoked, that method could check its potential
parent element, and if that does not contribute to the Bootstrap's grid structure (such as said
accordion, carousel, panel, etc.) it can go up a further level in the tree.
This feature would also make it possible to allow plugins depending on the siblings context.
Backwards Compatibility
Since we don't need the complicated caching functionality anymore, I even believe that it
reduces the amount of code. By adding an overridable method allowed_as_child_of() to the
base class CMSPluginBase, this feature could even be implemented in a backward compatible
manner. This method then just would have to examine the plugin's attribute parent_plugins
and the attribute of its ancestor child_plugins to determine whether it is allowed of
being added or not.
Implementation
In case the django-CMS community agrees on this proposal, I will implement this feature so
that it is available in a future major release. With this in mind, I'd like to open a discussion
about it.

Hello @jrief,
Thanks for your proposal.
The google groups are still active and should be used for feature requests.
I've moved this to https://groups.google.com/forum/#!topic/django-cms-developers/vtsdrMWnUFA

@czpython as I wrote, Google groups does not support markup. So please give me write access to the Wiki, so that I can cross post it there.


connection refused

I followed Docker-Compose Quick Install deployed my bot on Ubuntu 18.04, everything is fine.
When I type this in Windows 10 terminal it show me "connection refused":
curl -X POST -H "Content-Type:application/json" -d "{\"sender\": \"Rasa\",\"message\": \"Hi\"}" http://<IP_ADDRESS>:5005/webhooks/rest/webhook
curl: (7) Failed to connect to <IP_ADDRESS> port 5005: Connection refused

<IP_ADDRESS> is Ubuntu's IP address.
docker-compose.yml :
version: "3.4"
x-database-credentials: &database-credentials
  DB_HOST: "db"
  DB_PORT: "5432"
  DB_USER: "${DB_USER:-admin}"
  DB_PASSWORD: "${DB_PASSWORD}"
  DB_LOGIN_DB: "${DB_LOGIN_DB:-rasa}"

x-rabbitmq-credentials: &rabbitmq-credentials
  RABBITMQ_HOST: "rabbit"
  RABBITMQ_USERNAME: "user"
  RABBITMQ_PASSWORD: ${RABBITMQ_PASSWORD}

x-redis-credentials: &redis-credentials
  REDIS_HOST: "redis"
  REDIS_PORT: "6379"
  REDIS_PASSWORD: ${REDIS_PASSWORD}
  REDIS_DB: "1"

x-duckling-credentials: &duckling-credentials
  RASA_DUCKLING_HTTP_URL: "http://duckling:8000"

x-rasax-credentials: &rasax-credentials
  LOCAL_MODE: "false"
  RASA_X_HOST: "http://rasa-x:5002"
  RASA_X_USERNAME: ${RASA_X_USERNAME:-admin}
  RASA_X_PASSWORD: ${RASA_X_PASSWORD:-}
  RASA_X_TOKEN: ${RASA_X_TOKEN}
  JWT_SECRET: ${JWT_SECRET}
  RASA_USER_APP: "http://app:5055"
  RASA_PRODUCTION_HOST: "http://rasa-production:5005"
  RASA_WORKER_HOST: "http://rasa-worker:5005"
  RASA_TOKEN: ${RASA_TOKEN}

x-rasa-credentials: &rasa-credentials
  <<: *rabbitmq-credentials
  <<: *rasax-credentials
  <<: *database-credentials
  <<: *redis-credentials
  <<: *duckling-credentials
  RASA_TOKEN: ${RASA_TOKEN}
  RASA_MODEL_PULL_INTERVAL: 10
  RABBITMQ_QUEUE: "rasa_production_events"

x-rasa-services: &default-rasa-service
  restart: always
  image: "rasa/rasa:${RASA_VERSION}-full"
  expose:
    - "5005"
  command: >
    x
    --no-prompt
    --production
    --config-endpoint http://rasa-x:5002/api/config?token=${RASA_X_TOKEN}
    --jwt-method HS256
    --jwt-secret ${JWT_SECRET}
    --auth-token '${RASA_TOKEN}'
    --cors "*"
    --port 5005
    --enable-api
  depends_on:
    - rasa-x
    - rabbit
    - redis

services:
  rasa-x:
    restart: always
    image: "rasa/rasa-x:${RASA_X_VERSION}"
    expose:
      - "5002"
    volumes:
      - ./models:/app/models
      - ./environments.yml:/app/environments.yml
      - ./credentials.yml:/app/credentials.yml
      - ./endpoints.yml:/app/endpoints.yml
      - ./logs:/logs
      - ./auth:/app/auth
    environment:
      <<: *database-credentials
      <<: *rasa-credentials
      SELF_PORT: "5002"
      DB_DATABASE: "${DB_DATABASE:-rasa}"
      RASA_MODEL_DIR: "/app/models"
      PASSWORD_SALT: ${PASSWORD_SALT}
      RABBITMQ_QUEUE: "rasa_production_events"
      RASA_X_USER_ANALYTICS: "0"
      SANIC_RESPONSE_TIMEOUT: "3600"
    depends_on:
      - db

  rasa-production:
    <<: *default-rasa-service
    environment:
      <<: *rasa-credentials
      RASA_ENVIRONMENT: "production"
      DB_DATABASE: "tracker"
      RASA_MODEL_SERVER: "http://rasa-x:5002/api/projects/default/models/tags/production"

  rasa-worker:
    <<: *default-rasa-service
    environment:
      <<: *rasa-credentials
      RASA_ENVIRONMENT: "worker"
      DB_DATABASE: "worker_tracker"
      RASA_MODEL_SERVER: "http://rasa-x:5002/api/projects/default/models/tags/production"

  app:
    restart: always
    image: "rasa/rasa-x-demo:${RASA_X_DEMO_VERSION}"
    expose:
      - "5055"
    depends_on:
      - rasa-production

  db:
    restart: always
    image: "bitnami/postgresql:11.3.0"
    expose:
      - "5432"
    environment:
      POSTGRESQL_USERNAME: "${DB_USER:-admin}"
      POSTGRESQL_PASSWORD: "${DB_PASSWORD}"
      POSTGRESQL_DATABASE: "${DB_DATABASE:-rasa}"
    volumes:
      - ./db:/bitnami/postgresql

  rabbit:
    restart: always
    image: "bitnami/rabbitmq:3.7.17"
    environment:
      RABBITMQ_HOST: "rabbit"
      RABBITMQ_USERNAME: "user"
      RABBITMQ_PASSWORD: ${RABBITMQ_PASSWORD}
      RABBITMQ_DISK_FREE_LIMIT: "{mem_relative, 0.1}"
    expose:
      - "5672"

  duckling:
    restart: always
    image: "rasa/duckling:latest"
    expose:
      - "8000"
    command: ["duckling-example-exe", "--no-access-log", "--no-error-log"]

  nginx:
    restart: always
    image: "rasa/nginx:${RASA_X_VERSION}"
    ports:
      - "80:8080"
      - "443:8443"
    volumes:
      - ./certs:/opt/bitnami/certs
      - ./terms:/opt/bitnami/nginx/conf/bitnami/terms
    depends_on:
      - rasa-x
      - rasa-production
      - app

  redis:
    restart: always
    image: "bitnami/redis:5.0.5"
    environment:
      REDIS_PASSWORD: ${REDIS_PASSWORD}
    expose:
      - "6379"

I tried this:
x-rasa-services: &default-rasa-service
  restart: always
  image: "rasa/rasa:${RASA_VERSION}-full"
  ports:
    - "5005:5005"
  command: >
    x
    --no-prompt
    --production
    --config-endpoint http://rasa-x:5002/api/config?token=${RASA_X_TOKEN}
    --jwt-method HS256
    --jwt-secret ${JWT_SECRET}
    --auth-token '${RASA_TOKEN}'
    --cors "*"
    --port 5005
    --enable-api
  depends_on:
    - rasa-x
    - rabbit
    - redis

but not working
pc:/etc/rasa$ docker-compose up
Creating network "rasa_default" with the default driver
Creating rasa_duckling_1 ... done
Creating rasa_redis_1    ... done
Creating rasa_rabbit_1   ... done
Creating rasa_db_1       ... done
Creating rasa_rasa-x_1   ... done
Creating rasa_rasa-worker_1 ...
Creating rasa_rasa-worker_1     ... error
WARNING: Host is already in use by another container

ERROR: for rasa_rasa-worker_1  Cannot start service rasa-worker: driver failed programming external connectivity on endpoint rasa_rasa-worker_1 (c40a151dc0f99c1128a42f19719048f7d5c788a90d04e79548e903ed5fe90b23): Bi
Creating rasa_rasa-production_1 ... done
Creating rasa_app_1             ... done
Creating rasa_nginx_1           ... done

ERROR: for rasa-worker  Cannot start service rasa-worker: driver failed programming external connectivity on endpoint rasa_rasa-worker_1 (c40a151dc0f99c1128a42f19719048f7d5c788a90d04e79548e903ed5fe90b23): Bind for
<IP_ADDRESS>:5005 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

Thanks so much for some help！

Can you raise this issue on the Rasa forum as this issue is not related to the Chatbot widget.🙂

https://rasa.com/docs/rasa/user-guide/connectors/your-own-website/

After connecting the rest input channel, you can post messages to POST /webhooks/rest/webhook with the following format:
{
"sender": "Rasa",
"message": "Hi there!"
}

NO PORT!


Unable to Integrate Cython and Pyinstaller

I am attempting to convert Python to Cython to run my pyinstaller executable to speed up the job and for obfuscation purposes.  I have noticed however, that when I do this, it can be easily decompiled, the C files do not seem to be loaded correctly.  Here’s the steps I have undertaken.  I am doing so on windows.
HA.Py to Pyx with:
driver = webdriver.Chrome(chrome_options = options)
driver.get('https://google.com')
driver.close()
I then Convert to pyx (rename Py -> Pyx)
Set up.py
from distutils.core import setup
from Cython.Build import cythonize
setup(
    ext_modules = cythonize("HA.pyx")
)

python setup.py build_ext –inplace  (pyd, I got a so file in Unix)
C:\Python31\python.exe C:\Python31\Scripts\cython.py smalltest1.py --embed
CMD:
python setup.py develop

pyinstaller -r file_a.so,dll,file_a.so -r file_b.so,dll,file_b.so -F /C:/ANDAR
In the folder it contains the pyx, as well as the setup file.
It seems that when I compile this, it tends not to run or if I put the python file, it runs with python only and can be easily decompiled.  I have tried creating a c file from Python though this did not seem to work through visual Studios.

You probably can't compile your main script with pyinstaller, only imported modules. If that doesn't help, user support is better handled on<EMAIL_ADDRESS>or stack overflow and you could try asking there.


Restart an appliance does not work with cyberx user

[Enter feedback here]
Please correct the document with the right information.
at link below is documented that appliance can be rebooted with cyberx account.
https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/cli-ot-sensor#restart-an-appliance
Which I tested, and it does not work. Please update the documentation.

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

ID: ef6e028a-a9a7-111b-68aa-14d3939a9606
Version Independent ID: 3cfb0a4a-5461-1569-da78-1ba420b3ffc6
Content: CLI command reference from OT network sensors- Microsoft Defender for IoT - Microsoft Defender for IoT
Content Source: articles/defender-for-iot/organizations/cli-ot-sensor.md
Service: defender-for-iot
GitHub Login: @limwainstein
Microsoft Alias: lwainstein

@ankkp
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thanks, we've opened a work item to address as part of our content maintenance work.

@limwainstein according to this
https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands#supported-users-by-cli-actions
The cyberx and cyberx_host users are only supported in versions earlier than [23.1.x]
I will put a note on the page with this

Thanks @tarTech23, when the change is public please update here with the link and add a comment with '#please-close' (without the '') to close the issue.

The documentation has been updated.
Here https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands#supported-users-by-cli-actions
and here https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/cli-ot-sensor#restart-an-appliance
The new code is reboot instead of restart.
#please-close


Can you use this with the official Whisper API (for those without good GPUs)?

Hey, is it possible to use this with the Whisper API so that the processing is done on OpenAIs servers instead? That way devices that don't have good GPUs can still us it (for those users that don't mind paying the small API fee).

No but I can try to implement that to be an option.
Right now, you can use the Google Colab Notebook (at the top of the Readme) to run this webui in the cloud for free as well!


Space law real

About the PR

Add space law from https://wiki.spacestation14.io/wiki/Space_Law in guidebooks format
Draft til i figure how to make tables in guideboooks
Why / Balance

Useful to have space law in-game
Technical details

All guidebooks should be updated manually
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Space Law book was added to the game!

@lzk228 are you coming back to this?

ye


Fix Close Button icon color in TitleBar while mouse over

Pull request type

Please check the type of change your PR introduces:

[ ] Update
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes

What is the current behavior?
Normally, the TitleBar should change Close button background to Red, and change foreground to White while mouse over. But it looks like this now.

Issue Number: N/A
What is the new behavior?

Because the TitleBar.cs hook mouse event, so the TemplateBinding in TitleBar.xaml cannot trigger by IsMouseOver. So this pull request continuely use the Hover/RemoveHover method in TitleBarButton.cs as event, and add a MouseOverButtonsForeground property to allow user defining this color.

Other information

hey @seasonyuu, thanks for your contribution to the project

This PR has some bugs that should be worked out.

Binding failures in TitleBar.xaml

<Setter Property="MouseOverButtonsForeground" Value="{Binding Path=MouseOverButtonsForeground, RelativeSource={RelativeSource AncestorType={x:Type controls:TitleBar}}}" />

There's no such property for TitleBar but there was one introduced for TitleBarButton. But anyhoo, the line can be omitted as the styling logic is entirely handled in code through TitleBarButton.Hover()

The ButtonsForeground is now broken when switching themes
To reproduce the bug: run the gallery app, hover over the TitleBar buttons (like minimize or close buttons), then switch themes and you'll see that the foreground is now stuck to the previous theme.
The reason for this is ButtonsForeground = _cacheButtonsForeground, which breaks the theme binding from
<Setter Property="ButtonsForeground" Value="{DynamicResource ButtonForeground}" />

as seen here, the buttons become invisible when switching to light theme

Got it. Give me sometime
koal44 @.***> 于 2024年3月17日周日 04:52写道：

image.png (view on web)
https://github.com/lepoco/wpfui/assets/78566945/b03b4280-c087-4968-aeb4-85b24b55de21
as seen here, the buttons become invisible when switching to light theme
—
Reply to this email directly, view it on GitHub
https://github.com/lepoco/wpfui/pull/993#issuecomment-2002127918, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACB5AR43RY2T67WR7MFCFHTYYSWJZAVCNFSM6AAAAABETRWBKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGEZDOOJRHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


add Hash2 func with uintptr as resulting type

The uintptr type has different sizes of different
platforms. Therefore this type is more flexible
and faster also on 32Bit Systems, instead of using a
fixed sized uint64. Furthermore a uintptr can hold any array
index, because it can hold any pointer (array of uint8).

Thanks for the contribution! Hope you find Hash2 useful going forward :).


Flutter ios builds do not support "[CP] Copy Pods Resources" Build Phase

Steps to reproduce

Create a Flutter package with a .plist file  in the /ios folder
Add this .plist file as a 's.resource' to the /ios folder .podspec file
Create an example Flutter app that imports this package as a dependency
Run flutter build ios on this example flutter app
Run pod install within the example app /ios/ folder for good measure
open the .xcworkspace  file generated and check the 'Build Phases' tab on the top level Runner

Actual results
Observe that the "[CP] Copy Pods Resources" step is not present. I'm not sure if there's a step missing or this is not something supported in Flutter ios, but we need to copy a pods resource in our package to be read by our native ios apps.

react-native project where this is included
flutter project where this is not included

Logs

Logs
pod install --verbose

Preparing

Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Finding Podfile changes
  - Flutter
  - klaviyo_flutter

Fetching external sources
-> Fetching podspec for `Flutter` from `Flutter`
-> Fetching podspec for `klaviyo_flutter` from `.symlinks/plugins/klaviyo_flutter/ios`

Resolving dependencies of `Podfile`
  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_b_1_7.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/1/7/KlaviyoSwift/4.0.0/KlaviyoSwift.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/b/1/7/KlaviyoSwift/4.0.0/KlaviyoSwift.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_6_4_6.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/6/4/6/KlaviyoCore/4.0.0/KlaviyoCore.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: all_pods_versions_9_b_6.txt exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/9/b/6/AnyCodable-FlightSchool/0.6.7/AnyCodable-FlightSchool.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/6/4/6/KlaviyoCore/4.0.0/KlaviyoCore.podspec.json exists! Returning local because checking is only performed in repo update
  CDN: trunk Relative path: Specs/9/b/6/AnyCodable-FlightSchool/0.6.7/AnyCodable-FlightSchool.podspec.json exists! Returning local because checking is only performed in repo update

Comparing resolved specification to the sandbox manifest
  - AnyCodable-FlightSchool
  - Flutter
  - KlaviyoCore
  - KlaviyoSwift
  - klaviyo_flutter

Downloading dependencies

-> Using AnyCodable-FlightSchool (0.6.7)

-> Using Flutter (1.0.0)

-> Using KlaviyoCore (4.0.0)

-> Using KlaviyoSwift (4.0.0)

-> Using klaviyo_flutter (0.1.0)
  - Running pre install hooks
  - Running pre integrate hooks

Generating Pods project
  - Creating Pods project
  - Installing files into Pods project
    - Adding source files
    - Adding frameworks
    - Adding libraries
    - Adding resources
    - Adding development pod helper files
    - Linking headers
  - Installing Pod Targets
    - Installing target `AnyCodable-FlightSchool` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/AnyCodable-FlightSchool/AnyCodable-FlightSchool.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/AnyCodable-FlightSchool/AnyCodable-FlightSchool-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/AnyCodable-FlightSchool/AnyCodable-FlightSchool-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/AnyCodable-FlightSchool/AnyCodable-FlightSchool-dummy.m`
    - Installing target `Flutter` iOS 12.0
    - Installing target `KlaviyoCore` iOS 13.0
      - Generating module map file at `Pods/Target Support Files/KlaviyoCore/KlaviyoCore.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/KlaviyoCore/KlaviyoCore-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/KlaviyoCore/KlaviyoCore-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/KlaviyoCore/KlaviyoCore-dummy.m`
    - Installing target `KlaviyoSwift` iOS 13.0
      - Generating Info.plist file at `Pods/Target Support Files/KlaviyoSwift/ResourceBundle-KlaviyoSwift-KlaviyoSwift-Info.plist`
      - Generating module map file at `Pods/Target Support Files/KlaviyoSwift/KlaviyoSwift.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/KlaviyoSwift/KlaviyoSwift-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/KlaviyoSwift/KlaviyoSwift-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/KlaviyoSwift/KlaviyoSwift-dummy.m`
    - Installing target `klaviyo_flutter` iOS 13.0
      - Generating module map file at `Pods/Target Support Files/klaviyo_flutter/klaviyo_flutter.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/klaviyo_flutter/klaviyo_flutter-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/klaviyo_flutter/klaviyo_flutter-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/klaviyo_flutter/klaviyo_flutter-dummy.m`
  - Installing Aggregate Targets
    - Installing target `Pods-Runner` iOS 13.0
      - Generating Info.plist file at `Pods/Target Support Files/Pods-Runner/Pods-Runner-Info.plist`
      - Generating module map file at `Pods/Target Support Files/Pods-Runner/Pods-Runner.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Pods-Runner/Pods-Runner-umbrella.h`
      - Generating dummy source at `Pods/Target Support Files/Pods-Runner/Pods-Runner-dummy.m`
  - Generating deterministic UUIDs
  - Stabilizing target UUIDs
  - Running post install hooks
    - Podfile
  - Writing Xcode project file to `Pods/Pods.xcodeproj`
  Cleaning up sandbox directory

Integrating client project

Integrating target `Pods-Runner` (`Runner.xcodeproj` project)
  - Running post integrate hooks
  - Writing Lockfile in `Podfile.lock`
  - Writing Manifest in `Pods/Manifest.lock`
  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update

-> Pod installation complete! There are 2 dependencies from the Podfile and 5 total pods installed.

Flutter Doctor output

Doctor output

[✓] Flutter (Channel stable, 3.24.4, on macOS 15.1 24B83 darwin-arm64, locale en-US)
    • Flutter version 3.24.4 on channel stable at /Users/daniel.peluso/Library/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 603104015d (4 weeks ago), 2024-10-24 08:01:25 -0700
    • Engine revision db49896cf2
    • Dart version 3.5.4
    • DevTools version 2.37.3

[!] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/daniel.peluso/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/to/macos-android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16B40
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] IntelliJ IDEA Ultimate Edition (version 2024.2.3)
    • IntelliJ at /Users/daniel.peluso/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (5 available)
    • iPhone 15 Pro (mobile)          • 74DE3224-B7E0-4F25-B19A-DD0A7C6B9CBD • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-5 (simulator)
    • iPhone 16 Pro (mobile)          • 8C03AF48-1C50-45EE-9F7A-682B42881CEB • ios            • com.apple.CoreSimulator.SimRuntime.iOS-18-1 (simulator)
    • macOS (desktop)                 • macos                                • darwin-arm64   • macOS 15.1 24B83 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad                • darwin         • macOS 15.1 24B83 darwin-arm64
    • Chrome (web)                    • chrome                               • web-javascript • Google Chrome 131.0.6778.70

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

One thing I noticed as well is that Podfiles generated by react-native will produce this: use_frameworks! :linkage => :static whereas Flutter generated Podfiles look like this use_frameworks!. Is there any specific reason that Flutter prefers not to use static linkage? Is there anything in Flutter I can add to my package to have importing projects get my package statically?When I change that line in my flutter-generated podspec to the linkage => :static I am able to see the resource in my build phases and the resource gets updated properly

Thanks for the detailed report. I tried to follow the steps to replicate, but probably missed a step as I am unable to run it properly. Can you provide us a sample repo that we can clone to verify this further ?

Is there any specific reason that Flutter prefers not to use static linkage?

I tried to look for this and could find https://github.com/flutter/flutter/issues/84418#issuecomment-861856717
Also maybe s.static_framework=true can be used in respective pod's podspec ?

Sorry for the delayed response. I'm not able to make a new repo for this, but I will say that after investigating this further I found that the only way resources are carried over to the ios project is if you change the following line in the podspec:
  use_frameworks! :linkage => :static // this will take any plist or resource tiles over from the shared codebase
  use_frameworks! // this will not carry over any shared codebase resources.

My concern with this is that I can't expect developers to change this in their podspec automatically, and I'd like the SDK I'm working on to use resources from the shared library. When you tried to follow the replication steps, what happened?

When you tried to follow the replication steps, what happened?

Thanks for the update. I reached till below step while trying to replicate it. I will try to go further to see if I am able to verify this properly or not. For time being, based on the report and behavior observed, I will keep the issue open for team's tracking,

Run pod install within the example app /ios/ folder for good measure

If it's built as a framework bundle (non-static) then any resources shouldn't be copied to the app, the Resource are in the framework, not the app, something like the_app.app/Frameworks/your_framework.framework/Resources.  You will see this if you open Xcode and create an out-of-the-box framework and then embed something.
As this issue is written the behavior looks expected.  Other than the missing build step, are you actually seeing a problem where the Resource is missing?  As in, if your plugin references the Resource, is it found?


Add other cloud providers

Hi!
Thanks a lot for the up-to-date information regarding lambda cold start time.
Did you think about adding more cloud providers like Azure, GCP, etc? This information could be useful for the users as well.
Thanks in advance!

👋 Thanks!
Yeah I'm planing to do it for GCP first


Google Keep Takeout zip file import failure

When trying to import my takeout.zip file, the error I receive is the following:
Unexpected token P in JSON at position 0
Thanks!

Would you feel comfortable providing the file so that I can attempt the import myself? It must have some data which is in a format I haven't expected.

i'm puzzled, but i am actually not able to reproduce my import error; neither with the old takeout.zip, nor with a new one...
i'm closing the issue, since it works now!


when i click the right calendar the left value also changed ?

how can i prevent this ? i hope it can behave like this :  when i click left only left value changed

like this


Use timezone aware datetime object on session

Naïve datetime objects are discouraged in https://docs.python.org/3/library/datetime.html#datetime.datetime.utcnow

Warning Because naive datetime objects are treated by many datetime methods as local times, it is preferred to use aware datetimes to represent times in UTC. As such, the recommended way to create an object representing the current time in UTC is by calling datetime.now(timezone.utc).

fixes N/A

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[ ] Run pre-commit hooks and fix any issues.
[ ] Run pytest and tox, no tests failed.

Sorry for not including all the contributing items. Some of the entries if you are open to this change I will do once I update my personal access token (can't work with this repo on the CLI right now due to not having the workflow permission authorized from the CLI)

I updated everything else to be timezone aware, this makes sense too. This case is already treated as UTC in set_cookie, but might as well be consistent.

Changes entry added
I don't believe that there is a relevant documentation update, but please let me know if that's incorrect
Existing tests related to verifying the session's expiration cover this, I believe

Please let me know if there is anything else you need and I'll do my best to provide those updates


Add policy to control when the Table class stops retrying

At the end of this task it will be possible to configure the bigtable::Table class with a policy to decide when to give up retrying RPC operations.  The default should use a long timeout, but other policies (maximum number of failures, combinations of failure counts and time) are possible.

This was completed as part of #26


chore: Increase timeout for process termination

Motivation
Current Java Edition Minecraft servers, especially those that are forks of the vanilla Minecraft server software, take some time to properly stop and save all resources, i.e. worlds, inventories and other state to disk. Prematurely terminating those processes leads to worlds not being saved at all, world corruption due to the interrupted save process and unloadable worlds. In addition this leads to lock files being left that don't belong to any process anymore.
Modification
Increase the timeout to 60 seconds. This gives servers more time to properly store all files and shutdown whilst still cleaning up servers that may have become stuck whilst shutting down.
Result
Server processes are now given more time to properly shutdown.
Other context
See the discussion in Discord starting from here.

I feel like this should be configurable instead of fixed 60s (or 5s)
Best would be a setting for the task imo. Some lobby template servers only need 5s and should be killed after, some heavily modded static server might need more. Yet you also don't want to wait for a whole minute for broken lobby server to be killed.

Yes, the configuration should be available per-service, but that's not a simple task to do as the task configuration is not available to the service, unless we provide the timeout as a variable in the service configuration or retrieve the task from the task name provided to the service configuration.

Yes, the configuration should be available per-service, but that's not a simple task to do as the task configuration is not available to the service, unless we provide the timeout as a variable in the service configuration or retrieve the task from the task name provided to the service configuration.

what's the problem with providing it as a variable in the service configuration?

The thing is: sure, we could just throw the variable in there and move on, but there are more places that have variables that cannot be set per service, and need to be accessed via the task (which shouldn't be the case). One example is the required permission for a task or the smart configuration. So imo it's better to delay this a bit and find a better solution on how we can handle the variables and then merge this :)


Support v4 mapping to v6

This PR introduces v4-mapping-to-v6 and properly implements IPV6_V6ONLY socket option.
The echo sample application is converted to use this feature.

@kartben The documentation build complains about this comment in the code
 *  @brief Is the IPv6 address an IPv4 mapped one. The v4 mapped addresses
 *         look like ::ffff:a.b.c.d

The warning is this one
WARNING: /runner/_work/zephyr/zephyr/include/zephyr/net/net_ip.h:1258: explicit link request to 'ffff' could not be resolved

Is there a way to mark this in the code so that doxygen does not think it is a link?

The net-shell refactoring PR https://github.com/zephyrproject-rtos/zephyr/pull/63164 should be merged before this one so adding DNM

@jukkar It feels like the README for the sample should be updated?


Feature for the roadmap -- the use of domain binding

Domain binding is where a prover includes a common input to a series of proof requests such that they can detect when the same credential is used multiple times in response.  There are several scenarios where this is useful:

as a unique, "directed identifier" for a service detecting the same credential being used again
to detect the malicious use of a credential that is submitted multiple times combined with different sets of other credentials
in a voting-type scenario, when an anonymous "vote credential" is submitted multiple times so that it can be handled by business rules e.g. last vote counts

The holder can also detect if the same domain binding input is received from multiple verifiers to detect collusion on the verifier side.  As long as each verifier uses a different domain binding input, verifiers determine when different verifiers get a credential.
This is described in the anonymous credentials literature and should be a feature added to AnonCreds.  It has been described for use in BBS+ Signatures, but I'm not certain if it has been implemented.

This is part of the AnonCreds 2.0 implementation we have. Closing this as a spec. Issue for v1.0.


Add initial support for composite primary keys

This pull request allows the table! macro and codegen to handle tables
which use more than one column for their primary key. At the moment they
are fairly useless, but they will compile.
The methods in question are primarily used for FindDsl and
associations. Things like update are defined in terms of FindDsl and
Identifiable. Since the generators for those traits don't handle
composite primary keys, none of that can be used (yet).
Working on this also made me realize a bit of a hole in our type system.
We implement Expression for a tuple of expressions as a comma
delimited list. However, a comma delimited list isn't always valid. In
particular a composite table does actually implement FindDsl for an
expression that matches it's primary key -- and would generate invalid
SQL like pk1, pk2 = $1, $2. Luckily, we're saved by the fact that
tuples don't implement AsExpression, so trying to do .find((1, 2))
won't compile.
I'm not sure if we should fix this or not, but the fix would basically
mean separating out "arbitrary expression" from "expression valid as a
select or returning clause", and potentially other places where tuples
appear such as set clauses and in expressions. For now though, as long
as the inproper code doesn't compile for the reasonable cases, I'm not
super worried. We should fix this eventually though, as I don't like
something that we can statically determine is invalid SQL compiling.
Ref #42

Review? @diesel-rs/contributors

LGTM. Do you maybe want to add some docs on how to use this? (Mentioning that the table! macro allows a comma separated list of columns for composite primary keys should suffice.)

(I added docs before merging)


Attributes for spot data price don't respect local time zone

Version 2.2.0
I am in timezone GMT+1
In attributes the first value is the value for 1 o'clock and the last value for 23pm is missing, so the list only covers 23 hours. The total list is shifted by one hour.
Example for today:

start_time: '2023-12-19T00:00:00+00:00'
end_time: '2023-12-19T01:00:00+00:00'
price_eur_per_mwh: 61.54
price_ct_per_kwh: 6.154
start_time: '2023-12-19T01:00:00+00:00'
end_time: '2023-12-19T02:00:00+00:00'
price_eur_per_mwh: 62.44
price_ct_per_kwh: 6.244
start_time: '2023-12-19T02:00:00+00:00'
end_time: '2023-12-19T03:00:00+00:00'
price_eur_per_mwh: 60.07
price_ct_per_kwh: 6.007
start_time: '2023-12-19T03:00:00+00:00'
end_time: '2023-12-19T04:00:00+00:00'
price_eur_per_mwh: 61.31
price_ct_per_kwh: 6.131
start_time: '2023-12-19T04:00:00+00:00'
end_time: '2023-12-19T05:00:00+00:00'
price_eur_per_mwh: 66.39
price_ct_per_kwh: 6.639
start_time: '2023-12-19T05:00:00+00:00'
end_time: '2023-12-19T06:00:00+00:00'
price_eur_per_mwh: 89.6
price_ct_per_kwh: 8.959999999999999
start_time: '2023-12-19T06:00:00+00:00'
end_time: '2023-12-19T07:00:00+00:00'
price_eur_per_mwh: 98.94
price_ct_per_kwh: 9.894
start_time: '2023-12-19T07:00:00+00:00'
end_time: '2023-12-19T08:00:00+00:00'
price_eur_per_mwh: 104.8
price_ct_per_kwh: 10.48
start_time: '2023-12-19T08:00:00+00:00'
end_time: '2023-12-19T09:00:00+00:00'
price_eur_per_mwh: 94.88
price_ct_per_kwh: 9.488
start_time: '2023-12-19T09:00:00+00:00'
end_time: '2023-12-19T10:00:00+00:00'
price_eur_per_mwh: 86.1
price_ct_per_kwh: 8.61
start_time: '2023-12-19T10:00:00+00:00'
end_time: '2023-12-19T11:00:00+00:00'
price_eur_per_mwh: 79.71
price_ct_per_kwh: 7.970999999999999
start_time: '2023-12-19T11:00:00+00:00'
end_time: '2023-12-19T12:00:00+00:00'
price_eur_per_mwh: 76.5
price_ct_per_kwh: 7.65
start_time: '2023-12-19T12:00:00+00:00'
end_time: '2023-12-19T13:00:00+00:00'
price_eur_per_mwh: 79.87
price_ct_per_kwh: 7.987
start_time: '2023-12-19T13:00:00+00:00'
end_time: '2023-12-19T14:00:00+00:00'
price_eur_per_mwh: 84.97
price_ct_per_kwh: 8.497
start_time: '2023-12-19T14:00:00+00:00'
end_time: '2023-12-19T15:00:00+00:00'
price_eur_per_mwh: 91.31
price_ct_per_kwh: 9.131
start_time: '2023-12-19T15:00:00+00:00'
end_time: '2023-12-19T16:00:00+00:00'
price_eur_per_mwh: 95.94
price_ct_per_kwh: 9.594
start_time: '2023-12-19T16:00:00+00:00'
end_time: '2023-12-19T17:00:00+00:00'
price_eur_per_mwh: 96.8
price_ct_per_kwh: 9.68
start_time: '2023-12-19T17:00:00+00:00'
end_time: '2023-12-19T18:00:00+00:00'
price_eur_per_mwh: 95.91
price_ct_per_kwh: 9.591
start_time: '2023-12-19T18:00:00+00:00'
end_time: '2023-12-19T19:00:00+00:00'
price_eur_per_mwh: 94.76
price_ct_per_kwh: 9.476
start_time: '2023-12-19T19:00:00+00:00'
end_time: '2023-12-19T20:00:00+00:00'
price_eur_per_mwh: 88.03
price_ct_per_kwh: 8.803
start_time: '2023-12-19T20:00:00+00:00'
end_time: '2023-12-19T21:00:00+00:00'
price_eur_per_mwh: 81.9
price_ct_per_kwh: 8.190000000000001
start_time: '2023-12-19T21:00:00+00:00'
end_time: '2023-12-19T22:00:00+00:00'
price_eur_per_mwh: 78.23
price_ct_per_kwh: 7.823
start_time: '2023-12-19T22:00:00+00:00'
end_time: '2023-12-19T23:00:00+00:00'
price_eur_per_mwh: 60.04
price_ct_per_kwh: 6.004

As I'm using Awattar/AT, the error might be here:
class Marketprice:
UOM_EUR_PER_MWh = "EUR/MWh"
def __init__(self, data):
    assert data["unit"].lower() == self.UOM_EUR_PER_MWh.lower()
    self._start_time = datetime.fromtimestamp(
        data["start_timestamp"] / 1000, tz=timezone.utc
    )
    self._end_time = datetime.fromtimestamp(
        data["end_timestamp"] / 1000, tz=timezone.utc
    )
    self._price_eur_per_mwh = float(data["marketprice"])

Went back to 1.3.1 (where I came from when upgrading to 2.2.0) and everything is fine again

Timestamps are given in UTC time in the developers view (as indicated by "+00:00"). If you use e.g. ApexCharts, they will be printed using your local time zone setting.

I can confirm the implementation in v2.2 is wrong. If the hours are in Utc timezone then the first hour for delivery date 4 Jan should start on 3 Jan 23:00 like it is in v1.4. Because Belgium is currently on Utc +1. You can see this time shift at https://www.timeanddate.com/worldclock/converter.html?iso=20240103T230000&p1=48&p2=1440

This is what I see if a configure an EPEX Spot Web Scraper for BE:

My timezone is set to (but this shouldn't make a difference at all):

Is this what you would expect? Do you see different values? If yes, there must be a difference in your system configuration. Please share more information about your configuration.

Hi @mampfes ,
I freshly installed HACS around 26/12 and then the v2.2.0 version of epex spot.
I displayed the prices via the apex charts and had the issue that when clicking on the first block that it was showing in the popup 02:00 as time.
Afterwards I saw this issue and had the same data format as Celphor.
The first timing started at midnight with the timezone indicator also on +00:00.
So something like:
start_time: '2023-12-19T00:00:00+00:00'
end_time: '2023-12-19T01:00:00+00:00'
Downgrading to v1.4 changed it in
start_time: '2023-12-18T23:00:00+00:00'
end_time: '2023-12-19T00:00:00+00:00'
The charts were fine then.
Today I did see the v2.3.1 version and upgraded to that one and now I have it as format:
start_time: '2023-12-19T00:00:00+01:00'
end_time: '2023-12-19T01:00:00+01:00'
For me this is also a correct representation. For my concern this bug can be closed. :)
@Celphor Can you upgrade to v2.3.1 and confirm it is fine for you too ?

@Celphor, @stevenboeckmans Did 2.3.1 fix the issue for you?

@mampfes For me it looks fine with 2.3.1 Thank you.

Tried 2.3.2 - the problem persists

@Celphor Hm, as the problem persists only for you, my guess that this has s.th. with your setup and/or operating system. Which HA installation type are you using? (HA OS, Container, Core, Supervised). Which timezone is configured in HA and - if you don't use HA OS - which timezone is configured in your operating system?
You mentioned that 1.3.1 worked and 2.2.0 doesn't work anymore. There were 3 releases in between (1.4.0, 2.0.0, 2.1.0.). Could you please find out which release exactly causes the problem? Because so far I don't an idea what causes this issue.

Sure. 1.4.0 is ok, 2.0.0 breaks it

@Celphor Are you using Awattar as source? If yes, could you please test the new beta version <IP_ADDRESS>?
I think I found the root case of this issue, but I'm not sure whether this fix is working. One problem is, that version 1.4.0 didn't use the Awattar API correctly. Therefore a change is definitely needed.

I'm using Awattar (at). In <IP_ADDRESS> the hours and prices match now, but now you pull the wrong days. Today shows yesterday prices and tomorrow is today. Miscount by 1 is developers best friend ;-)

the hours and prices match now,
ok, good!

today shows yesterday prices and tomorrow is today
Could you please check this again? I don't see this on my machine and I don't think that this has s.th. to do with the latest changes.

Ah, the problem is a little bit different. You pull 3 days of data now, so the first set is yesterday. Before there was only today and tomorrow (if available). As I reuse the data on an external display assuming the data starts on the current day, i went into the trap ;-)
Do you keep it like this or wasn't this intended?
As of now:

So in the future, can I rely on this code to work? I just changed the indices to the second and third split as follows on my sensors returning a string of pipe separated daily prices:

name: Strompreise heute
unique_id: strompreise_heute
icon: mdi:currency-eur
state: "
{% set s = states.sensor['epex_spot_at_price'].attributes.data | map(attribute='price_ct_per_kwh') %}
{% if (s | batch(24) | list | length) < 2 %}
{{ '' }}
{% else %}
{% set s = states.sensor['epex_spot_at_price'].attributes.data | map(attribute='price_ct_per_kwh') %}
{% for price in (s | batch(24) | list)[1] %}
{{- price | round(2) -}}
{%- if not loop.last %}|{% endif -%}
{% endfor %}
{% endif %}
"

name: Strompreise morgen
unique_id: strompreise_morgen
icon: mdi:currency-eur
state: "
{% set s = states.sensor['epex_spot_at_price'].attributes.data | map(attribute='price_ct_per_kwh') %}
{% if (s | batch(24) | list | length) < 3 %}
{{ '' }}
{% else %}
{% set s = states.sensor['epex_spot_at_price'].attributes.data | map(attribute='price_ct_per_kwh') %}
{% for price in (s | batch(24) | list)[2] %}
{{- price | round(2) -}}
{%- if not loop.last %}|{% endif -%}
{% endfor %}
{% endif %}
"

Yes, I will keep this behaviour, because I need the day from yesterday for epex_spot_sensor in certain situations.

I am happy with it. Thanks for fixing the bug!


Sometimes imposters are not being able to kill

Really obscure, needs further investigation.

Seems to happen primarily after au_debug_restart.


uncertainties for hitran and hitemp

I added functions to get the uncertainty codes of HITRAN or HITEMP database.
The uncertainty range corresponding to the code can be found here; https://hitran.org/docs/uncertainties/

We can export the uncertainty indices by setting with_error=True. Here is an example of usage:
mdb = MdbHitemp('./database/CH4/',nu_grid,with_error=True)  #mdb.ierr become available

#wavmask (optional)
wavmask = (mdb.nu_lines >= nu_grid[0]) * (mdb.nu_lines <= nu_grid[-1])
mdb.apply_mask_mdb(wavmask)

#add error
mdb.add_error()

nu_lines_err = mdb.nu_lines_err  #uncertainty indices corresponding to mdb.nu_lines

@YuiKasagi Can you pull the current develop branch into the branch?
git pull origin develop

Because hitemp_uncertainty does not include the recent update of develop (in particular #394 #395), the integration tests fails.
You may test integration (need a bit time ) by
cd exojax/test/integration
pytest

I have missed to pull the current branch. Thank you for pointing it out.
I also tried $pytest exojax/test/integration/ and it successfully passed.

@YuiKasagi I couldn't pass the test for test_hitran_with_error (from clean download).
What's wrong?
Traceback (most recent call last):
  File "/home/kawahara/exojax/tests/integration/api/api_hitran_hitemp_test.py", line 55, in <module>
    test_Hitran_with_error()
  File "/home/kawahara/exojax/tests/integration/api/api_hitran_hitemp_test.py", line 46, in test_Hitran_with_error
    mdb = api.MdbHitran("CO",nus, with_error=True)
  File "/home/kawahara/exojax/src/exojax/spec/api.py", line 876, in __init__
    self.activate(df)
  File "/home/kawahara/exojax/src/exojax/spec/api.py", line 413, in activate
    self.instances_from_dataframes(df[mask])
  File "/home/kawahara/exojax/src/exojax/spec/api.py", line 906, in instances_from_dataframes
    self.ierr = df_load_mask.ierr.values.to_numpy()
  File "/home/kawahara/anaconda3/lib/python3.10/site-packages/vaex/dataframe.py", line 288, in __getattr__
    return object.__getattribute__(self, name)
AttributeError: 'DataFrameLocal' object has no attribute 'ierr'

Thanks! @YuiKasagi Can you make a new issue about the uncomment after the future merge and release of radis PR 574?


Implement object duplication instruction

Checklist

[x] cargo clippy reports no issues
[x] cargo deny issues have been fixed or added to deny.toml
[x] relevant examples/test cases run
[x] changes added to changelog

[x] Add credit to yourself for each change: Added new functionality @githubname.

Problems PR Solves
Sometimes it is desirable to duplicate an object. A good example is duplicating an object and changing its material to do a second render pass with a different shader.
This PR implements a duplicate_object function, which internally implements an InstructionKind::DuplicateObject. Overrides are possible for all the three fields of an Object (mesh, material and transform).
Related Issues
None that I'm aware of. But this is an alternative solution to the problem solved by PR #305

CI is mad (you can run bash ./build.bash ci or manually cargo clippy to check).

Oh, now I see what happened! I was running cargo clippy from the repository root, but I only get the relevant error when running it from inside the specific crate folder. Is that intended?
Anyway, let me fix that, just a moment :+1:

Yeah I've just been silencing them, structs are shockingly noisy and well documented arguments are annoying, but fine.

Also format is mad 😭

Sorry about that! Should be fixed now.


How to res.send data 2 times?

Hello.
I want to show the user a loading line, and then when the data from the database is received, show the full page.
var express = require('express');
var app = express();

app.get('/', function (req, res) {
  res.send('Loading ...');
  setTimeout(function() {
    console.log('Get database data ...');
    res.send('Hello World!');
  }, 3000);
});

app.listen(30000, function () {
  console.log('Example app listening on port 30000!');
});

Such code leads to an error.
Example app listening on port 30000!
Get database data ...
_http_outgoing.js:491
    throw new Error('Can\'t set headers after they are sent.');
    ^

Error: Can't set headers after they are sent.
    at validateHeader (_http_outgoing.js:491:11)
    at ServerResponse.setHeader (_http_outgoing.js:498:3)
    at ServerResponse.header (/home/express/node_modules/express/lib/response.js:767:10)
    at ServerResponse.send (/home/express/node_modules/express/lib/response.js:170:12)
    at Timeout._onTimeout (/home/express/app.js:8:9)
    at ontimeout (timers.js:482:11)
    at tryOnTimeout (timers.js:317:5)
    at Timer.listOnTimeout (timers.js:277:5)

The res.send method is just an everything at once for the 99% of usage. For your use case you'll have to use res.write for the first call and then res.end for the second call :+1:

i am having the same issue and i dont know how to tackle it
var express = require('express');
var router = express.Router();
var session = require('express-session');
/* GET home page. */
router.get('/', function(req, res, next) {
res.render('index', { title: 'Express' });
});
module.exports = router;
router.post('/', function (req, res) {
res.end(JSON.stringify(req.body));
res.redirect('/login');
});
router.get('/login',function(req,res, next){
res.render('login',{title: 'login'});
})

Neither of these uses are possible (the new comment, or the OP).  HTTP and the browser are the restrictions here, so nothing you can do about it in express or any other web framework.  If you want to send a page, then send another page you will need to render two pages.  In the json version, you would have to do the redirect on the browser side after receiving the json.  For the loading bar, you would have to render a page with the loading bar, then poll for your finished data with separate requests.

thanks for the information, saved me time to hassle how to the impossible.
I am new to express and so far am learning fast , I want to create an API
for my mobile app which is database orientated. i fear my system will be
vulnerable when the app communicate with the API through exchange of API ,
soo can i encrypt the json file and if i do will it reduce the perfomance
of the system?.
and again i want my system to be able to retrieve pdf files and pictures
from the server , do i create a no sql database for that or is the a way to
save file on mysql?

Express is a great tool for what you want to do, but this is not the best venue for asking these type of questions.  I would recommend asking for help on stackoverflow and reading up on building api's with express, there are some decent examples here: https://dev.to/t/express


fix leading dashes in log and pid filenames

Fix for issue #178, utile.randomString will give you a leading hypen in 1/64 uids and associated filenames.

Why Qq? I'm curious.

Hahaha, maybe they take pull requests?


ARROW-672: [Format] Add MetadataVersion::V3 for Arrow 0.3

As a matter of diligence, we increment the metadata version for Arrow 0.3 since we've changed the metadata format is various ways.

Thanks. I'm going to add a C++ unit test at least

done

GCE having problems today, on my fork 2 out of 3 linux builds ran https://travis-ci.org/wesm/arrow/builds/218559567


fix: throw "no cloud event detected" if one can't be read

This commit changes the event mode detection in HTTPReceiver so that it will
throw a TypeError if the event mode can't be detected per the spec.
Fixes: https://github.com/cloudevents/sdk-javascript/issues/136
Signed-off-by: Lance Ball<EMAIL_ADDRESS>

@helio-frota Good catch. I can do it now, or wait until #134 lands and update this PR from master (which is what I was planning to do).

@helio-frota updated with simplified constants usage


feat: bump go to 1.22

Description:
support for 1.19 ended, see https://endoflife.date/go
Checklist:

[x] Does your PR pass tests?
[x] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

'bout time
thanks @bufferoverflow !


Overlap Matrix with MBAR issue: KeyError=2

Hi All,
I have compiled alchemical_analysis/pymbar with python_2.7.9 and I could not export the overlap matrix within MBAR procedure, though MBAR free energy estimation worked well.
I got this error:
O = MBAR.computeOverlap()[2]
KeyError: 2
This issue can be easily fixed by editing the alchemical_analysis.py code.

Find this block in the code:

         O = MBAR.computeOverlap()[2]

change the line to this:

         O = MBAR.computeOverlap()['matrix']
I hope it helps,
RD

Thank you!
Was having exactly this problem!


Enhancements to Stake page

I added the price to the top of the Stake page (fixed resulting layout issues for mobile); I also added a listing for a wallet's wrapped staked sb token; added a new section below staked grid to use the price and token totals to calculate balances.

Oops, just realized I forgot to calculate the value of the wrapped tokens correctly using the Index... i'll fix that tomorrow.

ok, calculation is fixed


Migrate to xmlbuilder2?

The creator of the original xmlbuilder package, @oozcitak has reworked it to create xmlbuilder2. Should we migrate to it?
Useful resources

Upgrading from xmlbuilder

// @Leonidas-from-XIV

What would be the advantages for xml2js?

@Leonidas-from-XIV https://oozcitak.github.io/xmlbuilder2/upgrading-from-xmlbuilder.html#comparison-with-xmlbuilder

I looked at this and couldn't find any tangible improvements, hence my question.

Major improvement: get rid of circular dependency ! (XMLNode.js -> XMLxxxx.js -> XMLNode.js => rollup fail)

It turned out to be simplest to just migrate a whole library I never touched before from xml2js to xmlbuilder2 to get rollup to work. So, in a way, there truly aren't any advantages for xml2js.


Added NotificationBanner

Project URL
https://github.com/Daltron/NotificationBanner
Description
Added NotificationBanner to the UI/Alerts Category.
Why it should be included to awesome-ios
NotificationBanner is an extremely customizable and lightweight library that makes the task of displaying in app notification banners and drop down alerts an absolute breeze in iOS.
It also has a built in banner queue system which makes displaying multiple banners that happen within the same timeframe easier than ever.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hey @Daltron thanks for contributing to awesome-ios 🎉🎉🎉


Python: added ollama connector

Motivation and Context

Ollama is a great way to run several smaller models locally, this connector allows that to be used with SK.
Description

Added services and request settings for Ollama.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

BTW Ollama will soon release their own Python client library: https://github.com/jmorganca/ollama-python we could use that eventually.

@juharris I added the link to this to their README and noted that in my PR for that as well, we can def use that then!


[WIP] Similarity search fix

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

What is this?

@srowen fixed description, didn't expect you to be so quick

+1, LGTM. Merging to master.
Thank you, @vitaliili-db.


Add defaultValues to StripePaymentElementOptions

Summary & motivation
We ran into typescript error when using the defaultValues option in Payment Element. This adds it to StripePaymentElementOptions interface.
Testing & documentation
I wrote unit tests.

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


Added class parsing

Fixes https://github.com/giladgray/ts-quick-docs/issues/5

@ryanmcnamara waiting on a push from you to address comments.
also can you enable circle? or, if you'd prefer, i can add you as a collaborator and you can work directly in this repo instead of forking. then you can leverage my existing circle setup.

in fact i might prefer that you reopen this from inside the repo instead of forking so testing locally is simpler...

aaaaand you've been added as a collaborator! mind closing this and re-opening from a non-fork?

For the test: it seems like the ts compiler is putting private vars before public


[Bug]: S3GOV not supported, S3 storage type hardcoded for AWS. This is a regression from 83.1

Terraform CLI Version
1.6.6
Terraform Provider Version
98.0
Company Name
Snowflake
Terraform Configuration
resource "snowflake_storage_integration" "storage"{
  name                  = "S3GOVFEDRAMPHIGHTEST"
  type                  = "EXTERNAL_STAGE"
  storage_provider      = "S3GOV"
  storage_aws_role_arn  = "arn:aws:iam::001234567890:role/myrole"
  enabled               = true
  storage_allowed_locations = [
    "s3gov://mybucket1/mypath1/"
  ]
  storage_blocked_locations = [
    "s3gov://mybucket1/mypath1/sensitivedata/", "s3gov://mybucket2/mypath2/sensitivedata/"
  ]

}

Category
category:resource
Object type(s)
data_source:storage_integrations
Expected Behavior
When specifying an AWS storage integration type I am passing the S3GOV parameter and the terraform resource should pass that same s3gov provider type to Snowflake.
Actual Behavior
The hardcoded value S3 specified in the following file is being passed instead. This worked <= version 83.1 but has been broken since 92.0.link here I believe is the problematic code.
Steps to Reproduce
Build a basic terraform snowflake storage resource and specify the S3GOV type with S3 URLS. You will find the following error: Error: error creating storage integration: 003113 (42601): Invalid location error: Specified location 's3gov://mybucket1/mypath1/' does not match the prefix 's3://' expected by storage provider 'S3'.
How much impact is this issue causing?
High
Logs
No response
Additional Information
No response
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Hey 👋
The solution is already proposed in https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/3213, we should merge it soon and the next released version should be able to handle other s3 protocols.

This is Awesome!
I will confirm the pull request, but this is great news!
On Fri, Nov 22, 2024 at 1:58 AM Jan Cieślak @.***>
wrote:

Hey 👋
The solution is already proposed in #3213
https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/3213,
we should merge it soon and the next released version should be able to
handle other s3 protocols.
—
Reply to this email directly, view it on GitHub
https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/3212#issuecomment-2493371025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYHWLSDZH6KFU6BJVFJGD2T2B355TAVCNFSM6AAAAABSGHF5GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGM3TCMBSGU
.
You are receiving this because you authored the thread.Message ID:
@.***
.com>

--
Stephen Jacobsohn
Staff Cloud Support Engineer
EMAIL  @.***
Snowflake Inc.
450 Concar Drive
San Mateo, CA 94402

Hey @theknowest
Could you confirm that the issue in not happening in the latest version of the provider? Thank you!

Hi Jan,
I can confirm that the issue is resolved on version .99, do you want me to
confirm with another version?
On Fri, Dec 6, 2024 at 8:58 AM Jan Cieślak @.***> wrote:

Hey @theknowest https://github.com/theknowest
Could you confirm that the issue in not happening in the latest version of
the provider? Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/3212#issuecomment-2523434353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYHWLSA5DXPVYQR5LT7TIEL2EG3Q3AVCNFSM6AAAAABSGHF5GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTGQZTIMZVGM
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

--
Stephen Jacobsohn
Snowflake Technical Account Manager
EMAIL  @.***
Snowflake Inc.
450 Concar Drive
San Mateo, CA 94402

I only need confirmation about v0.99.0 (as the fix was applied there). It's great to hear it works now. Closing the ticket.


Error when running out of sources

Unable to instantiate workbench contribution WorkbenchConfigurationContribution. Error: Handler already set!
    at ExtensionPoint.setHandler (extensionsRegistry.js:72)
    at new GettingStartedService (gettingStartedService.js:59)
    at InstantiationService._createInstance (instantiationService.js:90)
    at InstantiationService.createInstance (instantiationService.js:61)
    at new WorkbenchConfigurationContribution (gettingStarted.contribution.js:147)
    at InstantiationService._createInstance (instantiationService.js:90)
    at InstantiationService.createInstance (instantiationService.js:61)
    at WorkbenchContributionsRegistry.safeCreateInstance (contributions.js:82)
    at WorkbenchContributionsRegistry.doInstantiateByPhase (contributions.js:56)
    at contributions.js:46

Thank you!


The navbar should be fixed at top

Describe the feature
The navbar should be fixed at the top of page and should not scroll with the page scrolling
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

/assign-me

Dear Contributor @Utsavladia ,
You have been assigned this issue. As you begin working on the assigned issue, please ensure that you follow the contributing guidelines closely. This will help maintain the quality and consistency of the project. If a Pull Request (PR) is not created within 5 days from the issue assignment, the issue will be reassigned. We appreciate your understanding and look forward to your valuable contribution.

thank you for giving me this opportunity. I will try to complete it within deadline.

@trishanu-init
thank you for giving me this opportunity. I will try to complete it within deadline.


Cask request: VSCode

Cask details
Please fill out as much as possible. Before you do, note we cannot support Mac App Store-only apps.
Name: VSCode
Homepage: https://code.visualstudio.com
Download URL: https://code.visualstudio.com/docs/?dv=osx
Description: Code Editor from Microsoft

visual-studio-code