Place generated OPTIONS ahead of user defined routes

Fix for #1260
This change places the generated OPTIONS routes ahead of user defined routes, so that 404 handling does not interfere.
I also noticed a problem when doing this, declaring a route with :any as the http verb would declare an OPTIONS route and a 405 Not Allowed route for ALL methods. It would just be below the user defined route in the stack, and therefore never called. This, however, interfered with my change so I fixed it to map to all methods properly in Grape::API#add_head_not_allowed_methods_and_options_methods

I think there might actually be a slightly better way to do this. I will revisit tomorrow

@arempe93 Thanks. Let us know how you feel about this PR. Either way please do squash the commits and update CHANGELOG. Possibly also update README.

Ok - I think this is ready for review now

There's a behavior change here when you use route :any with OPTIONS, it's possible that some people accidentally relied on broken behavior, I think you should also add a paragraph into UPGRADING, thanks!

Code looks good FYI, nice work.

I believe this change should address your comments. I left in the part about Not Allowed methods because the following spec would also fail before my changes.
it 'should route 405' do
  subject.get :hello do
    'Hello World'
  end
  subject.route :any, '*path' do
    error! :not_found, 404
  end

  post '/hello'

  expect(last_response.status).to eql 405
end

Let me know if there needs to be any other documentation

Merged via https://github.com/ruby-grape/grape/commit/e54b8b0e40d34b64df65c2002f0dcc8be7edfcf3 (I added a period in the CHANGELOG, OCD ;)).

This introduced a regression, see https://github.com/ruby-grape/grape/issues/1307. I am not sure what the right fix is (yet).

@arempe93 I have reverted this fix in https://github.com/ruby-grape/grape/commit/5aa655406398e547f16e32f3f1327a3f8248c820. Couldn't fix the last spec in that commit. Reopening #1260 as well.

@dblock the problem is (using the example from spec/grape/api/namespace_parameters_in_route_spec) is that me/:id should get a 405 for a GET, but that can also match me/pending. And it does match that first because of how this PR re-ordered the route stack - like this
# PR 1263 ordering
version=, method=PUT, path=/me/pending(.:format)
version=, method=POST, path=/me/pending(.:format)
version=, method=DELETE, path=/me/pending(.:format)
version=, method=PATCH, path=/me/pending(.:format)
version=, method=OPTIONS, path=/me/pending(.:format)
version=, method=GET, path=/me/:x(.:format)    # first match, incorrect (405)
version=, method=POST, path=/me/:x(.:format)
version=, method=DELETE, path=/me/:x(.:format)
version=, method=PATCH, path=/me/:x(.:format)
version=, method=HEAD, path=/me/:x(.:format)
version=, method=OPTIONS, path=/me/:x(.:format)
version=, method=PUT, path=/me/:id(.:format)
version=, method=GET, path=/me/pending(.:format)

compared to master ordering
# original ordering
version=, method=PUT, path=/me/:id(.:format)
version=, method=GET, path=/me/pending(.:format)   # first match, correct (200)
version=, method=OPTIONS, path=/me/:x(.:format)
version=, method=GET, path=/me/:x(.:format)
version=, method=POST, path=/me/:x(.:format)
version=, method=DELETE, path=/me/:x(.:format)
version=, method=PATCH, path=/me/:x(.:format)
version=, method=HEAD, path=/me/:x(.:format)
version=, method=OPTIONS, path=/me/pending(.:format)
version=, method=PUT, path=/me/pending(.:format)
version=, method=POST, path=/me/pending(.:format)
version=, method=DELETE, path=/me/pending(.:format)
version=, method=PATCH, path=/me/pending(.:format)

But this is complicated, because even if we do some complicated ordering where the 405/options are placed after each route, this can still be incorrect
# concept complicated ordering
version=, method=PUT, path=/me/:id(.:format)
version=, method=OPTIONS, path=/me/:x(.:format)
version=, method=GET, path=/me/:x(.:format)   # still first match, incorrect (405)
version=, method=POST, path=/me/:x(.:format)
version=, method=DELETE, path=/me/:x(.:format)
version=, method=PATCH, path=/me/:x(.:format)
version=, method=HEAD, path=/me/:x(.:format)
version=, method=GET, path=/me/pending(.:format)
version=, method=OPTIONS, path=/me/pending(.:format)
version=, method=PUT, path=/me/pending(.:format)
version=, method=POST, path=/me/pending(.:format)
version=, method=DELETE, path=/me/pending(.:format)
version=, method=PATCH, path=/me/pending(.:format)

The only solution I see to make 405 work is to dump them all after the routes...which was the point of this PR to fix 404 handling. So I am unsure of how to fix it, short of re-ordering your routes in your grape project and having some more complicated route ordering.

@arempe93 I totally understand the problem (and your explanation is correct). Of the two evils I chose the lesser, not to have a regression. I think we need a much smarter fix here that doesn't create these other routes, but inspects the routing table to figure out if there's a match with a different verb and generates a 405 accordingly.

ok I will look into a solution more in that direction when I finally have the free time again


simplify job with interface

Codecov Report

Merging #7 (b6f55e6) into main (ac85f3a) will increase coverage by 0.26%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   72.46%   72.72%   +0.26%
==========================================
  Files           8        9       +1
  Lines         414      418       +4
==========================================
+ Hits          300      304       +4
  Misses         94       94
  Partials       20       20

Impacted Files
Coverage Δ

job_builder.go
63.80% <63.80%> (ø)

job.go
95.00% <100.00%> (+23.31%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Thanks, Woiden Will End Its Service Soon!

I don't speak nor understand Chinese, so I will write this in English.
Recently, the community just got an information from Woiden (& Hax) admin , saying:

The end of service WOIDEN
Thanks to the auto-renewal script provided below, it caused us to lose more than half of our website visitors
https://github.com/Zakkoree/woiden_extend
We announced that, we will be discontinuing WOIDEN free vps next month, please take your backup, we provide plenty of time.
all servers below will be discontinued on this date:
EU-1 - Germany - May 16, 2023
EU-2 - Germany - May 16, 2023
EU-3 - France - May 31, 2023
EU-4 - Poland - May 31, 2023
EU-5 - France - May 31, 2023
EU-6 - France - May 31, 2023
EU-7 - United Kingdom - May 31, 2023
EU-8 - France - May 31, 2023
EU-BEST-1 - Germany - May 16, 2023
HAX may suffer the same fate but we still decided to wait 1 month longer before any decision is made, there is also the possibility of Woiden's old server moving to HAX, if HAX survives.
thanks for being part of Woiden

Think about it. Did you think what impact will be received by Woiden and the "loyal" community when any of you make this autorenew script? Did you think how Woiden getting its revenue? Yes, ADS!
They got paid with ads revenue, while the community gets free (NAT) Linux server to use. That's a win-win. But with this autorenew, this becomes win-lose situation. The community gets free servers, while Woiden gets nothing.
Judging from your repo' star count, there are many users who used your script.
Use your mind before doing anything, please. Well, maybe you just did this in your spare time, or just curious how do Woiden make a request to its backend server. But please, DON'T SHARE IT TO PUBLIC! THE WHOLE COMMUNITY WILL SUFFER FOR IT! Or even better, don't even try to make it!
Once again, thanks.

I don't speak nor understand Chinese, so I will write this in English.
Recently, the community just got an information from Woiden (& Hax) admin , saying:

The end of service WOIDEN
Thanks to the auto-renewal script provided below, it caused us to lose more than half of our website visitors
https://github.com/Zakkoree/woiden_extend
We announced that, we will be discontinuing WOIDEN free vps next month, please take your backup, we provide plenty of time.
all servers below will be discontinued on this date:
EU-1 - Germany - May 16, 2023
EU-2 - Germany - May 16, 2023
EU-3 - France - May 31, 2023
EU-4 - Poland - May 31, 2023
EU-5 - France - May 31, 2023
EU-6 - France - May 31, 2023
EU-7 - United Kingdom - May 31, 2023
EU-8 - France - May 31, 2023
EU-BEST-1 - Germany - May 16, 2023
HAX may suffer the same fate but we still decided to wait 1 month longer before any decision is made, there is also the possibility of Woiden's old server moving to HAX, if HAX survives.
thanks for being part of Woiden

Think about it. Did you think what impact will be received by Woiden and the "loyal" community when any of you make this autorenew script? Did you think how Woiden getting its revenue? Yes, ADS!
They got paid with ads revenue, while the community gets free (NAT) Linux server to use. That's a win-win. But with this autorenew, this becomes win-lose situation. The community gets free servers, while Woiden gets nothing.
Judging from your repo' star count, there are many users who used your script.
Use your mind before doing anything, please. Well, maybe you just did this in your spare time, or just curious how do Woiden make a request to its backend server. But please, DON'T SHARE IT TO PUBLIC! THE WHOLE COMMUNITY WILL SUFFER FOR IT! Or even better, don't even try to make it!
Once again, thanks.

翻译
最近，Woiden (& Hax) 管理员发布了一条消息，宣布将终止 Woiden 服务。原因是由下面提供的自动续订脚本导致我们失去了一半以上的网站访问者。
https://github.com/Zakkoree/woiden_extend
我们宣布，我们将在下个月停止 WOIDEN 免费VPS， 请备份您的数据，我们提供充足的时间。
以下所有服务器将在以下日期停止服务：
EU-1 - 德国 - 2023年5月16日
EU-2 - 德国 - 2023年5月16日
EU-3 - 法国 - 2023年5月31日
EU-4 - 波兰 - 2023年5月31日
EU-5 - 法国 - 2023年5月31日
EU-6 - 法国 - 2023年5月31日
EU-7 - 英国 - 2023年5月31日
EU-8 - 法国 - 2023年5月31日
EU-BEST-1 - 德国 - 2023年5月16日
HAX 可能会面临同样的命运，但我们决定等待一个月再做任何决定。如果 HAX 存活，还有可能 Woiden 的旧服务器将移动到 HAX。
谢谢你成为 Woiden 共同体的一分子。
请想想，你们中的任何人使用此自动续订脚本对 Woiden 和“忠实”的社区产生的影响。你想过 Woiden 如何获取其收入吗？没错，是广告！
他们依赖广告收入，而社区则获得免费的 Linux 服务器（NAT），这是双赢的局面。但是，有了这个自动续订脚本，这种局面变成了单赢的情况。社区享受免费服务，而 Woiden 却一无所获。
从您在Github收到的星星数量来看，我们注意到有很多人都使用了您的脚本。
请在行动之前三思，这也许是你在闲暇时间做的或只是想好奇一下 Woiden 如何向其后端服务器发出请求。但请不要公开分享此脚本，整个社区都会因此受到伤害！更好的做法是不要尝试制作！
再一次感谢。

I don't speak nor understand Chinese, so I will write this in English.
Recently, the community just got an information from Woiden (& Hax) admin , saying:

The end of service WOIDEN
Thanks to the auto-renewal script provided below, it caused us to lose more than half of our website visitors
https://github.com/Zakkoree/woiden_extend
We announced that, we will be discontinuing WOIDEN free vps next month, please take your backup, we provide plenty of time.
all servers below will be discontinued on this date:
EU-1 - Germany - May 16, 2023
EU-2 - Germany - May 16, 2023
EU-3 - France - May 31, 2023
EU-4 - Poland - May 31, 2023
EU-5 - France - May 31, 2023
EU-6 - France - May 31, 2023
EU-7 - United Kingdom - May 31, 2023
EU-8 - France - May 31, 2023
EU-BEST-1 - Germany - May 16, 2023
HAX may suffer the same fate but we still decided to wait 1 month longer before any decision is made, there is also the possibility of Woiden's old server moving to HAX, if HAX survives.
thanks for being part of Woiden

Think about it. Did you think what impact will be received by Woiden and the "loyal" community when any of you make this autorenew script? Did you think how Woiden getting its revenue? Yes, ADS!
They got paid with ads revenue, while the community gets free (NAT) Linux server to use. That's a win-win. But with this autorenew, this becomes win-lose situation. The community gets free servers, while Woiden gets nothing.
Judging from your repo' star count, there are many users who used your script.
Use your mind before doing anything, please. Well, maybe you just did this in your spare time, or just curious how do Woiden make a request to its backend server. But please, DON'T SHARE IT TO PUBLIC! THE WHOLE COMMUNITY WILL SUFFER FOR IT! Or even better, don't even try to make it!
Once again, thanks.

As a fellow user, I am deeply saddened by the news of Woiden's termination. It is such a shame that the service had to end due to the actions of a few individuals who misused it. It is unfortunate that some members of the community failed to recognize the importance of respecting the terms of service and maintaining a sustainable business model. I hope that we all can learn from this experience and work towards creating a more responsible and supportive online community.


fix(langchain): message parsing for langgraph

resolves https://github.com/Arize-ai/phoenix/issues/3120
Note that this mostly like does not affect regular usage because the error originates from a (seemingly ancillary) component in langgraph called ChannelWrite.

Thanks @RogerHYang!


Interactive plots

Given how busy the plots can get, having a hover feature to see what you are really looking at would be nice. Examples:

https://towardsdatascience.com/tooltips-with-pythons-matplotlib-dcd8db758846
https://docs.bokeh.org/en/latest/docs/user_guide/tools.html#hovertool
https://plotly.com/python/hover-text-and-formatting/
https://github.com/bqplot/bqplot/blob/master/examples/Marks/Object Model/Scatter.ipynb (scroll down to "Adding tooltip and custom hover style")

Thanks. I'll probably fall back to python if I can get this to work in gnuplot. I found these:

https://stackoverflow.com/questions/63554863/how-to-show-values-upon-mouse-hover-in-gnuplot-in-svg
https://funprojects.blog/2020/09/10/gnuplot-realtime-plots-in-20-lines

Join the dark side!


Add files via upload

@Ahmedito First stage of verification passed, official domain is zsegw.pl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Ahmedito Pull request merged. Thank you!


Review and Clean-Up API Folder Structure

We've made a lot of changes from moving Services > APIs and probably had a lot of dependency issues throughout, resulting in a somewhat convoluted code structure for each. Additionally, we're having to establish rules for working with other APIs vs. 'outside; this folder, so would be good if we could flatten down as much as possible now that pretty much everything's moved over.

Resolved in build 103.


how to train i2v from cogvideox-2b model

error : RuntimeError: Given groups=1, weight of size [1920, 16, 2, 2], expected input[24, 33, 24, 42] to have 16 channels, but got 33 channels instead

You need to change the config in models/Diffusion_Transformer/CogVideoX-Fun-2b/transformer/config.json
{
"_class_name": "CogVideoXTransformer3DModel",
"_diffusers_version": "0.30.0.dev0",
"activation_fn": "gelu-approximate",
"attention_bias": true,
"attention_head_dim": 64,
"dropout": 0.0,
"flip_sin_to_cos": true,
"freq_shift": 0,
"in_channels": 33,
"max_text_seq_length": 226,
"norm_elementwise_affine": true,
"norm_eps": 1e-05,
"num_attention_heads": 30,
"num_layers": 30,
"out_channels": 16,
"patch_size": 2,
"sample_frames": 49,
"sample_height": 60,
"sample_width": 90,
"spatial_interpolation_scale": 1.875,
"temporal_compression_ratio": 4,
"temporal_interpolation_scale": 1.0,
"text_embed_dim": 4096,
"time_embed_dim": 512,
"timestep_activation_fn": "silu"
}

I will close this issue first. If there is anything unclear, you can reopen it.

@bubbliiiing Hi, I'am using CogVideoX-Fun-V1.1-5b-Control model to fine tuning, deepspeed type, and get the following error, my control_file_path videos are 3 channels edge maps, the size of them are same as the file_path videos.
RuntimeError: Given groups=1, weight of size [3072, 32, 2, 2], expected input[12, 16, 60, 104] to have 32 channels, but got 16 channels instead


Questions about layer-wise sliding window attention

Thank you for the awesome work!
I am reaching out to seek further clarity regarding the Sliding Window Attention (SWA) mechanism as described in the README
As we know, SWA is typically implemented by sliding a fixed-size window over the input sequence to process it in smaller, manageable chunk.  Suppose the window size $W$ is 5, the context length is 15 and  the decoder model has 10 layers. From my understanding, since the SWA in mistral-7B is layer-wise, in this scenario it could work as follow:

Initially, the window covers tokens 1 to 5 of the input sequence.
If the window slides by  $W-1 = 4$ tokens, it would then cover tokens 5 to 9.
In the next slide, it covers tokens 9 to 13.
Finally, it would cover tokens 11 to 15.

But this only accounts for first 4 layers out of 10 layers. I am curious about the remaining 6 layers. Do the rest layers only conduct attention mechanism on token 11 to 15?
Besides, I couldn't find any code that is about the implementation of a layer-wise sliding window. It seems that every layer uses a consistent sliding window, rather than each layer moving by W tokens. Did I miss something?

@timlacroix Thank you for your reply.
According to the README,

At each attention layer, information can move forward by W tokens at most: after two attention layers, information can move > forward by 2W tokens, etc. For instance in a sequence of length 16K and a sliding window of 4K, after 4 layers, information > has propagated to the full sequence length.

This is where I am really confused. If my understanding is correct, the attention mechanism here is a "layer-wise" approach, which differs from the  common one we are familiar with, since a sequence of 16k length can process through 4 layers with a sliding window of 4k.

@NormXU Sorry to bug you, but did you actually manage to figure out the answer to this or did you just eventually give up on ever receiving an answer?

@NormXU Thank you so much for the in-depth explanation, it is very much appreciated! I know llama.cpp has been looking to implement this but it didn't seem like the necessary information was available.
I'll share this in the discussion over there and I'm sure it will help a lot!

@NormXU Hey, sorry for a bit of necroposting. I'm also trying to understand this caching idea and I think you're right about the general idea but wrong about the details. If we look at the illustration from Mistral paper:

We can see here that token at the position i attends to the maximum  number of tokens i-w:i from the previous layer (each token only sees previous layer's tokens on the left side). At minimum (if i=0), it's gonna attend to only one token at position i=0 of previous layer. If we follow your example, it would mean:
The output of Layer 1 (A', B'.... are the corresponding hidden states):
A' integrates information from only A.
B' integrates from A, B.
C' integrates from A, B, C
D' integrates from B, C, D (we reach the window size of 3) and so on.
And because of the stacked nature of decoder layers, tokens can attend to other tokens outside window size.
I might absolutely be wrong, but that's how it looks from the Mistral paper.

@defdet Thank you for pointing this out. I think you are right. All tokens only consider information from their preceding tokens, rather than having a bi-directional attention. This makes sense to me :)

Sorry for reviving this thread again haha.
I'm slightly confused on the inputs to each layer. Let's say your context vector length is 10, and each multi-head-attention layer has an input size of 5. Does layer 1 read tokens 1-5, and layer 2 takes in tokens 6-10? and each token in layer 2 attends to the tokens in layer 1, as per the diagram in the Mistral paper? @NormXU @defdet

@rshah918, you are correct about the whole idea, but I think you're a bit wrong about the details. Attention windows should be overlapping, as shown in the diagram above. In your example it would mean (first token is number 1, not 0) first layer indeed reads tokens 1-5, but the second one reads tokens 5-9, not 6-10. This detail is actually really important, because token 5 has information about tokens 4-1. If we don't include him in the calculations, upper layers (2 and above) are gonna have no information about tokens 4-1. Also, I'm pretty sure we're talking about whole decoder layers (consisting of self-attention and MLP each), not only attention layers.
Come to think of it, attention layers are overlapping by only one token. Maybe it could be beneficial to make them overlap by 2 tokens?..

Firstly, I want you to know that I really appreciate your super quick and detailed reply!!!
Could you clarify what the query and keys would be in this example? I was under the impression that, for layer 2, Q would be tokens 5-9, and the Key would be tokens 1-5 (AKA layer 2 attends to tokens in layer 1).

@defdet Firstly, I want you to know that I really appreciate your super quick and detailed reply!!!
Could you clarify what the query and keys would be in this example? I was under the impression that, for layer 2, Q would be tokens 5-9, and the Key would be tokens 1-5 (AKA layer 2 attends to tokens in layer 1).

Hey, Bro, I have seen the implementation of mistral from github and I try to help you understand the process. First of all you have to understand that this model (mistral) has multi-layers(actually 32 layers) and the role of each layer of cache: mistral each layer has a cache to store the input value of this layer (actually the output value from the previous layer) that was input by the previous fragment.
After understanding what I said above, consider the example in the paper illustration:
The actual expression of the second layers in the figure is that when the input is to the second fragment token 5-9, the query is actually from the current input token 5-9, while the key and value are converted to 1-9 by cache splicing token 1-5 of the previous fragment. Due to the slide window size set (4 for example), each token can only see the previous 4 furthest tokens. At the same time, in the attention calculation process of this layer, token 9 in token 5-9 in the same fragment can see the information of token 5 at the farthest. In this way, layer 2 token 9 indirectly sees layer1 token 1 information through layer 2 token 5. And so on, assume that the slide window size is W, and assume that the token entered in the position T on this layer can see the token from the position T-W on the previous layer.

Actually, I have also looked at their implemented source code, and I'm curious that SWA cannot be applied to training.

It doesn't matter anyway lol. Mistral v2 doesn't have SWA.

It is not related to mask , every layer has the same window, no shift. I have deep discussion w/ GPT4 about this topic, finally it is clear now, see the below GPT4 explains.
--
When we discuss how multi-layer stacking allows models to integrate broader contextual information in deeper layers, we are describing a recursive information processing mechanism. In this mechanism, each layer not only processes the input it directly receives but also indirectly integrates information from previous layers. This recursive layering is a core feature of deep learning and particularly deep Transformer models, enabling the capture and utilization of long-range data dependencies.
Layer-by-layer Information Accumulation
Each layer's output contains information processed by that layer as well as information inherited from its input. This means that although each token may only directly attend to the previous W−1 tokens' information at each layer, through inter-layer transmission, each layer can indirectly access information processed by earlier layers.
Specific Example
Consider a simple example with a window size W=4 and a model with three layers. Here's how Token 5 can access a broader range of information at each layer:

First Layer: Token 5 directly attends to Tokens 2, 3, 4, and itself.
Second Layer: At this layer, Token 5 again attends to Tokens 2, 3, 4, and itself. However, since these tokens have already aggregated information from their preceding tokens in the first layer, Token 5 now indirectly accesses information from Token 1 (through Token 2).
Third Layer: The process repeats, and Token 5 continues to attend to Tokens 2, 3, 4, and itself, but these tokens now contain aggregated information from even further tokens (like Token 1). Thus, by the third layer, Token 5 can indirectly aggregate information from Tokens 1, 2, 3, and 4.

Indirect Receptive Field Expansion
With each layer, Token 5’s indirect receptive field expands. Although the direct computation window per layer is fixed, the layer-by-layer transmission of information allows each token to 'see' the influence of increasingly distant other tokens. This layer-wise expansion of the receptive field enables deep networks to handle complex, long-range dependencies, which is particularly important in natural language processing, image processing, and other scenarios.
Conclusion
Multi-layer stacked networks achieve the recognition of complex patterns and the capture of long-range dependencies through the accumulation and transformation of information across layers. This capability is a key feature distinguishing deep learning models, especially Transformer-type models, from shallow models, critically supporting their efficient performance on various complex tasks.


Fail to extract Entity using ollama

Hi! Thanks for your light version of GraphRAG!
Here I use the using_ollama_as_llm.py in example with model llama3.2:1b, but got:

It seems that LLMs are running without errors.
How can I solve that? Really thanks for your help!

Fixed with FAQ


Invalid tests for audit library with empty result sets

In case the result set is empty during tests, such result set is not verified. We should add an assertion for such cases when data is not returned.

It seems to be fixed in https://github.com/wultra/lime-java-core/pull/110 Close this issue when merged.

Closing issue.


Integration with AWS Secrets Manager

This PR addresses #1574

AwsSecretsManagerEnvironmentRepository implements EnvironmentRepository. Based on the application and profile(s), we build path to fetch secrets in a hierarchical order of profiles as per the documentation.

AwsSecretsManagerEnvironmentProperties defines all the properties required for configuring aws secrets manager client to fetch secrets.

Authentication is done using AWS Default Credential Chain

Things to note:

label has not been used since I wasn't sure.

GetSecretValueRequest is constructed using only secretId only. That means it supports the default operation to retrieve secretString on the version with the VersionStage equal to AWSCURRENT

you now have a bunch of unrelated commits

@spencergibb i just did a rebase from master since my PR build was failing due to org.junit.vintage dependency and the unrelated commits that you are talking about started showing up for some reason after the rebase.
would you recommend creating a new PR off master to only reflect my changes?

you needed to git push --force. I'm not sure how to recover from this without a new PR

@spencergibb cool, i will create a new pull request. thanks.


Can't View Stories Anonymously Anymore

What happened? Viewing stories anonymously was one of the best components. What is up with the change?

+1 here is happening too
maybe something with commit acc48c5f33b80d08e29e8c62b68918794d351a9a (a day ago)

It seems to work now.


Date Version 2.1.0

It seems to me that in https://reogrid.net/download/ the date of version 2.1.0 is Oct 21, 2016 instead of Oct 21, 2017

Thanks! My mistake :)


ARROW-1173: [Plasma] Add blog post describing Plasma object store

I will plan to merge this and publish the blog tomorrow (with a note about the upcoming 0.6.0 release for getting hands on this code)

Sounds good! Right now the date says date: "2017-08-04 00:00:00 -0400". Let me know if you want me to update this.

Can you update to 8/8 (midnight is fine)? When I generate the site tomorrow morning it will show up

Changed to 08-08.

thank you!


Rework history layout and delete alerts

Changes information display for entire history (alignment of text)
Removes ⓧ icon from treatments and adds standard iOS swipe-to-delete behaviour
Adds proper descriptive message when deleting FPU entries with the sum of carb equivalents that are to be deleted

This feature was inititally proposed through PR https://github.com/Artificial-Pancreas/iAPS/pull/236. Please see that PR for user feedback (about a dozen people have tested this) and test feedback.

OLD VIEW
dark & light mode
NEW VIEW
dark & light mode

@Jon-b-m Can we have a look at this one? If this one gets in, I can pull the then-updated dev into the other PRs, update them, and we can get them going too  🚀  The swipe-to-delete behaviour is content of this PR, as I split up the other PR into as small as possible parts, so this needs to get in first, then PR #271 (insulin dialog) and PR #272 (glucose dialog) can follow 😄

Can we remove the order of HStack elements in this PR and just focus on the delete and alert message, please.
I'm not sure about the order of elements yet. I think this part needs a more substantial change, but should be made in another Pr.
Regarding the alert message if you look at the mother alerts in iAPS there are usually a \n added before every message to make the alert more readable.

Sure, will remove text ordering and adapt alert text styling.

I will add the history text layout/ordering in a PR of its own – it has been discussed and been approved over the course of a month my many community members. I'll push this to a new PR.

This alert function has been deprecated. Please use the new

alert(_:isPresented:presenting:actions:message:)
Instead.

Please don't force unwrap, unless you 100 % know you can. In this case you don't need to.
Is the use of fpuFormatter when filtering really necessary here? I think it's better to filter by fpuID here instead, as all FPUs belonging to same entry is identified with the same ID.


Consider a simple optimization to kProcessor 1

kProcessor 1 can be easily used, and it's a dependency in the current version of kSpider and other tools. The hashmap of the index and others can be optimized to use the parallel version of the flat_hash_map with the maximum number of sub-maps to easily handle very large indexes.
Increasing the number of sub-maps in kProcessor v2 will also be good optimization (even if it's used in single-threaded applications).

Resolved by #103


Fixed link syntax error in 'Dead Letter Queues' README link

There was a lingering > in the hyperlink.

👍

Coverage remained the same at 78.972% when pulling 40f50ed00620c5f7fd600e9a1138922f35bebfdf on Bartvds:patch-1 into 39f05172213fc4ca9dbddb09c908e31d43cc1c36 on Miserlou:master.


fix: double 'show all data' button in case of multiple objects with the same id prefix

This issue was happening because ContentDocument and ContentNote have the same Id Prefix.
I'm now passing the RowObjectType to renderCell, so that the ObjecType is given and it doesn't need to be calculated via the prefix.
Unit test evidence:

Great thank you very much @baslu93 for this quick fix !
I'll try test this today, kudos for the run of the tests, you're the first one to do it 👏

Hi @baslu93,
I can see a regression for polymorphic fields when trying to showAll data :

Hi @tprouvot,
Interesting, I think the condition I adjusted is doing more than what I was expecting.
Thank you for testing, and apologize for that.
I'm reviewing it.

Hi @tprouvot,
I changed the approach here.
objectType is something you can't be get from the SalesforceId prefix in some cases (e.g. in ContentDocument, CaseComments, ...)
So when "Show all data" page is loading (when isTooling=false), I use the ui-api to get the objectType.
If isTooling=true remained ASIS.
I prefered to work on "Show all data" because there's only one record there, and 1 api call is needed, in the data extract page more api calls were needed.
I'm using the /ui-api/records/${recordId}?layoutTypes=Compact which seems to be the lightest, since I need it to get objectType only.
Let me know you feeling.


Update version: Transmission.Transmission version 4.0.5

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335226
2023-12-08 12:42:37.834 [CLI ] ShellExecute installer failed: 1603 Property(S): ErrorDialog = ErrorDlg MSI (s) (78:94) [12:42:37:600]: Product: Transmission 4.0.5 (a6fe2a64aa) (x64) -- Installation failed. MSI (s) (78:94) [12:42:37:603]: Windows Installer installed the product. Product Name: Transmission 4.0.5 (a6fe2a64aa) (x64). Product Version: 4.0.5. Product Language: 1033. Manufacturer: Transmission Project. Installation success or error status: 1603.
2023-12-08 12:42:54.328 [CLI ] ShellExecute installer failed: 1603 MSI (s) (D8:2C) [12:42:54:147]: Product: Transmission 4.0.5 (a6fe2a64aa) -- Installation failed. MSI (s) (D8:2C) [12:42:54:147]: Windows Installer installed the product. Product Name: Transmission 4.0.5 (a6fe2a64aa). Product Version: 4.0.5. Product Language: 1033. Manufacturer: Transmission Project. Installation success or error status: 1603.

@wingetbot waivers Add Validation-Shell-Execute


Caasp4 Cleanup: fix a typo

Add jinja syntax to dereference the variable instead of treating it
as a string literal.

I think this is fixed by another PR, but it doesn't hurt of doing so in this patch.


Update swagger.json schema for TFJobSpec to include RunPolicy

TFJobSpec has been updated to contain RunPolicy which encapsulates, for example, backoff limit.
Yet Swagger schema and Python SDK are not reflecting this change, so it’s impossible for now to configure RunPolicy in TFJobSpec using Python SDK.

Resolved in https://github.com/kubeflow/training-operator/pull/1420.
This issue can be closed now.


Service page - remove hand pointer from import service view

Describe the bug

There is not any action so remove hand pointer from service import heading


Double rocker cannot control right switch from actions

On the lumi.switch.b2laus01 "Wall Switch - No Neutral - Double Rocker" you cannot control the "right" switch from actions.
I am setting up a remote Zigbee switch to control the Aqara double rocker to turn the lights on/off from across the room. When I go to the action on the remote, I cannot control the right switch. You can test this by trying to add right control to an action if you don't have remote to test with.
https://user-images.githubusercontent.com/1400808/230397585-885515a0-abea-41e5-8ab5-a5abef66ec72.mp4

Side note, I'm a software developer and work on smart home stuff too, so I'm more than happy to help here. just opening the issue on your repo since you've done this great work so far!

so it is, hooray! thank god my wife has a pixel


create test bots (trybots)

buildbots should only build; for unit and ui testing we should have diff. machines without any dev stuff

if possible, lets use some cloud service for that. it does not need any access to our source code etc. only download the new build, run tests, run uitests, just run the app; report back the results or perhaps collect it in a waterfall, in buildbot view

We can also create Virtual machines in our Build machines and use them as Trybots


wasapi: Fix random crashes on shutdown

Hi there! This is a bug I discovered by accident while debugging a crash in Dolphin.
Sometimes when trying to close a cubeb stream, Dolphin will instead randomly crash because of an invalid handle. This PR fixes this.
If there's something off about this PR or this is a result of a mistake on our side, I'd be happy to assist!

Thanks for the PR.  What's the value of shutdown_handle when the crash occurs?  Can you track down where the invalid handle first appears?  It should be either NULL or a valid handle.

What's the value of shutdown_handle when the crash occurs?

-1. It shows up as stm->shutdown instead of stm->shutdown_event (doesn't exist according to VS despite the fact it's clearly in the source code) though which is strange

Can you track down where the invalid handle first appears?

The handle seems to be invalid from the moment it is created but I'm not sure how to properly diagnose where it gets invaldiated.
It seems that SetEvent always returns true though.

-1. It shows up as stm->shutdown instead of stm->shutdown_event (doesn't exist according to VS despite the fact it's clearly in the source code) though which is strange

The VS debugger gets confused and shows the layout for the cubeb_stream declared in cubeb_winmm.c.  Coincidentally winmm_stm->shutdown and wasapi_stm->shutdown_event are at the same offset in the struct.  If you edit CMakeLists.txt to exclude the WinMM backend, it'll show the correct layout for WASAPI.

The handle seems to be invalid from the moment it is created but I'm not sure how to properly diagnose where it gets invaldiated.

So you're seeing CreateEvent return -1 here?  Or does it happen sometime later?
Looking at every store to stm->shutdown_event in cubeb_wasapi.cpp, it's initialized to 0, rewritten with the result of CreateEvent (which according to MSDN should be 0 on error, otherwise a valid value), and rewritten to 0 when stop_and_join_render_thread is called.
If you could put a hardware watchpoint on the location of stm->shutdown_event and work out who's storing -1 into it, that'd help understand what's going on here.

Sorry for the very late response but I was pretty busy.
So I did some more testing and it turns out CreateEvent actually returns -1 every time it is called for some reason.
I'm currently investigating whether we are using all Cubeb API calls properly, so maybe that's the issue.

We were doing some really weird stuff with our audio streams, so it was on us. Mea culpa.

Thanks for following up!


ARROW-4616: [C++] Log message in BuildUtils as STATUS

Merging. One of the Java builds failed from a flaky Flight test


Base64 encoded contents returned by file API not raw contents leading to unnecessary commits

The files API, see here: https://python-gitlab.readthedocs.io/en/stable/gl_objects/projects.html#project-files
Returns the contents from the gitlab api which is Base64 encoded, this line:
https://github.com/gitlabform/gitlabform/blob/f96efbe89ad4ae707a5d55ff476be825b8bb16d2/gitlabform/processors/project/files_processor.py#L141
Need to first decode() it and then convert it to a string for the not equals comparison here:
https://github.com/gitlabform/gitlabform/blob/f96efbe89ad4ae707a5d55ff476be825b8bb16d2/gitlabform/processors/project/files_processor.py#L143
For more visual results, you end up comparing base64 to non-base64 (which will always fail) and therefore make empty commits, like this:
Changing file '.gitlab/renovate.json' in branch 'alpha', delta:
- ewogICAgIiRzY2hlbWEiOiAiaHR0cHM6L...

{

"$schema": "https://docs.renovatebot.com/renovate-...

Thanks for reporting @alex-lmco . Looks like you've done a lot of troubleshooting work to identify the root cause. Could you help contribute the fix with a test case? The repo must be missing a test case resulting in this bug being added when the files processor was recently refactored.

Unfortunately I can't contribute the fix. It is probably though just: repo_file.decode().decode(sys.stdout.encoding)

I'll pick this up today - affecting us wide spread


iter() is missing on Buf

The documentation for IntoIter claims that Buf should have an iter() function which will return an IntoIter. Unfortunately, this function seems to be missing, and nothing else provides similar functionality. Some types in the bytes crate do seem to have an into_iter which returns this type though (Chain, Bytes and BytesMut), but nothing seems to work on arbitrary Buf implementations.
I have my own Buf implementation and would very much like to iterate over it too. Unfortunately, as there is no generic iter() on Buf, and the constructor for IntoIter is only crate-public, I have no way to do this except by implementing my own iterator, even though IntoIter just does exactly what I want.
Is it possible to provide some way for me to make an IntoIter from an arbitrary Buf implementation?

Calling it iter() would be incorrect because it takes ownership. It should be called .into_iter(). However, adding a method to the Buf trait called into_iter is probably too much of a breaking change to do it at this point. It would make byte_slice.into_iter() fail with an error about it being ambiguous on the &[u8] type if you have Buf in scope.
I don't mind adding a constructor though.

Making the existing constructor public instead of crate-public will work for me. If you like, I can do a PR for it.
Also, the documentation here will have to be modified: https://docs.rs/bytes/latest/bytes/buf/struct.IntoIter.html

Sure, I would be happy to merge a PR like that.


Scope of Jaynes analysis/Bayesian formalism

Your reference to Jaynes (1987) implies that he discussed the Lomb-Scargle periodogram. I don't think he knew about this particular algorithm, but was remarking more generally on least-squares fits to sinusoids.
Also, I wonder if you considered and rejected a fully Bayesian formalism for the problem you address in this paper?  In http://arxiv.org/abs/math/0111127 I tried to demonstrate a generic link between frequentist statistics such as the periodogram and the Bayesian posterior for a corresponding quantity (in the spirit of Larry Bretthorst's power spectrum analysis: Bretthorst, G. Larry, 1988, Bayesian Spectrum Analysis and Parameter Estimation, Lecture Notes in Statistics, Springer-Verlag, No. 48; http://bayes.wustl.edu/).  I don't know how universal it is, but a connection of the form
                       P( a ) ~ exp[ - C(a) / error variance ]

seems to pop up a lot.  C(a) can be an auto- or cross-correlation function; or a power spectrum or a cross-power spectrum, corresponding to  a  being a time lag or the frequency of a sinusoidal component.  Then the expedient of simply multiplying posteriors (for independent quantities) might be useful in the multi band context.  If nothing else this might lead to a more rigorous "Occam factor" regularization.

Thanks @jscargle – yes, the sentence about the Jaynes paper is a bit misleading. We'll correct that.
I'd thought briefly about the Bayesian point-of-view for the multiband method, but I avoided discussing it for a couple reasons:

As your paper makes clear, the Bayesian and frequentist results for periodograms are usually related by a simple monotonic function, so going from one to the other is easy.
I think a fully-Bayesian treatment of the periodogram would involve marginalization over nuisance parameters in the model, and in some cases you want the nuisance parameter to be the period! Unfortunately, since the posterior is so highly multi-modal with varying period, I don't know of any Bayesian approach which can properly handle the problem in higher than a couple dimensions (perhaps nested sampling, but that's still a long-shot). I thought that rather than doing a half-Bayesian job which amounts to not much more than proposing some improper priors that lead to the exponent of the frequentist result, I'd stick to classical statistics here.

That said, a Bayesian approach to the multiband sinusoid-fitting problem would likely end up with a couple features:

Priors would probably take the form of some constraint on the deviation of amplitudes and/or phases within each band. Mathematically, the result would be equivalent to a nonlinear regularization of the model, and likely be similar in spirit to the ad hoc nonlinear regularization proposed in Long (2014), which we discuss briefly in the appendix. The main disadvantage is that the nonlinear optimization at each frequency is much more computationally complex (though Long points to tricks that can be used to overcome this)
Alternatively, you could construct a prior which would be precisely equivalent to our linear regularization, namely a wide Gaussian prior centered on zero for the band terms, but then you have an ad-hoc prior over parameters in a statistical rather than physical model, which to me is not much more satisfying than the statistically motivated (but admittedly still ad hoc) regularization we use.

For a truly Bayesian approach to period finding, I think a CARMA or similar model is a much better avenue (see e.g. Kelly et al 2014)

Good comments.
In the restricted context of a single sinusoid don't you think Larry Bretthorst's treatment is pretty compelling?  Sure, you have to choose what parameters you take as "nuisance" and there are many possibilities, but Larry treats the most useful case(s) IMHO.
Yes, in this context Bayes and frequentist are related one-to-one in a monotonic fashion.  But, if only cosmetically, the exponentiation can emphasize the "correct" mode at the expense of other (smaller) local maxima.  More important if you have a good handle on the observational errors the Bayesian expression gives the full posterior probability (as opposed to a single global maximum).
You make excellent points regarding uncertainty in priors making the marginalized distribution ad hoc in much the same way as regularizations.  (This is especially clear for regularization via the approximate BIC -- Bayesian Information Criterion.  I wonder what the count of regularization schemes is?  AIC, BIC, MDL, … )  Alas, well-justified priors are rare; but when then are available the so-called Occam factor in the marginal posterior avoids ad hocery.

… on a different topic.  In the discussion of Fig. 3 you state:
"Second, notice that as the number of terms is increased, the general \background" level
of the periodogram increases. This is due to the fact that the periodogram power is inversely
related to the chi-squared at each frequency. A more flexible higher-order model can better
fit the data at all periods, not just the true period. Thus in general the observed power
of a higher-order Fourier model will be everywhere higher than the power of a lower-order
Fourier model."
This seems counterintuitive to me.  Adding harmonic components to the model in the manner of eq. (14) makes the frequency, omega, represent both omega itself and its harmonics n omega, n > 1.  You can see this in the right-hand panels of Fig.3: as n goes from 1 to 2 to 3, the peak power at the true fundamental Po increases -- power from the harmonics is incorporated via eq. (14) into the fundamental.  How can one interpret the rise (from total insignificance) of the power at the first harmonic, 2 Po?  And why doesn't a better-fitting higher order model move power from the background continuum into the harmonics? -- the reverse of what you state. I am sure you are correct, but I guess I don't understand your "inversely related to … " argument.

Jeff – thanks for all the comments! I really appreciate your close read of the paper and taking the time to discuss.
A couple responses:

I think you're right that Bretthorst's treatment is compelling in terms of fitting a single sinusoid to data. But the problem is that P(omega|data, M) with M=(a single sinusoid fits our data) is not exactly what we're after. What we're after is P(omega|data, M2) where M2=(our data has a period omega), and we need to be very careful about assuming one maps to the other! For example, in typical ground-based data, the strong Fourier power in the survey window function causes all sorts of issues, to the point where I don't in practice trust the top peak in the single-sinusoid fit. So I don't trust the Bayesian posterior here to reflect the information I'm interested in, and its propensity to diminish secondary peaks seems a shortcoming rather than an advantage.
In other words, while the Bayesian result might give you the correct posterior given your assumption that a single sinusoid fits your data, that assumption is indisputably wrong! Nevertheless, a wrong model can still be a useful model. I chose in the paper to focus on the chi^2 because I think it's a less complicated discussion: in particular, we found that the true period is often among the top 5 peaks. This is easy to justify in the chi^2 view, but I think much more difficult to justify in the Bayesian picture where those peaks (given our flawed model) are suppressed by orders of magnitude!

Regarding the multi-term fits: I was thinking of them in terms of nested linear models with N parameters. At each frequency, as N increases, the chi^2 decreases. The periodogram is P = 1 - K chi^2 for some constant K, so increasing N increases the power. And this is true regardless of frequency, so the periodogram of a higher-order model is everywhere greater than the periodogram for a lower-order model.
If there's any way I can make that more clear in the discussion, I'd be open to suggestions.


Supporting Syscalls introduced in VFS: file system context

Motivation
Containerization is growing among the Linux developers, and new Syscalls were introduced in order to handle virtual filesystem using context.
Feature
Add support for the following new Syscalls that were introduced in Linux kernel 5.2

fsconfig
fsmount
fsopen
fspick

Alternatives
There are no current alternatives, since these Syscalls are not supported and show up as "unknown".
Additional context
fsconfig patch:
<EMAIL_ADDRESS>https://lwn.net/Articles/780267/
https://patchwork.kernel.org/project/linux-fsdevel/list/?series=4245&state=*&archive=both

Thanks @Osherz5!
I am tagging a couple of guys who can help with this!
/cc @andreabonanno @loresuso @Andreagit97
Thanks for the heads up!

Closing this as this is tracked by the umbrella issue in Falco!


Enhancement on new list feature: Blacklist

Don't merge. Fixing Travis CI.

Coverage decreased (-0.5%) to 91.594% when pulling f1c29ef9df6201ce187e479493c07fc481881ca4 on jaivigneshvenugopal:enhancement_for_various_lists_implementation into d2d5150f298298b22ed314f3933419630ee4c6ce on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.09%) to 92.141% when pulling ad3e40741ceba09bea6ff63cbe62f56dc1b9bb2b on jaivigneshvenugopal:enhancement_for_various_lists_implementation into d2d5150f298298b22ed314f3933419630ee4c6ce on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.2%) to 92.202% when pulling 62d4ca5890e8df5b21264b9d2a421278b97f45e7 on jaivigneshvenugopal:enhancement_for_various_lists_implementation into d2d5150f298298b22ed314f3933419630ee4c6ce on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.1%) to 92.202% when pulling 1488a789010ad8f93f201c519a3834e2679c49d7 on jaivigneshvenugopal:enhancement_for_various_lists_implementation into 1a1773cb8bbed95a21b955e72f152dddb94f55f9 on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.1%) to 92.202% when pulling 01846bf57e07d76ec9502d7a34a62604e9850166 on jaivigneshvenugopal:enhancement_for_various_lists_implementation into 1a1773cb8bbed95a21b955e72f152dddb94f55f9 on CS2103AUG2017-T17-B1:master.


Typescript error on dynamic style when the the condition is undefined

Issue and Steps to Reproduce
There's a condition where the variable that used for the condition is undefined. Example:
apply(disabled && "opacity-50")

the disabled is optional and can be undefined. Then on the vscode showing typescript error like in the screenshot
Versions

OsmiCSX v1.1.2
Expo v47

Screenshots

Expected

Should not showing any typing error

Actual

Showing typescript error on vscode

Additional Details

@Diananaa do you wanna work on this? if not I will handle this


.NET installation issue

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Hi @Tiham69
Could you please describe the problem you are experiencing?

Thank you for your response Adam Sitnik. I was having issue with the
command Terminal that dotnet was not running but it was solved by me
smashing keyboard. And thank you again for your response though.
On Tue, 5 Jul. 2022, 9:08 pm Adam Sitnik, @.***> wrote:

Hi @Tiham69 https://github.com/Tiham69
Could you please describe the problem you are experiencing?
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/7577#issuecomment-1175171985, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZCU5EPY5UY5KWARF7SH4EDVSRFVFANCNFSM52V4RFDA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Instructions clarification needed regarding AOAI deployment selection

Lab/Demo: 06
Task: Configure your application
Step: 04, second point:
Description of issue
We ask user to create two deployments in AOAI: one for embeddings and one for chat.completions. In prior version of lab, embeddings model creation wasn't necessary as we were not utilizing AI Search vectorization.
Point 2 asks the user to update appsettings.json or .env files with the "deployment name", but does not specify the name of the deployment used for chat.completion. Clarification needs to be added.

Fixed with f777c6e


Add Chinese simplified translation for README.

I created Chinese translation for README. :)

Hey @kenshinji, thanks so much for the translation! However, we just updated all of our docs and made sure we had several translations for them. 😬
Would you mind pulling down the update-docs branch and working off of that? We need an updated README-zh-CN.md, CONTRIBUTING-zh-CN.md, and CODE_OF_CONDUCT-zh-CN.md. If you could also add links all of the other docs, that would be amazing. ❤

Ok, will do that later ;)

Just a heads up, @kenshinji, we’ve just merged the new versions of all of our documents. Make sure to pull down the develop branch and work off of that. 😉

Hey @kenshinji, were you able to update the translated docs?

@trezy yeah, sure, crazy busy these days, I'll update it before the end of this week, good?

@trezy I created a new PR here https://github.com/nostalgic-css/NES.css/pull/225, pls help me to review and merge, thanks.


support resId in the way that makes sense

Currently property values are stored without paying any attention to resId. But having one single value for a property seems fundamental mistake. When resId is involved, the property values are stored like a map. juce_midi_ci has the same problem. Common Rules for PE specification itself is indeed problematic by stating almost nothing about resId. There is no access to what kind of resId is available, especially to clients.

[ ] updating property value from client request should involve resId and requireResId
[ ] updating property value locally should involve resId and requireResId
[ ] subscription should be keyed with both resource and resId
[ ] retrieving property value without resId should be prevented when requireResId is true

55a4f9d1 started some resId related changes.

I'm rather thinking, current PropertyValue should become abstract and current one should become a specialized one like CommonRulesPropertyValue. It comes with a problem on serializability though.
We should probably "serialize" the configuration itself just as UMP bytes. But that's going to be another issue (that may be first to resolve though).


[QUESTION] Example for CREATE TABLE on TRINO using HUDI

I am using Spark Structured Streaming (3.1.1) to read data from Kafka and use HUDI (0.8.0) as the storage system on S3 partitioning the data by date. (no problems with this section)
I am looking to use Trino (355) to be able to query that data. As a pre-curser, I've already placed the hudi-presto-bundle-0.8.0.jar in /data/trino/hive/
I created a table with the following schema
CREATE TABLE table_new (
  columns, dt
) WITH (
  partitioned_by = ARRAY['dt'],
  external_location = 's3a://bucket/location/',
  format = 'parquet'
);

Even after calling the below function, trino is unable to discover any partitions
CALL system.sync_partition_metadata('schema', 'table_new', 'ALL')

My assessment is that I am unable to create a table under trino using hudi largely due to the fact that I am not able to pass the right values under WITH Options. I am also unable to find a create table example under documentation for HUDI.
I would really appreciate if anyone can give me a example for that, or point me to the right direction, if in case I've missed anything.
Really appreciate the help
Environment Description

Hudi version : 0.8.0

Spark version : 3.1.1

Hive version : 3.0.0 (Metastore only)

Hadoop version : 3.2.0

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : Yes

This is more of a question than an issue, sorry couldn't apply a label for it.

@codope : Can you take this up please.

Hi Team,
any luck with this. I've tried asking this question on the slack channel for trino as well, but haven't got any luck there.

@codope gentle ping to assist here.

@gunjdesai First of all, apologies for the late response. I missed tracking this issue.
In its current state, we must sync Hudi table to Hive metastore in order to query through Trino. Our integration with Trino is via the hive connector. And that too, only for reads i.e. we cannot create hudi tables using Trino.
After syncing the Hudi table to Hive metastore and placing the hudi-presto-bundle in the hive plugin path, we can run snapshot queries on COW table and read-optimized queries on MOR table right away. You can look at an example in our docker demo. That said, we are working on a separate Hudi connector to which we'll add the write support after the base PR is merged.
I would love to understand your requirements and help you out with the Hive sync and Trino setup to query Hudi tables. You can also help us by checking out the PR linked above and test for your tables. Feel free to directly ping me on Hudi slack or join our weekly community syncs.

Thanks @codope for the detailed description. I was under the assumption that you could directly create & query hudi tables using trino. Hence our setup was of trino using hive-metastore but not hive.
Thanks to your detailed explanation, I will use the hudi-hive-sync to sync our tables and query them via Hudi and revert back to you on the same.
In the meanwhile, I will also keep an eye out for HUDI connector for trino and try to integrate it as soon as it comes out.
Thank you once again for your help. Really appreciate it.

thanks Sagar for the help.
will go ahead and close out the issue. If you come across any other issue, feel free to open a new issue.


confgenerator: add metric for retried log entries

Description
This change tests out https://github.com/fluent/fluent-bit/pull/6537 and should only be merged after the submodule has been updated to use that change. This PR exists to soak test and integration test the fluent bit commit.
Related issue
b/232158052 | P2 | Add log_entry_retry_count self metrics to Ops Agent
How has this been tested?

Checklist:

Unit tests

[ ] Unit tests do not apply.
[x] Unit tests have been added/modified and passed for this PR.

Integration tests

[x] Integration tests do not apply.
[ ] Integration tests have been added/modified and passed for this PR.

Documentation

[ ] This PR introduces no user visible changes.
[ ] This PR introduces user visible changes and the corresponding documentation change has been made.

Minor version bump

[ ] This PR introduces no new features.
[ ] This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
[ ] This PR bumps the version.

screen/mNJVGKuccErxByi
I tried a manual test by running a log generator on a VM that would write logs once every second. And then would enable a firewall rule that prevented any egress requests from the VM (forcing some log retries) and then disabled said firewall rule. As you can see the retry counts are now available on the monitoring side.
This is kind of harder to do as part of an integration test, but maybe not impossible.


Support Request:

Describe Your Problem
Linking Account is not working
Relevant log output
I have followed the instructions to create the API keys. On next step, I clicked on Link Account, I was then able to login to Honeywell and it showed my 2 Round Thermostats. I selected all and then submitted. This then came with a page which says "Please confirm the URL below is the address of your homebridge... "

The page does not redirect when I click confirm

Config for homebridge-honeywell-home
{
    "platform": "HoneywellHome",
    "name": "HoneywellHome",
    "credentials": {
        "consumerKey": "XXXXXX",
        "consumerSecret": "XXXXXXX"
    }
}

Screenshots

Device & Model
Honeywell Round Thermostat
Node.js Version
v.14.17.5
NPM Version
v.7.20.5
Homebridge Version
Hoobs
Homebridge Honeywell Home Plugin Version
10.0.1
Homebridge Config UI X Plugin Version
10.0.1
Operating System
Hoobs

You need to have homebridge v1.3.4.
I would recommend moving to homebridge.

Anyway to update the configuration manually ?

@ajayjprakash I develop this plugin for homebridge only, Sorry.


add support for actions

CAR analytics have a concept of actions associated with analytics.  For example:
process = search Process:Create
cmd = filter process where (exe == "cmd.exe")
output cmd

Add support for STIX for these actions.  This could several forms, such as a special term, or a simple property.  For example:
[process:create:name = 'cmd.exe']

or
[process:name = 'cmd.exe' and process:action = 'create']

or
create:[process:name = 'cmd.exe]

wiki writeup: Action-Proposal

Based on our team discussion we're going to go with Option 1 for this and are starting development.


Changing the "presentationHint" on a stack frame doesn't take effect until the next step

Debug something, use skipFiles
Find a grayed out frame in the callstack that says "Skipped by 'skipFiles'"
Right click, "Toggle skipping file"
The DA will send another pause event, triggering another stackTrace request
The new stack trace doesn't set the origin or presentation properties on that frame
But, the frame still appears grayed out with the origin on hover :bug:
But after I step again, then the frame is rendered correctly

This used to work, and I don't know what the difference is between the fake "refresh" stack trace and the next one after a step. And I see the same with the 2 js DAs which do this slightly differently.

Closing as will not fix.


Project name is misleading

While I'm sure it's a good resource, people coming here looking for an actual sheet or sheet-like document (which limits the amount of information it can contain) would be disappointed. Sorry to be so pedantic, but maybe consider renaming it to guide, compendium, or something?
Edit: just read that you're calling it "guide" in the README already..

Hi @timotgl , many people have been complaining about the name both on Reddit and Hackernews so you're not alone.
I understand where the complaints are coming from, but I named it a cheatsheet because everything is held in a single page document. This is why I made the repo in the first place ; every notion treated here has an explanation on the web but it was hard to find them all summarized in a single document.
It was hard to find a name for this though, because people might have been complaning about the doc not being a guide but a list of notions. Compendium seems to be it, but I'm not sure everyone knows the word (I didn't 😅).
Besides, I didn't thought that the repo would have had such an audience in the first place so I might have choosen a better name if I had seen this coming. Now it is how it is and I don't think changing the name would be a good idea for it's visibility since people have forked it and the repo has been spread.


Bonus Rewards: Add message box to add liquidity

in add liquidity form add message box to tell the user they are eligible for bonus rewards if they keep their liquidity in tell end of bonus period.

added - closing


Tagged release and bioconda package?

I'm interested in making a conda recipe for CliqueSNV so a package for it can be made available for easy installation via the bioconda channel. A couple questions: 1) would that be OK? (it's under open license, so I'm primarily asking if it is ready for distribution), and 2) Are there plans to tag a release on this repository? Doing so would be helpful for versioning of the conda package.
bioconda is an open community, and the original authors of software are also welcome to submit packages (more info on how to do so here: https://bioconda.github.io/contributor/index.html )

Hello

Yes, it's a great idea

I just tagged the latest version 1.5.5. Is it how you expect it to be? (never used tags here before). If yes, then I'll tag future releases as well

Thank you, that's great. Software versioning varies, and so too do expectations. The main rationale for building packages based on tags is that they're a way to ensure the resulting package has the version expected (rather than, say, a build from what the latest source happens to be when a conda package is built or what is included in an explicitly-specified cryptic commit hash). Conda recipes can either pulling a pre-built binary/bytecode, or build from source. Sometimes folks also include the built file as part of the tagged release (can be uploaded when tagged on the web version of GitHub); GATK is one example—the "assets" of each release includes the source as well as a zip with the built jar file. In this case it looks like this repo includes the built jar file for CliqueSNV, so the "source" package with the repository contents will contain it.
As long as the jar file exists at https://github.com/vtsyvina/CliqueSNV/blob/${TAG}/clique-snv.jar, referencing by tag will work. Otherwise if it would make more sense to build from source, it may be helpful to include build instructions in the README.md file. It looks like CliqueSNV uses a Maven-based build process, but I'd be guessing at what I would need to do to build it.

I just added "How to build" in the README.
Yes, I update the jar file at https://github.com/vtsyvina/CliqueSNV/blob/${TAG}/clique-snv.jar for each release

Thanks for adding the build instructions—easy enough!
I opened a pull request to add a package for CliqueSNV to bioconda. based on the jar file.
Once the PR is merged, CliqueSNV will be available to install via conda install -c bioconda cliquesnv (full (bio)conda setup instructions here).


Continuous Deployment and Tests

This PR introduces acceptance testing that makes sure the raffler is running well. These are fully functional and not unit tests, mostly due to easier coverage and the fact that our usual failures are due to external factors or coordination of the whole. So win, win.
These tests are written in nightmare.js but some things are still in progress.

[ ] Await for Electron  to be able to run headless in CircleCI (or find functioning workaround) [segmentio/nightmare#224 and electron/electron#228]

You can run headless Electron with xvfb. Let me know if you have any questions.

@lastmjs i tried  a couple versions of that and none worked out, could you fork from this branch and get our circle.yml in shape? I would appreciate that very much. Thanks


Adds doc strings for attributes in base_model and base_submodel

Description
Related #4170
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[ ] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

I have added doc strings for a few private attributes. Am I going in the right direction with this or do I have to add the doc strings defining the attributes to the main doc string defining the class?

Hi! I think you are going in the right direction (but asked a review from @kratman as he opened the issue). Could you also add docstrings to the properties that return an empty dictionary. After defining what the method does, you can say that it returns an empty dictionary and that is defined in inheriting classes.

@brosaplanella, @medha-14 The #4170 was a much larger ticket and probably should not be marked as "fixed" by this PR. It originally came from when I was fixing IDE inspections that said things like _rhs were not documented. Essentially the doc strings were out of date because the _ was missing. The whole ticket is probably quite a lot more than this because there are plenty of classes where the arguments and attributes should be checked.

@kratman Could you confirm if the approach I took to address the issue was correct? If so, should I proceed by implementing similar changes in other classes as well? Additionally, could you please advise on which specific classes I should apply the required changes to?

@medha-14 I was suggesting that you edit your PR description to remove the fixes part. Change it to "Related #4170" instead. Otherwise it will close the ticket when the ticket is probably larger than a single PR.
As far as the approach, I don't see any issues with adding more doc strings, but the original topic was about the class-wide doc string block. You want to turn on inspections in your IDE to make sure you also clean up any undocumented or incorrectly documented attributes there too.
The end goal should be making sure that all publicly accessible attributes appear in the documentation and none of the private ones are shown. Many of those are the properties, so this is a good start. It is a fairly open ended and visual task, you just have to go into the documentation and make sure everything is appearing.
You have some docs warnings to sort out as well:
/home/runner/work/PyBaMM/PyBaMM/src/pybamm/models/base_model.py:docstring of pybamm.BaseModel.boundary_conditions:1: WARNING: duplicate object description of pybamm.BaseModel.boundary_conditions, other instance in source/api/models/base_models/base_model, use :no-index: for one of them
/home/runner/work/PyBaMM/PyBaMM/src/pybamm/models/base_model.py:docstring of pybamm.BaseModel.name:1: WARNING: duplicate object description of pybamm.BaseModel.name, other instance in source/api/models/base_models/base_model, use :no-index: for one of them
/home/runner/work/PyBaMM/PyBaMM/src/pybamm/models/base_model.py:docstring of pybamm.BaseModel.variables:1: WARNING: duplicate object description of pybamm.BaseModel.variables, other instance in source/api/models/base_models/base_model, use :no-index: for one of them

Thanks for the review. I have added all public attributes in base_model and base_submodel to the respective class wide doc strings.

@medha-14 As a helpful guide, you should turn on inspections in your IDE then a lot of this shows up. PyCharm is what alerted me to the problem in the first place.
Basically we had docs for variables that used to be public (e.g. rhs), once they were made private like (e.g. _rhs), the docs were not updated so the variables do not even exist in the class. Ticket #4170 was about going through and making sure are the private attributes' documentation was removed, but then making sure the properties are properly documented.
I split that into a separate task from the original PR because I was not sure of the best way to handle it. It might be doc strings on the properties, it might be putting documentation in the main class's doc string block while properly marking them as properties. I am not sure what the correct fix is off the top of my head. You need to turn on IDE inspections so you can find stuff that is incorrect in the existing doc strings (most IDEs have plugins for doc warnings), and you need to view the generated documentation to make sure it all appears correctly. Sphinx probably has suggestions for how to document properties properly.

Thank you for your review and feedback. I've successfully resolved all warnings related to unresolved references in the documentation and removed all private attributes. I utilized PyCharm to address these warnings and ensured that properties are documented according to the Sphinx format. If there are any additional suggestions for improvements, I would be happy to work on them.

Thanks @medha-14 I will go through another review later

Thank you for the prompt reviews and guidance @kratman.


Remove version: NumeRe.NumeRe version <IP_ADDRESS>3

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/numere/files/v<IP_ADDRESS>3/numere-win-v115rc.exe/download
Status Code: 200
(Automated message - build 897)

Close with reason: Package still available.;


ESR (#12) - API

The SDN Controllers must adhere to relevant security standards and best practices for API security including REST security principles as recommended by OWASP, NIST, and ISO/IEC.

Comments from TC meeting on Feb 8
must be refined and more detailed, which specific SFRs and best practices should be clarified
be more specific – keep it for now...

A bit refined and more detailed, shared below, as suggested. Please let us know what you think, otherwise, we will keep the above ones. Please add/delete as you find appropriate:

SDN Controllers must comply with established security standards and implement best practices for API security, particularly emphasizing REST security principles. They are expected to follow guidelines set forth by recognized entities like OWASP, NIST, and ISO/IEC. This involves ensuring secure authentication, authorization, encryption, and coding practices, alongside conducting regular security evaluations and managing vulnerabilities to protect against current and emerging cyber threats.

SDN Controllers are mandated to conform to essential security standards, focusing on API security and REST security principles as outlined by leading organizations such as OWASP, NIST, and ISO/IEC. This includes adopting secure authentication and authorization practices, data encryption, and following secure coding guidelines. Additionally, they must engage in continual security assessments and vulnerability management to mitigate against a spectrum of cyber risks.

I'm concerned by calling out of REST in particular. If I have a product which uses gRPC, it sounds like I am excluded. I doubt this is the intent.
Would it be better to remove the line "particularly emphasizing REST security principles" from (1)?


uiux(client): Disable editor horizontal scrollbar on web and tablet

fixes #785
Used the BreakpointObserver to disable word wrapping on tablet and web. Should we enable word wrapping on tablet as well?
P.S. Was back and forth on the commit type. Is uiux ok?

I didn't enable wordwrapping in the embedded editor view because we can't know in which size/context the embedded editor is shown. We could add a query param setting to the embedded editor page, something like &wordwrap=true.

Looking into this now.

Okay, so I tested it locally and it doesn't really behave the way we want  it to. Just to recall: we want the editor to be horizontally scrollable when in mobile viewport, and going into wordwrap mode on desktop. Right now it's behaving the exact opposite way.

The breakpoint observer is not exactly doing what I expect it to do. I thought it really detected the device it was running on, but looking at the sourcecode, I noticed it checks the size of the screen. So with the current implementation, when you scale the viewport, the wordwrapping is constantly toggling between on and off.

This is because the Breakpoints.Tablet and Breakpoints.Web breakpoints are defined for portrait and landscape and there for introduce some "gaps" where they don't match, which makes the configuration jump back and forth.
I ran into a similar thing when I ported the Breakpoints to our SCSS for responsive design. That's why I introduce additional breakpoints like "portrait up" or "landscape up" which is kind of the min-width equivalent. You can take a look here: https://github.com/machinelabs/machinelabs/blob/master/client/src/mixins.scss#L68-L74
Unless Angular Material/CDK provides breakpoints that match our needs, I think we need to introduce our own equivalent in TS then and maybe open an issue on CDKs repo for clarification. Maybe there's plans on their side to fix this.


Bluetooth: Audio - internal changes to media proxy instance structure

Updates an include guard, and moves a callback struct inside the media proxy instance struct.
closes https://github.com/zephyrproject-rtos/zephyr/issues/41201

Rebased on main with no changes.


Scroll view working so fast

devexteme version: 18.1.4
devextreme-angular version: 18.1.4

[ ] bug Report
https://stackblitz.com/edit/angular-skrhrf?file=src%2Fapp%2Fapp.component.html
**This project is a small example of the problem. You can also examine the problem in the following images in detail.
https://image.ibb.co/nb3dBo/bandicam_2018_07_14_19_46_00_178.gif
https://image.ibb.co/cJryBo/bandicam_2018_07_14_19_43_10_941.gif

You mean it doesn't have "smooth" scroll effect or what exactly is the problem? From what I can see, it works as expected.

Hi,

Yes, dxScrollView operates in this manner and there is no option to change this behavior. We will consider adding an API that will help you adjust scrolling speed.

If the current behavior does not meet your requirements, wrap your content in a scrollable DIV element. This is the only option we can suggest at the moment.
<div style=" overflow-y:scroll; ...">
   ...
</div>


Updated the application for rails 5.1 and ruby 2.3.5

closes #68 #85

Coverage decreased (-0.07%) to 97.257% when pulling 60037a195c52505cdb82939e637f1593f2c4c028 on rails-5.1 into f14bb2528902cd5efd2e50c562844e7ea1758ce5 on master.

Coverage decreased (-0.07%) to 97.257% when pulling 1824bd9b199b2f36c89040df6310766e2d60f443 on rails-5.1 into f14bb2528902cd5efd2e50c562844e7ea1758ce5 on master.

This needs to be rebased. A few of these changes conflict with some things I did in the master branch while adding in the new stat graphs.

Coverage decreased (-0.07%) to 97.283% when pulling c150fde5a5bcd27bfc1d33f31a01b50c2d488ad2 on rails-5.1 into c05952ec351dd940f3dd47f7609919a33c43be0b on master.


HmIP Schlüsselsensor HmIP-DLS fehlt

Device related data
If you want to add a new device or add a feature to a new device, please login to your hap-homematic WebUI; Select Internal/Help and create the device description file as described in the dialog you will get. Please attach the file to your request.
{
"devices": [
{
"id": 1000,
"intf": 0,
"intfName": "",
"name": "HmIP-DLS",
"address": "2297857947ABCD",
"type": "HmIP-DLS",
"channels": [
{
"id": 1001,
"name": "2297857947ABCD:0",
"intf": 0,
"address": "2297857947ABCD:0",
"type": "MAINTENANCE",
"access": 255
},
{
"id": 1002,
"name": "2297857947ABCD:1",
"intf": 0,
"address": "2297857947ABCD:1",
"type": "DOOR_LOCK_STATE_TRANSCEIVER",
"access": 255
},
{
"id": 1003,
"name": "2297857947ABCD:2",
"intf": 0,
"address": "2297857947ABCD:2",
"type": "ALARM_COND_SWITCH_TRANSMITTER",
"access": 255
}
]
}
]
}

@thkl :)


RARBG returns results after trying 5+ tries most of the time. Not sure what is the reason if anything is broken. LOGS included.

RARBG returns results after trying 5+ Times most of the time. Not sure what is the reason if anything is broken.
Log:
kodi.log
As u can see in the log this is where it accepts it after refusing many times:
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] Status for 'https://torrentapi.org/pubapi_v2.php?mode=search&search_imdb=tt10872600&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=rldngs9pzw' : 200
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Accepted resolutions: ['filter_240p', 'filter_480p', 'filter_720p', 'filter_1080p', 'filter_2k', 'filter_4k']
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Accepted release types: ['240[pр]', 'vhs\\-?rip', '480[pр]', 'xvid|dvd|dvdrip|hdtv|web\\-(dl)?rip|iptv|sat\\-?rip|tv\\-?rip', '720[pр]|1280x720', 'hd720p?|hd\\-?rip|b[rd]rip', '1080[piр]|1920x1080', 'hd1080p?|fullhd|fhd|blu\\W*ray|bd\\W*remux', '1440[pр]', '2k', '4k|2160[pр]|uhd', '4k|hd4k', 'brrip|bd\\-?rip|blu\\-?ray|bd\\-?remux', 'web_?\\-?dl|web\\-?rip|dl\\-?rip|yts', 'hd\\-?rip', 'hd\\-?tv', 'dvd|dvd\\-?rip|vcd\\-?rip', 'dvd\\-?scr', 'screener|scr', 'telesync|ts|tc', 'tv\\-?rip|sat\\-?rip|dvb', 'vhs\\-?rip', 'iptv\\-?rip']
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Blocked release types: ['3d', 'cam|hd\\-?cam', 'trailer|трейлер|тизер', 'workprint', 'line']
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Minimum size: 0.0 GB
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Maximum size: 150.0 GB
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] JSON response from API: {'error': 'No results found', 'error_code': 20, 'rate_limit': 1}
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] result_keys: ['torrent_results']
2023-01-29 03:11:29.181 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] results: []
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] >>>>>> rarbg would send 0 torrents to Elementum <<<<<<<
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] >>>>>> rarbg would send 0 torrents to Elementum after cleanup <<<<<<<
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Before keywords - Query: '{tmdb_id}' - Extra: 'search_themoviedb'
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] After keywords  - Query: '634649' - Extra: 'search_themoviedb'
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] -   rarbg query: '634649'
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] --  rarbg url_search before token: 'https://torrentapi.org/pubapi_v2.php?mode=search&search_themoviedb=634649&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=TOKEN'
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] --- rarbg using POST payload: {}
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] ----rarbg filtering with post_data: {}
2023-01-29 03:11:29.182 T:1904  WARNING <general>: [script.elementum.burst] [rarbg] Reusing existing token
2023-01-29 03:11:29.182 T:1904  WARNING <general>: [script.elementum.burst] [rarbg] >                RARBG search URL: https://torrentapi.org/pubapi_v2.php?mode=search&search_themoviedb=634649&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=rldngs9pzw
2023-01-29 03:11:29.182 T:1904    DEBUG <general>: [script.elementum.burst] Opening URL: 'https://torrentapi.org/pubapi_v2.php?mode=search&search_themoviedb=634649&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=rldngs9pzw'
2023-01-29 03:11:29.285 T:4028    DEBUG <general>: [script.elementum.burst] Timer: 9s / 27s
2023-01-29 03:11:29.390 T:16256   DEBUG <general>: XCURL::DllLibCurlGlobal::CheckIdle - Closing session to https://image.tmdb.org (easy=0x2eabf786a80, multi=0x2eab6afd1c0)
2023-01-29 03:11:29.536 T:4028    DEBUG <general>: [script.elementum.burst] Timer: 9s / 27s
2023-01-29 03:11:30.038 T:4028    DEBUG <general>: Skipped 1 duplicate messages..
2023-01-29 03:11:30.038 T:4028    DEBUG <general>: [script.elementum.burst] Timer: 10s / 27s
2023-01-29 03:11:31.041 T:4028    DEBUG <general>: Skipped 3 duplicate messages..
2023-01-29 03:11:31.041 T:4028    DEBUG <general>: [script.elementum.burst] Timer: 11s / 27s
2023-01-29 03:11:32.043 T:4028    DEBUG <general>: Skipped 3 duplicate messages..
2023-01-29 03:11:32.043 T:4028    DEBUG <general>: [script.elementum.burst] Timer: 12s / 27s
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] Status for 'https://torrentapi.org/pubapi_v2.php?mode=search&search_themoviedb=634649&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=rldngs9pzw' : 200
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Accepted resolutions: ['filter_240p', 'filter_480p', 'filter_720p', 'filter_1080p', 'filter_2k', 'filter_4k']
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Accepted release types: ['240[pр]', 'vhs\\-?rip', '480[pр]', 'xvid|dvd|dvdrip|hdtv|web\\-(dl)?rip|iptv|sat\\-?rip|tv\\-?rip', '720[pр]|1280x720', 'hd720p?|hd\\-?rip|b[rd]rip', '1080[piр]|1920x1080', 'hd1080p?|fullhd|fhd|blu\\W*ray|bd\\W*remux', '1440[pр]', '2k', '4k|2160[pр]|uhd', '4k|hd4k', 'brrip|bd\\-?rip|blu\\-?ray|bd\\-?remux', 'web_?\\-?dl|web\\-?rip|dl\\-?rip|yts', 'hd\\-?rip', 'hd\\-?tv', 'dvd|dvd\\-?rip|vcd\\-?rip', 'dvd\\-?scr', 'screener|scr', 'telesync|ts|tc', 'tv\\-?rip|sat\\-?rip|dvb', 'vhs\\-?rip', 'iptv\\-?rip']
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Blocked release types: ['3d', 'cam|hd\\-?cam', 'trailer|трейлер|тизер', 'workprint', 'line']
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Minimum size: 0.0 GB
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] Maximum size: 150.0 GB
2023-01-29 03:11:32.210 T:1904    DEBUG <general>: [script.elementum.burst] [rarbg] JSON response from API:

@Kristijan1001
try to open (from the same network) the "final" search URL from your log file, like:

2023-01-29 03:11:29.182 T:1904    DEBUG : [script.elementum.burst] Opening URL: 'https://torrentapi.org/pubapi_v2.php?mode=search&search_themoviedb=634649&category=14;48;17;44;45;47;50;51;52;42;46;54&format=json_extended&app_id=script.elementum.burst&token=rldngs9pzw'

for me it almost always gives {"error":"No results found","error_code":20,"rate_limit":1}.
probably some anti-robot/anti-ddos protection or they use some caching and it is broken at the moment.
so, imho, not an elementum issue.

Got worsened in the past months, couldn't get more than 1 or 2 results in weeks, only magnets work.
Surely there must be something with Burst that needs to be updated (that bypass those "anti-robot/ddos protection").
BTW, there is some comfort when sometimes one more provider that usually shows very misleading info (wrong s/p --because it's not synced live with their site, or not the same link title name with the [rartv]) but will actually use the same rarbg link when starting to download including the correct s/p.
Really hope someone will find a way, as for today rarbg is still no' 1 (HDR10+/DV), far ahead of any other.

I'm experiencing the exact same behavior. It would be great if we could fix this behavior as Rarbg is by far the best public provider. Searching 5+ times with no errors to finally get search results is frustrating.

@Shazb0t Rarbg is now closed, that is why is it removed: https://rarbg.to/

Also closed: zooqle, ETTV (www.ettvcentral.com).

torrentdownloads.info new domain: .pro / .me
There's another torrentdownload.info site btw (without the "s")

torrentz2.is / torrentz.is are dead, torrentz2k.xyz never shows results because the site has some strange 404 messages for 1 second before loading the correct domain.

looks like https://bt4g.org is a good replacement.

These are all just from what I recall right now, hope it helps a little.
Other providers work fine. TGx is the best alt-rarbg right now so, all good.

@SubEdict thanks, i created #336 to disable those.


Adds onHover and onLongPress to IconButton widget

Adds onHover and onLongPress to IconButton widget
fix #159972
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

@TahaTesser Thank you for your suggestion, I will implement it ASAP

cc: @bleroux

I tried using a Column, but I encountered a problem with the finder retrieving multiple iconButtons. I researched how to test multiple variants with a single method and found that the testWidgets method has a variant parameter. I used it, but there are some variables outside the method. Is this considered good practice?
I will push the results. Please let me know if this is good practice. If there are any issues, I will revert the commit.

@M97Chahboun
I understand what you're encountering. You can still column and put those variants, instead of using just find.byType (because it cannot find variants). Use find.ancestor, you can say ancestor of an icon which is find.byType IconButton.
You can similar find.ancestor examples in the source code. Also please revert the workaround if you decide to find.ancestor which is much simpler and it is perfect to find such objects.

I'll be on vacation from now until Jan 2nd, @bleroux can help review this next week.

I tried using a Column, but I encountered a problem with the finder retrieving multiple iconButtons.

One simple way to mitigate this, is to set a different icon for each button and use a finder such as:
find.widgetWithIcon(IconButton, Icons.wb_sunny_outlined).

I researched how to test multiple variants with a single method and found that the testWidgets method has a variant parameter. I used it, but there are some variables outside the method. Is this considered good practice?
I will push the results. Please let me know if this is good practice. If there are any issues, I will revert the commit.

testWidgets variant (subclasses of TestVariant) is on over complex feature in the context of this PR.
The main usages of TestVariant is through predefined variants, the main one being TargetPlatformVariant which allow to specify the target platform (iOS, linux, etc) for a test.

@bleroux Thank you for your reviews


chore: increase github action runner size

Is this available already @FabienArcellier ?

Is this available already @FabienArcellier ?

Yes the runner are enable in github actions.

Woohoo can't wait


Running make command fails.

What happened?

Failure when running make command from the home of repo as below:
➜ crossplane-provider-aws ✗ make
17:39:31 [ .. ] verify dependencies have expected content
all modules verified
17:39:35 [ OK ] go modules dependencies verified
17:39:35 [ .. ] installing golangci-lint-v1.23.8 linux-amd64

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
17:39:39 [FAIL]
build/makelib/golang.mk:345: recipe for target 'XXX/crossplane-provider-aws/.cache/tools/linux_amd64/golangci-lint-v1.23.8' failed
make[2]: *** [XXX/crossplane-provider-aws/.cache/tools/linux_amd64/golangci-lint-v1.23.8] Error 1
build/makelib/common.mk:302: recipe for target 'build.all' failed
make[1]: *** [build.all] Error 2
build/makelib/common.mk:313: recipe for target 'build' failed
make: *** [build] Error 2

How can we reproduce it?

Close latest master
change to dir
Run make

What environment did it happen in?
Crossplane version:
latest Master

Hey @rajalokan! Apologies, this can be a bit confusing :/ I believe if you run make submodules first then this should work for you 👍

I'm afraid, this didn't solve for me.
 ➜ crossplane-provider-aws ✗ make submodules
Synchronizing submodule url for 'build'
 ➜ crossplane-provider-aws ✗
 ➜ crossplane-provider-aws ✗
 ➜ crossplane-provider-aws ✗
18:58:13 [ .. ] verify dependencies have expected content
all modules verified
18:58:21 [ OK ] go modules dependencies verified
18:58:22 [ .. ] installing golangci-lint-v1.23.8 linux-amd64

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
18:58:26 [FAIL]
build/makelib/golang.mk:345: recipe for target 'XXX/crossplane-provider-aws/.cache/tools/linux_amd64/golangci-lint-v1.23.8' failed
make[2]: *** [XXX/crossplane-provider-aws/.cache/tools/linux_amd64/golangci-lint-v1.23.8] Error 1
build/makelib/common.mk:302: recipe for target 'build.all' failed
make[1]: *** [build.all] Error 2
build/makelib/common.mk:313: recipe for target 'build' failed
make: *** [build] Error 2
 ➜ okan@dembouz11 crossplane-provider-aws ✗

Getting same error. In my investigation it fails at this line while doing curl GOLANGCILINT.

Seems to be issue with my local setup. Thanks for the quick help.


Add a TextResponse?

There is currently the base Response, but also HtmlResponse, JsonResponse, etc.
That's practical when we want to return HTML or JSON, but there is no simple TextResponse (or PlainTextResponse. That's not a huge deal, but writing a simple hello world is just plain confusing.
Example:
// Super verbose
$response = new Response();
$res = $res->withHeader('content-type', 'text/plain');
$response->getBody()->write('Hello world!');
return $response;

// Wrong content type, but at least it's simpler and shorter
return new HtmlResponse('Hello world');

Do you think it would make sense to add a new TextResponse class?
Or even simpler if we could use the base Response class to return plain text content, but the $body parameter in the constructor seems to only accept streams. Maybe it could accept a plain string? (but then how to differentiate from a stream…)

@mnapoli The base Response class is supposed to be general-purpose, and work for both client and server-side; as such, the constructor targets a stream. (As you note, this also prevents the need for trying to differentiate from a stream; it's either a valid stream resource DSN or it isn't.)
The various response types under the Zend\Diactoros\Response hierarchy are the more specific implementations, and I'd be quite happy to entertain a TextResponse or PlainTextResponse implementation there.

:+1: makes sense about the generic response class, will work on a TextResponse tomorrow!

Closed with #77.


Changed "operation" to be required in Function Definitions

[x] Specification
[ ] Schema
[ ] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

What this PR does / why we need it:
operation not being required in Function definitions seems to be a bug. The web editor complains if we don't define an operation in a function definition.

If the editor is complaining, then I understand the scheme is correct, the only missing issue is in the description?

If the editor is complaining, then I understand the scheme is correct, the only missing issue is in the description?

Yes. The scheme is correct.
https://github.com/serverlessworkflow/specification/blob/da216bf69700d5ef0bcfd441bb6bd46285226b02/schema/functions.json#L40


Polkadot v0.9.13

Still WIP

Separate dev-net Thala, refactor node to support mulitple runtimes
Upgrade to Polkadot v0.9.13 (upstream hasn't release yet)

Upstream Polkadot 0.9.13-rc1 released, and they fix compiling issue, so it's time to prepare ours