How do you expand properties for dom in vue-template? To achieve the effect of dynamic delivery attributes

What problem does this feature solve?
For example, when I use react, the dynamic attributes of the operation of dom:
// The "options" is a object.
<div {... options} />

So I realized the production of the object through the front of the object to achieve the dynamic operation of the div, because I can not determine the property has a fixed set, can only use the program production, react also take this into account so that they describe the render also directly , The direct use of ES6 attribute expansion (... operator) can achieve results.
However, in the vue-template, try the ES6 deconstruction (... operator) also read the entire vue official documents, are to find relevant instructions and documentation.
What does the proposed API look like?
Just as react as simple as providing a parameter argument, setting a dynamic property, or providing something like react, directly supporting the use of ES6's ... object structure.

中文描述版本
What problem does this feature solve?
What problem does this feature solve?
举个例子，我在使用 react 的时候，对 dom 进行动态熟悉的操作：
// The 「options」 is a object.
<div {...options} />

这样我就实现了 通过前面生产 options 这个对象达到对 div 的动态属性操作，因为我无法确定拥有固定的属性设置，只能运用程序生产，react 也考虑到了这一点 所以 react 他们描述 render 中也直接说，直接运用 ES6 的属性展开（... 操作符）就可以达到效果。
但是在 vue-template 中，尝试了 ES6 的解构符（... 操作符）也完整的翻阅了整个 vue 官方文档，均为找到相关说明和文档。
What does the proposed API look like?
就像 react 那么简单，提供一个参数参数，设置动态属性，或者提供 类似 react 那种，直接支持使用 ES6 的 ... object 结构符。

v-bind="object"

@yyx990803 Thanks, It is recommended to join vue official documents, thanks again.


Add more IDs for Ron Estes.

All checks have failed! Oh my! :)
(Thanks for adding these.)

Trying again ...

@JoshData should be OK now

Thanks!


fix: drop table with watermark panic

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Remove the assert when dropping the table since the watermark filter has an additional internal table.
close #8922
Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

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

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

Release note

Also add some e2e tests? 👀


implemented InstanceNorm

Proposed changes
Implemented InstanceNorm (https://arxiv.org/abs/1607.08022).
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

@gboduljak thanks for the contribution! And sorry for the delay on this one. Will review soon. In the interim, could you rebase and resolve conflicts?

@gboduljak thanks for the contribution! And sorry for the delay on this one. Will review soon. In the interim, could you rebase and resolve conflicts?

Sorry for the delay. I was on holidays the last week. I will work on the requested changes today.

@awni Could you review my recent changes addressing your comments?

@awni I have addressed the requested nits and resolved conflicts. Please take a look :)


.sasnb cell execution

Describe the bug
Running multiple cells in a row in .sasnb notebooks leads to errors. Specifically, if you do shift+enter and execute multiple cells, the second, third, ... cells do not wait for cell 1 to finish running. They all try to run simultaneously and not sequentially.
Steps to reproduce
Steps to reproduce the behavior:

Create a .sasnb notebook with a two or more cells that will each take a couple of seconds to run and that depend on each other (i.e., cell 1 creates an output table used in cell 2 and so on...)
Go to cell 1 and press shift+enter as many times as you have created cells (this should lead to multiple cells running at the same time)
See error: you will notice that cell 2,3,4, etc. start executing immediately without waiting for cell 1 to finish. This will cause errors as the needed inputs for cell 2 won't be available yet as cell 1 has yet to finish running.

Expected behavior
The expected behavior in those scenarios is that cells should run one after the other and not simultaneously. The behavior should mimic that of .ipynb notebooks where if you use shift+enter to execute multiple cells, there will be a sequential running pattern and not a simultaneous one.
Screenshots
NA
Environment (please complete the following information):
SAS Viya Workbench
Additional context
NA

also note #402

Note that the Execute Above Cells, Execute Cell and Below and Run All commands do execute cells in queue.

Will it be possible to embed this capability when executing shift+enter? That's the most typical way to run cells in notebooks

Also, from VSCode I am not seeing Execute Above Cells and Execute Cell and Below; if I click on the arrow on the left-hand side to run the cell I still experience simultaneous execution of multiple cells

Will it be possible to embed this capability when executing shift+enter? That's the most typical way to run cells in notebooks

Yes

Also, from VSCode I am not seeing Execute Above Cells and Execute Cell and Below;

It should be on the cell toolbar when focus is in a cell

Also note that you can always call a command via Command Palette, and optionally assign a shortcut.


How to export 1 csv file?

I want to export DynamicDataframe to just 1 csv file.
How can I do it?

.coalesce is the way to go!
closing this issue.


Feature request: Status Message

It would be nice to see the status (activated/deactivated) in the chat (client only).
If I'm underground in a completely mob proof room,  I can't tell if the overlay is activated or not, even if I switch it via the hotkey.

That is a very needed feature! I also miss an easy way to know the status!
@AC-ID : you can see the current status using F3 (near the bottom). That's what I'm doing, but that's a cumbersome way to check status.
IMHO, Light Overplay could have two kinds of status messages:

On F7, prints a timed message (similar to in-game "you can only sleep at night" or  "cat drowned"), so we know if we are enabling or disabling it. I believe this is what the OP requested, and that's a feature I miss a lot. Please implement at least this one!
A permanent message if it is disabled, like a single "Light Level is  DISABLED" written in red on top of the screen, or a more subtle (but always visible) marker. This marker/message could be disabled in options.

The idea is: Light Overlay should always be ON, but in some conditions I turn it off (exploring overworld, hunting mobs, etc), and it's a huge risk to forget to turn it back on when back at base and explored mines, as there is no visual cue that it is OFF,  we assume everything is safe when it might be not.


Is it possible to add support for multiple /azp commands in a single comment?

Each time I need to execute 5 pipelines, I leave 5 comments, one for each pipeline. And then I get 5 bot responses back, and it clutters the PR comments.
Would it be possible to add support for me to specify multiple commands in a single comment, say, each starting with a newline?
Or, comma-separated? Or maybe there can be a new command for triggering multiple pipelines?
I would also ask to add a something like /beQuietIfSuccessful switch so that I don't get 5 comments back from the bot. I'll know that if it is quiet, it must've started all the pipelines that I asked for (from what I remember, it's always been so). And if I don't see them popping up in a reasonable time, I'll retry without the /quiet switch and will know that there is a problem that the bot is not responding, and I'll act on it. But I think all will be fine 99% of time.
Alternatively, if I could get a single comment from the azp bot after I asked it to run 5 pipelines via single comment, I can live without /quiet switch.
cc @Jinming-Hu

cc @danieljurek, @weshaggard

The /azp command is handled by Azure DevOps so we cannot really add that support.
Instead, I would ask the question why are you manually triggering 5 pipelines? Should we be adding trigger paths to those pipelines to have them trigger automatically based on changes?


Add version: ransome1.sleek version 1.1.9

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Update README - unencrypted SMTP connection

Description
PR is adding information to README how to adjust SMTP_SECURE_TYPE parameter in case of insecure SMTP connection. There was no such information in current version of README.
Tests
Tested with success on following environment:

kubernetes 1.27.0
docker.io/boky/postfix:v3.6.1-ubuntu
docker.io/tiredofit/self-service-password:5.2.3

@tiredofit bumping this PR ;-)


Adding an enhancement for checking image existence using the container-runtime.

/cc @yevgeny-shnaidman @mresvanis @TomerNewman

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.62%. Comparing base (fa23a9b) to head (ae33536).
Report is 131 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #915      +/-   ##
==========================================
- Coverage   79.09%   72.62%   -6.48%
==========================================
  Files          51       65      +14
  Lines        5109     4493     -616
==========================================
- Hits         4041     3263     -778
- Misses        882     1045     +163
+ Partials      186      185       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

There is one  more scenario that we need to handle:

user creates a KMM module
Module NMC creates a MIC
MIC controller tries to pull the image, image is missing and the MIC status is updated accordingly
user creates an images in the repo
user triggers module's reconcilaition
MIC reconciliation is not triggered since MIC spec is not changed

We might consider adding some counter to the MIC spec , so that Module NMC might update it and thus trigger reconciliation.

There is one more scenario that we need to handle:
user creates a KMM module
Module NMC creates a MIC
MIC controller tries to pull the image, image is missing and the MIC status is updated accordingly
user creates an images in the repo
user triggers module's reconcilaition
MIC reconciliation is not triggered since MIC spec is not changed
We might consider adding some counter to the MIC spec , so that Module NMC might update it and thus trigger reconciliation.

What do you think about just adding the ImagePullPolicy from the module to the ModuleImagesConfig correct entry?
We are using this ImagePullPolicy in the init-container so we can use the same policy for checking if the image exists

Checking the image existence and pulling it will be consistent
We don't need to handle any user race condition - if he override the image, he should use ImagePullPolicy=always to always pull or delete the image on the node manually before re-triggering the reconciliation.

WDYT?

/lgtm


There is no option to upload the new theme and plugins.

Please provide option to upload themes and install plugins after the installation.

try to upload to public/wp-content/themes   or /plugins   , as per your usual wordpress installations.
Or try to write it into composer, neater.

Something else which may be good is to figure out which plugins / other configuration is disabling the "Upload Theme" button from the appearance tab after default install / deploy.

Perhaps wordpress recognises the inherent "ephemeral" nature of the heroku file system. Even if you can try to upload or install something from the app, it will go missing when your heroku app restarts itself, you can read the heroku documentation for more details.

Super relevant point! I agree.
On May 1, 2017 8:06 PM, "punggolzenith"<EMAIL_ADDRESS>wrote:

Perhaps wordpress recognises the inherent "ephemeral" nature of the heroku
file system. Even if you can try to upload or install something from the
app, it will go missing when your heroku app restarts itself, you can read
the heroku documentation for more details.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/xyu/heroku-wp/issues/122#issuecomment-298486597, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKIgAvXflEJA0s31GFBjndZiBwns-mMks5r1p2zgaJpZM4NMpuj
.

@punggolzenith / @abeering yup exactly on point with the ephemeral FS and problems with allowing uploading of things in WP. This is why I've set DISALLOW_FILE_EDIT and DISALLOW_FILE_MODS explicitly to disable this. :)
https://github.com/xyu/heroku-wp/blob/nginx-php7/public/wp-config.php

If not an Upload option then can it be made possible to push a theme to added into wp-content/themes/ using a git push

I've done this in public/wp-content/themes and this does not work - the code is committed and theme doesn't appear


Interface to easily programmatically score many models locally on public benchmarks

After the update, it seems that brain-score deprecated the interface to easily programmatically score many models locally on public benchmarks. This is essentially the function achieved by this tutorial but now it is deprecated.
As a user of brain score, I think this use case is still very desirable because it is often the case that users want to do some quick prototyping of many different models (could be the same model architecture but trained with different hyperparameters, etc.) on a small number of public benchmarks before submitting to the brain-score full benchmark. When doing quick prototyping, users may want to keep the code for model definition (defining pytorch models, loading weights, etc.) in their own repository instead of registering the model in the brainscore_vision/models (writing all the init.py files, etc.) each time they want to score a new model with perhaps just a small variation, because this could be tedious and time-consuming. It would be great if brain score could still support this use case or perhaps use some script to automate model registration process (writing all the init.py files in brainscore_vision/models, etc.) while allowing users to keep the model definition in their own repo.
I figured out a little hack to make it work though, but this may not be ideal since it bypasses many new features such as dependency check and score saving. (https://github.com/brain-score/vision/issues/533#issuecomment-1937820878)

I'm guessing the ideal would be either
from brainscore_vision import score, model_registry

model_registry['mymodel'] = ...

myscore = score(model_identifier='mymodel', benchmark_identifier=...)

or
from brainscore_vision import score

myscore = score(model_identifier='mymodel', model=mymodel, benchmark_identifier=...)

Is this right?
@kvfairchild from how locate_plugin works, option 1 seems quite difficult to implement, is that right?

Yes, either of them would be great, and what I have in mind is that this should work in user's own repository after installing brainscore.

@kvfairchild from how locate_plugin works, option 1 seems quite difficult to implement, is that right?

It could be done but I think option 2 is cleaner and makes more sense for the use case. A lot of the functionality in ImportPlugin and CondaScore is to support the leaderboard scoring and not really necessary for this type of local development, so the simplest solution would be to bypass those altogether if a model is passed directly to score.

could this then not just be as simple as
def local_score(model: BrainModel, benchmark_identifier: str) -> Score:
    benchmark = load_benchmark(benchmark_identifier)
    score = benchmark(model)
    return score

?

Is the pain point maybe in wrapping the model? We could add an example for doing this, e.g.
from brainscore_vision.model_helpers.activations.pytorch import PytorchWrapper
from brainscore_vision.model_helpers.activations.pytorch import load_preprocess_images

def get_model():
    model = torchvision.models.mymodel(pretrained=True)
    preprocessing = functools.partial(load_preprocess_images, image_size=224)
    wrapper = PytorchWrapper(identifier='mymodel', model=model, preprocessing=preprocessing)
    wrapper.image_size = 224
    return wrapper

activations_model=get_model()

mybrainmodel = ModelCommitment(
    identifier=activations_model.identifier,
    activations_model=activations_model,
    layers=mylayers)

Yes, the local_score could be very simple.
The concerns I had when first doing something similar to local_score is that:

It bypassed some new functions such as ImportPlugin and CondaScore, as a user I don't know what these are doing, so without confirmation that something like local_score could work, I am unsure this would give me the correct result, and it feels a little hacky.
It bypasses the save_score function in brainscore, so the user has to save the score separately, and when rerunning the same benchmark on the same model, some computation has to be rerun. Since brainscore already implemented some function to save/cache the score, it would nice if local_score could reuse these. (this is just a small suggestion to further improve the user experience and it is unrelated to the core function, I understand there may be other considerations that make this not necessary now.)

Some examples about how to wrap the models and score them locally using local_score in the tutorial would be awesome! They would show the user this is also a supported use case (if the team wants it to be), so that they won't be unsure about whether they did the right thing or not.


TestFlight - The Info.plist file is missing the required key: CFBundleShortVersionString

Unstoppable is having issues uploading  to TestFlight because of the following error:
*** Error: Asset validation failed The bundle 'Payload/Unstoppable.app/Frameworks/libzcashlc.framework' is missing plist key. The Info.plist file is missing the required key: CFBundleShortVersionString. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring (ID: 62d555af-4a1b-453c-b572-e6a14ecf4a55) (90057)
Seems like Zcash library is missing some plist keys.

Fixed in SDK 2.1.10


Custom fields

I wanted to have some extra fields other than the ones documented. I figured out a few by my own such as date and guid, but I still needed fields such as author and categories for each entry.
If there is already a way to set those, I could not get it right, and it is not documented I believe.

By using a create function you can use all the features from https://github.com/jpmonette/feed ☺

I'm still not being able to get the author and image fields to populate, the module simply ignores those.

@arctouch-arthurrolim then it must be an issue of the above linked module, not the nuxt wrapper


Fix issue with Tor Logo and website resizing

Currently there's a weird issue where the Tor logo can be larger than the navbar in large screens. Let's work on addressing this issue.

This can be extended and clean up style.css.

Apparently this issue only appears in Mac OS X Safari and only when in Full Screen Mode. Let's see if we can get this fixed this time for good.

@DaKnOb Is there any other way to reproduce this bug other than in Mac OS X Safari?

First pull request as part of Hacktoberfest - hopefully all is correct, but I believe I have resolved the issue in my referenced request above.

Fixed with Pull Request #27 and Commit 523153d


How to add a second go-e Charger?

I am unfortunately not able to add a second go-e charger due to the following issue:
Platform goecharger does not generate unique IDs.
How could I solve the problem?

Are you sure you are using this custom component because a unique ID is generated in general here.

Yes - I was directly referred from the home assistant page when clicking in "documentation"...

Interesting. I will have a look! :-)

Many thanks - if you need further information please let me know. In the meantime I try to start the complete setup again... maybe I had some issues in my setup process

Is there something specific I need to include in the field "base topic"? Is there any specific format needed for the serial number?

First of all you should be able to add the component multiple times to talk to different chargers. IMO a missing unique ID shouldn't have an impact here.
The base_topic depends on your charger version & firmware. This is the expected pattern to be able to auto-discover your devices: https://github.com/syssi/homeassistant-goecharger-mqtt/blob/main/custom_components/goecharger_mqtt/config_flow.py#L79-L82

ok... to be honest - I do not know what to do with this (sorry!).
I am even not able anymore to add again the first go-e charger which worked before... And I think it was auto detected before. I also know from the MQTT Explorer that both send their values correctly to the Mosquitto broker...

first device is running again after using my backup... but second one is not discovered and I do not really understand what to do or where I could find helpful instructions...

Could you try to subscribe to your mosquitto broker and provide some received messages (including the topics) of both devices? Do you know how to monitor the MQTT traffic manually?

I am able to see all the details send using MQTT Explorer, but I do not know how to monitor it using the Mosquitto broker. Anyway the MQTT is connected to the Mosquitto broker and should therefore show all data

Based on the Mosquitto broker the Base topic seems to be go-eCharger/233782/
Anyway I am not able to get it running using the integration. But when monitoring the MQTT Explorer all information are correctly forwarded to the Mosquitto broker. Both go-e Chargers are identical.... same firmware etc. The other one is running without any issues...

Could you tell me the base topic of the working one? Does it start with a / or not?

without a /
but I tried to setup the go-e Charger with several combinations for the base topic considering with / and without

now it worked ;-)
After a high amount of restarts and even shutting down the system I was able to have it running now... for the base topic I just have included "go-eCharger" and with the serial number it resulted in an autodetect ;-)...
Many thanks for your support!


SA1206 and IDE0036 disagree on modifier ordering of file keyword

In the code snippet static file class ElementsMarshallingCollectionSourceExtensions {}, IDE0036 from the compiler puts the file keyword after the static keyword, but SA1206 says to put the file keyword before the static keyword.

Regarding IDE0036, I do not experience the same behaviour that you are describing and https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0036 also says it expects file before static, at least by default. Are you sure you read the IDE0036 hints correctly? If IDE0036 really is behaving the way you say without you having reconfigured the desired order, I suggest you file a bug report over at https://github.com/dotnet/roslyn.
Regarding SA1206, this is the intended behaviour. There are un-released bug fixes concerning the code fix for SA1206, but the diagnostics were correct before as well if I am not mistaken.

Yes, I have IDE0036 configured to error in my build and it's causing an error if I do file static. This might be a bug on IDE0036 and not on SA1206.

Found the problem. SA1206 doesn't respect the csharp_preferred_modifier_order editorconfig option, so when a custom value for that option is set, IDE0036 and SA1206 can get out of sync.

See https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1206.md for a brief description of what SA1206 expects. And note that file is treated as an access modifier in SA1206, so it expects it to come first in your example. SA1206 is weaker in its ordering compared to IDE0036, since it only requires the three groups of modifers to be in the the expected order, without caring for the order within each group, whereas IDE0036 is more strict and requires the exact order you have specified (or according to its default).
If you want a customized modifier order, then turning off SA1206 and going with IDE0036 instead is the way forward for you, in my opinion. @sharwell, do you have another opinion on this?

Yeah file is an access modifier:
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/14245e2d8f2a86abd03f73d51b38acb40ddf6665/StyleCop.Analyzers/StyleCop.Analyzers/Helpers/ModifierOrderHelper.cs#L50-L51
I believe this is the only logical classification for this modifier.
Since IDE0036 is strictly a more complete analyzer than SA1206, there is no need to run them both at the same time. The following are supported scenarios:

SA1206 enabled, but IDE0036 disabled
IDE0036 enabled, but SA1206 disabled
Both IDE0036 and SA1206 enabled, provided the modifier order defined by IDE0036 adheres to the partial order defined by these buckets for SA1206

While option 3 is supported, it is not recommended.


Add a capability to allocate load balancer ip only on hosts which interfaces belongs to subnet specified in the kubevip config for namespace

Please Add a capability to allocate load balancer ip only on hosts which interfaces belongs to subnet specified in the kubevip config for namespace.
Scenario:
Secured k8s deployment where control plane  and worker nodes resides in different subnets
Current behaviour:
for example you have this subnets:
1)Control-plane <IP_ADDRESS>/24
2)worker nodes sub: <IP_ADDRESS>/24
Load balancer ip for ingress NGINX from pool configured would be assigned to control-plane nodes and obviously would not work.
Proposed behaviour:
with some config flag ( or may be by-default) kube-vip would follow subnet ranges of host interfaces and would allocate load balancer IP addresses only on nodes that belongs to subnets in config

Is the new auto feature doing the trick?
It only works in arp mode, but instead of defining the ip and subnet mask manually it is auto discovered from the node the service ist running on.
Additionally there are new annotations for services.
Please check out the new release.


I deleted all the nodes with remove-node, how do I add the localhost node back?

ok maybe im just really dumb or no one ever thought of this scenario.
on a test machine I deleted all the nodes with remove-node, even the last controller node, now there are no nodes in my microk8s setup, and im wondering how i can add the machine that i am running microk8s back as a node.
when i use add-node, then try to join, microk8s tells me that its not possible because the machines share the same ip (obviously)
any ideas or is this just something that should never be done and cant be recovered from

I recall theres a --force argument in the remove-node that will remove it also from dqlite.

You can remove the snap and reinstall it again

yea thats what I did, but there must be another solution surely?

Had a slightly different issue. My workers weren't working (no pun intended) so I applied a patch to them. However that presents an issue with reverting the patch changes when joining from another node. In conclusion, I get the following impossible to remove node now.

I think I've literally run into every issue in microk8s so far 😞


Find next/previous unusual behavior

Hello there,
Not sure if this is a bug or designed behavior, but here is my issue:
For example, we have some text in editor, and we start search for some word.
We have several matches found and go through them by pressing Find next.
Then, we decided to press Find previous to move to previous result, but nothing happens and if we click Find previous again we will move to previous result as expected.
Same, if after pressing Find previous we decide to press Find next, two clicks are required to actual move to next result.
Is there any way to change this behavior? So, if we click “Find previous” right after “Find next” it moves to previous result.

This happens because the cursor is moving first or last in search item. I think it would be better if it stays last...


Feat: add degen to deployments

Deploy Multicall3 to Degen

Thanks! Can you verify the code first? I was unable to verify it, and the bytecode is much shorter than the bytecode on mainnet, and blockscout usually can automatically verify the Multicall3 deployments so I suspect this one has e.g. an incorrect number of optimizer runs or even a different version.
The production settings for Multicall3 can be found here, so want to make sure this deploy matches: https://github.com/mds1/multicall?tab=readme-ov-file#contract-verification

Closing as stale due to lack of response


Is this still working?

Not sure what changed but I keep getting a "Reference Error: Instafeed is not defined"
Compared to the guide, instafeed.min.js needs to be declared as "type=module".  Doing this change and keeping the rest as before there is this new "ReferenceError: Instafeed is not defined" error.
I saw on a post for something else that this might be due to calling the script before the source has been loaded. I declare the source script in the head with no changes and I also tried delaying the call with a jQuery.read. Still the same error.
I´m not fluent on web development so there might be an easy fix on the way to declare the new Instafeed. Or I might be completely wrong and it´s still working.

Howdy!
I haven’t made any updates to this library in a few years, and as far as I know should still be working.
That error message you mentioned sounds related to ESM Modules to me.
I think you can get that error when an ESM module tries to require a non-ESM module.
Are you using a build system or anything to compile/bundle your assets? An upgrade of a build system could have maybe switched a default to use ESM?

First, thanks for answering!
I´m using the web-page builder from ionos which is super limited! You can however embed html/javascript and that´s what I did in the past. It was working for a long time. Since a few months back it stopped working with this message.
No idea of what ESM Modules are (as stated I don´t know much on web development, as I´m a backend developer) and no idea if I can do something to change it from this limited web-page builder. I will dig a little bit into the subject.


Is it possible to integrate postcss?

I would like to integrate postcss in order to use autoprefix and other plugins, but looks like it is not supported. So, two questions:

Is it going to be supported in the future?

Is there a easy way to integrate postcss in my current project with angular-cli?

Keep up the good work! =)

+1

See https://github.com/angular/angular-cli/issues/1656

Dupe of https://github.com/angular/angular-cli/issues/1512


luci-app-frpc: some improvement

fix local_ip data type
add plugin options
show remote port on overview page
some translations fix

Please update your commits with a valid Signed-off-by with your real name and a valid mail address.
See the other commits.

ok, I will check it

pushed to master https://github.com/openwrt/luci/pull/5935


Revisit IAM library API (PolicyDocument, PolicyStatement)

Reconsider the fluent API for PolicyStatement
Make autoAssignSids immutable and more to ctor option (requires breaking ctor signature)

@rix0rrr is this closed?


the lesson does not show all the tests in this Challenge(Stand In Line) as passed, whereas all  other tests have passed.

Challenge Stand in Line has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function queue(arr, item) {
  // Your code here
testArr.push(item);
  var shifted = testArr.shift();
  //console.log(testArr);
  return shifted;

}

// Test Setup
var testArr = [1,2,3,4,5];

// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(queue(testArr, 1)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));

this has been a mistake !! the Test was not passing as the value array that was used was actual array name instead of the argument !! Sorry for any inconvenience.

I have the same problem in that problem.
`function queue(arr, item) {
// Your code here
testArr.push(item);
item=testArr.shift();
return item;  // Change this line
}
// Test Setup
var testArr = [5,6,7,8,9];
// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(queue(testArr, 1)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));`

Failed Test case:
queue([5,6,7,8,9], 1) should return 5

I finished doing this:
var testArr = arr;
testArr.push(item);
var shifted = testArr.shift(item);
return shifted;


Allow custom build directory

Closes #171

[X] Add -C flag to meson commands
[x] Add tests and verify that compilation happens in right place

@lagru Ready for testing.

@lagru Please take another look; the build directory can now be absolute, and can be set using SPIN_BUILD_DIR, which is helpful for creating an alias. I also updated the alias to be a better example, showing how to set the compiler to clang and build into a different build directory using clang.

Nice!
I was just about to suggest this feature. I just gave it a quick er... spin and it seems to work exactly as I wanted.
One suggestion though:
When you run meson setup build-dir it adds a .gitignore to the build directory. I already have a .gitignore entry for the build-install directory but if I do:
meson setup build-release -Dbuildtype=release
spin -C build-release run ...

Then the build-release-install directory is created but it does not have any .gitignore file. Perhaps spin could create the directory and add the .gitignore file before running meson install.

@oscarbenjamin What you request sounds very reasonable, but it's already the way my setup behaves:
$ spin build -C build-xyz && ls -al build-xyz/.gitignore
-rw-r--r--. 1 stefan stefan 92 Sep  2 21:05 build-xyz/.gitignore

I see the same behavior when adding the -Dbuildtype=release flag.

it's already the way my setup behaves:

I've just checked again and confirm that the .gitignore is not added here:
$ spin build -C build-foo -- --pkg-config-path=.local/lib/pkgconfig -Dadd_flint_rpath=true
...
$ git status
On branch pr_nmod_ctx
Your branch is up-to-date with 'origin/pr_nmod_ctx'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	build-abc-install/
	build-foo-install/
	build-xyz-install/

nothing added to commit but untracked files present (use "git add" to track)

Is it meson that adds it in the meson install step?
I didn't expect that meson install would do that so it didn't seem surprising that the .gitignore was not being added.


Support 'version_type' to allow triggers on 'major' or 'minor' version number

Hi, we have a problem with Pivnet Resource updates when new stemcell is released. In our pipeline, we want it to trigger only if the new released stemcell has higher major version than our current one. Right now, we have a task there to take both version numbers as inputs and compare them in the task container. The container will return true or false, so our pipeline knows if it should proceed or not. It is working but the issue is that it will make the job RED if false, which makes our pipeline look bad.
For example, pivnet resource is triggered now for 3146.12 since it is the latest release (timeline wise) in pivnet. But in our pipeline we already have the latest version 3232.4 (version wise). We don't want it to update in this case.
For our case we would like to have something like:
  - name: pivnet-stemcells      type: pivnet      source:        api_token: _sample_token_        product_slug: stemcells        version_type: major
version_type: minor | major

Sounds good. There's already a story for this: 117119027 with a proposed version of minor|major just like you suggest.
As noted in the story, I think it would be cleaner to support a version regex, with semantic versioning support, similar to how some of the other concourse resources (e.g. the s3 resource) behave.
If we went down the regex route I would imagine seeing something like:
source:
  api_token: _sample_token_
  product_slug: stemcells
  version: (.*)

And the versions that came back would be ordered sematically, meaning your use-case would be solved.
However, I think that version_type is quite a bit easier to implement, so we might prefer to do that first.

+1!
The version regex option would also solve a problem that PCF Release Engineering have recently encountered where we would like to pin to a particular major/minor version and just float on the patch level of the release.

Thinking about this some more, my first suggestion of version_type: major|minor and the story I originally linked to is not relevant here; I was thinking of release_type but in the example given of stemcells, both of the stemcells are Security Release so we can only differentiate them from the version numbers.
So, the only way to solve this is by parsing the version number and ordering semantically.
@davewalter your requirement is a subset of the one @xtremerui wants - you both want to filter on versions but you don't care about semantic ordering (and @xtremerui doesn't care about pinning to major/minor versions).
There's a story to tackle the first part (filtering on regex):

pivnet resource check should filter on version via regex in source config

and then there's a placeholder story to tackle the extension of this to return the versions ordered semantically:

PLACEHOLDER: allow (force?) some sort of (semver?) regex for check / in / out

We can more easily scope the second story (semver ordering) once we've implemented the first.
Sound good?
Thanks,
Rob

Sounds good. We only care about semantic ordering in so far as we want the highest version that matches the specified regex. Given that we are extremely unlikely to release a lower patch number of a specific major/minor release after a higher one, the order should take care of itself.
Thanks,
Dave

That's what I was expecting your workflow looked like - thanks for clarifying. I'll close this issue now, as the necessary stories have been created and prioritized.


Select component still renders material SVG icon even with native prop set

When the 'native' prop is added to the Select component, the SVG icon is still rendered even though this is not needed/wanted when specifying native since the SVG icon is being rendered on top of the native select element's scrollbar.
This issue is visible as rendered even on the documentation page:
https://material-ui.com/components/selects/#multiple-select in the Multiple Select section.

As a workaround, if I wrap the select as below, the icon disappears.
const StyledSelect = withStyles({
  icon: {
    display: 'none'
  }
})(Select)

Seems like when native is specified it should not render the redundant SVG icon.
Thanks!

@craigmjackson Thanks! Would you like to try and fix it?

Sure, I'll give it a shot.  Just wanted to make sure this is not following some upstream behavior in the material spec.  Now that you label it as a bug I will figure out how this whole github pull request thing works. :)

This should help: https://github.com/mui-org/material-ui/blob/master/CONTRIBUTING.md#getting-started

@craigmjackson Maybe something like this?
diff --git a/packages/material-ui/src/NativeSelect/NativeSelectInput.js b/packages/material-ui/src/NativeSelect/NativeSelectInput.js
index 0ef5ff351..5dd73c916 100644
--- a/packages/material-ui/src/NativeSelect/NativeSelectInput.js
+++ b/packages/material-ui/src/NativeSelect/NativeSelectInput.js
@@ -25,7 +25,7 @@ const NativeSelectInput = React.forwardRef(function NativeSelectInput(props, ref
         ref={inputRef || ref}
         {...other}
       />
-      <IconComponent className={classes.icon} />
+      {props.multiple ? null : <IconComponent className={classes.icon} />}
     </React.Fragment>
   );
 });
@@ -58,6 +58,10 @@ NativeSelectInput.propTypes = {
    * @deprecated
    */
   inputRef: PropTypes.oneOfType([PropTypes.func, PropTypes.object]),
+  /**
+   * @ignore
+   */
+  multiple: PropTypes.bool,
   /**
    * Name attribute of the `select` or hidden `input` element.
    */

I thought about trying to do the conditional in the NativeSelectInput but wasn't sure the props references would make it there from the Select component.  I was really scratching my head last night trying to do some hackish thing overriding the styles in Select which made a lot of other tests fail.  I have the test failing in Select.test.js that is finding the svg as an expected failure, and I will try your approach tonight and see if I can make it pass.  Really appreciate the warm welcome by helping me through this!

Here goes: https://github.com/mui-org/material-ui/pull/16992
Thanks again for the help.

Great :)


Share/Export Button

First, a preface: I found you via https://alternativeto.net/software/podcatcher-by-yoav-frandzel/. In a list full of corporate portals and obscure CLI scripts, CPod really stands out. I am so impressed with it. It's already so close to perfect: it's beautiful, easy to use, easy to find shows in.
It passed the mom test: my mom figured it out in about 30 minutes. I think that's pretty solid, right there.
Now, for my request:
CPod version: 1.27.1
Description:
On AntennaPod every podcast (and episode) has a bunch of "share" options: I can export the podcast's RSS link, its main website, or an episode's page (if it exists), or an episode's audio file URL.
Right now there's no way I can see to get these links out of CPod. I guess I could poke around ~/.config/cumulonimbus/Local\ Storage/leveldb/ but I don't know where to look.
Please add a way to get the podcast's address out of the Details view. A "copy feed URL" button would be good, or displaying it and making sure it's copyable in the extra details added as part of #210 would work too.
Being able to get similar details from the Player view would be great, too, but I recognize that that's more work.

Could a bounty be set for this?


styling: alignment landingpage & header btn

removed class padded  - the padding were in conflict with ui container
target bottom padding ui.flashed.message for landing page - recordMangement.
removed navbar-item.navbar-button css, to make alignment correct with the body.
closes #517

screenshots

@mb-wali Can you try another rebase and force push (rebasing is still disabled because of conflicts).


Table driven tests for Repeat()

Current tests for repeat may be incomplete.
Which File
github.com/chewxy/gorgonia/tensor/f64/matop_test.go
Which function
TestRepeat
What to Test

Repeat scalar on 1, 2, n axes
Repeat colvec on 1, 2, n axes
Repeat rowvec on 1, 2, n axes
Repeat vector on 1, 2, n axes
Repeat matrix on 1, 2, n axes
Idiotic actions a user might do (these should all return errors).

@alienchow did good work


Forcing non-tile-aligned reshapes to ROW_MAJOR

If the desired shape in a reshape op has either of the last two dims not tile dim aligned, they must be in ROW_MAJOR. The compiler does not yet model memory config/layout. After #818  is merged, this workaround will be in place:
if (in.get_layout() == ::ttnn::TILE_LAYOUT &&
      (shape[shape.size() - 2] % 32 != 0 ||
       shape[shape.size() - 1] % 32 != 0)) {

    in = ::ttnn::to_layout(in, ::ttnn::ROW_MAJOR_LAYOUT, std::nullopt,
                           std::nullopt, in.device());
  }

In runtime/lib/ttnn/operations/data_movement/reshape.cpp

We have an open issue on the TT-Metal side to fix this:
https://github.com/tenstorrent/tt-metal/issues/12866

@sdjordjevicTT That seems like a different issue. In my case the reshape call will throw an error rather that giving garbage output

It is probably because we didn't specify the tile output shape properly(including tile padding). Once we do that, you will get the wrong results as well.

@LPanosTT do we have some simple repro that I can check when consume new metal version, to test if it works?

@LPanosTT do we have some simple repro that I can check when consume new metal version, to test if it works?

I supposed creating a 10x10 tensor then setting it to tile layout, then reshaping it to 1x100 would show whether or not it was fixed. You'll have to check that the data is correct of course.

@dgolubovicTT please sync with @mtopalovicTT and @jserbedzijaTT. Metal folks did an additional fix for this a day ago, hence we should verify this once we uplift the metal to the latest.


Coinbase and other crypto domain blocked

It looks like https://github.com/StevenBlack/hosts/pull/868 began blocking valid crypto-currency exchange domains (e.g. coinbase.com, bittrex.com, etc.) that aren't involved with browser mining.
This issue seems to have been brought up before by another user with: https://github.com/StevenBlack/hosts/issues/509

Looks like the last release added https://gitlab.com/ZeroDot1/CoinBlockerLists which blocks everything Crypto related.
I also require the use of a lot of those domains.

Bump. This is affecting me as well. This is blocking a ton of valid cryptocurrency, non-mining related domains.
cc/ @StevenBlack @FadeMind

Shit.  Thanks everybody.  Reverting now.


[INTERNAL] Azure Pipelines: Rerun tests with native AVA output on failure

Also name all steps properly

Coverage remained the same at 91.143% when pulling ce01602291b073a6a10d943c5d9f653d1e377d45 on azure-pipelines-test-failure-reporting into 0bf7880c8b16c7350c643bb235ef23c10248b109 on master.


Dynamically configure SemaphoreBackPressureHandler with BackPressureLimiter (#1251)

:loudspeaker: Type of change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring

:scroll: Description

This change enhances the SemaphoreBackPressureHandler with the support of a new BackPressureLimiter interface.
This BackPressureLimiter interface is to be implemented by applications. It has a single method int limit() that returns a number of permits that can be consumed by the SemaphoreBackPressureHandler.
Before each polling, the limit will be checked by the SemaphoreBackPressureHandler and adjust the number of permits that can be requested (in the range [0, totalPermits]). The limit returned by the BackPressureLimiter#limit() method is to be understood in terms of number of messages that can be consumed from the queue at the current instant. If 0 (or less) the queue consumption is considered to be on standby.
When a polling is performed and the consumption is on standby, the SemaphoreBackPressureHandler will sleep the standbyLimitPollingInterval before allowing for a next polling attempt (we cannot rely on the semaphore acquire timeouts here, hence the need for standbyLimitPollingInterval.
Both the BackPressureLimiter and standbyLimitPollingInterval can be configured via the ContainerOptions
:bulb: Motivation and Context

The goal of this change is to address #1251.
#1251 aims to provide a more general solution to issues like #481 by giving control to users on how they would like to dynamically limit messages consumption from an SQS queue. Typical use cases could be rate-limiters (like #481) or more complicated setups involving measuring the load of a downstream system and adjusting or stopping the messages consumption
:green_heart: How did you test it?
The testing was so far only tested via integration tests which tested various scenarios:

static limit being 0, totalPermits or more, and various values in between.
Dynamic limit changing, and checking the queue processing adjusting itself (in a "synchronized" way)
Dynamic limit changing, and checking the queue processing adjusting itself (not in a synchronized way, so more realistic of what will happen, but harder to make strict assumptions on the moving target)

:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Collecting feedback on the approach
Work on updating the reference documentation to mention the new capability.

@loicrouchon If i read this correctly and i would need to build #481 with for example process 5 messages every second.
I would need to implement the BackPressureLimiter, with a logic to set/increase the limit to/with 5 for every second?
As every message received would substract one of the BackPressureLimiter.

@jeroenvandevelde, the goal of the BackPressureLimiter is to provide an information on the maximum number of messages that can be read from the queue in the next polling cycle. This is done by calling the BackPressureLimiter#limit() before trying to acquire permits to poll messages from the queue.
However, it does not consider how many messages are currently being processed by the queue consumer, nor does it check again the current BackPressureLimiter#limit() after obtaining permits if this number should be reduced.
So what you would need to do to implement a rate-limiter is a 2 step approach.

rate-limit implementation: In the queue consumer, you would need to protect sending messages to the rate-limited API using to effectively wait before sending an API call if you're over the limit. This will ensure the hard constraint on the rate limit is being applied.
Making the queue rate-limit friendly: Configure the SQS container with a BackPressureLimiter#limit() that reads the current API rate and translates it into a limit. This will allow the queue consumption to avoid polling messages which would have to wait and therefore potentially exceed the the visibility timeout.

In case the rate-limit is not a hard limit (i.e. meaning you can temporarily have short bursts over the limit), then 1. is not necessary.
So rate-limiting can somehow be performed, but it requires extra care if there are hard constraints regarding the rate limit. The solution implemented in this PR primarily aims at use-cases where the pressure is measured from an external system and in which case there is by design a delay between the measure of the pressure on the downstream system and reacting to it.
A good example would be when pushing messages to another system (could be another queue for example). In this case, the BackPressureLimiter#limit() could be built in such a way it would measure the pressure on the system and map the pressure level to a certain limit.
For example, in the case the downstream system is an SQS queue:

If the number of visible messages < 10, then limit = total permits (full speed)
If the number of visible messages < 100, then limit = 50% of total permits (reduced speed)
If the number of visible messages < 100, then limit = 0 (standby)

PS: the advantage of the example pacing messages publication to a downstream queue might not be obvious, but there are two:

The regular resources consumption one: Avoids consuming cluster resources (CPU, memory) and other systems' resources involved into the process of publishing that message so that critical systems have more bandwidth to catch-up.
Allow different publishers to publish messages with different priorities. One publisher might be low priority and should stop publishing messages if there is a high load, while another might have a higher priority and should not stop yet

I missed the fact than that if it reads a message it doesn't subtract it from the limit.
In my case where i would like to have a max rate of x messages / second, your approach seems a bit weird as all the information for this is available in the library.
How fast are we processing and the rate at which we would like to go (configurable value).
So therefore i would prefer to not push the complexity of keeping track of how many messages we are retrieving and change the limit based on that to the user of the library.
I can follow if it is based on parameters outside of the library, which your case sounds like.
In the coming days, i will take a look if i can find an alternative way to do this.

How fast are we processing and the rate at which we would like to go (configurable value).
So therefore i would prefer to not push the complexity of keeping track of how many messages we are retrieving and change the limit based on that to the user of the library.

@jeroenvandevelde I think this information is only fully available in a very limited number of use cases. Most of the queue consumer implementations I had to implement in the past were doing a variable number of API calls. It usually depended on the content of the message being consumed, some persistent state, or the result of previous API calls.
So limiting consumption from the queue at a fix rate-per-second is not accounting for cases where the rate-limited API we're trying to protect would be called a variable number of times (0 times or more). That is why in the solution presented here the BackPressureLimiter#limit() performs a measure of the pressure and then translates into how many messages can be consumed at that point in time. It does not do a computation of many it allowed/how many it can still allow.
I totally agree with you, it is more complicated than the use case you described. But it would avoid the issue of blocking the queue consumption for messages that did not triggered the API call that should be rate-limited.

I will try to find some time in the coming days to look if i can find an alternative way to do this.

Please do so, and let me know about your findings.

I think this information is only fully available in a very limited number of use cases. Most of the queue consumer implementations I had to implement in the past were doing a variable number of API calls. It usually depended on the content of the message being consumed, some persistent state, or the result of previous API calls.

If these situations are very limited or are a normal use case will depend a lot on your context.
Maybe both situations require separate solutions with their own degree of complexity.
I totally understand your solution gives room for more fine-grained rate limiting as you can increase/decrease based on the input from other systems/...
We have designed our system, so that every HTTP call to an external endpoint has a queue in front to handle the overflow.
We do a kind of intake with both internal and external apis whereafter we get an x amount of requests / seconds, especially in external apis it is quite common that you pay/get x requests / seconds.


[Snyk] Upgrade dotenv from 16.1.4 to 16.2.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade dotenv from 16.1.4 to 16.2.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-06-16.

Release notes

Package name: dotenv

16.2.0 - 2023-06-1616.2.0

16.1.4 - 2023-06-0416.1.4

    from dotenv GitHub release notes

Commit messages

Package name: dotenv

a0e21a5 16.2.0
406f2c3 Merge pull request #753 from motdotla/target
ea8db8c update README
431521d Update CHANGELOG and README
96c29b4 Add ability to change the target from process.env to your own object
75cee88 Update CHANGELOG
0a87d62 Merge pull request #751 from Jakousa/patch-1
ad2f100 fix missing import

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #143 (9ed103b) into main (b8926b5) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #143   +/-   ##
=======================================
  Coverage   92.24%   92.24%
=======================================
  Files           5        5
  Lines         116      116
=======================================
  Hits          107      107
  Misses          9        9

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


open ".jsp" file, html-mode doesn't work

init-html.el:
(add-auto-mode 'html-mode "\.(jsp|tmpl)\'")
==> "\.\(jsp\|tmpl\)\'"

Hi! Thanks, but "doesn't work" isn't a bug report. Please can you be more specific? And is there a different mode which would be preferable?

Okay, I found what you meant.


Changing plot title

I create a plot thanks to:
mesh = model.metadata.meshed_region
mesh.plot(my_field)
I'd like to change the title of this plot. I tried using the 'text' argument of the plot function of PyVista (https://docs.pyvista.org/api/plotting/_autosummary/pyvista.plot.html?highlight=mesh plot):
mesh.plot(my_field,text='dummy title')
But I get the following error:

Am I using this incorrectly? Not sure whether the issue is related to DPF-Core or to PyVista here.
Thanks!

I don't think its your fault. pymapdlwas imroved a lot during the latest releases in refards to plotting (still more work is needed). pydpf-coreand pydpf-post` on the other hand are still very limited in regards to plotting, and need to be changed. See e.g. pypdf-post/#36.
You could try to change your plots via pyvista Themes, as described here. But I think thats also not working for all cases (e.g. I have not tested what happens if you set a title). Or you need to create the pyvista plot yourself from the data you want to plot. Sadly there is no example for this as far as I know (I would like such an example too, as I would like to plot results together with deformed shapes)


Generic definition & ternary operation

func genericClosure<T, K>(_ closure: (T, K) -> Node) {

}

Done, after much effort!


[video_player] Add RTSP/RTMP support

Hi.
I found flutter video_player based on AVPlayer in IOS, which does not support rtsp url.
Can anyone help me know how to play a video with format like 'rstp/rtmp' in flutter? 🤔

@mravn-google

If iOS AVPlayer doesn't support the format you want, you might have to write a Flutter plugin wrapping a more powerful player than the platform default. Similarly, it should be quite doable to wrap ExoPlayer rather than MediaPlayer on the Android side. We're hoping to get around to do that, but the Flutter community is more than welcome to beat us to it.

thanks you. I am really happy when have a framework that help me code once time then build for android + IOS, now I think i will code IOS for solve that rtsp/rtmp problem, and wait for the great flutter lib that can play it for IOS, because im not master to code flutter lib to solve it :)

I wonder if there's an easy way to just bridge to FFMPEG?  I have no clue what's involved as far as distribution.  I just think if FFMPEG was supported (directly or otherwise) you'd be set.  And, I would become super more interested in Flutter.

@phillipkerman I think you are looking for #7053

I'm going to close this because I don't expect the Flutter team to provide a plugin with support for an alternative video player.

I'm going to close this because I don't expect the Flutter team to provide a plugin with support for an alternative video player.

Saw your question on implementing wowza with flutter, need a helping hand on same problem. Thank you

@paayao you mean https://www.wowza.com/community/questions/46506/how-to-use-wowza-with-flutter.html? What kind of help?

@paayao you mean https://www.wowza.com/community/questions/46506/how-to-use-wowza-with-flutter.html? What kind of help?

Yes. Want to know if you were able to use flutter with wowza. Finding it difficult.

Sp how is this going, can live video be streamed from one flutter app to many now?

Hey, @function1983:

From my personal experience with Android video player:

If you need RTMP only then you can manually add 'com.google.android.exoplayer:extension-rtmp:2.9.1' to the dependencies of video_player. It will work with just a few lines of code.

This is my requirement; was this experience in flutter or box-stock android? The concept of editing a few dependencies is a lot more attractive than creating my own exoplayer wrapper or depending on<EMAIL_ADDRESS>port of the (ancient) ijk repo.
I'm just going to throw it in the video_player's gradle and see what happens... honestly, I think there is only bespoke application for exoplayer wrappers that do not support exoplayer's extensibility.

Flutter WOWZA plugin for iOS/Android. The project is based on Wowza GoCoder SDK
https://pub.dev/packages/flutter_wowza

RTSP Android side may be covered by https://github.com/flutter/plugins/pull/3933

Rescoping this to adding support on Android, where doing so is feasible. Making a new plugin for platforms where the wrapped player doesn't support it is out of scope.

https://github.com/flutter/plugins/pull/4447 had a partial implementation of this, if anyone is interested in picking it up again and completing the PR.

Rescoping this to adding support on Android, where doing so is feasible. Making a new plugin for platforms where the wrapped player doesn't support it is out of scope.

ExoPlayer project is deprecated.  Should have turned towards AndroidX Media3 direction.  AndroidX Media3 undoubtedly supports streaming media.

RSTP was completed here: https://github.com/flutter/packages/pull/7081.


alacritty: broken darwin build

Issue description
builder for '/nix/store/ajwnb79524qjli5wflfdhvxya2a9p13p-alacritty-unstable-0.2.1.drv' failed with exit code 101; last 10 log lines:
  thread 'src/meter.rs - meter (line 21)' panicked at 'couldn't compile the test', librustdoc/test.rs:332:13
  note: Run with `RUST_BACKTRACE=1` for a backtrace.

  failures:
      src/meter.rs - meter (line 21)

  test result: FAILED. 0 passed; 1 failed; 3 ignored; 0 measured; 0 filtered out

  error: test failed, to rerun pass '--doc'
[0 built (1 failed)]
error: build of '/nix/store/ajwnb79524qjli5wflfdhvxya2a9p13p-alacritty-unstable-0.2.1.drv' failed

Steps to reproduce
nix build alacritty
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
 - system: `"x86_64-darwin"`
 - host os: `Darwin 18.0.0, macOS 10.14`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.1.3`
 - channels(root): `"nixpkgs-18.09pre149107.3878342ef02"`
 - nixpkgs: `/Users/username/nixpkgs`

cc @Mic92

Can you try to adapt for alacritty: https://github.com/NixOS/nixpkgs/pull/49661/files ? This might be the same regression here

i had hope that the regression is related to the the rust upgrade.

mhm. I hope this is not due linking llvm against the system version: https://hydra.nixos.org/build/83279533/nixlog/1

@jwilm Have this llvm linking been reported before? https://hydra.nixos.org/build/83279533/nixlog/1

I don't think disabling tests is the solution. I get these linking problems when running tests of work-related Rust projects as well. This seems to have surfaced since the upgrade to Rust 1.30. Interestingly enough I get the same errors with Rust from Mozilla's nix overlay. But I can't find anything in the Rust bug tracker.

Another interesting data point. Both in the trace above and in some work project that I tried, the linking error seems to occur in doc tests.
Maybe a temporary work around is not running doc tests for Rust derivations? (cargo test --lib)

We could disable them globally instead of fixing each package.

@Mic92 can we close this since rust doctests and jemalloc fixes went in staging?


feat: add instance reference into PolymorpheusComponent

This is a wrong idea.

Same PolymorpheusComponent can be instantiated many times
polymorpheus philosophy is that it's irrelevant whether you use strings, functions, templates or components — they are equal, they shouldn't have preferential treatment.


Design: Organization Capability Matrix

Problem
Implement the capability matrix
Describe the solution
Contact Aaron for offline documentation when the time arrives.
Additional context and instructions
Add any other context or screenshots about the feature request here.

Done.


the exit function is not for scripts

The exit() call here is triggers a hard exit somewhere in the middle of the script and it is unclear why that is needed; interruptions in the control flow should be treated explicitly by raising exceptions and dealing with them. Second, the exit() function is only available if the site module is loaded, which can be omitted by the user via the -S switch (read the docs).
https://github.com/core-unit-bioinformatics/cubi-tools/blob/33c72d2ad41b229a870d67694c9088fef28e2a4a/cubi-tools/update_metadata.py#L187

I replaced the exit() call with raising an exception with information what went wrong.


UEFI Boot Option fails to start after fresh 19.03 install

Describe the bug
I installed nixos with a USB live copy of NixOS 19.03 following the manual's instructions for UEFI boot.
I then rebooted and because my usb drive was next in my boot order, I came back to the usb live installer.
I ran efibootmgr and I saw something like:
Linux Boot Manager
USB UEFI...
Windows...

So I'm pretty sure a boot loader was installed. I remounted my boot partition to /mnt/boot and observed that /mnt/boot/EFI/systemd existed.
This may be related to #45032.
I can't try the grub solution they posted now, but will soon:
# Use the systemd-boot EFI boot loader.
#boot.loader.systemd-boot.enable = true;
boot.loader.grub.enable = true;
boot.loader.grub.device = "nodev";
boot.loader.grub.efiSupport = true;
boot.loader.efi.canTouchEfiVariables = true;

@codygman You never explain how things go wrong for you. Is there an error message that you see? At what point?

@codygman
I am running Nixos on UEFi with below config
   boot = {
      loader = {
        systemd-boot.enable = true;
        efi.canTouchEfiVariables = true;
        grub.enableCryptodisk = true;
      };
      kernelPackages = pkgs.linuxPackages_latest;
    };

My apologies, I was up quite late battling with it and wanted to make sure
my issue was recorded.
It turns out in my BIOS I had set a default within the 'boot from' hard
disk option even though per efibootmgr Linux was first.
I successfully booted with grub though, so I can't yet say sysytemd-boot
works for me.
As soon as possible Ill revert to the installer default, ensure that
'smart' override atop efi boot order is set, and report back.
Probably good to add to FAQ of manual in case others waste 5 hours with
this same silly 'smart' BIOS issue.
On Sun, Oct 6, 2019, 16:16 Dmitry Kalinkin<EMAIL_ADDRESS>wrote:

@codygman https://github.com/codygman You never explain how things go
wrong for you. Is there an error message that you see? At what point?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/70518?email_source=notifications&email_token=AABXEN3OYNR2SFKPAVI2URDQNJIS7A5CNFSM4I53NCO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOUIOQ#issuecomment-538788922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABXEN5XODOPOTJJDQLLBDDQNJIS7ANCNFSM4I53NCOQ
.

19.03 has been EOL for years. If this still happens in supported releases, please open new issues.


Implementation of new MCDA types

As in title.
Addresses the first point in the list tracked by #677

@Zapiano ready for second review.
After this set of changes in, I may rebase onto the yax-main branch.

I'm just going to go ahead and merge - thanks for the comments.


Syncup 6.0/release with master

This fast-forwards the 6.0/release branch to the same commit as master.
Testing

ab-pre-push (aws): http://selfservice.jenkins.delphix.com/job/devops-gate/job/master/job/appliance-build-orchestrator-pre-push/4196/
ab-pre-push (esx): http://selfservice.jenkins.delphix.com/job/devops-gate/job/master/job/appliance-build-orchestrator-pre-push/4195/

I'll close this for now, given that #5 was integrated. We should probably look into syncing bcc with upstream on master first, as it's already 8 months old, and then we can sync 6.0/stage.


Is this project inactive?

Are there any future updates planned for this project?  For example, porting to python3?

Just casting my vote in favor of this project continuing, particularly given some of the encouraging results here: http://engineering.indeedblog.com/blog/2018/02/indeed-mph/
Perhaps some of the ideas in Indeed's MPH lib could be implemented in discodb.

just pointing out that the results of this image
http://engineering.indeedblog.com/wp-content/uploads/2018/01/mph5.png
are heavily weighted by discodb's  python wrapper due to (comparatively) slow UTF-8 string encodes.  If you write k/v pairs using their own c library ripped out of of the python wrapper, disco becomes extremely write-performant.
That's exactly what I've done in my fork and exactly how I use it.
They do have a good point about final filesize being bloated in discodb because we keep all the string keys on-hand where indeed-mph nukes them to obtain a smaller file size.
I believe it's a useful (and differentiating) feature to allow a user to dump k/v pairs back out of the binary blob and you can only do that if you keep the copy somewhere.


OrthographicCamera :up break mesh rendering

with this template :
...
 <OrthographicCamera ref="camera" :position="[0, -20, 0]" :up="[0, 0, 1]" :far="200000">
      <TrackballControls :rotate-speed="0.01" :pan-speed="0.01"/>
 </OrthographicCamera>
...

changing :up to   :up="[1, 0, 0]"  or   :up="[0, 1, 0]" break the camera/scene

Can you provide more details? It works in all my scenes.

Can you provide screenshots of what doesn't work? I cannot run the code as I don't have your glTF file.
I only found a small issue with auto-resize="true" which should be :auto-resize="true" otherwise you are passing a string value 'true'.

It occurs only when x=0, z=0 and y=any value

not fixed on 1.0.0-alpha-1.34

I'm sorry, but can you explain what are you doing to the model? I still don't understand what might be wrong

I'm just left clicking on the canvas to rotate the camera !
with :up="[0, 1, 0]"

I can't right click and move the camera (pan ?)
with enable-raycasting, the mesh disapear like in the gif
without enable-raycasting, the mesh don't disapear (but pan dont work)

with :up="[0, 1, 1]"

I can pan
with enable-raycasting on, the mesh disapear like in the gif (if I pan a lot, it disapear totally...)
without enable-raycasting the exterior faces disapear but I see inside faces that shouldnt be visible perfectly !

with :up="[0, 0, 1]"

works perfectly

I'm still using GLTFLoader and the code shared previously
    "@formkit/vue": "^1.0.0-beta.14",
    "@janvorisek/drie": "^1.0.0-alpha-1.34",
    "@sipec/vue3-tags-input": "^3.0.4",
    "@tweakpane/plugin-essentials": "^0.1.7",
    "@vuelidate/core": "^2.0.0",
    "@vuelidate/validators": "^2.0.0",
    "axios": "^1.2.3",
    "core-js": "^3.8.3",
    "dat.gui": "^0.7.9",
    "three": "^0.148.0",
    "three-trackballcontrols": "^0.9.0",
    "troisjs": "^0.3.4",
    "tweakpane": "^3.1.2",
    "v-tweakpane": "^0.2.0",
    "vue": "^3.2.13",
    "vue-axios": "^3.5.2",
    "vue-router": "^4.1.6",
    "vue-select": "^4.0.0-beta.6",
    "vuetify": "^3.1.2"

The file I'm using :
Torso_F.zip
I can share my screen with parsec if needed

I think you are running into the three controls limitations. You can't for example use OrbitControls and set camera position to [0,0,ANYTHING].
I haven't got much experience with OrthographicCamera and TrackballControls.  Got a busy weak ahead. I cannot help you at the moment, but I will try to replicate the issue later this week and find solution/reason why it is not Drie issue :)

No worries, it's not even an issue for my project ! I don't use it.
I was just testing your release by using random parameters on props
I will tell the level of criticity on my next issue
Do you have a ticket template you want to adopt ?

I loaded a new stl files much bigger than the previous one (x,y,z not size) and the disapear glitch came back!
I think I figure out what the issue was
It was due to the camera position
I need to test if the camera position is correct, because if I load my mesh with the camera "inside" (but in the renderer/canvas, Im not inside) it glitches, maybe the camera position is not well updated ?
If I zoom in or zoom out, the camera.position don't get updated !
It only update if i rotate with left click.
I will try to make a component that emulate it when I have time !
Anyway, I fixed it by doing this :
<template>
    ...
    <GLTFLoader
        v-bind:url='fileName_'
        @load="onCreation"
    >
   ...
</template>

<script>
  ...
  methods: {
    onCreation(group) {
      this.mesh = group.getObjectByName("myMesh")
      this.mesh.geometry.center()
      this.camera.position.y = -this.mesh.geometry.boundingSphere.radius / 0.5
}
  ...
</script>

I'm trying to figure out your code but I guess I should read typescript doc instaid

Can you check again? There were some issues with props handling in cameras.

It occurs for example when :
<OrthographicCamera ref="camera" :far="200000" :position="[0,0,0]">

And then a mesh is added to scene and the mesh have a centroid of [0,0,0]
If I unzoom with my mouse, I wont be able to see the mesh
If I unzoom(chaning camera position) from console/code I can see it


establish a benchmarking method

Why
For youki, performance is one of the most important concerns. Until now, we have relied on our individual senses for this, but we should prepare the official and easy way to measure it more accurately.
Goal
Provide documentation and scripts to measure performance.
Ideally, it should be incorporated into the CI and measured by PR every time.

a example https://github.com/containers/youki/pull/447#issuecomment-958991982

I am looking for people who are willing to take on this challenge.

I had actually been fooling around with benchmarking Youki. I had previously used the Criterion crate to benchmark Rust projects for work and have really enjoyed it. I'm also aware of flamegraph-rs which can give performance profiles. I'm not sure how well these things might work since Youki works in a different way from many other applications, such as forking processes, but currently I have a mostly working Criterion setup on this branch.
A couple of problems I face are having to redo some of the setup logic, some general weirdness around relative paths, it's really a pain to run anything but rootless mode since I almost never have a system wide install of the rust toolchain, and I currently cannot have the benchmarks cleanup their containers since the current delete routine exits the process which means the test process exits whenever I try to delete a container.
This is just my adventure in trying to leverage Rust tooling to get some benchmarks, but perhaps there are other tools that might make more sense which can just execute youki as a separate process. Though I think benchmarks are just the most surface level thing we can do, especially in such a coarse manner. It would be really nice to get profiling so we can understand how things are performing and where the issues might be.
I'd be interested in diving in further here.

@tsturzl I agree with your point, so what I wanna raise here is a part of the benchmark progress.
Since I have some idea with the libcontainer lib wanna do some modifications, but I am afraid to effect the performance, so I want to add a PR to do the relative benchmark by the GitHub action with a label triggering way to get the benchmark criteria of each PR'd build compares to main branch's build.
And since the GitHub action running independently and remotely won't screwed up the local env I think this one can be added up for the first step.
The comparison will be quite simple, in my imagination it just using the tool @utam0k used then running few commands like echo a string, ls a path by the youki with the same conditions, that's all.
If this is not an acceptable way please correct and guide me 🙇♂

@tsturzl I agree with your point, so what I wanna raise here is a part of the benchmark progress.
Since I have some idea with the libcontainer lib wanna do some modifications, but I am afraid to effect the performance, so I want to add a PR to do the relative benchmark by the GitHub action with a label triggering way to get the benchmark criteria of each PR's build compares to main branch's build.
And since the GitHub action running independently and remotely won't screwed up the local env I think this one can be added up for the first step.
The comparison will be quite simple, in my imagination it just using the tool @utam0k used then running few commands like echo a string, ls a path by the youki with the same conditions, that's all.
If this is not an acceptable way please correct and guide me bowing_man

@tommady
Your suggestion is a good first step. Looks good. I agree with you. Let's give It a try
I'm imagining https://github.com/TaKO8Ki/frum/pull/16.

@Furisto @yihuaf If you have any suggestions, please let me know.

@tommady In general I am not a fan of github action or CI for performance benchmark. A local machine, ideally a physical box for this, should be preferred.
In terms of benchmark, we have two separate pieces.
The first is benchmark youki as a binary. The goal here should be automation to bench mark a variety of different usecases, and compare to runc and/or crun. hyperfine is a good choice. We can also explore if we can use hyperfine as a library to produce something similar to our integration test crate.
The second piece is benchmark individual functions and/or modules. This will help us narrow down places where we need optimization. This should be used in addition to a profiler that will help us understand this deeper. I believe cargo and rust has build in benchmark support this similar to unit testing. This will likely give us better signal on where to optimize.
Let me also reach out to a few friends who specializes in doing performance testing and see if they have better advice on how we can do this.

@yihuaf absolutely, and I was about to say the same thing actually. GitHub actions are simply not a good or stable way of performing benchmarks. We don't know how those VMs are setup, they could burst in performance, they could be suffocated by a noisy neighbor, the performance is too varied to expect reliable benchmarks.
Flamegraph actually has an excellent and detailed guide on analyzing performance, and I'd really recommend reading it. I think it's similar to what you're saying. Benchmark from the broader scope, profile it, use that profiling to select your optimization targets.
I think it's similar to what you're saying. My Criterion based benchmarks are admittedly quite hacky at the moment, but I was hoping to simplify things by having the benchmark run all the steps in a single process. Currently the hyperfine benchmarks already consider the create-start-delete to be one iteration of the benchmark, so this is no different in that way. The benefit is that it's much easier to get flamegraph profiling over a single process rather than 3. Also Criterion is exactly what you're talking about, it's utilizing rusts built-in benchmark capabilities. Both flamegraph and Criterion essentially extend Rust tooling, and my branch is basically achieving exactly what hyperfine would be doing.
I hope I'm being clear in what I'm trying to say. I definitely recommend looking at criterion as it's probably the most popular benchmarking tool for Rust. Starting with it may also provide a solid foundation for creating benchmarks around specific areas of concern.

As far as a strategy for benchmarking regressions and improvements. I think benchmarks should be specific to the local machine your benchmarking on, as in you never check in your benchmark results, they are not tracked by git. Instead you record the last benchmark to compare against that way you can change branches to compare performance against main branch or a specific release. This does leave a lot for the user to do, but it's probably the only convenient way we can measure changes in performance reliably. It would also be up to you to communicate this performance change in your PR comment, and this performance change should be relatively easy to cross-examine by a reviewer.

Hi @tsturzl @yihuaf ,
I totally agreed with your points, but what I am thinking about is just like this article said:
What if we only want to detect regressions introduced in a PR?
Or in the current commit against the last release?
We do not need absolute measurements, just a way to compare two commits in a reliable way.
This is exactly what we meant by relative benchmarking.

The idea is to run the benchmarking suite in the same CI job for the two commits we are comparing.
This way, we guarantee we are using the exact same machine and configuration for both.
By doing this, we are essentially canceling out the background noise and can estimate the performance ratio of the two commits.

so let the CI do a relative benchmark ( in my idea the benchmark should be fast and small )
to provide a matrix for everyone to have a quick view.
WDYT? 🙇🏻

@tommady I think the relative benchmark can even be inconsistent enough to provide misleading results. I think sometimes a benchmark might not be super influenced by the system, but in this case in order to even get a reliable or useful benchmark you need to warmup and then run a number of iterations which could be influenced by too many external factors. I'd be willing to see this be tested, but my intuition is that a hyperfine or criterion benchmark in CI will be more misleading and than useful.
However, there might be some metric of performance we can use. This article is pretty interesting and possibly provides some solution. We could use some of the metrics from something like Cachegrind to analyze the performance characteristics of a program in CI. The only downside is it's pretty low level and it's certainly more difficult to interpret than execution time.

Sorry, I didn't word that well. Of course, local machine measurement is preferable. However, I think it is useful enough to compare the performance with the main branch in PR's CI, although it is only a rough guide. I don't think it's realistic for reviewers to benchmark against all PRs at reviwer's local machine every time.
However, I have never attempted this and would like to hear your insights. If it implements easy, you can challenge using hyperfine and see the results rather than discussing it and make a decision.

Maybe a good strategy here is to inform the need for benchmarks on a specific PR using something that's more deterministic to get performance insight? Maybe using something like Cachegrind to analyze a PR branch to see if CPU instructions count falls beyond a certain threshold, we can inform a person to run the benchmark tools to compare against master? So cachegrind can be used in some capacity to see if a benchmark is even needed, but we still have some way to catch changes that greatly improve or degrade performance and then we can reassess a benchmark using a common piece of dedicated hardware to actually run the benchmark (ie the reviewers computer). I mean I have a hard time getting a benchmark to run without a 6% deviation on my machine, I think that only gets worse in a github action. I think Cachegrind gives us a deterministic and very high confidence metric to gauge our performance by. I also think that Youki in general is pretty subject to a high level of benchmark variance because it's relying heavily on the kernel.  I don't think it's like benchmarking an algorithm. Similarly that's why SQLite uses Cachegrind for it's performance and doesn't rely on benchmarks at all, because performance can vary too much for outside reason. The more I read, the less I feel like a benchmark is all that useful of a metric to begin with, and may only really have use in comparing Youki to other runtimes like runc and crun.
Some relevant reading:

The Rust Performance Book
CI for performance: Reliable benchmarking in noisy environments
Are Benchmarks From Cloud CI Services Reliable?
Measuring and Reducing CPU Usage in SQLite

@tsturzl I'd like to see performance measurements using Cachegrind. Could you please, I think it would be to see how messy the performance measurement on github actions can be. We have already gotten hyperfine` measurements with a simple command.


Focusing on input using custom directive does not show list?

As the title already stated, I have made an autofocus custom directive for my input elements. The directive automatically place the cursor on the input element. However, doing so doesn't show the list despite cursor is on the input box but only if the user click on the user box. Is there any way to solve this?
Thank you.

Duplicate to #112


Fix alert link

When a user is alerted about a pending observation, it includes a link. Curtin/Outlook seems to sanitise it so much that the link breaks.
We must work out a way to prevent this or just sent a non-link that users can easily add https:// to

I think removing the redundant http fixed this


Feature/survey config

Raised another PR for this:- https://github.com/COMPASS-DPG/wpcas-service/pull/18

Raised another PR for this:- https://github.com/COMPASS-DPG/wpcas-service/pull/18


[WIP]Stopword alert in search

fixes  #10592
Testing Plan:
GIFs or Screenshots:

For the first commit, this isn't exactly what I had in mind.  I made a few changes to the backend commit:

Simpified the API to be just calling read_stop_words().
Moved the new function to zerver/lib/narrow.py, since that's sorta our search helpers library.
Called it from the part of zerver/lib/events.py that generates the bulk of page_params, so that mobile apps (Etc.) can access this as well.
Rewrote the commit message to explain things at a higher level, rather than simply listing the changes.

And then pushed the remaining 2 commits back to this PR.
I'll leave the zjquery commit for @showell to review; is that commit needed for tests to pass with your frontend commit?  If so, it should be ordered before the frontend commit in your branch.

I have a few concerns here.  More details on chat:
https://chat.zulip.org/#narrow/stream/91-code-review/topic/.2311369/near/694760

@timabbott  I updated this again by adding another assertion to the node test to see if the stop_words in the search query are being selectively altered. I think everything is ready with this now.

@YashRE42 the code looks good.  I had to rewrite the commit message, which was a useless list of the changes you made.  Please write commit messages that explain the purpose of the change, and then anything non-obvious about how it works.
Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages
@rishig FYI; I think this produces a reasonable result; I'm not opening a follow-up issue for moving these changes into typeahead as you suggested in the issue description at this time, because I think we need some user feedback on to what extent this addresses the root issue before further investment in that direction makes sense.


Not working on Linux

Installation process goes as it should be, but "discord restarted" or "discord killed" doesn't actually do anything.
Tried both Canary and Stable same result.
To Reproduce
Normal installation from the appimage located on both the website and here in github releases.
Expected behavior
Themes, Plugins and Settings to show up in the left bar when user settings is opened.
Screenshots

System Information:

OS: Manjaro 21.0.4 Ornara.
Discord Version: Stable 84785 (fe5e237)
SHA-1? : ef627297fcbb6330143efa82f8029a53fb65de2e

If you're still having this issue, you can use betterdiscordctl instead.

If you're still having this issue, you can use betterdiscordctl instead.

Ah hello it's been awhile!
Yeah I tried, it gave me that known problem.
The one where discord becomes a "web" client thing for some reason.

Alright so it didn't work with the Arch package.
So I downloaded the package from discord and it works now for some reason.


Update CLI documentation, --sync-tolerance

[x] Update CLI documentation

--sync-tolerance now only works as part of the --node-socket flag

Issue Number
ADP-1538

Thanks Piotr! 🙏  In the interest of speed, I'm merging this manually, as only the documentation has been updated and no code has been changed. (Not sure why our documentation-auto-approve bot didn't pick this one up.)


Improve styling and organization of element panel

Follow up to #639 (please merge that other one first). This gets the element panel much closer to desired styling:

Outstanding thing: The "Add text" button in the Text Panel needs to be aligned - technically easy, but I'm not very familiar yet with Styled Components and how to extend/nest styles of a existing component (maybe @wassgha or @swissspidy can do a quick follow up here).

(this looks big because it contains the changes from #639)


python312Packages.langchain-ollama: init at 0.2.0

Description of changes
Adds langchain extension to access Ollama.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 343125 at 33d7c222 run on aarch64-darwin 1

2 packages built successfully:

python311Packages.langchain-ollama
python312Packages.langchain-ollama

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

4 packages built:

python311Packages.langchain-ollama
python311Packages.langchain-ollama.dist
python312Packages.langchain-ollama
python312Packages.langchain-ollama.dist


Feature request: DateIntervalFormatter

It would be nice to have DateIntervalFormatter.
Implementation could be ported from https://github.com/papandreou/inter/blob/master/lib/inter.js#L825

Hi, I'm open for it.
I believe this is also called Date Range Format, another library that does that is iLib.
https://github.com/rxaviers/javascript-globalization/blob/master/date-range-format.md
Would you be interested in champion this? The first step I suggest is to look for alternatives and come up with an API.

I think I could do that, but only after #602 ;-)

;)


missing variation_id in assign

Version: 0.4.5
I'm just trying to write an animation to a show and hide for a banner.  As part of that I also want to update an assigned value hidden.
  def show_banner(js \\ %JS{}, id) do
    js
    |> JS.show(
      transition: {
        "transition ease-in-out duration-200",
        "opacity-0 translate-y-4",
        "opacity-100 translate-y-0"
      },
      to: "##{id}"
    )
    |> JS.push("assign", value: %{hidden: false})
  end

The problem here is that Storybook then gives me the warning missing variation_id in assign.
If I do the JS.push("assign..... directly in the variation template this works, because the Storybook code automatically adds in the variation_id.  Am I missing something obvious?  I'm not really wanting to have to force in the variation_id to show_banner as that will create a dependency on Storybook within the component.  Apologies if I'm missing something obvious here.

You indeed need to pass variation_id in the pushed value.
Here is an example: https://github.com/phenixdigital/phx_live_storybook_sample/blob/main/storybook/components/templates/slideover.story.exs
It seems that by relying on the "assign" phx event, you already created a dependency on Storybook, didn't you?

Thanks for the quick reply.  With the "assign" I was looking for a way just to manage the state in the component, so that I could add in additional control in the component HTML.  That's just a standard LiveView JS thing isn't it, rather than a specific Storybook part isn't it?
The example looks useful though thanks, I think I can take that and pipe it from the Storybook variation into the components show_banner function.

JS.push is standard
the "assign" event is not, it is implemented here in phx_live_storybook :)  https://github.com/phenixdigital/phx_live_storybook/blob/main/lib/phx_live_storybook/live/story_live.ex#L484

Ah, I'd missed that, thanks.  Looks like I need to rethink my strategy a bit here, as I definitely don't want the components to have any reliance on Storybook.


add is_lat_unit_matters.py

After I explore the data, I found some interesting details, like we have differnt types of "LongitudeUnits". I am wondering if the latitude data could be presented in differnt ways, and we meed more steps before plotting the data. So I wrote this code to see if we could tell the difference from the plots, marked by different "LongitudeUnits".

Code Review:

Variable and function names:  The purpose of the variables named position_x is a little unclear - what does the position number mean?

Readability: The function description for the if_data_ready function is outside of the function description, instead of after the line defining the function (def ...). Additionally, triple quotes are used at the end of the script to describe results, when # comments would likely be a better stylistic choice.

Suggestions for code improvements: Overall, the code accomplishes its goal. However, a few improvements could be made. First, the plotting code could likely be rewritten as a separate function because the same code is used twice (i.e. plot_lat_and_lon(X, Y, file_name)). Second, using the "raise" function to return an error instead of printing an error message and then exiting the code  in the case of a non-existent file may be a cleaner solution. This would also avoid use of the sys package. i.e.:
else:   raise(FileError, "Filename does not exist")

Use of existing packages: Numpy is imported, but is not used in the script.

Comment placement: The comments at the beginning of the file are a little disorganized. There is not comment at the beginning of the function describing the inputs and outputs and what the function is doing. These comments seem to more or less be included at the beginning of the document, but they are in two separate multi-line quotes which makes it difficult to read.

Plots: We are creating four different plots and saving them. I am not sure if this is really necessary. It may be easier to have all the data on the same plot to see how well they overlay or to make each plot a subplot so only one figure is downloaded.

More on plots: The code to create each plot is very similar, so it would probably be easier to have a function for plot creation that allows you to set the x- and y-positions, s values, and output filename.

There are also some line comments in the py file.