Add ontology ancestor mapping notebook

Notebook used to compute ancestors for nodes in human, mouse and UBERON (only a subset) ontologies.

Suggest mentioning this in this doc.
And what if we put this notebook/script somewhere under cellxgene_schema_cli/cellxgene_schema to keep it closer to related files?

Adding to the doc for sure, not that sure about adding it to cellxgene_schema - this is more of a static generation file and it's not quite related to the validator. @pablo-gar since you mostly work on this repo, what are your thoughts?

I agree that for the moment we should not include under cellxgene_schema_cli/cellxgene_schema. However if at any point we need to put extra constraints in obs["development_stage"] for the validator, then we need to make sure to include ancestors in the reference static ontology files.
The work Emanuale did here is because ancestors and descendants cannot be extracted as usual with owlready2, thus that info is not included in the reference files at cellxgene_schema_cli/cellxgene_schema/ontology_files/all_ontology.json.gz.
I may recommend we put this under docs to not clutter the root of the repo, @brianraymor any suggestions?

@ebezzi can you also please add a brief description of what the notebook does, maybe at the beginning of the notebook

@pablo-gar

What about a notebooks folder?
Agree, if we increase the ontology constraints (or add new species) we will need to regenerate the files. I think this would be infrequent enough not to justify automating the process
This will be used in production. I think @brianraymor mentioned that we're not particularly concerned about having to regenerate the mappings often. When I ran the script, I downloaded the ontology files from the link you sent me and ran it from my machine, so they're the latest versions.
I will add a description, thanks for the suggestion!

Who is the audience for this notebook? I like Pablo's suggestion to use notebooks.
The ontologies must match the pinned versions in schema 2.0.0. HSAPDV and MMUSDV do not change much, but UBERON does.

@brianraymor The notebook is mostly meant for developers who want/need to regenerate the mapping files. Regenerating it won't be a big deal, but it should be a sporadic activity (say once per year), otherwise we might have to create some sort of automation for this.


Confusing comment on corejs@3

https://github.com/facebook/create-react-app/blob/master/packages/babel-preset-react-app/dependencies.js#L88-L89
// This will need to change once we upgrade to corejs@3
corejs: 3,

Was the change not really that needed?

Unstale
On Sun, Jan 9, 2022, 19:59 stale[bot] @.***> wrote:

This issue has been automatically marked as stale because it has not had
any recent activity. It will be closed in 5 days if no further activity
occurs.
—
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/11099#issuecomment-1008335899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWYQIMSPXFK6SYOMJT2NZDUVG5GDANCNFSM46ULM5PQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Horizons is not a constructor

Hello!
I`m using your library to build 3D Solar System Map and really appreciate you for given possibilities to interact with HORIZONS.
But unfortunatelly, when I try to initialize new Horizons it sends me error you can see below.
Can you please help me to understand what I do wrong?
Thanks!

Code is simple:
import * as THREE from "three";
import { TrackballControls } from "three/examples/jsm/controls/TrackballControls.js";
import { Horizons } from "@zachfejes/js-horizons";

export default {
  name: "Map",
  props: {},
  data() {
    return {
     ...not important info...
    };
  },
  methods: {
    init: function() {
      const horizons = new Horizons();
      horizons.initialize(() => {
        horizons.search("Jupiter", (error, response) => {
          console.log(response);
          horizons.close();
        });
      });

Install all dependencies and replace import...from by
var jsHorizons = require("@zachfejes/js-horizons");
And now receive next error.
What it can even be?

Also you can write import like this
import Horizons from "@zachfejes/js-horizons";JavaScript

Hey @letUser! I'll take a look at this this evening and see if we can find the problem.

I had the same problem. Using
const Horizons = require("@zachfejes/js-horizons");

instead of
 const { Horizons } = require("@zachfejes/js-horizons");

works.

@zachfejes any update on this issue? neither const Horizons = require("@zachfejes/js-horizons"); nor const { Horizons } = require("@zachfejes/js-horizons"); (like your docs suggest) works


chore(starknet_sierra_compile): avoid using OUT_DIR in run time

Stack:

#2481 ⬅
#2475
#2474

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


Move docs generator script to tabris-js-docs repo

Problem description
At the moment the json doc files are processed via the generate-doc.js script. The output of that script is than processed in the tabris-js-docs repo. This limits our ability to include json docs from other sources/repos to incorporate into our website docs.
Expected behavior
We should move the generate-doc.js script to the tabris-js-docs repository and aggregate docs from multiple sources there.
Environment

Tabris.js version: 2.5

The docs repo now launches the generate script.


Rails 7.0 support

This PR adds Rails 7.0 support. Rails 7.0 is still in the alpha release stage, so this shouldn't be merged until there's a release candidate. I'm opening the PR for comments right now. It is built on top of #1010, so that PR should be merged first or closed in favor of this one.
The biggest changes are in some initialization code. Rails 7 changes autoloading behavior on boot, so that's what caused most of the changes to the framework code. There was also a monkey patch for an Action View method that is removed in Rails 7, so that is dealt with as well.
Rails 7.0 is added to the CI build. Since I was adding jobs to the build, I also switched to a matrix approach. Previously, on Travis CI, only four jobs would run concurrently, so it made sense to use fewer jobs in the build. Now with Github Actions, the jobs all run concurrently, so there's no penalty for testing all combinations.

Nice change to matrix testing strategy.
LGTM


GUI is slow to react.

Testing on Nexus 6/Firefox, at least the following actions are painfully slow (several seconds beteween click and GUI react)

open connection
post
add detail
search
connect
... basically anything.

Before we start 'fixing' that we need to be sure we know the actual cause. Possible hypotheses are:

excessive use of angular observers and ng-repeat: #1104
too many queries into rdfstore-js
too many http requests

i try/tried to tackle the issue as follows:
Due to our past research we found that since everything is a single thread in js, we somehow block the gui by rather expensive/long lasting rdfstore functions, thus i focused my research within linkeddata-service.won.js for now
the idea that we are using too many angular observers and ng-repeats is imho not the reason why our gui is lacking behind, because the amount of repeated elements is way too small to have an performance impact, cuz even with angular 1 that performance drop would have caused people to not adapt to angular in the first place (but thats just MY opinion and could be proven wrong of course)
that the problem lies in the many http requests is also misguiding in my opinion since we would see or run into http timeouts if there are too many long running http requests, (usually a browser only does 5 requests synchronously and pushes the pending requests until the running requests have been done)

with that being said i created log entries for most of the methods in linkeddata-service-won.js to get a feel on what is called when and how often, and found out that alot of things are done there... duh....
anyway i found somewhat of a low hanigng fruit within the ensureRdfsMemberArrays method, this method is called recursivly way too many times, as seen in the log excerpt: provided here:
linkeddata-service-won.js:1546 ensureRdfsMemberArrays  . linkeddata-service-won.js:1546 ensureRdfsMemberArrays  m linkeddata-service-won.js:1546 ensureRdfsMemberArrays  m linkeddata-service-won.js:1546 ensureRdfsMemberArrays  a linkeddata-service-won.js:1546 ensureRdfsMemberArrays  a linkeddata-service-won.js:1546 ensureRdfsMemberArrays  s linkeddata-service-won.js:1546 ensureRdfsMemberArrays  t linkeddata-service-won.js:1546 ensureRdfsMemberArrays  e linkeddata-service-won.js:1546 ensureRdfsMemberArrays  r linkeddata-service-won.js:1546 ensureRdfsMemberArrays  r linkeddata-service-won.js:1546 ensureRdfsMemberArrays  . linkeddata-service-won.js:1546 ensureRdfsMemberArrays  m linkeddata-service-won.js:1546 ensureRdfsMemberArrays  a linkeddata-service-won.js:1546 ensureRdfsMemberArrays  t linkeddata-service-won.js:1546 ensureRdfsMemberArrays  c linkeddata-service-won.js:1546 ensureRdfsMemberArrays  c linkeddata-service-won.js:1546 ensureRdfsMemberArrays  h linkeddata-service-won.js:1546 ensureRdfsMemberArrays  a linkeddata-service-won.js:1546 ensureRdfsMemberArrays  t linkeddata-service-won.js:1546 ensureRdfsMemberArrays  . linkeddata-service-won.js:1546 ensureRdfsMemberArrays  o linkeddata-service-won.js:1546 ensureRdfsMemberArrays  r linkeddata-service-won.js:1546 ensureRdfsMemberArrays  g linkeddata-service-won.js:1546 ensureRdfsMemberArrays  g linkeddata-service-won.js:1546 ensureRdfsMemberArrays  / linkeddata-service-won.js:1546 ensureRdfsMemberArrays  w linkeddata-service-won.js:1546 ensureRdfsMemberArrays  w linkeddata-service-won.js:1546 ensureRdfsMemberArrays  o linkeddata-service-won.js:1546 ensureRdfsMemberArrays  n linkeddata-service-won.js:1546 ensureRdfsMemberArrays  / linkeddata-service-won.js:1546 ensureRdfsMemberArrays  r linkeddata-service-won.js:1546 ensureRdfsMemberArrays  e linkeddata-service-won.js:1546 ensureRdfsMemberArrays  s linkeddata-service-won.js:1546 ensureRdfsMemberArrays  o linkeddata-service-won.js:1546 ensureRdfsMemberArrays  u linkeddata-service-won.js:1546 ensureRdfsMemberArrays  r linkeddata-service-won.js:1546 ensureRdfsMemberArrays  c linkeddata-service-won.js:1546 ensureRdfsMemberArrays  e linkeddata-service-won.js:1546 ensureRdfsMemberArrays  / linkeddata-service-won.js:1546 ensureRdfsMemberArrays  n 2linkeddata-service-won.js:1546 ensureRdfsMemberArrays  e linkeddata-service-won.js:1546 ensureRdfsMemberArrays  d linkeddata-service-won.js:1546 ensureRdfsMemberArrays  / linkeddata-service-won.js:1546 ensureRdfsMemberArrays  v linkeddata-service-won.js:1546 ensureRdfsMemberArrays  v linkeddata-service-won.js:1546 ensureRdfsMemberArrays  o linkeddata-service-won.js:1546 ensureRdfsMemberArrays  f linkeddata-service-won.js:1546 ensureRdfsMemberArrays  f linkeddata-service-won.js:1546 ensureRdfsMemberArrays  o linkeddata-service-won.js:1546 ensureRdfsMemberArrays  w linkeddata-service-won.js:1546 ensureRdfsMemberArrays  m linkeddata-service-won.js:1546 ensureRdfsMemberArrays  c linkeddata-service-won.js:1546 ensureRdfsMemberArrays  n linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  n linkeddata-service-won.js:1546 ensureRdfsMemberArrays  x linkeddata-service-won.js:1546 ensureRdfsMemberArrays  x linkeddata-service-won.js:1546 ensureRdfsMemberArrays  9 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  9 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  2018-05-30T15:53:30.325Z linkeddata-service-won.js:1546 ensureRdfsMemberArrays  2 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  2 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  1 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  1 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  8 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  8 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  - linkeddata-service-won.js:1546 ensureRdfsMemberArrays  - linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  5 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  5 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  - linkeddata-service-won.js:1546 ensureRdfsMemberArrays  3 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  3 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  T linkeddata-service-won.js:1546 ensureRdfsMemberArrays  T linkeddata-service-won.js:1546 ensureRdfsMemberArrays  1 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  5 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  : linkeddata-service-won.js:1546 ensureRdfsMemberArrays  5 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  3 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  : linkeddata-service-won.js:1546 ensureRdfsMemberArrays  3 linkeddata-service-won.js:1546 ensureRdfsMemberArrays  0
apparently the method gets called for each character of a string too.... i also found that this method or the initial call of itself doesnt seem to serve any purpose because there is no return value and the second parameter is never accessed from the outside (and usually initialized as a new Set()) the first parameter seems to be the same before and after the call (checked via log entry and non equality operator), so i am assuming we can remove this method all together.... HOWEVER our main performance issue is not going removed then, so it is still somewhere else

see the two screenshots above, the first is with the ensureLoadedMethod, the second without the method (results are the same)
the performance without is significantly better than with the method (data is 1 whatsaround need with 15matches -> 16 needs that get parsed), also without the method the gui seems to stay responsive even though no elements are present yet (e.g loading indicator, cursor change on hover, clickable elements open etc)
i will create a pull request with that method removed for now because it is a big performance update (half the processing time per need), but i will investigate different issues further as we are not in the clear yet

Sounds like a good first step!

Merged  #1862 but it's not significantly faster on the original problem setup (live with Nexus 6)

I think click-reactions and typing are a bit faster now (typing sometimes was painfully slow even on the laptop).

One thing we can do immediately is prevent loading of archived needs by remembering their uris in localstorage.

And if we take one step back: what causes the impression that the application is slow?

initial loading time (until you see something) - that has improved and isn't so bad now.
delay when posting: it can take several seconds until the need shows up in the list.
slow GUI reactions: you click a button, the app takes long to even show you that you clicked. Sometimes animations are painfully slow, probably slowed down by other activities, such as loading data from the server
long delay after logging in while all the data is being loaded

Another, quite important issue is: which needs should we show in the list when someone logs in? And how should we order them? Currently, we show all active ones, and the ordering is not explained (or even clear to me). If we showed fewer items, we would have less of a performance problem.
I see the following options:

Top N, according to posting/reactivation date
Top N, according to recent activity on them
Top N, according to recency of unread events
Long shot: allow to group needs by topic, and only show topics

Of course, if we do not show all postings, we need to allow forcing to load the other needs

Another problem that adds to the impression of low speed is the handling of the websocket connection and session timeout. Over several sessions, I learned that, to be on the safe side, I have to reload the page after the  websocket crashed - which leads to me waiting again while everything loads. If that situation was handled gracefully (relogin if necessary, reestablishing the ws connection), that would remove a lot of friction.
Also, the big red bar at the top looks like something went really wrong. Maybe we could use the secondary color for that?

ok, I'll do it

As mentioned in #1908 a lot of our GUI sluggishness is specifically bad in Firefox, and has to do with the way we layout our sites.


refactored image_classifier_head to classifier_head

What does this PR do?
Refactored the file image/classification/heads.py moving the head to the core/classification.py changing the name from IMAGE_CLASSIFIER_HEADS to CLASSIFIER_HEADS
Fixes #1462
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[x] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Al lot, hope to "get to know more" the code

Have you considered leaving out the IMAGE_CLASSIFIER_HEADS and just instantiate it with all heads from CLASSIFIER_HEADS?
This way you will gain the following:

Not introduce a breaking change - removing IMAGE_CLASSIFIER_HEADS
Have IMAGE_CLASSIFIER_HEADS that could be further extended in the future with image specific heads.

This way you will gain the following:
* Not introduce a breaking change - removing `IMAGE_CLASSIFIER_HEADS`

* Have `IMAGE_CLASSIFIER_HEADS` that could be further extended in the future with image specific heads.

Regarding the error, pretty sure I didn't touch anything on this error looks like more of a precision error.
=================================== FAILURES ===================================
________________________ test_embedder_raising_overhead ________________________

    @pytest.mark.skipif(not _CORE_TESTING, reason="Not testing core.")
    def test_embedder_raising_overhead():
        """Tests that embedding to the output layer of a 3 layer model takes less than 10ms more than the time taken to
        execute the model without the embedder.

        Note that this bound is intentionally high in an effort to reduce the flakiness of the test.
        """
        model = NLayerModel(10)
        embedder = Embedder(model, "output")

        start = time.perf_counter()
        model.predict_step(torch.rand(10, 1000), 0, 0)
        end = time.perf_counter()

        model_time = end - start

        start = time.perf_counter()
        embedder.predict_step(torch.rand(10, 1000), 0, 0)
        end = time.perf_counter()

        embedder_time = end - start

>       assert abs(embedder_time - model_time) < 0.01
E       assert 0.013533204999987447 < 0.01
E        +  where 0.013533204999987447 = abs((0.11517994799999087 - 0.12871315299997832))

tests/core/utilities/test_embedder.py:108: AssertionError

Regarding the second point:
I am not an expert of lightning-flash I just went with was stated in the Issue #1464, but I don't get your point?
there were no  CLASSIFIER_HEADS

My point is that we are changing the public API by removing the IMAGE_CLASSIFIER_HEADS. This means that if there were users that was using that their code will be broken. My suggestion is to not break the public API but rather make it backwards compatible.
@ethanwharris What's your take on this as a original author of issue #1462?

My point is that we are changing the public API by removing the IMAGE_CLASSIFIER_HEADS. This means that if there were users that were using this API that their code will be broken. My suggestion is to not break the public API but rather make it backwards compatible.
@ethanwharris What's your take on this as a original author of issue #1462?

I agree, and let's safely assume that there will be users using IMAGE_CLASSIFIER_HEADS (though I didn't see relevant usage on GitHub global grep, but that's not enough to say no one uses it).
Let's point IMAGE_CLASSIFIER_HEADS to CLASSIFIER_HEADS in this PR, and add a deprecation message, something like:
In future releases, IMAGE_CLASSIFIER_HEADS will be deprecated in favor of CLASSIFIER_HEADS. Please consider using `<imports>.CLASSIFIER_HEADS` instead.

Sorry for the delay in getting back on this. @ethanwharris - Does this sound good to you? Also @ligaz @Abelarm please feel free to share any thoughts. :)

I am not an expert so I trust your opinion more 🙃

I'm leaning more towards:

The other alternate way would be to keep IMAGE_CLASSIFIER_HEADS and not deprecate, if in the future there is a possibility that IMAGE_CLASSIFIER_HEADS and CLASSIFIER_HEADS will diverge (or one of them will be a superset of the other).

I'm also perfectly fine with safely deprecating IMAGE_CLASSIFIER_HEADS.

Hi @ligaz and @krshrimali would something like this be an acceptable solution?
My idea was:

move the "generic_head" to CLASSIFIER_HEADS
keep the IMAGE_CLASSIFIER_HEADS but make it point to the generic CLASSIFIER_HEADS

It should keep the backwards compatibility and should be possible to add "image-specific" heads

Hey, @Abelarm - Yes! I think that's something we all can have a consensus on. :) Looks like you've already made the required changes, I'm sorry for the delay - I'll take this from here. Just need to check if we are missing anything in the docs etc. Thank you for your contribution 🚀 ⚡
@ligaz @ethanwharris - Please let me know if you've any further thoughts on this. Thank you all for the active discussion and involvement.

Looking at the azure pipeline I found out that there is an error:
File "/__w/1/s/flash/core/registry.py", line 123, in _register_function
    raise MisconfigurationException(f"You can only register a callable, found: {fn}")
pytorch_lightning.utilities.exceptions.MisconfigurationException: You can only register a callable, found: tensor

Could it be that I introduce it?


GUACAMOLE-1738: Update version of MySQL connector

Update version of MySQL connector used to resolve issue 1738 where it can no longer connect to the MySQL server using the new extension and old connector https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLE-1738

Thanks, @kelderek - please update your commit message to also include the GUACAMOLE-1738 tag.

@necouchman You mean just add GUACAMOLE-1738 to the message, or is there something else I need to do?  Sorry, not super familiar with Github

Ok thanks, it should be good now, then

Sorry, the title of the commit message still lacks the prefix:
Update version of MySQL connector
You'll need to reword the commit message and force-push it to fix it.

I was thinking you wanted the PR changes, not the commit.  My mistake, will get it fixed in a bit

@necouchman I made the original change through Github's web interface and it was going to be a bigger hassle for this to edit the commit title, so I just created a new PR #802


MM-27454 - Added CWSUrl to client config

Summary
Added CWSUrl to the client config to create the url for Cloud contact us.
Related PRs
Server: https://github.com/mattermost/mattermost-server/pull/15916
Webapp: https://github.com/mattermost/mattermost-webapp/pull/6731
Ticket Link
Needed for MM-27454 - Cloud Contact Us

/cherry-pick cloud-ga

Cherry pick is scheduled.


1573 changestreams

Adds support for output streams, which are turning out to be pretty awesome. Some notes on how this works:

If anything is reading from an output stream, the combiner will write the old and new tuple to it when syncing, otherwise there's no additional meaningful overhead
For sliding window queries, output stream writes are done separately by executing the overlay plan on cached in-window tuples
Sliding-window queries will tick roughly every step_size_ms in order to keep writing out values that depend on wall time
Out-of-window tuples are GC'd and indicated by the output stream tuple of the form: (<old>, null)
Concurrent combiners only cache and process the SW groups that belong to them, so all of this work is distributed evenly across combiners

Note that this diff doesn't include a function wrapper (e.g. output_of('cv')) for the output stream yet, so output streams are just referred to literally (v_osrel). Doing this the right way isn't too complicated but actually isn't trivial and does require some thought, and I didn't want to go out of scope with this diff.
As soon as this diff is ready to land, I'm going to rip out all legacy trigger stuff. I just didn't want the diff to be unnecessarily large. I think we should rip out the alert server as well.
Also, pytests are on the way.

Also, after doing some profiling on SW ticking, the overlay plan execution is definitely the obvious bottleneck.

Unfortunately, we won't be able to do it for aggregates which are uncombinable. But other than count(DISTINCT), I think all the other commonly used aggregates are uncombinable.

Instead of writing to any worker queue, I think the output streams should be sharded using the hash as well so that the changes made to a specific group are never reordered? Only insert should write to any worker.

Doesn't sharding over workers by combiner group hash mean (in the worst case) acquiring a lock on a worker for every tuple being written to the output stream? I think it's a good idea to always write to the same worker, but shouldn't we choose it like this?
worker_queue = worker_queues % combiner_id

Yes, that's probably a better way to do it. We also only need to write to the same worker when writing from a combiner process, otherwise we can keep on round robinning.

Cool, change coming shortly.

Looks good!


Secrets store with SQL back-end

Describe changes
Implements the Secrets Store as an alternative to using Secrets Manager stack components to store and manage secrets in a centralized service or database that doesn't require an active stack.
Design considerations
The Secrets Store is an optional runtime extension to the Zen Store:

it is an extension because it's not an integral part of the Zen Store interface. The Secrets Store interface is defined separately and Secrets Store implementations only need to implement the Secrets Store interface rather than the entire Zen Store API.
it is a runtime extension because the Zen Store can be dynamically extended at runtime with a Secrets Store according to how it is configured
it is optional because ZenML can even be configured to not implement a Secrets Store

This modular design allows us to support multiple implementations of Secrets Store and to decide at runtime through configuration means which one to use:

the REST Secrets Store (included in this PR) is implemented to use the REST Zen Store and its ZenML server HTTP connection as a back-end
the SQL Secrets Store (included in this PR) is implemented to use the SQL Zen Store and its SQL database as a back-end
other Secrets Stores (not included) will use the existing Secrets Manager implementations and should, in theory, be usable with any of the Zen Store flavors, although it only makes sense to use them in combination with the SQL Zen Store.

I considered various design patterns to support this, but there was one that was clearly superior in terms of ease of implementation and long term maintenance: the Proxy, or a slight variation of it. The ZenStore singleton instance acts as a Proxy or a Facade, meaning that it exposes a single API that includes its existing concerns (CRUD for Stacks, Stack Components, Pipelines etc.) as well as the Secrets Store concerns (CRUD for Secrets). I.e. the consumer code can just run zen_store.create_secret(...) without having to be aware that the Secrets Store is an optional extension. The ZenStore is responsible for proxying/relaying those calls to the Secrets Store instance configured at runtime, or raising a NotImplementedError exception if a Secrets Store wasn't configured.
Here's how this is implemented:

the BaseZenStore class inherits the Secrets Store abstract interface, so the exposed API includes secrets management
the BaseZenStore also has a BaseSecretsStore field - the object to which secrets management calls will be proxied
finally, the BaseZenStore implements the Secrets Store abstract interface by simply relaying all calls to the Secrets Store

To avoid writing a lot of boilerplate code required to proxy all secrets management method calls in the BaseZenStore, I wrote a reusable class decorator that generates those methods dynamically.
What's in the box ?
Included in this PR:

Secrets (domain) Models
Secrets Store interface definition - slightly resembles the Base Secrets Manager abstraction
Base Secrets Store and Secrets Store configuration classes
SQL Secrets Store implementation - built as an extension of the SQL Zen Store (in fact, it uses some of it's attributes and methods). Optionally encrypts and stores secrets in a new table in the SQL database.
REST Secrets Store implementation - built as an extension of the REST Zen Store (in fact, it uses some of it's attributes and methods)
ZenML Client API for centralized secrets management
ZenML CLI for centralized secrets management
Changes to existing secrets management consumer code (i.e. secret reference resolution) to first attempt to resolve secret references through the Secrets Store and then fall back to the current Secrets Manager stack components.

Secrets Scoping
Secrets Managers currently support different scopes for managing secrets. The Secrets Store being a global entity, it also implements secrets scoping and namespacing but it uses the existing ZenML concepts to that purpose:

secrets are by default scoped to a Workspace
in addition to that, secrets can also be scoped to a User
resolving a secret name is implicitly done first at User level, then at Workspace level
there is currently no enforcing of secrets visibility server-side through RBAC or authorization, just like it is currently done with Secrets Managers: any user can access any secret in any scope. Scoping is about managing different secrets namespaces.

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[x] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Should be good to go when the CI passes.

Thanks for the last-minute docs review @strickvl ! Should be good now.


In .NET CORE 6, user strings are not obfuscated.

In .NET CORE 6, user strings are not obfuscated.
my source :
https://github.com/pulmuone/WinFormsApp6
Screen-shot :
https://github.com/pulmuone/WinFormsApp6/blob/master/Obfuscator.png
test :
\bin\Debug\net6.0-windows>Obfuscar.Console.exe -s obfuscar.xml

obfuscar.xml

I added this and saw that it obfuscates normally.
However, in .net framework 4.8, this line was not required.

Duplicate to #318

In .NET CORE 6 you can try to add

it works for me


[WIP] Adjust HTML generated for announcements

Mark front page announcements as <aside> elements
This matches the HTML that gets generated for announcements on the rest of the site. It helps avoid search engines treating the announcement banner as the primary content of the web page.
Spotted during triage for issue #22036.

As part of this PR, would you add the attribute, data-nosnippet?
Related issue #22036.
/hold

/retitle [WIP] Adjust HTML generated for announcements

Related to #21788

Is this still on hold?

/retitle Adjust HTML generated for announcements

/hold cancel
Thanks @sftim

As an aside (😄 ), the front page has a better margin for the text in the announcement.
The other pages have a small left hand margin. I don't remember what the margin looked like when the announcement was first added. The Case Studies page announcement looks better.
Should open another issue to address the styling.
Thanks.
/approve

@sftim, I noticed that this pr closed (automatically) a couple of issues.
This worked, but are there any follow-on issues (release/merging)?

I don't see any further work - if I've missed something then feel free (anyone!) to point it out.


Writing a github action to deploy to staging

writes a github action that would deploy to staging every 12 hours

needs the secrets!


FLEX-4758 ~ Removes send from error handler

SonarQube analysis reported 2 issues

 2 major

Watch the comments in this conversation to review them.


Separate stdout and stderr from the run output

Put all tested method output in the same variable is an alteration of the real method result.
For exemple :
testedMethod() {
  echo "the result"
  (>&2 echo "some log informations")
  return 0
}
value=$(testedMethod)

value contain only "the result" and when I use it in a script I'm only interested in "the result".
But it's not possible to assert only the stdout. It should be possible to assert separatly stdout and stderr.
That's why I propose this update.
In order to keep compatibility I juste add variables :

stdout: Only the stdout output
stderr: Only the stderr output
stdlines: stdout by line
errlines: stderr by line
output: Contain stdout+stderr concatenated

Any chance to see that PR merged?

This repository is not actively maintained anymore, see a discussion here: https://github.com/sstephenson/bats/issues/150#issuecomment-395835936
Try https://github.com/bats-core/bats-core

Good to know. What a pity it's not explicitly mentioned at the very beginning of the README.
Thank you @xmik

There are already at least 2 PRs trying to accomplish just that (to update README): https://github.com/sstephenson/bats/pull/248 and https://github.com/sstephenson/bats/pull/269 but no success so far


Line Break for „Global Note“

Hi WOK,
As already discussed, it would be nice if the „Global Note“ field (which is sticky now :-)) would support line breaks because we would like to note a longer text as some guideline for the meeting.
Even if the long text is completely visible in the email, it would be good so see the text also completely in the minutes so it is easier to update it.
Maybe after this change it would be reasonable to be able to collapse the field like the "Participants" list because it might "waste" a lot of height?
Best regards, Christoph

I must second this. Love the system, but this is one of the issues I've faced. I use the Global Notes to send out instructions of what to prepare for the meeting and what I need sent to me before hand. Being able to use Markup and mutli lines on the global notes would be a huge help :)

As a moderator I want to have multi line "Global Note" so that I can distribute even more complex meeting rules and notes.
Acceptance Criteria:

Field should be initially 2 lines in height
Pressing ENTER in this field will add a line
If user adds more lines, the hight should increase
Line breaks should be preserved in: browser, eMail and generated PDFs, finalized meetings
TAB should allow to leave field. Latests in this case changes shall be stored to database (and be propagated to other connected users)

Hint: The "Add Info Item" dialog has a "Details" multi line text area that grows automatically in height.


Angular msal 2.0 forgot password did not work

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
I have tried angular 11 b2c project which you provided. I have used same credentials which you provided in sample but forgot password is not working. it redirecting to login page itself.
I have also tried with my credentials but it redirecting to change password instead of redirecting to forgot password.
Source
 let resetPasswordFlowRequest = {
            scopes: ["openid","profile"], // I have tried with openid
    authority: environment.b2cPasswordReset,
  }
  this.msal.loginRedirect(resetPasswordFlowRequest);

same b2cPasswordReset url is working in msal 1.0 but not working in msal2.0
@jo-arroyo  could you please let me know if I am doing something wrong.

@jitendraP-ashutec Can you please share what the value of environment.b2cPasswordReset is?

@jitendraP-ashutec Can you please share what the value of environment.b2cPasswordReset is?

@jo-arroyo   Thanks For response. It was my mistake. I am passing wrong passwordReset URL.
    this.broadcastService.msalSubject$.subscribe((result: EventMessage) => {
        if (result.error instanceof AuthError){}
     });

In Sample code you checked instanceOf AuthError but it is not working.

@jo-arroyo   Thanks For response. It was my mistake. I am passing wrong passwordReset URL.
    this.broadcastService.msalSubject$.subscribe((result: EventMessage) => {
        if (result.error instanceof AuthError){}
     });

In Sample code you checked instanceOf AuthError but it is not working.

I was using wrong wrong url in password resetting so that its was not working.
Thanks @jo-arroyo


[NCLSUP-268] Enable Scp-like urls to be created

All Submissions:

[ ] Have you added a note in the CHANGELOG wiki for your change?
[ ] Have you added unit tests for your change?

Thanks @dominikbrazdil for the changes! They look good.
Could you please run this to fix the CI failure (it's due to code formatting):
poetry run tox

# yeah run it twice
poetry run tox

Don't worry if it fails the first time. That should make the CI happier and I'll merge it. I've also taken an action to add a unit test for this. Stupid me didn't add it in the original PR.

@thescouser89 Thanks for the review and the advice :) I'll checkout the test and fix this PR

Hi @dominikbrazdil ! Scp-like urls are identified by that : with no port after and not the git@ protocol. It's technically not even URL so I am not sure if urlparse is sufficient. In Orch I've had to write a custom parser because of that.

Oh, I see @michalovjan, I thought that the ":" is connected with the url not having any protocol (therefore starting with git@). I will remake the check for the collon as well. Thanks for noticing

LGTM! THanks @michalovjan  for the extra :eyes:  for the review! :)


nhcb: unit test framework to automatically generate custom histogram series from classic histogram series

Proposal
Depends on:
#13486
#13487
If the unit test has this kind of definition:
load 5m
	testhistogram2_bucket{le="0"}	 0+0x10
	testhistogram2_bucket{le="2"}	 0+1x10
	testhistogram2_bucket{le="4"}    0+2x10
	testhistogram2_bucket{le="6"}	 0+3x10
	testhistogram2_bucket{le="+Inf"} 0+3x10
	testhistogram2_count{} 0+3x10
        testhistogram2_sum{} 0+3x50

Then automatically create and store a custom histogram series called testhistogram2.

Yes, that is a good idea. Maybe there should be some parameter to (de-)activate the behavior, but we can try without it and see if any problems are happening.
A scenario could be if somebody wants to create a normal native histogram called testhistogram2 in the same test as the classic histogram above. Maybe we only create the NHCB implicitly if there is no series with the corresponding name already?

completed


Fix always zoom in animateCamera and moveCamera #14

Alternative fix might be to change how we convert the argument in Map.js, this line is the underlying issue:
cameraPosition.target = common.convertToPositionArray(cameraPosition.target);
I didn't want to change Map.js because that could break something in iOS. I feel like this is a design choice of the plugin that you @wf9a5m75 are more suited to make. Feel free to throw away this PR and change Map.js if you feel that's a cleaner solution

Thank you for sending a pull request. I will check it tonight.

Thanks. I fixed this issue in the Map.js. But your inspection saved my time.
https://github.com/mapsplugin/cordova-plugin-googlemaps/commit/8b5fe7386e2a383bab6bbc5f94d13bb1e0308408


restrict keyword error with cpp

I get the following errors when compiling as part of a cpp project. I believe the solution is to either remove the restrict qualifier from the header definitions, or conditionally define it out. (similar issue as here: https://github.com/Cyan4973/xxHash/issues/88)
base85/base85.h:47:32: error: expected ',' or '...' before 'dest'
 char* bintob85( char* restrict dest, void const* restrict src, size_t size );
                                ^~~~
base85/base85.h:54:32: error: expected ',' or '...' before 'dest'
 void* b85tobin( void* restrict dest, char const* restrict src );

My current workaround:
#define restrict
#include <base85.h>

Are you sure this issue concerns this Swift library? Based on the function names, I think you may have meant to create an issue on this repository instead: https://github.com/rafagafe/base85

You are correct!


Player right / left click sensor

Describe your idea
Something with the goggles, maybe an event with the AR controller, or an item that detects when the player wearing them right / left clicks.
If this gets implemented I'd be able to make interactable features the the Hologram API.
Floating chat bubbles, holographic control panels, anything!
Describe alternatives you've considered if you've any
Advanced monitors touch screen :(
Additional context
No response
Linked Issues
No response

I think implementing something like OpenPeripheral's Wireless Keyboard could be nice for that, allowed interaction with the goggles


Skaffold dev fails due to git clone timing out

When I run skaffold dev in the substra-backend repo, I have the following error:
Step 8/16 : RUN pip3 install -r requirements.txt
 ---> Running in e5731adf43f3
Collecting git+git://github.com/hyperledger/fabric-sdk-py.git@df19cf51ff4f21507869184901988c094658367a (from -r requirements.txt (line 31))
  Cloning git://github.com/hyperledger/fabric-sdk-py.git (to revision df19cf51ff4f21507869184901988c094658367a) to /tmp/pip-req-build-ydgheoes
  Running command git clone -q git://github.com/hyperledger/fabric-sdk-py.git /tmp/pip-req-build-ydgheoes
  fatal: unable to connect to github.com:
  github.com[0: <IP_ADDRESS>]: errno=Connection timed out

ERROR: Command errored out with exit status 128: git clone -q git://github.com/hyperledger/fabric-sdk-py.git /tmp/pip-req-build-ydgheoes Check the logs for full command output.

I am on Ubuntu 18.04 (inside a VM).
When (outside of substra-backend repo) I run:
git clone git://github.com/hyperledger/fabric-sdk-py.git it also fails (Connection timed out).
But
git clone https://github.com/hyperledger/fabric-sdk-py.git works.

It may be a issue from github ? Can you retry it later ?

@RomainGoussault  Do you still have an issue ?

I tried again today, and I don't have the timeout anymore.
Magic !


Update to remove redundant parts of documentation.

Hi Son,
please confirm that this pull-request is part of #63.
Thank you,
Thomas


Add DataStoreS3 and IOThreadPool

What problem does this PR solve?
Issue Number: ref #6827
What is changed and how it works?

Port DataStoreS3 from cn_mvp branch.

Interface linkDMFile is deprecated and removed. @lidezhu

IOThreadPool is ported too because DataStoreS3 depends on IOThreadPool to upload/download files concurrently.

Number of thread in cn_mvp branch is hard code and looks a little random.
This PR add a configuration: profiles.default.io_thread_count_scale which means the max number of thread of IOThreadPool is cpu_logical_cores * io_thread_count_scale. Default value of io_thread_count_scale is 5.0.

TODOs:

[ ] DB::DM::Remote::Manager which manages DataStore object is not ported in this PR because it depends on DB::DM::Remote::LocalPageCache.

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-unit-test

/run-all-tests


[BUG] Major inconsistencies between Java client and OpenSearch API

What is the bug?
Many API's are broken and unusable using the client due to the fact that the auto-generated code is relying on a later Elasticsearch version where the API has changed since 7.10.2
How can one reproduce the bug?
run
GetSnapshotResponse getSnapshotResponse = javaClient().snapshot().get(g -> g.repository(“test-repository”).snapshot(“test-snapshot-5"));

fails with:
error: Missing required property ‘GetSnapshotResponse.total’

what is this field total?
see it here in the elasticsearch docs version 8:

total (integer) The total number of snapshots that match the request when ignoring size limit or after query parameter.

Notice that the param is missing from the response body in same docs page in version 7.10
What is the expected behavior?
A valid response with no errors
This is causing the client to be impractical for use in production from our standpoint. as it seems to be auto-generated from an incompatible Elasticsearch client!

Thanks @MarinaRazumovsky for finding these issues 💪

PS: This is not just opensearch-java issue but covers all clients fleet.

Thank you @reta for the quick response, I was led here by the docs. And we wish to use the official client.

fixing the APIs which people use and report inconsistencies with

Currently, that list is long. We can fix some, but it seems like a futile task since the base code needs to be taken from a client that is compatible with elasticsearch 7.10.  And then we would gladly build on top of that.


Fix rewrite regex to match the start of the URL and not a substring

fixes #294

This change is

Coverage increased (+0.04%) to 45.932% when pulling 77221b3555d50a1e442c5d24259cf662e3e4a34d on aledbf:fix-rewrite into 3d9f89be1d17ca7e6df58d86978c1cab7467b0a3 on kubernetes:master.


docs(de): translating docs to German

Whole docs are now translated to German

@all-contributors please add @nobkd for docs


Laravel 5.6.24 - Passing array or separate parameters to eloquent ::where() creates different sql query

Laravel Version: 5.6.24
PHP Version: 7.1
Database Driver & Version: PostgreSQL 10.3, compiled by Visual C++ build 1800, 64-bit

Description:
Eloquent's database where(); method returns different queries when it should not.
This causes problems when applying query/model caching mechanism as, well, the queries are different.
where(); should return SQL the same in both the use-cases of passing separate parameters or an array of parameters.
Steps To Reproduce:
The following two queries produce different SQL statements:
$users = DB::table('users')->where('id', 1)->get();

Gives:
select * from "users" where "id" = ?

While
$users = DB::table('users')->where(['id' => 1])->get();

Gives:
select * from "users" where ("id" = ?)

The query is essentially the same, as is the output, but the second query is encapsulated while the first one is not, meaning this would not match a cached result and it will continue to actually query the database.
This should produce the same query so you won't miss cached queries.

The encapsulation of arrays is intended behaviour. Take a query like this:
DB::table('users')->orWhere(['a' => 1, 'b' => 2])->where('c', 3)->get();

select * from "users" where ("a" = ? or "b" = ?) and "c" = ?

I would argue that this is the expected SQL. Without the encapsulation, the query would return a different result (AND has precedence over OR).
As you said, the queries are "essentially the same", but not exactly the same.

I think the argument here is that encapsulating a single condition is pointless and interferes with caches.
The fix would be to only encapsulate the condition if the condition array has more than one element in it.
DB::table('users')->where(['id' => 1, 'active' => 1])->get();
// select * from users where ("id" = ? AND "active" = ?)

DB::table('users')->where(['id' => 1])->get();
// select * from users where "id" = ?

I don't think it's Laravel's job to check the array length.

@staudenmeir at first that makes sense, but if not Laravel, who else is going to check the queries for this optimisation?

@hyperized The developer?
I'm struggling to see a legitimate use case where you would routinely be making the same query, but passing your filter as an array only some of the time.

Thanks for responding @staudenmeir, @36864, @hyperized
@staudenmeir Going by what you stated, I wouldn't see a problem with encapsulating both of the clauses.
It's not about how you write your PHP statements, placing a orWhere before a where with or without arrays.
I would vote for encapsulating all the time, essentially writing the following:
DB::table('users')->orWhere(['a' => 1, 'b' => 2])->where('c', 3)->get();

Would produce:
select * from "users" where ("a" = ? or "b" = ?) and ("c" = ?)

This would suffice.
@36864 I think that it would be the other way around. Both queries are valid SQL, but in the line of what Eloquent currently does, and that is encapsulating an array of parameters, I would vote for doing the same with separate parameters only.

Also, @staudenmeir , As you said, the queries are "essentially the same", but not exactly the same.
Well, in the stated use-case one could argue that they are the same ;-).
But, it shouldn't depend on how you pass your arguments to your method call, should it?

@Caroga If you use where() in different ways (multiple parameters vs. array), you can expect the same query result. But I would argue that you can't expect the generated SQL to match exactly.

If it can be done without a significant impact on performance, I don't see a strong argument against encapsulating everything.
I can imagine some people's tests would break if they're explicitly checking sql query strings, so I wouldn't submit the change on a point release.
Then again, this might all just be going through a lot of unnecessary work for the sake of a (presumably) rare use case that could be solved by the developer just checking inputs.

If it's a minimal effort fix, it would potentially save up to 50% in any caching layer, such as model caching (https://github.com/GeneaLabs/laravel-model-caching for example) or even on the database layer itself (which also can contain a query cache). I don't think it's such a rare use-case, and a potential big win.

I didn't mean that caching is a rare use case.
I meant that using ->where('field', $value) and ->where($filter), with $filter being a single-element array in the same context isn't something I see very often.

So, closed, no final argument as to why, just closed? Great action. :+1:

@Caroga I think because its not a bug, please open issue in internals https://github.com/laravel/ideas.
You see, many people get notifications because of this issue and since its not a bug it should not be here.

Thank you @Kyslik for clearing that up. Knowing this makes me understand of the situation. I will continue and forward this "issue" to the appointed ideas section.
I will make sure to focus on the intention to always encapsulate.
Thanks. :+1:


Added Platforms to learn cyber security

I had a list of platforms where I tried to learn Cyber Security. After I saw that there is a pretty useful awesome cyber security repo, I decided to contribute to it .

Some links to the platforms are not yet provided, they will be added soon, and with more platforms, if pull request will be accepted. Btw, thanks for your and others work in this repo!

Hello buddy,
Thanks a lot, your contributions seem real nice! I will accept the pull request now, thanks for helping us to keep on learning.


Show “all cloud perspective” only when cloud provider is available

Refactored the overview and cost explorer perspective to ensure:

A perspective option is shown when there is an associated source provider.
An empty state is shown if the source provider does not have data.

https://issues.redhat.com/browse/COST-1934
Overview

Cost explorer

Codecov Report

Merging #2266 (c3add06) into master (56d33ee) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2266   +/-   ##
=======================================
  Coverage   70.46%   70.46%
=======================================
  Files         400      400
  Lines        7406     7406
  Branches     1624     1624
=======================================
  Hits         5219     5219
- Misses       2155     2159    +4
+ Partials       32       28    -4

Impacted Files
Coverage Δ

src/components/pageTitle/pageTitle.tsx
15.55% <0.00%> (ø)

src/components/charts/costChart/costChart.tsx
10.76% <0.00%> (ø)

...omponents/charts/dailyCostChart/dailyCostChart.tsx
9.09% <0.00%> (ø)

...nts/reports/reportSummary/reportSummaryDetails.tsx
13.26% <0.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 56d33ee...c3add06. Read the comment docs.


Fix default values for acr

The previous PR was merged too quickly to notice this.

Firstly, the default Comparison value for SAML2int should be exact.
Secondly, as I discussed with @jkakavas , it does not make much sense to have a default class_ref value. It is the vital part of the acr_mapping configuration and it is mandatory that it is provided. If no value for class_ref is given this should fail by producing a KeyError exception.

Sorry, I should give some PRs more time to be discussed.


Add documentation for Kerberos Authentication mode

This PR adds documentation for the new Kerberos authentication features in ES-Hadoop.

Nice work @jbaiera, this is quite comprehensive. Do you know if these instructions work against Elastic Cloud and ECE? Also, this is quite long, would it make sense to split out the setup for different Hadoop components into separate pages?

Thanks @acchen97

Do you know if these instructions work against Elastic Cloud and ECE?

I'm not sure if Kerberos authentication is applicable in Elastic Cloud since that is a hosted service and I'm not sure how one would set up a Kerberos realm from within it. For ECE I don't see why this wouldn't work if you were deploying on prem, or if you were hosting Kerberos within the same cloud distribution. I would defer to the ECE team on that.

Also, this is quite long, would it make sense to split out the setup for different Hadoop components into separate pages?

Once this is compiled in the docs project, the pages will be broken out by their components:

The structure looks great, thanks @jbaiera. :+1:

Resolved most of your points on the docs layout and contents @jakelandis. Would like your feedback on the changes in the Hive chapter to see if the new user impersonation setup steps make sense/are easy enough to follow.

@jakelandis Are we good on the edits for this?


arrow view bug

There is an unused arrow on the top right.
I tried to make the arrow invisible, but I can't access the view.

If you don't want to show the spinner, try the below attribute.
expandable_showSpinner="false"

Btw, the screenshot which you provided seems weird. (There are duplicated spinners)
Does your parent & child view have arrows?.


Setup RBAC

Setup RBAC auth with information in the session object using Next-Auth https://next-auth.js.org/tutorials/role-based-login-strategy

pr: #46


Search by skills

In the volunteers management, it's useful to be able to search by skills a volunteer has / do not have.

Example: "Find all volunteers that are neither US or AS" (exhaustive query, as we use DQL in the app):
select * from (
  select nivol, first_name, last_name, group_concat(label) as tags
  from volunteer v
  left join volunteer_structure vs on v.id = vs.volunteer_id
  left join volunteer_tag vt on v.id = vt.volunteer_id
  left join tag t on t.id = vt.tag_id
  where vs.structure_id = 1 /* UL 1/2 */
  group by nivol
) t
where find_in_set('social_assistance', tags) = 0
and find_in_set('emergency_assistance', tags) = 0;```

duplicate of #263


Year in footer should be dynamic

Bug Report
Description
[Provide a clear and concise description of the bug.]
Steps to Reproduce
[Outline the steps to reproduce the behavior:]

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected Behavior
[Describe what you expected to happen.]
Actual Behavior
[Describe what actually happened.]
Screenshots

Environment

Operating System: [e.g., Windows, macOS, Linux]
Browser: [e.g., Chrome, Firefox, Safari]
Version: [e.g., 22]

Additional Information
[Any additional information or context that might be relevant to the issue.]

Hello @chandel-aman please assign this issue to me under gssoc 24

Can i work on this issue? @chandel-aman


Clean up

Remove dead code
Remove duplicate code
Replace with more readable code

Will re-submit another PR.


ONNX support

Hi, guys.
How does MMdnn relates to ONNX?
Do you guys use it as IR or have plans for that?
Thank you

Hi @pliniosilveira,
ONNX support is in our plan. For IR, our ops are similar but still have some difference.

That means the current IR will be abandoned sooner or later or somehow they may coexist?
Or maybe you didn't stop to think about it yet?

In our plan, onnx will be treated as other framework, with the parser and emitter. And we may refer the ONNX ops' defination to refine ours.

Will there be an update with this soon?

Hi @BenPYeh, we have implement the onnx support now.Try the newest code. Thanks!


Cannot make inscriptions because ord indexer never finishes.

System information:

ord 0.4.2 (also tested on the latest version of Ord)
Ubuntu 22.04
Bitcoin Core 24.0, using cookie authentication and txindex=1
16 GB RAM, 8 threads

Problem:
I ran ord wallet inscribe, and it started indexing the blocks on my node. However, indexing became progressively slower until it stops completely, sometimes on block 300,000, other times on block 370,000, or somewhere in that region.
If I interrupt the program and start again, it will never print any output (even in debug mode) or resume indexing.
Most recent log messages:
# ...I had to trim the beginning because it only consisted of dozens of messages similar to below.
[indexing blocks] ███████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 368627/778665[2023-03-02T04:27:21Z ERROR ord::index::updater] failed to fetch block 368660, retrying in 2s: JSON-RPC error: transport error: HTTP response too short: length 0, needed 12.
[indexing blocks] ███████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 369254/778665[2023-03-02T04:44:47Z ERROR ord::index::updater] failed to fetch block 369287, retrying in 2s: JSON-RPC error: transport error: HTTP response too short: length 0, needed 12.
[indexing blocks] ███████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 369259/778665[2023-03-02T04:45:35Z ERROR ord::index::updater] failed to fetch block 369292, retrying in 2s: JSON-RPC error: transport error: HTTP response too short: length 0, needed 12.
[indexing blocks] ███████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 370000/778665

How much memory does this take in total? As mentioned I have 16 GB of RAM but I run a lot of stuff on this box so I tend to be on the "almost full" side of my memory usage most of the time.
On Thu, Mar 2, 2023 at 7:26 PM, lepar @.***> wrote:

You first have to index all the satoshis using Ord
RUST_LOG=info ord --index-sats index
Took me 7 days for it to finish. It indexes ALL satoshis, more than 1.9 quadrillion. It creates a index.redb file in the ord directory and it's currently at 118gb (apart from the 500gb bitcoin blockchain
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Memory doesn't take much, I have 8gb. It takes alot of storage space though. The bottleneck is that it indexes ALL 1.9 quadrillion satoshis on a database, that takes time to do
index.redb - 118gb
BTC Blocks Folder - 513gb
BTC indexes folder - 41gb
BTC chainstate folder - 5gb

I ran the command you pasted now. 5 minutes have passed and I see CPU and memory activity obviously coming from ord but it's not printing anything useful in info or debug levels past "Connecting to bitcoin RPC Server at ..." (which it does, but some additional verbosity would be very helpful here.)

Message ID: @.***>

Maybe it has something to do with my indexer being half-finished?

Are you running a bitcoin server with the index option?
"bitcoind -txindex"
It takes time, it'll give a few errors now and then too, and warnings. You have to have everything synced and indexed first before inscribing.
I suggest you delete the index.redb and restart it with --index-sats flag. It'll go fast until block 300k then it'll slow down cus alot of transactions starts appearing

can we close this?

can we close this?

Yeah, sorry about that. Forgot about this thread to be honest.


Clean up #1271

Due to my trigger-happy fingers, I merged #1297 pre-review. We should do some final tweaks and write specs for both fixes in #1271 (the spaces in headers and the invalid character parsing) to ensure that everything's working as expected. Sorry!
To Do:

[ ] fix extra spaces in error message
[ ] double check instructions for spaces in example CSV
[ ] double check that UTF-8 encoding command is actually happening
[ ] write specs for both header spaces and UTF-8 invalid character parsing
[ ] switch checking for whitespace and raising an error with just parsing out any whitespace in the header row

Just left some inline comments in #1297, refer to those for feedback. Thanks!

Based on the last set of comments in #1297, I've added the parsing of whitespace out and removing the error message we just added to the to-do list above.


Resolve issues with empty protobuf argument.

Comply with GRPCException constructor signature when rethrowing Inv…
Prevent "Google\Protobuf\Internal\Message::mergeFromString() expects parameter 1 to be string, null given" when body is empty for empty proto argument.

Example Proto - ListTask is the culprit
syntax = "proto3";

package demo.service;

import "google/protobuf/empty.proto";

service ToDo {
    rpc AddTask (Task) returns (Task) {
    }
    rpc ListTask (google.protobuf.Empty) returns (ListTaskResponse) {
    }
    rpc CompleteTask (CompleteTaskRequest) returns (Task) {
    }
    rpc GetTask (GetTaskRequest) returns (Task) {
    }
}

message Task {
    string id = 1;
    string label = 2;
    enum TaskState {
        PENDING = 0;
        COMPLETED = 1;
    }
    TaskState status = 3;
}

message ListTaskResponse {
    repeated Task tasks = 1;
}

message CompleteTaskRequest {
    string task_id = 1;
}

message GetTaskRequest {
    string task_id = 1;
}

Thank you. We are currently on holiday break but I'll check this issue once back. The fix seems ok but something wrong with the code-style checker. I need to fix it first.

@YamenSarah can you please address the code-style issues? You can run vendor/bin/spiral-cs fix src to fix the codebase.

I'm not sure which is better.. checking if body is empty or checking if $in is an empty message?

$body !== null is OK

PHP 7.1 is dying, but we are going to bump the dependency to 7.2 anyway. Thank you for the PR.


Adding external javascript script to React failed!

I'd like to include & run some js file in the React using Helmet component. Here is the simple code:
index.js:
import React from "react";
import ReactDOM from "react-dom";
import { Helmet } from "react-helmet";

import "./styles.css";

function App() {
  console.log("op");

  return (

      <Helmet>

 </Helmet>

it works!
Why doesn't  the external js file work?

Hi,  @Mulligan81 !
For you resolve this problem, you can move the your project files from "src" folder to "public" folder. You can move or copy !
Good Lucky !


Bug: TEE Data - Update default display for 'Quarter'

Issue:
When a user wishes to create TEE Data in the QA Module, then the Quarter field by default displays the option 1 instead of 'Select a value'
Steps to Recreate:

Login to ECMPS and access the Cert Event and TEE Module
Select and checkout a Configuration and click on Add for TEE data
You will notice that the selection for Quarter has been defaulted to 1 instead of Select a value

Bug fixed


Windows Installer Error

@lufre1 @constantinpape
I could reproduce the error we spotted here: https://github.com/computational-cell-analytics/micro-sam/issues/381 (also reported by @Sagnik700) and found a fix to it as well.
TLDR: error encountered - RuntimeError: Freetype library not found (detailed error report sent to @lufre1)
Fix:

Put the freetype.dll library file to .\micro_sam\Scripts\ from here
i. Unzip the installed freetype.zip's freetype.dll to the above mentioned folder
Rerun the script from command line:.\micro_sam.annotator_2d.exe -i ..\<IMAGE>.tif -m vit_b. (IT WORKS!)

Would it make sense to find a way to add the missing library in the windows installer?

I would suggest adding the .dll file to the installer. There might be an alternate solution to download the .dll when the installer is executed. I will check how reliable each solution is. Also, I will check how reliable downloading the .dll file during build or during install processes is.

@lufre1 The latest windows installer works seamlessly (tested it for 2d annotator using command line). Thanks!
A few mentions (not sure if they are because of my system or something regarding the installer, would leave the mentions anyways)

While the installation happens, the step for "Setting the package cache" takes a very-very long time
Once all the installations are done, the step for "Clearning the package cache" takes an equally long amount of time

PS: My system config is - WIndows 10 Pro, Intel i5 7th Gen, 8GB RAM (has HDD disk storage)

The post_install.bat and the reference to it in construct.yaml is missing. This might cause the error reoccurring again


Update test.tex

If the message below is truncated, see https://ci.appveyor.com/project/yihui/latex-pass/builds/44295776 for the full version.


Format and check format quality in CI

Closes #49.

Coverage decreased (-0.02%) to 95.727% when pulling 3b815824b18cb1e9b249d344c975c7d4e8e3c045 on sheharyarn:sn/formatter into 04a437e54ee1fbb6ed507015360b7bdd71db0b62 on bernardolins:master.

Hey @bernardolins, can you please try running Travis job 260.4 and 260.7 manually again? It seems like a random error where the port was already in use. (Unlike #50, this PR formats code in a way that is valid on older Elixir releases as well).
As for the coverage, not sure why it says decreased when in fact there has been no change. From the details, it looks like it's the percentage is dependent on LOC, which makes sense because they've been increased as a result of formatting the code.

Hi @sheharyarn,
Those tests are not good at all. I executed the jobs again and now they are all green, thank you for your help!
I think you are right about the coverage, the calculation is based on the LOC number. That's not a problem :)


ACME challenge bug

I just deployed v1.1.0-rc3 with single LE certificate for ~10 domains. At first it had problem with validating one domain for some time:
time="2016-11-07T09:06:34Z" level=debug msg="Challenge GetCertificate redacted.com"
time="2016-11-07T09:06:34Z" level=debug msg="ACME got nothing redacted.com"

This domain had live traffic, that cannot be stopped.
After a while (minutes) it validated and created certificate. But I still see this in log appearing every few seconds even after restarting traefik:
time="2016-11-07T09:43:32Z" level=debug msg="Challenge GetCertificate redacted.com"
time="2016-11-07T09:43:32Z" level=debug msg="ACME got domain cert redacted.com"

@OndroNR We need a bit more details on your config: TOML file, and all you DEBUG logs.

I hope it will help. Log is from few minutes of already running https://gist.github.com/OndroNR/5273d5b02d6ef01fd1e2e711baa2e5a8

Had the same problem. After a few tries (changing the requested host name via the frontend rule) it validated successfully.
LE is probably having intermittent problems: https://github.com/letsencrypt/boulder/issues/1217

I'll close the issue due to inactivity but feel free to re-open if needed.

@ldez - I too am having this issue. The slack invites are either not being sent out or are being sent out slow. Shall I create a new issue with detailed information or can you reopen this one and I'll put the logs and what not here?

Ok, this appears to be due to lack of [[acme.domains]] and/or me using onHostRule instead of OnHostRule (not sure which change fixed it). The documentation conflicts...one part has an example with OnHostRule (https://docs.traefik.io/user-guide/docker-and-lets-encrypt/), another has an example with onHostRule (https://docs.traefik.io/configuration/acme/). Also, is [[acme.domains]] required?

@cretz [[acme.domains]] required only if you want provide SANs.

@ldez - how about the OnHostRule/onHostRule inconsistency...or whether https entrypoint has to be setup on a frontend for the cert to be created?

Thanks for your interest in Traefik 😃
This issue is closed. Please discuss this in :

the Traefik community Slack channel


Small request: Add Golem topic to repository

Hello!
It would be much appreciated if you could add the topic golem to the repository!
That would mean people could find all the awesome projects by just exploring the topic golem here https://github.com/topics/golem, and hopefully create a little bit more exposure for this awesome project! :heart:
There will be a settings wheel on the right side of the screenshot if you head over to your repository's main page, click that and you should see the option to add a topic.

@cryptobench Thanks :)
I didn't see the topic last time I edited the repo, I used golem-network which appeared in the suggestion list given by Github.
But golem is in fact the one that seems to be used on the official Golem repositories. Updated 👍
Thanks again!

@cryptobench Thanks :)
I didn't see the topic last time I edited the repo, I used golem-network which appeared in the suggestion list given by Github.
But golem is in fact the one that seems to be used on the official Golem repositories. Updated 👍
Thanks again!

No worries bud! Thanks for taking your time to add the topic :heart: 👍 !

No worries bud! Thanks for taking your time to add the topic :heart: 👍 !


PLOT/GRATICULE interacts with PPL PEN 0

Reported by ansley b manke on 13 Jan 2011 17:39 UTC
Reported on the Users List:
http://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2010/msg00795.html
I wanted to thicken the plot using "ppl pen 0,7". This is not effective in combination with the mode GRATICULE or plot/grat option. But i need plot thickening as well as graticule. Jnl file and Figure as follows.  Hope somebody will repond, who overcame this problem.  Thanks in advance.
NOAA/PMEL TMAP
 FERRET v6.05
 Linux(g77) 2.4.21-32 - 07/27/07
 13-Jan-11 14:25

ppl pen 0,7
use coads_climatology
plot/line/thickness=2/vgrat=(line,color=blue)  ssty=15
The plot has thickened lines on the vertical axis and most of the labels, but the horizontal axis lines and labels are drawn with a thin line.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1787

Comment by steven.c.hankin on 13 Jan 2011 20:36 UTC
There are many examples of manually specified PLOT+ commands that are over-ridden by Ferret's automation.  The work-around that (I think) is discussed in the Users Guide (somewhere) is to use the /SET_UP qualifier.  Does that not apply here?
use coads_climatology
plot/SET_UP/line/thickness=2/vgrat=(line,color=blue) sst[y=15](x=60,)
ppl pen 0,7
ppl plot

Comment by ansley.b.manke on 13 Jan 2011 20:49 UTC
No, this does not work here, but still reproduces the buggy plot.  The graticule setting is overriding the thick pen that's been requested by PPL pen 0,7.  The standard thin pen is being substituted, only for the horizontal axis where the graticule lines are drawn.

Comment by ansley.b.manke on 24 Aug 2016 00:08 UTC
This is fixed; it applies to Ferret only, not Pyferret, though code changes were merged to the Pyferret branch.


View-maximize failure with Vertical File Tabs

Hi.
I'm a newbie about atom, but now I'm a junkie of atom and this wondorful plugin.
So, my problem is:
with following "Vertical File Tabs in Atom" style,
Terminal-Plus's maximize/normal view changing doesn't work correctly.
Vertical File Tabs in Atom
https://gist.github.com/jasesmith/114da4e5310eda6238f0

Atom Version: 1.1.0-beta.0-ad60d7b
Terminal-plus Version: 0.11.1
OS: Ubuntu

@suzetmk Thank you for reporting this. I'll take a look and notify you once I release a fixed version.

I had a chance to look at this, so I'll explain what is happening:
Terminal-Plus is displayed as a panel attached to the bottom of Atom. In the same plane is the section containing the tab-bar view. Atom prevents the section containing the tab-bar from shrinking below the size to display the tab-bar. This results in Terminal-Plus being stopped at the last tab in your tab-bar view. Terminal-Plus will continue to grow because it thinks it has more room (and it does). That causes the bottom of the editor to be pushed down out of sight. Not much I can do about this since this is related to how Atom displays sections of the editor.
You might want to check out issue #9. They are requesting that tabs be implemented, which would let you effectively "full screen" your terminal. If this interests you, you can comment there and I will notify everyone once an update with tabs has been released.

Thank you for your quick reply.
Yes, terminal-plus as tab should be best resolution for me.
Please continue implementation for issue #9.

No problem, closing this issue as it is being handled by another issue.

I'm so sorry, but I had a misundersanding about what you mentioned of "terminal as a tab"...
I tried tab feature and it seems to be really nice, but unfortunately didn't fit to my use case.
I prefer to use terminal-plus with small size normally,
and to maximize/re-contract it on demand, with keeping current jobs.
(In addition, it will be nice if I can toggle maximize with command)
I tried those operations with tab-terminal and atom's pane splitting/resizing commands,
but that was really complicated...
So, I think that if I can toggle teminal between tab and bottom-tool-panel with command,
that could be an alternative for me.
Could you check to see if it's possible?

One more request,
It would be nice if atom's active tab is restored to last one
when activated terminal-tab is switched to botom-tool-panel in above use case.

@suzetmk I have been planning on replacing the default full screen with this tab view mode. A command for toggling "fullscreen" can be added with this update. That way you could toggle between tab view and bottom panel view.

One more request,
It would be nice if atom's active tab is restored to last one
when activated terminal-tab is switched to botom-tool-panel in above use case.

Just to clarify, should the focus return to the previous active tab or to the terminal? In this instance, in focus implies that your typing input would go to the item that is "in focus". The difference being is that I could have the previous active tab become the active tab while keeping the terminal in focus or the previous active tab would become active and take the focus from the terminal.
Sorry for the late reply! It has been a busy week.


Fix games run faster on non 60Hz screens

Games run faster on higher screen refresh rates.
It's somewhat difficult to play ;)

I'm running on 144hz and haven't seen issues.  I believe that's part of the game's code though.  They (the developer) need to restrict the frame rate.

Ah I see, that makes sense.
For reference you can see the speedup in Tackle Box, a fishing adventure.
There is the Forum link for this game.

Sorry to perform issue necromancy, but...
I'm experiencing this issue in both Firefox and Chromium. I've done all the necessary calls: calling arduboy.setFrameRate at setup and checking arduboy.nextFrame in my loop. The same sketch I've tested functions the intended way on 60hz displays and on real hardware. This speed is making debugging very difficult.
I don't believe this issue is on the sketch developer to fix, as even the "Arduboy" boot screen is too fast on my computer.


Hive climate component schedule an hour out in Home Assistant

I’m running HA 0.98.5 on HassOS 2.12 and have been having an issue with my hive integration (I use the basic integration (hive: in configuration.yaml).
What I’ve noticed is that everything works fine, I have some hive plugs and the thermostat, plugs all work fine (although I don’t use schedule) and the thermostat works fine e.g. it heats my home at the right time when temp is below target and schedule comes on.
What’s not right is how this is represented in HA, it seems to report schedule changes to the Hive component an hour after the actually happen whereas the actual temperature reports fine. I thought this might be a British Summertime issue, but where?
If you look at the screenshots from the history component you can see the issue. My schedule is as follows:
During the night (until 06:00) the temp is set to 19c
At 06:00 until 07:30 it is set to 21.5c
Then at night it turns back down to 19c at 22:30, you can see the target temp change occurs an hour late in HA but the actual temperature clearly shows that the heating has come on or gone off.
Puzzled, any ideas?

@captaindaveman,
I think I had this same thing a long while ago on a manual Linux installation of HASS, I am sure the solution then was that the timezone was not set correctly in the OS and using the following command resolved this issue:
sudo dpkg-reconfigure tzdata
Also, if you use add the custom component from my GitHub then you get a few more sensors which add more data to see heating and hotwater information.  You can then click on the Heating Mode or Hot Water Mode to check the current and next two schedules and see if the api library is picking the schedule up correctly.

(I don't have my heating turned on yet so I cant show a screenshot of the heating schedule)

@Rendili thanks for the quick response, the custom component looks great, a job for the weekend me thinks!
how do I run the code you mentioned on home assistant?
I think it is a difficult window to spot and fix this, as the timezone issue only appears for a short period when its offset by one hour and you need your heating on, the clocks change again next month so I need to fix it before then to be sure!

@captaindaveman,
sorry, but I don't know how you would go about doing this in hassOS or HASS.IO. From what I gather this OS is locked down and you I didn't think you could do something like that.
For my situation I used putty to get on to my Linux installation then just run that command

@Rendili unfortunately these don't work with Hass io. How is your custom component configured, does it use local time (from configuration.yaml) or system time (UTC)?

@captaindaveman I thought one of those was specific to hass.io and / or some links off of one was?
The custom component does not handle time directly, it just receives the time variables from the pyhiveapi library. There is nothing special going on in the library to manipulate the time for timezones.  If it needs a current time then it gets this from the context it is run, which with normal Home Assistant I believe comes from the OS timezone. Any timestamps from Hive it just stores and uses as is

@captaindaveman , in fact I think the Hive data when using datetime stamps now uses UTC everywhere, if this is the case then we will need to update the library to convert the Hive datetime stamps to local time


sorry ,I don't know which package the "import en"  from ?

Hello,MR.Deng! I'm very excited when I saw your project ,but I am a new student in NLP . So,ccould you give me some guidance ? I don't know which package the "import en"  from ?  Is it from nltk? But , I have installed the nltk3.4 package, and I download the corpus of the nltk.  It still doesn't work.

https://www.nodebox.net/code/index.php/Linguistics

Oh,thank you! I am in BIT. And I see you are in Tsinghua University. What a small world ! haha

Hi, @caoxu915683474, @Cppowboy , I changed the framework to a new version, it is much more powerful and easier to understand, you are welcome to take a look at it.


Docs: enumerate client/server port and process metrics

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

Project coverage is 51.00%. Comparing base (84148fe) to head (c44848c).

:exclamation:  There is a different number of reports uploaded between BASE (84148fe) and HEAD (c44848c). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (84148fe)
HEAD (c44848c)

oats-test
1
0

k8s-integration-test
1
0

integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1020       +/-   ##
===========================================
- Coverage   81.64%   51.00%   -30.65%
===========================================
  Files         137      137
  Lines       10936    10936
===========================================
- Hits         8929     5578     -3351
- Misses       1498     4976     +3478
+ Partials      509      382      -127

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
51.00% <ø> (ø)

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

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


rowClassname on table

Can you add the prop for table rowClassName from antd that let add classnames on row, like adding a different background in base of state

Hi @valesceva I don't see issues in adding this prop; if you are in a hurry feel free to submit a PR

I'll close this since it has been covered by https://github.com/mia-platform/design-system/pull/554


Making Makefile on Ubuntu gives error

sudo: dnf: command not found
Makefile:5: recipe for target 'install-dependencies' failed
make: *** [install-dependencies] Error 1

The dnf command is not recognised by Debian, instead using apt does the job. I hope that should work. @csomh @lachmanfrantisek .

I have locally built just the dashboard on my system to work on it. Will that be an issue ?

The make file is actually written for Fedora which uses DNF as it's package manager (next gen YUM), if I'm correct.

You are right, we use the dnf as a package manager -- we can fix this problem by:

Finding the right package manager.
Have a variable for that.
Use some general tool like ansible playbook with package module.

@lachmanfrantisek Can I take up this issue?

@lachmanfrantisek I have made a PR referencing this issue. If you could please review it.


@sentry/vue + @sentry/capacitor - attachProps, seems not to passed to Sentry

Environment
What version are you running? Etc.
 "@sentry/vue": "^7.69.0"
"@sentry/capacitor": "^0.15.1"
Steps to Reproduce

What
you
did.

I am trying to migrate from using @sentry/vue to @sentry/capacitor
@sentry/vue (current config)

@sentry/capacitor (something that I implemented based on the examples 🤔 )

Expected Result

with attachProps: true props are passed properly to Sentry

(screenshot of the logs with @sentry/vue)

@lucas-zimerman do you maybe see any obvious, wrong implementation here?
Actual Result
attachProps seems to have no results (no props attached inside sentry.io log report)
What actually happened. Maybe a screenshot/recording? Maybe some logs?
as described and presented above. I didn't find any examples of how to do it properly and the current approach seems not to work anymore.

I am sorry that you are experiencing issues integrating Sentry Capacitor with VUE, we'll investigate what's going on and give out a return shortly


Error while downloading SBERT and BERT error detector for FENSE metric

The module was installed with 'pip install aac-metrics'. The previous files were installed successfully.
Traceback (most recent call last):
File "/home/esanchez/miniconda3/envs/xac-ic/bin/aac-metrics-download", line 8, in
sys.exit(_main_download())
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/download.py", line 308, in _main_download
download(
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/download.py", line 125, in download
_download_fense(verbose)
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/download.py", line 246, in _download_fense
_ = FENSE(device="cpu")
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/classes/fense.py", line 49, in init
sbert_model, echecker, echecker_tokenizer = _load_models_and_tokenizer(sbert_model, echecker, None, device, reset_state, verbose)  # type: ignore
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/functional/fense.py", line 130, in _load_models_and_tokenizer
echecker, echecker_tokenizer = _load_echecker_and_tokenizer(
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/functional/fluerr.py", line 193, in _load_echecker_and_tokenizer
echecker = __load_pretrain_echecker(echecker, device, verbose=verbose)
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/aac_metrics/functional/fluerr.py", line 427, in __load_pretrain_echecker
echecker.load_state_dict(model_states["state_dict"])
File "/home/esanchez/miniconda3/envs/xac-ic/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1671, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for BERTFlatClassifier:
Unexpected key(s) in state_dict: "encoder.embeddings.position_ids".

It was due to the transformers version, my bad xd


Types folder missing when importing telescope modules from published npm package

hi, i've created telescope generated modules of our AssetMantle chain, the repo for which exists here. I've then published the package to npm here. On importing this npm package to my webApp, I notice that I'm unable to import the signing clients (getSigningAssetmantleClient) or any assetmantle modules. On investigating I found out that inside @kombos/telescopeexample folder in node_modules, there is no 'types' folder generated (see screenshot):

any ideas why the types folder is missing on publishing to npm and importing? tx.

https://github.com/kombos/telescopeExample/blob/60a9c10847c522580f2c8ca52cd819cf0b178569/package.json#L24
you should run yarn build:ts to create the types

fixed


Upgrade com.fasterxml.jackson:jackson-bom <IP_ADDRESS>21013 -> 2.14.0

This PR contains the following updates:

Package
Type
Update
Change

com.fasterxml.jackson:jackson-bom
import
minor
<IP_ADDRESS>21013 -> 2.14.0

[ ] If you want to rebase/retry this PR, click this checkbox.

Suggested commit message:
Upgrade Jackson <IP_ADDRESS>21013 -> 2.14.0

See


Cassava Leaf Disease Classification

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Cassava Leaf Disease Classification
:red_circle: Aim : The aim of this project is to identify the defected leaf using image processing methods.
:red_circle: Dataset : https://www.kaggle.com/datasets/nirmalsankalana/cassava-leaf-disease-classification
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hey! Hope you are doing well, I am interested in doing this project and would request you to assign this issue to me 😊
Thanks a lot!

Are you part of the SWOC event?
@VaishnaviMudaliar

Yes, I am a contributor at swoc

Hi @VaishnaviMudaliar please share your approach for solving this issue, what the models you are planning to implement for this project, do let me know here.

Hey @abhisheks008  i am interested in this project. should i mention my approach?

Hi @abhisheks008 , I am interested in doing this project and would request you to assign this issue to me. Thank you. Below are the requested details-
Full name : Arijit De
GitHub Profile Link : https://github.com/arijitde92
Email ID<EMAIL_ADDRESS>Participant ID (if applicable): N/A
Approach for this Project :

Exploratory Data Analysis
First I will download the data and check for corrupt images and remove them if present. I will also check whether the dataset has class imbalance or not. I will provide some report about the number of samples in each class.
Data preprocessing
Will find out the mean and standard deviation of the images so that I can normalize the data.
Data Splitting
The dataset contains five classes and they are not already divided into train/test sets (as given in Kaggle). I will divide the dataset into training/testing sets in the ratio 80:20 (will experiement with other ratios and see which is best).
Data Augmentation
Since the dataset is class imbalanced, training any deep learning model will cause biasness for majority class. Hence I will do data augmentation (rotation, scaling, flipping) to increase the samples of minority classes in the training set so that all classes have the same number of images.
Model Training
I will train the images with four different models - EfficientNet, DenseNet, MobileNet and SqueezeNet. Some are heavy models while some are lightweight models. I will experiment and see how each model performs. Will also experiment with pre-trained versions of the models.
Model Hyper parameters
I will also experiment with the model hyperparameters like learning rate, batch size and optimizer to find the best model.
Testing
I will test the model on the test set and apart from accuracy, will determine the precision, recall, sensitivity and specificity of the models.

What is your participant role? SWOC 24 contributor.

Issue assigned to you @arijitde92


Add ability to add JFrame as parent component

LWJGL can support JFrame as parent, but it is currently not used. Add an option to specify a target JComponent to add as parent.

Mentioned in https://github.com/liavt/Jumbo-Engine/issues/16