QA by provider

This feature makes all existing QA tasks specific to a provider.  With this implementation, you cannot perform QA tasks on multiple provider data, nor can you perform QA tasks on the entirety of the saved/enhanced records.  You must choose one and only one provider.
The provider is stored as a session variable.  It is set when a user clicks on a provider link from the admin#index page.  The value for session[:provider] is currently the provider name, but could be changed to the provider id, or the institution id stored in the application's relational database.
The main methods for restricting QA tasks to one provider are in the module Krikri::QaProviderFilter.  This module can be mixed into controllers or libraries.
I also took the opportunity to refactor some of the business for querying the solr index into a new class, Krikri::IndexQuerier.  This makes things simpler and more consistent across Krikri::ProviderList, Krikri::RandomRecordGenerator, and Krikri::ValidationReportList.
There are two new controllers: admin#index will be a dashboard for administrator tasks.  dashboards#index will be a dashboard for hub tasks.

I made a couple of changes to the views based on Gretchen's feedback.

Without reading anything beyond the main pull request comment up top, the first observation I have is that we're apparently using a session variable for the provider.  This may be fine, for now, but I'm usually wary of using session cookies because we can't really make a RESTful API for the QA app if we're relying on them.  (For a given resource, that returns something like a list of items for the provider, the provider ID is not conveyed in the URI of the request.)  This makes it more roundabout to write frontend Javascript to do things that are convenient for the users and reduce latency in updating parts of the u.i.
I don't necessarily know where I'm going with this, or how big an impact it has, and I'll have to read the code, but I just wanted to bring session variables up as something that can mean less-clean code if you want to do certain things with the u.i.

I think I'm with @markbreedlove that Provider ID would be better as a part of the request path or parameters.

I have just a few more observations at a high level.
The controllers named AdminController and DashboardsController break with the usual paradigm and don't represent the objects they seem to describe -- admins, dashboards.  There is a convention to have a PagesController for pages like the admin or dashboard page -- at least there was with CakePHP, so I assume it's the same with Rails.   This is useful for things that are landing pages, index pages, etc, that just serve as menus or as mostly static pages -- "mostly" because you can still have dynamic elements.  You can have the PagesController call various views depending on the path parameters it's given. The AdminController as it exists is basically a list of providers, so it should probably be ProvidersController.
Also, with the MVC paradigm:  there are various classes now in the lib directory that are doing what models do, e.g. returning lists of things, given some parameters.  Do you think validation reports could be represented with a model?  When ValidationReportList makes a query on the search index to get a list of report links, it's doing a database query the same as an ActiveModel model for a relational database, except the database happens to be Solr under the hood.
I'm sorry if some of this is out of context, because I don't recall commenting on the original pull request that introduced the validation reports.
Also, I know there's a need to get this merged soon, so I don't see anything that should necessarily hold that up, but I'm just pointing out things that we may want to revisit.

Re: using a session variable for providers.  My rationale for doing this was mainly so that an admin could access parts of the website as if she were logged in as a provider.  This includes not only accessing that provider's dashboard and completing solr queries by that provider, but also things like seeing the provider's name in the navigation bar.  To me, it fits the paradigm of a session state.  Also, since any non-admin logged in user is going to be associated with a provider institution, the identity of the provider is going to be somehow saved in a session variable anyway, no?  I am not opposed to changing the code so that the provider ID is in the URI rather than a session variable, since I understand that it's more RESTful that way, but I thought it worth a quick conversation

This makes sense, @AudreyAltman.  I think maybe there's a middle ground.  The guideline I would try to follow is that things like the navigation bar and permissions depend on session state, while access to "resources" (web pages, reports, provider-specific searches) is URI driven.
Does that make sense?

The main complaint versus session cookies, or any cookies, from the REST point of view is that they prevent the transactions from being stateless.  Cookies have been described as breaking the client's back button.
I know some partners might only look at one provider page, but others, like administrators, might want to jump around between different provider pages.  Also, sharing information about a given resource between frontend and backend code is more cumbersome if the frontend code can't analyze the URI to get everything it needs.
Ideally we would not be drawing the whole HTML page every time something on the page needs to be updated; though I know it's easy to do that with any MVC framework like Rails.  We should have endpoints that enable us to redraw small sections of the page dynamically with frontend code. (Later, not right away because I acknowledge things need to just get done :-) )
I think that, ideally, there would be one authentication endpoint that could accept a session cookie, but that returns an access token, which then gets put into the URL for every request. (That may be doable with what's there now with Devise.)   Anything like the provider could go into the URL.  Then when you go through your browser history tomorrow and try to go back to provider page x, it either just works or, at worst, you get redirected to a login page, which is then capable of redirecting you back to the page you wanted by virtue of the fact that the application state is conveyed entirely in the URL.  If a crucial session cookie were expired, that had the provider (or a browser cookie, where that state were stored in the client) it would be less smooth -- someone would have to presumably log in and then navigate around, and the bookmark or history item would not have been useful.

Closing this, since #134 is now. :rocket:


More specificity on errors please...

[11/27/2020] [4:21:38 AM] [OBS] › ✖  error     Can't connect or lost connnection
[11/27/2020] [4:21:38 AM] [OBS] › ℹ  info      Trying to reconnect in 5 seconds
"can't connect or lost connection" to what?  How do I debut this if I don't know what connection failed.


feat(axe-core-4.1.1): update axe-core, report, and ai-scan packages

Description of changes

Updated axe-core to 4.1.1
Updated accessibility-insights-report to 4.0.0
Updated accessibility-insights-scan to 0.6.0

Pull request checklist

[x] Addresses an existing issue: WI # 1797798
[n/a] Added relevant unit test for your changes. (yarn test)
[n/a] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[x] Ran precheckin (yarn precheckin)

Codecov Report

Merging #390 (2f70703) into master (0ce0ddc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #390   +/-   ##
=======================================
  Coverage   95.84%   95.84%
=======================================
  Files          20       20
  Lines         409      409
  Branches       23       23
=======================================
  Hits          392      392
  Misses         17       17

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 0ce0ddc...2f70703. Read the comment docs.

Codecov Report

Merging #390 (2f70703) into master (0ce0ddc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #390   +/-   ##
=======================================
  Coverage   95.84%   95.84%
=======================================
  Files          20       20
  Lines         409      409
  Branches       23       23
=======================================
  Hits          392      392
  Misses         17       17

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 0ce0ddc...2f70703. Read the comment docs.


Will gene 4.3.6

Emergency fixes for 4.3.6

alt/ref pedigree clipping on triple-digit counts
NCBI broken link
PubMed link
up/downstream clipping and limit region buffer BP to 99,999
gnomAd title and pop/freq replaced with full words
Removed text and glyph from pedigree inheritance title for any n/a inheritance

quarantest build successful. Demo link at
http://2119458e.quarantest.iobio.io


project: webpage with meta tags

Several websites like Twitter and Discord use meta tags to provide useful insights of the website like title, description and name. This embed for example:

please assign me the issue if you want me to add an example project about it here.

ya ya it will increase SEO of website go ahead assigned @externref


Repurpose repository to be conventional commits repository

Contents
New features

[x] Add semantic version checker and realease note compiler

Operations

[x] Add continuous deployment CI workflows
[x] Add check-semantic-version entrypoint
[x] Add compile-release-notes entrypoint
[x] Use version 0.0.2 of hook when developing

Refactoring

[x] Rename module
[x] Rename repository to conventional-commits

Other

[x] Add hook installation instructions to README
[x] Add code coverage and style badges to README

Uncategorised!

[x] Merge 86d3133ac934fab82a693276de60807711f3e6fb into f95388e110024176fcd644c4a41c66d87f1539b1

Codecov Report

Merging #3 (86d3133) into main (f95388e) will decrease coverage by 54.73%.
The diff coverage is 0.95%.

@@             Coverage Diff              @@
##              main       #3       +/-   ##
============================================
- Coverage   100.00%   45.26%   -54.74%
============================================
  Files            2        4        +2
  Lines           86      190      +104
============================================
  Hits            86       86
- Misses           0      104      +104

Impacted Files
Coverage Δ

conventional_commits/check_semantic_version.py
0.00% <0.00%> (ø)

conventional_commits/commit_message_checker.py
100.00% <ø> (ø)

conventional_commits/compile_release_notes.py
0.00% <0.00%> (ø)

conventional_commits/cli.py
100.00% <100.00%> (ø)

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 f95388e...86d3133. Read the comment docs.


ClassProperty initializer implemented.

Implements parsing of class property with value initializer, such as
javascript
class Foo {
prop:string = "bar";
}
AST definition based on babel/acorn, for apparent lack of standard spec.

esprima-fb has been deprecated.

Yea, I fairly certain we won't be making any more substantial changes at this point, so I'm going to close this out. That said, if we change our minds and want to make some more changes, we'll come back to this.
I encourage you to work with upstream esprima and see if you can make progress getting this change accepted there and/or in espree.


Include Byron checks

Related to #7
Using the dev/pallas-applying-public-API pallas branch.
The first step is to classify the checks based on the information they need. Some checks only require transactions, while others require a subset of the UTxO set.

The validations from the byron era are listed below, in a block structure. Blocks start with a statement that describes requirements of the validations within that block. Nested blocks require their requirements and the ones from containing blocks.
Some validations require specific context to validate, those validations (5th to 7th validations) were implemented but not added to the validations list.

- The following validation only requires the tx size and the protocol params
1. validate_byron_size(size, prot_pps)

- The following validations require the transaction
2. validate_byron_ins_not_empty(tx)
3. validate_byron_outs_not_empty(tx)
4. validate_byron_outs_have_lovelace(tx)

    - The following validation requires the tx utxos
    5. validate_byron_ins_in_utxos(tx, utxos)

        - The following validation requires network information
        6. validate_byron_witnesses(mtxp, utxos, prot_magic)

        - The following validation requires the size and the protocol params
        7. validate_byron_fees(tx, size, utxos, prot_pps)


Fix bug where calicoctl artifcat isn't created in Circle

LGTM. But then it would since I told you what to type :-)
There's still an issue where the calicoctl.sh files isn't being created. I will look into that.


removing duplicate function

Description

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

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Post some testing, looks like this could actually be useful since LocalSdkRepoDirectory only gets the root of the repo but SdkRepoRootDirectory checks for the directory which actually has the sdks (SDKs dir and AzureStack dir)


Sitemap

After @samhza changes the library to Arikawa as he's insisted, there needs to actually be a sitemap.xml document. This is the most important part, because without one, Google only indexes the index page.
The sitemap, which will be updated once a day, will need to list all variations of the following:

[x] dfs.ioi-xd.net/
[x] dfs.ioi-xd.net/guildID
[x] dfs.ioi-xd.net/guildID/chanID
[x] dfs.ioi-xd.net/guildID/chanID/postID

Additionally

[x] The xml files need to be (optionally) compressed as gz files.
[ ]  The entries in the files should have appropriate dates set.

#7 may need to be mentioned here. I don't think that the sitemap needs to reflect such a change but it might.

(there's still work to be done i'm just merging it into master so that the person working on this code after i go to bed can merge into his code)


Implement roulettes for the secondary image (point mass)

Note that alpha and beta must be recomputed for each local origin used.  The secondary image has its own local co-ordinate system, but it corresponds to the same source co-ordinate system as the main image.

First step should be to modify update() to take an arbitrary xi' as centre.

update() needs to recalculate xi'/eta'
we need to distinguish between source centre eta and origin eta'

Other functions will follow.  The existing getSecondary and related methods are wrong, as they fail to recalculate eta' and just use eta.

This requires setXi for RoulettePMLens, and this may be tricky because of the rotation.


Resizing HF token embeddings with PipelineModule

With a HF model class, one can resize token embeddings to account for any special tokens, there's no upper limit, i.e.,
in the usual scenario (this isn't necessarily working code, I may have gotten the tokenizer APIs incorrect):
from transformers import GPT2Config, GPT2LMHeadModel, GPT2Tokenizer
config_class = GPT2Config
model_class = GPT2LMHeadModel
tokenizer_class = GPT2Tokenizer

config = config_class.from_pretrained("gpt2-xl")   # let's say we want to use the XL config for now, has its own vocab size
tokenizer = tokenizer_class.from_pretrained("gpt2-xl")  # default XL vocab

tokenizer.add_special_tokens("<speaker1>")
tokenizer.add_special_tokens("<speaker2>")

model = model_class(config)
model.resize_token_embeddings(len(tokenizer))

The last line essentially allocates 2 new indices for the newly added special tokens in the input embeddings matrix, and initializes their embeddings with random weights.
Now in the pipeline regime, one cannot just resize the token embeddings after initialization of the PipelineModule, since the module would have already split the model across pipeline stages. Is it possible to provide a callback/mechanism with PipelineModule that can allow for resizing and fresh initialization of newly added special token embeddings for downstream users?
Also, shouldn't this be a problem with the implementation of pipeline (and more generally 3D) parallelism in the DeepSpeedExamples repo too? A user of a model that's been pre-trained with pipeline parallelism would certainly have some basic downstream needs such as addition of special tokens for fine-tuning.
@ShadenSmith @stas00

I don't know much about DS's version of pipeline - I worked only with the pytorch's native version of it.
I know I had to add gather and re-partition with Zero-3 for that exact situation of resizing embeds - twice in this code:
https://github.com/huggingface/transformers/blob/8d43c71a1ca3ad322cc45008eb66a5611f1e017e/src/transformers/modeling_utils.py#L643
Does pipeline have a similar feature? I just don't know this side of DS

@stas00 have you already migrated HF towards native pipeline parallelism with pytorch 1.8? If so, can you point me to that?
For pipe, I don't think there's an equivalent feature to the one you listed @stas00, although I have a few questions about that:

Does that method you linked work if DeepSpeed ZeRO-3/infinity were enabled outside of the Trainer class? I do not use the Trainer but I use DeepSpeed with HF model classes. Does with deepspeed.zero.GatheredParameters make any assumptions about pre-initialization, such as deepspeed.zero.Init?

Would also like @ShadenSmith and @tjruwase's thoughts here because I think 2 above (i.e., ZeRO perf on HF classes) is incredibly poor, as seen with ZeRO-2. I have a separate GitHub issue ongoing with @tjruwase about this. I feel like pipeline or even 3D parallelism would be better than ZeRO-3/infinity because of the reduced communication volume with pipeline parallelism. Fitting massive models in GPU memory is one thing, being able to train them fast is another thing.

re: Pipeline Parallelism:
Most HF models are too complicated. All Pipe-approached that I tried require:

models converted nn.Sequential
inputs/outputs to be Tensors

So after spending weeks on this I gave up (or rather parked the idea). I managed to make a pipeline using 2 pytorch pipelines because pipelines can't handle conditional modules, which encoder/decoder models are. The performance was terrible, I couldn't get over the 50% gpu util over 2 gpus.
pytorch Pipe API has been becoming more user-friendly wrt (2) and will soon handle any input/outputs.
In order to convert HF models to pipeline the models have to drop complex feature like past key and hidden states aggregates - this was the most difficult part. I made a workaround using closures but it doesn't scale well. If you want to see some really crazy code that experimental PR is full of it.
Bottom line - to make pipelines work the models

they need to be designed to be easily convertable to nn.Sequential
if we want DeepSpeed pipeline they must not use complex input/outputs or bool control variables (though the latter can be worked around).

re: Performance testing
I hope to start doing that in the next few days, now that ZeRO-Inf has been merged. As usual I will make an Issue on HF transformers and start sharing the results.
We plan to do an extensive benchmarking including sagemaker, jax, megatron-lm and deepspeed, of course. I'm not sure if fairscale will be included - last one of us looked it was not complete, but perhaps they have caught up - I was too busy with deepspeed integration and dealing with bf16-pretrained models getting NaNs under fp16/mixed precision/deepspeed to have time to look.
One other approach I hope to include is FlexFlow https://github.com/flexflow/flexflow - I hope we will now be able to convert our models to pytorch.fx trace - which is a prerequisite for flexflow. I highly recommend you check it out - the paper looks very interesting - but I haven't had a chance to see it in action yet and hope this will change soon. @michaelbenayoun has been making an awesome progress proxying the symbolic tracing via https://github.com/huggingface/transformers/pull/11475 which should enable flexflow usage with HF transformers.


Add logging levels

Add configuration to what types of messages get logged
EX:

info
warn
error

closed by #5


DoS Watcher test for standard exit

Overview
As a security-concerned application provider, I would like to ensure the security-critical watcher will work on DOS condition so that I know my funds are secured
first part generates proper exit: using watcher api to check available utxo
Testing
This :pr: brings two new tests in Performance application:

time response for asking for exit data - pretty fast, just ask Watcher for exit data,
watcher catch all non_canonical_ife - modifies txs and starts IFE exits, then waits when Watcher's in_flight_exit_processor processor synchronize and detect these non-canonical exits.

:spiral_notepad: For the above tests we run Ch-ch and Watcher in dev env to not abuse other tests we have. Also we start Watcher app (1st time in tests) it's in fixture: omg_watcher.

Coverage decreased (-27.0%) to 58.433% when pulling 15b41187dbba859d0c0275fcd19c89ae81a6571f on 855-complete_security_critical_watcher_under_high_load into 531370f23845f08bdd598ce2c8193f9a8c4747bf on master.

The way you approached this with Tasks and anonymous functions I  think is not the best use case for Tasks. I would rather see a pool of GenServers that perform a set of operations in a clear and readable way. This will be in no way easy to debug. Also, please limit the fragmentation between tests and implementation modules, if there's no need. Don't write code for "future" use.

From :pr: description: "...watcher will work on DOS condition so..."
can you please extend what kind of DOD is tested here: malicious agent is sending large number of standard exits (part of them are invalid)

Splitting to deliver standard exits part in #998 with a test under a load.


Publish test jars

We should publish test jars so that it is easier for third-party denominator providers to test their code. Specifically, we need test jars published to maven for the model and core modules.

cc @MisterK

You can add apply plugin: 'nebula-test-jar' to any project's build.gradle
that needs to produce a test jar. Alternatively just split out testing
chunks to separate subprojects.
On Tue, Mar 17, 2015 at 8:36 AM, Adrian Cole<EMAIL_ADDRESS>wrote:

We should publish test jars so that it is easier for third-party
denominator providers to test their code. Specifically, we need test jars
published to maven for the model and core modules.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/denominator/issues/343.

heh thanks tons.. I had significantly more lines in progress than that one!

@adriancole Sorry but I cannot find the test jars in Maven Central for v4.5. Are you planning on releasing them over there as well? Or do I have to build them myself?
Thanks in advance.

You shouldn't have to build your own test jars. We need to look into this.

@MisterK sorry. I missed a cherry-pick. pushing 4.5.1
https://travis-ci.org/Netflix/denominator/builds/59734605

@adriancole Thanks! I'm now all set to finish integrating with 4.5.1.


Lower privilege using --cap-add=SYS_ADMIN when starting neurodesktop

--cap-add=SYS_ADMIN might provide sufficient permissions for running internal singularity container versus using the full --privileged mode.
Need to test and see if anything breaks
Ref: https://groups.google.com/a/lbl.gov/g/singularity/c/e9mlDuzKowc/m/Kx-aP_vkEgAJ

Thanks @civier, would you be able to try this in place of --priveleged on neurodesktop and test the behaviour?

closed as dealing with this in #55

Thanks @civier, would you be able to try this in place of --priveleged on neurodesktop and test the behaviour?

Sorry I missed it. Was quite busy lately.
Is it still relevant for #55? I can ask the SNI fellows to test it, now that we all use Neurodesktop.
Best,
Oren

no more input needed right now @civier

Continuing the reduced permission discussion from #55
Hi @civier. We're testing out running neurodesktop with reduced permissions.
Would you (and the group) be able to test out this quickstart script for neurodesktop
sudo docker run \
  --shm-size=1gb -it --cap-add SYS_ADMIN \
  --security-opt apparmor:unconfined --device=/dev/fuse \
  --name neurodesktop \
  -v ~/neurodesktop-storage:/neurodesktop-storage \
  -e HOST_UID="$(id -u)" -e HOST_GID="$(id -g)" \
  -p 8080:8080 -h neurodesktop-20211028 \
  vnmd/neurodesktop:20211028

Let us know if anything doesn't work like it used to

@civier Any feedback using the updated run command?

@DavidjWhite33 @TomEmotion @willw1 @Matte16  @PJLYONS
SNIers, I tag you here, so you know where to report issues with the new arguments to run neurodesktop.
If all seems to work fine with the new arguments, please report as well.
Cheers,
Oren

seems to be working since a while. Closing for now.

Hi Steffan,
yes - thanks!
Sorry, i have not revisited that data since then but will be soon.
Thankyou very much,
Matt.

From: Steffen Bollmann @.>
Sent: Wednesday, 30 March 2022 4:50 PM
To: NeuroDesk/neurodesktop @.>
Cc: Matthew Hughes @.>; Mention @.>
Subject: Re: [NeuroDesk/neurodesktop] Lower privilege using --cap-add=SYS_ADMIN when starting neurodesktop (Issue #59)
seems to be working since a while. Closing for now.
—
Reply to this email directly, view it on GitHubhttps://github.com/NeuroDesk/neurodesktop/issues/59#issuecomment-1082647986, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANJD6T7FNN5ARSNFC4GMIE3VCPTRJANCNFSM5GKQYZYQ.
You are receiving this because you were mentioned.Message ID: @.***>


Change PHP Namespace for AutoML

Can we change the PHP namespace in automl_gapic.yaml to AutoML from Automl?
If so, will this be enough, or do we need to add the php_namespace option to all of the *.proto files as well?

@michaelbausor Any updates?

Closing as no longer relevant - if this is still needed, please reopen.


Improve Replicator Group Manager

The MDReplicatorGroupManager currently has very simple logic for balancing the updates between frames. What could be needed is some more advanced balancing logic and possibly rebalance logic.
Also is it worth it to allow users to set custom group names? It seems like allowing this just makes balancing harder, if we don't have group names any form of balancing we introduce could be much more efficient. I know I was the one who introduced the concept but now after thinking about it I am questioning the value of it.

There might be value in letting users choose to replicate out all the properties of a given node by giving them a common group. It's definitely something I've wanted before when making games.


[Persistence] Adds node subcommand to CLI

Description
Adds the first step of the CLI harness for save and load E2E testing. This PR is the first of a series and will be followed by additional PRs adding the actual sub-command logic and execution.
node keyword was chosen contrary to #566 as per the Discussion in Discord.

Issue
Relates to a series of changes to address #566
Type of change
Please mark the relevant option(s):

[x] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[ ] Other

List of changes

Adds the node sub-command to the app CLI.

Testing

[x] make develop_test; if any code changes were made
[x] make test_e2e on k8s LocalNet; if any code changes were made
[x] e2e-devnet-test passes tests on DevNet; if any code was changed
[ ] Docker Compose LocalNet; if any major functionality was changed or introduced
[ ] k8s LocalNet; if any infrastructure or configuration changes were made

Required Checklist

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
[ ] I have tested my changes using the available tooling
[ ] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

Changes lgtm. Any reason we can't base this against main instead of persistence/savepoints-initial?

Absolutely none 😄  I had just been on savepoints-initial when I made the PR 👍 I dropped the others and updated the base branch. 🌴


Debug out with MaybeUninit.

Now this needs the srai instruction.

This shortens the "print" test from 14744 to 9557 rows.


Set up an interim fork of the Kubernetes code-gen

After the kubernetes/code-generator#163 issue in Kubernetes code-gen has a PR that is likely to be merged, we should set up an interim fork of that repo.
Such fork would be tracking the Kubernetes code-gen until the said PR be available in Kantive.
The fork should be automatically updated with a CI, to apply our modification on top of the K8s code-gen for each of the release branches.
Our interim drift of K8s code-gen may contain just an embedding of K8s scripts, similar to knative/hack#222
Here are some references which may help set up such a fork:

RH runs its forks with the https://github.com/cardil/deviate tool, which simplifies the sync process greatly (see example project configuration https://github.com/openshift-knative/kn-plugin-event/blob/main/.deviate.yaml, and the example Jenkins log)
VMware uses a https://github.com/carvel-dev/vendir tool to sync anything
Kuberentes is also syncing their monorepo https://github.com/kubernetes/kubernetes onto project specific ones. We might use those tools as well.

FYI - this doesn't seem necessary
see: https://github.com/kubernetes-sigs/gateway-api/blob/ee42a6d5d81283d9f41a85627b93e4492b876638/hack/update-codegen.sh#L64

/reopen
/remove-lifecycle stale
/triage accepted


Allow to offload / customize key signing operations when using Boring…

…SSL.
Motivation:
BoringSSL allows to customize the way how key signing is done an even offload it from the IO thread. We should provide a way to plugin an own implementation when BoringSSL is used.
Modifications:

Introduce OpenSslPrivateKeyMethod that can be used by the user to implement custom signing by using ReferenceCountedOpenSslContext.setPrivateKeyMethod(...)
Introduce static methods to OpenSslKeyManagerFactory which allows to create a KeyManagerFactory which supports to do keyless operations by let the use handle everything in OpenSslPrivateKeyMethod.
Add testcase which verifies that everything works as expected

Result:
A user is able to customize the way how keys are signed.

This depends on https://github.com/netty/netty-tcnative/pull/446

I will merge this now as the code is really isolated and so will not affect other things. This will allow me to make progress


apis_entities: refactor get_all_entity_classes

This commit refactors the get_all_entity_classes() method. Instead of loading a
hardcoded module we simply get a list of all models and check wether they are
children of TempEntityClass (or in the future of another class that is the root
of all entities). This way we can also loose the inspect import.
I tested the changes in an test instance. Before merging this PR I would like
to clarify the reason of or remove the ent_class comparison.

We can merge this PR for now. Didn't run it, but from looking at the code I trust that this works.
But just as a heads-up: I already see these following problems will emerge with the upcoming restructuring despite it:

TempEntityClass will be removed from apis core logic and only assumed to exist in legacy ontologies. But for the future we want to move away from it entirely, so better not assume it to "represent an entity".
RootObject will be the major "thing" for everything that exists in an ontology. However RootObject will also be used for Properties and Vocabularies / Concepts. So RootObject can't be assumed to stand for an entity, as a potential replacement.
We will definitely need a simple elegant way to differentiate between "Entity", "Property", "Vocabulary/Concept" since they will all inherit from RootObject. Maybe boolean flags attached to dedicated Abstract Classes for each? But that's a separate issue.

So for now, this PR will work, but it will need surely again little work in the near future.

I merged this now, but the question still stands: does anyone now what that ent_class refers to?

I introduced the ent_class but I don't remember myself. Safe to throw away by now though.

I pulled this to my local instance and now ./manage.py makemigrations fails with django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.
@b1rger can you make migrations?

@b1rger I don't know either, I think I just put it in the Docstring for completeness' sake.

I pulled this to my local instance and now ./manage.py makemigrations fails with django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.
@b1rger can you make migrations?

Ah, yeah, that makes sense - the app registry is only loaded later. Given that the class will be remove anyway, I've created a PR that reverts the commit: https://github.com/acdh-oeaw/apis-core-rdf/pull/58 I'll look into how to solve that when we move to the new class hierarchy

sensible, thank you.

ent_class  might be a leftover from vanilla apis-core? https://github.com/acdh-oeaw/apis-core/blob/main/apis_core/context_processors/custom_context_processors.py#L12

ent_class might be a leftover from vanilla apis-core? https://github.com/acdh-oeaw/apis-core/blob/main/apis_core/context_processors/custom_context_processors.py#L12

might be. Whatever it is, we can probably safely delete it.


[SuperEditor] - Creating new tasks eventually blows up

Repro: Run the example app. Place the caret at the end of a task. Press enter to create a new task. Type something. Repeat many times.
Expected: New tasks are created forever, and characters are entered.
Actual: Eventually, an error occurs and we lose IME input.
======== Exception caught by services library ======================================================
The following _Exception was thrown during method call TextInputClient.updateEditingStateWithDeltas:
Exception: Couldn't map an IME position to a document position. IME position: TextPosition(offset: 3, affinity: TextAffinity.downstream)

When the exception was thrown, this was the stack:
#0      DocumentImeSerializer._imeToDocumentPosition (package:super_editor/src/default_editor/document_ime/document_serialization.dart:252:5)
#1      DocumentImeSerializer.imeToDocumentSelection (package:super_editor/src/default_editor/document_ime/document_serialization.dart:161:13)
#2      TextDeltasDocumentEditor._applyInsertion (package:super_editor/src/default_editor/document_ime/document_delta_editing.dart:102:46)
#3      TextDeltasDocumentEditor.applyDeltas (package:super_editor/src/default_editor/document_ime/document_delta_editing.dart:40:9)
#4      DocumentImeInputClient.updateEditingValueWithDeltas (package:super_editor/src/default_editor/document_ime/document_ime_communication.dart:336:30)
#5      DeltaTextInputClientDecorator.updateEditingValueWithDeltas (package:super_editor/src/default_editor/document_ime/ime_decoration.dart:129:14)
#6      TextInput._handleTextInputInvocation (package:flutter/src/services/text_input.dart:1875:63)
#7      TextInput._loudlyHandleTextInputInvocation (package:flutter/src/services/text_input.dart:1761:20)
#8      MethodChannel._handleAsMethodCall (package:flutter/src/services/platform_channel.dart:555:55)
#9      MethodChannel.setMethodCallHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:548:34)
#10     _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:393:35)
#11     _invoke2 (dart:ui/hooks.dart:183:13)
#12     _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:40:5)
#13     _Channel.push (dart:ui/channel_buffers.dart:130:31)
#14     ChannelBuffers.push (dart:ui/channel_buffers.dart:326:17)
#15     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:664:22)
#16     _dispatchPlatformMessage (dart:ui/hooks.dart:86:31)
call: MethodCall(TextInputClient.updateEditingStateWithDeltas, [1, {deltas: [{selectionBase: 4, oldText: . sf, selectionAffinity: TextAffinity.downstream, deltaEnd: 3, deltaText: a, deltaStart: 3, composingExtent: -1, selectionIsDirectional: false, selectionExtent: 4, composingBase: -1}]}])
====================================================================================================

Update: this problem isn't specific to task items, it happens with regular paragraphs, too.
The problem may or may not be related to speed of text entry. If it's speed related, then this issue might be a duplicate of https://github.com/superlistapp/super_editor/issues/914

After investigation, I believe that this issue is a duplicate of #914 - closing this one in favor of that one.


Week 2 - Write create_hours_dist.sh

Lab 1, Task 3
https://github.com/umm-csci-3412-fall-2022/log-processing-lab-1-dongbo#write-create_hours_distsh

This Issue has been finished and will be closed. : )


Get a real user IP from a request and associating it with a Context

I am not sure if it is need it for MVP scope if it is not fit to the project feel free to close it.
clientIPFromRequest  functions for extracting real user IP address from a request and associating it with a Context in handler.

I like these changes. @jcbwlkr and @nstogner what do you think?

Thanks for submitting the PR! We are always appreciate new requests.
My though process for adding new http functionality like this:

Should we be writing common http related code in our service repo or use a library?

I would lean towards using libraries for non-business related code when possible.

Does the value we are parsing belong in the context or can we just use a function like ParseIP(r *http.Request) string, error

I think we should limit the scope of the context as much as possible, it can quickly become a dumping ground otherwise. A large dependency on context-carried variables becomes hard to reason about.

Should we be logging every request that comes through our API?

Hotpath logging is expensive and noisy, should we be doing this by default?

Should we be logging PII?

https://www.enterprisetimes.co.uk/2016/10/20/ecj-rules-ip-address-is-pii/

Hi, @farrukhny! Thanks for contributing :)
I am going to close this PR primarily because trusting those proxy headers is only appropriate in some circumstances. Specifically only if the service you are making is being deployed behind a proxy that knows to strip those headers from client requests. If the service is not behind a proxy or it is not configured appropriately then clients can spoof their IP by just sending certain headers.
The decision to use/trust those headers can only be made by service operators once they know how it will be deployed.
Thanks again for your contribution!


💡 Cycle schema hydration is too slow

I have an idea!
Currently, spiral/roadrunner app bootstrapping is very slow, it takes a pod at least 1 minute to become ready, part of which is cycle fetching information_schema data and setting up its schema. I wish it were faster.
Upon debug dumping queries, I noticed that the data is not cached in any way, so information_schema is queried over and over again.
If I were to connect to a DB that is far from the app (say, there is a 60-100ms latency), then the app wouldn't be able to boot itself at all in reasonable time frame.

In case I wanted to cache the schema data manually, where would be the best place to do it?

Hi
I prefer to cache the ORM Schema in a PHP file. By using https://github.com/cycle/schema-provider, you can build a pipeline that retrieves the schema from a PHP file, and if it's not available, renders it from attributes and writes it to the cache.


Fix IndexOutOfBoundsException when Metadata Header Value is Empty

Description
Resolves a bug where an IndexOutOfBoundsException would be thrown if the metadata header value was empty ("") and fixes validation of leading spaces in the metadata name as Constants.HeaderConstants.X_MS_META is equivalent to x-ms-meta instead of x-ms-meta-.
Additionally, this replaces the usage of, or the equivalent of as this explanation isn't using the direct code, headerName.toLowerCase(ROOT).startsWith("x-ms-meta-") with "x-ms-meta-".regionMatches(true, 0, headerName, 0, "x-ms-meta-".length()) as regionMatches and the code change supports the following:

NullPointerException won't be thrown if the header name was null (shouldn't happen)
regionMatches supports case-insensitive comparisons based on the boolean parameter
regionMatches doesn't require creating a new String as toLowerCase does

Using regionMatches also improves performance, a benchmark running validation against 10 header name-value pairs should a 2-2.5x performance improvement.

Benchmark
Mode
Score
Units

regionMatches
avgt
107.473 +/- 3.665
ns/op

toLowerCase
avgt
255.500 +/- 1.387
ns/op

All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

Hi, which version will include this fix

Any Storage SDK depending on azure-storage-common 12.18.0 or later


Unsure of required "Page Group Representatives" format and where to find them

Hi,
I'm not quite sure where to find page groupings in search console.
I'm currently looking at GSC -> Core web vitals -> Desktop -> LCP issue report -> Examples table at the bottom with URLs (and you can click on of them to view similar URLs). Am I looking at the correct thing?

Would you be able to clarify what you mean by Page Groupings?
Would you be able to provide an example of the format the spreadsheet is expecting the URLs to be added as? (Commas? new lines? etc?)

I'm sorry, this might be because my speciality isn't Search Console, I feel like I'm missing something obvious here.
Thanks,

+1 please clarify this part (perhaps with a screenshot)
Thanks


Theme is not loaded

I created Nexus One device from Android Studio, but running example not use any theming

AppRestrictionEnforcer

I am closing this issue/PR, as it has been migrated to the new repo linked above in the comments. Thank you!


AWS_SESSION_TOKEN missing on Lambda

Hi,
When debugging the filesystems settings, I see that the token was not added as described in the documentation: https://bref.sh/docs/frameworks/laravel.html#file-storage-on-s3
That's it! The 'AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY' and 'AWS_SESSION_TOKEN' variables are defined automatically on AWS Lambda, you don't have to define them.

The result of Laravel's dd command returns the configuration array as below without TOKEN.
"s3" => array:9 [
       "driver" => "s3"
       "key" => "ASIAZ7N74ORB26CAAAAA"
       "secret" => "EC3K2NFgsij3oUHYo7HDqAd21+iYoQ6BWNRAAAAA"
       "token" => null
       "region" => "us-east-1"
       "bucket" => "my-bucket"
       "url" => null
       "endpoint" => null
       "root" => "/my-path"
]

Any idea what it could be?
Thanks

Sorry, after a few days I managed to identify the error, minutes after opening this issue I identified that the variable I configured in filesystems was incorrect.
I will close this issue.
Thanks


Is it normal to keep PEDDING after submitting? It's been three hours.

Is it normal to keep PEDDING after submitting? It's been three hours.

@ChonghaoSima

Yes

It's been PEDDING for seven hours now. 苦笑😂😂

It's been PEDDING for seven hours now. 😂😂

+1 It's been PEDDING for 12 hours now @ChonghaoSima

+1

We suggest you re-submit the file and see if that is still pending. From our side it can run successfully.

We've resubmitted and it's still PEDDING!

Any solutions, please? It's been over a week without a successful submission. 🌹🌹

@24werewolf
Hi, bro. Did you submit it successfully?

+1, keeps PEDDING for 3 hours

@24werewolf Hi, bro. Did you submit it successfully?

No, This seems like a sad story.

We are waiting for huggingface to restart the test server and allocate more resource. No further progress for now.

@ChonghaoSima Hello, with the competition deadline approaching, may I ask when the server will be fixed?

+1

I saw there were some successful submissions on Aug 29. Please re-submit if there’s any pending issues.
Best
Chonghao Sima

From: 24werewolf @.>
Sent: Monday, September 2, 2024 1:31:02 PM
To: OpenDriveLab/DriveLM @.>
Cc: Sima, Chonghao @.>; Mention @.>
Subject: Re: [OpenDriveLab/DriveLM] Is it normal to keep PEDDING after submitting? It's been three hours. (Issue #114)
---- External Email: Use caution with attachments, links, or sharing data ----
@ChonghaoSimahttps://github.com/ChonghaoSima Hello, with the competition deadline approaching, may I ask when the server will be fixed?
+1
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenDriveLab/DriveLM/issues/114#issuecomment-2323846649, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6RGLXUYRVNYFU5HTY5PZTZUPZZNAVCNFSM6AAAAABNJYOCJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRTHA2DMNRUHE.
You are receiving this because you were mentioned.Message ID: @.***>

I saw there were some successful submissions on Aug 29. Please re-submit if there’s any pending issues. Best Chonghao Sima
…
________________________________ From: 24werewolf @.> Sent: Monday, September 2, 2024 1:31:02 PM To: OpenDriveLab/DriveLM @.> Cc: Sima, Chonghao @.>; Mention @.> Subject: Re: [OpenDriveLab/DriveLM] Is it normal to keep PEDDING after submitting? It's been three hours. (Issue #114)
---- External Email: Use caution with attachments, links, or sharing data ---- @ChonghaoSimahttps://github.com/ChonghaoSima Hello, with the competition deadline approaching, may I ask when the server will be fixed? +1 — Reply to this email directly, view it on GitHub<#114 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6RGLXUYRVNYFU5HTY5PZTZUPZZNAVCNFSM6AAAAABNJYOCJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRTHA2DMNRUHE. You are receiving this because you were mentioned.Message ID: @.***>
That was our group, however, we never succeeded again！

Still can't evaluate it.

still keep pending for 8.30 and 9.02 submission

@ChonghaoSima Hello, I'm still unable to submit. Is the issue still being fixed?

👼👼

hf team is allocating more compute resource for our test server and we are waiting for their result.

Could you download our submission.json, test it on your local machine and then give feedback on the results?


Add basic simple support to ubuntu

Hi  and thanks! Could you rebase with master? I fixed testing in #4

I played a bit with git so managed to get the commits from your branch into: https://github.com/CSCfi/ansible-role-sssd/compare/ubuntu_support2
This shows an error in this role you probably stumbled over: https://travis-ci.org/CSCfi/ansible-role-sssd/jobs/454929291#L928

TASK [ansible-role-sssd : template sssd.conf] **********************************
fatal: [test.lxc]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ldap_access_filter' is undefined"}

This would have been an issue for existing Gentoo/Arch users too.
I've made a new PR which still includes your commit that also fixes this: #5
I'll close this PR. Thanks for the contribution!


Why can't I see recent failures / retries?

The grey pills at the top of the screen seem to be clickable but when I click I can't see what's failed, or clear them. Googling it seems like there was an issue in the past w/ a non admin user seeing them, but I'm running as admin and can't see them.
Regardless, how can I even clear the failed jobs? I don't see where they're stored to clear them out in any easy way, or where in MySQL they're even stored.
Thanks

Hey,
do you see the "Job Management" link in the "Account" dropdown? If that is not the case your user is not an admin. The only was to grant a non-admin user admin rights is via the database or rails console:
# rails c

user = User.find_by_username("username")
user.admin = true
user.save!

Ah perfect. I found the database flag and set it properly now and it works great. Should I update the wiki to include that in the setup instructions? Seems like it's a worthwhile thing.

Great! Which wiki page do you refer to? I think all installation guides should include rake db:seed which automatically creates the first user as an admin.

Weird - I followed the directions and didn't get my user created as admin. I suppose it's possible I missed that one command but everything else works flawlessly. Odd.

Which directions did you follow? It also possible that one of the guides does not include the database seeding instruction.

Honestly don't recall now - it was like 3-4 months ago. I agree the directions now include that rake command. Perhaps I just missed it before.

I see, we probably will never know :) Can we close this issue?


404 This is not the web page you are looking for.

Hello,
The "Project repository: Limpet project repository" link, which is at the bottom of the page https://docs.microsoft.com/en-us/windows/iot-core/manage-your-device/azureiotdm?source=docs, does not it's working.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://docs.microsoft.com/en-us/windows/iot-core/manage-your-device/azureiotdm?source=docs'
Click on 'Project repository: Limpet project repository.'
See error: 404 This is not the web page you are looking for.

@luizpires Please move this issue to https://github.com/MicrosoftDocs/windows-iotcore-docs/issues


Add an additional Data Node

Hi Team,
After creating an Elastic search cluster with ARM template provided. Is it possible to add another VM as a data node.
We have been trying this out and it always crashes the entire elastic search cluster.
Is there any additional template for adding extra nodes to the existing cluster?

Using the portal UI, it is not possible to add another data node to an existing Elasticsearch cluster. You used to be able to deploy to an existing resource group from within the portal UI but this feature was removed by Microsoft, so the portal UI only allows deployments into a new resource group.
The deployment template itself however does allow you to deploy into an existing resource group, so using the Azure CLI command line tools, it is possible to scale up (or down) an existing Elasticsearch cluster. This scaling mechanism however is not intended to be a foolhardy solution but can be an easy way to add additional nodes to an existing cluster, and tends to work best when you have dedicated master nodes and simply wish to add additional data nodes. For a cluster in production, I would recommend developing automation with something like puppet to suit your organisational requirements.
Some important points to highlight for how scaling with the template works:
The ARM template deploys in incremental mode meaning that it

leaves unchanged resources that exist in the resource group but are not specified in the template
adds resources that are specified in the template but do not exist in the resource group
does not re-provision resources that exist in the resource group in the same condition defined in the template
re-provisions existing resources that have updated settings in the template

so when you use the deployment template to add an additional data node, be sure to specify all of the same settings as you did when you originally deployed the template, changing only the number of data nodes.
If you are not using dedicated master nodes i.e. you have master eligible data nodes only, the template should update the elasticsearch yaml configuration file on each existing and new data node to set discovery.zen.minimum_master_nodes to a quorum of the number of master eligible nodes. I would recommend checking that this is the case after deployment has finished by running
sudo grep discovery.zen.minimum_master_nodes /etc/elasticsearch/elasticsearch.yml

The number assigned to discovery.zen.minimum_master_nodes should be the same across all nodes and be equal to (number of master eligible nodes / 2) + 1 so for 3 master eligible nodes, discovery.zen.minimum_master_nodes should be 2.
Similarly, discovery.zen.ping.unicast.hosts should also be updated on each node and be seeded with the host names of either the master nodes if using dedicated master nodes, or the host names of all master eligible nodes.


Revert to rancher/rancher:v2.9-head image

Let's see if the CI works with this

The PR has to be run in the rancher org for drone to work, duh! Closing..


console logger: Fix undefined variable or method block

Fixes #805 .
replace yield if block which is incorrect at least nowadays by yield if block_given?.
REDMINE_INSTANCE=default bundle exec rake redmine_git_hosting:install_hook_files

 * Installing/updating Gitolite hooks:
rake aborted!
NameError: undefined local variable or method `block' for RedmineGitHosting::ConsoleLogger:Module
/usr/share/redmine/plugins/redmine_git_hosting/lib/redmine_git_hosting/console_logger.rb:9:in `title'
/usr/share/redmine/plugins/redmine_git_hosting/lib/tasks/redmine_git_hosting.rake:71:in `block (2 levels) in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
Tasks: TOP => redmine_git_hosting:install_hook_files
(See full trace by running task with --trace)

Thank you for your work so far. It has been superseded by #815


Fix #1703, update docs for CFE_FS_BackgroundFileDumpRequest

Describe the contribution
Update notes to better clarify that the meta object must persist for the duration of the dump operation, which occurs in another task, so it must not be on the stack.
Fixes #1703
Testing performed
Build and run all tests
Expected behavior changes
None - documentation only
System(s) tested on
Ubuntu
Additional context
Noted in PR #1650 which allocated meta object on stack during test (producing weird/unpredictable errors)
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

CCB:2021-08-04 APPROVED


Phantom teardrop appears on screen while selecting text inside of a TextInput

Is this a bug report?
YES
I NEED TO KNOW IF THIS IS A BUG ON RN SIDE OR ANDROID (I suspect RN...)
CONSUMERS have experienced this phenomenon VERY recently, and I have not found any developer-side info on this.
Links:

https://us.community.samsung.com/t5/Other-Mobile-Devices/Blue-water-drop-like-icon-Just-hangs-there-on-every-screen/td-p/76639
https://forums.androidcentral.com/samsung-galaxy-s7-edge/791122-there-blue-tear-drop-my-s7-screen-wont-go-away.html

Have you read the Contributing Guidelines?
NO, and why does it matter? I am not contributing right now.
Environment
Environment:
OS: Windows 10
Node: 6.11.2
Yarn: 1.2.1
npm: 3.10.10
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: 0.49.5 => 0.49.5
Steps to Reproduce

IS NOT Reproducible on an emulator
IS Reproducible on Galaxy Tab and Galaxy View tablets when installed from APK

(Write your steps here:)

Tap on the TextInput
Type in text
Tap ONE TIME on text you just typed
Tap ONCE MORE in a different spot
Now you will (should) see two teardrops, one being at the last spot you tapped, and another at the original spot.
Tap ONCE MORE in a different spot. Now you will see two teardrops again...one for the latest spot you tapped and another for the ORIGINAL spot.
Navigation to another screen does NOT A THING.
Restart of the app is the only way to remove the teardrop.

Expected Behavior
Every time you select text in side a text input, a blue (or green) teardrop appears below the selector.
Upon clicking at a different spot, this teardrop should be moved to the location of the new cursor.
However, it seems that the teardrop remains in place (at a seemingly random spot) and does not go away until the app is restarted, even when switching screens via react-navigation library (with navigation.navigate('TargetScreenKey')).
Additionally, the phantom teardrop remains whether Keyboard.dismiss() is employed or not.
Actual Behavior
There should be ONE teardrop connected to a text cursor for any ONE TextInput at any ONE point in time. There are, however, multiples that can appear. See description above.
Reproducible Demo
Stick this anywhere inside of a RN app (pick your own props & callbacks):
<TextInput
multiline={true}
value={specialInstructionsTextTemp}
numberOfLines={4}
underlineColorAndroid="rgba(0,0,0,0)"
style={styles.specialInstructions.textInput}
onChangeText={(text => this.onSpecialInstructionsTextChange(text))}
placeholder={'Tell us any specification for how you want it packaged / substitutions that are ok, etc.'}
/>
I know you want us to be respectful of your time, but please also be respectful of ours / mine :)

I also noticed this issue on Galaxy Tab A6 device, it seems to be related to the poor performance of the device. The problem appears only when I type inside controlled fields (unable to reproduce with field without value props).


Scan area isn't properly centered in the visible viewfinder

What

@monsieurtanuki @g123k @M123-dev loosely related to #1581 which seems to be at a stalemate currently. I'm not currently clear as if of now, the focal point is defined by default at the middle of that vizor. It should be, because that's where users are going to put the barcode.

@teolemon I don't plan to approve #1582 as long as it uses copied/pasted code, when an elegant (and suggested) inheritance is possible.
I don't think the displayed viewfinder and the focus point are programmatically connected - though obviously the end-user would expect some consistency. I think we can even scan invisible barcodes, for instance a barcode hidden by the carousel.

This ticket is actually just a UI issue.
=> nothing related to the scan performance
I really love your draw @M123-dev, but I'm not sure where you want the visor to be.
Could you elaborate a bit more, please?

Sure @g123k the upper line is way shorter then the lower one. The ViewFinder should be centered in between the top and the carousel not directly below the "Clear" and "Compare" buttons

Comment by @stephanegigandet in #1794

I used to have the scan area in the good position, but with recent updates, it's now on top of the screen.
Screenshot/Mockup/Before-After

Smartphone model

Device: Galaxy S8


Increment Version

@JuliaRegistrator register() UtilityModels v0.2.3

Registration pull request created: JuliaRegistries/General/35953
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.3 -m "<description of version>" 3e15d652626f523943c5ab1b08bd3a625351035f
git push origin v0.2.3

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/53422
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" 26b98167b7f9a755b843b5c54fd1fc407ff7b77f
git push origin v0.2.4

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/55026
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.5 -m "<description of version>" efb1cb179a96ca9fe1a9fd560ff03e4576980e41
git push origin v0.2.5

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/82022
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" ac8352d5319cabb393235d60fa4311938e9d3256
git push origin v0.3.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/82022
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 0551b683854f41988df5d6e6df7cee9fa7cb5fc8
git push origin v0.3.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/82022
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" d2f170045a47f63272e7784fa39075ea9f7145f6
git push origin v0.3.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/82937
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" 339bada252c4b9a7c5aeaa385349cddbaf8963a0
git push origin v0.3.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/84804
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" d25d41631f181fbef6b4bd03d6ab6aba266debf7
git push origin v0.3.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/104860
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" 634f93854bcec896a4b4e1d1f9a1c9fc3d40b955
git push origin v0.3.3

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/111926
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" 4e14a3f22cc20438849794d2f3b5afa01ff8b650
git push origin v0.4.0


custom item -> too high minimum item level

if I want to integrade a custom item with BfA, I get the error: "The minimum item level of custom items is 550!"
With BfA it is a much too high border for custom items. It should be more like 200.
In:"CustomItems.lua", if you change the lines:
11: local minimumIlvl = 550
to
11: local minimumIlvl = 200
and
138:   if iLevel < 500 then
to
138:   if iLevel < 200 then
it works at me.
(funny the old text said 550 and the code checks 500 :)

Hey, thank you for your message.
I fixed this in the developer branch.
Just testing some other things and then there will be an update :)


Using background knowledge makes FCI algorithm slower

Hi!
I would like to use the FCI algorithm with background knowledge, but I have noticed that the computation speed with the background is much slower than the computation speed without passing the background knowledge to FCI (or PC). I work with about 300 variables and there are not many dependencies (about 1,2 or 3) between them. In my background knowledge there are a lot of forbidden edges and some required edges. As far as I understand the FAS function, the amount of forbidden edges will reduce the adjacency list by a lot and also the separating set will be smaller than the version without the background knowledge.
I cannot find a explanation for the increase of computation speed, what am I missing?
Thanks in advance!

The issue I think is that checking background knowledge requires an overhead, so if you don't have to do it the algorithms will run faster.
The way it's stored is in pairs <{n1, ..., nm>, {nq...nr}>, where edges are forbidden in reverse. The set lookups should be fast (i.e., if you forbid all of the second from causing any of the first, and you try to add an edge x1->x2, if will look to see if x1 is in the second set and x2 is in the first set and if so will forbid it). If you give separate singleton pairs for each, like <{x1}, {x2}>, it has to go through a lot of sets to figure this out. Do you know how your knowledge is being entered?

Hi, I have added a childclass of this BackgroundKnowledge class called FastBackgroundKnowledge in my code which inherits all the properties of the BackgroundKnowledge, except for the is_forbidden() and is_required()  functions to fix my problem.
I have added two dictionaries for which the required and forbidden edges are stored in. For each required edge X1 -> X2 we have a dict_required {"X1" : [X2]}. This way the is_forbidden() function and is_required() function do not have to look through all sets, but has a lookup by node name. This has lowered the FCI function computation time significantly!
There is only one problem, in the file fas.py line 286, type checking has been done by stating type(knowledge) == BackgroundKnowledge I would like to suggest to change this to isinstance(knowledge, BackgroundKnowledge), such that inheritance is possible :)

Thanks so much! Your solution looks fantastic : ) If you would like to, could you please create a PR (including a short test example) for this so that your contribution could be better recognized? We can also review and push this if everything goes smoothly. Of course, we greatly appreciate your suggestions whether you would like to PR it or not.


Error with unicode module names on Python2

I maintain a Django installation and want to migrate the settings (lots of from X import *) to django-split-setings. Seems everything went fine, but the tox test for Python 2.7 (the only tested version < 3) bailed on me with the following error:
Traceback (most recent call last):
  File ".tox/py27/bin/django-admin.py", line 5, in <module>
    management.execute_from_command_line()
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 302, in execute
    settings.INSTALLED_APPS
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/django/conf/__init__.py", line 55, in __getattr__
    self._setup(name)
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/django/conf/__init__.py", line 43, in _setup
    self._wrapped = Settings(settings_module)
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/django/conf/__init__.py", line 99, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/…/source/streambox/streambox/settings/test.py", line 19, in <module>
    scope=globals()
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/split_settings/tools.py", line 84, in include
    exec(compile(to_compile.read(), included_file, 'exec'), scope)
  File "/home/…/source/streambox/streambox/settings/components/base.py", line 147, in <module>
    scope=globals()
  File "/home/…/source/.tox/py27/local/lib/python2.7/site-packages/split_settings/tools.py", line 90, in include
    module = types.ModuleType(module_name)
TypeError: module.__init__() argument 1 must be string, not unicode

This might be a result of from __future__ import unicode_literals. Any ideas how to handle this?

Thanks, will dig it soon. Do you have any fix for yourself?

Not really… For starters we just dropped Python 2 support (cause it's not needed in house). But that's temporary, cause we would like to keep 2.7 supported. I'm not sure, if unicode_literals is absolutely needed, but have to read up on it and check our code a lot more.
So, just workarounds for now. I was thinking about monkey–patching and "byteify" the relevant parts… but not sure where to start and what's relevant.

Hi, I got this working. Damn this unicode/str things in python2.
Here's the change itself: https://github.com/sobolevn/django-split-settings/blob/d3d1afb3bbab117ab4479537f170056f6c4a809a/split_settings/tools.py#L91
It won't probably work on decode error, but that's intended.
This is your example, I guess:
https://github.com/sobolevn/django-split-settings/blob/d3d1afb3bbab117ab4479537f170056f6c4a809a/tests/test_unicode.py
Basic unicode test: https://github.com/sobolevn/django-split-settings/blob/d3d1afb3bbab117ab4479537f170056f6c4a809a/tests/test_tools.py#L79

Thanks for the fast fix!
While we will wait with re–enabling Python 2 support for your next release, I ran the latest Github version in some test environments and it works.

Nice, I will release it soon.


Fix euler's totient in factordb

Fixed #338

All linting warnings (except those in XYXZ) are lifted

I feel like it makes more sense to set private key phi than directly decrypt ciphertext in the function, but please let me know if that introduces bugs for other attacks. Will change it back.

I am not sure what solveforp is doing here. Left it as it is for now, but happy to make the function cleaner if someone knows what edge cases the function deals with.

Sample Output
└─$ time ./RsaCtfTool.py -n<PHONE_NUMBER>87398016057355158654193468564980243813004452658087616586210487667215030370871398983230710387803731676134007721137156696714627083072326445637415561591372586919746606752675050732692230618293581354674196658443898625965651230501721590806987488038754683843111434873697465691139129703835890867256688046172118591 -e 65537 --uncipher<PHONE_NUMBER>03687479298989188290833629421904543231503224641743768867721632949682167895699280370759100055314992068135383846690184090232092994595979623784341194946153538127175310278245722299688212621004144260665233469561373125699948009903943019071999887294005117156960295183926108287198987970959145603429337056005819069 --attack factordb
private argument is not set, the private key will not be displayed, even if recovered.

[*] Testing key /tmp/tmp4mdky8uy.
[*] Performing factordb attack on /tmp/tmp4mdky8uy.
[*] Attack success with factordb method !

Results for /tmp/tmp4mdky8uy:

Unciphered data :
HEX : 0x696374667b736d346c6c5f7072316d65735f6172655f6e305f6e305f39623132393434337d0a
INT (big endian) :<PHONE_NUMBER>2382695540362968023909576616640795468890045561607192167142506709009625171732167946
INT (little endian) :<PHONE_NUMBER>026446523630569196961759828517612905583806931284709521828848496203920243271426921
utf-8 : ictf{sm4ll_pr1mes_are_n0_n0_9b129443}

utf-16 : 捩晴獻㑭汬灟ㅲ敭彳牡彥の湟弰戹㈱㐹㌴੽
STR : b'ictf{sm4ll_pr1mes_are_n0_n0_9b129443}\n'

real    0m1.334s
user    0m0.316s
sys     0m0.023s

Nice! Thanks


Create preview environment which used to point to dev branch

Create preview environment and it will be used for pointing to dev branch later for any branch.

We are using 3.0 as main branch for dev


GPS Location

Have we ever discussed requesting the user's GPS location and zooming to that on load? Or at least adding a button to zoom to it.

Nope, but we can crib that from plss.

Bert said that this used to be in atlas and then was removed. Not sure if it ever was in there but he asked for it again the other day.

@nathankota do you want to contact Bert and see if he would like to sponsor this feature?

Sure. We're going to send him an estimate for another project in the very near future, and I could include this. What do you think it will take hours/effort-wise?

A half day more or less.


How to enable E-mail verifications?

I'd like to know how to enable e-mail verification because it's kinda complicated xD

you have to set this config to true
https://github.com/kokspflanze/PServerCore/blob/master/config/module.config.php#L427

Thank you ;) I installed pservercmsfull so I don't have this file. Can I find it somewhere in PserverCMSFull or should I install pservercore with pservercmsfull?

@craineyo its already install you just have to overwrite the config, and dont forget to setup the mail smtp access.


drivers: uart: Assert in event driven nRF UART driver when using power managament

Describe the bug
When enabling asserts in a build that otherwise appear to be working fine an assert is seen when enabling dynamic device power management and attempting to send data.
The assert happens in nrfx drivers when starting an already started timer for the HW RX counter.
To Reproduce
prj.conf:
CONFIG_PM_DEVICE=y
CONFIG_PM_DEVICE_RUNTIME=y

CONFIG_SERIAL=y

CONFIG_NRFX_UARTE3=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_UART_0_ASYNC=y
CONFIG_UART_0_NRF_HW_ASYNC=y
CONFIG_UART_0_NRF_HW_ASYNC_TIMER=0
CONFIG_UART_0_NRF_ASYNC_LOW_POWER=y
CONFIG_NRFX_TIMER0=y

CONFIG_ASSERT=y
CONFIG_CONSOLE=n

main.c:
#include <zephyr/kernel.h>
#include <zephyr/device.h>
#include <zephyr/drivers/uart.h>
#include <zephyr/pm/device.h>
#include <zephyr/pm/device_runtime.h>

#include <string.h>

#define UART_DEVICE_NODE DT_CHOSEN(zephyr_shell_uart)
#define MSG_SIZE 32

static const struct device *const uart_dev = DEVICE_DT_GET(UART_DEVICE_NODE);

void _uart_callback(const struct device *dev, struct uart_event *evt, void *user_data)
{
	/* Ignore */
}

void print_uart(char *buf)
{
	int msg_len = strlen(buf);

	uart_tx(uart_dev, buf, msg_len, 0);
}

int main(void)
{
	if (!device_is_ready(uart_dev)) {
		return 0;
	}

	/* configure interrupt and callback to receive data */
	int ret = uart_callback_set(uart_dev, _uart_callback, NULL);

	if (ret < 0) {
		printk("Error setting UART callback: %d\n", ret);
		return 0;
	}

	pm_device_runtime_enable(uart_dev);
	pm_device_runtime_get(uart_dev);

	print_uart("Hello world!\r\n");

	return 0;
}

Build and flash, and attach to see hanging in assert handler.
west build -b nrf9160dk/nrf9160/ns
west flash --erase
west attach

Expected behavior
Impact
Can't enable asserts, which as explained here: https://github.com/zephyrproject-rtos/zephyr/issues/71130#issuecomment-2222322648 a lot of functions rely on to fail fast.
Logs and console output
ASSERTION FAIL [m_cb[p_instance->instance_id].state == NRFX_DRV_STATE_INITIALIZED]
 @ WEST_TOPDIR/modules/hal/nordic/nrfx/drivers/src/nrfx_timer.c:210

Environment (please complete the following information):
Zephyr v3.7.0 or current main branch.
Linux
Zephyr SDK 0.16.4

Triaged internally

Sorry no. It crashed with the application like this on my own board, but on the DK it did not.
Adding CONFIG_CONSOLE=n it crashes on the nrf9160 DK (with NS).
I have updated the description.

I still cannot reproduce it (on 3.7.0). On which commit are you running it? Maybe anything specific in the overlay?

I went back and checked it. I'm not sure anymore what I have reproduced it on earlier.
It happens to me on NCS 2.7.0 release.
I therefore went to zephyr commit ea02b93eea3 which is the last common commit between zephyr and the NCS fork.
It is reproducible there.

Finally, I managed to reproduce it on that commit. I did bisect and it was fixed by 79c93dd5ecfde7b6af6109672b856bbf230bbda1. I think we can close it.


⚠ ClamAV has degraded performance

In face2e5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: ClamAV performance has improved in fb014c4.


Add HTML, CSS, JavaScript linter

See the wallet directory in the testapp.

Hi @joshklop is this still open, if yes could you tell the exact requirement would like to contribute.

@Nandini1071 Something like a prettier config and integration into the make lint Makefile target would probably be sufficient.


Add a basic CI/release pipeline

This adds a release pipeline that packages and pushes based on tags. The overall flow is:

create commit crafting CHANGELOG.md with desired version number
tag that commit with the matching version number
pipeline should

read changelog
perform build
set version/release notes
create package
create github release
push package to nuget

before this is done, we will need to create a NUGET_KEY secret in this repository.

I added an Ionide-org nuget key with publish rights to FsAst and any future FsAst.* packages to the secrets for this repository.

Thoughts on this now @Krzysztof-Cieslak/@7sharp9?

Looks good. What else is required?
You can look at this repo for the reference
https://github.com/fsprojects/FSharp.Collections.Immutable/tree/master/.github/workflows
PR triggers build workflow, merge to develop publishes to MyGet, merge to master publishes to NuGet

Just want a quick once-over from another owner of this repo before I merge this and try it out. @Krzysztof-Cieslak or @7sharp9 any thoughts?  I'm pretty confident in this.

needed a couple small tweaks to the action around escaping strings and regexes, but it's working! 0.10.0 is validating on nuget now: https://www.nuget.org/packages/FsAst/0.10.0


Write a blog about the engineering side of Azure Search migration

It's been quite a long time since we've shipped. We can reconsider this later, if desired, and re-open.


Search Query and Response

Fixes #22
Changes Made

Added search function with query and response structs
Added tests (only work locally with elasticsearch running)

Go ahead and add Skip to the beginning of the test function's name. CI should then pass. Ref #31.
Please add a link to the new ticket #32 above the time.Sleep line.

Actually, you know what: @hkethi002, go ahead and take your additions to def.go and move them to search.go. You had the right idea, there are several responses in def.go, but I've decided to keep file-specific structures (ones not reused elsewhere) in their own files.

LGTM! An example search I ran:
>>> search_query = {"filters":[{"terms":{"file.type":["tabular data"]}},{"terms":{"subject.sex":["male"]}}],"return_type":"a
nalysis","search_string":"afq","all_data":False}
>>> results = fw.search(search_query)
>>> len(results['results'])
52


Use tqdm from tqdm_utils

This PR replaces tqdm from the tqdm lib with tqdm from datasets.utils.tqdm_utils. With this change, it's possible to disable progress bars just by calling disable_progress_bar. Note this doesn't work on Windows when using multiprocessing due to how global variables are shared between processes. Currently, there is no easy way to disable progress bars in a multiprocess setting on Windows (patching logging with datasets.utils.logging.get_verbosity = lambda: datasets.utils.logging.NOTSET doesn't seem to work as well), so adding support for this is a future goal. Additionally, this PR adds a unit ("ba" for batches) to the bar printed by Dataset.to_json (this change is motivated by https://github.com/huggingface/datasets/issues/2657).

The current CI failure is due to modifications in the dataset script.

Merging since the CI is only failing because of dataset card issues, which is unrelated to this PR


Add ember-qunit-assert-helpers assertions

This is one of the steps needed to deprecate https://github.com/workmanw/ember-qunit-assert-helpers (by rolling in the helpful assertions)
Depends on https://github.com/emberjs/ember-test-helpers/pull/1071

i don't have time to work on this

@stefanpenner thanks for clarifying the state on this as you hit your out-of-time spot. If someone wants to pick it up, could you potentially carve out 15–30 minutes to get them up to speed on the issues?

@chriskrycho - I'm probably the best contact person there (@stefanpenner handed off to me, but I ran into the same general "out of time" issue).


Crash slice bounds out of rang

Have you checked the roadmap on the website, and existing issues, before opening a dupllcate issue?
Yes
Describe the bug
bitmagnet crash with panic :

panic: runtime error: slice bounds out of range [:49152] with capacity 38184

goroutine 5492610 [running]:
github.com/bitmagnet-io/bitmagnet/internal/metainfo/metainforequester.readAllPieces({0x935b360, 0xc000774590}, 0x9528)
        /mnt/podman-volume/bitmagnet/bitmagnet-io/internal/metainfo/metainforequester/requester.go:262 +0x445
github.com/bitmagnet-io/bitmagnet/internal/metainfo/metainforequester.requester.Request.func1()
        /mnt/podman-volume/bitmagnet/bitmagnet-io/internal/metainfo/metainforequester/requester.go:89 +0x1ae
created by github.com/bitmagnet-io/bitmagnet/internal/metainfo/metainforequester.requester.Request in goroutine 5492132
        /mnt/podman-volume/bitmagnet/bitmagnet-io/internal/metainfo/metainforequester/requester.go:67 +0x2e7

To Reproduce
Just wait a torrent with a lot of pieces I guess
Expected behavior
Not crash
General (please complete the following information):

Bitmagnet version: v0.0.7
OS and version: Ubuntu

Hi @dr4gn3l , this is fixed in the linked PR which will be merged shortly.


add igtv

please add historys and igtv links

updated , now igtv is supported
you can see history at ig.log file


Ability to delete RBAC role bindings

Is your feature request related to a problem? Please describe.
JulieOps doesn't delete obsolete role bindings if they're removed from topology file. Even if we use --allowDelete option.
Looks like only new role bindings are created.
Describe the solution you'd like
JulieOps deletes obsolete role bindings if they're removed from topology file (assuming it is run with  --allowDelete option).
Additional context
Preliminary investigation: Default implementation of AccessControlProvider.listAcls() returns empty map, and it's not overridden in RBACProvider. So as far as I understand, Julie Ops will never consider any RBAC binding as "existing" in the cluster and will never delete it.
https://github.com/kafka-ops/julie/blob/master/src/main/java/com/purbon/kafka/topology/AccessControlProvider.java#L16
https://github.com/kafka-ops/julie/blob/master/src/main/java/com/purbon/kafka/topology/roles/RBACProvider.java

Hi,
thanks for requesting this. I agree this is a limitation, so I have changes into a bug, it should really work.
As a context:
  private Set<TopologyAclBinding> loadActualClusterStateIfAvailable(ExecutionPlan plan) {
    Set<TopologyAclBinding> bindings =
        config.fetchStateFromTheCluster() ? providerBindings() : plan.getBindings();
    return bindings.stream()
        .filter(this::matchesManagedPrefixList)
        .filter(this::isNotInternalAcl)
        .collect(Collectors.toSet());
  }

  private boolean isNotInternalAcl(TopologyAclBinding binding) {
    Optional<String> internalPrincipal = config.getInternalPrincipalOptional();
    return internalPrincipal.map(i -> !binding.getPrincipal().equals(i)).orElse(true);
  }

  private Set<TopologyAclBinding> providerBindings() {
    Set<TopologyAclBinding> bindings = new HashSet<>();
    controlProvider.listAcls().values().forEach(bindings::addAll);
    return bindings;
  }

the deletion will only be avoided when using the bindings provided from the cluster, if bindings are provided from the local state, it will work as expected as the list method is not used.


docs(examples): add example template aws-verify-email

Holla!

This PR adds aws-verify-email.tsx to the example templates
In addition, there's an aws-logo.png image to complement the template

Thanks for the PR!

Welcome!


GPD Win Mini 2024 SteamUI / Gamescope framerate limiter does not work

Describe the bug
FPS Limiter set by steam UI does not limit the in game FPS based on what the performance monitoring tools are reading.
What did you expect to happen?
Expected framerate to be limited to what is set in the UI
Output of rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:f70eae81ad4d8cadfd03eea4b11e9c0825206f483ed02a677af9cee023f1a972
                  Version: 40.20240828.0 (2024-08-29T00:21:44Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:f70eae81ad4d8cadfd03eea4b11e9c0825206f483ed02a677af9cee023f1a972
                  Version: 40.20240828.0 (2024-08-29T00:21:44Z)

Hardware
G1617-01
Extra information or context
No response

Yes, the limiter is broken when VRR is on unfortunately. You need to use another means to set the framerate limit for now.

@KyleGospo close as completed and remove dosubot


Mute everything

ok, I activated mute everything, and ummm, now I cant unmute everything??  what gives?  am I doing something wrong??

If I push the button again, nothing, if I uninstall your plugin nothing, I can NOT get audio or microphones to work on my computer at ALL, WTH did you do?:"?a,gAFSD<GB?VDZC   This is some BULL CRAP!!  WTH would you make a mute ALL, but not an unmute ALL??  SERIOUSLY!?!?!?!?!?!?!?!?

I have now made a ticket with loupedeck and reported this issue to them, I still cant get ANYTHING to play, and now also my mic is muted....why would you make such a button and not have it reversable????  I stream on twitch and now you are costing me!!!!


Describe what each optional mod adds

Bob ores:
Thorium
KS Power:
Wind turbines
Landfill Painting:
Landfill options. Default type is configurable in Sea Block startup options.
Bob mining:
Pickaxe research
Bob inserters:
Bob enemies:
Worm variety. Alien artefacts. Power armour. Etc

Different categories:

Required (e.g. Sea Block, Bio Processing)
Recommended for full experience (SCT, Circuit Processing)
Optional (Bob's Mining, KS Power)
Graphical (Landfill Painting, Artisanal Reskins)
Helpers (FNEI, Recipe Book, Helmod)

Once LandfillPainting has been updated with standardized walk speeds, mods in Graphical and Helper categories should not affect gameplay at all.

This documentation is really helpful! Right now it is pretty unclear why you would even want mods like bobores when the whole point of this modpack is to remove all ores. I would like to suggest to also change some dependencies according to the categories you created:
SeaBlock:

hard dependency: "required"
optional dependency: "recommended"
hidden optional dependency (when necessary): "optional", "graphical" and "helpers"

SeaBlockpack:

hard dependency: "required", "recommended" and "optional"
optional dependency: "graphical" and "helpers"

As a personal preference I would also add Factory planner into the helpers category.

This documentation is really helpful! Right now it is pretty unclear why you would even want mods like bobores when the whole point of this modpack is to remove all ores. I would like to suggest to also change some dependencies according to the categories you created:
SeaBlock:

hard dependency: "required"
optional dependency: "recommended"
hidden optional dependency (when necessary): "optional", "graphical" and "helpers"

SeaBlockpack:

hard dependency: "required", "recommended" and "optional"
optional dependency: "graphical" and "helpers"

As a personal preference I would also add Factory planner into the helpers category.

https://seablock.fandom.com/wiki/Sea_Block_Pack_Mods

https://seablock.fandom.com/wiki/Sea_Block_Pack_Mods


Setup general verification and add verification processing on setup options

Overview

Let's define in the spec, with reference to 'validator.js' functions.
Update 'question-and-answer' interrogation bundle to take 'validations' fields which takes an array of string validation specs
Update option processor to run validation checks
create issue in 'command-line-documentation' to utilize the validation spec

Work for this issue will begin begin on branch work-liquid-labs/cloudsite/240.


Add MSE info

I've a few doubts.

The feature is supported in IE11, but only on Windows 8+.
Looks like it's supported on Safari 8, according to http://www.jwplayer.com/html5/mediasource/, but there's no info on https://www.webkit.org/status.html, https://www.chromestatus.com/features/4563797888991232 and https://dev.windows.com/en-us/microsoft-edge/platform/status/mediasourceextensions say Safari doesn't support it.
Support for codecs varies according to browser and operating system.

http://nickdesaulniers.github.io/mp4info/
http://nickdesaulniers.github.io/netfix/#/

Safari 9 has it

Since we are tracking feature implementation and not per platform details.
Also http://nickdesaulniers.github.io/netfix/demo/bufferWhenNeeded.html works in Safari.


Diagram rendering states [no data, error and loading]

Hello @NikolovI this is a good task in order to get to know the frontend part of the project. It will require to get to know a bit about Plotly JS, how thefront-end request data from the backend and how we handle JSON response from the Backend.
Short intro:
On the frontend we have special JSON definition that describes what data needs to be fetched from the backend, what transformations need to be performed over the data and how the data will be rendered/decorated on the fronend. I blogged a bit about this topic in chapter "Diagram configuration format" here - https://calendar.perfplanet.com/2019/lessons-learned-from-developing-my-real-user-monitoring-system-basic-rum/
As matter for fact we don't really send the JSON definition to the backend but we transform the JSON to post parameters that are handled later in the Backend. For reference most of the JS related logic is located here: https://github.com/basicrum/backoffice/blob/master/public/js/basicrum/widget.js
What to fix?
1. No diagram data:
Sometimes we do not return any results for the cases when:

Our DB is empty
Applied filters in JSON diagram config do not return data

Currently for this case the UI looks broken and my idea is to fix the coordinate system and provide information to the user that there is not data.

2. Backend error/exception:
The current state of the backend is far from perfect and we get errors when Basic RUM's database doesn't contain performance data yet. However this will be fixed in next weeks but we are not protected from backend errors in the future for whatever reasons.
This problem can be observer under the following conditions:

Basic RUM DB is empty.
We load the main dashboard and look at "Device distribution" diagram.

In this case the diagram is empty and there is no indication what actually happened.
We should:

Add centered error message.
Have coordinate system.

It's important to note that in this case the backend doesn't return JSON but the frontend JS logic works only with JSON. This means that we will need to handle exceptions in the backend and craft proper JSON response to the front-end.
For reference this is is the current response we get from the backend:
<!-- Notice: Undefined index: count (500 Internal Server Error) -->
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="UTF-8" />
        <meta name="robots" content="noindex,nofollow" />
        <meta name="viewport" content="width=device-width,initial-scale=1" />
        <title>Notice: Undefined index: count (500 Internal Server Error)</title>
...

3. Diagram loading:
Right now there is no indication that a diagram is in loading state but sometimes it may take some time for the backend until diagram data is fetched, transformed and returned to the backend. My suggestion is that we add a loading animation in the center a diagram.
For now we should use this GIF because we already have it in the project: public/img/devoops_getdata.gif.
The loading animation should be shown when:

We visit the main dashboard for first time and we are waiting for all diagrams to be loaded.
We change filters and wait new data to be loaded. For example we can simulate the filtering when we click on the periods control (30, 60, 90) days.

Hint: While developing locally we can add artificial delay in WidgetController::generateDiagram() method. We can use the sleep() function: https://www.php.net/manual/en/function.sleep.php
Good luck!

Due date: yesterday!


Provide option to use actual OpenAI Backends.

Currently, USE_SIMULATOR flag will control the deployment of the simulator. However, when we set the value to false it breaks the deployment due to simulator_key.
There are few options,

Along with URLs as env, get their corresponding keys as well from .env

Make simulator_key as optional, provide guidance to use api_key as a header

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Any update on this issue ? Any workaround ?

Closed via PR #63


Move volume types into reference section

This is a Feature Request

What would you like to be added
Take https://kubernetes.io/docs/concepts/storage/volumes/#volume-types and move it to be inside https://kubernetes.io/docs/reference/storage/ (you will have to create https://kubernetes.io/docs/reference/storage/)
Why is this needed
https://kubernetes.io/docs/concepts/storage/volumes/ is a long page that does not particularly help a new person understand how volumes (whether these are configMap, csi, emptyDir) etc work, and how some volumes are also PersistentVolumes and some aren't.
Comments
/sig storage
/label refactor
/language en
Please only start work on this issue if it has been triaged as Accepted. If you don't see a label showing that, please look for some other way to contribute.

More context: https://github.com/kubernetes/website/issues/31159

/assign

@sftim assign me

/triage accepted

/assign

Hey @sftim , Should I create a different section for reference

HShould I create a different section for reference

@kumarankit999 you will have to create https://kubernetes.io/docs/reference/storage/ as part of the change you propose. However, check if PR #43278 already covers this. If it does, you might want to liaise with @tengqm first.

Yes, I will look into this!!

@kumarankit999 Are you still working on this issue?


Forms submit when they are empty #85 - Form Submission Fixed

#85
Fixed the form submission as required issue

Resolve conflicts and share the hosted link of your repo.

I have resolved the conflicts.
Here is the hosted link of the repo:  https://ishika414.github.io/Aec-Library-Website/

This issue already has been fixed


[feat]: ability to transfer vehicles to other citizens

Describe the feature
The ability to transfer a vehicle from one citizen to the other citizen. Originally in v3, requested to be in v4 too.
Additional Context
No response

Soon:tm: