S1 extraction fixes - PR Re-opened

In this PR I re-open the changes brought and then reverted of the old s1-extraction-fixes branch.
Changes include (those can be ticked once validated here):
Miscellaneous changes

[ ] Fixes in the fetching module: now accepting CDSE-STAGING
[ ] Fixed load_collection parameters wrongly passed in the S1 fetchers
[ ] Added an hardcoded parameter for the CDSE S1 catalog to only query for VV & VH products. Otherwise, it would fetch for products only having VV or VH, causing a crash in the backscatter computation process.
[ ] New dataset uploaded to the artifactory for S2 tile job-splitting. As the original s2grid bounds contained S2 tiles unknown to the CDSE catalog. The new s2grid_bounds_v2.geojson file contains an additional column cdse_valid to filter out those tiles.

Job manager changes

[ ] Added a retry_on_exception wrapper for post-job actions, as internal openeo exception can disrupt the extraction process.
[ ] Dynamic job scaling: By default disabled, it allows to change the property parralel_jobs depending on the running time of the manager. Useful feature but a bit complex, I'm not using it in-fine for the WorldCereal project so personally I don't mind removing it.
[ ] Use of pickle serialization to contain the STAC catalogue. Writing the full catalogue on json format at the end of each post-job action is too heavy. Instead we are now just appending new items to the in-memory object, and serializing it in a single binary file after each post-job action. The full catalogue is written whenever all the jobs are finished. Works fast and efficiently but I already got a corrupted catalogue cache as I Ctrl-C'ed the script whenever one thread was writing the binary serialized file. So there is something to improve here.
[ ] Some various fixes: the thread lock to write on the STAC catalogue, safeguards such as check for missing fields in the openeo job metadata...

@HansVRP I still need your green fire for the remaining open conversations

Thanks @GriffinBabe will dedicate some time this afternoon

Some questions and comments.
The code provided is not necessarily very general. In addition I miss practical unit tests for the newly introduced functionalities. e.g. unit test for calculating the s1 area ect

By the way there is a unit test available for the s1 area calculation: https://github.com/Open-EO/openeo-gfmap/blob/s1-extraction-fixes-PR2/tests/test_openeo_gfmap/test_utils.py#L24
There are missing unit-tests for:

JobManager, although I really don't know how to test such a complicated feature
Generic extractors


docs: add external docs urls

Contributes to https://github.com/carbon-design-system/carbon-platform/issues/1380
Adds externalDocsUrls to the index, so the IBM Products library's assets have View asset docs in Carbon Platform like this example below.
What did you change?

add external docs urls
clean up ibm security carbon yml formatting
fix smart quote in description

Example

@jeanservaas @aubrey-oneal @aagonzales can you review? Not all indexed assets are documented in https://pages.github.ibm.com/cdai-design/pal, but for those I found, I added as externalDocsUrls.


Update djunits-generator to Java-17

Following the update of djunits to Java-17, djunits-generator should also be updated.

Completed.


Implement \updownarrows and \downuparrows

Currently MathJax has support for \upuparrows and  \downdownarrows but not for \updownarrows and \downuparrows which is quite inconsistent. I haven't found alternatives (apart from \uparrow\downarrow...).

The glyph needed for the \updownarrows and \downuparrows are not the the MathJax TeX fonts used by MathJax v3 and below.  This is because the Mathjax TeX fonts are based on the TeX Computer Modern fonts and the AMS symbol fonts, which do not include the characters you are looking for.  Those seem to be available in the mathabx TeX package, which includes many glyphs that are not in the MathJax TeX fonts.
One of the new features in MathJax v4 is the availability of 10 new fonts (plus the original MathJax TeX fonts), and these have much greater character coverage, though MathJax does not predefine a macro for every possible character.  You can define those yourself, as needed.  For example, you could use
\newcommand{\updownarrows}{\U{20C5}}

to define the macro in a particular page, or use the configuration
MathJax = {
  tex: {
  }
}

In version 3 you can use `\newcommand{\updownarrows}{

The glyph needed for the \updownarrows and \downuparrows are not the the MathJax TeX fonts used by MathJax v3 and below.  This is because the Mathjax TeX fonts are based on the TeX Computer Modern fonts and the AMS symbol fonts, which do not include the characters you are looking for.  Those seem to be available in the mathabx TeX package, which includes many glyphs that are not in the MathJax TeX fonts.
One of the new features in MathJax v4 (now in beta release) is the availability of 10 new fonts (plus the original MathJax TeX fonts), and these have much greater character coverage, though MathJax does not predefine a macro for every possible character.  You can define those yourself, as needed.  For example, you could use
\newcommand{\updownarrows}{\U{20C5}}

to define the macro in a particular page, or use the configuration
MathJax = {
  tex: {
    macros: {
      updownarrows: ['Macro', '\\U{21C5}']
    }
  }
}

in order to pre-define when MathJax starts up.  This uses the command \U that is introduced in v4 in order to obtain the needed character.
In version 3 you can use
\newcommand{\updownarrows}{\mathrel{\unicode{x21C5}}}

to accomplish the same goal.  You can do a similar configuration to pre-define the macro.  Note, however, that in v3 and below, the needed glyph is not in the MathJax fonts, so MathJax will try to obtain one from the fonts installed on your system.  That may not match the rest of the math very well, and will vary from user to user depending on what fonts they have installed.

Thank you for the information! I'm writing my notes in .md files in a private Github repo. Github uses MathJax to render them on their site but it doesn't recognise \newcommand and it also ignores \unicode due to recent events.

Yes, GitHub did don't include \newcommand, and had some problems with their implementation (though they have improved on that).  There are other Markdown engines that do handle MathJax much better (and allow \newcommand and such), so you might consider trying one of those.  For example, pandoc can translate Markdown to HTML, PDF, LaTeX, and a variety of formats.  That is a mature and well-supported product, but there are many other Markdown programs that integrate MathJax.

PS, you can, of course, enter the Unicode characters ⇅ and ⇵ directly into an expression in order to get these symbols as well (without the need for a macro) as a last resort.


perf(payment): enhance data validator & db-transaction

before delivery service, need to:

run python manage.py migrate
run apt-get install php


FIX Resolving various console warning

As titled. There's a few React warnings that come up in the console when using this module (with dev built JS) - This resolves all of those that this module is responsible for.s

Currently GraphQL gives IDs as strings. I've converted the expectation in this module so that IDs are strings. I think GraphQL would need changes if we wanted to keep them as integers - but I may be missing something.

Needs a rebase now, soz

Done 🙂


[TASK] Compile of Java can lead to two set of classes

Description
When you update the java folder and recompile java, sometimes two sets of classes appear and they conflict. We can wipe the classes folder prior to compiling to prevent this.
Existing
Is there any relevant code or ui feature that the developer should know about when resolving this issue.
Reference
This issue references. . .
Tasks
What are more specific tasks that a developer needs to take to consider this issue resolved.

Estimated time for completion EOW Sept 20, 2024


Re-implement swear filter on UrbanDictionary

Rebuild has removed that ability.

This requires #63

No real demand


Misspelling in exception

Thank you for your library.
I use it whenever I need to do some FTP operations.
I noticed a little misspelling here

I think it should be Error while creating directories

Changed, Merged, Fix in next release


Error exporting Yandere simulator

Every time I try to export the game I get an error that tells me to check the unity default resources file
This is the link to the October 15th built I downloaded
http://www.mediafire.com/file/viciqzzv01kna3q/YandereSimulator.zip
tried exporting a built from one of my own projects and it worked fine, am I missing something ?

Same issue as https://github.com/mafaca/UtinyRipper/issues/72
For now I can't fix it from my side so you need to manually change version for "unity default resources" file

But how can I know which version is the right one?
The version in the file is 2017.2.0f1 but I can't understand what version I should add instead

Look last message in referenced issue

Yes, it's looks like your text editor insert some extra symbols. Notepad++ works fine for me

You're right, Notepad++ worked !
So to anyone reading this in the future, just download Notepad++ ( I already had it but still 😂 )
Thanks for the help, good luck on future projects/updates 😊

Closing this one as a duplicate of https://github.com/mafaca/UtinyRipper/issues/36


Upgrade cis-benchmark chart

Upgrade cis-benchmark chart to use latest sonobuoy & kube-bench releases.
Related issue: rancher/rancher#37727

Validated on rancher v2.6.7-rc2
Validation steps followed

Created a rancher server 2.6.7-rc2
Provision a downstream k8s cluster v1.24
Installed a CIS Benchmark chart version.
Made sure that the CIS uses the sonobuoy v0.56.7.
While running the scan, exec into the security-scan pod and checked the kube-bench version. kube-bench version shows 0.6.8

Sonobuoy and kube-bench version are as expected for the CIS Benchmark chart version 2.0.5-rc4, hence closing the issue.


Release 3.9.2_7.1.1

Wazuh version: 3.9.2
Elastic version: 7.1.1

[x] Adapt to new versions (3.9.2 - 7.1.1)
[x] Update changelog
[x] Tests
[x] Tag: v3.9.2
[x] Draft release

Hi team,
In order to update the code to the new release I did the following task:
Filebeat versioning
Filebeat now supports versioning of packages and has been adapted to support CentOS installation.
https://github.com/wazuh/wazuh-chef/blob/26b41ce35edf3177425092e9ecb547401e1b2be2/cookbooks/wazuh_filebeat/recipes/filebeat.rb#L8-L21
Bump version
Default attributes of versions now specify 3.9.2 and 7.1.1 values.
You can check these attributes at #e0603b3
Best Regards,
Jose


Integrate Automatic Indexing into DB

Specification
Indexing is the act of creating a separate data structure that makes it faster to lookup data on a primary data structure.
PK has several domains that require secondary indexing:

acl - perm id, vault id, node id
gestalts - discovery, adjacency list indexing
nodes - possibly needed in the future for all sorts of optimal routing needs (kadmelia indexing?)
notifications - to be able to filter notifications
sigchain - to be able to filter sigchain
vaults - for vault tagging and vault names

Right now secondary indexing is implemented manually in ACL by persisting bidirectional maps in leveldb.
Indexing is tricky topic, and it's better to create a single indexing mechanism in DB so that all domains in PK can benefit from them.
Generic indexing can reply on LevelDB's eventemitter interface. The good thing is that other people have already created good libraries for this:

https://github.com/hypermodules/level-auto-index - is compatible with subleveldown, and uses "hooks" to abstract the leveldb eventemitter interface
https://github.com/hypermodules/level-idx - this uses level-auto-index

The second library automates some of level-auto-index. In fact it binds secondary index interfaces to the leveldb object.
For @matrixai/db it makes more sense to use level-auto-index so we can more tightly control how the indexes are stored. Most likely via sublevel interfaces.
Additional context

https://github.com/MatrixAI/js-polykey/issues/188 - further details on applying indexing to sigchain operations
http://www.tiernok.com/posts/adding-index-for-a-key-value-store/

Tasks

[x] - Investigate possible dependencies to automate secondary indexing and their relationship
[x] - Prototype the usage of level-auto-index
[ ] - Integrate the level-auto-index into this library's domain/level creation, each level including the root level should have the ability of attaching a secondary index (or multiple secondary indexes)

Was thinking that this secondary index is by default unique.
However non-unique keys can be done by making use of the sequence range.

The level-idx automates level-auto-index by expecting the usage of a single sublevel as the index database. That sublevel is then further split into sublevels for each index that is created.
So for a structure like this:
ID -> {
  name: string;
  title: string;
}

The ID is the primary index, thus we don't need to index that. The name and title would be 2 separate secondary indexes. These would each occupy a sublevel under an index sublevel.
If we want to apply this to each sublevel we already have with the this.level(domain: string, dbLevel: DBLevel): Promise<DBLevel>, we may have an index sublevel for each sublevel we create, or a global index sublevel for all possible indexes.
The name and title become names of the index sublevels.
If we imagine there are:
aLevel

ID -> {
  name: string;
  content: string;
}

bLevel

ID -> {
  name: string;
  signature: string;
}

You can see that the name index would be conflicting. If we wanted to index the name for aLevel and bLevel, we would need to separate them out.
We could do this by making use of our domain array.

Every sublevel created from DB.level can have an associated indexes sublevel. It can be automatically named by taking the domain string and appending domain.index. The . separator has to be different from the prefix separator in order to not confuse it with another sublevel. Perhaps maybe domain-index to avoid any confusion since I often use . to represent separators too.
This indexes sublevel is a sublevel containing all the index sublevels for respective primary db.
Not every sublevel requires an index though, so this can lazily initialised.
On the otherhand, creating a sublevel doesn't actually do anything to the database unless the sublevel is actually used. It can simplify things right now if it is just constructed.
The DB currently does not maintain any of the sublevel references. These are just given to the the user to make use of. See that DB.level returns a DBLevel. It is the user and all the PK domains that currently maintain this. If we keep this same pattern, then the PK domains would have to keep around the indexes. It would the be only way for users to be able to query with respect to an index.
Having the associated indexes sublevel is one thing, it is another to keep around the index itself. The index sublevel is in fact an implementation detail. It would be ideal for the indexes sublevel to not need to be maintained by the user. The user wants to use the index sublevel instead.
So here's a possible API:
const mgrDomain: DBDomain = ['Manager'];
const dirsDomain: DBDomain = [mgrDomain[0], 'dirs'];

const mgrDb = await db.level(mgrDomain[0]);
const dirsDb = await db.level(dirsDomain[1], mgrDb);

// this is is still a Db, but now used as an index
const mgrDbIndex = await db.index(mgrDb, 'indexname', ['name, 'title']);

// remember we can use the db themselves, but we don't benefit from automatic serialisation/deserialisation and encrypt/decrypt

// so if we want to "get" but according to an index, we now have to refer to the index domain
const indexDomain = ['Manager', 'indexname'];

// note that when you are creating a compound index, you now have to use a separator to indicate this
await db.get(indexDomain, 'somename!sometitle');

Remember you don't actually need to create a sublevel to use get, put... etc. The domain parameter basically ends up creating sublevels on the fly.
This means when you first create an index, and then start get and put it should work fine as the docs indicate that it automatically tracks these operations. However what happens if you already have data in the db, and you create the index afterwards? We can enforce the idea that the index should be created ahead of time, but it would be ideal that AutoIndex has a way of reconstructing the index from scratch if there was already data in the primary sublevel.
Another issue is the fact that the DB is now always using buffer encoding. So that means the index dbs should also be always using buffer encoding for values. But keys themselves depend.
A further problem is whether the indexes are going through the encryption/decryption? If they are not using the DB.get/put mechanisms, then the index values are not encrypted.

Ok so there's a problem. Because the values are encrypted before storing into the DB. The hooks which relies on the event triggers only have access to the encrypted ciphertext. Thus the usage of level-auto-index is not possible because our encryption/decryption sits on top of the leveldb.
Ok so if we want to do this, we would need to synthesise and extract the implementation into our own DB here rather than just using the upstream libraries.

One issue with encrypting indexes, is that the index sublevel key is based on the primary sublevel value.
So if the primary sublevel name value is "sam".
Then would this mean that the index sublevel key is "sam"? If so, this would then be leaking the value itself.
If we would to encrypt the index keys this ends up with some problems...

Encryption would have to be deterministic. You are given sam and you must always get back the same ciphertext.
Sort order of the index keys no longer make sense.

Here's an alternative. An order-preserving hash. If the index keys can go through an order-preserving hash, then it should still work nicely preserving order, and you can deterministically hash any value you want to look up and then find the "encrypted" ID and decrypt it. It may even be possible to just hash the ID instead of encrypting it. The values of the index sublevels are just keys of the primary sublevels, and keys of primary sublevels are not encrypted anyway.

What kind of indexes do we want to support?

Unique value indexes, I'm not sure how the index works when multiple entries have the same value, does it figure out that the same entry can point to multiple keys?
Range indexes - need an iterator that counts it
Compound indexes - requires separator...

This gets pretty complicated. The most likely usage right now is just unique value keys, and possibly when it is not unique. If we end up with too many complicated indexes, we might as well change to using Sqlite instead.
Going to prototype this with level-auto-index to see how it deals non-unique value indexes.

Order preserving hashing is not useful because you can recover the original value. https://crypto.stackexchange.com/questions/8160/secure-order-preserving-hash-function
I'm not sure if this applies to perfect minimal hashes. But it seems there is some leak.
There are new algorithms for order preserving encryption but no libraries in JS and too costly to implement for this feature.
However if we were to not use indexing, we would probably have to create bidirectional maps and end up not encrypting the key anyway. Therefore having an unencrypted index isn't any worse.
The main thing then is that anything we index is going to be leaked and thus indexing should be limited to values we are willing to leak like ID values. Things that are not meant to be leaked should not be indexed then.
So for now we can go with unencrypted & unhashed index keys. But index values are going to be encrypted as normal.
The best solution would where the leveldb block system itself had encryption. This would mean all keys and values are encrypted and encryption is happening at the lower level. However this is not feasible to change to atm.

It appears there's a relationship between proper transaction support, block level encryption and secure indexing.
In EFS we have an issue for integrating native snapshots into the transaction system. This requires going into the C++ binding of leveldb and making it work. Then our transactions can use leveldb snapshots natively. And in such a case our transaction could scale too.
Block level encryption means encryption at the blocks of the DB rather than at record level. RocksDB has this capability https://github.com/facebook/rocksdb/pull/2424, but would require changing to use rocksdb which is possible because it fits the levelup API, but any encryption mechanism would be done at the C++ level, and not involve webcrypto APIs or primitives.
Indexing as in this issue is currently not entirely secure or is very limited in order to not leak values. It would work better if block encyption was available. Then we would not need to work out complicated OPE.
All 3 problems can be resolved by using sqlite3 and the sqlcipher extension assuming that it does block level encryption. However cross platform requirements need analysis. This also impacts the common crypto mechanisms used by PK.

For now we will stick with simple indexing, and the current transaction support is sufficient.
When the combination of 3 problems becomes worthwhile, then we should investigate solutions for this DB to have encryption to be at block level, and then having proper transactions and proper indexing support. The first path would likely to be investigating the usage of SQLCipher. It's not an extension, it's a fork. It would need to be usable on PK CLI and PK GUI, and for Android & iOS it looks like it would need to be compiled for those platforms. This would be large epic, as it would involve multiple subissues to resolve. The encryption work would also need to involve consideration of WASM https://github.com/MatrixAI/js-polykey/issues/155 and QUIC https://github.com/MatrixAI/js-polykey/issues/234.
Basically for our next phase of work, there's going to be alot of C/C++ involved.
@joshuakarp

2 ways we can implement this. By trying to bring encryption into the leveldb via hooking into its event system, and thus getting a good idea of how we can apply indexing just before the encryption. Or by doing it above the existing encryption in our DB class. The former requires diving into the leveldb internals, the latter might result in some code duplication and a recreation of an event system. The former doubles down on leveldb investment, the latter may be lighterweight and enable us to move to sqlite3 or other systems in the future.
Additionally, in order to represent an index that can point to multiple keys, a multi-value index that is, we can make use of sublevels again. Basically every time we index a value, that value doesn't directly point to the primary key, but instead to another sublevel of primary keys. The values of these can be arbitrary or contain metadata relating to each record. But one can now use the order of the primary key so you can get the "latest" value for a given index.

Compound indexing is useful for our Discovery queue to represent priorities.

2 ways we can implement this.
1. Embedding into LevelDB Extension Points (hooks, events, abstract-leveldown wrappers): By trying to bring encryption into the leveldb via hooking into its event system, and thus getting a good idea of how we can apply indexing just before the encryption.
2. Building on top of DB here: By doing it above the existing encryption in our DB class.
The former requires diving into the leveldb internals, the latter might result in some code duplication and a recreation of an event system. The former doubles down on leveldb investment, the latter may be lighterweight and enable us to move to sqlite3 or other systems in the future.
Additionally, in order to represent an index that can point to multiple keys, a multi-value index that is, we can make use of sublevels again. Basically every time we index a value, that value doesn't directly point to the primary key, but instead to another sublevel of primary keys. The values of these can be arbitrary or contain metadata relating to each record. But one can now use the order of the primary key so you can get the "latest" value for a given index.

Way 1. cannot be done unless #4 and #5 are solved first. As these are long and complicated problems, we'll park these until later, it will involve ultimately looking into the C++ codebase of leveldb and making changes there or at the level nodejs wrapper code.
Way 2. will be what we have to do to proceed for now.

In https://github.com/MatrixAI/js-polykey/issues/244 we are storing each node entry in buckets. The buckets are ordered due to the lexi-int encoding of the bucket index, however the node ids  themselves require to be indexed by the lastUpdated timestamp. This is to allow us to do fetches and streams in the order of last updated and to avoid having to sort the bucket every time we acquire it.

With the merge of #10, this can now use a special root level called index to store all relevant index level data to avoid conflicting with normal data usage.

Automatic indexing is made easier with snapshot isolation, because we can expect consistent reads, meaning while traversing an index, we can look up what the index points to easily.

Since we're on rocksdb now, we can make use of some prior art for secondary indexing:

https://github.com/nlfiedler/mokuroku
https://misfra.me/2017/01/18/how-to-implement-secondary-indexes/

There's too many ways we use indexing for it to be automated unless we first have a structured schema. So won't need this now since.


hassio menu missing

Since 0.73.1, I do not have the hassio menu in the web interface.
I tried rebooting (that's an excerpt from hassio su logs):
18-07-20 09:13:40 INFO (MainThread) [hassio.hassos] Detect HassOS 1.5 on host system
18-07-20 09:13:40 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to supervisor homeassistant/aarch64-hassio-supervisor with version 115
18-07-20 09:13:40 INFO (SyncWorker_1) [hassio.docker.interface] Attach to image homeassistant/raspberrypi3-64-homeassistant with version 0.73.1

but still no menu. So I tried upgrading to 0.74.0b4 (using hassio su update), still no menu.
Anything I should try or look at? Here are the info outputs:
hassio ha info
{
    "result": "ok",
    "data": {
        "version": "0.74.0b4",
        "last_version": "0.74.0b4",
        "machine": "raspberrypi3-64",
        "image": "homeassistant/raspberrypi3-64-homeassistant",
        "custom": false,
        "boot": true,
        "port": 8123,
        "ssl": false,
        "watchdog": true,
        "wait_boot": 600
    }
}

$ hassio su info
{
    "result": "ok",
    "data": {
        "version": "115",
        "last_version": "115",
        "channel": "beta",
        "arch": "aarch64",
        "wait_boot": 5,
        "timezone": "Asia/Singapore",
        "addons": [
            {
                "name": "Configurator",
                "slug": "core_configurator",
                "description": "Browser-based configuration file editor for Home Assistant.",
                "state": "stopped",
                "version": "0.4",
                "installed": "0.4",
                "repository": "core",
                "icon": false,
                "logo": false
            },
            {
                "name": "SSH - Secure Shell",
                "slug": "a0d7b954_ssh",
                "description": "Allows SSH connections to your Home Assistant instance",
                "state": "started",
                "version": "2.5.0",
                "installed": "2.5.0",
                "repository": "a0d7b954",
                "icon": true,
                "logo": true
            }
        ],
        "addons_repositories": [
            "https://github.com/hassio-addons/repository"
        ]
    }
}

Indeed I did remove discovery: (as I was doing many restart at the time, and didn't want all Apple TV to turn on, nor to set the AppleTV component to start off).
I added hassio: to my configuration, and the menu is back. Thanks, I didn't understand this was "discovered"…


Harmonize names between CUDArt and CUDAdrv

CUDArt's test scoped all the calls (to make it easy to reload the module and try again...), but this obscured the fact that there were several name conflicts between CUDArt and CUDAdrv. This strips the scoping out of the tests, and imports necessary names from CUDAdrv.
This will exhibit a merge conflict with #88, but feel free to merge in either order and I'll fix the conflict.

Codecov Report

Merging #89 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #89   +/-   ##
======================================
  Coverage    40.6%   40.6%
======================================
  Files          10      10
  Lines         564     564
======================================
  Hits          229     229
  Misses        335     335

Impacted Files
Coverage Δ

src/CUDArt.jl
100% <ø> (ø)
:arrow_up:

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 88c44b7...2bb9df2. Read the comment docs.


Support for additional/custom color variants

Please add an option to specify a color or primary/secondary color variants to be used in a theme in addition to the predefined list of colors

This is a difficult to implement issue


fix(examples): fix typo 16-drag-from-outside -> 15-drag-from-outside

14-toolbox.html is missing the "next" link to 15

@STRML fixed. And I fixed html markup in these files


Opacity facade animation doesn't work in edge case - element remains Opacity 0

Describe the bug
We found a scenario where an Opacity 0 element stays invisible when animating its Opacity to 1 using Facade animations.  This bug was found by a real react-native-windows customer.  See:  https://github.com/microsoft/react-native-windows/issues/4312
Steps to reproduce the bug

Steps to reproduce the behavior:
I managed to get this down to XAML min repro app.
Unzip the attached VS project
App18.zip
Build
Run
Hover your mouse over the red rectangle
Expected behavior
Another red rectangle is supposed to appear above the red rectangle you hovered over
Screenshots

Version Info
This is using inbox XAML
Windows 10 (just has to be 19H1 or higher)
Desktop

I debugged this down to a dirty flag issue in the facade animations code:
Check_return HRESULT CUIElement::StartAnimationImpl(In WUComp::ICompositionAnimationBase* animation, bool isImplicitAnimation)
{
IFC_RETURN(FacadeAnimationHelper::StartAnimation(this, animation, isImplicitAnimation));
if (!HasFacadeAnimation())
{
    SetRequiresComposition(CompositionRequirement::HasFacadeAnimation, IndependentAnimationType::None);
}

DOFacadeAnimationInfo* opacityFacadeAnimation = GetContext()->GetFacadeStorage().TryGetFacadeAnimationInfo(this, KnownPropertyIndex::UIElement_Opacity);
if (opacityFacadeAnimation != nullptr && opacityFacadeAnimation->m_animationRunning && !HasWUCOpacityAnimation())
{
    SetHasWUCOpacityAnimation(true);
}

// If the CompNode already exists, we can avoid dirtying the UIElement and instead just dirty the CompNode.
// Note that we're guaranteed to tick again because we just started an animation, which requests another Commit.
HWCompTreeNode* compNode = GetCompositionPeer();
if (compNode != nullptr)
{
    CDependencyObject::NWSetRenderDirty(compNode, DirtyFlags::Render);
}

m_areFacadesInUse = true;
return S_OK;

}
There are two code paths here that dirty the node:
1 - When we call SetRequiresComposition, if the element doesn't have a CompNode, we'll mark the node as dirty.  But if it already requires a CompNode we will not mark it dirty.
2 - Further down we check to see if it actually has a CompNode, and if it does, we mark the CompNode dirty.  But if it doesn't have a CompNode we will not mark it dirty.
There is a case where neither 1 or 2 apply, that's the case here:  If you set one of the properties that requires a CompNode (eg Translation animation), and also set Opacity = 0, it will require a CompNode, but then we will cull the CompNode as it's not needed.
Once you get into this state, if you then schedule an Opacity animation, it won't dirty the node, and thus won't give the node its CompNode back.  You then end up stuck with no visible content.
It's certainly an edge case, however the way that react-native animations work make this case more likely.     The fix is super simple - just add an else to the "has compnode" branch and set the UIElement dirty for render, like this:
HWCompTreeNode* compNode = GetCompositionPeer();
if (compNode != nullptr)
{
    CDependencyObject::NWSetRenderDirty(compNode, DirtyFlags::Render);
}
else
{
    CUIElement::NWSetContentDirty(this, DirtyFlags::Render);
}


Bootstrapcrowbar to use original cloud version

The bootstrapcrowbar code checks for cloudsource, not
upgrade_cloudsource. This means we have to check for the original cloud
version.

I think that for upgrade case cloudsource=$upgrade_cloudsource should be executed from mkcloud's crowbarupgrade_5plus so in our case that would be Cloud 7.

@jsuchome will check that, but the results from today say the contrary.

I think that for upgrade case cloudsource=$upgrade_cloudsource should be executed from mkcloud's crowbarupgrade_5plus so in our case that would be Cloud 7 anyway.

Right, this is set in mkcloud. For an upgrade path do not rely on $upgrade_cloudsource to be set in qa_crowbarsetup.

@jdsn I think the problem is we refresh cloudsource from /etc/cloudsource very often: every time we can get_proposalvars. I think we may need to write not only cloudsource but also /etc/cloudsource.

I think the problem is we refresh cloudsource from /etc/cloudsource very often

@abel-navarro
Outch, just found it. Thats extremely bad.
This was introduced with commit ed7448973e851fcf364d8659f7d9bdde624166ed.
I will have to look at this carefully.

This approach proved to be wrong thanks to @MaximilianMeister . crowbar-init tried to start already in cloud6, which is wrong. Closing it.


Occasional crashing

somethimes it generates wrong youtube id and crashes.

UPDATE: Scraper picks garbage because it found playlist instead of video.

Fixed IndexError:List index out of range


Some issue if height is changing

when height is changing, the data is changed. Its working weirdly. If you want to reproduce the issue than open docked inspector and continuously change the height of view-able screen.

I failed to reproduce the issue. Are you talking about changing the height of the .treadmill or .treadmill-unit class? Also, are you changing height dynamically?


Adapt mutable fragment for gs::DynamicFragment

What do these changes do?

Add directed_ to fragments
Add DynamicVertexRange and DynamicDualVertexRange for gs::DynamicFragment

Related issue number

Fixes

Codecov Report

Merging #92 (c500e87) into master (f2e9422) will decrease coverage by 0.48%.
The diff coverage is 78.12%.

@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
- Coverage   73.90%   73.41%   -0.49%
==========================================
  Files          60       60
  Lines        4813     4823      +10
==========================================
- Hits         3557     3541      -16
- Misses       1256     1282      +26

Flag
Coverage Δ

app_tests
73.41% <78.12%> (-0.49%)
:arrow_down:

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

Impacted Files
Coverage Δ

grape/fragment/e_fragment_loader.h
18.75% <ø> (ø)

grape/fragment/ev_fragment_loader.h
13.63% <ø> (ø)

grape/graph/mutable_csr.h
41.05% <ø> (-3.98%)
:arrow_down:

grape/utils/vertex_array.h
90.53% <ø> (-0.88%)
:arrow_down:

grape/utils/vertex_set.h
90.12% <ø> (ø)

grape/fragment/mutable_edgecut_fragment.h
52.57% <36.36%> (-2.11%)
:arrow_down:

grape/fragment/basic_fragment_loader.h
89.15% <100.00%> (ø)

grape/fragment/fragment_base.h
91.17% <100.00%> (-2.77%)
:arrow_down:

grape/fragment/immutable_edgecut_fragment.h
69.95% <100.00%> (ø)

grape/graph/adj_list.h
71.73% <100.00%> (+1.28%)
:arrow_up:

... and 6 more


Test Hub page

This PR is raised to test the landing page

Docs Build status updates of commit 790467b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:warning:Warning
View
Details

msteams-platform/index-test.yml

Line 45, Column 1: [Warning-yaml-duplicate-key] Key 'highlightedContent' is already defined, remove the duplicate key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 852e0e5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:x:Error

Details

msteams-platform/index-test.yml

Line 48, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.itemType'.
Line 48, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.url'.
Line 45, Column 1: [Warning-yaml-duplicate-key] Key 'highlightedContent' is already defined, remove the duplicate key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 55bc474:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:x:Error

Details

msteams-platform/index-test.yml

Line 50, Column 4: [Error-unknown-field] Could not find member 'highlightedContent2' on object of type 'Object'.
Line 24, Column 7: [Warning-yaml-duplicate-key] Key 'itemType' is already defined, remove the duplicate key.
Line 25, Column 7: [Warning-yaml-duplicate-key] Key 'url' is already defined, remove the duplicate key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3e55c5a:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:x:Error

Details

msteams-platform/index-test.yml

Line 52, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.itemType'.
Line 52, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.url'.
Line 49, Column 1: [Warning-yaml-duplicate-key] Key 'highlightedContent' is already defined, remove the duplicate key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 654ce86:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:x:Error

Details

msteams-platform/index-test.yml

Line 21, Column 5: [Error-array-length-invalid] Array 'highlightedContent.items' length should be <= 8.
Line 48, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.itemType'.
Line 48, Column 7: [Error-missing-attribute] Missing required attribute: 'highlightedContent.items.url'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 248a42b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:x:Error

Details

msteams-platform/index-test.yml

Line 21, Column 5: [Error-array-length-invalid] Array 'highlightedContent.items' length should be <= 8.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c18b456:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0dffdd6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7edae5e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 98a07a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2d6913b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2ec528d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3a9280d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 179b99c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7fd1407:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8cc1c9b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c25b97a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e5b1ecb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 95ce2fa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7abb2d2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dfd5f2d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9f7caf9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 79735ee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8672e80:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index-test.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d0a0c4c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c74298c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 33a95ef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dbf61a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit da2edfa:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index.yml
:x:Error

Details

msteams-platform/index.yml

Line 122, Column 11: [Error-yaml-syntax-error] While parsing a block mapping, did not find expected key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a7c89d5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f8e761a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bdb1243:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1edefa7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 26ca2e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e48b645:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a044996:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d4ba7de:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c95530c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit cbad068:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d015f29:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d0d5dae:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 839f312:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 839f312:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c45d7d3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c45d7d3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3aa1252:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 688355f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 76d098f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 76d098f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 675c7bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 675c7bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6d1ec09:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index.yml
:x:Error

Details

msteams-platform/index.yml

Line 119, Column 11: [Error-missing-attribute] Missing required attribute: 'conceptualContent.items.links.itemType'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 20c3d85:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/index.yml
:x:Error

Details

msteams-platform/index.yml

Line 119, Column 11: [Error-missing-attribute] Missing required attribute: 'conceptualContent.items.links.itemType'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit edc6a8e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 02fc2a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 05c1b7e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fa947fa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6171a4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0c77e7c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit adedf18:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5cf764e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 99fce7c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a374b63:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0c26d5a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

msteams-platform/index.yml
:white_check_mark:Succeeded
View

[Warning-RepositoryOwnerPermissionInsufficient] Owner laujan of repository https://github.com/MicrosoftDocs/msteams-docs has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Installing on Windows 7/8/10

This allows you to connect new libraries

Does virtualenv not work on windows? Or is anaconda better somehow?


RCD can be charged with raw materials

About the PR
read the title.
Why / Balance
Tg has it.
Technical details
For some reason RCD uses charge component instead of battery component so i just copy-pasted MaterialEnergySystem into MaterialChargeSystem.
Media
RCD.png
Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog
:cl:

tweak: RCD can be charged with raw materials.

Summary by CodeRabbit

New Features

Introduced the MaterialChargeComponent for managing a whitelist of materials.
Added the MaterialChargeSystem to facilitate interaction between materials and charge management.
New MaterialCharge entity allows interaction with a variety of materials, enhancing tool functionality.

These updates improve gameplay by enabling more dynamic material interactions and charge management.

media?

being able to make windows with steel feels kind of weird

any engineer mained after 1993 cant craft, all they know is deconstruct captain door, make frezon, steal from CE, get rad poisoning, charge they RCD and die.

being able to make windows with steel feels kind of weird

you can do that in SS13 and i dont want to rewrite whole RCD system (upstream will brake it one day).

media?

media of what? me clicking with a steel sheet on RCD and steel sheet disappearing?

media of what? me clicking with a steel sheet on RCD and steel sheet disappearing?

yeah

@yglop what if, instead of this, RCD gained material when destroying something?

@yglop what if, instead of this, RCD gained material when destroying something?

done


Example of tain_path and val_path

Hello, can you please give me an example of train_path(car_train.txt) and val_path(car_val.txt) used in train_Mobilenet.py line number 17 and 18. Thanks!


QDR Auth in smoketest (#525)

QDR Auth in smoketest

Added qdr-test as a mock of the OSP-side QDR

Connection from qdr-test -> default-interconnect is TLS+Auth

Collectors point at qdr-test instead of default-interconnect directly

Much more realistic than the existing setup

Eliminated a substitution in sensubility config

Used default QDR basic auth in Jenkinsfile

(cherry picked from commit 37b6f035d6ff44a39598aacf812b3b893bafda7e)

@leifmadsen Just an FYI that this need to merge here, but no need to re-tag anything for future 1.5.3 builds since this doesn't affect deliverables.


Adding dismiss option on notifications

Title. Maybe also look into adding other options on the notification itself.

Have added an auto-dismiss option to notification. Pending discussion if that is better..


Simplify top nav

Dependent on solutions for

In-repo redirects
Zombie zapper in deploy bot

Under exploration with Clade Design

Closing since this is covered as part of #172


[FEATURE] add support for infering FeedbackDataset structure in from_huggingface for transformer models

Is your feature request related to a problem? Please describe.
I would like to focus on HF models.
Describe the solution you'd like
https://huggingface.co/models has models categorized by task
import argilla as rg

rg.FeedbackDataset.from_huggingface(""ProsusAI/finbert")

Internally, something like this should happen, but Ideally we should avoid downloading the entire model and just use a config.
import argilla as rg
from transformers import pipeline

name = "sentiment-analysis"
pipe = pipeline(name)

ds = rg.FeedbackDataset.for_text_classification(
    labels=list(pipe.model.config.id2label.values()),
    multi_label=pipe.model.config.problem_type == "multi_label_classification"
)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @davidberenstein1957, I think that re-using from_huggingface to not just load Argilla datasets dumped in the Hugging Face Hub, but also to load a configuration for any given model can be confusing to users and also confusing internally code-wise, so if this appears to happen I think we need to discuss about a proper method on doing so. Also the idea you propose I assume is to re-label already labelled datasets? If you could elaborate more over e.g. Notion and share with the team that would be great!

Hi @alvarobartt, it is not something that is directly happening or was mentioned anywhere. However, I was just dreaming and thinking a bit and given that have gotten a lot of mentions that people don't understand how to use and configure the dataset so things like the task_templates could help for those. It is not used to re-label a dataset but more so to easily configure and link them. Similar to the reasoning about using a default embedding_model and text descriptions metadata for datasets.

I agree with @alvarobartt that from_huggingface might be confusing. I think this might be better placed in the task templates somehow but also we might want look at the bigger picture: associate hub model IDs with datasets for using them in different parts of the product (retraining, inference, etc.)


Enable remote git repos for check-ref, history, and stages

mmm... why so many commits? I did sync my main with the iterative main before pushing new commits... what should I have done differently?

mmm... why so many commits? I did sync my main with the iterative main before pushing new commits... what should I have done differently?

I assume this is because you didn't fetched upstream in the repo, so after the previous PR was merged, your main branch contained all those commits, being branched out from the HEAD of main few commits back. NP :) Merging this!

Codecov Report
Base: 81.88% // Head: 82.79% // Increases project coverage by +0.90% :tada:

Coverage data is based on head (6c45fc8) compared to base (a3cefdb).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #273      +/-   ##
==========================================
+ Coverage   81.88%   82.79%   +0.90%
==========================================
  Files          16       17       +1
  Lines        1905     1953      +48
==========================================
+ Hits         1560     1617      +57
+ Misses        345      336       -9

Impacted Files
Coverage Δ

gto/api.py
91.33% <100.00%> (+0.35%)
:arrow_up:

gto/cli.py
70.43% <100.00%> (ø)

gto/constants.py
100.00% <100.00%> (ø)

gto/git_utils.py
100.00% <100.00%> (ø)

gto/base.py
87.25% <0.00%> (+1.41%)
:arrow_up:

gto/tag.py
86.39% <0.00%> (+2.72%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Got it thanks! Not used to the github fork-pull strategy (I come from GitLab MRs...)


training on custom dataset

how can I train this model on my own custom dataset?

Currently Pascal VOC and COCO dataset formats are supported. You can dump your custom dataset into either of these two formats (e.g. in cvat) and just point the train.py to it, specifying format with --dataset-style parameter, path to it with --dataset parameter and image set for VOC or annotation filename for COCO for training and validation stages with --train-image-set and --val-image-set keys (they are set with train and val by default, correspondingly).

thank you so much


fix name of ACS dataset

Fix name of ACS dataset

Description

Category: bugfix
JIRA issue: N/A

Fix name of ACS dataset - https://ihme.slack.com/archives/C02KUQ9LX32/p1681934664853799
Testing
N/A

I guess I should have taken the time when I added that container to actually update everywhere. Sorry about that.


Add Stylus linter (stylint)

Maker for Stylus linting via stylint.

@benekastah: Any interest in this? I'm using it in production for a couple of weeks now without any issues.

Thanks, @herrbischoff.
Could you add it to the README also, please? (after rebasing)
I think it makes sense to include an URL / link to the linter's homepage there then, too.


Database Conversion fails 15.1->15.2

This is basically a continuation of issue #879 "Database Conversion fails)
Last time the solution was to restart PowerShell, after installing new cumulative BC.
But now that does not help me.
I get error:
Invoke-NAVApplicationDatabaseConversion : A technical upgrade of database 'Demo Database BC (15-0)' on server 'EROL-T470\BCDEMO' cannot be run, because the database’s application version '130581' is greater than or
equal to the platform version '130581'.
However my server instance started without issues and the upgrade of System and Base app was also a success.
Does this mean that upgrading from 15.1->15.2 we dont have to do a Database Conversion?
If Yes, then this information should clearly be stated in upgrade manual.
(We are dealing with precious customer databases here and any error with database during upgrade makes the blood pressure rise dramatically.-)

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

ID: e71477e4-f2ea-1481-7597-29b324bd4f57
Version Independent ID: a2bb3a05-e5c1-d9f7-f47f-d2f34c4a91ea
Content: Install an update - Business Central
Content Source: dev-itpro/upgrade/upgrading-cumulative-update-v15.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Upvoting my question:
Does this mean that upgrading from 15.1->15.2 we dont have to do a Database Conversion?

Hello, Thanks for the feedback!
We did some investigation and can also reproduce the issue. I understand the confusion, and the article needs to be fixed to reflect the 15.1 to 15.2 update. The short answer is that when going from 15.1 to 15.2, you do not have to run the database conversion. No harm is done if you do run the cmdlet though.
A database conversion is required when schema changes have been made to the system tables, which is not the case from 15.1 to 15.2. However, it is the case when going from 15.0 to 15.1 or from 15.0 to 15.2, so you must run the database conversion.  When a database conversion is required, you will not be able to start the BC server instance against the database. If you try, you will get an error that the database must be converted.
The error thrown by the cmdlet is misleading for a couple reasons. First, it is more of an informational message, and it registers as a warning in event log. Also, the “application version“ shown in the message is actually the value of the databaseversionno column in the dbo.$ndo$dbproperty table of the application database. There is also a hard-coded version in the platform. We increase the hard-coded platform version for an update whenever schema changes have been made to system tables. When you run the Invoke-NAVApplicationDatabaseConversion cmdlet, it compares the databaseversionno value to the hard-coded platform version. If the databaseversionno value is less than the platform version, then the conversion will run.
I hope this answers your question, otherwise let us know. We will update the article in the meantime. Thanks!

Hello, The article has been updated to make this more clear. The update will be published soon. We will close this issue for now. If you have more feedback, we will reopen it. Thanks!


mkdir for current terraform version fails because -p flag is absent

https://github.com/Flaconi/docker-atlantis-terragrunt/blob/eb3111dd622d4d8cc9b708c9962d518234b685e1/Dockerfile#L29
Error screenshot

This is happening when I am building altantis image with --target alpine. If I don't pass this arg, then final image stage is debian based in atlantis. And that fails at your Dockerfile apk command step.

@romeshb29 since directory structure in base image ghcr.io/runatlantis/atlantis was changed - creating this repositories become obsolete. It was fixed in #69


Retry button - for finding Dropbox folders located on external drives

Is your feature request related to a problem? Please describe.
I have my Dropbox folder on an external drive. When I reboot, Maestral always launches before the drive has had a chance to mount, so I get a popup that Maestral can't find my Dropbox folder every time I restart, which is annoying when the only issue is the small time gap between Maestral launching and the drive mounting successfully.
Describe the solution you'd like
It would be great to add a "Retry" button to the dialogue box that pops up, so that Maestral can simply try to find the existing folder again when it has had a chance to mount,
Describe alternatives you've considered
None of the existing options in the dialogue box seem appropriate for this - I don't want to move the folder, or do anything that will trigger an unnecessary rescan or resync. I just want Maestral to retry the existing folder location, once I know that drive has mounted and is good to go.

None of the existing options in the dialogue box seem appropriate for this

I would argue that the "Quit" option is appropriate, followed by starting Maestral again once the drive was mounted. That being said, a retry button certainly would be an option.
The most elegant solution would be to create you own startup entry (using launchd on macOS, systemd or an XDG desktop entry on Linux) which either waits explicitly until the drive is mounted, or which waits a constant amount of time after login before starting Maestral. This would remove the need to press any button at all.

Agreed a customised startup with launchd would be great, but it's a bit of an ask for most people (including me) to learn OS tools like that, when a Retry button feels just as elegant in this situation. Quit & restart is the least elegant option, but it's the one I'm using for the moment.

https://github.com/samschott/maestral/issues/846#issuecomment-1450915473

or which waits a constant amount of time after login before starting Maestral. This would remove the need to press any button at all.

@samschott, time-based solutions simply don't work on slow hardware. It would need to verify that all drives have been mounted (of course, in addition to the retry button since unmounture at any time remains possible).


E2E tests for multi-token send flow

Description
Updates the E2E tests to use the multi-token send flow, built on top of #2289.
Other changes
Additional tests for deeplink payments.
Tested
Tested locally on iOS and in CI on Android
How others should test
This does not need to be tested by QA. For reviewers please check that the e2e tests are passing in CI and that the tests run locally on Android and iOS.
Related issues

Fixes #1775

Backwards compatibility
Yes

Hey @MuckT since NA is mentioned in how other should test section we are skipping this PR
Thanks