cleanup(select): remove runtime checkbox padding calculation workaround

The previous change handled the transition period where we had two different size psuedo checkboxes in the the external and internal versions of the psuedo checkbox.  The psuedo checkbox is used by the select for multiple selecting.


Allow to select a branch

It would be excellent if one could select the branch to deploy from. We have different environments (auth0 tenants), but the rules are nearly the same. At the moment, each environment has a repo, but it would be much more convenient if we could use one repo and different branches to make the changes to the rules eg. develop -> test -> master.

Sorry, please ignore this issue.


Clarification needed. Left box plus used in Right Invariance filter.

Dear, @joansola and @artivis
I'm looking into the implementation of the UKF on manifold from this repo.
I've just noticed, that in the case of the Right Invariance sigmas and increments are added to the current state using the left box plus operator. In which frame P (covariance) is expressed then? Local tangent space at X, or global at the group origin?
I expected that with Right Invariance increments and covariance are expressed in the local tangent space at X and thus right box plus operator shall be used.
https://github.com/artivis/kalmanif/blob/5e0f1f2275e22979afa39d8f67782929f21c1072/include/kalmanif/impl/unscented_kalman_filter_manifolds.h#L155-L161
At the same time, in the example from manif repo, the description matches the operator used to add sigma increments to the state.
*  The estimation error dx and its covariance P are expressed
*  in the tangent space at X.

https://github.com/artivis/manif/blob/805a0b2adf9435dd658fdad5606c342db4d889e8/examples/se2_localization_ukfm.cpp#L311
        // sigma points on manifold
        for (int i = 0; i < DoF; ++i)
        {
          s_j_p = X + manif::SE2Tangentd( xis.col(i));
          s_j_m = X + manif::SE2Tangentd(-xis.col(i));

          xis_new.col(i) = (X_new.lminus(s_j_p + u_est)).coeffs();
          xis_new.col(i + DoF) = (X_new.lminus(s_j_m + u_est)).coeffs();
        }

Thank you in advance for your answer!
Best regards,
Alex

@slovak194,
First of all I have to point that the UKFM examples in manif are wrong and listed on my todo list for a fix. You should therefore refer the kalmanif implementation as the most up to date.
To answer your question clearly, the covariance P is expressed in the global frame at the group origin.
Note that the README states: Both the IEKF and UKFM filters are implemented in their 'right invariant' flavor. However they are able to handle both 'right' and 'left' measurements.
The conditional invariance you've linked to is only related to the measurement model used.
This being said, this topic isn't trivial and a little far in my memories. That's why I have just added some old and partial notes on the invariance topic. They are based on [1] and other publications from the same authors/group.
Mind that the right/left invariance definition comes from this line of work and may be a little confusing with respect to our definition of right/left box-plus. Indeed they are somewhat inversed in that the right invariance is naturally associated with the left box-minus and the left invariance goes in pair with the right box-minus. This is all detailed in eqs (7-10) in the notes.
Let me know if those notes are any useful and if you have any further question.
[1] “The Invariant Extended Kalman Filter as a Stable Observer” A. Barrau and S. Bonnabel.


CS1503

[Enter feedback here]
The groundCheck variable uses groundCheckRadius to evaluate whether the Player is on the surface
"playerIsGrounded = Physics2D.OverlapCircle(groundCheck.position, groundCheckRadius, ground);"

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

ID: 5f98776d-66cc-91ad-697a-783f80914f9c
Version Independent ID: 66121850-861c-9e37-27f0-811f80427d70
Content: Compiler Error CS1503
Content Source: docs/csharp/misc/cs1503.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

@RatalBad
I don't have enough context to understand what should change in the documentation. This may be a question that is better answered in our Q & A forums. Can you provide more info on what the issue with our content is?


Automated cherry pick of #1770: scheduler: schedtag predicate match resources then do filter

Cherry pick of #1770 on release/2.11.0.
#1770: scheduler: schedtag predicate match resources then do filter

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11.0@18aee8c). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.11.0   #1772   +/-   ##
================================================
  Coverage                  ?   7.64%
================================================
  Files                     ?     412
  Lines                     ?   63212
  Branches                  ?       0
================================================
  Hits                      ?    4832
  Misses                    ?   57970
  Partials                  ?     410

Flag
Coverage Δ

#aFlag
7.64% <ø> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 18aee8c...98ee0f8. Read the comment docs.

/lgtm
/approve


Errors in Console (Cannot read property 'isValid' of undefined)

we are using the px-calendar-picker in APM component. for one of the use case while loading this polymer component we are getting the below error logs in console. it is happening only in chrome not in other browsers. we investigate the issue in  px-calendar-cell.html and found that the filed "displayDate" is initialized as undefined and will be initialized after notifying the observers(_updateDate) associated with this property. till it get initialized this error logs keeps occurring.
polymer-mini.html:2128 Uncaught TypeError: Cannot read property 'isValid' of undefined
at HTMLElement. (px-calendar-cell.html:99)
at Debouncer.complete (polymer-mini.html:2167)
at Debouncer.boundComplete (polymer-mini.html:2144)
at Object._atEndOfMicrotask (polymer-mini.html:2122)
at MutationObserver.window.MutationObserver.observe.characterData (polymer-mini.html:2137)
(anonymous) @ px-calendar-cell.html:99
complete @ polymer-mini.html:2167
Debouncer.boundComplete @ polymer-mini.html:2144
_atEndOfMicrotask @ polymer-mini.html:2122
window.MutationObserver.observe.characterData @ polymer-mini.html:2137

I believe this would have been resolved by the undefined check in the Polymer 2 hybrid upgrade. Please reopen / let us know if that is not the case.


broke image link to cloudfront.net

the html was changed to
<img<EMAIL_ADDRESS>style="width:850px;height:115px;">

This extension does not replace "cloud", only "the cloud".  You are using a fork.  See README for more info.


Initial manager missing infrakit tags

Flow:

Bootstrap VM creates initial manager with LogicalID of mgr1 in os group mode with shared NFS for terraform files
mgr1 then commits a group with the 2 (or 4) additional managers
group controller detects that mgr1 already exists and issues a Provision for the additional members

The managers group is successfully created with the following members:
+ infrakit group describe managers
ID                            	LOGICAL                       	TAGS
instance-1499453209           	mgr3                          	infrakit-link-context=swarm::rnn3rirgdngoflx2xlmgilzbj::manager,infrakit-link-created=2017-07-07t18:46:47z,infrakit-link=za1pnvookmnx4ylh,infrakit.config_sha=qhzuig2vfziwccsahjlawpwzrdp44gi3,infrakit.group=managers,logicalid=mgr3,name=instance-1499453209,swarm-id=rnn3rirgdngoflx2xlmgilzbj
instance-1499453211           	mgr2                          	infrakit-link-context=swarm::rnn3rirgdngoflx2xlmgilzbj::manager,infrakit-link-created=2017-07-07t18:46:47z,infrakit-link=ynas3ip2mep6z373,infrakit.config_sha=qhzuig2vfziwccsahjlawpwzrdp44gi3,infrakit.group=managers,logicalid=mgr2,name=instance-1499453211,swarm-id=rnn3rirgdngoflx2xlmgilzbj
instance-1499452504           	mgr1                          	infrakit.config_sha=2wrobluhcc7havbj5hlpxfpv6lmwwdzx,infrakit.group=managers,logicalid=mgr1,name=instance-1499452504

Since mgr1 was not created using the swarm flavor it is missing the infrakit-link-context, infrakit-link-created, infrakit-link, and swarm-id tags. Also, the infrakit.config_sha tag is different then the other 2 managers.
The instance SPI has a Label function that can be used to update the tags on mgr1.  https://github.com/docker/infrakit/blob/master/pkg/spi/instance/spi.go#L31
@chungers Any ideas on how we can update the tags on mgr1 to make them consistent with the others?

@kaufers  - I think if you label the initial manager with a label bootstrap, the group controller will essentially assimilate it and considers it a member of the group and update its labels:
https://github.com/docker/infrakit/blob/master/pkg/plugin/group/scaled.go#L191
convergence: https://github.com/docker/infrakit/blob/master/pkg/plugin/group/scaler.go#L230

Thanks @chungers; this appeared to update the infrakit.config_sha label on the initial manager correctly.
+ docker exec d4b-instance-plugin infrakit group describe managers
ID                            	LOGICAL                       	TAGS
instance-1501184046           	mgr1                          	infrakit.config_sha=cldtgspin74nag7ytzjlgcl3ne6xlztf,infrakit.group=managers,logicalid=mgr1
instance-1501184432           	mgr3                          	infrakit-link-context=swarm::wa39pil0zk243rq2y285rl69t::manager,infrakit-link-created=2017-07-27t19:40:30z,infrakit-link=jkykcjdir4u7qj6c,infrakit.config_sha=cldtgspin74nag7ytzjlgcl3ne6xlztf,infrakit.group=managers,logicalid=mgr3,name=instance-1501184432,swarm-id=wa39pil0zk243rq2y285rl69t
instance-1501184435           	mgr2                          	infrakit-link-context=swarm::wa39pil0zk243rq2y285rl69t::manager,infrakit-link-created=2017-07-27t19:40:30z,infrakit-link=pnfel8wcfq7uvser,infrakit.config_sha=cldtgspin74nag7ytzjlgcl3ne6xlztf,infrakit.group=managers,logicalid=mgr2,name=instance-1501184435,swarm-id=wa39pil0zk243rq2y285rl69t

However, the initial manager is still different then the others.

What about the other tags that are missing on mgr1; do they matter?
What about the fact the there the docker engine on the initial manager does not have any infrakit-* labels?

The config sha is the most important because that's how infrakit determines if the nodes in the group are of the same configuration.  The other flags, in particular, the link-context, is a 'join' key that associates a swarm node to an infrastructure node /host.  This ideally should be the label for Docker engine on the initial node, but it most certainly isn't, because we wouldn't know what values to set (those are generated by the swarm flavor plugin).
However, these labels can be pre-assigned and set up as the initial Docker engine labels..  For example, we could set it up so that the first node has the infrakit-link-context label set to some known value, say, "bootstrap", as any string value would work as long as the Docker engine and host all have the same values (thus the 'join').  The only other label missing is the swarm id, but that is just informational only and doesn't serve any purposes for infrastructure orchestration and monitoring.


Add a new search_type option  similarity_with_score to VectorStore

I have added similarity_with_score as an option to the search_type parameter in the search method of the VectorStore class. When this string is specified, it will execute similarity_search_with_relevance_scores, allowing you to reference the score obtained from there in the metadata field of the Document.
This is a typical use case, particularly with the intention of being able to reference the score in the metadata of the Document obtained by RetrievalQA. One of the main motivations is to enable users to handle various actions using the score. For example, if the average score of the results obtained by RetrievalQA is below a certain threshold, users can return a typical message to the end user, and so on, using the score.
from langchain.chains import RetrievalQA
from langchain.chat_models import ChatOpenAI
from langchain.embeddings import OpenAIEmbeddings
from langchain.vectorstores import FAISS
from langchain.document_loaders import TextLoader
from langchain.embeddings.openai import OpenAIEmbeddings
from langchain.text_splitter import CharacterTextSplitter
from langchain.vectorstores import FAISS
from langchain.document_loaders import TextLoader

loader = TextLoader("../docs/modules/state_of_the_union.txt")
documents = loader.load()
text_splitter = CharacterTextSplitter(chunk_size=1000, chunk_overlap=0)
docs = text_splitter.split_documents(documents)
embeddings = OpenAIEmbeddings()
vectorstore = FAISS.from_documents(docs, embeddings)
retriever = vectorstore.as_retriever(search_type="similarity_with_score")  # <- specify similarity_with_score option
qa_chain = RetrievalQA.from_chain_type(
    llm=ChatOpenAI(model_name="gpt-3.5-turbo", temperature=0),
    chain_type="stuff",
    retriever=retriever,
    verbose=True,
    return_source_documents=True,
)
r = qa_chain("What is the meaning of life?")

r['source_documents'][0]
# > Document(page_content='And built the strongest, freest, and most prosperous nation the world has ever known. \n\nNow is the hour. \n\nOur moment of responsibility. \n\nOur test of resolve and conscience, of history itself. \n\nIt is in this moment that our character is formed. Our purpose is found. Our future is forged. \n\nWell I know this nation.  \n\nWe will meet the test. \n\nTo protect freedom and liberty, to expand fairness and opportunity. \n\nWe will save democracy. \n\nAs hard as these times have been, I am more optimistic about America today than I have been my whole life. \n\nBecause I see the future that is within our grasp. \n\nBecause I know there is simply nothing beyond our capacity. \n\nWe are the only nation on Earth that has always turned every crisis we have faced into an opportunity. \n\nThe only nation that can be defined by a single word: possibilities. \n\nSo on this night, in our 245th year as a nation, I have come to report on the State of the Union.', metadata={'source': '../docs/modules/state_of_the_union.txt', 'score': 0.6600354698630632})

r['source_documents'][0].metadata
# > {'source': '../docs/modules/state_of_the_union.txt', 'score': 0.6600354698630632}

Just FYI, I also implemented the same idea in this PR #3675 . I think this could be a practical and useful feature.

added in other pr!


Double tap menu button to quick cycle through input sources of HDZ/HDMI/Expansion Module.

Double tap the menu button to cycle the goggle input to the next input source. This may be used in conjunction with a new menu setting to define the quick switch sources to reduce the cycling options if the pilot only uses 2 inputs regularly.  Otherwise cycle through HDZ/HDMI/Expansion Module/AV.
Optionally, cycle through only detected inputs, but unsure if the goggle is able to detect all active/connected inputs.

Perhaps have a menu option to alter the jog wheel function from switching channels to switching input sources.

+vote for this!
Alternative: option in menu to change input with function button instead of changing fan speed.

Lets keep the interactions well defined. Double tap cycles through all import sources.

@bkleiner I think it's better to double-click on the OK button of the wheel to call a pop-up window with a list of all sources and select the desired one with the wheel, then after a pause of 2 seconds automatically or by pressing OK - select this channel.
This is how we get rid of:

the need to scan only connected sources
from accidentally switching the source instead of entering the menu
accidentally pressing twice, which will cause the source to switch, just wait a couple of seconds or press the OK button on the wheel and the selection menu disappears

And:

it's faster to select only what you need than to jump over all sources

Similarly, it would be convenient to adjust the fan speed: we hold the button for a couple of seconds and the menu for changing the fan speed from 1 to 10 appears, since now the most minimal fan mode creates a lot of noise and a couple of points below are missing to make the glasses silent. Plus it will speed up the fan speed reset after we blew the lenses, instead of switching all the speeds in a circle.
What do you think?

@bkleiner I think it's better to double-click on the OK button of the wheel to call a pop-up window with a list of all sources and select the desired one with the wheel, then after a pause of 2 seconds automatically or by pressing OK - select this channel.
This is how we get rid of:

the need to scan only connected sources
from accidentally switching the source instead of entering the menu
accidentally pressing twice, which will cause the source to switch, just wait a couple of seconds or press the OK button on the wheel and the selection menu disappears

And:

it's faster to select only what you need than to jump over all sources

Similarly, it would be convenient to adjust the fan speed: we hold the button for a couple of seconds and the menu for changing the fan speed from 1 to 10 appears, since now the most minimal fan mode creates a lot of noise and a couple of points below are missing to make the glasses silent. Plus it will speed up the fan speed reset after we blew the lenses, instead of switching all the speeds in a circle.
What do you think?

similar to https://github.com/hd-zero/hdzero-goggle/issues/98 and yeah i agree that some flavor "context menus" are probably what we ultimately want, however there is some "plumbing work" that needs doing so we can make that happen.

@bkleiner yes, exactly that
I understand that implementing a popup on top of a video is not as easy as just going to the main menu
I'm already starting to think about learning another programming language, namely C, to help you, as such products are very inspiring

Switching sources is a dangerous thing to do and is best done from the menu.


Inlined SVG extracted with invalid filename

Bug report
What is the current behavior?
When using css-loader with an SVG that is inlined the extracted SVG gets an invalid filename
If the current behavior is a bug, please provide the steps to reproduce.

Use css-loader

({
    test: /\.css$/,
    use: [
        'style-loader',
        'css-loader'
    ]
});

Set assetModuleFilename to something

{
  assetModuleFilename: 'media/[name].[contenthash:8][ext]'
}

Have CSS with inlined SVG

.className {
  background: url(data:image/svg+xml;utf8,<svg width=%279px%27 height=%276px%27 viewBox=%270 0 9 6%27 version=%271.1%27 xmlns=%27http://www.w3.org/2000/svg%27 xmlns:xlink=%27http://www.w3.org/1999/xlink%27><g id=%27Artboard%27 stroke=%27none%27 stroke-width=%271%27 fill=%27none%27 fill-rule=%27evenodd%27 transform=%27translate%28-636.000000, -171.000000%29%27 fill-opacity=%270.368716033%27><g id=%27input%27 transform=%27translate%28172.000000, 37.000000%29%27 fill=%27%230E242F%27 fill-rule=%27nonzero%27><g id=%27Group-9%27 transform=%27translate%28323.000000, 127.000000%29%27><path d=%27M142.280245,7.23952813 C141.987305,6.92353472 141.512432,6.92361662 141.219585,7.23971106 C140.926739,7.5558055 140.926815,8.06821394 141.219755,8.38420735 L145.498801,13 L149.780245,8.38162071 C150.073185,8.0656273 150.073261,7.55321886 149.780415,7.23712442 C149.487568,6.92102998 149.012695,6.92094808 148.719755,7.23694149 L145.498801,10.7113732 L142.280245,7.23952813 Z%27 id=%27arrow%27></path></g></g></g></svg>)
}

Run webpack

The image gets placed in the output with a filename like svg>.abc123 which breaks on a windows machine.
What is the expected behavior?
Webpack produces a file that doesn't break windows with .svg as the extension or omits the inlined SVG entirely
Other relevant information:
webpack version: 5.45.1
Node.js version: 14.16.0
Operating System: Windows

shouldn't the asset stay an data url anyway? Did you change that to an real asset?

I used the filter url function to not include it, but I feel webpack should do that by default ootb. I hand the realized it happened until our window build broke.

@hipstersmoothie I don't understand you, what is mean doesn't break windows

The build worked fine on Mac but when we tried to build our app on windows we got this error (presumably because > isn't a valid character in a filename)

So either producing a filename that works on all platforms or not extracting the inlined SVG at all would be better default behaviors.

So either producing a filename that works on all platforms or not extracting the inlined SVG at all would be better default behaviors.

You can setup it on own side

Yeah I understand that and I've done that, I just think that this isn't an error a user should have to encounter and notice, webpack + it's loaders out of the box shouldn't produce this bug. Or there should at least be a note somewhere in the docs explaining that you must configure it. I'm willing to make a PR for either approach.
The bug happens here when webpack runs basename on the SVG resulting in </svg> being the last part of the path so svg> becomes the filename.

The bug happens here when webpack runs basename on the SVG resulting in  being the last part of the path so svg> becomes the filename.

We should fix it, and yes you can send a PR to docs

bump

@alexander-akait should hash treated as name here? also should webpack try to determine extension?

Yep, I think it is good idea


visionOS Support

Expected behavior
Be able to use this package inside a VisionOS application for the Apple Vision Pro
Actual behavior
Currently appears to fail to compile to the VisionOS simulator
Steps to reproduce

Open the package and try and run to a VisionOS Simulator

If possible, minimal yet complete reproducer code (or URL to code)
NA
SwiftNIO version/commit hash
Latest
System & version information
Running Xcode 15.2 on Sonoma 14.1.2

Yup, good catch: looks like we need to add some #if visionOS().

Oh actually before even that swift-system needs to.

Let's get apple/swift-system#150 fixed first.

I actually forked that one just a bit ago and sprinkled in a lot of || os(visionOS) and it worked just fine. This might be a quick easy win

Looks like https://github.com/apple/swift-system/issues/150 has not been updated for a few years, might have to be something forked and done outside of "official" support

I mean I only filed that ticket two hours ago.


Chrome console dark theme coloring

This is a minor thing, but is there any chance the blue log color could be lightened a bit, it looks very harsh in Chrome's dark theme

Maybe use teal instead

Here's teal in both light and dark

Or maybe "dodgerblue" :)

@mvestergaard, good idea, made green color a bit lighter as well.

Published as 4.2.3


Consider generic host initialization process

We should document how to build IHostedServices that cover the main scenarios:

"Warm-up" processes that grab data and initialize the service logic (by putting code in StartAsync)
Ordering of services

We think a doc is sufficient, but if the doc looks ugly, features may be necessary :).

Duplicate of https://github.com/aspnet/Extensions/issues/1151


Any examples about MFConv?

Dear developers,
Could you provide some examples about using MFConv please?
Best regards,
MagicPF

I'm sorry that we do not have any examples for MFConv. However, it's use is similar to any other operator included in PyG. Do you have any problems with applying MFConv to your specific use-case?

Do you have some examples that create a dataset with labels, which is accessible for the MFConv or other Convs?

A small example for utilizing MFConv on the ZINC dataset:
import torch
from torch_geometric.nn import MFConv, global_add_pool
from torch_geometric.data import DataLoader
from torch_geometric.datasets import ZINC

dataset = ZINC('/tmp/ZINC')
loader = DataLoader(dataset, batch_size=32, shuffle=True)

class GNN(torch.nn.Module):
    def __init__(self, hidden_channels, out_channels, num_layers):
        super().__init__()

        self.emb = torch.nn.Embedding(21, hidden_channels)
        self.convs = torch.nn.ModuleList()
        for _ in range(num_layers):
            self.convs.append(MFConv(hidden_channels, hidden_channels))
        self.lin = torch.nn.Linear(hidden_channels, 1)

    def forward(self, x, edge_index, batch):
        x = self.emb(x.squeeze(-1))
        for conv in self.convs:
            x = conv(x, edge_index).relu()
        x = global_add_pool(x, batch)
        return self.lin(x)

model = GNN(64, 1, num_layers=3)

for data in loader:
    out = model(data.x, data.edge_index, data.batch)
    print(out.shape)

If you show me from which data you want to create a dataset, I can give you more guidance on how to do so.

The format of my dataset is a set of SMILES formula with a 0/1 labels.

Here is an example on how to convert SMILES strings to graph data.


Has anybody reproduced the results on UCF101 and HMDB

Hi,
Could anybody please share the hyperparameters for fintuning UCF101 and HMDB? There is a huge gap in my experiments.
Thanks a lot!
Xudong

Have you got any updates on your question was it resolved?

Have someone get any update about this?
And, @XudongLinthu, would you like to share how big is the gap?
Is it like 10% for top1 accuracy?


Schema export

Hi! I'm working with GraphQL and see benefits from export to .graphqls you've made to track diff between schemas. But it's built-in in IDE and I cannot add a kind of pre-commit hook for it or run in terminal. Are there any ways to run it as separate tool?
Apollo has issue on exporting to .graphql but it doesn't seem to be active or developed.

Hi Mark.
Thanks for using the plugin.
If I'm understanding your use case correctly, you have a running GraphQL endpoint, but the schema is not expressed using Schema Definition Language (SDL).
If that's the case, take a look at https://blog.apollographql.com/three-ways-to-represent-your-graphql-schema-a41f4175100d which describes how to convert between the different schema representations. Based on that you should be able to setup a script for a pre-commit hook.
As an alternative, v2 alpha of the plugin can create a .graphql file which describes your schema using SDL by running an introspection query against your endpoint. If you'd prefer that approach, see https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/releases/tag/2.0.0-alpha-3 but note that doesn't allow for integration with git hooks.
Let me know if you have any questions.
Best regards,
Jim.


Possible issue with Logging actuator

We deployed the latest (from dev branch) Management sample app to PWS. We built, published, and tested this using the provided nuget.config configured Steeltoe library. We also built, published, and tested this using the latest (dev) version of Steeltoe (3 assemblies were newer). In both cases, when run, the app always logs 5 of the 6 (excluding the Trace) test log messages into the logs regardless of how the app's logging level is configured. We observed that the app is receiving the /loggers POST and GET from the App Manager. We did not observe any obviously related errors in the logs.

Hi @Jason01450, sorry about the slow response, we're trying to get an RC out for 2.0 and it also looks like the trigger to kick this over to our Tracker didn't fire. Were you adjusting the log levels via Apps Manager at runtime, or changing the configs and redeploying?

HI Tim, thanks for the reply. We were adjusting the logging levels via Apps Manager. The goal of the exercise was to demo changing the logging level and seeing the change take effect.

Closing this , feel free to reopen if you are still seeing this.
Dave


Add reading time to csv

What
Adding reading time column to the CSV of search results. Formatted in the 0h 0m style.
Why
Allows this data to be exported.

Review Checklist

[x] Changes in scope.
[x] Added/updated unit tests.
[x] Added/updated feature tests.
[x] Added/updated relevant documentation.
[x] Added to Trello card.

Waiting on PR for content performance manager.

 (2) Add 'reading time' to the CSV


spop gives wrong number of arguments

I'm trying to use spop command to get multiple set members at once, similar to
    let chain =  redis.multi();
    chain.spop('myset')
    .spop('myset')
    .spop('myset')
    .spop('myset')
    .spop('myset');
    chain.execAsync();

I think the quantity to pop addition to the command is pretty new (supported since redis > 3.0), can we expect to see support for this in node_redis in the near future?
Thanks!

@baao this is already supported. As soon as you use a redis version that supports that command it'll also work in node_redis.


NPAPI FFlag

so there's a site that requires me to do it otherwise i can NOT play, is there any fflag (or just add it) cus it says it used to exist before chrome 44

The NPAPI in chromium has been removed about a decade ago, your best bet is to install the Palemoon browser and use that for NPAPI plugin support as it is the only modern-ish browser to still support it.
Support for the NPAPI in Supermium would be amazing though.


Save training metadata to model outputs

Hi thanks so much for your work with the LoRA training, its been a blast
I was thinking it would be a good help if the training parameters used for a LoRA model were saved to the resulting .pt file. I might want to remember how I configured a model and right now I have to remember to write down the parameters myself every time. Adding the data automatically would also help if I receive a model from somewhere else and want to know how they trained it
Some examples of things I would find useful in this metadata

SD model name/hash that was trained on
Directory structure/number of images/list of concepts/repeats
Epoch count
Batches per epoch
Regularization image count
Total number of optimization steps
LR scheduler/warmup rate
Training batch size
Learning rates

Given that the output files are PyTorch models (.pt) they seem to just be .zip files, so maybe just putting the training parameters as a .json file inside would suffice. And the .safetensors format has a JSON header also
From the additional_networks extension this data could later be inspected from a new tab or similar
It is important that the data is embedded into the .pt file itself so it is retained if the model is distributed later

I'm testing the PR, saving the metadata to .safetensors works well. But if I save the metadata to .ckpt, I got an error while loading that .ckpt.

Whoops you're right, I accidentally overwrote the .zip when saving it. But when saving the .json as if it were a .zip the safe model loaders I tried reject the file anyway. I think your solution is good for now. Please feel free to revert the change for .ckpts if it blocks anyone


Improving performance of typed memoryview to tuple (or similar)

Describe your issue
Tried the naive approach to convert a typed memoryview to a tuple. However noticed that the C code generated handled the typed memoryview like a generic Python sequence, which left quite a bit of performance on the table.
Then tried the next best thing use a comprehension. It appears this needs to live in a list for cpdef functions. This actually makes a significant improvement with pretty minimal code. However this still creates one Python object (a list) and then copies that over to a new tuple.
So did a third attempt leveraging the C API for tuples through Python. This does the usual things to create an efficient C-loop. Construct an empty tuple. Then set each value in the tuple. The code is reasonable, but there is more to keep in mind like referencing counting and the tuple C API.
Ideally Cython code like the first case tuple(a) would generate something closer to the C code in the last case. Am curious what would be needed to close that gap.
from cpython.tuple cimport PyTuple_New, PyTuple_SetItem, PyTuple_SET_ITEM
from cpython.ref cimport Py_INCREF

cpdef tuple to_tuple0(double[::1] a):
    return tuple(a)

cpdef tuple to_tuple1(double[::1] a):
    return tuple([i for i in a])

cpdef tuple to_tuple2(double[::1] a):
    cdef Py_ssize_t n = len(a)
    cdef tuple t = PyTuple_New(n)
    cdef Py_ssize_t i
    cdef object o
    for i in range(n):
        o = a[i]
        Py_INCREF(o)
        PyTuple_SET_ITEM(t, i, o)
    return t

import numpy as np
a = np.arange(1_000, dtype="double")

In [5]: %timeit to_tuple0(a);
77.9 µs ± 352 ns per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

In [6]: %timeit to_tuple1(a);
10.2 µs ± 304 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

In [7]: %timeit to_tuple2(a);
7.23 µs ± 30.9 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

I think what's happening is that "typed memoryview->Python object" gives you a wrapper class which exposes a Python interface. This wrapper class gets passed to tuple's constructor and treated as a generic iterable.
Our current "conversion to PyObject" handling lacks the ability to make decisions based on what type of PyObject it's ending up as. Which would make optimizing this specific case difficult. Arguably that might be a useful feature generally though.

I find it reasonable to support and optimise both list() and tuple() on memory views. Lists seem more interesting than tuples, though. What's your user case for tuples?

We have a container class that works kind of like memoryview/Py_buffer. Though it handles some other cases that those don't handle (notably __cuda_array_interface__). It also tries to smooth out the differences between CPU and GPU memory as well as Python and C
It lowers properties as much as it can to make them easily usable in C/C++/Cython code while still accessible in Python. It places shape and strides metadata in typed-memoryviews
However there can be cases where users expect tuples like shape or strides, which we construct. Note the C contiguous case stores strides as None for faster checks, meaning the strides property computes them when creating the tuple
Agree the list case can be more interesting since nested-lists are more likely. Had written a different container class for a different purpose (smoothing out Python 2/3 buffer handling differences), which acted basically like memoryview (for Python 3). That included a tolist method with a bit more involved implementation

The right place to replace the generic Python builtin calls with dedicated C code is probably here:
https://github.com/cython/cython/blob/7beedb19c43f3e865056b8181e55897b222a645b/Cython/Compiler/Optimize.py#L2491
https://github.com/cython/cython/blob/7beedb19c43f3e865056b8181e55897b222a645b/Cython/Compiler/Optimize.py#L2512
Look for create_to_py_utility_code() and to_py_function on the memory view's dtype to get the conversion function. The rest can be done with templating in a utility code section in Optimize.c. I think I'd use three different sections for list, set and tuple, just to keep the implementation simple and readable, even though they're going to be quite similar.

Or, use a Cython utility code section, like we do for the C++ STL conversions in CppConvert.pyx.


Implemented: support for using oms package for fetching product details(#2rbwzuj)

Related Issues

Closes #
Short Description and Why It's Useful

Using the package to fetch the specific product details
Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Closing as this is not required as of now. We will pick this once we will move multiple apps to oms product module.


SavingData only allowed when suspending?

ExtendedExecutionSession in a running app scenario is always denied it seems, if SavingData is used as the reason; while the Unspecified ends up Allowed. It is not clear if this behavior is specific to particular test device, or will also have effect for the entire Universal Platform.
If SavingData case is reserved for certain specific scenarios, rather than as an abstract Reason categorizer, that should probably be reflected in the documentation to avoid confusion.

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

ID: 0e2753ab-6324-eec9-5690-0bda0bc7752f
Version Independent ID: 821568c4-ada4-08db-a7b7-0f3d308afbac
Content: ExtendedExecutionReason Enum (Windows.ApplicationModel.ExtendedExecution) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.applicationmodel.extendedexecution.extendedexecutionreason.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: lastnameholiu
Microsoft Alias: alholiu

Thanks for taking the time to let us know about this. Due to the sheer volume of feedback in our repo, we're currently prioritizing new Issues. If you believe your feedback is still actionable, let us know either directly in this thread or by filing a new Issue and we’ll work to incorporate your suggestions. Though this issue will be marked as Closed, this issue is still being tracked internally and you're welcome to leave a comment with more details. Thank you again!


scraper: add logging

scraper: add logging

There is more background for this in a general ticket here: #94

Addressed in PR #141
Accordingly, this can be closed. If any issues with that PR, this can be reopened.


slow speed not working properly on all voices on Mac

On Mac OSX, all voices seem to handle speed up but only Alex seems able to do slow down.
Example with output experienced:
say.speak('Hello!','Alex','0.5'); //speaks slow
say.speak('Hello!','Alex','1.0'); //speaks normal
say.speak('Hello!','Alex','2.0'); //speaks fast
say.speak('Hello!','Samantha','0.5'); //speaks normal
say.speak('Hello!','Samantha','1.0'); //speaks normal
say.speak('Hello!','Samantha','2.0'); //speaks fast
command line seems to work fine, both of the following examples speak slow:
say -v Alex "hello" -r100
say -v Samantha "hello" -r100

console.log(convertSpeed(0.5));
console.log(convertSpeed('0.5'));
console.log(convertSpeed(0.25));
console.log(convertSpeed('0.25'));
console.log(convertSpeed(1.0));
console.log(convertSpeed('1.0'));
all give proper results though, so not the function itself, weird stuff

say.speak('Hello!','Samantha','80');
she speaks normal speed again.
i'm guessing there is a minimum rate threshold, and that anything below that snaps back to normal speed default instead of lowest possible. haven't found any documentation online on the max and min rate for the voices. there are some information that they differ between voices. might be worth investigating further to cap these limits somehow, or just have them documented for the user to know how low can they go. :)


Memory issue when displaying an animated webp

I'm displaying an animated WebP by using this simple code
let webp = YYImage(data: data)
gifView.image = webp

where gifView is a YYAnimatedImageView.
In a tableView/collectionView, the memory keep growing till the app crashes for memory issue. Is there a way to fix this problem?

Seems like caused by this

Seems like caused by this

How did you solve the problem？


BREAKING: NUT-04: payment_hash -> hash

Critical update. We need to fix NUT-04 to not use the bolt11 payment_hash as this enables a third party to steal tokens from a user if they publicly post a Cashu invoice online or leak it in any other way. An attacker could compute the payment_hash and start hitting the mint with POST /mint requests until the invoice is paid. If the attacker is faster than the user, they get the ecash.
What do we need to change?
Wallets:

Very easy: simply rename the URL param from payment_hash to hash in POST /mint. You received the hash in the previous step when you called GET /mint.
This is simply for semantic consistency (as we're not using a payment hash anymore). An option would be to make mints backwards compatible for a transition period and accept both parameters.

Mints:

Medium easy: instead of returning the payment hash in NUT-03: GET /mint, generate a random string to look up the invoice state later in POST /mint. This either has to be stored in a database (so it can be mapped back to the invoice) or it could be encrypted with the private key of the mint (which would make it stateless).
Any comments on these approaches are appreciated, especially from mint devs.
Edit: It seems the easiest way to implement this in a mint would be to encrypt the payment_hash with the mint's private key (or: the hash of the private key string). Then pass that encrypted (random-looking) string we call hash to the user upon GET /mint. When the user then asks for POST /mint, the mint takes hash, decrypts it with the private key and gets payment_hash that can be used to look up the invoice state in the Lightning backend.

Tracking progress (please report):

[ ] Nutshell
[ ] LNbits
[ ] Feni
[ ] Cashu.me
[ ] Nutstash
[ ] Peanut
[ ] cashu-ts
[ ] ngutech21/cashu-rs
[ ] clarkmoody/cashu-rs

Ping: @Egge7 @BilligsterUser @gandlafbtc @clarkmoody @ngutech21 @gohumble

LGTM

Fixed in https://github.com/ngutech21/cashu-rs/commit/9e4020ff77fc99d32f39d659cf77b8c7191ca938

Fixed in https://github.com/thesimplekid/cashu-crab/commit/d138135613475af563191b113c82c77d539f1213

https://github.com/cashubtc/cashu-ts/releases/tag/v0.7.2

@gohumble @ngutech21 @clarkmoody please confirm that the hash you're producing is urlsafe (since we're using it in a URL param)! 🙏

Yes, I'm encoding as hex.

Thank you everyone for a smooth coordinated upgrade like the Solana people.


Not compiling scss into css

Not compiling scss into css
Machine & Versions

Item
Value

VS Code
v1.65.2

Platform
darwin arm64

Node
14.16.0 (89)

Live Sass
5.3.0

Installed Extensions
- vscode.configuration-editing (1.0.0)- vscode.css-language-features (1.0.0)- vscode.debug-auto-launch (1.0.0)- vscode.emmet (1.0.0)- vscode.git (1.0.0)- vscode.git-base (1.0.0)- vscode.github (0.0.1)- vscode.github-authentication (0.0.2)- vscode.ipynb (1.0.0)- vscode.json-language-features (1.0.0)- vscode.merge-conflict (1.0.0)- vscode.microsoft-authentication (0.0.1)- vscode.typescript-language-features (1.0.0)- atlassian.atlascode (2.10.11)- bajdzis.vscode-twig-pack (1.1.0)- bradlc.vscode-tailwindcss (0.7.7)- DmitryDorofeev.empty-indent (0.2.0)- eamodio.gitlens (12.0.5)- ecmel.vscode-html-css (1.11.0)- esbenp.prettier-vscode (9.5.0)- formulahendry.code-runner (0.11.7)- glenn2223.live-sass (5.3.0)- josee9988.minifyall (2.10.0)- mblode.twig-language (0.9.2)- mrmlnc.vscode-scss (0.10.0)- ms-vsliveshare.vsliveshare (1.0.5449)- oderwat.indent-rainbow (8.2.2)- pranaygp.vscode-css-peek (4.2.0)- redhat.vscode-yaml (1.6.0)- ritwickdey.LiveServer (5.7.5)- Zignd.html-css-class-completion (1.20.0)

LOG:
{
"NO LOG": "PLEASE SPECIFY YOUR ISSUE BELOW"
}

=======================

Sorry to hear you're having an issue.
Did the application close (or did you close it) before you ran the command to open this issue? I only ask because there is no error information provided in the copy.
Is this happening for every file?
Can you provide the SASS you were trying to save (or, better yet, a zip of the whole code)?
Can you also set the 'showOutputWindowOn' setting to trace and save the same file again then provide the output here?
Thanks in advance

I'm assuming this is an application error. It may be that there is a SASS error. Have you tried converting to @use instead of @import? Does the icon in the bottom right switch to 'Error` when you save a file?

Closing as info required


v1.12 Backports 2023-09-04

[ ] #27656 (@pchaigno)
[x] #27572 (@bimmlerd)
[ ] #27814 (@haiyuewa)
[ ] #27359 (@brb)
[x] #27706 (@tklauser)

PRs skipped due to conflicts:

#27831 (@tklauser)
#27798 (@ti-mo)

dropped while lb4_extract_tuple() gets backported to 1.12

Once this PR is merged, you can update the PR labels via:
for pr in 27656 27572 27814 27359 27706; do contrib/backporting/set-labels.py $pr done 1.12; done

or with
make add-labels BRANCH=v1.12 ISSUES=27656,27572,27814,27359,27706

bpf: lxc: support Pod->Service->Pod hairpinning with endpoint routes #27798

lb4_extract_tuple() does not exist on v1.12, making the commit broken. I'm currently looking at the 1.12 backport for this PR.

ack, I'll drop the backport for now then :+1:

/test-backport-1.12

/test-backport-1.12

/test-runtime

/test-1.23-4.19

/test-1.17-4.9

/test-1.21-4.9

/test-1.17-4.9


add localeScript capability to set script in locale

depends on https://github.com/appium/appium-adb/pull/372
After merging the PR, we should update the module.
In this PR, I've introduced localeScript capability to set Hans in zh-Hans-CN. The middle one is named script in the Locale term. It only available in Android so far.

@KazuCocoa Might it be that something has happened to Unlock script after the SDK tools version has been bumped for Appium Settings: https://travis-ci.org/appium/appium-android-driver/jobs/450112540 ?

mmm, in my locale, below command worked... let me see.
$ adb shell am start -n io.appium.settings/.Unlock -c android.intent.category.LAUNCHER -a android.intent.action.MAIN -f 0x10200000

Maybe it does not work with API 20 emulator (the one used for this job)?

API 19, arm emulator also worked 🤔


Running a command from the toolbar broken for tidy

#576 fixed the problem for clang compile. However the same behavior still stands for launching tidy. For me using the toolbar icon or the assigned keyboard shortcut launches tidy on some random file even if the active pane is solution explorer with a project selected. The only way to actually launch tidy is to use the context menu in solution explorer.
Also the related bug #614  was closed as fixed, while in 5.2.1 I see the problem as reported. My keyboard shortcut used in the editor launches compile on the solution-explorer active selection instead of the active file in the editor. (make sure at testing you turn off the feature that auto-selects the current file in the explorer, as then then it will seem like working)

Hi,
We'll address this issue in a future release. Thank you for your feedback.
Meanwhile, the new version of Clang Power Tools v5.3 was just released. Please check for updates.
Regards,
~Ionut

Cool. While at it, please test CPT with llvm 9, or if that already happened update the FAQ page to reflect that. And make the Eg. ling point to 9 or 8.0.1 if staying with that.
From: Enache Ionut<EMAIL_ADDRESS>Sent: Thursday, October 24, 2019 3:24 PM
To: Caphyon/clang-power-tools<EMAIL_ADDRESS>Cc: pasa-<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Caphyon/clang-power-tools] Running a command from the toolbar broken for tidy (#693)
Hi,
We'll address this issue in a future release. Thank you for your feedback.
Meanwhile, the new version of Clang Power Tools v5.3 https://marketplace.visualstudio.com/items?itemName=caphyon.ClangPowerTools  was just released. Please check for updates.
Regards,
~Ionut
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Caphyon/clang-power-tools/issues/693?email_source=notifications&email_token=AAM7QIBVOL7W6S7DBA24ALTQQGOVJA5CNFSM4JEP6YKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECFAGFQ#issuecomment-545915670 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM7QICWG2NG5OW62CIEX6TQQGOVJANCNFSM4JEP6YKA .

Hi,
LLVM 9.0 is under testing as we speak.
There are some issues to be addressed both by LLVM (MSFT compat) and Visual Studio teams.
One example/blocker we found:
https://developercommunity.visualstudio.com/content/problem/691073/-com-ptr-t-is-not-accepted-by-clang-90rc.html
Some issues will be addressed in  LLVM 9.0.1, some in VS v16.5

Hello,
I am glad to announce you that the new version of Clang Power Tools fixed this issue. Please check for updates.
Also, LLVM 10.0 is now available for installation in the Clang Power Tools - LLVM settings panel.
Regards,
Ionut


⚠ Bofrost.de has degraded performance

In 6c79348, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1664 ms

Resolved: Bofrost.de performance has improved in f7d8e3d after 23 minutes.


rendering issue with submodules

I have a repo that contained a number of submodules.
All my submodules have been listed in the .gitignore file.
When I open a submodule with atom, it's not recognized as a git package and all its folders are greyed out. I assume it's because the parent .gitignore mentionned it.

I have the same issue

I'm not sure I understand – if the submodules are in the .gitignore file then the intended behavior is that they'll be grayed out in the tree-view.

@mnquintana that's the expected behavior if I open the top-most folder as the "project"
repo
| submodule1 // should be grayed out
| submodule2 // should be grayed out
.gitignore

However it's not the expected behavior if I open one of the submodule as the "project"
submodule1 // should not be grayed out

@mnquintana for example
I have a vagrantfile repo, it is include a project source code as as git submodule.
I just want keep the repo clean, so I add source code folder into .gitignore.
the bug is: currently, all source codes in tree view are gray when I open its directory as root directory in Atom
another bug, Search can not search the submodule file.
Textmate not have those bugs, I think Atom should fix it too


Some technical words

I've discovered that these words were missing from the lexicon while transl(iter)ating Godot engine.
operand	𐑪𐑐𐑼𐑨𐑯𐑛 (values to which an operation is applied to)
operands	𐑪𐑐𐑼𐑨𐑯𐑛𐑟
Bezier	𐑚𐑧𐑟𐑦𐑱 (Bézier curve: a type of mathematical curve)
Bézier	𐑚𐑧𐑟𐑦𐑱
interp	𐑦𐑯𐑑𐑻𐑐 (short for interpolation)

Thanks for these suggestions. I will add them when I can, but may not have a chance for about a week or so.

Added. Sorry for the delay.


Feature: Cassandra DSE configurations added

Added the configurations for DataStax Enterprise Configurations for using Cassandra DB

Merged. Thanks for contributing.


Release Google.Cloud.Bigtable.V2 version 3.1.0

Changes in this release:
New features

Added ResponseParams proto messages

Created release for Google.Cloud.Bigtable.V2-3.1.0


[FEAT] Endpoint for Managing User Preferences

Description
Create an API endpoint to manage user preferences. This includes creating, updating, retrieving, and deleting preferences for a user. Preferences can include settings like theme, notification settings, and other configurable options relevant to the user. The endpoint must be secure and only accessible to authorized users. Proper logging should be added to capture any issues or errors during the API operations.
Acceptance Criteria

Create Preference:

Endpoint should accept a request to create a new preference.
If a preference with the same name already exists, it should return an error.
Endpoint must be secure and only accessible to authorized users.
Log the creation process and any issues that arise.

Update Preference:

Endpoint should accept a request to update an existing preference.
If the preference does not exist, it should return an error.
Endpoint must be secure and only accessible to authorized users.
Log the update process and any issues that arise.

Retrieve Preference:

Endpoint should return the current preference settings for the user.
If no preferences are set, it should return an empty list.
Endpoint must be secure and only accessible to authorized users.
Log the retrieval process and any issues that arise.

Delete Preference:

Endpoint should delete an existing preference.
If the preference does not exist, it should return an error.
Endpoint must be secure and only accessible to authorized users.
Log the deletion process and any issues that arise.

Requirements

Ensure the user has proper authorization to access the preference information.
The user must be authenticated for these endpoints to work.

Endpoints

Create Preference

Method: POST

Endpoint: /api/v1/user/preferences

Request Body:
    {
      "name": "string",
      "value": "string"
    }

Response:

Success: 201 Created    {
      "id": "integer",
      "name": "string",
      "value": "string",
      "message": "Preference created successfully."
    }

Error: 409 Conflict
    {
        "error": "Preference with the same name already exists."
    }

Update Preference

Method: PUT
Endpoint: /api/v1/user/preferences/{preference_id}
Request Body:    {
        "name": "string",
        "value": "string"
    }

Response:

Success: 200 OK    {
        "id": "integer",
        "name": "string",
        "value": "string",
        "message": "Preference updated successfully."
    }

Error: 404 Not Found    {
        "error": "Preference not found."
    }

Retrieve Preferences

Method: GET
Endpoint: /api/v1/user/preferences
Response:

Success: 200 OK    {
        "preferences": [
            {
                "id": "integer",
                "name": "string",
                "value": "string"
            },
        ]
    }

Success with no preferences: 200 OK    {
        "preferences": []
    }

Delete Preference

Method: DELETE
Endpoint: /api/v1/user/preferences/{preference_id}
Response:

Success: 200 OK    {
        "message": "Preference deleted successfully."
    }

Error: 404 Not Found    {
        "error": "Preference not found."
    }

Expected Outcomes

The endpoint should correctly create, update, retrieve, and delete user's preferences.
Appropriate error messages should be returned for invalid operations.
The data should be persisted in the database and correctly reflect the current state of user's preferences.
The endpoint must be secure and only accessible to authorized users.
All operations should be logged, including requests, responses, and any errors.

Testing

Unit Tests:

Test creating a new preference.
Test creating a preference that already exists.
Test updating an existing preference.
Test updating a non-existent preference.
Test retrieving all preferences.
Test retrieving preferences when none exist.
Test deleting an existing preference.
Test deleting a non-existent preference.

Integration Tests:

Test the entire workflow from creating, updating, retrieving, and deleting preferences.
Ensure the responses are correctly formatted and contain the expected data.
Test the security of the endpoints by ensuring unauthorized access is denied.

Security Tests:

Test endpoint access with valid and invalid JWTs.
Ensure that unauthorized requests are correctly handled and access is denied.
Verify that JWT expiration and invalidation are correctly managed.

Logging Tests:

Verify that all actions (create, update, retrieve, delete) are logged.
Ensure that error conditions are properly logged with detailed information.
Test log output for correctness and completeness.

Manual Tests:

Use tools like Postman to manually test the API endpoints.
Verify the responses and the state of the database after each operation.
Confirm that only authorized users can access the endpoints.
Review logs for completeness and correctness after each operation.

Notes

Ensure that the endpoint is secure and only accessible to authorized users using JWT.

duplicate

duplicate
It's not a duplicate. What exists is an endpoint for Organization preferences. This is user preferences.

@CaptainAril Please link both issues and say the difference

@CaptainAril Please link both issues and say the difference

@highb33kay https://github.com/hngprojects/hng_boilerplate_nestjs/issues/233#issue-2416915470 - The issue for organization preferences.
They are quite similar because they border around an account's preferences, so they should have a very similar implementation. However, since the organization and user are two different account types/models, they should have different implementations and endpoints.


Short mode be default setting

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
A button in settings to make short mode the day fault setting for all queries, as well as a "short mode off" query item to turn this off for specific queries.
✔ Solution
It'd be nice for those of us that use short mode for most or all queries. I find that with ADHD, the extra visual noise makes it difficult to easily read queries without short mode. However, there are a few use cases where I wouldn't want it, hence the turn off query command.
❓ Alternatives
Manually putting short code for every query = cumbersome.
📝 Additional Context
No response

Hi, thanks for the suggestion.
This falls under the category of things that will be easy for users to do once this feature is implemented:

https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1619

So we wouldn't provide a very specific feature in the meantime.

Oh, but the ‘short mode off’ or ‘full mode’ instructions would still be needed.
Good point.

Thanks again for the suggestion.
Changing an existing default would be a breaking change, so would need to be very important, to be considered.
However, the following two feature requests would provide an alternative way to achieve the same goal:

#1619
#1806

I'm therefore closing this as won't do. Feel free to subscribe to those other two request for updates, if you wish.


package vendors ANN

cctbx-base 2020.8 vendors ANN (https://github.com/conda-forge/ann-feedstock) in /lib/$PYTHON/site-packages/annlib.

I'll fix this this weekend with #1


WIP: Algebraic Refactor (+ rational root isolation/refinement)

This is a WIP PR. I still need to write some more tests. I was hoping to get more written, but keep getting bogged down in actually fixing bugs the tests find :)
This is a pretty big refactoring of Algebraic. It simplifies the whole structure greatly (no more cake) and also makes optimizations a bit easier (less indirection). It also adds a new rational root constant type to Algebraic (eg. Algebraic.roots(poly) or Algebraic.root(poly, 0)).
This also adds algorithms and a bit of an API for rational polynomial root isolation and refinement (just BigDecimal refinement right now). Both use good algorithms; VAS for root isolation and QIR for refinement.
For the API, if you have a poly: Polynomial[BigDecimal] then you can val roots: Roots[BigDecimal] = poly.roots(MathContext.DECIMAL128), for instance. From there, roots(0), roots.count, etc. The roots method actually takes an implicit RootFinder, which is a bit weird. So, there are implicit conversions from MathContext => RootFinder[BigDecimal], for instance, which is why the previous example works. It also means if we have a type like Double, we can just call poly.roots since RootFinder[Double] wouldn't require any context (eg MathContext), like BigDecimal does.

Thanks so much!
If there is any simple testing you'd like help with, feel free to comment here and I can submit PRs against this branch. Also, at any point where you feel like this is a net improvement over what we have, I'd be happy to merge it (which will probably make collaborating on bug fixes easier).

By the way, some warnings (as errors) under 2.10:
[error] /home/travis/build/non/spire/core/src/main/scala/spire/math/Algebraic.scala:288: reference to mc is ambiguous;
[error] it is both defined in method toBigDecimal and imported subsequently by
[error] import Expr._
[error]     val roundingMode = mc.getRoundingMode
[error]                        ^
[error] /home/travis/build/non/spire/core/src/main/scala/spire/math/Algebraic.scala:336: reference to mc is ambiguous;
[error] it is both defined in method toBigDecimal and imported subsequently by
[error] import Expr._
[error]     val approx = rec(expr, mc.getPrecision + 2)
[error]                            ^
[error] /home/travis/build/non/spire/core/src/main/scala/spire/math/Algebraic.scala:337: reference to mc is ambiguous;
[error] it is both defined in method toBigDecimal and imported subsequently by
[error] import Expr._
[error]     val newScale = approx.scale - approx.precision + mc.getPrecision
[error]                                                      ^
[error] /home/travis/build/non/spire/core/src/main/scala/spire/math/Algebraic.scala:342: reference to mc is ambiguous;
[error] it is both defined in method toBigDecimal and imported subsequently by
[error] import Expr._
[error]       .round(mc) // We perform a final round, since roundExact uses scales.
[error]              ^
[error] four errors found
[error] (core/compile:compileIncremental) Compilation failed
[error] Total time: 110 s, completed Apr 20, 2015 3:58:29 PM

Ah shoot - teach me for not +testing! FWIW, I think it is pretty much a net improvement over what existed already. Likely many areas that should be ~easy to test if you're feeling up for it, so I'll go through the PR a bit and comment on a few places that are probably bug-prone.

:+1:
Once Travis passes I'm going to merge this -- it's a big improvement over the existing thing. Any issues with this PR can just become Spire issues.


Update info on write source; fixes #121

The information on "write source" was very obsolete;
update it with current information.
In particular, write source now has /split.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

@nmegill - this should be a 0-problem addition - it just updates the "write source" documentation from metamath's "help write source".

This is fine, ok to merge.

Actually I changed my mind.  I am going to remove /format because no one uses it, and it might accidentally be used when /rewrap is required.  There is never any reason not to use the full /rewrap.  So take out the /format option.  I will take care of metamath.exe.

Ok, I modified the branch to remove /format.  How's it look now?

OK to merge.


fix(bitswap): use different channels for have, cancel and block requests

Summary of changes

As a follow-up of https://github.com/ChainSafe/forest/pull/3713
In the current bitswap implementation, a block request should have higher priority than a have request. Splitting the channels to allow block requests to be sent early when a lot of have requests are queued. This could mitigate bitswap timeout when it takes long to send all have requests as block requests can now be made early
Manually tested on mainnet. bitswap timeout rate is low and forest is able to sync and follow with normal performance
bitswap_message_count{type="get_block_failure"} 24
bitswap_message_count{type="get_block_success"} 1592

Changes introduced in this pull request:

use different channels for have, cancel and block requests

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

looks good. perhaps some extra docs explaining how it works are in order.

@ruseinov Added some code comments explaining why using separate channels. Not in code doc though as this is an internal implementation detail.  Please re-approve if it looks good.


move docker/distribution-library-image to distribution org

https://github.com/docker/distribution-library-image is the repository that's used  to build registry official image
It's still owned by Docker, but the code that is used to build the image is owned by CNCF and managed under this org.

@thaJeztah would you please take this over?
I believe there should no longer be any blocker that prevents this from happening. CC: @justincormack

I probably don't have permissions to transfer the repository, so yes, @justincormack and maybe @yosifkit or @tianon are probably needed to help moving it.

Oh! This was moving it to distribution, right? (ISTR there was some talk about moving it to docker-library, so if it's distribution then probably @yosifkit and @tianon are not needed
I recall @tianon mentioned that having it in docker-library would allow them to take care of (part of) maintenance, but I'm a but fuzzy on that part.

I recall @tianon mentioned that having it in docker-library would allow them to take care of (part of) maintenance, but I'm a but fuzzy on that part.

Wouldn't that require a lot of coordination between ourselves and @tianon @yosifkit? I'd like ton hear more about how that'd work. Where things stand at the moment is: that repo is owned by Docker where none of the maintainers bar you and @justincormack have write access over so the end users are doomed to come here and complain when there is a release but there is no DOI image available for it becase we're having to chase Docker folks. Not ideal.

Wouldn't that require a lot of coordination between ourselves and @tianon @yosifkit?

Maybe! I pinged them on Slack as well (Tianon is still on leave, but I think back "soon"). I agree that it probably should be moved "somewhere" but hopefully they can fill be in on details (pros/cons and options for each)

Maybe this was around automation; I know that for (for example) the golang image, they have automation running, so whenever a release happens of Go, it automatically updates the images, and it allows them to update the base-image (alpine versions), so perhaps moving it there indeed means "less maintenance" (or "none at all") for the distribution maintainers.

Curious to hear more. I'm pretty sure we could hack up something that could even open a PR in library repo on every release. But as I said, this is a blocker at the moment so I'd like to avoid this dragging for too long, hence IMHO, the ideal  first step forward would be moving the existing repo under this org 🤷♂

Yep, I'm still out, but this is an easy one from as much as I/we can help - we're happy to take the repo in docker-library and automate version bumps, but we do definitely prefer it be upstream-maintained, and that the existing repository continuity is preserved (issues, commit history), so transferring to distribution makes sense IMO (however huge caveat I can't make that call nor do I have GH permissions to initiate such a thing).
When considering automated PRs (once the repo home is settled), you'll want to review https://github.com/docker-library/faq#can-i-use-a-bot-to-make-my-image-update-prs :bow: :heart:

Thanks @tianon!
My train of thought was "where to make the split", and what to consider a release; I think various (most) official images build from source, so was considering if "distribution" maintainers should be dealing with the source, and official repo deal with "build from source if a tag / release is created on GitHub". And the DOI side could handle "we're gonna be updating all images to use alpine X".
But I'm not sure what's most common, and what's preferred from both parties (what level of control each wants over the image).
@milosgajdos is there a timeframe you're targeting to complete this work? (Wondering if a (zoom) call would work once Tianon is back to work)

@milosgajdos is there a timeframe you're targeting to complete this work? (Wondering if a (zoom) call would work once Tianon is back to work)

There is no timeframe for this or rather there is one = as soon as the milestone issues are cleared. But I understand that saying this might just completely deprioritise this issue in the minds of people who can actually get this done.
Either way, we will be pushing the images into https://hub.docker.com/r/distribution/distribution and to GHCR; we would love if the end users had access to the releases via the official images, too, but if it becomes an issue that drags for weeks then we'll just point the users to the relevant repo that owns the official image.

Yup; let's see how fast we can come up with a plan / best location / move, and set that in motion.
I had a brief chat with @justincormack on Slack, and from Docker's perspective, there's no objections against moving the repository, and to hand over maintenance to distribution and/or official images maintainers.

According to the README for the registry DOI, it is the official image for this GitHub repo. If that is true, then it seems everything is already in place.
Note: I was unable to find any docker/distribution image on Docker Hub.

I should have also noted that Docker Hub does not support redirects, so there is no way to "move" a repository from one namespace to another. Moving is a manual process that involves pulling all the images from the source namespace and pushing them to the destination namespace and then, optionally, deleting them from the source and posting a notice in the source README. The optional step is not recommended since it will break people's builds.

According to the README for the registry DOI, it is the official image for this GitHub repo. If that is true, then it seems everything is already in place.

Yes, the situation was a bit weird; it was the official image for "docker/distribution", which of course got donated to the CNCF (now distribution/distribution), but ownership of the official image repository (both on Docker Hub, and on GitHub (https://github.com/docker/distribution-library-image)) remained at Docker.
I think there was some motivation behind that at the time (I recall I asked about it, but I forgot the details). In either case, that's no longer the case, so we should be good to go to set things in motion.
And when we conclude the technicalities (where to move, and who to (help) maintain), I can try finding a GitHub admin/owner for the docker org to help transferring the GitHub repository.

Note: I was unable to find any docker/distribution image on Docker Hub.

There is no such thing. Please see the link I've explicitly mentioned in one of my comments: https://hub.docker.com/r/distribution/distribution

According to the README for the registry DOI, it is the official image for this GitHub repo. If that is true, then it seems everything is already in place.

It isn't. No. Docker donated this repository to CNCF but the base repo used to build the official image remained under docker GH org. It's all discussed earlier in this thread.

Indeed!
To reiterate, https://hub.docker.com//registry is a packaging of the server component of the open source project at https://github.com/distribution/distribution (which was previously https://github.com/docker/distribution and a Docker Inc project, but was donated to the CNCF), so  is the official "upstream" for https://hub.docker.com//registry and as such should ideally be maintaining it (similar to https://hub.docker.com/r/distribution/distribution, which differs from the DOI image mainly in that it also contains "edge" / development builds).
So to summarize, my suggestion here would be to further echo what Milos is suggesting; that is:

transfer https://github.com/docker/distribution-library-image to https://github.com/distribution
(need someone with transfer capability on https://github.com/docker for that)

update https://github.com/docker-library/official-images/blob/master/library/registry and https://github.com/docker-library/docs/tree/master/registry (via PRs) to reflect that transfer in location and maintainership appropriately

@justincormack are you able to transfer the repo? (do you need someone on the distribution side, or do you have all the permissions needed?

@milosgajdos, sorry for the confusion around which repo (GitHub vs. Docker Hub) move was being requested. Please accept my apology.
I'll ping internal folks to try to get a transfer of ownership request initiated for https://github.com/docker/distribution-library-image to the https://github.com/distribution org (@tianon's item 1).
Once that is done, perhaps @milosgajdos you can create the PRs for item 2?

Once that is done, perhaps @milosgajdos you can create the PRs for item 2?

Yes, we're happy to do that indeed.

The GitHub docs on transferring repositories are not entirely clear on this, but it seems when transferring a repo from one org to another, the person doing it needs to have owner-like permissions in both orgs. @justincormack is going to take it from here.

@thaJeztah what is the status of this? Is that still with @justincormack? Can you ping him, please.

Yes, let me give him a nudge again

He's attending KubeCon, and told me he would be looking at this after that.

Any progress with this @thaJeztah

Am I correct in understanding that this is the last remaining task in the milestones for the v3.0.0 Release? if so, perhaps it's time for another nudge?

moved, sorry for delay


release: release 1.1.0

Signed-off-by: slievrly<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
release: release 1.1.0
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

seata-all + @EnableAutoDataSourceProxy(useJdkProxy = true) + mysql + file   commit/rollback valid
seata-all + @EnableAutoDataSourceProxy(useJdkProxy = true) + mysql + nacos   commit/rollback valid
seata-all + datasourceProxy + mysql +file  commit/rollback valid
seata-all + datasourceProxy + mysql +nacos  commit/rollback valid
SCA sample + seata-spring-boot-starter +mysql + propertites  commit/rollback valid

Codecov Report

Merging #2272 into develop will decrease coverage by 0.13%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2272      +/-   ##
=============================================
- Coverage      50.11%   49.97%   -0.14%
- Complexity      2662     2664       +2
=============================================
  Files            518      518
  Lines          17030    17011      -19
  Branches        2061     2022      -39
=============================================
- Hits            8534     8501      -33
+ Misses          7689     7682       -7
- Partials         807      828      +21

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/io/seata/core/protocol/Version.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0%> (-9.53%)
3% <0%> (ø)

...otobuf/convertor/BranchReportRequestConvertor.java
90.9% <0%> (-9.1%)
3% <0%> (ø)

...obuf/convertor/BranchRollbackRequestConvertor.java
92% <0%> (-8%)
3% <0%> (ø)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0%> (-7.41%)
3% <0%> (ø)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0%> (-6.25%)
3% <0%> (ø)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0%> (-6.25%)
3% <0%> (ø)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0%> (-6.25%)
3% <0%> (ø)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0%> (-5.27%)
3% <0%> (ø)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0%> (-4.77%)
3% <0%> (ø)

... and 22 more


remove deprecated comparison kernels

Which issue does this PR close?

Closes #4733 Remove Deprecated Comparison Kernels
Rationale for this change

What changes are included in this PR?
this is the first part of the change, which updates all tests of the old kernel tests

Are there any user-facing changes?
NO

@tustvold like you suggested, this PR updates all tests in place for the convenience of review. take a look when you have time.

I'm okay with removing macros as long as codes are not duplicated everywhere.
I did try to come up with generics to make a corresponding scalar in test_primitive_dyn_scalar didn't manage to do it.

Marking this as a draft to make clear it isn't awaiting review, feel free to unmark when you would like me to take another look


Add "http.url" tag to HTTP client generated spans

Hi.
I would like to add a default "http.url" tag on spans generated by HTTP client instrumentation with the requested URL.
This information is very useful when calling "external" applications.
This is simple and I should issue a pull request soon.
Aurélien

made notes on your pull request. next time, chat with us on gitter first ok? sorry about the effort you spent. https://gitter.im/openzipkin/zipkin


Microsoft.Teams.SchoolorWork version <IP_ADDRESS>

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

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

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

#68845

Close with reason: Microsoft Teams for School or Work exists under Id Microsoft.Teams;


Bubble should hide, if missing data

A bubble with missing data for X, or Y or Size, can not show.  and should not be on the axis, as it does now See small bubbles on Y-axis

When playing over time the availability of data changes, those appearing should fade in, and does disappearing should fade out from and to the invisible status.

done


Please update java version, proguard-base and proguard-core

Hi.
Please, update to java version at least 22. Now java version 24 is already available. I have my project build in LibericaSDK 22, so I cannot use the plugin.
Also, the latest version for proguard base is now 7.6.0, and proguard-core is 9.1.6
Thanks

I see that it is already a PR with no #373 . How can be merged this one?

Maybe you meant Java 23, not 24.
But also note that you can always set the version yourself. What we have here is just the default version.

Try the last example on page https://wvengen.github.io/proguard-maven-plugin/

Ohh... I've see...
In configuration I need to change proguardVersion to use 7.6.0 , and in dependencies I need to add those two dependencies, of proguard-base and proguard-core.
Thank you very much. ❤


Operational Discovery (CON-1306)

How would I perform operational discovery?
I was look at the DiscoveryImplPlatform class which seems to have this functionality. I'm however unsure if there is a better higher level functionality to perform operational discovery. Moreover I get the error
undefined reference to chip::Dnssd::DiscoveryImplPlatform::GetInstance(), and it seems the file is not included when compiling? Other files in the same directory seems to be included so I am a bit confused.

Node-id<PHONE_NUMBER> might be my google nest hub, as when I plug out my other device only node-id 16 disappear. However this confuses me as I specified a fabric id as filter, and I am pretty sure they are not on the same fabric (google nest hub and chip-tool). Also node-id 16 does not correspond to the node-id I assigned to the device, it should have been id 10.

Looks like the Filter doesn't work for minimal mDNS resolver. This might need a fix for upstream repo of connectedhomeip. I am looking into this issue. Thanks for report this issue!

Thanks, can I also ask about the minimal mDNS? as the context for the resolver says:
/**
 * Node discovery context class.
 *
 * This class enables multiple clients of the global DNS-SD resolver to start simultaneous
 * discovery operations.
 *
 * An object of this class is shared between a resolver client and the concrete resolver
 * implementation. The client is responsible for allocating the context and passing it to
 * the resolver when initiating a discovery operation. The resolver, in turn, is supposed to retain
 * the context until the operation is finished. This allows the client to release the ownership of
 * the context at any time without putting the resolver at risk of using a deleted object.
 */

But in the minimal mDNS resolver StartDiscovery() it says:
 // minmdns currently supports only one discovery context at a time so override the previous context
    SetDiscoveryContext(&context);

What exactly does this mean / what are the effects of this. Do I have to be careful when I perform my own discovery, so that I do not override a context set by another discovery?

What exactly does this mean / what are the effects of this. Do I have to be careful when I perform my own discovery, so that I do not override a context set by another discovery?

That means the resolver can only handle one browsing at a time. You need to stop current discovery when you start a new discovery.

Is it safe to just stop any discovery and is there a safe way to see if a discovery is ongoing?

It is safe the call the stop function even if you don't start any discovery.

https://github.com/project-chip/connectedhomeip/pull/35063 Created a PR to fix this issue, could you try with this patch?

project-chip/connectedhomeip#35063 Created a PR to fix this issue, could you try with this patch?

Yes, fixes the issue for me.
I couldn't build when switching to the PR, some errors occurred from some esp32 component delegate, so I wrote your changes in manually to test it. I just wanted to be sure that this might be due to the compliance of the esp32-matter to the version of the upstream repo.

I just wanted to be sure that this might be due to the compliance of the esp32-matter to the version of the upstream repo.

Yes, the esp-matter should be updated if you update the upstream repo.


First draft of the PoC interactive game

Likely certainly has many bugs and is missing important pieces; to be cleaned up once #587 is merged.

closing in favor of #682


Typo in Russian localization

The button is titled "Эскпорт" instead of "Экспорт", but I can't find it in .strings or source code.

This one https://github.com/vector-im/riot-ios/blob/develop/Riot/Assets/ru.lproj/Vector.strings#L288 ? Seems like it is ok..

I guess it's this one https://github.com/matrix-org/matrix-ios-kit/blob/develop/MatrixKit/Assets/MatrixKitAssets.bundle/ru.lproj/MatrixKit.strings#L269

https://translate.riot.im/ is where the translations are written if you want to fix it. Anyone can edit the translations.


System.IndexOutOfRangeException: Index was outside the bounds of the array. (in v3.0.331)

Describe the bug
Cannot load save files on the newer version of KoARR with fatesworn dlc.
To Reproduce
Steps to reproduce the behavior:
Open app, attempt to load save

Downloaded app from mod nexus, also tried latest from github (in v3.0.331)
KoAR.SaveEditor-8-3-0-290-1616027846
Started KoAR.SaveEditor.exe
Opened save file svd_fmt_5_0.sav
Get error message pop up:

System Information
Tried on two different systems with the same error.

OS: Windows 10 LTSB 1607 | Windows 10 LTSC 1809
Game version Steam CS:13779
Version of the editor:  tried in v3.0.290 and v3.0.331  Same error message on both.

Additional context
Renamed the save file to .txt ext to allow upload.
svd_fmt_5_0.sav.txt

I can see now that an updated version is in the works:
https://forums.nexusmods.com/index.php?/topic/9133703-kingdoms-of-amalur-re-reckoning-save-editor/page-15#entry102944128
15 December 2021, 6:08AM
Fatesworn support is coming. The initial release will probably be later this week.
NOTE: you will need .net 6 to run the new version of the application. I was originally planning on having some phased in support, but I lost a lot of interest in doing that as the expac showed up much later than I expected.
The PR that add the support is available here:
https://github.com/mburbea/koar-item-editor/pull/93
It works and all the new items and buffs are documented. If you have VS22 you can build it yourself and give it a whirl.
===============
Will give it a shot once released. Thx


Introduce a function to extract all includes from bind configuration file

We need to support chroot because we store all named configurations in a chroot environment for named (/var/named/chroot/)


Fix exclude-caches directive

It's called --exclude-caches, not --exclude-cache
see https://restic.readthedocs.io/en/latest/040_backup.html#excluding-files

thanks :kissing_heart:


[ZEPPELIN-5665] rework xml factory

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
Todos

[X] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5665

How should this be tested?

Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

LGTM

I've missed it. Thank you for merging it.


refactor(power actions): split up api calls

Codecov Report

Merging #332 (2950737) into master (80db54e) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

:exclamation: Current head 2950737 differs from pull request most recent head 7d61948. Consider uploading reports for the commit 7d61948 to get more accurate results

@@            Coverage Diff             @@
##           master     #332      +/-   ##
==========================================
- Coverage   51.34%   51.23%   -0.12%
==========================================
  Files          34       34
  Lines         890      892       +2
  Branches       92       93       +1
==========================================
  Hits          457      457
- Misses        397      399       +2
  Partials       36       36

Impacted Files
Coverage Δ

src/app/devices/devices.service.ts
15.00% <0.00%> (-0.79%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80db54e...7d61948. Read the comment docs.


LESS show page can be better organised

Currently, it is a bit chaotic.
My thoughts on how it can be improved:

It should show all the generic stuff first, on top (e.g. strategies, stakeholders, the topology).

Below the topology it should read something like: "Click on a node above to see the load and technologies".

Once you select a node you should see a header title "Load and technologies for connection HH1", the load chart (already implemented now) and the technologies. No need to 'open and close' the latter I think.

cc @antw and @ChaelKruip

:+1:

@ChaelKruip Is this issue still relevant?

Once you select a node you should see a header title "Load and technologies for connection HH1", the load chart (already implemented now) and the technologies. No need to 'open and close' the latter I think.

This is maybe something that's still nice to do though.

Maybe something subtle like the header in the screenshot above.

Maybe something subtle like the header in the screenshot above.

If this can be done without too much work I would like that yes.

If this can be done without too much work I would like that yes.

Yes. This can be done without too much work.

Fixed with: 1274e5b


failOnError: false with streams causes Input file is missing error

What is the output of running npx envinfo --binaries --languages --system --utilities?
System:
    OS: Linux 4.9 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (6) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
    Memory: 231.25 MB / 1.95 GB
    Container: Yes
    Shell: 4.4.12 - /bin/bash
  Binaries:
    Node: 11.10.1 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.7.0 - /usr/local/bin/npm
  Utilities:
    Make: 4.1 - /usr/bin/make
    GCC: 6.3.0 - /usr/bin/gcc
    Git: 2.11.0 - /usr/bin/git
  Languages:
    Bash: 4.4.12 - /bin/bash
    Perl: 5.24.1 - /usr/bin/perl
    Python: 2.7.13 - /usr/bin/python

What are the steps to reproduce?
Using  {failOnError : false} constantly gives an Input file is missing error. Remove that option and everything works.
const fileName = __dirname + '/input.jpg';
const saver = sharp({ failOnError: false }).toFile(__dirname + '/output.jpg', function(err) {
  console.log('err', err);
  });
fs.createReadStream(fileName).pipe(saver);

What is the expected behaviour?
See output.jpg created.
Are you able to provide a sample image that helps explain the problem?
Any image seems to work.

I think this is related to #1579 - certain input options have previously (and appear to continue to) prevent sharp accepting Stream-based input.
As a workaround, please can you try sharp(null, { failOnError: false }) to force sharp to expect Stream-based input.

Perfect! In order to stop TypeScript from yelling at you, you've got to use sharp(undefined, { failOnError: false }), but the end result is the same.

Test and fix in commit 6289968 to be included in v0.23.0. Thanks for reporting this.

sharp v0.23.0 is now available.

Im still experiencing this error in latest version of Sharp with a Samsung S22, and even when using failOn: 'none'
[Error: VipsJpeg: Invalid SOS parameters for sequential JPEG
]


Fix series buffer reset

Add MixedModeReadWrite integration test
Fix series buffer reset options

/cc @robskillington @xichen2020

Coverage remained the same at 78.12% when pulling bde1413a0e1c392686597223b616f3dba29dea06 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage remained the same at 78.12% when pulling bde1413a0e1c392686597223b616f3dba29dea06 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.02%) to 78.144% when pulling 9d50398a4e30c1a84ad958268ad170fdfb483999 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.02%) to 78.144% when pulling 9d50398a4e30c1a84ad958268ad170fdfb483999 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage decreased (-0.009%) to 78.111% when pulling 6ff776dde203f82c3c6ca62fe21a9c6aa3feb5a0 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.02%) to 78.144% when pulling 52ef496a923afe1f72eb3bddd6d6483f27406ae0 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.02%) to 78.144% when pulling 52ef496a923afe1f72eb3bddd6d6483f27406ae0 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.05%) to 78.173% when pulling 7a006375c6ef856580378bf254d80a15ff3129d0 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.

Coverage increased (+0.05%) to 78.173% when pulling 7a006375c6ef856580378bf254d80a15ff3129d0 on prateek/fix-series-buffer-reset into 045b8a9a70de6477ee400ea4420330d4e3665ec2 on prateek/ns-isolation.


Implement Capabilities.screenResolutionX/Y

Using this PR:
https://github.com/openfl/lime/pull/530

Sorry about the stray text commits. Those should just magically vanish from relevance once you pull the fix_text branch, I think.

Got it! :)
https://github.com/openfl/openfl/commit/c5d2ffcea2b3667dc17197a56edbce821fbcce51


Add demo Scrypt package

A wrapper package around a JS and a Wasm implementation.
JS: https://github.com/ricmoo/scrypt-js
Wasm: https://github.com/MyEtherWallet/scrypt-wasm/pull/2
This is purely demonstrational code with no other purpose than personal entertainment right now.

Performance JS vs. Wasm implementation
Node.js 12
About 25 % decrease in runtime:
  1 scrypt (js)
    ✓ works for keplr params (16 secs)
    ✓ conforms to test vectors from RFC 7914 (14 secs)

  2 scrypt (wasm)
    ✓ works for keplr params (12 secs)
    ✓ conforms to test vectors from RFC 7914 (10 secs)

Browsers
For browser, this brings a nice speed improvement of 1.5x – 4x.
Firefox
scrypt (js)
    works for keplr params: 35.845s, 40.525s
    conforms to test vectors from RFC 7914: 29.412s, 31.256s

scrypt (wasm)
    works for keplr params: 10.599s, 10.502s
    conforms to test vectors from RFC 7914: 9.656s, 10.251s

Chrome
scrypt (js)
    works for keplr params: 21.866s, 18.245s
    conforms to test vectors from RFC 7914: 15.808s, 16.118s

scrypt (wasm)
    works for keplr params: 10.62s, 10.583s
    conforms to test vectors from RFC 7914: 11.405s, 12.459s

Not a priority


Update Circle Schema

What?
Let's update the circle schema to support new operations.
Details
Currently, it is not able to see Gelu operation in CircleEditor and in CircleViewer.

Schema updated.
Now it is able to see Gelu operation. =)

Close this issue!


Exception: "Unexpected end of JSON input"

Hello,
This project look's really cool, unfortunately I can't get it working :(
Whenever I submit a valid query, it throw an exception
"Unexpected end of JSON input"

It seems that the problem comme from
JSON.parse
https://github.com/calebmer/postgraphql/blob/master/src/graphql/utils/idSerde.ts#L44
Module version: 2.1.0 from npm
Node version: 6.9.1 (also tested with 6.7.0)
PostgreSQL version 9.5.4
Thanks !

Hi there, could you post the complete stack trace and the query you were trying to run.

Sure :)
http POST 0:5000/graphql query="{ user(__id: 0) { id } }"
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Origin, X-Requested-With, Accept, Authorization, Content-Type, Content-Length
Access-Control-Allow-Origin: *
Access-Control-Request-Method: POST
Connection: keep-alive
Content-Length: 1494
Content-Type: application/json; charset=utf-8
Date: Fri, 21 Oct 2016 11:36:44 GMT

{
    "data": {
        "user": null
    },
    "errors": [
        {
            "locations": [
                {
                    "column": 3,
                    "line": 1
                }
            ],
            "message": "Unexpected end of JSON input",
            "stack": "SyntaxError: Unexpected end of JSON input\n    at Object.parse (native)\n    at Object.deserialize (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/utils/idSerde.js:38:52)\n    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:113:48\n    at next (native)\n    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:7:65\n    at __awaiter (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:3:12)\n    at resolve (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:112:20)\n    at resolveOrError (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:454:12)\n    at resolveField (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:445:16)\n    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:252:18"
        }
    ]
}

Pretiffied stack trace
SyntaxError: Unexpected end of JSON input
    at Object.parse (native)
    at Object.deserialize (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/utils/idSerde.js:38:52)
    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:113:48
    at next (native)
    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:7:65
    at __awaiter (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:3:12)
    at resolve (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/build/graphql/schema/collection/createCollectionQueryFieldEntries.js:112:20)
    at resolveOrError (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:454:12)
    at resolveField (/.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:445:16)
    at /.nvm/versions/node/v6.9.1/lib/node_modules/postgraphql/node_modules/graphql/execution/execute.js:252:18"

Ah, so this query:
{
  user(__id: 0) {
    id
  }
}

Expects a serialized global Relay id and not an integer :blush:
My guess is that you want to use something like:
{
  userById(id: 2) {
    __id
    id
  }
}

The __id selected in the query above would be what you use with user(__id). This could use a better error message though, thanks for reporting :+1:

Oh, thanks !
I'm really sorry, I should definitely have read the full docs first :(

@vanwalj glad to hear that solved it!