Ensure timestamp monotonicity within a series.

Fixes https://github.com/prometheus/prometheus/issues/481

@beorn7

I recently started prefixing commit messages with the name of the mainly affected subsystem/package. I think it improves searching for specific changes significantly if we did it consistently.

Looks good.

Changed the commit message. I feel like the prefixes are mostly good, but I'm ambivalent about making them mandatory. The one obvious downside is that adding them leaves even fewer characters before reaching the recommended 50-char limit for the first line (http://stackoverflow.com/questions/2290016/git-commit-messages-50-72-formatting). Like right now, I'm stepping over it already :)

Other question would be: what prefix (if any) to use for cross-cutting changes that touch all/multiple parts?

I don't see the value. If I'm looking for changes to a certain part of the
codebase I can just restrict git log?

We probably do not have to save the latest timestamp in the checkpoint, but we should have in in the series object and populate it upon load from the checkpointed head chunk (with the expensive operation currently in the normal code, this code path will then only executed once per time series upon startup).
Might need changes for crash recovery, too.

@beorn7 Changed this cache the last time in the series. That field is already reconstructed in memory when loading a checkpoint.
I haven't touched crash recovery yet, and probably there should also be a test for the new feature in the checkpoint loading. Feel free to push over this branch (and eventually merge) while I'm on vacation...

OK, I'm taking this over.

@fabxc This is ready for review now. As @juliusv is on vacation, I delegate to you.
About the package prefix in commit messages: It breaks the common practice of starting a commit message with a verb in imperative form. Not that I would feel strongly personally. But it means our convention would fight a very established Git convention.

Picking up the question of whether there can be two samples with the same timestamp:
In our current understanding of the world there is only one state at any given time (advanced physics put aside). The time series we collect are thus an approximation of a function over time.
Having multiple samples for the same timestamps requires us to apply an interpretation of this data to approximate a function. We now have to agree on a valid interpretation – do we average the samples? does the last added sample overwrite the previous one? It's hard to answer this question without knowing the reason for having multiple samples with the same timestamp.
The easiest solution is to simply not ingest a sample for a time at which we already have a sample.
Once we implement backfilling we can deal with cases where we want to overwrite samples.

Yeah, overwriting is hard as we so far maintained append-only semantics...
If we enforce strict monotonicity, the bug I have found cannot happen anymore. (See https://github.com/prometheus/prometheus/pull/880 .) I still think my fix makes the code simpler and more robust, so we should keep it. Just my test doesn't work anymore, because it created samples with the same timestamp.
So I could remove my commit that allowed non-strict monotonicity and modify my test in https://github.com/prometheus/prometheus/pull/880 . Thought?

Sounds good.

:+1:


Context generator

This allows users to generate schemas and a context that is compatible with the template.

@rzane Thanks for this! I have it on my todo list for review on Monday.

This is shaping up nicely. As much as possible, the behaviours should probably all be flags.

The only thing left here is to sort the authority behaviours. If they're not in the "correct" order, you get all kind of weird compiler warnings.
Shouldn't be too difficult.

This no longer depends on Mix.Phoenix, and I don't think it added much more complexity, so good call. Not sure how this will behave on an umbrella app, though.
I mentioned a concern in an earlier comment, but I think the diff hid it:

I think I would like to avoid generating a file for Accounts.Token.Purpose and Accounts.Lock.Reason.

I have four potential ideas for how we might do that:

Ship Authority.Ecto with these custom types pre-defined. (e.g. Authority.Ecto.Purpose).
Authority.Ecto can provide yet another macro to generate an Ecto enum. (e.g. Authority.Ecto.Enum)
Tell users to install an enum library and generate code under that assumption. (e.g. exnumerator)
Just use strings instead of atoms in Authority.Ecto.Template when generating changesets. Then, use validate_inclusion in the changeset.

I'm going to merge this in. Before we cut another release, I'd like to:

Generate some tests?
Add docs for mix authority.gen.context


Account roles

This PR adds the option to create account IAM roles

@gdbranco

Do you need to save the policies for each version? can't you download those files during runtime?
(policies_v_4.10, policies_v_4.11)

No, when using the attribute "policy"
you need to specify the file path: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_policy.html#policy you need to use a
Another option is to use an ARN (but it's not that case- those files are located on github)


remove hard requirement that prevents more than 3 masters

Fixes #304
This change removes that hard requirement that prevents an administrator from adding more than 3 masters, even if specified in the manifest.
The reasons to allow more than 3 nodes:

5 nodes (n+2) is a common model for highly reliable systems
When rotating nodes, it may be preferable to add the replacement node before deleting the node that is to be replaced.

Note: I don't know why this was implemented as a hard requirement in the first place

etcd performance does degrade with more members, this is correct. What happens is inserts to the raft log can only happen on the cluster leader, and the leader replicates to all members. So the more members the more time spent replicating additional log entries, which does have a performance impact.
However, gravity is in this weird situation, where if a user tries to specify more etcd members, for whatever reason, gravity just silently rewrites the node to not be a master. So even in a 7 node (n+3 redundancy) cluster, if a user wants to use a replacement strategy where they add then delete a node, we'll have some artificial limit that prevents that behaviour. Although I suppose running a 7 node cluster is far less common than a 3 or 5 node cluster.
This is implemented as your soft limits approach, where if the node profile doesn't specify master or worker, the first 3 nodes in the cluster will become masters. It only doesn't create a hard cap on the masters if specified. If anything, having something other than 1/3/5/7 nodes should just be a warning in satellite.

I think in this particular case, we should not have a hard limit on the number of masters. Satellite and documentation hints should suffice.
Honestly I'd be somewhat hesitant to place infrastructural limits that cannot be removed as opposed to scaling down the cluster if starts performing poorly due to initial misallocation of nodes.

@a-palchikov @knisbet If you guys both think so, I will concede. I agree that the limit (7, 10, whatever) is somewhat artificial, but I also think that just removing the limit altogether without having an idea of how the system will scale/behave is asking for a trouble. At least we should try to make a large master-only cluster and see what happens (I don't think anyone tried that?).

@r0mant I went to 9 masters using the telekube app, and I don't see anything weird, although the telekube app isn't very hard on the cluster.
Single Node
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.010239s
PASS: Stddev is 0.000451s
PASS
2 nodes
knisbet-test1:/$ etcdctl3 member list
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 150 writes/s
PASS: Slowest request took 0.056850s
PASS: Stddev is 0.001135s
PASS
3 nodes
knisbet-test1:/$ etcdctl3 member list
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.040429s
PASS: Stddev is 0.001079s
PASS
4 nodes
knisbet-test1:/$ etcdctl3 member list
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.015874s
PASS: Stddev is 0.000943s
PASS
5 nodes
knisbet-test1:/$ etcdctl3 member list
dab21782b63e68b, started, 10_162_15_245.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.018748s
PASS: Stddev is 0.000895s
PASS
6 nodes
knisbet-test1:/$ etcdctl3 member list
dab21782b63e68b, started, 10_162_15_245.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
f3229338dd572a7c, started, 10_162_15_246.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.021954s
PASS: Stddev is 0.000811s
PASS
7 nodes
knisbet-test1:/$ etcdctl3 member list
dab21782b63e68b, started, 10_162_15_245.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
dd27a3bca3ec7ba5, started, 10_162_15_247.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
f3229338dd572a7c, started, 10_162_15_246.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.017133s
PASS: Stddev is 0.000747s
PASS
knisbet-test1:/$
8 nodes
knisbet-test1:/$ etcdctl3 member list
dab21782b63e68b, started, 10_162_15_245.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
16570b444b40996c, started, 10_162_15_228.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
dd27a3bca3ec7ba5, started, 10_162_15_247.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
f3229338dd572a7c, started, 10_162_15_246.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 151 writes/s
PASS: Slowest request took 0.015699s
PASS: Stddev is 0.000704s
PASS
9 nodes
knisbet-test1:/$ etcdctl3 member list
dab21782b63e68b, started, 10_162_15_245.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
13d758505fa4f1d1, started, 10_162_15_242.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
16570b444b40996c, started, 10_162_15_228.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
775ddc055485c103, started, 10_162_15_248.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
823b2103c2bb5159, started, 10_162_15_243.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8b9ea8c629340b60, started, 10_162_15_249.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
8c83715ef7b1264b, started, 10_162_15_244.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
dd27a3bca3ec7ba5, started, 10_162_15_247.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
f3229338dd572a7c, started, 10_162_15_246.competentstallman8178, https://<IP_ADDRESS>:2380, https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
knisbet-test1:/$ etcdctl3 check perf
60 / 60 Booooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo! 100.00%1m0s
PASS: Throughput is 150 writes/s
PASS: Slowest request took 0.014148s
PASS: Stddev is 0.000634s
PASS


{virtual-network-tap} Migrate to AAZ Codegen

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

/azp run

do we need confirmation for delete commands?  it might be breaking change to vendor sdk version

do we need confirmation for delete commands? it might be breaking change to vendor sdk version

Pls mention this change in release notes


Switch to null-safe lazy initialization

Let's continue the discussion we are having here: https://github.com/webonyx/graphql-php/pull/557#discussion_r437184406
@simPod @shmax

Coverage increased (+0.006%) to 86.154% when pulling 94a670a590a40d445513c5b5ad62bc01e66e6f6f on spawnia:safe-lazy-initialization into a747575e5a5c8e72a1d5a71e9c3eeb580159b9f9 on webonyx:master.

LGTM 👍 Mind resolving conflicts? Will merge it then.

@vladar ready to go.


Update Dependencies: faster-whisper and torch

Hey there, whisper-asr-webservice! 🌟 Wishing you all the best on your journey—may your transcriptions be spot-on and your performance top-notch! Cheers to awesome updates ahead! 🎉
We need to update the following dependencies in the project to address security concerns and improve compatibility:
1. faster-whisper: Update to version 1.1.0.
2. torch: Update to version 2.2.0, if possible.
Reason for the Updates

The current version of torch (1.1.3) has multiple reported security vulnerabilities. Updating to a newer version is critical to mitigate these issues.
Updating faster-whisper to the latest version (1.1.0) ensures compatibility and potentially unlocks new features or fixes.

No GPT in issues please 😅


Snake Example's Screen Goes White When Resizing

When increasing screen size, snake example gets the background as white. It is weird, since Game::render's clear call to clear screen should make the screen black. Also, when the snake "leaves" a cell, it ends up clearing the cell. I am not sure it happens every time the screen is increased. The game looks like this:

It does not seem to happen only when increasing size, but also when decreasing size.

I think I figured it out. The problem seems to be that on resize, I try to clear the screen via crossterm, but I do not reset the colors, and so, it uses the last colors (the snake colors are used when the background gets white).


Does Neorv32 support Altera DE2 with Cyclone II ?

I have an Altera DE2 with Cyclone II dev board which was bought more than 10 years ago.  Does Neorv32 support it ?

Older versions of Quartus (that still support Cyclone II) have problems with inferring block RAM from the default memory descriptions (see #197). We have added alternative memory components in rtl/core/mem that work with these legacy Quartus versions (see #198).

Yes, the NEORV32 also runs on a Cyclone II. An example for an Altera DE1 board can be found here:
https://github.com/emb4fun/neorv32-examples
Take a look for de1-neorv32-sdram-qsys. This is a simple example using on-chip RAM as memory
for IMEM and DMEM. In addition, there is the SDRAM which can be addressed by the Wishbone to
Avalon Master in the Qsys area.

@ralphnguyen86
I think this can be closed, right?

@stnolting thank you very much.


Public API of the framework

Hey @holyturt,
Thanks for your effort, and thanks for accepting the pull requests!
My usecase for the framework is querying the Overpass server for nodes in a bounding box, basically for performing the bare requests. I store nodes in memory and keep track of them in memory, merging new ones with existing ones, avoiding duplicates, etc by myself. Therefore, I'm not dependend on the methods for loading related entities, such as loadRelatedWays().
How do you use this framework? I'm asking because I'd like to exchange ideas and opinions. Do you have any experience that you can share? Thanks in advance for your response!

Hi @wtimme,
Thank you for your message and sorry for the delay. The notification seems not working.
Your pull requests were really helpful!
My last project needs relations of city boundary and nodes which are related to the relations to overlay it on a map. Also, I didn't want to write raw overpass queries on source files as multiple lines of String and I believed it will be more readable. Therefore, I made this framework. My goal was write query easily in Swift. Miscellaneous methods, such as loadRelatedWays(), were made by such aspect.
I think users don't want to use their time to learn Overpass QL or XML just to get map data for iOS development.
Honestly, this framework has lack of specific visions and usecases. And this is why this repository is currently lazy.
So, I'm very happy to hear your ideas and opinions! I'd like to improve the framework with it! Thanks.

Thanks for the feedback and the insights, @holyturt!
I'm currently working on an app that displays certain nodes on a map, loading the information lazily as the users pans on the map. Furthermore, the app allows for editing the tags of the POIs on the map. The purpose is to give users the possibility to add small bits of information that is missing from those POIs, e. g. the numbers of parking spots available at a parking space, in a similar manner to the quests of the Android app StreetComplete.
I'm glad that you're open for feedback. Here's the first thing that pops into my mind. Let's get the conversation rolling! :)
Testing
I'm a big fan of unit testing, and try to embrace TDD. When new to a project, adding tests help me getting to know the API and understanding the underlying logic. Furthermore, it helps me being more confident with refactorings, as the tests will have my back if I screw up. 😉
I've already started adding tests for the XML parsers, but noticed that in order to create the node, entity or way, I needed to always provide the OverpassResponse that the XML came with. This doesn't feel quite right. Have a look at this snippet from one of the test cases. xmlElement is a AEXMLElement that I read from a local file.
let dataResponse = DataResponse<String>(request: nil,
                                        response: nil,
                                        data: Data(),
                                        result: Result<String>.success(""))

let response = OverpassResponse(response: dataResponse,
                                requestQuery: "")

// Actually use the XML parser
guard let node = OverpassNode(xmlElement: xmlElement, response: response) else {
    XCTFail("The XML should properly initialize the model.")
    return
}

So just for testing the XML parsing, I need to create an OverpassResponse that I don't actually need for the XML parsing. But when wanting to lookup releations, the models need to have a reference to the response. So what could be a solution?
Dedicated object for relations lookup
Instead of having the reference to the response that an item was retrieved with, I suggest to use a dedicated object that can be queried for this information. Internally, it would keep track of the "world" that it knows about, and could lazily lookup data when needed.
 This makes unit testing easier and reduces the complexity of the models. Additionally, it improves readability, which is always good to have, as there's no logic in those objects.
Letting the app "learn" about the world: With each query, new relations might be discovered, and "old" references to response instances don't contain the whole picture.
Preparing/allowing for the addition of optional caching: This is something that I'm currently implementing in my own app, but would be nice to have shared with everyone.

Other ideas for the framework
Beside improving the testability and the coverage, I have a couple of feature proposals/ideas.
Caching
Maybe using a database such as SQLite. Could be useful for offline applications. If we didn't want to include a cache in this project, we could still make sure that our objects are easy to cache and that a cache can optionally be added to the data management object.
Elaborate "rules"
This is something that StreetComplete has and what is really nice for reading/editing queries. Have for example a look at the tag filter for the AddBabyChangingTable quest:
(type:node or type:way)
and
diaper!=*
and
(
    amenity = toilets
    or
    (
        (
            amenity~="restaurant|cafe|fuel|fast_food"
            or
            shop~="mall|department_store"
        )
        and
        name=*
        and
        toilets=yes
    )
)

As an added bonus, the StreetComplete has a test case for their parser, allowing for TDD. 🤓
A proper parser allows for more complex rules than we can currently do in code. Furthermore, the queries could be built using an external tool (such as overpass turbo) and can be exchanged.
I guess for starters, this is enough information. 😄 Thanks for taking the time! I'm very much looking forward to your feedback.

First of all, thank you for your ideas and proposals, @wtimme! It is really helpful and inspires me. Your project and the StreetComplete as well. Thanks for sharing it!
Testing
I'm glad to hear that you are a unit test enthusiast. I'm the type of guy who only have knowledge but few experience about unit testing. Therefore, I will merge your tests with pleasure!
Dedicated object for relations lookup
As you pointed out, OverpassNode and the others shouldn't involve the OverpassResponse. It's embarrassing. 😅
The idea is really great. As you mentioned, it will make those models so simple and readable! Furthermore, it would provides flexibility for changes near future. I'm happy that OverpassNode no longer have unrelated lookup methods such as loadRelatedRelations()!
So do you have any ideas you can share for implementing the dedicated object from your works or thoughts?
Caching
Caching data seems not necessary for every apps. But it is an important feature for many apps which this project relate to. So, in my opinion, it should be optional.
There are several ways to cache data in iOS development such as SQLite, Realm. Do you have any ideas how to help user to cache easily with this project?
Elaborate rules
The StreetComplete's query looks simple and functional. It would be nice to have such "rules" in this project! Because this project supports few filters now, e.g. bbox, tag, and it may have more (complex) filters. It will work tremendously in future! Implementing complex parser seems to cost much time but it is worth to do.
Overpass XML vs. Overpass QL
I don't know this topic is important but what do you think about using Overpass XML for the API. When I started this project, I picked it without thinking so much. However, if using Overpass QL is more convenient in future, I could switch to it. Because the project seems still simple enough to do it.
Lastly, could you be a collaborator? It would be nice if you join the project! Please feel free to ask anything! 😉 Thanks.

Thanks for your thorough response, @holyturt!
Dedicated object for relations lookup

So do you have any ideas you can share for implementing the dedicated object from your works or thoughts?

Yes, I do. First of all, I'd create a central place for storing the results of all the responses so far, and already started working on a protocol. Take a look:
public protocol OverpassEntityManaging {
    /// Provides all available entities from storage.
    var entities: [OverpassEntity] { get }

    /// Adds a list of entities to the storage.
    /// The method will filter and list and only add those nodes that are either completely new or updated.
    ///
    /// - Parameter entities: The entities to process.
    func add(_ entities: [OverpassEntity])
}

As you can see, the object takes elements of type OverpassEntity and processes them. In my current implementation, add(_:) already handles multiple instances of the same entity being added, and maintains a list of only the newer ones (= those with a greater version).
I plan on having yet another object that contains a OverpassEntityManaging object for each of the elements (way, node and relation), but haven't started implementing it yet. That object can then have methods for looking up related nodes, ways and relations. I'll come back to you once I have some results to show.
Caching

Caching data seems not necessary for every apps. But it is an important feature for many apps which this project relate to. So, in my opinion, it should be optional.

Yes, I agree. That's why it would be nice to work with protocols, as it allows other developers to optionally add their own cache. I haven't worked on this yet, though, because I feel like the first point (having a dedicated object for relations lookup) needs to be addressed before we can move on to caching.
Elaborate rules
This is something for the future, and could even reside in its own little project, as SwiftOverpassWrapper doesn't necessarily depend on it. Before adding this new feature, I'd make sure that the rest of the code base is in a way that can be easily extended.
Overpass XML vs. Overpass QL
I haven't had a closer look on the query language vs. the XML, but if we go with the rules it may save us a conversion step if we also decide to switch to Overpass QL.

Lastly, could you be a collaborator? It would be nice if you join the project!

I'd happily do so. Is there anything from my end that you need, or is it something that you can set up in GitHub?
On an ending note: How about we move the different topics to their dedicated issues? That way, it's easier for other contributors to have a look at the plans/ideas for SwiftOverpassWrapper.


Why does ended support to PHP 5.5?

This is not an issue. Only a question.
I still using Ubuntu Server 14.04 LTS with PHP 5.5.9.
There is no official upgrade to 16.04 LTS until 16.04.1 be lauched.
There is no official Ubuntu 16.04 LTS AMI in AWS.
There is a real reason to break support to PHP 5.5?
So I am freezed in sendgrid-php 5.0.4.

Hello @fernandoval,
PHP 5.5 is end of life: http://php.net/eol.php
We are not intentionally breaking the library with respect to php 5.5, we are just no longer officially supporting it. AFAIK, the library should still work in php 5.5.
If there are library changes that must be made to specifically support 5.5, I suggest you fork this library.
I hope that helps!

It's ok.
But the Composer (based on the requirement of the minimum version of PHP) by default does not update or install a newer version of php-sendgrid than 5.0.4.
I am forced to use --ignore-platform-reqs option and this is not so good.
However, thanks for the explanation.

@fernandoval,
Sorry for the extra pain.
The other option is: https://github.com/sendgrid/sendgrid-php#alternative-install-package-from-zip


Improve display of caching, permissions, mobile preview and view as user panels

Currently, in version 9, some of our auxiliary page panels/content panels don't look so hot.  Let's fix the following panels.
Caching
Permissions
Mobile Preview
View as User
We don't have comps for these - but I don't think we need them to make them look a lot better than they do.
Caching
This one seems simple - let's make sure we're using the right fieldset and header tags just like we're using in the SEO panel, so that fields match and get indented properly. Make sure you're using the right float and button styles, like btn-secondary.
Permissions
This is probably as simple as making sure the right header styles are used at the top, and the right button/float styles used for cancel/save buttons.
Mobile Preview
Let's add back custom styles that are missing into a panels/pages/_mobile-preview.scss partial. They were removed during the LESS transition. Make sure the panel header and back arrow match other panels like SEO.
View as User
Let's add back custom styles that are missing into a panels/pages/_view-as-user.scss partial. They were removed during the LESS transition. Make sure the panel header and back arrow match other panels like SEO.
Additionally, let's get rid of the spinning cog loader. We don't use that anywhere else. Just use our standard loader by running jQuery.fn.dialog.showLoader() and jQuery.fn.dialog.hideLoader(). Anything else you can do to make this panel and detail content panel look better would be nice, but don't spend too much time on it.

Hi!
I'll start working on this if it's ok.

Great! sounds good!

Hi @aembler !
It seems the mobile preview is no longer working in version 9 (at least not for me).

yes, I think that's quite likely. It's probably due to the removal of old stylesheets; we'll need to go back in and add certain styles from the old mobile preview .less stylesheets back into whatever new SCSS you create.

Thanks for the reply @aembler !
I'm afraid it's a Javascirpt issue (there are errors in the console and the mobile preview never loads).
I have found two issues:

It seems the PanelLoad event fires too soon and the code in concrete/views/panels/page/devices.php is not triggered. As a temporary fix, I have changed this line to:

_.defer(function(){
    Concrete.event.publish('PanelLoad', { panel: this, element: element })
});

(Maybe not the best solution but it works)

According to Undescore docs, "Underscore templates no longer accept an initial data object", so this line was failing. I have chaged it to:

template = _.template(device_template),
viewport = $(template({device: device}));

Now everything works so I can start working on the styles.
Should I create a separate issue / pull request for the Javascript errors?

You can submit the JS fixes in with the same pull request.
Yes, that underscore issue has been something popping up all over the core. Kind of annoying.
Thanks!

Thanks @aembler !
I just submitted the pull requests.

Thanks @jordif !


Mark the XCTest overlay as obsolete & stop running its test

The actual XCTest overlay is not maintained in this repository -- it is distributed in Xcode (libXCTestSwiftSupport.dylib), along with XCTest.framework itself.
The codebase here builds the obsolete /usr/lib/swift/libswiftXCTest.dylib that currently ships in the OSes. There is no expectation that that library is usable for anything; it only exists to maintain a superficial level of binary compatibility with existing apps that happen to link to it by mistake.
Add notes explaining this to the XCTest sources and stop running the XCTest test in the validation suite. (It is causing spurious build timeouts on ci.swift.org due to what looks like a bad interaction between StdlibUnittest and XCTest.)
Fixes rdar://59486106

@swift-ci test and merge


How to resume training

How to resume training when once stopped. I have the best_accuracy.pth file.

Do you have iter_100000.pth?
If you don't have it, you probably can't run it again.
If you want to adjust the output:
# save model per 1e+5 iter.
if (i + 1) % 1e+5 == 0:
    torch.save(
           model.state_dict(), f'./saved_models/{opt.experiment_name}/iter_{i+1}.pth')

Do you have iter_100000.pth?
If you don't have it, you probably can't run it again.
If you want to adjust the output:
train.py(212~215)
# save model per 1e+5 iter.
if (i + 1) % 1e+5 == 0:
    torch.save(
           model.state_dict(), f'./saved_models/{opt.experiment_name}/iter_{i+1}.pth')

I have the iter_ files also after every 2000 iterations. How to resume it.

@yyyash8 just add '--saved_model' option when running train.py

example
python3 train.py --train_data data_lmdb_release/train/MJ/****/  \
--valid_data data_lmdb_release/validation/****/ --select_data MJ \
--batch_ratio 1.0 --Transformation TPS --FeatureExtraction ResNet \
--SequenceModeling BiLSTM --Prediction CTC --saved_model saved_models/****/iter_2000.pth

Thanks


Get Started with SAP Cloud Platform Rapid Application Development by Mendix

Can you kindly re-visit Step 5 if it is working? Tried many times but it is not working. Tried using hana-schema or postgresql but it did not work. Errors are:

Service postgresql does not exist
Service hana does not exist

@IObert I think this involves more the services on the cloud then the Mendix functionality.
@otiliamarinescu Can you help here?

@thecodester @IObert postgresql and all other backing services have been retired for new SAP CP customers as well as for trial from July 15:
https://blogs.sap.com/2019/07/15/evolution-of-sap-cloud-platform-retirement-of-sap-managed-backing-services/
So this tutorial definitely has to be updated it it requires the use of that.
Hana schema should still be available on trial, not very familiar with the details or what specific service plan is required for the tutorial. It could also be an issue with the lack of entitlements, but these are just guesses, I am not very deep into this topic.

Hi,
I have updated the tutorial. I added the domain and database that should be used when choosing the Cloud Foundry environment- see Step 4. ([https://developers-qa.sap.com/tutorials/mendix-onboarding.html#642c97ee-3223-4689-9196-df0974c344f1])
Select hanatrial-schema for the database.
Can you please run through the steps in the tutorial again. It should work now.
Thanks,
Shira

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.

very useful information for,Rapid Application **Development.Thanks** for Sharing.


Main.java:11-12: essa instanciação da lista de tarefas...

The puzzle 2-a6158369 (from #2) in src/java/main/Main.java (lines 11-12) has to be resolved: "essa instanciação da lista de tarefas não está legal melhor seria a utilização de uma interface aqui"
The puzzle was created by Paulo Lobo on 02-Dec-17.
Estimate: 0 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Fixed.


add glossary to unit7

Hey there 👋 thanks for the contribution. I'm running the preview to see if everything works correctly

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


⚠ Secret Website 3 has degraded performance

In 7a7fc0c, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2588 ms

Resolved: Secret Website 3 performance has improved in 39885fb.


feat: add service tag possibility

Checklist
Added possibility to open inobund internet traffic based on Service Tag

[x] I've updated both the azurerm_linux_web_app and azurerm_windows_web_app resources.

Tests pass 🚀


Question on the page "hits"

Hi! I have a documentation issue on InstantSearch.js. I could not find what I was looking for on the page "hits".
How do I limit the length of text returned by Instant Search in JS?
{{{_highlightResult.description.value}}}
Is way too long.

You can use _snippetResult instead after setting up that on your index. https://www.algolia.com/doc/guides/searching/highlighting-snippeting/#snippeting-overview
Basically make sure that attribute is in attributesToSnippet
search.addWidget(
  instantsearch.widgets.configure({
    attributesToSnippet: ['description:5'], // 5 words, still highlighted
  })
);

Can this be used with the Hits widget? Here's a rough outline of my code, the code you've linked to doesn't work as expected with my example"
const productSearch = instantsearch({
    appId: 'xxx',
    apiKey: 'xxx',
    indexName: 'products',
    routing: true
});

var hitsWidget = instantsearch.widgets.hits({
    container: '#product-results',
    autoHideContainer: true,
    searchParameters: {
        hitsPerPage: 4,
    },
    templates: {
        empty: 'No results',
        allItems: '{{{_highlightResult.description.value}}}'
    }
});

var configWidget = instantsearch.widgets.configure({
    attributesToSnippet: ['description:5'], // 5 words, still highlighted
});

var searchInput = instantsearch.widgets.searchBox({
    container: '#search',
    placeholder: 'Search for products'
});

productSearch.addWidget(hitsWidget);
productSearch.addWidget(configWidget);
productSearch.addWidget(searchInput);
productSearch.start();

Needed to also start using _snippetResult not _highlightResult


Multiselect Component setter does not add the selected pills.

When you use the setter of the tp-multi-select, it adds the selected attribute to the option, but does not add the pill.
e.g. when we use document.querySelector( 'tp-multi-select' ).value = ['24']

Pills are not added.

@i-am-chitti Do you think you could take a look at this one?

@imranhsayed This is now fixed!

Thanks @junaidbhura


Skyline: Handle latest chromatogram library export from Panorama, inc…

…luding new support for ion mobility and small molecules.

Here's a view of a mixed proteomic/smallMol clib with ion mobility info in Library Explorer.
Note that we now show that in the tooltip when available, and that we now show the file and IM/CCS in the main pane as we already did with spectral libraries.

One strange thing about the chromatogram view you are showing in the screenshot above, is that there is nowhere that you can find the fragment m/z value for the chromatogram. I assume that you can still switch back to spectrum view to see it, and that the RT would then be visible in the file name line as well?

Thanks - must be some peptide-specific filtering going on there. I expect it's an easy fix.

Hmm. Near as I can tell, it's acting exactly the same way Skyline-Daily does. I just didn't have everything turned on, I guess:

I assume that you can still switch back to spectrum view to see it, and that the RT would then be visible in the file name line as well?
I'm not sure what RT means in the context of a chromatogram library entry?

FWIW here are some screenshots of Daily showing a proteomic clib:

Are these as you would want them?

Not really. What happened to the y- and b-ion annotations in the spectrum plot? Also the line breaks in the legend look pretty awful. And, I think you want to show the "Ion m/z values" in the legend on the chromatogram plot regardless, because it is not included as the x-axis, as in the spectrum plot. I see how the checked menu items I developed for the spectrum plots might sort of give you something for "free" in the chromatogram plot, but they need to be rethought in this new context, considering line breaks and whether they still really make sense.

I agree with all that. But it should be made clear that this is Skyline's current behavior, none of my changes for IMS and small molecule in CLIB are in the code that produced the two images showing the popup menus. Do we want to fix that as part of my branch, or on its own?

I'm not sure what RT means in the context of a chromatogram library entry?

I suppose it's just the RT of the chromatogram peak?

I don't see the annotations missing when I turn of "Show Chromatograms".

But I do see a bunch of other strangeness, we should probably work through separately. I obviously haven't tested this thoroughly enough before. Yes, the RT should be the retention time you see in the Chromatogram, the apex of the integrated peak. That is weird that we don't produce retention times as they are understood by Skyline from this type of library, when we expect the retention times stored in these libraries to be more accurate than the ones stored in spectral libraries from DDA.

I don't see the annotations missing when I turn of "Show Chromatograms".

Mysterious. I guess I'd like to understand this before I merge. Can you do a screengrab of the popup menu showing your options?

That is weird that we don't produce retention times as they are understood by Skyline from this type of library

It may be that we're just not showing them here. This seems like a reasonable one to do on this branch.

I find I can get Daily in and out of that state of missing annotations with some sequence of menu selections, so now I just have to figure out what that recipe is then fix it.

OK, this should be good to go.
BTW I notice that a lot of information we show in Library Explorer isn't shown in Library Match, is that intentional?

Multiple small mol ID types on seperate lines in tooltip:

cleaner formatting of IM values, and legend shown regardless of settings used by other views:

no "Scores" option in popup menu for chromatograms


Issue #8: convert Container to an interface.

Codecov Report

Merging #9 (7ecd578) into main (8abb1d9) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           90        90
=========================================
  Hits            90        90

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

izidic.go
100.00% <100.00%> (ø)

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


Keep tooltip open when it gets hovered

Closes #1131
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[x] Updated documentation (if it already exists for this component).
[x] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
yarn test

Thanks for the contribution @Andarist! We will take a look.

@snowystinger I've focused on implementing @react-aria part as @react-spectrum is out of the scope of my interests 😉 It wasn't really too complicated so I've added this just now - please take a look. As to the docs - I've also added this to the existing example, not sure if this is enough or you'd like to add more information about this.

@Andarist That's understandable, I just wanted to make sure that was your intent. I appreciate that you added it to the other places, makes it easier to play with a live example.

One of the last thoughts on this one - if the same amount of time is used for both keeping the tooltip open after leaving the trigger and for the global "cooldown" then how useful the cooldown mechanism is? It still makes a functional difference for situations when a tooltip gets closed with ESC as noticed by @snowystinger but as the whole cooldown mechanism is focused on pointer interactions I'm not sure if this situation is really important - I would be inclined to say that no, it isn't. If you agree with that then the implementation could be simplified slightly by dropping that mechanism and making the warmup to rely on the module state of opened tooltips.

@Andarist Cooldown is different from time allowed to get hovered over the tooltip itselt.  There's a series of stories with multiple tooltips where you can try this out if you like, it's also explained in our documentation here https://react-spectrum.adobe.com/react-spectrum/Tooltip.html#warmup--cooldown

I understand this mechanism - I might have not described my intention too well though so let me rephrase.
I believe that the cooldown could be removed because when leaving a trigger a tooltip doesn't disappear immediately (unlike before the changes from this PR). The disappearing of the tooltip could act as a cooldown mechanism - if we hover another trigger element when the previous tooltip is still displayed then we switch to displaying the new tooltip anyway (as the mechanism has been warmed up already) and if the tooltip disappears then we could consider this as cooldown delay passed so if we hover over whatever trigger after that then we'll have to wait for a new warmup.

Ahhhh, yes, I misunderstood. Thank you for clarifying. I'll ask Design, though we may not get an answer back until the new year.

Sure, no problem. This doesn't have to block this PR though - it's just a potential refactor opportunity for the future. Do you think that those 500ms is the appropriate time for keeping the tooltip open when leaving the trigger?

Yep, 500ms is fine for this PR


Fix import error in example page

Fixes Uncaught SyntaxError: Cannot use import statement outside a module in https://github.github.io/clipboard-copy-element/examples/

:wave: Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

:art: If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
:fast_forward: If this is a PR that includes changes to an interaction, please include a video recording in the description.
:warning: If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.


Breaking wth --enable_xformers_memory_efficient_attention \

Hi! Thank you so much for this.
I'm trying to run this on Google Colab but I'm always running into the "CUDA out of memory" error.
I've tried adding:
+  --enable_xformers_memory_efficient_attention \
+  --gradient_checkpointing \
+  --use_8bit_adam \
+  --mixed_precision="fp16" \

but it's breaking with:
--enable_xformers_memory_efficient_attention \

error:
ValueError: Query/Key/Value should either all have the same dtype, or (in the quantized case) Key/Value should have dtype torch.int32
  query.dtype: torch.float32
  key.dtype  : torch.float16
  value.dtype: torch.float16

once I remove this argument it works, but always fails at the last step, like 1000/1000 because out of memory (16GB limit, V100)

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: https://github.com/huggingface/diffusers/issues/5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore this.

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Without enable_xformers_memory_efficient_attention flag training works fine.

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Without enable_xformers_memory_efficient_attention flag training works fine.

Yes, if your GPU has >16 GB memory. On a Colab I was trying with V100 it was failing at the end. A100 was unavailable at that time. A few hours after A100 became available and then it worked.

If you're on PyTorch 2.1, it might be a problem to use it xformers (see: https://github.com/huggingface/diffusers/issues/5484). For that case, we default to SDPA (scaled dot-product attention) and should run on a Google Colab free-tier.
If xformers usage is a must, I would recommend using it with Torch 1.13.1.

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Without enable_xformers_memory_efficient_attention flag training works fine.

Yes, if your GPU has >16 GB memory. On a Colab I was trying with V100 it was failing at the end. A100 was unavailable at that time. A few hours after A100 became available and then it worked.

When I was running train_dreambooth_ziplora_sdxl.py on 4090 (24G), I also running into the "CUDA out of memory".

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Without enable_xformers_memory_efficient_attention flag training works fine.

Yes, if your GPU has >16 GB memory. On a Colab I was trying with V100 it was failing at the end. A100 was unavailable at that time. A few hours after A100 became available and then it worked.

When I was running train_dreambooth_ziplora_sdxl.py on 4090 (24G), I also running into the "CUDA out of memory".

See #8. You can free vram instantly. I successfully run it on 4090.

Without enable_xformers_memory_efficient_attention flag and followinghttps://github.com/mkshing/ziplora-pytorch/pull/8, while I still run into the "CUDA out of memory" on 3090 (24G), sorry not 4090

Are you working with PyTorch 2.1? This might be linked to an issue you can find here: huggingface/diffusers#5484
Also, if it fails at the end, it's likely just a validation issue. Training is probably done (check your LoRA save path), if so, you can ignore it, or just remove validation_~ in arguments.

Yep, PyTorch 2.1. What version should it be?

Without enable_xformers_memory_efficient_attention flag training works fine.

Yes, if your GPU has >16 GB memory. On a Colab I was trying with V100 it was failing at the end. A100 was unavailable at that time. A few hours after A100 became available and then it worked.

When I was running train_dreambooth_ziplora_sdxl.py on 4090 (24G), I also running into the "CUDA out of memory".

See #8. You can free vram instantly. I successfully run it on 4090.

Without enable_xformers_memory_efficient_attention flag and followinghttps://github.com/https://github.com/mkshing/ziplora-pytorch/pull/8, while I still run into the "CUDA out of memory" on 3090 (24G), sorry not 4090

i think xformers and torch used different version cuda to compile,caused this problem,recompile xformers from source code ,try it


[WIP] integrating artifact changes for a cleaner main branch

Not ready for review yet, may be deprecated if I separate these changes into a new branch for a new PR. Will link to new PR if so.

Deprecated in favor of #5. Closing PR.


Rest server false unable to start NSDATA

Hi
I was forced to migrate to IoP this weekend, due to certain data types no longer being supported in the 994 version of ISY. It mostly went well. However I had to delete all my node servers and reinstall them. I got the above error when trying to install wstag. Any suggestions how to get rid of it.
Thanks
Logs and screen shots attached

WirelessTag_3-20-2022_90637_AM.zip
.

This is an issue with 3.0.47 and @bpaauwe is aware.

Ok no problem…Is there a forum I should watch for the fix or will you post on wstags when fixed.
Steve

On Mar 20, 2022, at 9:33 AM, JimBoCA @.***> wrote:
This is an issue with 3.0.47 and @bpaauwe https://github.com/bpaauwe is aware.
—
Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/54#issuecomment-1073286713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWOSO7CKJWAPMWL3NLLVA5HO5ANCNFSM5RFW4KPQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

The main PG3 forum where Bob posts his release notes

PG3 3.0.48 is released which should fix this issue.


Prepare for v0.7.3

We've had #337 merged for a while and it seems like it would be helpful for users to get it released, and now #344 to go with it. No other changes since then (except a small doc change) so it should be an easy release.

r? @rust-embedded/cortex-m


Fixes

Updated to get views from resoruces/views

@manshu thank you for great work

It's still not changing the actual views. Can you look into the code and see why it's not reading from resources/views ?

are you sure you have changed the view code in resources ? laravel won't load your file until you change them

yes, i did. It's still not working. It's loading views from Vendor folder, instead of resources/view folder.


New version: Surrogates v1.3.0

Registering package: Surrogates
Repository: https://github.com/SciML/Surrogates.jl
Created by: @ludoro
Version: v1.3.0
Commit: dbe963fd94bf61642227e9f268ee4a29d7bed2a8
Git reference: master
Release notes:

Added Earth surrogate
Added multi objective optimization methods
Updated docs
Removed MOE surrogate due to bug in GaussianMixtures package, planning on adding it again in the next release

@JuliaRegistrator register()

@JuliaRegistrator register branch=master


visual bugs in properties

i tried turning off my snippets and it doesen't affect them. let me know if you need my plugin list, but i don't think i have any that modify the property view.

thanks for reporting!
I wasn't expecting it to be approved so quickly, no to mention get any users so quickly! I will try to look into it over this weekend!


Expand installation instructions

Based on IRC conversation:
<soreau> solarkraft: well there was a change to dbus and I think it needs gdbus loaded too?
<soreau> hang on
<soreau> you need latest w-p-e with https://github.com/WayfireWM/wayfire-plugins-extra/blob/master/src/glib-main-loop.cpp loaded
<soreau> glib-main-loop
<soreau> then run `wayfire -d` and make sure it shows that the plugins were loaded successfully
<soreau> then you should have a binary, `wf-prop`, you can run to click on a window and get its info
<soreau> tux_: is it correct, latest dbus_interface plugin requires "glib-main-loop" to be loaded?

(...)
<tux_> soreaau: yes correct it need glib-main-loop

And my own experience getting it to run.

Thanks!
I've been not monitoring mails a few days. You can ping me on irc, tux_


Fixing container list command.

When passing sudc, I got an error message saying it wasn't a valid revision.

It's working now!  Was there a recent update?


python310Packages.siobrultech-protocols: 0.12.0 -> 0.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.siobrultech-protocols is: A Sans-I/O Python client library for Brultech Devices
meta.homepage for python310Packages.siobrultech-protocols is: https://github.com/sdwilsh/siobrultech-protocols
meta.changelog for python310Packages.siobrultech-protocols is: https://github.com/sdwilsh/siobrultech-protocols/releases/tag/v0.13.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.13.0 with grep in /nix/store/iiqf1wi3p8fvjqmsi994aqa3ylhqqify-python3.10-siobrultech-protocols-0.13.0
found 0.13.0 in filename of file in /nix/store/iiqf1wi3p8fvjqmsi994aqa3ylhqqify-python3.10-siobrultech-protocols-0.13.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.greeneye_monitor
python310Packages.greeneye-monitor
python310Packages.siobrultech-protocols
python311Packages.greeneye-monitor
python311Packages.siobrultech-protocols

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iiqf1wi3p8fvjqmsi994aqa3ylhqqify-python3.10-siobrultech-protocols-0.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.siobrultech-protocols https://github.com/r-ryantm/nixpkgs/archive/1007489fe663b437d915f09e1333b39cfa82b036.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1007489fe663b437d915f09e1333b39cfa82b036#python310Packages.siobrultech-protocols

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iiqf1wi3p8fvjqmsi994aqa3ylhqqify-python3.10-siobrultech-protocols-0.13.0
ls -la /nix/store/iiqf1wi3p8fvjqmsi994aqa3ylhqqify-python3.10-siobrultech-protocols-0.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.greeneye_monitor
python310Packages.greeneye-monitor
python310Packages.siobrultech-protocols
python311Packages.greeneye-monitor
python311Packages.siobrultech-protocols

Maintainer pings
cc @dotlambda for testing.

Result of nixpkgs-review pr 266896 run on aarch64-darwin 1

8 packages built:

python310Packages.greeneye-monitor
python310Packages.greeneye-monitor.dist
python310Packages.siobrultech-protocols
python310Packages.siobrultech-protocols.dist
python311Packages.greeneye-monitor
python311Packages.greeneye-monitor.dist
python311Packages.siobrultech-protocols
python311Packages.siobrultech-protocols.dist


ci: migrate to GitHub actions

https://github.com/longhorn/longhorn/issues/8039

@FrankYang0529 have you figured out the necessary credentials with @yangchiu ?

@yangchiu Please review this as well. Merge this PR after approving it.

@FrankYang0529 have you figured out the necessary credentials with @yangchiu ?

Yes, already set it. Thank you.


Compile instructions

Hey,
I can't wait to use it!
I'm getting the error below - I guess that's because I'm using a wrong version of Go - it would be nice if your instructions included the minimum version.
➜  ~ go get -u github.com/alufers/inpost-cli
package context: unrecognized import path "context" (import path does not begin with hostname)
package github.com/mdp/qrterminal/v3: cannot find package "github.com/mdp/qrterminal/v3" in any of:
        /usr/lib/go-1.6/src/github.com/mdp/qrterminal/v3 (from $GOROOT)
        /home/gdr/tmp/src/github.com/mdp/qrterminal/v3 (from $GOPATH)
        /tmp/src/github.com/mdp/qrterminal/v3
package github.com/urfave/cli/v2: cannot find package "github.com/urfave/cli/v2" in any of:
        /usr/lib/go-1.6/src/github.com/urfave/cli/v2 (from $GOROOT)
        /home/gdr/tmp/src/github.com/urfave/cli/v2 (from $GOPATH)
        /tmp/src/github.com/urfave/cli/v2

Hi!
This program uses go modules, which were added in Go 1.12 and that makes 1.12 the minimal required Go version, although I recommend using the latest stable release - 1.15.6 at the time of writing (December 2020).
If for whatever reason you cannot install Go 1.12 there binaries available for various operating systems and architectures at the releases page.
Thanks for the info, I will add this information to the Readme.
Kind regards,
Albert


Unsubscribe link information clarification

I've added this extra phrase :
When creating a new campaign using own HTML code be sure to not delete the "To unsubscribe please click here" from the email body, otherwise SendGrid will NOT automatically add the unsubscribe link.
This is related to the automated addition of the unsubscribe link for the users who are using their own html code. Working previously in support I have noticed that there are very many clients that deleted the [unsubscribe] tab and then complaint that this is a SendGrid issue.

@burghelea It looks like you're referring to Marketing Campaigns in this change, but the PR is on a Legacy Newsletter User Guide page.
Could you clarify if you're referring to Legacy Newsletter or Marketing Campaigns?
Sorry for the delay, and thanks for the help!

Hey Erik,
I am referring to the Legacy Newsletter, the page is for the correct app,
the name can be a bit misleading, I remember the day when we have changed
the displayed name that our customer see after they open the app.
Let me know if you have further questions.
Thank you,
Paula
On Fri, Nov 11, 2016 at 8:43 PM, Eric Schallock<EMAIL_ADDRESS>wrote:

@burghelea https://github.com/burghelea It looks like you're referring
to Marketing Campaigns in this change, but the PR is on a Legacy Newsletter
User Guide page.
Could you clarify if you're referring to Legacy Newsletter or Marketing
Campaigns?
Sorry for the delay, and thanks for the help!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sendgrid/docs/pull/2254#issuecomment-260051191, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AR2bIBht5NZ2kjuL2DHQ3Ky6FSENvbYBks5q9NN2gaJpZM4KjVx2
.

--
{
basics:
{
name: "Paula Burghelea",
phone: "07783-186603",
website: "http://mycupoflatte.com/wp/",
location: {
address: "Ferncliffe Road",
postalCode: "B17 0QG",
city: "Birmingham",
countryCode: "UK",
region: "West Midlands"
}
}
}


Create python lint action

I personally love these types of static checks for silly things I miss in my code. I don't know if we need to make changes to the action or to the code to get it to pass?

I personally love these types of static checks for silly things I miss in my code. I don't know if we need to make changes to the action or to the code to get it to pass?


Fixed React in website category

Description:
This pull request addresses and resolves an issue related to a React page on our website in the Websites category. The primary focus of this fix was to rectify a JSON error that was occurring within the ReactJS codebase.
Through a careful analysis of the issue, I identified and resolved the root cause of the JSON error, ensuring the React page now functions smoothly and as intended. The changes made in this pull request guarantee a seamless user experience, eliminating any disruptions caused by the JSON error.
Before:
  {
    "tag" : "html",
    "title": "JavaTpoint",
    "description": "ReactJS tutorial provides basic and advanced concepts of ReactJS. Currently, ReactJS is one of the most popular JavaScript front-end libraries which has a strong foundation and a large community.",
    "link": "https://www.javatpoint.com/reactjs-tutorial",
    "img": "../../Card%20Images/../images%20original/react_javatpoint.png"
    "tag": "react",
    "title":"Free Code Camp",
    "description":"It provides the specific path of how to get started as it contains the new features that are announced in 2023",
    "link":"https://www.freecodecamp.org/news/how-to-learn-react-in-2023/",
    "img":"https://user-images.githubusercontent.com/91741581/253747628-6660a999-7d7b-4613-85b4-02e6f3979b87.png"
  }

After:
 {
    "tag" : "html",
    "title": "JavaTpoint",
    "description": "ReactJS tutorial provides basic and advanced concepts of ReactJS. Currently, ReactJS is one of the most popular JavaScript front-end libraries which has a strong foundation and a large community.",
    "link": "https://www.javatpoint.com/reactjs-tutorial",
    "img": "../../Card%20Images/../images%20original/react_javatpoint.png"
  },
  {
    "tag": "react",
    "title":"Free Code Camp",
    "description":"It provides the specific path of how to get started as it contains the new features that are announced in 2023",
    "link":"https://www.freecodecamp.org/news/how-to-learn-react-in-2023/",
    "img":"https://user-images.githubusercontent.com/91741581/253747628-6660a999-7d7b-4613-85b4-02e6f3979b87.png"
  }

@jayk-gupta ,please review and merge my pull request


#4486: Remove Trailing zeros for decimals/float

Remove trailing zeros incase of decimal numbers.

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


update syslog-ng configs with modern options

Hello, I was updating our internal syslog-ng configs since it would throw warnings about the format being "too old" and decided to also check the configs in potluck.
This PR makes these changes:

Parameter names seem to have changed from underscores to dashes so updated the ones that still used underscores
tcp() and udp() source/destination drivers are considered obsolete so I switched those to the network() driver
mem-buf-size() is renamed to flow-control-window-bytes() since version 4.2
disk-buf-size() is renamed to capacity-bytes() since version 4.2
stats-freq(0) is now an option under the stats() group, fixes https://github.com/bsdpot/potluck/issues/49
I have gotten a warning when starting syslog-ng that it can't switch to the new truncation logic since truncate-size-ratio() isn't set so I set it to 1(no truncation) which is also the default

Functionally there should be no changes, this is more syntax changes.
@bretton I don't know if you want to rebuild haproxy and influxdb this time, I didn't bump the versions.

awesome stuff @thrashwerk , thanks a lot! Perfect for haproxy & influxdb - will get to updating and including influxdb soon


ForceUpdateTag shall be "string", not integer, sample needs to be corrected

Sample here https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template#sample-templates specifies "ForceUpdateTag":1 which causing script to fail, it shall be "string" instead. ("1")

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

ID: b5c4c8c5-7757-a969-5800-17f2f2312649
Version Independent ID: 9ced8dd5-43ca-6d1f-c054-842299db8327
Content: Use deployment scripts in templates - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/deployment-script-template.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@artisticcheese Thanks for your comment. We will review the issue and get back to you shortly.

I submitted the fix for this issue and when it merges, this issue will automatically close. After the merge, the updated document will be online within 24 hours.


v2 api for atxs

api: https://github.com/spacemeshos/api/pull/281

[x] watch support. subscribe to atxs emitted after validating and saving database
[x] encode the rest of the fields
[x] add support for limit and offset and make use of it in List api. public services should not expose Stream, as it is much harder to track resources for streams
[x] extract into separate service that has access only for to db pointer, in order to enable readonly replicas
[x] always order by epoch asc, id
[ ] matcher for watcher based on request parameters
[ ] refactor services with generics
[ ] extract query builder into separate module
[ ] test coverage

streaming full atxs
stream all atxs before and including publish epoch 2:

grpcurl -plaintext -d '{"end_epoch": 2}' <IP_ADDRESS>:9093 spacemesh.v2.ActivationStreamService.Stream

stream all atxs that belong to the specific smesher

grpcurl -plaintext -d '{"node_id": "MaAcOOLRj0pffyWO8gfuuWiBszQG2ueq/SNbbMnHHoU="}' <IP_ADDRESS>:9093 spacemesh.v2.ActivationStreamService

the same as above, but also continue waiting for atxs from same smesher

grpcurl -plaintext -d '{"node_id": "MaAcOOLRj0pffyWO8gfuuWiBszQG2ueq/SNbbMnHHoU=", "watch": true}' <IP_ADDRESS>:9093 spacemesh.v2.ActivationStreamService.Stream

streaming headers
all queries above will return full atx data, which in total is about ~1KB. it is useful if someone knows what they are looking for, but generally less amount of data is sufficient. for this purpose StreamHeaders exists and will return much less data:

grpcurl -plaintext -d '{"node_id": "MaAcOOLRj0pffyWO8gfuuWiBszQG2ueq/SNbbMnHHoU="}' <IP_ADDRESS>:9093 spacemesh.v2.ActivationStreamService.StreamHeaders

{
  "v1": {
    "id": "sJAmeZqJr3m40nhQ4y5pMh+uW0rK6uyQGhEN0K8JRe8=",
    "nodeId": "MaAcOOLRj0pffyWO8gfuuWiBszQG2ueq/SNbbMnHHoU=",
    "publishEpoch": 3,
    "coinbase": "sm1qqqqqqq986rj6x5lfzctc6h8wf6uddqpdxr6n2c36nvmx",
    "units": 4,
    "baseHeight": 18880,
    "ticks": 9412
  }
}

listing headers and atxs
streaming if more convenient to use (less memory footprint, can read whole collection from same stream), however
it is harder to enforce fair distribution of resources for multiple concurrent users. for public api it is better to use req/resp pattern
with strict limits and no ability to continuously watch collections.
list full atxs

grpcurl -plaintext -d '{"start_epoch": 2, "limit": 100, "offset": 100}' <IP_ADDRESS>:9092 spacemesh.v2.ActivationService.List

list headers

grpcurl -plaintext -d '{"start_epoch": 2, "limit": 10000, "offset": 10000}' <IP_ADDRESS>:9092 spacemesh.v2.ActivationService.ListHeaders

note that limit and offset are effective only for specific query, so that if you started iteration with start_epoch: 2, you can't just bump start_epoch to 3 and continue using same offset and limit if you care about getting correct results.
scalable read only replicas
non-streaming api by design references only database instance, therefore we can scale it to match demand and isolate from the node that listens to consensus:

[ ] binary that enables only isolated read only apis
[ ] replicated enabled with https://litestream.io/

versioning
data in spacemesh is mostly static and not expected to change constantly. for the case when it does change, object can be bumped to the next version. all responses return protobuf oneof version type.
other tasks
read only apis:

[ ] rewards
[ ] accounts
[ ] layers (applied block, opinion)

[ ] ballots / proposals
[ ] hare certificates
[ ] blocks
[ ] transaction results (copy from original and add lister)
[ ] malicious identities (remove references to lru cache and add lister)

other interesting api is for mempool txs, inclusion but it will be considered separately

I think we also need some way to display the count of ATX per epoch. That could be used to show sync atx progress.


ERROR JDA - One of the EventListeners had an uncaught exception java.lang.NullPointerException

Hey,
when I enter a command it doesn't work and the issue:
ERROR JDA - One of the EventListeners had an uncaught exception java.lang.NullPointerException
is in the console.
I saw the post with the same issue, but it doesn't helped me, so I make a new.
Sorry for my bad English xd
I would be happy if you can help me,
Greats,
Mikenator

You didn't even post the full stack trace, code and JDA version. And this not the place for help. Go to JDA's Discord Server to get help.
https://discord.gg/0hMr4ce0tIl3SLv5

Looks like an error in your code, read the stacktrace and use a debugger.
The github issue tracker is reserved for feature requests and bug reports. Your issue is neither and should be sorted out inside of our discord server. Go to discord.gg/0hMr4ce0tIl3SLv5 to receive the needed help.


Image error

Description
when searching I have this error from the external services that handle image :
{"status":"error","code":404,"message":"The hostname of the origin is unresolvable (DNS) or blocked by policy."}
Version
0.8.2
Steps to Reproduce
Do a search (doctor in my case)
Screenshots
No response
Logs
No response
Platform
desktop
Device
Mac
Operating System
Mac OS 14.4
Browser
Safari
Additional Context
if I do remove : https://wsrv.nl/?url= from the url it do work tough (on the external website), so it's wsrv.nl who seem to fail
Code of Conduct

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

same with me

Exactly the same, project is dead ? Did someone managed to modify the code to remove the wsrv.nl ? Thanks you

Exactly the same, project is dead ? Did someone managed to modify the code to remove the wsrv.nl ? Thanks you

Yeah it seem dead as this kind of major bug is not yet fixed

Looks like wsrv.nl is just used for image resizing & caching. Maybe worth seeing if possible to drop support, and just use sharp if really needed? cropped images can be stored in the storage path for cache if speed is really an issue


moved over downsample method and fixed unpacking bug

Looks good to me, thanks!

Looks great!  I'll probably want to tweak it a bit, but I may as well merge it for now, and can change anything in a later PR.


buildSync: Add @Grapes dependencies for http-builder

@rbrindl thank you for your PR and the catch that we missed dependencies in the setup instructions.  In general we prefer not to use @grape dependencies in artifactory user plugins (although we do use them nearly everywhere else, because they're very cool) because many users run artifactory in off-line environments and user plugins load as part of artifactory startup.  Instead our preference is to create a setup.groovy which will statically allocate a specific set of dependencies to the $ARTIFACTORY_HOME/etc/plugins/lib directory.  An example of one of these can be found here: https://github.com/JFrogDev/artifactory-user-plugins/blob/master/deploy/remoteDownload/setup.groovy
@DarthFennec @aaronsrhodes

Thank you!
I saw the setup.groovy in buildsync Plugin, but did not know how to use it.
Is there some Dokumentation about it?
Regards,
Ron.
Am 13.05.2016 18:43 schrieb "Mark Galpin"<EMAIL_ADDRESS>
@rbrindl https://github.com/rbrindl thank you for your PR and the catch
that we missed dependencies in the setup instructions. In general we prefer
not to use @grape https://github.com/grape dependencies in artifactory
user plugins (although we do use them nearly everywhere else, because
they're very cool) because many users run artifactory in off-line
environments and user plugins load as part of artifactory startup. Instead
our preference is to create a setup.groovy which will statically allocate a
specific set of dependencies to the $ARTIFACTORY_HOME/etc/plugins/lib
directory. An example of one of these can be found here:
https://github.com/JFrogDev/artifactory-user-plugins/blob/master/deploy/remoteDownload/setup.groovy
@DarthFennec https://github.com/DarthFennec @aaronsrhodes
https://github.com/aaronsrhodes
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/JFrogDev/artifactory-user-plugins/pull/56#issuecomment-219096527

At the moment, the setup.groovy files are primarily used by the plugin development environment, and actually depend on some of the code in that project's Gradle script. The devenv can't currently be used with existing Artifactory instances (only with its own internal instance), so right now the setup.groovy files aren't really useful outside of that context, but that should change in the future.
In the meantime, I've updated the install instructions in the README with links to the dependencies. Hopefully that helps.


Feature/refactor ova post test

ova post test withEnv to args
delete portforwarding, use config replacement instead

@panpan0000 @PengTian0

RAC-5848


Who to contact for security issues

Hey there!
I belong to an open source security research community, and a member (@ktg9) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

@rxtur - just a heads up that we also have these reports against the repository:
https://www.huntr.dev/bounties/732943c9-a344-41f7-af76-491c3074965b/
https://huntr.dev/bounties/41be3de5-fd26-4207-a447-71c7723c1636/
https://huntr.dev/bounties/58cbfaf5-d390-4038-9650-c31797bed351/
https://huntr.dev/bounties/712da34e-817a-489a-9ca1-c52977de0397/
https://huntr.dev/bounties/85818a06-a234-4742-95e9-adc0d2ef3d4f/
https://huntr.dev/bounties/a1d29f4f-3f99-47a9-87bb-c1bc3e3007c1/
https://huntr.dev/bounties/4c733f44-c755-49a4-959f-9b3246ad2d36/
https://huntr.dev/bounties/373e7ca7-768b-4f77-ae70-a2a156daaee7/
https://huntr.dev/bounties/80db3a88-3212-4e0b-8d88-97b0394fb13d/
Let me know if you have any questions! 👍


Universal Cables not transferring RF

Using build 185 of Mek, build 94 of Thermal Dynamics, 138 of TE, 58 of Thermal Foundation, 207 of CoFHCore, and 123 of CoFHLib.  Mek cables refuse to transport RF either from generators (with the exception of its own) or to any destination, including its own machines.  KL has said that the version of the RF API Mek's using might be out of date, hence the transference problems.

CoFH API updated


Doesn't work with Single Page Applications

Due to the paths generated being relative, they won't work with SPA's.
Perhaps an option to force absolute paths should be added.

@StevenWeathers great works with the PR! :D
@haifeng2013 please, can you merge and release? We need this ASAP.


Filter for every nth element

Does kuiper support filtering for every nth element?  I don't see a built-in function for it.  I thought maybe I could select every nth element of a group, but I don't see support for that either.  Any way to do this without having to create a custom function?

Do you mean function such as 95% percentile data? If it's true, now it's under planning. Hopefully it would be available at the end of Sep.

What I want is if I have these temperature readings coming into kuiper: 75, 79, 85, 86, 91, 92 and I want to filter for every 2nd reading, only the values 79, 86, and 92 will pass through.  If I want to filter for every 3rd reading, only the values 85, ad 92 will pass through.  If I want to filter for every 6th reading, only the value 92 will pass through.  So I want to be able to specify a number (n), and only the nth value will pass through the filter.

Currently no such functions are supported, I will set the feature as enhancement.
Below could be a workaround, but it's cumbersome.

Use countwindow to trigger data with specified count interval.
Use data template in sink to filter your expected data.

We added a new function collect() which will return an array of the elements of the current window. Thus, you can use index to access any of the elements in that array. For example, to get the temperature of every 3rd element, the sql will be like SELECT Collect(*)[2]->temperature AS temp FROM demo GROUP BY COUNTWINDOW(3)  or SELECT Collect(temperature)[2] AS temp FROM demo GROUP BY COUNTWINDOW(3)

Great!  Quick turn-around time.  Thanks.


Example config.corn does not start

Describe the bug

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

install ironbar on ArchlinuxARM: cargo install ironbar
copy config.corn from repository to ~/.config/ironbar
run ironbar

Expected behavior
The example config starts like with the othe config files (toml, yaml, json)
what actually happens:
Ironbar starts with default config and these messages:
2023-08-30T16:06:00.550003Z  INFO ironbar: 92: Ironbar version 0.13.0
2023-08-30T16:06:00.550101Z  INFO ironbar: 93: Starting application
2023-08-30T16:06:00.729009Z  INFO ironbar::ipc::server: 43: Starting IPC on /run/user/1000/ironbar-ipc.sock
2023-08-30T16:06:00.729659Z ERROR ironbar: 176: Failed to load config: failed to resolve referenced input
2023-08-30T16:06:00.729734Z  WARN ironbar: 177: Falling back to the default config
2023-08-30T16:06:00.729758Z  INFO ironbar: 178: If this is your first time using Ironbar, you should create a config in ~/.config/ironbar/
2023-08-30T16:06:00.729769Z  INFO ironbar: 179: More info here: https://github.com/JakeStanger/ironbar/wiki/configuration-guide
2023-08-30T16:06:00.730099Z  INFO ironbar: 231: Creating bar on 'eDP-1'
2023-08-30T16:06:00.732452Z  INFO ironbar::bar: 33: Creating bar bar-5
^C2023-08-30T16:13:52.936957Z  INFO ironbar: 142: Shutting down

(The other config files work ok)
System information:

Distro: ManjaroARM
Compositor: [Hyprland 0.28]
Ironbar version: [0.13]

Looks like this has come about due to an issue in the new(ish) string interpolation feature in Corn, which I've logged here https://github.com/JakeStanger/corn/issues/21.
In the meantime, I've just pushed an update to master with a patched example.corn and an updated Corn build that will return more helpful errors, so you'll now get the input name it can't resolve.

Works now, thanks :-)


Embedded image in html

Embedded images didn't work in html report.

The problem is the html converter just generates an image like this:

testHtml is the name of the html file. no idea why the image is called like the html file.
In Html you can show an embedded image like this:

It's important in html that there is at the begining of the src "data:image/png;". In common rdl you have the node "MIMEType" with "image/png".
The embedded image code from the rdl file is not in the html file. It's just ignored.
Example embedded image:
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD0AAABACAIAAAAmvOihAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAAEnQAABJ0Ad5mH3gAAAMKSURBVGhD7ZixihVBEEX9Fr/H3/AvjMwNjQxNjAQxMTAxEU1kIzeRxWBFWBRFWRCTZ0HXDm1N3ztVXTULD97lssFuvZmz03Orq9+dw3HqxH27OnHf6MP387sv7q39+ut7rahQPfej86eGuPn+u4daUaFi7m9/fhjc3h9/XmhdWsXczz6/Mqy9n3x6rnVpVXL/+nttQNeWBdHqnCq5USJ7V6WzkvvB2WNDuXZVOsu4L35fGkTkknSWcfNE9i5JZw23J5G98+ms4X57dWbImtEelE9nDbekzZA1o3XIp7OAW3JmsJpfXr6Rv6L3PpnOAm7JmWFq/nJ9JX+Vn+b3zcl0ZrnRQCK9XCvwW5RJZ5ZbEmZomiWpWoFTm0lnltugLJZEagUdErUirhQ3Gkgki1pxI5QBuYJWBJXiRu153SvQfyhX0Iqg5rnR6qPebMoWz6Vznhs1ZpQ2VN/afFST3GQgQc8PNXKxVkQ0yT33vqJGPpHOSW50ROAEZPzSCrdmuMkRQSuASCOPpnOGGyVs3bbXQo08ms4wN0lkG6S40PAo1gqfwtzoHfWP1OaDi0PpDHOjntAPUlzySpjPNofSGeMmq9wPUlykkfvTGeNGqYoeAlAb9aczwE26WPTQhUIi1ootBbjREcGfyEWkKTnTGeA2N1g8NxihV86ZTi83GkjE0a2uiUTcc0EvtzwGc/X97FlAFzdJ5E7WG2O5uNFAsp8307nNTbK/nzfTuc1NEikDbdKot4p5Ore50d4W3SOHIovJ07nBLY/EXG5xdI9EIuHRipE2uNFFJ/ZIJPJoSDoZ9/QiRoVm4/7LUSPGTaafuT0SidwInaEYN3oME8dvLrKvoTMr5Cbzg3NkCwmNWeLhiQRyRy+UVPQxjbknFi4vc6PFw3SOuck25vmyYU7So8y9Fq9vOuY2H1tc2LbXCi3ygJsMJP4vG+aEZgqxCdWAmxwR9khkL/LITDotN1mskkGKi+zQJp2Wm0w5VYMUFwHo0/kfN/l3d01kLzJm9ekcvN9HoRP37eo4uQ+Hf8znq/4iYM+3AAAAAElFTkSuQmCC" >

Please help :D. The source of the My-FyiReporting is a little bit confusing for a newbie of the project.

I am not 100% certain but I believe you want to look at https://github.com/majorsilence/My-FyiReporting/blob/master/RdlEngine/Render/RenderHtml.cs or maybe https://github.com/majorsilence/My-FyiReporting/blob/master/RdlEngine/Render/HtmlConverter/RenderHtmlTable.cs.
Search for "img src=" to find the areas that need to be changed.

Thanks for the help. I have fixed it, but I don't have the permission to commit.
Here is the patch:
patch.txt

Great.  Thanks for the patch.  I can merge it or you can also create a fork and send a pull request.

Would be great if you can merge it.

The patch looks fine.  I'll review it again and then merge it.

it's working. thank you!
issue can be closed.


The experimental setup of the accuracy of 92.5% seems overly simplified.

``In the 74 pairs we have tried so far, ChatGPT obtains an accuracy of 92.5%.''
In this experimental setup, may I ask if all 74 pairs of events are causally related?
If that's the case, then the experiment seems to only focus on determining the direction of causality, rather than its existence.
Do you have any experimental results that simultaneously consider both the direction and existence of causality?
For example:
Input: event1. event2
Output: one of the three choices

cause to effect
effect to cause
3.non-causal

Good point, we have now added those experiments. The tubingen benchmark did not contain any pairs that did not have a causal relationship. So we added two new datasets: neuropathic pain dataset and an arctic atmospheric science dataset. Here we ask chatGPT to decide between all three options: A->B, B->A, and no effect. We find that ChatGPT and GPT-4 do well on this task too, although the accuracy is less than 92%. You can find the results here: https://arxiv.org/abs/2305.00050

Thank you for your patient reply! I have found this part of the experiment.


Need more food

This PR adds more food like :hamburger: instead of important things like :ambulance:

en

iPhone 5s

iPhone 6s Plus

iPad Air

de

iPhone 5s

iPhone 6s Plus

iPad Air

  Generated by :no_entry_sign: danger

Hi @KrauseFx , could you please specify how deeplink (:link: com.krausefx.app://bacons/show/937) was added to this PR. I couldn't find any reference based on description here,
https://github.com/fastlane/fastlane/tree/master/fastlane/lib/fastlane/actions/device_grid#make-use-of-deep-linking

@kumarSC You just provide the deep link via the PR body for your app that supports deep linking

How this fastlane device grid is different than normal fastlane jenkins setup as we have PR checker with different devices


Ver. 1.0.4 doesn' install

I try to install the new version, with the translations, but isnt intalling or generating a log, try to disable and update, try to remove and install manually, but neither working.

I've re-uploaded the v1.0.4 into the release 1.0.4 . You can download and manually update it again.

I removed the version available in the rocketchat repository, and installed it manually, it worked perfectly, the language selector appears, but some things didn't get the translation, I'll test all the functions and let you know later, I'll open a new call for that too, to not to populate this one that has nothing to do with the subject.


Updated deployment process and docs

This PR changes the deployment script to provide more logging and output to help guide the user. This PR is more consistent with how the AKS and hybrid deployments work.

added a config.json to set the params for the script
kicks off a log file and json output from the bicep deploy
RG is created separately, so the bicep script is changed to scope to RG
log file output provides detailed URL's for each of the services (see example below). helpful for users getting started
updated README to match the above
added a demo-script.md in the docs folder to provide some guidance on how to demo various features
added a gitignore

Example output:
***************************************************************
Demo successfully deployed

Details:

Resource Group:  briar-cont-app-reddog-23316
Container Apps Env Domain:  wittymeadow-a953b79d.eastus.azurecontainerapps.io
UI:  https://reddog.wittymeadow-a953b79d.eastus.azurecontainerapps.io
Product:  https://reddog.wittymeadow-a953b79d.eastus.azurecontainerapps.io/product
MakeLine orders:  https://reddog.wittymeadow-a953b79d.eastus.azurecontainerapps.io/makeline/orders/Redmond
Accounting order metrics: https://reddog.wittymeadow-a953b79d.eastus.azurecontainerapps.io/accounting/OrderMetrics?StoreId=Redmond
Order:  https://reddog.wittymeadow-a953b79d.eastus.azurecontainerapps.io/order

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

Closing this one after similar recent updates


feat: add --allow-path and --manifest flags

A path can be renamed using '=': --allow-path .=/my/new/path
Or exposed using its existing name: --allow-path .
Adds --manifest to load manifest from disk instead of WASM module

Should we use : as the separator, similar to Docker's volume / mount args https://docs.docker.com/storage/volumes/#choose-the--v-or---mount-flag ?


feat: add --flatten-metadata to unstructured-ingest

For some use cases, json output is often translated into a single row in a table, but having an extra level of indirection with a metadata nested dictionary makes inserting into such a table awkward.
Therefore, we want to add a --flatten-metadata parameter to https://github.com/Unstructured-IO/unstructured/blob/main/unstructured/ingest/main.py, which simply results in all elements in the metadata field moving up a level and removing the metadata field. I.e.:
{
    "element_id": "d551bbfc9477547e4dce6264d8196c7b",
    "text": "More info available at the Github Project Page",
    "type": "Title",
    "metadata": {
      "page_number": 1
    }
},

->
{
    "element_id": "d551bbfc9477547e4dce6264d8196c7b",
    "text": "More info available at the Github Project Page",
    "type": "Title",
    "page_number": 1
},

opened a new PR for this.


Feature/php version bump

Not really a feature:

array() => []
CS fixes
PHP version bump in Composer
Added Author in Composer

Two things:

Check the travis-ci output to see what the failures are.
In Module.php, can you change line 30 to read:$sm->get('ZF\HttpCache\HttpCacheListener')->attach($em);

This will prepare it for v3 of the event manager, making the new version we tag from this forwards compatible.

Thanks!

.travis.yml outdated (bad php versions) => fixed
added forward compat


Last Updated showing incorrectly

With an active issue, the "Last Updated" on the home page and issue history page show the time since created and not since last update.  Is this happening to everyone or just me?

Same here.
Regards,

Thanks for reporting this. This is now fixed in master.


is NDI useful ?

Hey @ioppermann
SRT and NDI are for different things, and I was wondering what your thoughts are on each ?
I use Video Mixing hardware / software, but not really uo with the Visio of Restreamer and if NDI is useful ?

SRT and NDI both offer a solution for low-latency live video/audio transport and both are IP based.
NDI uses its own format with or without H264 and HEVC encoding in their latest format and is meant for a well connected studio environment. I don't know how resilient NDI is towards packet loss or a bad wifi connection.
SRT is data agnostic. With SRT you can send anything you want. For video/audio transport you usually use the mpegts container. I has mechanisms for error correction and resending data in case it gets damaged or lost, and it will also drop data in case it arrives too late.
Because NDI is proprietary, we prefer SRT which is an open standard.


Use target: 'webworker' in the InjectManifest compilation

Library Affected:
workbox-webpack-plugin
See https://webpack.js.org/configuration/target/#string
CC: @prateekbh

I don't think setting target: 'webworker' when configuring the child compilation will work.
https://github.com/webpack-contrib/worker-loader/blob/b82585a1ddb8ae295fd4b1c302bca6b162665de2/src/index.js#L50-L71 seems to be the "canonical" example of doing this (based on https://github.com/webpack/webpack/issues/9240#issuecomment-500702163), and it instantiates WebWorkerTemplatePlugin explicitly. We should probably just do that.

probably yes


Convert current usage scripts to support the new usage base classes

Hi,
after the implementation of #1175, I would like to merge all existing usage commands in our repository to inherit from our new base classes.
Just assign the task to me. Afterwards, I am going to create an issue for each remaining usage command that hasn't been implemented yet.
br,
Patrick

Awesome! Appreciate your help @plamber 👏