Check if the cached temp conf file still exists before using it.

On some systems older unused temp files get cleaned up regularly. So,
we cannot rely on the availability of the temp_files in long running
processes.

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   93.36%   93.36%
=======================================
  Files          11       11
  Lines         829      829
=======================================
  Hits          774      774
  Misses         55       55

Impacted Files
Coverage Δ

config/kube_config.py
91.86% <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 9213876...80c2525. Read the comment docs.


tnum font feature being stripped from Noto Sans

This is an odd one, but I’ve tried to eliminate everything else I can think of. I’ve attached a Noto Sans woff file to this issue:
NotoSansLatin-Regular.woff.zip
This was prepared from the normal Noto Sans Latin Regular ttf by running it through fonttools to strip most font features and save it as a woff, leaving it with liga, tnum, zero and kern.
The next step in our pipeline is to subset it by running it through subset-font and export it as a woff2. The code for this is as simple as you’d expect:
  const glyphs = glyphsFromUnicodeRange(unicodeRange);
  const result = await subsetFont(font, glyphs.join(''), {
    targetFormat: 'woff2',
    preserveNameIds: true
  });

At this point, the tnum feature is lost from the font.
This wasn’t an issue with the older version of Noto we were using (forked ~5 years ago), but has cropped up when upgrading to a newer version. I’ve tested various versions of subset-font back to 1.7.1 to see if it’s a recent bug, but no luck. Fonttools doesn’t seem to be the issue either, as excluding it from the pipeline doesn’t stop the tnum stripping from the subset-font command. My best guess is that the way tnum has been specified in Noto is now out of spec enough for harfbuzzjs or subset-font to trip on it.
I’ve been verifying the end state with https://wakamaifondue.com/beta/ so it’s I guess possible that there’s a bug there?
Any ideas?
(Side note: me or @bjrn should probably work on a layoutFeatures contribution to this project at some point so that we can skip our usage of fonttools entirely, but that’s a seperate issue.)

Hmm, I think the issue might be that the Harfbuzz subsetter doesn't support this yet.
I can confirm that the font you provided does indeed contain a tnum feature tag:
$ ttx -o - testdata/NotoSansLatin-Regular.woff | grep FeatureTag
[...]
Dumping 'GPOS' table...
        <FeatureTag value="kern"/>
        <FeatureTag value="kern"/>
        <FeatureTag value="kern"/>
        <FeatureTag value="kern"/>
        <FeatureTag value="kern"/>
Dumping 'GSUB' table...
Dumping 'STAT' table...
        <FeatureTag value="liga"/>
        <FeatureTag value="tnum"/>
        <FeatureTag value="zero"/>

I can also confirm that it get stripped by subset-font. But trying to explicitly tell the harfbuzz subsetter to preserve it doesn't help:
diff --git a/index.js b/index.js
index b46f4e5..0386963 100644
--- a/index.js
+++ b/index.js
@@ -77,6 +77,12 @@ async function subsetFont(
     }
   }

+  const inputLayoutFeatureTags = exports.hb_subset_input_set(
+    input,
+    6 // HB_SUBSET_SETS_LAYOUT_FEATURE_TAG,
+  );
+  exports.hb_set_add(inputLayoutFeatureTags, HB_TAG('tnum'));
+
   if (noLayoutClosure) {
     exports.hb_subset_input_set_flags(
       input,

I tried compiling the hb-subset CLI tool, and unfortunately it seems to have the same issue, even when explicitly telling it to include the tnum feature:
$ ./build/util/hb-subset --layout-features+=tnum ../subset-font/testdata/NotoSansLatin-Regular.ttf --text=foobar0123456789 -o hbsubsetted.ttf
$ ttx -o - hbsubsetted.ttf
[...]
Dumping 'GPOS' table...
        <FeatureTag value="kern"/>
Dumping 'GSUB' table...
Dumping 'STAT' table...
        <FeatureTag value="liga"/>

You probably know more about tnum than I do. Does it look like I'm doing something wrong? At this point I'm not sure if the feature is missing from hb-subset (and thus isn't available for subset-font either), or if I'm making some kind of rookie mistake :thinking:

Thanks so much for spending the time to test and confirm, really appreciate it.
I agree that this is either a harfbuzz / hb-subset bug or an unexpected behaviour. So I’ll file an issue with them to see if we can resolve it one way or another.

Great! Let me know what you find out and if/when there's something we can do in subset-font :sun_with_face:

As discussed on harfbuzz, the primary cause for my confusion turned out to be a bug in the original font, followed up by a secondary problem with fonttools 🤦♂ This can be closed.

I noticed that subset-font already hardcodes the equivalent of --font-features=* here, so we shouldn't need to change anything here unless we want to offer stripping features.


Missing Icons in Gutter

Hello,
I'm trying out nvui and its been nice.
One issue I am having is I place diagnostic glyphs in the gutter. They seem to have some trouble rendering:

vim.api.nvim_command('sign define DiagnosticSignError text=🄴  texthl=Error linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignWarn text=🅆  texthl=Warning linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignInfo text=🄸  texthl=Warning linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignHint text=🄷  texthl=Warning linehl= numhl=')

The above are the configuration lines. I believe these are just UTF characters as they are rendering right here on GitHub. Any idea?

I tried to set guifont to my normal patched font which I know exists on my system.
I always get the error message "Could not find font for family Monospace"

Yup im sure, since neovide and goneovim work fine and can display those UTF-8 symbols with the same config i use for nvui


Missing parameter for seo()->setValue in the Docs

After struggling with setting the value for a new meta-tag, I realized the Docs are missing a parameter under
https://www.baumrock.com/en/processwire/modules/rockfrontend/docs/seo/#setvalue
Should be
$rockfrontend->seo()
  ->setValue("foo", $page->title);

instead of
$rockfrontend->seo()
  ->setValue($page->title);

In my opinion an additional example with both functions together could be helpful:
$rockfrontend->seo()
  ->setMarkup("foo", "<meta property='foo' content='{value:20}'>")
  ->setValue("foo", $page->title);

Thanks for RockFrontend, @BernhardBaumrock !

Thank you very much @inreti-sb  :) I've pushed it to the dev branch and it will be merged soon


OpenSSL 3.0: Compiler error with gcc 12.2.0 for x86_64 and lp64 data model

With OpenSSL 3.0, I get a compile error in aes_x86core.c, when using gcc 12.2.0 for a x86_64 target and lp64 data model.
crypto/aes/aes_x86core.c:89:28: error: conflicting types for 'u64'; have 'long long unsigned int'

crypto/aes/aes_local.h:27:18: note: previous declaration of 'u64' with type 'u64' {aka 'long unsigned int'}

there are two different typedefs for u64:
aes_local.h:
typedef uint64_t u64;
aes_x86core.h:
#if (defined(_WIN32) || defined(_WIN64)) && !defined(__MINGW32__)
typedef unsigned __int64 u64;
#define U64(C)  C##UI64
#elif defined(__arch64__)
typedef unsigned long u64;
#define U64(C)  C##UL
#else
typedef unsigned long long u64;
#define U64(C)  C##ULL
#endif

for x86_64 with lp64 data model, aes_x86core.h defines unsigned long long for u64, which is wrong and conflicts with the type defined in aes_local.h
Is this a bug or is there something wrong with my configuration?
(It worked with OpenSSL 1.1.1n)

This does not affect 1.1.1 branch.

Fix in 20043

Hmm, the file actually isn't used by OpenSSL build at all and should be removed.

I am not sure how is your build triggering an error on the file as it should not be built at all.

There was a problem with my build configuration. Without aes_x86core.c it is working fine.
Thank you!


how can I set selected date as marked

I want to set selected date of month with different background, but how will I do with your day decorator

hello, you got to set selected date programatically?


Materials for using WMS

Tracker for reviewing/enhancing materials for Exploring WMS (w/ ncWMS & Cartopy extensions)

Try to fix color map.


Announcement: Rollback of 50.13.3 CLI 7.84.2

We had to roll back yesterday's CLI release because it caused multiple issues for customers. In the spirit of transparency, we want to explain what happened and how we plan to fix it.
As many of you know, we’ve made great progress in open sourcing the CLI (https://developer.salesforce.com/blogs/2020/05/open-sourcing-salesforce-cli.html); stay tuned for a blog post updating the community soon. We’re committed to transitioning the CLI to be fully open-sourced. However, the transition involves moving many commands and builds to multiple public repositories and environments. We are also currently releasing the CLI using both the old and new system.
We haven’t released a new version of the CLI in over a month because of Dreamforce and the holidays. This delay created a release with a lot of changes (https://github.com/forcedotcom/cli/tree/main/releasenotes#50133-january-14-2021---cli-7842). Nonetheless, the release candidate sat in `latest-rc' for over a week to allow for testing, and everything seemed to work correctly in our CI and testing environments.
However, when the CLI was promoted Thursday, January 14, 2021, the archives and plug-in versions were pointing to incorrect and incompatible dependency versions, which caused a variety of regressions. We are still investigating what exactly happened and why our tests didn't catch the issues. We're working to ensure that the new build system will prevent these regressions from happening in the future.
We plan to fix all the dependency issues and build a new latest-rc version next week, and then promote it on Thursday, January 28, 2021.
We apologize for the inconvenience.

Is there a way I can revert back to previous version?

Is there a way I can revert back to previous version?

@amphro Could you clarify what it means that the 50.13.3 release was rolled back? I ran sfdx update this morning, and ended up with version 50.13.3 of the salesforcedx plugin. I had seen this announcement and it took me quite some time to realize that I have the wrong version, since I was expecting that sfdx update would not install a release that was rolled back.
And to echo the previous comment -- now that I have the wrong release, how do I install the previous one?

@amphro Could you clarify what it means that the 50.13.3 release was rolled back? I ran sfdx update this morning, and ended up with version 50.13.3 of the salesforcedx plugin. I had seen this announcement and it took me quite some time to realize that I have the wrong version, since I was expecting that sfdx update would not install a release that was rolled back.
And to echo the previous comment -- now that I have the wrong release, how do I install the previous one?

@davisagli follow these instructions then install from here.
What a pain this is...

@davisagli follow these instructions then install from here.
What a pain this is...

@davisagli @sjurgis I was able to rollback successfully by reinstall the salesforcedx plugin.
sfdx plugins:install salesforcedx@latest
This put it back to 50.12.

@davisagli @sjurgis I was able to rollback successfully by reinstall the salesforcedx plugin.
sfdx plugins:install salesforcedx@latest
This put it back to 50.12.

The stable channel, which sfdx update points to, seems to be on different versions... I can look into that a little more.

The stable channel, which sfdx update points to, seems to be on different versions... I can look into that a little more.

@amphro please could we have some clarification on which versions are broken and which are ok?
As far as I can tell I currently have 7.84.2 / 50.13.3 which I must have received by auto update as I haven't run SFDX manually. This is apparently the broken version that was rolled back but appears to be working? (though obviously there may be commands that are broken that I don't use on a day to day basis).
One of my team installed SFDX from the website (https://developer.salesforce.com/tools/sfdxcli) earlier which has 7.83.0 / 50.9.1 - this version is not mentioned as being the broken version but does have the changed sfdx force:auth/sfdx auth changes - which breaks all of our tooling. There are no release notes for this version on the release notes page: https://github.com/forcedotcom/cli/tree/main/releasenotes#50133-january-14-2021---cli-7842. I've run sfdx update manually on his machine and he's been upgraded to the same version as me 7.84.2 / 50.13.3 where sfdx force:auth seems to work.
My findings are that 7.83.0 / 50.9.1 is broken but not mentioned anywhere in this thread and doesn't have any release notes - this is the version being distributed from the Salesforce website. It can be updated to 7.84.2 / 50.13.3 by sfdx update (and will presumably happen automatically after a while?), which is apparently broken but doesn't appear to be me.
Please could we have some clarification?

@amphro please could we have some clarification on which versions are broken and which are ok?
As far as I can tell I currently have 7.84.2 / 50.13.3 which I must have received by auto update as I haven't run SFDX manually. This is apparently the broken version that was rolled back but appears to be working? (though obviously there may be commands that are broken that I don't use on a day to day basis).
One of my team installed SFDX from the website (https://developer.salesforce.com/tools/sfdxcli) earlier which has 7.83.0 / 50.9.1 - this version is not mentioned as being the broken version but does have the changed sfdx force:auth/sfdx auth changes - which breaks all of our tooling. There are no release notes for this version on the release notes page: https://github.com/forcedotcom/cli/tree/main/releasenotes#50133-january-14-2021---cli-7842. I've run sfdx update manually on his machine and he's been upgraded to the same version as me 7.84.2 / 50.13.3 where sfdx force:auth seems to work.
My findings are that 7.83.0 / 50.9.1 is broken but not mentioned anywhere in this thread and doesn't have any release notes - this is the version being distributed from the Salesforce website. It can be updated to 7.84.2 / 50.13.3 by sfdx update (and will presumably happen automatically after a while?), which is apparently broken but doesn't appear to be me.
Please could we have some clarification?

My team and I are not able to Authorize an org on VSCode. Is this issue related?
We are having this issue since friday 22 january. We are on Ubuntu 20.04.

My team and I are not able to Authorize an org on VSCode. Is this issue related?
We are having this issue since friday 22 january. We are on Ubuntu 20.04.

@amphro - is there any update on this?
The version that this post says has been rolled back hasn't, it's still the version users get auto updated to.

@amphro - is there any update on this?
The version that this post says has been rolled back hasn't, it's still the version users get auto updated to.

I was able to get it to work by removing the npm version of sfdx-cli and installing the executable directly. This solves the issue we were having during authorize an org where it was not doing the callback to localhost:1717.
If you perform the above solution, you may encounter an issue with port 1717 already open. Simply kill it and restart
``
lsof -i :1717
kill -9 <PID_HERE>

I was able to get it to work by removing the npm version of sfdx-cli and installing the executable directly. This solves the issue we were having during authorize an org where it was not doing the callback to localhost:1717.
If you perform the above solution, you may encounter an issue with port 1717 already open.
Though, my bigger concern is that Salesforce think 7.84.2 / 50.13.3 has been rolled back and the release notes say it has been rolled back. However, it hasn't been rolled back - it's still the version that auto-updating will install. Including new users going to the Salesforce official website, downloading SFDX and installing it - that installs a more broken version 7.83.0 / 50.9.1 that doesn't have any release notes then auto updates to 7.84.2 / 50.13.3.
As it happens 7.84.2 seems to be ok for me but I have a large team of developers using SFDX that will all be on this version. I want to be prepared for any issues and know if I need to get them all to manually install an older version (which will be very painful). That's where I'm hoping @amphro can help.

Thanks for the info @kevanmoothien.
Though, my bigger concern is that Salesforce think 7.84.2 / 50.13.3 has been rolled back and the release notes say it has been rolled back. However, it hasn't been rolled back - it's still the version that auto-updating will install. Including new users going to the Salesforce official website, downloading SFDX and installing it - that installs a more broken version 7.83.0 / 50.9.1 that doesn't have any release notes then auto updates to 7.84.2 / 50.13.3.
As it happens 7.84.2 seems to be ok for me but I have a large team of developers using SFDX that will all be on this version. I want to be prepared for any issues and know if I need to get them all to manually install an older version (which will be very painful). That's where I'm hoping @amphro can help.

Hey @gdman - apologize for the delay in communication. Here is where we stand:
There are three different install paths:

NPM
Unversioned archives
Versioned archives
The first two experienced the problem and have been rolled back. In other words, the NPM latest tag now points to a previous version and the unversioned archives have been overwritten with the previous version.

The third one, which is used for the auto-update, apparently does not have the same problem. There are stable channel files that point to a version that tells the CLI which version to auto-update to. The time we update those files is in our build to a new version. i.e. roll forward. I looked into rolling those back and I really don't want to update those pointers/shas manually if I don't have to. It seems easy to mess them up.
Assuming that the version is working for people who are auto-updated, I'm not going to change them and they will be updated next week.
Yes, you heard that right, next week. We can't release tomorrow for some reasons outside our control. This means we will update everything next Friday. We will still be publishing the latest-rc npm channels tomorrow.

Hey @gdman - apologize for the delay in communication. Here is where we stand:
There are three different install paths:

NPM
Unversioned archives
Versioned archives
The first two experienced the problem and have been rolled back. In other words, the NPM latest tag now points to a previous version and the unversioned archives have been overwritten with the previous version.

The third one, which is used for the auto-update, apparently does not have the same problem. There are stable channel files that point to a version that tells the CLI which version to auto-update to. The time we update those files is in our build to a new version. i.e. roll forward. I looked into rolling those back and I really don't want to update those pointers/shas manually if I don't have to. It seems easy to mess them up.
Assuming that the version is working for people who are auto-updated, I'm not going to change them and they will be updated next week.
Yes, you heard that right, next week. We can't release tomorrow for some reasons outside our control. This means we will update everything next Friday. We will still be publishing the latest-rc npm channels tomorrow.

@amphro While cleaning up the npm versions, is it possible to deprecate/unpublish
47.15.1 (a year ago)?
This version seems to not follow any of your versioning patterns.
Background: I'm currently on<EMAIL_ADDRESS>which appeared to me to have been the latest stable version for the past weeks, but npm (respectively npm-check and renovatebot) are trying to update to 47.15.1 😃.

@amphro While cleaning up the npm versions, is it possible to deprecate/unpublish
47.15.1 (a year ago)?
This version seems to not follow any of your versioning patterns.
Background: I'm currently on<EMAIL_ADDRESS>which appeared to me to have been the latest stable version for the past weeks, but npm (respectively npm-check and renovatebot) are trying to update to 47.15.1 😃.

@amphro - Thanks for all the information, that's really useful.
We found the 7.83.0 / 50.9.1 version has the change to move sfdx force:auth:* to sfdx auth:* but doesn't have backwards compatibility so the sfdx force:auth:* commands don't work - this breaks our build scripts. 7.84.2 / 50.13.3 fixes this so I can just tell any users who install from the website to run sfdx update.
Thanks again for the response.

@amphro - Thanks for all the information, that's really useful.
We found the 7.83.0 / 50.9.1 version has the change to move sfdx force:auth:* to sfdx auth:* but doesn't have backwards compatibility so the sfdx force:auth:* commands don't work - this breaks our build scripts. 7.84.2 / 50.13.3 fixes this so I can just tell any users who install from the website to run sfdx update.
Thanks again for the response.

@amtrack I noticed that a while back too, but I can't unpublish it because of NPM rules. I didn't even know or think to try deprecating the version. I'll give it a go.

@amtrack I noticed that a while back too, but I can't unpublish it because of NPM rules. I didn't even know or think to try deprecating the version. I'll give it a go.


feature: $deepStateRedirect.reset() with parameter for stateParameter

as discussed in #64

Did i miss something?

@readme42 no, you didn't miss something.  sorry I just forgot to merge it


Make code compile with all warnings enabled

I was moved by Karthik's heroic efforts to systematically get rid of all unused variables, and thought I'd try to revive my previous attempts to make it work for realz this time.
This is with the corresponding branch on krml
Note that i) the code compiles with all warnings removed from Makefile.basic and ii) krml now inserts IGNOREs for unused function parameters too
Thoughts, comments, etc. @karthikbhargavan @R1kM @polubelova @franziskuskiefer

Oh and there's a little bit of noise in this PR because hints & dist haven't run in a while.
All changes of the form
KRML_HOST_IGNORE((void *)(uint8_t)0U);

are covered by another fix in krml that has been merged already.

Thanks, looks like a lot of warnings are gone, that's great!
There are a bunch more though that would be good to squash.
There are still non-portable include paths
warning: non-portable path to file '"Lib_Memzero0.h"'; specified path differs in case from file name on disk [-Wnonportable-include-path]
warning: #include "lib_memzero0.h"

There are a ton of implicit, lossy conversions (using -Wconversion), e.g.
krml/internal/types.h:99:
warning: implicit conversion loses integer precision: 'uint128_t' (aka 'unsigned __int128') to 'uint64_t' (aka 'unsigned long long') [-Wimplicit-int-conversion]

Compiling EverCrypt_AEAD.c on a machine without AES-NI and all the required features gives unused parameter warnings on all the AES functions, e.g.
warning: unused parameter 'k' [-Wunused-parameter] create_in_aes256_gcm(EverCrypt_AEAD_state_s **dst, uint8_t *k)

I have never been happier to see my painful work being obsoleted. Looks good overall, but yes, let's do a little bit more and squash all the warnings we can. It is much easier to do this with tooling.

There are still non-portable include paths

Is that a leftover old file that hasn't been removed? I thought Lib_Memzero0.h was gone for good after I renamed it for you into lib_memzero0.h ... is that in dist/gcc-compatible?

There are a ton of implicit, lossy conversions (using -Wconversion), e.g.

The one you posted is in a hand-written file, independent from this PR: https://github.com/FStarLang/karamel/blob/master/krmllib/c/fstar_uint128_gcc64.h -- if you know how to fix this, you can submit PRs over there directly and the next refresh of the code will pick them up.

Compiling EverCrypt_AEAD.c on a machine without AES-NI and all the required features gives unused parameter warnings on all the AES functions, e.g.

Ah, yes, that's a tricky one because the use is under an #ifdef -- that one might require some refactoring, or a manual call to LowStar.Ignore in the meanwhile

Is that a leftover old file that hasn't been removed? I thought Lib_Memzero0.h was gone for good after I renamed it for you into lib_memzero0.h ... is that in dist/gcc-compatible?

It's in a bunch of files, e.g.
https://github.com/hacl-star/hacl-star/pull/861/files#diff-a0d77c72d84485650f708e3c8920bee10bfc074dec13a9367c00ad179b9eaa99L29
I see it in at least Hacl_Hash_Blake2s_128.c, Hacl_Hash_Blake2.c, and Hacl_Ed25519.c as well.

The one you posted is in a hand-written file, independent from this PR: https://github.com/FStarLang/karamel/blob/master/krmllib/c/fstar_uint128_gcc64.h -- if you know how to fix this, you can submit PRs over there directly and the next refresh of the code will pick them up.

There are these two. I'm not sure if there's more https://github.com/FStarLang/karamel/pull/382

Ah, yes, that's a tricky one because the use is under an #ifdef -- that one might require some refactoring, or a manual call to LowStar.Ignore in the meanwhile

Yeah that's a little harder. Another option would be to have the ifdef on the outside and a second function that ignores all the arguments.

Regarding your warning:
warning: non-portable path to file '"Lib_Memzero0.h"'; specified path differs in case from file name on disk [-Wnonportable-include-path]
warning: #include "lib_memzero0.h"

where is Lib_Memzero0.h coming from? I don't see it in HACL*
jonathan@absinthe:~/Code/everest/hacl-star (main) $ find . -name 'Lib_Memzero0.h'

returns nothing. The warning says #include "lib_memzero0.h" finds Lib_Memzero0.h on an OSX machine, but we don't have Lib_Memzero0.h anywhere in HACL*.

where is Lib_Memzero0.h coming from? I don't see it in HACL*

Ah, I guess these files don't get updated properly on Mac because they are considered identical. Going in manually and deleting everything seems fine. So this shouldn't be an issue.

#863 has a more recent version of the diff, closing this one


Remove Pandas dependency

For a lighter implementation, we should use a standard library to read the CSV files and use numpy arrays instead of a dataframe.

Not a critical priority so closing for now.


OAR: add async to _submit_job method

_submit_job is awaited by the Job.start.

Thanks a lot for fixing this! This bug was very likely added with the SpecCluster refactor (#307) and not noticed since the 0.7 release ...
I added an entry in the changelog, so merging this!

As discussed IRL, if you ever get the chance to add CI for OAR, it would be super appreciated!
I would also make OAR more of a first citizen in dask-jobqueue (as SLURM, SGE and PBS) and help avoid similar problems in the future. We use docker-compose for your CI, you can have a look how it is done for SLURM, SGE and PBS: https://github.com/dask/dask-jobqueue/tree/master/ci.
While I am at it, one of the limitation of OARCluster: in the OAR cluster I have access to, oarsub is not installed on the compute nodes. My understanding is that this is the default setup in OAR.
If you create your OARCluster on a compute node (rather than on the login node, which is easier but not completely best practice compliant), a work-around as the one mentioned https://github.com/dask/dask-jobqueue/issues/333#issuecomment-530263090 is probably necessary.
If it turns out that oarsub is not installed on the compute nodes on your OAR cluster either, we could add a parameter to OARCluster e.g. login_node_host or something similar to make OARCluster easier to use.


ctapipe.image.cleaning.tailcuts_clean speed up factor ~10

Same as #665, but this time doing only the smallest possible diff to reach the result.
No additional tests, so no proof that this is faster than the previous version. Proof was shown in #665
Regarding readability vs speed, I think some people might even like matrix notation better than the previous version, but who knows.
One peculiar thing is this:
Before:
boolean_vector = (Matrix & Vector).any(axis=1)
integer_vector = (Matrix & Vector).sum(axis=1)

Now:
boolean_vector = Matrix.dot(Vector)
integer_vector = Matrix.dot(Vector.view(np.byte))

This might actually confuse the readers ... "Why is this view needed here?? WTF?"
The point is obvious for us when I write it down here ... but a month from now I might have forgotten it ... see this code and remove the view, since I think it is superfluous.
Luckily there is a test, that immediately fails, when this view(byte) is removed, so we have a test harness for this peculiar piece of code, which is really good.
Of course instead of view(byte) also one could have written astype(int) or so ... gives the same result. but view is faster than astype and a numpy boolean array is a char array in the background, so this view was the fasted version I found. It still costs ~430ns which is a lot, given that the view is not actually doing anything, it is just needed so that the result of the later dot-product is not cast

Now that I think about it, maybe it is worth to just grep for all use cases of neighbor_matrix and see if the sparse version can be dropped in, without bothering about profiling the possible impact on Performance... just assuming it might help.
Not good working style but hey... the neighbor matrix is really sparse by design.

Turns out neighbor_matrix was only used in one more function dilate() in the same file. So I just used it there as well...hope that is file for you.

In fact when I originaly implemented the neighbor_matrix, I had used a sparse matrix, but it made things much slower for some reason (a factor of around 20x if I recall) - not sure why it is different now! It could be due to differences in versions of numpy and whether or not some optimizations were enabled.

Interesting.... I remember having used sparse matrices in other projects of mine some years ago, and they performed as expected.
I assume you are aware of these different types of sparse matrices and the fact that not all of them are good at dot-product...
Anyway thanks for the quick merge.


Consolidate Inbox and Outbox Pages into Messages

Is your feature request related to a problem? Please describe.
At the moment, Inbox and Outbox are independent routes to PASS, but can be consolidated to just one page called Messages.
Describe the solution you'd like
Consolidate Inbox and Outbox pages into Messages. Users would then be able to toggle between inbox and outbox components without routing using some sort of button or internal navigation within Messages.

@timbot1789 Are you currently working on this? No one has been assigned to it yet.

Have completed the merger of this issue into Development. Closing issue.


Memory Error

Hello,
I get a "Memory Error" when converting an ansys .msh to a vtu-binary.
In fact, it's a 3d volume mesh, but the code output says: "number of triangles."
Is it possible that it's recognizing the wrong kind of mesh?
Thank You,
Vitaly

Certainly possible. With the mesh, it's impossible to properly debug though.

Closing for lack of response. Feel free to reopen (ideally with a mesh that reproduces the problem).


Broken link to Track after login

Story
After login in, when the user chooses Track it gives a 404 error because of a double dash in the URL.
https://dev.tolatables.tola.io//login/tola.
On the other hand, we should be flexible in the configuration and allow to set the Track URL ending with slash or without it.
Acceptance criteria
GIVEN I am logged in
AND the developer set TOLA_ACTIVITY_URL ending with a slash or without it
THEN the resulting address should have just one slash

@Menda I am experiencing this error for some situations in Staging:
Actions: Clear cache > Login as Microsoft User OR Login as Tola > Click Track option
Result: Error

I can reproduce. This belongs to a different kind of bug, so I will create a new Blocker for it. If the Acceptance Criteria for this ticket is met, then we can mark this as done.


servedocs improvements

First suggestion: https://github.com/asprionj/LiveServer.jl/issues/43#issuecomment-481399735
Then, we should add tests for it to get coverage up again.
Should we move it to a separate file? It does not belong in the main module file LiveServer.jl, but somehow neither in server.jl...
A nice feature would be that it automatically detects new files. For this, we could use the coreloopfun and a marginally modified FileWatcher with one additional field holding the path to the docs folder we're serving. This could be used in the loop-function (e.g. on every 10th call or so) to check for new files against is_watched.

This is your brainchild, so I let you decide what to do and what to leave. I'll help as time allows me to. ;-)

With respect to your 3d point, I think there's now enough to have a utils.jl file which contains example, verbose and servedocs.
I agree with the rest. Tests are somewhat artificial here since there's not much that's being done in the function that isn't tested by serve but I can check.
And yes for new files with coreloop. In fact that's pretty much why I use coreloop in JuDoc.


Fixing clash with multilingual plugin. Use 'baseurl_root' if posible for assets path.

[ ] I have added or updated the specs/tests.
[x] I have verified that the specs/tests pass on my computer.
[x] I have not attempted to bump, or alter versions.
[ ] This is a documentation change.
[x] This is a source change.

Description
What issue are you trying to resolve?
use 'baseurl_root' if posible for assets path.
This fixes the issue with the plugin "jekyll-multiple-languages-plugin" opened here: https://github.com/envygeeks/jekyll-assets/issues/507
This pull request has also been submitted into to the master branch https://github.com/envygeeks/jekyll-assets/pull/602

Is baseurl_root a default Jekyll configuration?

Is baseurl_root a default Jekyll configuration?

No. It's the 'alias' the plugin jekyll-multiple-languages-plugin uses before they overwrite base_url:
jekyll-multiple-languages-plugin.rb Line 110
I know this pull request is very coupled with another plugin but it's harmless and it might be a good practice going forward for Jekyll plugins.

Harmless is subjective. If I didn't know it was an "alias" now, I won't know in 10 months, I don't use that plugin.  Add a note inside of the source indicating why it's there, and I'll mull it over  this weekend, though at this point I still Stan not having to maintain hacks for other people's software.

Harmless is subjective. If I didn't know it was an "alias" now, I won't know in 10 months, I don't use that plugin. Add a note inside of the source indicating why it's there, and I'll mull it over this weekend, though at this point I still Stan not having to maintain hacks for other people's software.

I know it's not the most elegant solution and the comment is a bit of a smelly code specially noticeable in your such a well structured code. But maybe it's tolerable.


KingArt KING-M4 compability

Hi, thanks for very nice work,
i have an wall dimmer switch in eweelink app, that does not appear in HA, any chance there is a way to intergrate it?
KingArt, model KING-M4, firmware: 2.7.0 (PSF-BTA-GL)

Duplicate #26

Supported


Ensure ModelIdentifier use write PDO connection.

When working with SerializesModels, it is possible that when Queue attempts to work on the job
the model is yet available on the read PDO connection, therefore findOrFail() would just fail,
On heavy server load, it is possible that the latency is big enough the max out the number of attempts
configured for queue.
Signed-off-by: crynobone<EMAIL_ADDRESS>

Please send this bug fix to 5.1.


Project Not working

I downloaded entire project and copied Examples folder to new project. then I setup pod and run the project but got 11 errors. Tried to do by some quick suggestions but still not working.

Some examples in the examples folder require some external dependencies. It is best to download the entire project and run CollectionKit.xcodeproj since it has the necessary dependencies setup.

I did the same thing. But unfortunately it's not working.
On Thu, Dec 28, 2017 at 1:37 AM, Luke Zhao<EMAIL_ADDRESS>wrote:

Some examples in the examples folder require some external dependencies.
It is best to download the entire project and run CollectionKit.xcodeproj
since it has the necessary dependencies setup.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SoySauceLab/CollectionKit/issues/41#issuecomment-354170686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZq3tYEyz9lJF2WSbv9qFZkw0l0WzzAHks5tEqOegaJpZM4RMpEO
.


chore: release 1.0.1

:robot: I have created a release *beep* *boop*
1.0.1 (2019-06-14)
Bug Fixes

docs: move to new client docs URL (#129) (689f483)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/nodejs-paginator/releases/tag/v1.0.1

The release build has started, the log can be viewed here. :sunflower:


headless builder fails when run on windows

At least as a github action, when one runs npx kui-build-headless on windows:
[webpack-cli] Invalid value '${MODE-production}' for the '--mode' option
[webpack-cli] Expected: 'development | production | none'

nevermind, i think this can be solved outside. the other client was using cross-env rather than cross-env-shell

Though we should probably remove npx kui-build-headless?


Monotonic growth and deletion

This looks great.  However, I don't see any way of pruning the database, so as clients create and edit docs, the persistence element will store an increasing amount of data in the attached database, with no option to ever prune it.  Potentially the volume of data could become enormous (this is also true of all the y-websocket variations I have seen).  This would be a problem if the code was used in a production environment with large numbers of users performing large numbers of edits.
What should be discarded and when will depend on the use case, but if I have understood this right, it wouldn't be possible to discard data using this backend as currently implemented.

Hey ... So if you look at the main branch ... updates are pruned when they are fetched by combining them into a single update if the number of updates are above a certain size. This is the same strategy as followed by y-leveldb. In the external_api_persistence branch, you can implement the backend api in such a way that it prunes updates while reading and/or writing ... (would suggest while reading because of the bature of reads and writes)


LDAP Connection

Hi, I'm building my environment like this:
version: '3.5'

services:
  cockpit:
    image: passwordcockpit/passwordcockpit:1.3.5
    volumes:
      - /passwordcockpit/upload:/var/www/html/upload
    user: '$UID:$GID'
    environment:
      TZ: America/Sao_Paulo
      APACHE_RUN_USER: www-data
      APACHE_RUN_GROUP: www-data
      PASSWORDCOCKPIT_DATABASE_USERNAME: passwordcockpituser
      PASSWORDCOCKPIT_DATABASE_PASSWORD: pass123
      PASSWORDCOCKPIT_DATABASE_HOSTNAME: database
      PASSWORDCOCKPIT_DATABASE_DATABASE: passwordcockpit
      PASSWORDCOCKPIT_BLOCK_CIPHER_KEY: pass123
      PASSWORDCOCKPIT_AUTHENTICATION_SECRET_KEY: pass123
      PASSWORDCOCKPIT_BASEHOST: https://<IP_ADDRESS>
      PASSWORDCOCKPIT_SWAGGER: enable
      PASSWORDCOCKPIT_SSL: enable
      PASSWORDCOCKPIT_AUTHENTICATION_TYPE: ldap
      PASSWORDCOCKPIT_ADMIN_PASSWORD: pass123
      PASSWORDCOCKPIT_UPLOAD_ACCEPTED_MIMETYPES: 'pdf'
      PASSWORDCOCKPIT_LDAP_HOST: <IP_ADDRESS>
      PASSWORDCOCKPIT_LDAP_PORT: 389
      PASSWORDCOCKPIT_LDAP_USERNAME: CN=svcLdap,CN=Users,DC=domain,DC=local
      PASSWORDCOCKPIT_LDAP_PASSWORD: pass123
      PASSWORDCOCKPIT_LDAP_BASEDN: DC=domain,DC=local
      PASSWORDCOCKPIT_LDAP_ACCOUNTFILTERFORMAT: (&(memberOf=CN=PassUsers,OU=MyGroups,DC=domain,DC=local)(samaccountname=%s))
      PASSWORDCOCKPIT_LDAP_BINDREQUIRESDN: 'false'
      PASSWORDCOCKPIT_LDAP_USER_ATTR_UNIQUE_IDENTIFIER: 'samaccountname'
      PASSWORDCOCKPIT_LDAP_USER_ATTR_NAME: 'givenname'
      PASSWORDCOCKPIT_LDAP_USER_ATTR_SURNAME: 'sn'
      PASSWORDCOCKPIT_LDAP_USER_ATTR_MAIL: 'mail'
      PASSWORDCOCKPIT_LDAP_USER_ATTR_PHONE: 'telephonenumber'
      PASSWORDCOCKPIT_DEBUG: 'true'
    ports:
      - "443:4343"
    depends_on:
      - database
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
        condition: on-failure

  database:
    image: mariadb:10.11.2
    #volumes:
      #/passwordcockpit/database:/var/lib/mysql
      #/passwordcockpit/backups:/backups
    user: '$UID:$GID'
    environment:
      MARIADB_ROOT_PASSWORD: pass123
      MARIADB_DATABASE: passwordcockpit
      MARIADB_USER: passwordcockpituser
      MARIADB_PASSWORD: pass123
    command: --character-set-server=utf8 --collation-server=utf8_unicode_ci
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
        condition: on-failure

However, I cannot log in to the system, neither with the user I entered to integrate with LDAP nor with another AD user.

Using an LDAP Search tool I confirm that my filter is correct:

Try with: PASSWORDCOCKPIT_LDAP_BASEDN: CN=Users,DC=domain,DC=local

Has the problem been solved?

This issue was closed because it has been inactive for 14 days since being marked as stale.


docs: Fix broken link in index.md

What does this implement/fix? Explain your changes.
Fix broken link to preprocessing section

Grande <3


[messageController] add messages in maskAppli and reformat

Everything said in title
:m:

I added a commit to have a larger medMessageError which allow to display a longer text

(and adapted the texts to follow the formulation of the other medMessageError)

Good!


Does not work with Open SUSE LEAP 15.2

Is your feature request related to a problem? Please describe.
C:\WINDOWS\system32>wsl.exe --list --online
The following is a list of valid distributions that can be installed.
Install using 'wsl --install -d '.
NAME            FRIENDLY NAME
Ubuntu          Ubuntu
Debian          Debian GNU/Linux
kali-linux      Kali Linux Rolling
openSUSE-42     openSUSE Leap 42
SLES-12         SUSE Linux Enterprise Server v12
Ubuntu-16.04    Ubuntu 16.04 LTS
Ubuntu-18.04    Ubuntu 18.04 LTS
Ubuntu-20.04    Ubuntu 20.04 LTS
Describe the solution you'd like
A clear and concise description of what you want to happen.
The SUSE Leap 42 listed is ancient and unsupported for security patches
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.

Here's some resources for troubleshooting opensuse as well as installing tumbleweed if that's of interest to you.
https://boxofcables.dev/why-do-apps-look-weird-on-wslg-on-opensuse/
https://boxofcables.dev/install-opensuse-tumbleweed-on-wsl/

@jimrome thanks for your interest in WSLg. For generic wsl question such as wsl --list --online, it is best to take those up on the core WSL project at http://github.com/microsoft/wsl. Please note that the various Linux distro publisher decide which of their distro they want to target and package for WSL... wsl --list --online gives you a list of distro that publisher have decided to package using a new package technology. You can also find additional WSL distro in the Microsoft App Store. It looks like OpenSUSE Leap 15.2 isn't available as a --install target, but it is available for install through the Microsoft App Store.


test: Sync bug 1882803 and ignore favicon request in network cache test

Requires https://bugzilla.mozilla.org/show_bug.cgi?id=1882803 to land first.
Updates a network.spec.ts test to ignore favicon requests.
Updates expectations for intermittents linked to 1907589 from FAIL, PASS to PASS

Note that will be using Firefox stable very soon so we will need to wait for fixes for longer.

Note that will be using Firefox stable very soon so we will need to wait for fixes for longer.

Oh good point, we shouldn't merge the test expectation changes. Would you still be OK with taking the fix for the test for now or do you prefer to wait until everything is in stable ?

I think the change to the test is valid, and we can merge that part.

Ok, I'll split the PR then, thanks!


Clarity about the what path references are relative to

Suggestion

🔍 Search Terms

references path relative
✅ Viability Checklist

My suggestion meets these guidelines:

[ x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x ] This wouldn't change the runtime behavior of existing JavaScript code
[ x] This could be implemented without emitting different JS based on the types of the expressions
[x ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Both https://www.typescriptlang.org/tsconfig#references and https://www.typescriptlang.org/docs/handbook/project-references.html aren't specific about what the string in path is relative to (the current tsconfig, the current working directory, rootDir, etc)
💻 Use Cases

I'm writing some build scripts around invocations of tsc with a lot of linking, aliasing, etc and I don't want to put absolute paths in the generated tsconfig files

IIRC all paths in a tsconfig are relative to the tsconfig.

I figured as much. But given:
https://www.typescriptlang.org/tsconfig#baseUrl and https://www.typescriptlang.org/tsconfig#paths
https://www.typescriptlang.org/tsconfig#rootDirs
https://www.typescriptlang.org/tsconfig#preserveSymlinks
I've run into issues before where those complicated the paths used in look up by tsc
But I also see  https://www.typescriptlang.org/tsconfig#files which I guess I took for granted my assumption that it's always relative to the tsconfig.json


pretty-printing xml can change its meaning

Markup.pretty_print knows which whitespace is significant in html. However for xml, it treats all whitespace as insignificant, which means that the pretty printed xml can have a different meaning from the initial xml. For instance, xml in .docx files store bits of the document's texts as elements like <w:t xml:space="preserve">a </w:t>, so any change of whitespace there changes the document.
It'd be nice for the library to behave more nicely. My use case is pretty printing xml in tests so it's easily diffed.
I wrote a couple of change to trim and pretty_print:

treat any node with node with the attribute xml:space as a phrasing element
allow the user to pass a function that's called on start_elements and can decide to have it treated like a phrasing element

But I don't know much about xml, so maybe it's best to discuss first.
The first one seems correct, but the second allows more control (in my case, leave all <w:t> elements alone, not just the ones that have xml:space="preserve" on them for instance, which would be easier to read).
Any thoughts about what's best?

As far as I know, the significance of whitespace is decided by each XML format. As a result, Markup can't reliably make decisions about whether whitespace is significant or not, and Markup's pretty_print for XML is meant essentially only for debugging purposes and does not aim to preserve the semantics of documents.
I thought the best way would be for users to define their own pretty-printers if they would like to pretty-print their formats in a way that preserves the meaning of whitespace. There may be other reasons for doing this too, as pretty_print is very basic (due, again, to not knowing anything about the meaning of what it is pretty-printing).

Even if you're debugging (I was testing, but that's not fundamentally different), "write your own pretty printer" is a non-trivial hurdle, especially if you're not very familiar with the library, and you might run into bugs of your own making.
The xml spec says, talking about the attribute xml:space:

the value "preserve" indicates the intent that applications preserve all the white space.

Now whitespace might be significant regardless even if it's not marked as such, so it may be better to ask the user to pass in a ~preserve_space_below:(name -> attrs -> bool) function to Markup.pretty_print, but that's much easier for the user than writing a custom pretty printer.

It would probably be useful to add a ?preserve_whitespace argument as you suggest, and expose default implementations for HTML and XML, with the XML one respecting xml:space="preserve". The default value of ?preserve_whitespace would be the HTML implementation for backwards compatibility and the most common usage, but it could also be improved slightly by examining the doctype if it is present in the signal stream.


scoreboard

Would it be possible to read a value from a scoreboard the same way {player} currently works, or store a value in a config file. So you can have item uses count a value up the more you use it which can be used in a command

There is a point where you're better of creating a real plugin, i'm not trying to create a second Skript here


Implement native bundle tag serializer serializeTags() function

The current implementation of serializeTags used by the data bundler depends on javascript librariestagparser and avsc. This PR allows the data_bundle functionality in ardrive-dart to be used on platforms other than web. Web targets still depend on javascript implementation by default.
Includes some lightweight avro serialization functionality (just enough for the use case), as well as corresponding tests.

Hey @elliotsayes. Thank you for your contribution! 🚀
We will review your code and give some feedback soon.

Explanation of differences in test file:

diff test/data_bundle_test.dart test/data_bundle_native_test.dart

1c1
< @TestOn('browser')
---
> @TestOn('vm')
8,9c8
< import 'package:arweave/src/utils/implementations/bundle_tag_parser_js.dart';
< import 'package:arweave/utils.dart';
---
> import 'package:arweave/src/utils/implementations/bundle_tag_parser_native.dart';
52,68d50
<   test('check if avro fails serialization when wrong data is given', () {
<     final testTags = [
<       Tag(encodeStringToBase64('wrong'), encodeStringToBase64('wrong'))
<     ];
<     final buffer = serializeTags(tags: testTags);
<
<     expect(
<       () => deserializeTags(buffer: [Uint8List.fromList(buffer), 0]),
<       throwsException,
<     );
<   });
<
<   test('check if avro deserializes tags correctly', () {
<     final tags = deserializeTags(buffer: testTagsBufferSnapshot);
<     expect(tags, equals(testTagsSnapshot));
<   });
<
94c76
<   test('create data bundle with large files', () async {
---
>   test('create data bundle with large-ish files', () async {
97c79
<         List.generate(5000 * pow(2, 10) as int, (index) => 'A')
---
>         List.generate(5000 * pow(2, 5) as int, (index) => 'A')
100c82
<     expect(await deepHash([testData]), equals(testFileHash));
---
>     expect(await deepHash([testData]), equals(testFileHashSmaller));

Implementation is only for running natively, so test on VM
deserializeTags() is unimplemented, so related test are removed
Test data generation in create data bundle with large files test takes a very long time on VM compared to web, so I worked around by reducing the size. If anyone has a more efficient implementation then feel free to substitute it in.


Resolve out-of-memory issue in CI

CircleCI seems to be having trouble running the crystal build step to build the Mare compiler, seemingly running out of memory. Here's a snippet of what the output looks like:
make compiler-spec.all
make[1]: Entering directory `/home/circleci/project'
find "spec/compiler" -name '*.mare.spec.md' | xargs -I '{}' sh -c 'make compiler-spec target="{}" extra_args="''" || exit 255'
make[2]: Entering directory `/home/circleci/project'
docker exec -i mare-dev make target="spec/compiler/privacy.mare.spec.md" extra_args="" compiler-spec.inner
mkdir -p /tmp/bin
crystal build --debug main.cr --error-trace -o /tmp/bin/mare
LLVM ERROR: IO failure on output stream: Out of memory
clang-10: error: no such file or directory: '_main.o'
clang-10: error: no such file or directory: 'S-lice40U-I-nt841.o'
clang-10: error: no such file or directory: 'P-ointer40U-I-nt841.o'
clang-10: error: no such file or directory: 'A-rgumentE-rror.o'
[...]

Honestly I'm not sure how to resolve this apart from switching to a different CI provider, but maybe there is some setting we can tweak or workaround we can use to make CircleCI keep working for us.
If we have to use a different CI provider, we could explore using GitHub Actions

Okay, attempting to set up GitHub Actions in draft PR #116

Well that was easier than expected.
GitHub Actions seems suitable for the main CI job, so I am going to wrap up that PR and I have opened a separate ticket to move our remaining VSCode publish CI job to GitHub Actions as well: #117


[Feature Request]: StorageAccounts Module - Support for Sas Policy

Description
The Storage Account Module does not support SAS Policies. Submitting PR.

See PR #3028


[REQUEST] Add a Linux version

Would it be hard to make a version that's capable of running on Linux? I have a ton of games that I want to decrypt but I'm not capable of installing Windows on any machine I own, and it feels like a waste to install Windows JUST to decrypt the game ISOs. Thanks!

Certainly!
i will build it and run some tests and let you know !

linux_test.zip
decryption worked but i did not test boot yet, please let please try this build and let me know

Will test asap, thanks for the quick response, will update with results.

I just tried with Far Cry 3, works perfectly, thanks for the build!

Thanks for the linux build! I can confirm it worked great for me in Windows 11 WSL and produced an identical file to original ps3dec. Great work on the app. I love the auto function and the progress bar! Original ps3dec actually completed two seconds faster in this test but I'm using a slow laptop and it's within margin of error so that's probably meaningless. Will test on faster hardware soon.
Would love to see a linux build added to releases or, alternatively, instructions for compiling on linux and a list of build dependencies added to the main page. :)


updated search-mailbox as per work item 118875008

removed references to data loss related to auto-expanding archiving in EXO

Docs Build status updates of commit cc2cdf4:
:clock10: Full build: the average full build time is 13 min(s) 55 sec(s), this is based on the last 435 build(s) for this repository.

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

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Search-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@chrisda can you please merge this PR to live?


Adapt to new spatstat.random package.

Also weeded out hard dependencies on spatstat (which was never used) and spatstat.core which is only used in tests, vignettes and README, so it can be optional (in Suggests). As far as I can see all functions from envi work without spatstat.core installed.
When spatstat (or spatstat.core) was in Depends it implied that whenever you loaded envi then spatstat (and hence spatstat.core, spatstat.geom, ...). This means that it was obsolete to write first library(envi) and then library(spatstat.core) afterwards. In case envi would never be used without also loading spatstat (or spatstat.core) you may of course reinstate this feature.
Feel free to ask if any of this is unclear.

Thanks, @rubak! I appreciate your (and the spatstat team) time and energy to help a new(er) developer.
I also manage the sparrpowR package so I suspect some similar issues.

Hi @rubak, I see you made a similar merge request for the sparrpowR package (https://github.com/machiela-lab/sparrpowR/commit/6bbdea5cf24642769b9c5e573de0d362903fdfec) and noticed you listed spatstat.core in Suggets here for 'envi' but listed spatstat (>= 2.0-0) in Suggest for 'sparrpowR'
Any particular reason for the discrepancy? Thanks for all the assistance.

Here in envi you always seem to load spatstat.core explicitly rather than the umbrella spatstat package (which would also load spatstat.linnet). Then it seems logical that you suggest the package that you actually use. In sparrpowR you call library(spatstat), so it is natural to have that in Suggests. However, I now see that the library(spatstat) call in sparrpowR is in a file called dev/hexSticker_sparrpowR.R, so it is probably not really a part of the package and you don't need to suggest spatstat (I don't even think you need to suggest spatstat.core).
Typically Suggests is used for a package that is only needed for a single function in your package which is not so important, but more of an extra feature. So it is feasible to install and use your package without the suggested package, and there is only a single function that wouldn't work. This function would test for the presence of the suggested package and exit with an informative message if it is not installed.
You use spatstat/spatstat.core a bit differently since it is mostly used in tests of your package (and possibly as examples in README, but that is not really part of the official package either). So installing them really doesn't add any functionality to your package, and you could say that they are not needed at all. Also the usual practice of checking whether the suggested package is installed before using it (which you don't do) is maybe not necessary here. The only unfortunate thing with your packages is that if you install them and only the required dependencies you will get a failure when trying to run R CMD check since they try to load spatstat/spatstat.core during tests. The way around this would be to wrap the relevant tests in
if(requireNamespace(spatstat.core){
# Run tests as usual
} else{
mesasge("Test skipped since spatstat.core is not installed")
}

but I think this might be overkill since it is only tests that fail and not actual user examples/functions.

Thanks @rubak! This rundown is helpful. I ran through each package and listed the appropriate Suggests. The dev directories and README are ignored by CRAN so it makes sense to remove the packages used therein from the CRAN submission. Thank you for thoroughly reviewing my code. Fingers crossed for CRAN checks. If not, I will try your 'overkill' suggestion.

Hi @rubak. I recently pushed an updated version of this package to CRAN and three environments have ERROR in the CRAN Package Check Results.
r-devel-linux-x86_64-debian-gcc
r-devel-windows-x86_64-new-UL
r-release-linux-x86_64
The error appears to be same in these environments relating to:
Error: object ‘is.poisson’ not found whilst loading namespace ‘spatstat.linnet’
Execution halted

I no longer have the spatstat.linnet package as a dependency, based on your recommendation in this pull request. Can you advise on a solution? Are you seeing this in other reverse dependencies?
Thanks!


message view: Mobile web is very slow, especially on Chrome.

See https://chat.zulip.org/#narrow/stream/general/topic/mobile.20web and https://chat.zulip.org/#narrow/stream/feedback/topic/chrome.20on.20mobile.
Seems to be worse on chrome than firefox or safari.

(From investigations here: https://chat.zulip.org/#narrow/stream/6-frontend/topic/mobile.20scrolling)
Scrolling through messages on mobile Chrome is slow, with frames dropped all over the place. The timeline shows that the "Update Layer Tree" (ULT) operation is taking forever. (This is particular to Chrome: Firefox is fine.)
Although initially spotted on CZO, it can be reproduced clearly with a dev server by adding ~10000 messages (./manage.py populate_db -n10000). Fewer may work.
Deleting, from within Chrome DevTools, all of webpack/app~archive.css (with some manual intervention to clear away #app-loading) makes it scroll significantly faster (ULT ~8ms, occasionally also "Hit Test" ~20ms). Deleting all of webpack/app~support.css as well gets the scroll speed up to a reasonably-consistent 60Hz.
All tests were run on a physical Moto G7 Power.

@zulipbot claim

Closing, as the hardware and UI have changed significantly since this issue was originally opened.


Improve intent classification

Currently for Chinese we have two pipelines:
Use MITIE+Jieba:
["nlp_mitie", "tokenizer_jieba", "ner_jieba_mitie", "ner_synonyms", "intent_classifier_jieba_mitie"]
Use MITIE+Jieba+sklearn:
["nlp_mitie", "tokenizer_jieba", "ner_jieba_mitie", "ner_synonyms", "intent_featurizer_jieba_mitie", "intent_classifier_sklearn"]
Both of them give good entity recognition results, but intent classification results are very bad.
For example:
$ curl -XPOST localhost:5000/parse -d '{"q":"我想吃顿面条"}' | python -mjson.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   325  100   299  100    26  19776   1719 --:--:-- --:--:-- --:--:-- 21357
{
    "entities": [
        {
            "end": 6,
            "entity": "food",
            "extractor": "ner_jieba_mitie",
            "start": 4,
            "value": "\u9762\u6761"
        }
    ],
    "intent": {
        "confidence": 0.027987433652389405,
        "name": "affirm"
    },
    "text": "\u6211\u60f3\u5403\u987f\u9762\u6761"

“面条” can be succesfuly extracted, but intent is WRONGLY assigned to "affirm" instead of "restaurant search".
Problem is probably that Chinese sentences should give special features for intent classification task. Will look into it.

Possible problem is the tokenize result encoding generated by Jieba and MITIE.
In [14]: type(jieba.lcut('我爱吃火锅')[2])
Out[14]: unicode

In [15]: type(mitie.tokenize('我爱吃火锅')[0])
Out[15]: str

In [16]: type(mitie.tokenize('我爱吃火锅')[0].decode('utf-8'))
Out[16]: unicode

In [17]: type(jieba.lcut('我爱吃火锅')[2].encode('utf-8'))
Out[17]: str

Fix encoding problem, and add more training data seem to solve the problem :)


Python 3 compatibility

What exactly is not working right now with python 3?

Working on this on python3 branch.

Should be fixed in #14, though I think the issue should only closed once we get python 3 testing working on travis-ci.

Working now and travis-ci tests python 3.4. Good job @mpeterv!


Unable to debug and select interpreter

Environment data

VS Code version: < 1.21.0 >
Extension version (available under the Extensions sidebar): < Python Microsoft 2018.2.1 (9th March 2018)>
OS and version: < Windows 10 1709 Home>
Python version: < 3.6.4 >
Type of virtual environment used (if applicable): <N/A  >
Relevant/affected Python packages and their versions: <Python Microsoft 2018.2.1 (9th March 2018) >

Actual behavior
< After Feb 2018 V-1.21 update, debugger option is not working (I've created folder) and it's showing error 'Debug adapter process has terminated unexpectedly'.
Also I cannot select the interpreter from the command palette, and it shows error message:
"command 'python.setInterpreter' not found". I've tried uninstalling and reinstalling vs code and also disabled the extensions and then checked for running the code either in debugger mode and integrated terminal but nothing works. >
Expected  behavior
< Debugger should work perfectly fine and show the tray consisting of start stop and pull over buttons to carry out the debugging session, also by using the combination ctrl + shift + p and choosing the interpreter it should have shown me the current python interpreter installed in my system which it showed earlier perfectly before the latest update >
Steps to reproduce:

< I've just enabled the Python extension from Microsoft and disabled other extensions, to re-create the whole scenario, a zip file is attached. >

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
< Nothing >

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
< nothing >

VScode1.zip

Looks like the installation of your Python extension is corrupted.
Please could you uninstall the Python extension, re-install it.
If it still doesn't work, then go into the Extensions directory, delete the Python extension folder and reinstall. (use the command Extensions: Open Extensions Folder to go into the extensions folder)
To keep things simple, please do not debug (lets focus our testing to one area):

Open a python file
Go into the command Select Python Interpreter
Ensure this works before proceeding

Thank you very much Sir, your second method i.e. deleting the python extension from python extension folder worked and the code is working normally from the context menu option "Run file in terminal", and select interpreter is also working fine and it showed me to choose the python interpreter installed into my system, Loads of thanks. :)
But now coming to Debugger section, it is showing the error "Time out for debugger session."
I've attached a .zip file to explain my case.
VS Code_debug.zip

Please could you try debugging a simple python file as follows:
print("Hello World")

Sir, it is showing the same error as above, "Time out waiting for debugger connection."
And I'm using Python Experimental: Current file (Integrated Terminal)
But then I deleted the .vscode file in my folder and re-run the debugger and it worked fine and showing the debugger tray on the top of my workspace and printed Hello World.
When I used the integrated debugger for my turtle code the debugger worked fine and accepted the inputs perfectly, But when I try to run my turtle code again (via debugger and choosing Python current file as debugger option), it gets stuck after my first input (I know this is irrelevant to the question but if you could help, it would be a great deal), I've attached a .zip file for the same.
P.S. My doubt is cleared regarding aforementioned case, but just wanted to ask the same for the debugging option via Python current file and why my code (which consists of input in turtle code) gets stuck using debugger option as  Python current file.
VSCode_debug2.zip

And I'm using Python Experimental: Current file (Integrated Terminal)

When using the Experimental Debugger, you need to have PTVSD 4 installed in your python environment:
Install PTVSD 4: pip install ptvsd --pre

it gets stuck after my first input (I know this is irrelevant to the question but if you could help, it would be a great deal),

You need to use the Python: Integrated Terminal to capture input (i.e. use the terminal when debugging)

As stated by you, I installed PTVSD 4 using terminal in vs code and then again when I re-run the file using Experimental debugger (current file), it again gets stuck when arrived at first input.
But I think most of my task can be achieved using integrated terminal, so no worries regarding whether current file debugger works or not.


encoding/json: document Valid allows invalid utf8

What version of Go are you using (go version)?

$ go version
go version go1.20 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/lukeshu/.cache/go-build"
GOENV="/home/lukeshu/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/lukeshu/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/lukeshu/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/run/user/1000/tmpdir/go-build2160073961=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I passed a binary garbage wrapped in " quotes to json.Valid.
package main

import (
	"encoding/json"
	"fmt"
)

func main() {
	jsonStr := "\"0\x85\xcd\xc0\xf3\xcb\xc1\xb3\xf2\xf5\xa4\xc1\xd40\xba\xe9\""
	fmt.Println(json.Valid([]byte(jsonStr)))
}

https://go.dev/play/p/rrtmrEL3Ipd
What did you expect to see?
As JSON is specified to be "a sequence of Unicode code points" (ECMA-404) or "encoded in UTF-8, UTF-16, or UTF-32" (RFC 7159) I would expect that a JSON document containing bytes that cannot be interpreted as Unicode codepoints to not be considered valid.
What did you see instead?
It considered the document to be valid, even though it contains bytes that cannot be interpreted as Unicode codepoints.

I understand that Unmarshal and Valid share underlying code, but Unmarshal being permissive of invalid input doesn't mean that Valid should declare it as valid (at least without its own note in the documentation).
And I discovered this because of inconsistency between the various functions, when I expected that even if they have quirks they'd at least be consistent because of sharing the underlying implementation. I'd discovered that json.Unmarshal(any)→json.MarshalIndent() would convert the binary garbage to U+FFFD, while json.Indent() and json.Compact() would pass it through unchanged. I figured that differing behavior for invalid JSON was reasonable, but then was surprised to find that json.Valid() identified it as valid.

CC @dsnet @mvdan

It's unfortunate that the json package allows invalid UTF-8 since RFC 8259, section 8.1 clearly states that JSON must be UTF-8.
Given that we already verbally promise handling of invalid UTF-8 in Unmarshal, we should also document how it operates in Valid.


Support for generic implementation of MsgExecuteContract for any kind of terra smart contract calls

Description
Added WasmMessageExecuteContractGeneric for to execute any kind of smart contract calls in terra chain.
Testing instructions
./build/tests/tests tests
tools/android-test
tools/ios-test
Types of changes

Fixed Issues:
#2182
New Feature
Added Introduced WasmMessageExecuteContractGeneric proto model
Checklist

✅  Prefix PR title with [WIP] if necessary.
✅ Add tests to cover changes as needed.
✅ Update documentation as needed.
🙅  I have read the guidelines for adding a new blockchain (not a new blockchain integration)
✅ If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

Thanks for reviewing @catenocrypt. The serialization change is needed as tx submission fails otherwise. The other comment is fixed.
Requested re-review.

Thanks for reviewing @catenocrypt. The serialization change is needed as tx submission fails otherwise. The other comment is fixed.
Requested re-review.

5


Issue #352 - Replacing mock datetime by fake_datetime fixture

Description

Fixes #352
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)

Additional requirements

[x] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct.

[x] I agree to follow this project's Code of Conduct

I was and I am still puzzled do we want to do that? Before in discussions @kairoaraujo said that it's better to remove them from a commit, but why? Maybe it's because plantuml (used to generate those pictures) version is not controlled by us and can generate different binary files depending on the version used. What would you say @kairoaraujo?

Yes, IMO It is nit remove it from the commit as the reviewers are aware about this issue of rebuilding the plantuml images. We should create a issue to solve it.

Nice work! @kairoaraujo I am approving, do you want to remove the changed binary png files or we are good to go?

It is ok replace it.


Custom row height

Is it possible to set a custom row height?

Since AloeStackView relies on Auto Layout to stacks it children, why not setting the Auto Layout height constant to the views like so:
class ViewController: AloeStackViewController {

    override func viewDidLoad() {
        super.viewDidLoad()
        view.backgroundColor = UIColor.white
        setupViews()
    }

    private func setupViews() {
        let view100 = CustomView()
        view100.label.text = "100"
        view100.backgroundColor = UIColor.red
        view100.heightAnchor.constraint(equalToConstant: 100).isActive = true
        stackView.addRow(view100)

        let view200 = CustomView()
        view200.backgroundColor = UIColor.green
        view200.heightAnchor.constraint(equalToConstant: 200).isActive = true
        view200.label.text = "200"
        stackView.addRow(view200)

        stackView.setInset(forRows: [view100, view200], inset: .zero)
    }
}

You can also do it directly on your CustomView if your view has a constant height.

Aah I didn't even think about it being auto layout, thanks @FlorianLdt !

not sure why this is still open, closing now


Workaround for the issue #257

This is workaround for the issue #257 using clipper-java removed lambda.
Recalculate interior polygons smaller than the original holes.

https://github.com/googlemaps/android-maps-utils/issues/257#issuecomment-230195788


Instruct to add HTML5 shiv in installation step 1

In step 1 ("Add Scripts and Stylesheets"), it should instruct the user to also include an HTML5 shim, as otherwise IE will fail to correctly parse the audio and source elements, and users will be racking their brains (like me) until they remember this notorious IE problem.

Good point. I've added a note about putting the code in the <head> or using html5shim


Remove opencensus dependency

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
This dependency is not necessary until SDK logging is re-introduced.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

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


feat(fabric-socketio-connector): sending transactions signed on the client-side

Add functions to support entire process of sending transaction to the ledger without sharing
any private key with the connector.
Add test cases to check the new functionalities.
Adjust asset-trade sample app to use new logic that doesn't send the private key to the connector.
Move fabric signing utils to a separate file.
Add fabric protobuf serializers and deserializers, so they can be send back and forth
between connector and BLP without loosing type information.
Add an option to FabricTestLedgerV1 to allow attaching to already running ledger container.
This can speed up test development/troubleshoot process.
Improve fabric-all-in-one ledger healthcheck, so that it waits for basic chaincode intialization.
This is not strictly needed by current tests, but may be expected by future tests.
Refactor duplicated logic in fabric-connector.
Fix fabric-socketio module entry points (minor fix).

Closes: #2070
Depends on #2047
Signed-off-by: Michal Bajer<EMAIL_ADDRESS>
As always, please review only the last commit. Remaining ones are just dependencies, that will be squashed before an actual merge.

@petermetz Rebased and tested, ready for merge.


Feat: Typewriter Animation

What feature?
Current
On landing page only images have animation the left side text is looking so simple
Add screenshots

Changes
I want to apply the Typewriter effect on left side text for better UI
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

duplicate of https://github.com/priyankarpal/ProjectsHut/issues/790


Sale icon is not showing even if catalog rule is applied for grouped and bundle type products

Bug report
Title
Sale icon is not showing even if catalog rule is applied for grouped and bundle type products
Preconditions
1. framework Version. Master

Steps to reproduce
1. step1  - create a grouped and bundle type product
2. step2 - create a catalog rule which should get applied on those products, get check at front end rule is getting applied but sale icon is not displaying

Expected result
if catalog rule has been applied then there should be sale icon
Actual result-
https://prnt.sc/ti07gd

Fixed in master


update exist function

Rule (8).zip
this is from before this code was implemented but it contains the define/dataset/rule for this branch.  I do want to make sure this preserves others rules that use exist/not_exist so it would be worth checking another rule or two from this list and ensuring exists functionality is preserved with the changes: rules_20240806_135751.xlsx

@RamilCDISC I updated the test suite.  In doing so, I noticed the nested logic was behaving differently than the original function which would return all False or True depending on presence of the target.  I changed the nesting logic to reflect this so we were not getting mixed returns of True/False bools (I believe the presence of True would override the other Falses though in processing which is why I believe this still behaves the same as before.  I tested on positive and negative data for CG0320.)  Would love for you to give it a second glance though but I believe the one line did not change anything except for giving a cleaner result consistent with the way the function worked previously.


Typo in console formatter option name

The console_formater_options has a typo. This PR deprecates the option and replaces it with console_formatter_options while maintaining backwards compatibility.

Thank you @HypeMC.


HSEARCH-2170 Convert the GsonHolder to a Service to ensure cleanup

Mainly because Gson holds references to ThreadLocals, so having it stored in a static variable is not desirable.
JsonParser has been moved to private static variables, though, since it does not contain any data.
https://hibernate.atlassian.net/browse/HSEARCH-2170

nice! Merging


Setting OAuth token to None causes TypeError in oauthlib 2.1.0

Reproduction
Lib versions
pokitdok==2.7.2
oauthlib==2.1.0

Code
Use example code as shown in readme on a fresh install.
Issue
Description
When the pokitdok client attempts to set the token of the oauth client to None, it triggers a property setter on the oauth client which treats the None as some sort of HTTP response.
Traceback (snipped for relevance)
File "/Users/laurence/src/patient-price/env/lib/python3.6/site-packages/pokitdok/api/client.py", line 143, in fetch_access_token
    self.api_client.token = None
  File "/Users/laurence/src/patient-price/env/lib/python3.6/site-packages/requests_oauthlib/oauth2_session.py", line 114, in token
    self._client._populate_attributes(value)
  File "/Users/laurence/src/patient-price/env/lib/python3.6/site-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 468, in _populate_attri
butes
    return self.populate_token_attributes(response)
  File "/Users/laurence/src/patient-price/env/lib/python3.6/site-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 479, in populate_token$
attributes
    if 'access_token' in response:
TypeError: argument of type 'NoneType' is not iterable

Location of issue
https://github.com/pokitdok/pokitdok-python/blob/master/pokitdok/api/client.py#L142
Mitigation
I had success in circumventing the issue by removing the offending line; however I have not submitted this as a PR because I haven't yet had the time to understand why the line was there in the first place and whether by removing it, errors would be caused further down the line.
Here is a commit on a forked repo that makes this change: https://github.com/PatientPrice/pokitdok-python/commit/7685b4adc8462a482a6317d1b5d301d49acec0aa

Hi @Sourceless - thanks for the report!
I believe https://github.com/pokitdok/pokitdok-python/blob/master/pokitdok/api/client.py#L142 was originally introduced a while back (like 2 years ago) to address a problem with automatic token refreshing.   It could be that this is no longer an issue with recent oauthlib versions.
If you'd like to open up that MR, we can help review and test it to ensure everything still works as expected using the latest oauthlib

Thanks for your quick response :) PR is here: https://github.com/pokitdok/pokitdok-python/pull/33


How to connect K8S to Triton Datacenter Elastic Docker?

Hello,
Please let me know, what is the best method to connect remote Docker Engine to a K8S cluster?
For example, there is Triton Compose having Docker API to connect to it even from a general docker CLI.
Can K8S create, run and manage it containers in Triton private cloud?
May be via something like K8S -> CRI -> CRI-xxx like cri-dockerd -> Triton Docker API?
May be like described in another issue:
https://github.com/Mirantis/cri-dockerd/issues/106
I am using cri-dockerd as CRI for kubernetes. I have set --container-runtime=remote --container-runtime-endpoint=unix:///var/run/cri-dockerd.sock as flags for kubelet

But using IP network to the Triton cloud with a TCP port of its Docker API? Is it possible? Or may be there is a better method to connect them?
Thanks,
Alex

Probably have a look at https://github.com/TritonDataCenter/triton-kubernetes, seems that they already have a product ?

Probably have a look at https://github.com/TritonDataCenter/triton-kubernetes, seems that they already have a product ?

Hello again,
It seems triton-kubernetes is not alive and most likely is not exactly what I wanted to use.
My idea was just to connect to Triton Elastic Docker as a K8S runtime by using cri-dockerd if specifying a host:port for remote docker is supported by this K8S CRI plugin.
Benefits:
cri-dockerd is an alive and supported project
Triton Elastic Docker officially invites to manage it via general remote docker compatible socket/connection.
I think it would be very convenient.
Is it possible to specify remote docker host in cri-dockerd so that kubelet can be hosted on a different node than where actual docker runtime is running?
In such case:

K8S node kubelet could run inside a very light VM or even LXD container
Actual docker runtime could run on another SmartOS host (in Triton Elastic Docker private cloud) which is Illumos fork (even not a Linux OS)

Please read more details about docker API support in Triton:
https://apidocs.tritondatacenter.com/docker
https://docs.tritondatacenter.com/public-cloud/api/docker
and about Triton Elastic Docker:
https://docs.tritondatacenter.com/public-cloud/instances/docker/how
https://docs.tritondatacenter.com/public-cloud/instances/docker/how/start-multiple-containers

This is not something that is supported, but maybe https://virtual-kubelet.io/ could be something for you?


post token to auth

@h1alexbel thank you for reporting this. I'll assign someone to take care of it soon.

@erstediy this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-18T19:39:10.668641.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@erstediy Don't forget to close this ticket before the deadline (2023-09-18T19:39:11). You are past the first half of the allowed period.

@erstediy Looks like you've missed the task deadline (2023-09-18T19:39:11). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@lisitsaaa this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-28T20:00:01.410239.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@lisitsaaa Don't forget to close this ticket before the deadline (2023-09-28T20:00:01). You are past the first half of the allowed period.

@lisitsaaa Looks like you've missed the task deadline (2023-09-28T20:00:01). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@NikiTuz18 this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-19T14:31:36.402977.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@NikiTuz18 Don't forget to close this ticket before the deadline (2023-11-19T14:31:36). You are past the first half of the allowed period.

@NikiTuz18 Looks like you've missed the task deadline (2023-11-19T14:31:36). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@PavelRyauzov this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-29T15:00:34.825037.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@PavelRyauzov Don't forget to close this ticket before the deadline (2023-11-29T15:00:35). You are past the first half of the allowed period.

@PavelRyauzov Looks like you've missed the task deadline (2023-11-29T15:00:35). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@LeonovAlexProg this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-09T15:30:51.612314.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@LeonovAlexProg Don't forget to close this ticket before the deadline (2023-12-09T15:30:52). You are past the first half of the allowed period.

@LeonovAlexProg Looks like you've missed the task deadline (2023-12-09T15:30:52). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@iColdLight this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-19T16:00:42.272627.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@iColdLight Don't forget to close this ticket before the deadline (2023-12-19T16:00:42). You are past the first half of the allowed period.

@iColdLight Looks like you've missed the task deadline (2023-12-19T16:00:42). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-29T16:30:07.180139.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-12-29T16:30:07). You are past the first half of the allowed period.

@l3r8yJ Looks like you've missed the task deadline (2023-12-29T16:30:07). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2024-01-08T16:59:38.078795.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@h1alexbel Don't forget to close this ticket before the deadline (2024-01-08T16:59:38). You are past the first half of the allowed period.

@h1alexbel Looks like you've missed the task deadline (2024-01-08T16:59:38). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role DEV available or because the project does not have enough funds.
Please, make sure there is at least one available contributor with the required role and the project can afford to pay them.


CMP graphical problems

Hello there, I couldn't find any similar problem but
when lsp shows an error in code, text in cmp dropbox doesn't render properly

 Screenshot:

I'm guessing that it is a problem with cmp/lsp virtual text conflicting but I don't know how to approach it

Seems to be fixed in update


Remove non-Python dependencies

The current version uses fslmaths for a number of steps that could very easily be done with nilearn or nibabel + numpy.
The only difficult part that I can think of is handling MELODIC's mixture modeling. We can either (1) assume the MELODIC data are in BIDS format already and work from there or (2) try to "implement" the mixture modeling method with a Python-based ICA algorithm.

Is it really necessary to implement the mixture modelling step? AFAIK, the spatial criteria only require to compute the percentage of the spatial variance in the ventricles or the edges of the brain.

I think that mixture modeling is necessary based on the blockers I came up against the last time I tried this conversion, but (1) I can't be sure I did the conversion correctly and (2) the official version of the code is, unfortunately, nearly unreadable. It should be easier for us to see if mixture modeling is necessary once we have thoroughly refactored the code.

Definitely. Once the code is refactored, it will be much easier to see what's missing and what our next steps should be.

I think the most important remaining FSL code is:

MELODIC for ICA and mixture modeling.
FLIRT for applying linear transforms from native-space data to standard space.
apply_warp for applying warps from native space to standard space.
fsl_regfilt for denoising (see #37).

I guess we could use nitransforms to replace FLIRT.

I guess we could use nitransforms to replace FLIRT.

I'm trying to see how we can do this.

I believe we have to do something like this for the affine:
xfm = nt.linear.Affine(afnixfm.to_ras(reference=new, moving=new), reference=new)
nt_with_afni = xfm.apply(new, order=0)

and I guess we can create the iso one ourselves and give it as input:
xfm = nt.linear.Affine(T)
moved = xfm.apply(new, order=0)

Do you know if nitransforms can handle nonlinear transforms?

I think it can but I would have to look into that.

Now that we're planning to drop transforms (see #45) for the immediate future, I think all we need to do now is figure out how to replace MELODIC's mixture modeling.

Is anyone familiar with nipy's Gaussian Gamma mixture model? See here and here. I think that a Gaussian Gamma mixture model is the one used by MELODIC:

I think we can also leverage tedana in replacing MELODIC. Something like the following:

tedana's MAPCA function in tedana to get number of components and dimensionally-reduced data.
tedana's TEDICA function to get component time series and maps.
Corrected version of tedana's computefeats2() to get component z-statistic maps. (We need the fixed version for this.)
nipy's GMM to threshold component maps.
FFT using tedana's plotting code to get the component power spectra.
Code proposed in #49 to get the masks used for spatial features.


[Nox.Docs] Generate Documentation for EndPoints MP-9202

Prepare templates and markdown files

the current readme file can me moved/generated in    .nox\docs (example https://github.com/NoxOrg/Nox.Generator/blob/main/samples/README.md)

in .nox\docs generate a <EntityName>EndPoints.md file for each entity (except owned entities) , that will be used to document all End Points (Use scriban)

Update the current generated readme, add a link to each entity, for example:

Generate the content for the End Points

Create a Section for Entity, a section for Owned Relations,section for Relations a section for Custom Commands a section for Custom Queries
All with subsection for each verb Get/Post/..
Generate a summary a a relative path for each end point

https://regusit.atlassian.net/browse/MP-9202

Hi @Mornevanzyl, can you please help out defining the Markdown for the Readme.md documentation for the Endpoints?
This is my suggestion, but let me knwo if you see it differently.
`# API Endpoints
This document provides information about the various endpoints available in our API.
Entity Endpoints
Get Entity

GET /api/entities/{id}

Description: Retrieve information about a specific entity by ID.

Create Entity

POST /api/entities

Description: Create a new entity with the provided data.

Update Entity

PUT /api/entities/{id}

Description: Update an existing entity by ID with the provided data.

Delete Entity

DELETE /api/entities/{id}

Description: Delete an entity by its ID.

Owned Relations Endpoints
Get Owned Relations

GET /api/owned-relations/{entity_id}

Description: Retrieve all owned relations for a specific entity.

Create Owned Relation

POST /api/owned-relations/{entity_id}

Description: Create a new owned relation for a specific entity.

Update Owned Relation

PUT /api/owned-relations/{entity_id}/{relation_id}

Description: Update an existing owned relation for a specific entity.

Delete Owned Relation

DELETE /api/owned-relations/{entity_id}/{relation_id}

Description: Delete an owned relation by its ID.

Relations Endpoints
Get Relations

GET /api/relations/{entity_id}

Description: Retrieve all relations for a specific entity.

Create Relation

POST /api/relations/{entity_id}

Description: Create a new relation for a specific entity.

Update Relation

PUT /api/relations/{entity_id}/{relation_id}

Description: Update an existing relation for a specific entity.

Delete Relation

DELETE /api/relations/{entity_id}/{relation_id}

Description: Delete a relation by its ID.

Custom Commands Endpoints
Execute Custom Command

POST /api/custom-commands

Description: Execute a custom command with the provided parameters.

Custom Queries Endpoints
Execute Custom Query

POST /api/custom-queries

Description: Execute a custom query with the provided parameters.

`


Updates backport workflow

Description
Updates backport workflow to allow adding backport failure labels to failed auto-backports.
Category
Maintenance
Why these changes are required?
To allow easier tracking of failed backport PRs.
What is the old behavior before changes and new behavior after changes?
No tracking before this change.
Issues Resolved

Resolves #2073

Check List
~- [ ] New functionality includes testing~
~- [ ] New functionality has been documented~

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks like it worked. @DarshitChanpura thank you