Duplicated modules in psci

Hi,
Do you know why is not possible to work with psci in this project due to:
"Error found:
Module Control.Alt has been defined multiple times."
It seems there is a lot of modules loaded twice¿?
Find this reference
https://github.com/purescript/purescript/issues/818
but I don't see the solution in this case.
Thanks in advance for your help,
Dani

That's odd -- I just did psci in the directory and it is working without any issues. Try using the newest version of PureScript and potentially deleting the local bower_components to clear the dependencies.

Totally agree.
I'm using the last version of psc in an OSX environment. And works fine with other projects.
I tried 'pulp psci' and 'psci' with the same result, the repl works, but when I try to import a module, the explained error appears.
Have you tried to import Prelude, for example? Or any other module?

Well, I tried on my laptop, and had the same problem you're mentioning. I deleted the .psci file and tried pulp psci and now it is working to import modules. ¯_(ツ)_/¯

Yes!
Sorry for the delay and thanks for the help

Cool! Is it working for you now then?

Yep, the project was working all the time, the only 'problem' was the repl.
Thanks again

Awesome :)


Safari not working due to unsupported RegEx

Completely changing this Issue to better reflect the problem as a reddit user posted:   Safari is no longer working as it has before.  Still an unsupported browser, but issue stems from regex "look behind" indicator that is unsupported in Safari, implemented in v3 tables.
Reddit post:  https://old.reddit.com/r/homebrewery/comments/p1rel1/issue_homebrewery_not_working_on_apple_safari/

Fixed with https://github.com/naturalcrit/homebrewery/commit/a48c74b2e714e769c0fe714c189ea785990458f8


Fix sudo needing sensu checks

A sudo key isn't being read by the ansible module or by sensu itself,
the sudo action needs to go on the command itself.
Also, given that some commands are now done without paths, we need to
define the secure path for sensu user for sudo.
Change-Id: I0942b7e44898cff7f1fc575f5bd0f73f9d712ba5

LGTM 👍 Lots of digging for this one, but a small solid commit.

yar 👍


Not compatible with version 1.2.10 in Docker

I'm running Kanboard 1.2.10 in docker.
I've installed Spectre in plugins/Spectre by git clone from github.
Kanboard finds the plugin bu declares it incompatible despite the fact ispactre says >= 1.2.10
Not clear whether this is a bug in Kanboard or Spectre...

Here's the error log
2019/08/27 16:28:22 [error] 14#14: *4 FastCGI sent in stderr: "PHP message: PHP Warning:  filemtime(): stat failed for plugins/Spectre/skin.min.css in /var/www/app/app/Helper/AssetHelper.php on line 37" while reading response header from upstream, client: <IP_ADDRESS>, server: localhost, request: "GET /extensions HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "kanboard.hps.perlucida.uk"

So the missing minified css file is the problem?

Just change plugin.php from$this->hook->on('template:layout:css', ['template' => 'plugins/Spectre/skin.min.css']); to $this->hook->on('template:layout:css', ['template' => 'plugins/Spectre/skin.scss']);


Appstudio update test-component-ic-zorl

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-ic-zorl-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
38 seconds
build-container

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
19 seconds
clair-scan

✅ Succeeded
18 seconds
inspect-image

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
13 seconds
label-check

✅ Succeeded
8 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom

Pipelines as Code CI/test-component-ic-zorl-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
38 seconds
build-container

✅ Succeeded
19 seconds
clair-scan

✅ Succeeded
18 seconds
inspect-image

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
13 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


SAK-31716 SAML filter to do logout

For those that may not read the JIRA be sure to use one of the following properties:
login.container.logout.url=/sakai-login-tool/container/saml/logout?local=true
login.container.logout.url=/sakai-login-tool/container/saml/logout

Okay makes sense. Thanks.


Fix nested query in Solr 7.7

refs #593
Local params are not allowed anymore with an edismax query type as of solr 7.2 https://lucene.apache.org/solr/guide/7_2/solr-upgrade-notes.html#solr-7-2
This updates the query to be lucene for the join, while setting the user portion of the query back to dismax.

Coverage remained the same at 100.0% when pulling 1d8691228c852a339eb1649042a2ba21c3a578a3 on update_solr_7_7 into fdd5f95e09dc5ceee2f40512ac5ce8fbf9a87ac9 on master.


[BUG] HDF5 error in ariaTSsetup processing

Describe the bug
I am getting some diagnostic error messages from the HDF5 (1.12.2) library when running ariaTSsetup.
To Reproduce
Steps to reproduce the behavior:

Download (ariaDownload.py -b '37.0 38.3 -122.6 -121.75' --track 42 --num_threads 8)
Command used (ariaTSsetup.py -f 'products/*.nc' -b '37.25 38.1 -122.6 -121.75' --mask Download --num_threads 8 --verbose)
Error Output:

Generating: coherence -
HDF5-DIAG: Error detected in HDF5 (1.12.2) thread 1:
  #000: H5A.c line 528 in H5Aopen_by_name(): can't open attribute
    major: Attribute
    minor: Can't open object
  #001: H5VLcallback.c line 1091 in H5VL_attr_open(): attribute open failed
    major: Virtual Object Layer
    minor: Can't open object
  #002: H5VLcallback.c line 1058 in H5VL__attr_open(): attribute open failed
    major: Virtual Object Layer
    minor: Can't open object
  #003: H5VLnative_attr.c line 130 in H5VL__native_attr_open(): can't open attribute
    major: Attribute
    minor: Can't open object
  #004: H5Aint.c line 545 in H5A__open_by_name(): unable to load attribute info from object header
    major: Attribute
    minor: Unable to initialize object
  #005: H5Oattribute.c line 494 in H5O__attr_open_by_name(): can't locate attribute: '_QuantizeBitGroomNumberOfSignificantDigits'
    major: Attribute
    minor: Object not found

Expected behavior
There are hundreds of these errors for the hundreds of interferograms I have. The processing continues despite the errors or warnings.
Desktop (please complete the following information):

ARIA-tools git tag: [e.g. git show --summary]

- commit 32018d59312f0267e077aba1e16de4f1c70a98d9 (HEAD -> dev, origin/dev, origin/HEAD)
Merge: 35c01cd 60ea380
Author: BB<EMAIL_ADDRESS>Date:   Wed Sep 6 13:48:34 2023 -0700

   Merge pull request #381 from aria-tools/sss_latsortbug

   Sort pairs by latitude

OS Linux
python --version
Python 3.11.3

Additional context
Add any other context about the problem here.

These errors looks like an HDF / filesystem issue


Problems with API level 30

(Thank you very much for your work on this plugin, it has been very useful for me)
I'm having trouble starting apps on the Android emulator running API level 30 and above.
These were my test so far (all of them work fine on API level 29 except for the last one):
let sApp = startApp.set({"package": packageName}).check();
//Doesn't work - NameNotFoundException
let sApp = startApp.set({"application": packageName}).start();
//Doesn't work - Application not found
let sApp = startApp.set({"action":"ACTION_MAIN", "package": packageName}).start();
//Works for chrome ("com.android.chrome")
//Doesn't work for other random apps - No activity found to handle intent (but also doesn't work on API 29)
Any idea how to solve this?

Hi @UnitedBiscuits, since Level 30, app cannot discuss with other app without explicit declaration in the AndroidManifest.
See https://developer.android.com/guide/topics/manifest/queries-element
Kr.

Hey guys,
does this mean there are apps that we cannot start with this plugin directly (because they did not add exported="true" to their AndroidManifest)? Or is something missing on our side?
I have also an app that I want to start. I am 100% sure that the package-name is correct, but I was not able to start it (tried it via application, component, package)... No luck so far. Ideas?


custom dataset preparation

The existing NeRF papers illustrated that we can use COLMAP to generate transform.json file. However, it comes with a condition that there should be 70% overlap with each images.
In Block-NeRF, they mentioned that image data captured from 12 cameras that collectively provide a 360° view. 8 of the cameras provide a complete surround view from the roof of the car, with 4 additional cameras located at the vehicle front pointing forward and sideways.
Would it be possible to share the piece of code that used those 12 camera images as input to generate a transform.json ?
Many thanks.

This part is very tricky. I don't think the Google teams use the same type of COLMAP because I often find that our COLMAP produces very weak poses while they still get strong poses. Probably they have an internal version of COLMAP, or they use an additional refinement procedure.
So the short answer is, I don't know this.

Understand. Do you happen to know any repo which shares details on how to generate a transform.json without using COLMAP or any third party tools?

Thanks for the info. Hope you are referring to this repo

Yep.


starchat-alpha change (cache=True on model) causes guidance to crash at end of completion

The bug
After an update to the Starchat-alpha model (https://huggingface.co/HuggingFaceH4/starchat-alpha/commit/2f20a76066a3fd9d7b0c28d5f11999042aebb2f4)
It seems like something about the model's _past_key_values is in an unexpected format for what the llm and transformer class expect.
To Reproduce
A simple Transformer model based on it
import torch
from transformers import AutoTokenizer,AutoModelForCausalLM
import guidance

class StarcoderChat(guidance.llms.Transformers):
    def __init__(self, model_path, **kwargs):
        tokenizer = AutoTokenizer.from_pretrained(model_path, device_map='auto')  # revision='5058bd8557100137ade3c459bfc8100e90f71ec7'
        model = AutoModelForCausalLM.from_pretrained(model_path, device_map='auto', torch_dtype=torch.bfloat16) # revision='5058bd8557100137ade3c459bfc8100e90f71ec7'
        super().__init__(model, tokenizer=tokenizer, device_map='auto', **kwargs)

    @staticmethod
    def role_start(role):
        return "<|"+role+"|>"

    @staticmethod
    def role_end(role):
        return '<|end|>'
model_path = "HuggingFaceH4/starchat-alpha"
guidance.llm = StarcoderChat(model_path)

prompt = guidance('''
{{#system~}}
You are a helpful and terse assistant.
{{~/system}}
{{#user~}}
How do you print something cool in python
{{~/user}}
{{#assistant~}}
{{gen 'answer' stop='<|end|>'}}
{{~/assistant}}''')
prompt()

gets an error:
File "/home/vscode/.local/lib/python3.10/site-packages/guidance/library/_gen.py", line 151, in gen
    for resp in gen_obj:
  File "/home/vscode/.local/lib/python3.10/site-packages/guidance/llms/_transformers.py", line 361, in _stream_then_save
    self._update_prefix_cache(streamer)
  File "[/home/vscode/.local/lib/python3.10/site-packages/guidance/llms/_transformers.py](https://vscode-remote+ssh-002dremote-002bazure-002da100.vscode-resource.vscode-cdn.net/home/vscode/.local/lib/python3.10/site-packages/guidance/llms/_transformers.py)", line 352, in _update_prefix_cache
    self._prefix_cache = streamer.generated_sequence[0][:self._past_key_values[0][0].shape[2]] # self._past_key_values is already saved, this just aligns with it
IndexError: tuple index out of range

Error in program:  tuple index out of range

System info (please complete the following information):

OS: Ubuntu
Guidance Version (guidance.__version__):guidance==0.0.54 and guidance==0.0.47 (I checked 2 versions, both showed the same error)

Thanks! I had not seen that format for last_key_values before...and I can't say I fully understand it since StarCoder only has 256 floats per key/value pair. How you cache 48 heads worth of KVs in 256 floats is something I would need to dig into to understand. But regardless, in the HF implementation for that model they reference -2 from the end of the array instead of +2 from the start to get the sequence length, so now we do the same and everything runs.

How was this error of _past_key_values solved for the starcoder model? Its tensor format is different from GPT-2 hence giving an error in line no. 281 of _transformer.py file
self._past_key_values = tuple((key[:,:,:prefix_match_len,:],value[:,:,:prefix_match_len,:]) for key,value in self._past_key_values)


Dirt Slabs don't work particularily well with texture and light mods

Using Dirt Slabs with Optifine and Shaders makes the side of the full grass block completely dark

same here... pls fix
thx


Feature Support fast schema evolution in shared data mode

This PR aims to support global column unique id in shared data mode
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@Mergifyio rebase

@wyb @sevev @kevincai PTAL

@Mergifyio rebase


Modified rand_cpu_x86.c to support builtin hardware randomizer on HPE…

Modified rand_cpu_x86.c to support builtin hardware randomizer on HPE NonStop.
CLA: Permission is granted by the author to the OpenSSL team to use these modifications.
Fixes #12903
Signed-off-by: Randall S. Becker<EMAIL_ADDRESS>

I pushed an amended commit with the correct sign-off for<EMAIL_ADDRESS>that has a valid CLA on file. Sorry about the slip-up. The default signature on our x86 system was from a different domain.

I pushed an amended commit with the correct sign-off for<EMAIL_ADDRESS>that has a valid CLA on file. Sorry about the slip-up. The default signature on our x86 system was from a different domain.

Our CLA checker bot looks at the commit author for that sort of thing, not appended commit message headers, so we do have to ask you to amend the commit with<EMAIL_ADDRESS> The only appended header the bot looks at is CLA:

@mattcaswell @levitte I think we're having that Travis issue again. Or did I do something bad?

@mattcaswell @levitte I think we're having that Travis issue again. Or did I do something bad?

It does not look like anything I did, from the Travis CI gcc output.

It was a merge error - see latest PR.

It was a merge error - see latest PR.

Thanks.

Why would an x86 processor support RDRAND but not support the CPU flags indicating it's usability? This seems pretty odd to me.

I think I have an (speculative) answer on this. Looking purely at the timing of events, the c99 compiler was developed by one group many years ago. The externalization of the RDRAND ops were added by request to a different group much more recently and likely did not include requested changes to the compiler(s), or approval was not given for that. This may be resolved when we get a more recent compiler made available but I have no timeframe on when that will be - very much outside my control.

@paulidale Is this ready to go? Anything else I need to do?

@paulidale Once PR #12933 is merged, I'll have a fixup for this PR to update the define used for selecting TANDEM. I think that's the last change needed.

@paulidale I have another change ready, but it's perplexing where to go. The NonStop Itanium platform has a similar randomize approach to rand_unix.c, although that method has everything folded together and it's suitable. The approach is a real time clock in nanoseconds and a system clock in microseconds. There is a suitable method to combine those without sleeping. I don't really think putting the code into rand_unix.c makes a lot of sense without a complete rewrite. And putting it in rand_cpu_x86.c, which easy, is somewhat misleading. Do you have a suggestion on this? Essentially, the code is:
unsigned long get_sys_random(void) {
        unsigned long long nanos = TS_NANOSECS_() % UINT_MAX ;
        unsigned long long micros = JULIANTIMESTAMP() % UINT_MAX;
        unsigned long long swapped_micros = (micros % 65536LL << 16LL)
                + (micros / 65536LL);
        unsigned long long random = (nanos * swapped_micros) % UINT_MAX;
        return (unsigned long) random;
}

There are two places for the timer to go: rand_tsc.c is the randomness source based on timers.  We currently do not allow this to be used because we can't quantify the amount of randomness produced.
It can also go in get_timer_bits() in rand_unix.c -- there is already special case code for Sun and HP/UX where a high resolution timer call is available.  This is called by rand_pool_add_additional_data() which mixes things up but doesn't count towards the randomness available.
If the timer is all you've got, you're out of luck for a seed source.  Better make sure that kernel random number generator is working.
As for the function that collects values:
unsigned long get_sys_random(void) {
        unsigned long long nanos = TS_NANOSECS_() % UINT_MAX ;
        unsigned long long micros = JULIANTIMESTAMP() % UINT_MAX;
        unsigned long long swapped_micros = (micros % 65536LL << 16LL)
                + (micros / 65536LL);
        unsigned long long random = (nanos * swapped_micros) % UINT_MAX;
        return (unsigned long) random;
}

My opinion is that this is attempting to obfuscate things and that it isn't producing anything even remotely close to cryptographic level randomness.  The variables nanos and micros will be highly correlated (since they are measuring the same thing).  The word swapping does nothing for the randomness.  Likewise the multiplication.  I'd just use TS_NANOSECS_():
uint64_t get_timer_bits(void) {
    return TS_NANOSECS_();
}

Any entropy that is present will be in the low order bits of the TS_NANOSECS_().  So maybe TS_NANOSECS_() & 15.  The exact number of bits is difficult to estimate: it requires data collection and a lengthy statistical analysis and even then it could be wrong.

Any entropy that is present will be in the low order bits of the TS_NANOSECS_(). So maybe TS_NANOSECS_() & 15. The exact number of bits is difficult to estimate: it requires data collection and a lengthy statistical analysis and even then it could be wrong.

Previous experience with this has shown that even some of the lower bits need to get masked out because of repeated patterns in the bits.. As Pauli says - Validating and justifying an entropy source can be very time consuming.

Why would an x86 processor support RDRAND but not support the CPU flags indicating it's usability? This seems pretty odd to me.

I think I have an (speculative) answer on this. Looking purely at the timing of events, the c99 compiler was developed by one group many years ago. The externalization of the RDRAND ops were added by request to a different group much more recently and likely did not include requested changes to the compiler(s), or approval was not given for that. This may be resolved when we get a more recent compiler made available but I have no timeframe on when that will be - very much outside my control.

I think you're at least misunderstanding the question. All x86
since the pentium in 1993, and all x86_64 CPUs support the CPUID
instruction. That instruction allows us to find out that RDRAND is
available or not. We have assembler support in
crypto/x86_64cpuid.pl that should allow is to detect if RDRAND is
available or not. The compiler is not involved.
It can be that the OS is masking certain CPU features, and that
even when the CPU supports it, we can't see it.

Why would an x86 processor support RDRAND but not support the CPU flags indicating it's usability? This seems pretty odd to me. I think I have an (speculative) answer on this. Looking purely at the timing of events, the c99 compiler was developed by one group many years ago. The externalization of the RDRAND ops were added by request to a different group much more recently and likely did not include requested changes to the compiler(s), or approval was not given for that. This may be resolved when we get a more recent compiler made available but I have no timeframe on when that will be - very much outside my control.
I think you're at least misunderstanding the question. All x86 since the pentium in 1993, and all x86_64 CPUs support the CPUID instruction. That instruction allows us to find out that RDRAND is available or not. We have assembler support in crypto/x86_64cpuid.pl that should allow is to detect if RDRAND is available or not. The compiler is not involved. It can be that the OS is masking certain CPU features, and that even when the CPU supports it, we can't see it.

I understand, but the instructions are not being detected. Perhaps it is because there is no assembler on this platform and the ELF formats are slightly different. There are also two variants, one is x86 (big endian), the other is ia64 (big endian). I've been through the lack of detection of features in many products, and may be the OS, so this is not a surprise. I can't control that part of things.

Is there a reason you don't use the assembler? Is it using a
different ABI? Not using the assembler will mean that you don't
use various CPU support like AESNI which will make it slower.
I'm pretty sure x86 only supports little endian, while ia64 can
switch between big and little endian. Maybe what you mean is that
like VOS, all data is stored in big endian, and you have the
compiler convert it on load and store?

Is there a reason you don't use the assembler? Is it using a different ABI? Not using the assembler will mean that you don't use various CPU support like AESNI which will make it slower. I'm pretty sure x86 only supports little endian, while ia64 can switch between big and little endian. Maybe what you mean is that like VOS, all data is stored in big endian, and you have the compiler convert it on load and store?

There is no available assembler on the platforms (TNS/E-itanium, or TNS/X-x86), not for a lack of trying to get one for years. gcc is also not available either or we would be using it. While objects are ELF format, they are not standard.
The x86 big-endian is implemented in custom millicode on the TNS/X platform.

There are two places for the timer to go: rand_tsc.c is the randomness source based on timers. We currently do not allow this to be used because we can't quantify the amount of randomness produced.
It can also go in get_timer_bits() in rand_unix.c -- there is already special case code for Sun and HP/UX where a high resolution timer call is available. This is called by rand_pool_add_additional_data() which mixes things up but doesn't count towards the randomness available.
If the timer is all you've got, you're out of luck for a seed source. Better make sure that kernel random number generator is working.
As for the function that collects values:
unsigned long get_sys_random(void) {
        unsigned long long nanos = TS_NANOSECS_() % UINT_MAX ;
        unsigned long long micros = JULIANTIMESTAMP() % UINT_MAX;
        unsigned long long swapped_micros = (micros % 65536LL << 16LL)
                + (micros / 65536LL);
        unsigned long long random = (nanos * swapped_micros) % UINT_MAX;
        return (unsigned long) random;
}

My opinion is that this is attempting to obfuscate things and that it isn't producing anything even remotely close to cryptographic level randomness. The variables nanos and micros will be highly correlated (since they are measuring the same thing). The word swapping does nothing for the randomness. Likewise the multiplication. I'd just use TS_NANOSECS_():
uint64_t get_timer_bits(void) {
    return TS_NANOSECS_();
}

Any entropy that is present will be in the low order bits of the TS_NANOSECS_(). So maybe TS_NANOSECS_() & 15. The exact number of bits is difficult to estimate: it requires data collection and a lengthy statistical analysis and even then it could be wrong.

The TS_NANOSECS_() method returns nanoseconds since the last system cold-load while JULIANTIMESTAMP() returns microseconds since about the creation of the world in biblical tradition. The two are independent. I get that this is hard to certify. There is no explicit hardware randomizer, so doing this based on what is in rand_unix.c seems closer to that.
In any event, the current pull request only applies to the x86 platform, and I'll keep it that way.

From what I read online, it's the compiler (and OS) that converts it to big endian.
The 2 timestamps might have a different starting point and resolutions, but they are most likely generated from the same hardware clock.

From what I read online, it's the compiler (and OS) that converts it to big endian.
The 2 timestamps might have a different starting point and resolutions, but they are most likely generated from the same hardware clock.

They are not generated by the same hardware clock. CPU coldload times are real-time clocks in each CPU and are independent. The System clock is an aggregate of the DateTime Clock from all CPUs and synchronises/self-corrects/publishes via the message system. They two are actually very unrelated. The DateTime clock is subject to a large amount of actual drift and it takes regular updates from NIST to keep it sane.

Rechecking uint64_t. Not posting anything relating to Itanium in this pull request. That will be a separate one if we go there.

I'm not sure I understand why this PR has issues.  Sure, @openssl/committers are often used to Linux or similar and the offer of a multitude of free compilers / assemblers, and here comes code for a platform very few of us have a good idea of, apart from manuals we can find on the net.  For this section of code, I don't think we have any other option than to trust @rsbecker's knowledge...  and it shouldn't matter for the rest of us, as it's guarded well enough.
And sure, some future fixes may do a better job of checking CPUID and find out all sorts of stuff, and starting to use the assembler code we have.  It doesn't have to happen now.  If this code is the difference between "working" and "not working" for NonStop machinery, that should be good enough for now.

(it took a looooong time before VMS builds started using the assembler code, at all, FYI...)

The TS_NANOSECS_() method returns nanoseconds since the last system cold-load while JULIANTIMESTAMP() returns microseconds since about the creation of the world in biblical tradition. The two are independent.

No they are not independent.  The two are extremely correlated: each advances one second per second.  In terms of randomness obtainable, a second timer adds effectively nothing.
I don't believe that Julian Day Numbers are biblical in origin...

The TS_NANOSECS_() method returns nanoseconds since the last system cold-load while JULIANTIMESTAMP() returns microseconds since about the creation of the world in biblical tradition. The two are independent.

No they are not independent. The two are extremely correlated: each advances one second per second. In terms of randomness obtainable, a second timer adds effectively nothing.
I don't believe that Julian Day Numbers are biblical in origin...

Just for info: on this platform, JULIANTIMESTAMP() == 0 corresponds to 12:00 UTC on January 1, 4713 B.C. The number is computed software clock aggregated across processors. Each of the 16 logical CPUs has their own real time clock that the 6 IPUs use for the TS_NANOSECS().
Before anything is done for the Itanium box, in a separate PR/Issue, I will be subjecting any random generator that uses these to a heavy weight battery test to assess randomness. This is not happening here. I will communicate the results of the tests. If I cannot get even the NIST tests to pass (a subset of what I am testing), that PR won't see the light of day. Ever. Aside from that, the box (TNS/E) goes off support in 2.5 years, so this may be a moot point if I can't get this to work by then. ;)

Use Test01, it's the most comprehensive in my experience.

Use Test01, it's the most comprehensive in my experience.

👍 Already downloaded and installed. That was the plan - using the full battery of tests.

👍 Already downloaded and installed. That was the plan - using the full battery of tests.

Make sure you do the tests on the raw entropy, not on the cooked version after your function whitens it.  Test01 I likely to detect the whitening but it isn't certain.

I find the NIST tool very useful: https://github.com/usnistgov/SP800-90B_EntropyAssessment

I find the NIST tool very useful: https://github.com/usnistgov/SP800-90B_EntropyAssessment

There are some serious problems with the NIST tooling.  The restart tests e.g. fail a significant percentage of the time even with truly random data.  I can't find the reference to the rebuttal of the tests -- it was presented at ICMC two years back.

There is rarely any correlation even at 10 parts per 10000 between the two clocks with the former being in software and the latter being in hardware.

Without disputing how the two clocks actually work, I would still assume that they both (mostly) increment...  I don't have the deep knowledge of randomness that others have, and still, just that assumption makes red flags go wild in my head.
Generally speaking, using clocks as a source of entropy is considered a bad choice.  I suspect people would otherwise abuse NTP for that sort of thing.

It's the only tool I know that's designed to test the raw input. All others I know look at the output of the RNG.

You probably mean: https://www.untruth.org/~josh/sp80090b/Care and Feeding of SP800-90B D12.pdf

Yes, it was Josh Jill who discovered the worst of it.  I submitted a few comments which were mostly addressed in the final revision.  The committee has been refining things since then.

There is also this very recent presentation: https://www.untruth.org/~josh/sp80090b/90B Extravaganza 20200921.pdf, and  new repository: https://github.com/KeyPair-Consulting/Theseus

For the Itanium generator, not included in this PR, we got the following results from the small battery on TestU01:
       Test                          p-value
 ----------------------------------------------
  4  SimpPoker                        eps
  5  CouponCollector                  eps
  6  MaxOft AD                      1 -  4.3e-5
  7  WeightDistrib                    eps
  9  HammingIndep                     eps
 ----------------------------------------------
 All other tests were passed

I'd say "not bad" but "not good enough". So we're in the won't happen soon category for the Itanium RNG at this stage. It should not impact this PR which is x86 only with that hardware RNG that does work.

Although, when running the FIPS-140-2 test:
============== Summary results of FIPS-140-2 ==============

 Generator:        nse_gsr
 Number of bits:   20000

       Test          s-value        p-value    FIPS Decision
 --------------------------------------------------------
 Monobit               9854           0.98       Pass
 Poker                14.00           0.53       Pass

 0 Runs, length 1:     2519                      Pass
 0 Runs, length 2:     1242                      Pass
 0 Runs, length 3:      648                      Pass
 0 Runs, length 4:      336                      Pass
 0 Runs, length 5:      165                      Pass
 0 Runs, length 6+:     150                      Pass

 1 Runs, length 1:     2609                      Pass
 1 Runs, length 2:     1248                      Pass
 1 Runs, length 3:      614                      Pass
 1 Runs, length 4:      313                      Pass
 1 Runs, length 5:      137                      Pass
 1 Runs, length 6+:     140                      Pass

 Longest run of 0:       14           0.46       Pass
 Longest run of 1:       13           0.50       Pass
 ----------------------------------------------------------
 All values are within the required intervals of FIPS-140-2

It should not impact this PR which is x86 only with that hardware RNG that does work.

This PR is approved as is, so that's not even a discussion at this point.

It would probably be fruitful to have the Itanium discussion elsewhere, for separation.

It would probably be fruitful to have the Itanium discussion elsewhere, for separation.

Thanks. You are quite correct. I have included my analysis in #12988.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged
d3edef83f5fa378237fcece038f9aff9f89f34cd Modified rand_cpu_x86.c to support builtin hardware randomizer on HPE NonStop.


refactor: introduce possibility to observe host for named slot changes

We have various use cases where we want to remove or render an entire section of elements, depending on whether a specific element is slotted into a named slot.
This PR introduces functionality to define a named slot state and a way to observe the light DOM of the host for changes.

It looks great. 🚀 Question: we can't test it until the Stencil slotchange bug is fixed, right?

Maybe with an e2e test?

Reminder: Please use logic in sbb-link-list

Codecov Report

Merging #1375 (d4b5c4f) into master (ab917b0) will increase coverage by 4.77%.
The diff coverage is 76.91%.

@@            Coverage Diff             @@
##           master    #1375      +/-   ##
==========================================
+ Coverage   54.85%   59.62%   +4.77%
==========================================
  Files          49       58       +9
  Lines        1659     2031     +372
  Branches      406      510     +104
==========================================
+ Hits          910     1211     +301
- Misses        671      735      +64
- Partials       78       85       +7

Impacted Files
Coverage Δ

src/components/sbb-clock/sbb-clock.tsx
0.00% <0.00%> (ø)

src/components/sbb-logo/sbb-logo.tsx
0.00% <0.00%> (ø)

src/components/sbb-signet/sbb-signet.tsx
0.00% <0.00%> (ø)

...obal/core/components/overlay/overlay-component.tsx
0.00% <ø> (ø)

src/components/sbb-alert-group/sbb-alert-group.tsx
33.33% <33.33%> (ø)

src/components/sbb-form-field/sbb-form-field.tsx
40.32% <40.32%> (ø)

...c/components/sbb-autocomplete/sbb-autocomplete.tsx
40.87% <44.44%> (+0.87%)
:arrow_up:

...c/components/sbb-toggle-check/sbb-toggle-check.tsx
66.66% <66.66%> (ø)

src/components/sbb-image/sbb-image.tsx
69.09% <73.77%> (+6.12%)
:arrow_up:

src/components/sbb-tab-group/sbb-tab-group.tsx
76.19% <76.19%> (ø)

... and 45 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: remove unused check for changed which always evaluates to false

This PR removes an unused check for changed beause this is always false as it seems and never executed.

What kind of change does this PR introduce?
Bugfix

Did you add tests for your changes?
No

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?

Thanks


Store check constraint annotations on entity type instead of model

Summary of the changes

Added check constraint generation to CSharpSnapshotGenerator.cs

Fixes #15676

@AndriySvyryd Can you take another look at this now the annotations are stored on entity types?

Also please rebase and squash commits

@Muppets Seems that some tests need to be updated.

@AndriySvyryd Good to go!

@Muppets Thanks for your contribution!


Speed of application

If you install the react plugin in google chrome you have the option to 'Highlight Updates' that allows to check which part of the dom is updated on each action.

I have the impression a lot of optimisation can be done at that level. For example if you touch the accordeon menu the SVG seems to be redrawed.
Also if you add
console.log('makePath', id);

in
https://github.com/cheminfo/nmr-displayer/blob/35a5849f1ba1789c52a7612bf4efb9acf9bf18d8/src/component/LinesSeries.jsx#L30
You see that even just selecting a serie will redraw many times all the spectra
Moving the cursor (zoom tool) also call many time the makePath method. The SVG of the serie is not expected to change when you move the cursor.

Concerning moving the cursor that force the redraw here is the related code:
https://github.com/cheminfo/nmr-displayer/blob/cef41d09a6a928c4a5022699ede3a22691a177f9/src/component/SpectrumChart.jsx#L69
@targos Please could you give some advice for this ?


add: trainer notebook

This PR adds a trainer notebook for the standard segmentation model. After the PR is merged, I will train it full-blown. From my initial analysis, we might need to use distributed training with mixed precision to complete model training within a reasonable amount of time.

@soumik12345 thanks!
I will then wait for your PR for the trainer CLI so that I could reformat my training notebook and incorporate distributed training with mixed precision.


Version question concerning docker swarm and vxlan plugin

We have been attempting to implement the docker-vxlan-plugin in docker 1.12 and have been running into some problems I'm hoping you can help clear up.
The tutorial for your plug-in uses pre-1.12 style swarms so I  followed those instructions in our first attempt to implement the plug-in.  It seemed to go okay until I hit the instruction in the tutorial "docker run -d --name=swarm-master-nginx --net=vxlan42 -e constraint:node==swarm-master nginx" and no matter what we tried, we kept getting "endpoint not found errors".
We decided that it could possibly be a problem trying to use the pre-1.12 style swarms in 1.12.  I recreated everything and verified the swarm was working as expected.  We started hitting a problem on the previous tutorial instruction to create the xvlan network.  The exact instruction we used for our environment was from the tutorial "docker network create -d vxlan -o Group=<IP_ADDRESS> -o VxlanId=42 -o VtepDev=eno1 --subnet=<IP_ADDRESS>/24 --gateway=<IP_ADDRESS> vxnet." which gave us 'rpc error: code = 3 desc = invalid driver specified".  Again I tried to use a few work-arounds, but keep hitting a wall/
Has the docker-vxlan-plugin been tested on 1.12?  Is there any reason it should not work as described?  Do you have any new instructions for the tutorial based on docker 1.12?  Do you see any other potential solutions we can investigate?
Thank you.
Larry Krigbaum

It does not work in swarm mode in 1.12. I've not tested trying to use the old style swarm with Docker 1.12. Since docker dropped support for global network plugins with swarm mode, I've only been running in local mode.
Since the old style swarm clustering is no longer actively developed, I haven't done any testing with it since 1.12 was released, and will probably be removing the global mode support.

I can tell you it works in "old style" swarm with docker 1.12.
Before dropping global mode support, please note that "old style" swarm seems to be still maintained, as 1.2.6 was released on 2017-01-17.
Having said that, it's rather sad it does not work with "new swarm mode".
Do you have an advice for vxlans with new swarm mode ?
Whatever happens to this plugin, thanks for your work on it @clinta . It has been very useful to me.

Good to know that there's still some work being done on the old style swarm. I won't bother removing global mode support as long as that is not officially abandoned.
https://docs.docker.com/engine/extend/plugins_network/#/network-driver-plugins-and-swarm-mode

Docker Engine running in swarm mode currently only supports the built-in overlay driver for networking.

Unless/until that changes, there's not much hope for vxlans with swarm mode.

Thanks @clinta for the explanations.
The current status of swarm mode and network plugins is quite unclear.
I have found this: https://github.com/docker/docker/issues/24569#issuecomment-267044175 saying that "1.13 supports network plugins with swarm-mode"
So I suspect the doc is outdated.


Patch release

TurbulenceConvection.jl's CI is broken because this package is limiting CLIMAParameters, which the latest Microphysics patch release depends on. This patch release should (hopefully) fix TC.jl's CI.

bors r+


cicd: increase memory limits for cicd runner

what: We intend to increase the limits to our cicd containers.Updated values.yaml file. The script "install-runners.sh" has to be manually triggered for changes to take effect.
why: Control Service Integration Tests have been failing with OOM errors. Although this doesn't directly update the values
it servers as a reference point for future changes.
testing: n/a
Signed-off-by: Momchil Zhivkov<EMAIL_ADDRESS>

Increase only the limit.


Is GPT-neo also considered

Will autonlp also train GPT-neo models for tasks like regression and classification?

respectively, which models are considered? All of them and are the newest also included?

GPT-Neo is not in the pipeline at the moment. If you want to train it using AutoNLP, you can use single model training: https://huggingface.co/docs/autonlp/training_hub_model.html

@abhishekkrthakur thanks!


/db_list - round up to at least 1 MB the result of DB size before sending to user

Now db_list shows the size of any DB, rounded up to the nearest integer value.
@lambotik , please write autotest with the scenario checking the size.

create db
create table
insert 100 records
size should be equal to 1 MB.


Allow users to clear the current text selection

Once the user presses ctrl+L, a text selection is created. It should be clearable.

Figured out issue naming convention :)


[Relay][Frontend][Onnx] Enable group_conv1d import through conv2d conversion.

TVM doesn't support group_conv1d currently and adding it formally is a non-trivial amount of work. Meanwhile, we're encountering an increasing number of models that use it. As an interim solution, we can import group_conv1d using group_conv2d by simply adding a new spatial axis with size 1. This PR adds that converter into the onnx frontend along with corresponding tests.

@mbrookhart @masahi can you guys take a look at this PR?


Rename .envtemplate to devcontainer.env

Type of PR

Documentation changes
Code changes
Test changes
CI-CD changes
GitHub Template changes

Purpose

...

Does this introduce a breaking change? If yes, details on what can break
Author pre-publish checklist

[ ] Added test to prove my fix is effective or new feature works
[ ] No PII in logs
[ ] Made corresponding changes to the documentation

Validation steps

...

Issues Closed or Referenced

Closes #issue_number

References #issue_number

.envtemplate is supposed to be just a template.


Deleting existing dataset with outstanding share requests orphans dataset URI

Describe the bug
We tried to delete an existing dataset which had outstanding share requests on it.  The delete was processed, but the dataset was not removed from the Catalog.  It still exists.  When selecting the dataset we get an orphaned URI error.  The dataset is not present in the "dataset" table.  But in the "dataset_table" table, there are still lots of references to this datasetUri.  This dataset was imported and there were a lot of tables pulled in as part of that import; all of them are still present in "dataset_table".
How to Reproduce
Version:   v2.0.0-beta1
Import a dataset with tables.
Submit one or more share request(s) to that dataset with another user.
Try to delete the dataset.
Observe that the dataset delete is processed, but that the dataset is still present in the Catalog.
Select the dataset from the Catalog.
Observe the URI not found error "An error occurred (ResourceNotFound):  Resource Dataset with URI <URI_here> not found", as well as the orphaned URI in records in "dataset_table" table (potentially also other tables).
Expected behavior
Deleting the imported dataset should either remove all references to that dataset URI (along with associated records in the database), or at least warn the user that they can not delete the dataset without first removing all share requests and other items which may prevent proper cleanup of the dataset.  From a usability perspective it would be preferred that the dataset delete handles all cleanup, without further manual intervention on the part of other users--perhaps the user deleting the dataset is shown all the items that would be removed in a confirmation dialog prior to confirming deletion.
Your project
No response
Screenshots

OS
n/a
Python version
n/a
AWS data.all version
v2.0.0-beta1
Additional context
No response

Hi @rbernotas - taking a look at the above issue you have mentioned and trying to reproduce it in an AWS Deployment of data.all working off of main-v2 branch
I was wondering what was the status of the outstanding share in the above scenario? - Currently, if the share is in a Share Succeeded or Revoke state then the dataset should not be able to delete but in a draft or submitted state we still allow dataset deletion
I verified the above in my account but want to confirm the expected behavior with what happened on your end.
In terms of the orphaned catalog items, I will continue looking into this on my end as well. In my attempts to reproduce I have seen some similarly strange behavior leaving behind items in the open search catalog - will let you know what I find

Hi @noah-paige , thanks for your response.  After discussing this some more internally, we think that this happened because we scrubbed some of the dataset tables manually to fix an issue, but we never cleared up the Opensearch index.  Thanks for taking a look at the Opensearch-specific issue!  We will look for this in the upcoming 2.0 release.

Sounds good @rbernotas - I will proceed with closing this issue for now. Thanks again for raising the issue and please reach out if you run into any other


Enh: Add support for Event Emitters

When using pipelines to create agentic tasks, it will be great to update the user UI with "status" messages, like "executing function", "creating images", "buying tickets"...  This can be done in open-webui function calling using "Event Emitters"
Is there any way to support this in pipeline?

Any guidance on how these emitters can be rigged on pipelines to begin with? It would appear we need to acquire an instance of the current event emitter on each invocation of pipe()...
What and where can the metadata be assembled assuming we can get an emitter instance from the backend?

This would be a wonderful feature.  I'd love to see LangGraph agents use event emitters.  I just wonder how the chat history (namely, the "thought process") will be saved.  It would be nice to pull up an old chat and see the thoughts along with the messages.

Threading to #229 , #373, an examples from openweb.
It appears that you could get there via this streaming example with a little bit of work.


[bug] fix shadow error

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: andrey1s sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

what is the point of this change?

Fix Shadow error

you are in an if block that assigns to the variables before returning them on the next line, please elaborate what you think the error actually is:

there is another error returned
please read more about shadow variables before proceeding

I've written Golang for years, I didn't realize it was fixing the err variable that was declared on https://github.com/Azure/go-ntlmssp/pull/22/files#diff-fcdf318479998e107934dce1a4547c9bR87.
It probably would help for you to include that in your commit description rather than a vague description.


build timeout

Details

Project URL: https://github.com/scikit-rf/scikit-rf
Build URL (if applicable):https://readthedocs.org/projects/scikit-rf/builds/4252709/
Read the Docs username (if applicable): arsenovic

Expected Result
the build to work
Actual Result
the build times out
the build doesnt appear to be failing for any reason other than the timeout. is there a way to increase this limit?

should i post this somewhere else?

now the builds just hang, and say building. i have tried to wipe them, but to no avail.
https://github.com/scikit-rf/scikit-rf/issues/81

I believe we solved this yesterday. #2573 also helps this by trying to reduce the number of unreported build exceptions. Closing this here, but feel free to reopen if this is still an issue.


move html part after text part

Mail.app and other clients don't display the html part. According to http://stackoverflow.com/questions/5188605/gmail-displays-plain-text-email-instead-html, parts in a multipart MIME message should be in order of increasing preference. With this change mail.app (and thunderbird) shows the html mail

I am having this very problem? MERGE please ;)

@hamann Thank you so much!
And sorry for being slow with the merge.

It's working beautifully, thanks @kamilc @hamann


DEVOPS-783  :  Removed the dependency of curl command from the pr_build and production_release.yaml file.  Also used the narrative method to improve the workflow

Added files to remove script dependency

Closing, as the pr_build and manual build workflows are live.


Warning: .nii files wrongly named with extension nii.gz

List of files:
XXX
TODO:

go to each folder, change extension .nii.gz -> .nii
compress:

for i in `ls *.nii`; do fslchfiletype NIFTI_GZ $i; done

I identified the following files with the wrong extensions:
/Volumes/sct_testing/large/amu_2017-virginie_BZ/t2/t2.nii
/Volumes/sct_testing/large/sherbrooke_biospective_100-005-s1/t2/labels.nii
/Volumes/sct_testing/large/sherbrooke_biospective_100-006-s1/t2/labels.nii
/Volumes/sct_testing/large/sherbrooke_biospective_100-009-s1/t2/labels.nii
/Volumes/sct_testing/large/sherbrooke_biospective_100-010-s1/t2/labels.nii
/Volumes/sct_testing/large/sherbrooke_biospective_100-012-s1/t2/labels.nii
/Volumes/sct_testing/large/ucsf_2017-talbott_1010/t2_sag/t2_sag.nii
/Volumes/sct_testing/large/unf_biospective_200-004-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-005-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-006-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-009-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-010-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-011-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-012-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-013-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-015-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-016-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-017-s1/t2/labels.nii
/Volumes/sct_testing/large/unf_biospective_200-018-s1/t2/labels.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_01/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_01/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_01/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_01/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_02/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_02/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_02/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_02/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_03/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_03/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_03/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_03/t1/t1_seg_manual.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_03/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_04/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_04/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_04/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_04/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_04/t1/t1_wat_seg.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_05/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_05/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_05/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_05/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_06/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_06/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_06/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_06/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_07/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_07/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_07/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_07/t1/t1_wat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_08/t1/t1_fat.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_08/t1/t1_inn.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_08/t1/t1_opp.nii
/Volumes/sct_testing/large/unknown_ivdm3seg_08/t1/t1_wat.nii

@jcohenadad Just to make sure before changing the files, we want .nii -> .nii.gz or .nii.gz -> .nii (as you mentioned in the initial comment to the issue) ? thanks

@alexfoias, please do not use the list that you made, but rather address the files that @hadihammoud will list as a replacement for my XXX here. What happens is that those files are nii files, but they are wrongly named with extension .nii.gz. So what we want to do with these files is:

rename them with extension .nii
and then compress:

for i in `ls *.nii`; do fslchfiletype NIFTI_GZ $i; done

@jcohenadad I compressed the data using FSL. In addition, I tested the data using FSLeyes, without any erroré


[Feature Request] Ability to specify pattern for backup bulk deletion

Folks,
Would be great if backup delete had a --pattern flag, so that a user could do bulk delete with a PCRE pattern as follows ark backup delete --pattern nginx*

I'd rather support --all and -l, --selector as that would be in line with kubectl

Alignment with kubectl is a good point.
--all should be self explanatory
--selector what would users be selecting backups on? name?

--selector would delete based on matching labels on the backups, just like with kubectl

WIP PR in #336


Try to go get imagebuilder if not installed

This is what was stopping me from make build-images working :-)
Uses optional go get ability of os::util::ensure::gopath_binary_exists.

/test pull-autoheal-check


Base for checking are parquet files, not sqlite [writing sqlite takes much longer than the actual R&C]

Fixed with https://github.com/LEEF-UZH/LEEF.analysis/commit/045892430d7ea6314a324c91ecc9b24b26292c78


Sub MA4: Fixing Issues- Notification of response from status

Pull Req for this issues:

(put your PR here, example #2 )


Increase performance of nested queries

With nested queries the code was switching on the option so that it
could display a custom message. This was causing a massive increase in
compilation time as the queries got deeper and wider. In my project we
were seeing build times of about 6 minutes, after this change the build
went down to about 10-11 seconds.
Instead of displaying a custom message, the PPX will now just call out
to Js.Option.getExn.
This might also fix #61

I think we should first understand the cause of the issue (ie how do the differences in output impact compilation performance). Or maybe it’s not differences in the output but the time it takes to compile the make error function

@wokalski My original idea was that the time it takes the PPX to run was the culprit as well. To test this you can go to this repo here and see that the final generated output of the code is the thing that takes a very long time to build using bsc.
You can see how the above PR changes the final compiled code by comparing the master branch of that graphql-ppx-perf-repo to this

@wokalski @baransu I'm not quite sure what's going on with the CI stuff. It seems like CI is just currently broken.
Outside of that, are there any other questions I can answer?


Nested accordions do not expand properly

When an accordion is nested inside another, the child accordion does not expand the height of its parent.
You can see the issue in this plunkr: http://plnkr.co/edit/Vv0DWehGhyi6eYkQCqvN?p=preview. It works correctly in ui-bootstrap version 0.12.1, but if you change the version to anything higher (including 0.14.0), it breaks.
This is how it looks in version 0.12.1 (correct):

This is how it looks in any version after 0.12.1 (broken):

I'm not convinced this is a bug in UI Bootstrap (but certainly needs more investigation) because if you expand the inner accordion and then collapse and then expand the outer one, it does what you desire.
Also, just a head's up - that plunker is using Angular 1.2.x and as of 0.13.0, Angular UI Bootstrap requires Angular 1.3.x.  That said, I confirmed this is still happening in Angular 1.4.6, Angular UI Bootstrap 0.14.0, and Bootstrap 3.3.5.

Sorry, I'm using Angular 1.4.6 in another project and the accordion still exhibits the same behavior for the same versions.
To me, having to click on the inner one and then again on the outer one only confirms that there is a problem. That's not needed on ui-bootstrap 0.12.1.
Thanks for investigating.

Sorry if I wasn't clear, I did confirm it is still happening with the latest versions of all the libraries/frameworks involved.  I agree that it's a nuisance and a "feature" that was introduced somewhere...

@peterneely
I also have use-case for the nested accordion in our application and faced the same problem , finally ended up writing a new accordion.
may be this http://kuldeepkeshwar.github.io/ui-accordion/ can solve your problem
@icfantv
I want to add callback(async) handlers for before opening or closing accordion panels.

I encountered a similar issue.  After adding angular-animate to the page it started to work.
I think it's related to the collapse directive, not triggering this done call:
https://github.com/angular-ui/bootstrap/blob/master/src/collapse/collapse.js#L18
Which is kind of strange since, $animateCss shouldn't be truthy?

Hmmmm.  That was added as a workaround when Angular 1.4.5 came out and hoarked all the animations.  I still need to investigate this.  We have a release coming up at work and I'm a bit preoccupied with that.  If someone wants to investigate more and potentially submit a PR with tests, that would be awesome.
@kuldeepkeshwar, I could see a use case for a select similar to tabs.  We do need to be very careful on adding too many configuration options as it can become too unwieldy for people to use.


[metric spec review] API SHOULD provide some way to pass state to the callback

    [API spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#synchronous-and-asynchronous-instruments) requires a state object to be passed to the callback, I couldn't find how it is supported in opentelemetry-js, e.g. https://github.com/open-telemetry/opentelemetry-js/blob/d154066354863e8c682b4aa488d79c7e914bf91c/api/src/metrics/Meter.ts#L110.

The API SHOULD provide some way to pass state to the callback.
Originally posted by @reyang in https://github.com/open-telemetry/community/issues/1204#issuecomment-1304288581

API spec requires a state object to be passed to the callback, I couldn't find how it is supported in opentelemetry-js, e.g. https://github.com/open-telemetry/opentelemetry-js/blob/d154066354863e8c682b4aa488d79c7e914bf91c/api/src/metrics/Meter.ts#L110.

The API SHOULD provide some way to pass state to the callback.

It is quite easy for JavaScript to capture variable in lambdas, so by the statement in the spec:

The API SHOULD provide some way to pass state to the callback. OpenTelemetry API authors MAY decide what is the idiomatic approach (e.g. it could be an additional parameter to the callback function, or captured by the lambda closure, or something else).

I believe the JavaScript API is sufficient to cover the requirements.
originally posted by @legendecas

Agreed.


Add support for Staticman commenting system

Just wondering if you would like a PR for the following? To have @eduardoboucas Staticman as a first class commenting system would have saved me a lot of time. I'm hoping by contributing this, it may save many others the effort. Thoughts?
I've got staticman commenting working at binarymist.io/blog
Source: https://github.com/binarymist/BinaryMistBlog
The main files, and related changes required are:

staticman.yml
config.toml
comments.html
article_metadata.html
CSS Would you want this added or something similar?

Shout out if you need clarification around any of this.
Thanks.

I would like to support the integration of Staticman. I have collected some problems with the common alternative Disqus:

Disqus is slow and has a bad (re-)loading behaviour.
Disqus is tracking many different things for different customers; some of them hidden and unknown.
Disqus does not allow Markdown.
Disqus does not allow anonymous content (IP address, email and name is recorded).
Disqus is hosted in the USA which is considered to have less stricter privacy laws than Europe.
Disqus is not open source.
Disqus does not allow that user can use free licenses for their comments. It is not clear who has the ownership about the comments.
Disqus in one central authority collecting all comments of your website visitors and users on their servers.

It may be that all the support required @petzi53 is to plus one the work I've already done which was sitting in PR #438 waiting to be merged. At this stage, @gcushen has stated that "This PR remains low priority".
Until such time that it's accepted, feel free to replicate the work I've done in my repo which I've provided hopefully complete details for in my blog post

@petzi53 I am happy to report that following @binarymist 's PR I was able to get comments to work on my website with a customized version of hugo academic. I just stripped the option to subscribe to comments and the unrelated to staticman changes from the PR. Basically, you just need to copy his comments.html, academic.css, and single.html for any section you'd like to have comments on.

Thank you @vkehayas and @binarymist  for offering help and for your tips how should I proceed. I have to confess that I tried it out over the weekend, but did not succeed.
As soon as I have time to spare I will try it again, but this time with an example/test site and reporting in detail my steps and what kind of error messages my test site has produced.

Closing this for now due to lack of suitable PR and lack of contributors who can develop and maintain it. Binarymist has written a blog post on how to perform the modification for anyone interested (linked in above comments).

"It's a shame it only works with GitHub hosted websites (see eduardoboucas/staticman#22 (comment)). Also, it's dependent on a third party server which all comment data goes through and is perhaps a lot more susceptible to going down than say Disqus."

Now Staticman supports GitLab.  You may see my demo GitLab Pages at https://vincenttam.gitlab.io/bhdemo served by @staticmanlab.


Feature Request: Favorite without Sound

With all the Epic gifts, it would be nice if we could mark the ones we are hunting without a dozen sound notifications on occasion. Separate option for having the star next to them and for getting pinged about it maybe?

Added a setting to enable this


Quarter-to-monthly interpolation: Always get into error when the high-frequency data has one or more than one quarter of data available to interpolate

Due to the issue with the calculation formula in the line 22 of ts_disagg.py,
    excess = n - i_len * nl
the program will always generate an extra period in my test scenario, leading the program to crash
In my test case, low-frequency quarterly data starts on 1995/6/1, and ends on 2001/12/1; high-frequency monthly data starts on 1995/3/1, and ends on 2001/12/1. The program will show up the following error:
IndexError: boolean index did not match indexed array along dimension 0; dimension is 28 but corresponding boolean dimension is 27

Further note: if I bring the data one more quarter earlier, say 1994/12/1, the error becomes this:
IndexError: boolean index did not match indexed array along dimension 0; dimension is 29 but corresponding boolean dimension is 27

Sounds like that logic is broken. If you want to open a PR that just adds your test (that doesn't pass), that'd be a good first step for fixing it. Otherwise I'll try my best to get to it by the end of the week

The data that I used to reproduced the error has uploaded into the latest pull request!

Thanks! I started looking at it over the weekend. I think the problem happens before the C matrix.
In your case, the time series aren't "aligned" -- there are too many high-frequency observations before the first low frequency observation. So we need some logic to work out how to align them. For yearly data I check that the set of years is equal in the high and low frequency data, but that doesn't work quarterly, since there's only 4 quarters. Maybe check the set of year-quarter?
I'm a bit swamped at work this week but I'll do my best to have a look. If you feel inspired, feel free as well. I think the problem function is actually handle_endpoint_differences

For the point that you mentioned regarding some more observations available earlier than the starting date of the low-frequency data, when I did the same task for R, R can do the interpolation properly, and interpolate the low-frequency data back to the starting point of the high-frequency data. The Python package that you wrote actually works for annual-monthly cases with monthly high-freq data starting earlier than the annual one. So I think this problem is more about how to make backcasting of the low-freq data work to the earlier date when high-freq data provides data for the earlier date in the quarter-monthly case.
For annual-quarter cases, I don't think I have encountered issues over that so far but I will have a try. I am working with a huge amount of data that needs to be interpolated with your package this week. I will pay attention to that case as well. If I have time, I will create a separate case to test that and see whether it works!

Tested with annual-to-quarter case today. The backcasting is working for this case.

Nice! I'm glad something is working. Would you be willing to make a PR with the rest you ran so it can be included in the testing suite? It will be useful if we start tinkering with the Q->M case, to make sure we don't break what currently works.

The year-to-quarter result and test cases has added, and it's available in the pull request that I opened a few days ago

I've been sick during the weekend so didn't take a look, but any updates on how to fix this issue?

Hey, thanks for the poke.
I have been overloaded with stuff the last week or so, hoping to get to this soon

We are aiming to make some public release of some economic data next week(hope to share it with you once it got published), and it will be highly appreciated if you can publish the fix to both the issue I raised as early as you can, as your package plays a vital role in interpolating our dataset. I understand that you might have packed schedule so take your time on fixing these bugs. I am currently overwhelmed by the rest of the work on the dataset and hopefully I can wrap them up early and work on the PR for the fix!

I'll put a couple hours into this today, hopefully I can make some headway

I cut a new release that I think fixes this and maybe also #9. Can you do pip install tsdisagg --update and open a new issue if you hit more errors.


Using host's VPN

Hi,
I have an issue accessing the VPN the host is connected to. I have set the network to be "Emulated VLAN" and for the most part it seems to work.
However, if I try and access websites on a non-default port (e.g. 8080), it does not connect even though the host does successfully.
Any tips greatly appreciated.
UTM: 4.1.5
Host: 2020 M1 MacBook, macOS Ventura 13.1
Guest: Windows 11 arm64, build 25276
Thanks,
Steve.

Duplicate of #3634


Further improvements to FLUX image-to-image

Summary
This PR improves the behaviour of FLUX image-to-image. It eliminates/simplifies much of the logic from #6900 while preserving the benefits and extending support to image-to-image in addition to inpainting workflows.
Changes:

Adjusts the denoise_strength scale in the Linear frontend for FLUX to improve usability (the amount of image change now varies more gradually with denoise_strength).
Adds support for fractional denoise_start / denoise_end steps. This results in smoother transitions as denoise_start is varied for a particular image/seed.
Update "Optimized Image-to-Image" toggle to apply to all image-to-image workflows - not just inpainting.
Remove trajectory_guidance_strength from FLUX Denoise node. The benefits of this feature are largely captured by the other (simpler) features in this PR.

Example - Image-to-Image
Image-to-image example with denoise_strength (in the linear UI) varied from 0.0 to 1.0 in increments of 0.1:

Example - Inpainting
Inpainting example with denoise_strength varied from 0.3 to 1.0 in increments of 0.1:

Related Issues / Discussions
Recent related PR that originally added Trajectory Guidance: https://github.com/invoke-ai/InvokeAI/pull/6900
QA Instructions

[x] Image-to-image

[x] optimized=True
[x] optimized=False

[x] Inpainting

[x] optimized=True
[x] optimized=False

[x] Outpainting

[x] optimized=True
[x] optimized=False

[x] Progress images are correct
[x] Default FLUX workflows load without errors

Checklist

[x] The PR has a short but descriptive title, suitable for a changelog
[x] Tests added / updated (if applicable)
[x] Documentation added / updated (if applicable)

I don't pretend to understand the whole flux timestep thing as most of it is way over my head. However, I did cobble together some tests to improve the denoise start and stop accuracy, which were mildly successful.
Do you think, in the clip_timestep_schedule_fractional function, it would be worth scaling all of the timesteps to the new extents rather than replacing only the first and last ones after clipping them?
This should maintain the shape of the timestep curve rather than having a jump at either end.  I know we are probably only talking about small fractions in the changes but I wasn't sure if this would have much of an impact or not.

https://discord.com/channels/1020123559063990373/1083864753543331981/1280944995569897494

I experimented with another version like what you've described. The results were pretty similar. The main advantages I see of the current approach is that you get to save a little time by running fewer steps if the denoise strength is low. I'm definitely open to changing it if you have convincing results to show that another timestep schedule is better though.

I don't pretend to understand the whole flux timestep thing as most of it is way over my head. However, I did cobble together some tests to improve the denoise start and stop accuracy, which were mildly successful.
Do you think, in the clip_timestep_schedule_fractional function, it would be worth scaling all of the timesteps to the new extents rather than replacing only the first and last ones after clipping them?
This should maintain the shape of the timestep curve rather than having a jump at either end. I know we are probably only talking about small fractions in the changes but I wasn't sure if this would have much of an impact or not.

I experimented with another version like what you've described. The results were pretty similar. The main advantages I see of the current approach is that you get to save a little time by running fewer steps if the denoise strength is low. I'm definitely open to changing it if you have convincing results to show that another timestep schedule is better though.

I experimented with another version like what you've described. The results were pretty similar. The main advantages I see of the current approach is that you get to save a little time by running fewer steps if the denoise strength is low. I'm definitely open to changing it if you have convincing results to show that another timestep schedule is better though.

I wasn't suggesting changing the number of timesteps, just the existing clipped timestep range might be better if it was scaled to the new values rather than just replacing the first and last ones. As this might better maintain the shape of the timestep curve.
However, the same as you, I have gathered no empirical evidence at all that it would improve the image.  My previous experiments didn't show any meaningful differences other than being easier to choose that fine line of Denoise start that shifts from doing i2i and not doing it.
I see this has been merged into main now, so I might run some tests to satisfy my own curiosity about it. I am not expecting any big differences with it but I am curious.


[Feature Request] Large world support

Would it be possible to get large world support in the main branch of T3D?
Here is what I mean by that -

Terrain paging via Terrain Master
Some form of large world coordinate system to avoid floating point issues. I know that game programming gems 4 has some form of Large world coordinate system in it. It should be a good starting point.

This is actually something that's come up a good bit, and already had some eyeballing done. It's not a perfect solution, but it'd be a good first step, in that I started looking at a level cell loading system. Think in games like Skyrim or the like, where the world is separated into a grid of level cells. As you move through, it progressively loads and unloads cells in the area around the player.
I already started some early investigative R&D along those lines, and it's looking promising. It wouldn't fix ALL issues, such as really extreme distances like your #2 touches on, but it'd definitely let you support moderately sized open worlds a la the elder scroll games. Correcting #2 is trickier, as it requires client-side tricks, and that touches a lot more systems, but it's certainly not impossible!

Even modern RPG MMO games that come out now often do not have larger worlds than the usual 4x4 km or similar.

@HeadClot is not the same, may this can help? https://github.com/GarageGames/Torque3D/pull/954

@John3 - It looks like it just handles the terrain seams. I could be wrong though.

Yep.. just that.

Hey this is just an update on this issue. I found a cell based level system however it is part of a bigger project called Open Simulator and is written in C#. It is under the BSD license and is fully open source.
That said - It could be a very good reference for large scale multi-region worlds in Torque 3D.

A few presentations on how to enable massive worlds :)
https://cesiumjs.org/massiveworlds/

At the risk of sounding like the master party pooper (all be it one who would like to use such a feature) There was once a discussion about which components  should be part of a game engine vs which should be addons/plugins. I cannot help but feel that this in particular is one of those areas where the discussion should be considered, particularly since the terrain systems is a needy part of the engine (at least imo)

@Bloodknight Ah good point.

Hey I updated the original post for those not aware. Maybe we could expose this as a component? Mainly for modular reuse in the engine :)


Nuxt 3 compatibility

Provide the folowing helpers:
const { renderCustomElements, getMenu, getCurrentPage, fetchPage, lazyFetchPage  } = useDrupalCe()

WIP: feature/LDP-1851

PR: https://github.com/drunomics/nuxtjs-drupal-ce/pull/99

thx. I think this is pretty good already. I see your point with the useDrupalCeFetchMenu syntax and it's better now without imports, but I'm not 100% convinced. Maybe something like useDrupalCe().fetchMenu() would work? but in the end we should stick to general nuxt conventions here. I'd suggest we merge first PR with what we have now and then clarify best syntax in a dedicated issue / PR.
So I think for merging this, we should just make sure we have a complete TODO list of open items, so we do not forgot anything. Maybe add the list of TODOs in the README or have a separate github issue where we keep track of it?

Solved in 2.x


docs: v1 - diataxis framework

close: #1613
New structure for documentation using the diataxis framework. Created landing pages for the major sections and re-organized the existing content into one of the 4 topics of the diataxis framework (tutorials, how-to guides, technical reference and explanation)
PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[X] Updated relevant documentation (docs/ or spec/) and code comments
[ ] Title follows the Conventional Commits spec

Maybe we should also check for 404 errors with a tool like https://github.com/stevenvachon/broken-link-checker

Maybe we should also check for 404 errors with a tool like https://github.com/stevenvachon/broken-link-checker

Hi @melekes, we do have a broken links check in the repo, I'll run that again to ensure we are not missing anything. The tool is not perfect because it gives false positives especially in the # anchor links, but overall it is helpful.

Thanks @adizere and @melekes


[1.11.3] build tree creation failure on P9

Loading channels: ...working... done
No match found for: importlib-metadata[version='>=7.0.0,<<IP_ADDRESS>a0']. Search: importlib-metadata[version='>=7.0.0,<<IP_ADDRESS>a0']

Fixed by pinning importlib-metadata https://github.com/cdeepali/open-ce/commit/749693fb571297f30ab28d407c87a9476862cc2a

This issue is seen currently only when pytorch-extras-env.yaml is used for the build and is not seen with opence-env.yaml.


Firebase timestamp in Unity

I want to get the timestamp of realtime database of Firebase in Unity, is this possible?
And to create a child with a timestamp in realtime database? how do I do?
Thankz

You can use Firebase.Database.ServerValue.TimeStamp when writing to the Database
https://firebase.google.com/docs/reference/unity/class/firebase/database/server-value#timestamp
This stackoverflow post describes the general flow although with the Android API
http://stackoverflow.com/questions/37864974/how-to-use-the-firebase-server-timestamp-to-generate-date-created


WIP: Decrypt after merging

This is a rebase of #215.

This merges the hash before trying to decrypt any values. This allows us
to have values in different yaml hierarchy encrypted with different
keys.

Hopefully the tests now pass and I've been testing it in my environment.
Fixes #214

I'm not convinced this code is used in Puppet 5/6.
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/functions/eyaml_lookup_key.rb replaces at least part of this gem???

Since hiera 5 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/functions/eyaml_lookup_key.rb is used as the entry point to the lookups.


Update index.js

Refactored code

Thanks, but we prefer the current code style. It's less prone to errors

Yeah but I adjusted it according to ES6, which makes your website even
faster.
But anyways thanks for reviewing it.
On Mon, Mar 23, 2020, 11:44 PM Gregor Martynus<EMAIL_ADDRESS>wrote:

Thanks, but we prefer the current code style. It's less prone to errors
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hoodiehq/hoodie/pull/898#issuecomment-602770722, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN6XDCWC4U7MEL7PFMUYYOLRI6RKHANCNFSM4LSA5M2Q
.


geographic attributes- name?

How should we refer to geographic attributes? Currently we are using LOCATION_ATTRIBUTE and AREA_ATTRIBUTE, but would another term be more appropriate? AREA_MEASUREMENT? AREA_OBSERVATION?

WG: Attribute is fine for 1.0


Bug: The External LB is getting stuck into "pending" state on AWS & few other clouds when protocol is TCP

📜 Description
while testing the SGE on private clusters, we found some issues with AWS specific annotations that worker-operator is adding.
// Note: Special treatment for AWS EKS clusters. The LB is not provisioned unless we add AWS specific annotations
    // to the service. This is needed only for EKS.
    if clusterProvider, _ := getClusterProviderID(ctx, r.Client); clusterProvider == "aws" {
        if svc.ObjectMeta.Annotations == nil {
            svc.ObjectMeta.Annotations = make(map[string]string)
        }
        svc.ObjectMeta.Annotations["service.beta.kubernetes.io/aws-load-balancer-type"] = "external"
        svc.ObjectMeta.Annotations["service.beta.kubernetes.io/aws-load-balancer-nlb-target-type"] = "ip"
        svc.ObjectMeta.Annotations["service.beta.kubernetes.io/aws-load-balancer-scheme"] = "internet-facing"
    }

https://github.com/kubeslice/worker-operator/blob/master/controllers/slice/slice_gw_edge.go#L128C1-L137C3
the LB is getting stuck into "pending" state on AWS when protocol is TCP. The issues were resolved simply by removing the annotations.
👟 Reproduction steps
while testing the SGE on private clusters, we found some issues with AWS specific annotations that worker-operator is adding.
👍 Expected behavior
external lb start running without any issue.
👎 Actual Behavior
The External LB is getting stuck into "pending" state.
🐚 Relevant log output
No response
Version
1.2.0
🖥 What operating system are you seeing the problem on?
Windows
✅ Proposed Solution
We can introduce a new field in the Cluster Custom Resource Definitions (CRDs) for a set of annotations for the External Load Balancer (Ext LB). If any cloud provider needs specific annotations for their Network Load Balancer (Network LB), these can be passed as input during the creation of the Cluster CRD. The Slice Gateway Edge (SGE) will then take these annotations and apply them to the External Load Balancer during its creation.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

Code of Conduct

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

Hi team! Is this being worked on? If not, I want to give it a try.
/assign

@Bhargav-InfraCloud, Thanks you for addressing the issue. You will likely need more details, so please join this channel if you are not here yet - https://kubernetes.slack.com/archives/C03Q64HNEJF, and contact Mridul Gain or Bharath for a detailed explanation.

Sure @narmidm. Will check with them. Thanks!

@Bhargav-InfraCloud any update. did you get clarification from @mridulgain?

@narmidm Yes, he has shared a few details on Slack. Unfortunately, I got caught up with some other work around the same time and it is still going on. If anyone is up for working on this, please feel free to pick. Otherwise, I'll try again sometime.

Hey @narmidm @mridulgain, Is this still open?

the LB is getting stuck into "pending" state on AWS when protocol is TCP. The issues were resolved simply by removing the annotations.

It seems like above is already fixed in this PR: https://github.com/kubeslice/worker-operator/pull/325 where we are only adding annotations for udp protocol?

hey @Rajan-226 yes the issue is still open because even if the issue was patched by adding AWS specific annotations to the LoadBalancer, we still don't have a way to pass vendor specific annotations in the control plane as per the proposed solution in the issue #330.

✅ Proposed Solution
We can introduce a new field in the Cluster Custom Resource Definitions (CRDs) for a set of annotations for the External Load Balancer (Ext LB). If any cloud provider needs specific annotations for their Network Load Balancer (Network LB), these can be passed as input during the creation of the Cluster CRD. The Slice Gateway Edge (SGE) will then take these annotations and apply them to the External Load Balancer during its creation.

@mridulgain I can try working on this, I would just need a start.
I checked the codebase of woker-operator, but didn't find any cluster CRD? I could see serviceexport, serviceimport, slice, slicegateway. Could you help me with some first timer guide so that I can get this done?

So, let me know if my understanding regarding the steps is correct?

Add a field for required annotations in cluster CRD.
Use that field in worker operator for adding annotation and remove existing logic.

Yes @Rajan-226 this is what we intend to implement.

For existing users, we can't stop supporting aws specific annotations which are already added in code. So, this needs to be taken care in cluster controller now?

We don't want to hard code these cloud provider specific annotations in reconciler logic. Still we can keep the logic to add AWS specific annotation in the cluster controller for now and remove it eventually.

This is a secondary thing, Is there any guide to test the flow?

Please checkout this installation doc: https://kubeslice.io/documentation/open-source/1.3.0/category/install-kubeslice

@mridulgain @narmidm After analysing, it seems like this will complicate things a bit.
We're not fetching cluster CRD currently in worker-operator and instead just getting cloudregion from nodes labels. So, we would need some identifier here to fetch corresponding cluster CRD which seems to be not there.
Also, to default AWS specific annotation in the new field introduced, we would need a mutuating webhook for cluster CRD and fetch nodes there to see if cloud region is AWS - which I'm not sure if it's feasible or not.

@Rajan-226 Thanks for the suggestion.
I think taking annotations as an input in the cluster CR as a user configuration seems like a viable approach. It would simplify handling cloud-specific annotations by allowing users to specify them directly.
By storing this in the cluster CR, we can easily manage it during service creation and avoid any complexity that comes with different cloud provider. If no annotation is provided, we can simply skip adding it to the Load Balancer, which should cover the use case where no special annotation is needed.
Please share if you have any alternative suggestions on this matter.

@Rajan-226, Do you need any further help?


Artisan serve ignores REAL environment variables

Laravel Version: 8.82.0
PHP Version: 8
Database Driver & Version:

Description:
I run Laravel via Sail (version 8.1) and supervisord is used to serve. However, while the variables from .env clearly show up and can be used, this is not true for the REAL system/server environment variables. According to docs these should overwrite the variables but nope. I have tried everything but I cannot let my docker/supervisord inject any variables into Laravel. However, this is the normal application for docker: Inject something.
Steps To Reproduce:
My supervisord.conf is this (sail default for 8.1)
[supervisord]
nodaemon=true
user=root
logfile=/var/log/supervisor/supervisord.log
pidfile=/var/run/supervisord.pid

[program:php]
command=/usr/bin/bash -c "export TEST_VAR_A=100 && env && TEST_VAR_B=200 /usr/bin/php /var/www/html/artisan serve --host=<IP_ADDRESS> --port=80"

user=sail
environment=LARAVEL_SAIL="1",TEST_VAR_C="100"
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0

As you can see, I add test vars at various places. I also run env above and, in the log, I see that this environment variable is correctly within the env. The environment variables are everywhere...
However, once in Laravel (whether I use getenv, check config, manually use env() function for a specific environment variable, it does not matter), I cannot access ANY of my TEST_VAR_x variables.
It cannot be so difficult to just pass in environment variables and use them in PHP? This is no issue in any other programming language/framework I know of including Python/Django, Go, Rust, custom C++, RuR, Java, JS Node, ...
The process of how environment variables go from the system/server environment into Laravel does not seem to be documented well either. Also, each google search for "environment variables" in PHP silently assumes that always .env is meant... PHP's way of adding some EXTRA variables that are actually not what the whole world understands by environment variables - thus neatly overriding a well-known and important concept and making it un-google-ble.
For anyone else reading this: My shitty workaround is for now to have some placeholder in .env file and run in supervisord a sed replacing the content of this variable.
Sorry, I'm exhausted and frustrated.
But I appreciate very much any help...

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? If so, please open up a new issue and we'll help you out.
Thanks!

It's a function, not a bug! The Illuminate\Foundation\Console\ServeCommand define the property $passthroughVariables. See:

So, in startProcess method, we found this:
/**
 * Start a new server process.
 *
 * @param  bool  $hasEnvironment
 * @return \Symfony\Component\Process\Process
 */
protected function startProcess($hasEnvironment)
{
    $process = new Process($this->serverCommand(), public_path(), collect($_ENV)->mapWithKeys(function ($value, $key) use ($hasEnvironment) {
        if ($this->option('no-reload') || ! $hasEnvironment) {
            return [$key => $value];
        }

        return in_array($key, static::$passthroughVariables) ? [$key => $value] : [$key => false];
    })->all());

    $process->start($this->handleProcessOutput());

    return $process;
}

Because of this, only the environments defined in $passthroughVariables will be passed to the PHP server. Looking for the past, others projects had problems with this, like in PR https://github.com/laravel/framework/pull/46857.
@driesvints , it is possible to reopen the issue? Or can we suggest a new feature to customize which environment variables are loaded?

For documentation purposes, we can rewrite the php artisan serve command creating a new Console Command:
php artisan make:command ServeCommand

Now, extends the Illuminate\Foundation\Console\ServeCommand class, adding all the extra environments:
namespace App\Console\Commands;

use Illuminate\Foundation\Console\ServeCommand as BaseServeCommand;

class ServeCommand extends BaseServeCommand
{
    /**
     * The environment variables that should be passed from host machine to the PHP server process.
     *
     * @var string[]
     */
    public static $passthroughVariables = [
        'APP_OTHER_ENV', # The new environment
        'APP_ENV',
        'IGNITION_LOCAL_SITES_PATH',
        'LARAVEL_SAIL',
        'PATH',
        'PHP_CLI_SERVER_WORKERS',
        'PHP_IDE_CONFIG',
        'SYSTEMROOT',
        'XDEBUG_CONFIG',
        'XDEBUG_MODE',
        'XDEBUG_SESSION',
    ];
}

So, if you are using Laravel Sail, you will able to add the APP_OTHER_ENV via Docker Compose environment:
# For more information: https://laravel.com/docs/sail
version: '3'
services:
    laravel.test:
        build:
            context: ./vendor/laravel/sail/runtimes/8.2
            dockerfile: Dockerfile
            args:
                WWWGROUP: '${WWWGROUP}'
        image: sail-8.2/app
        extra_hosts:
            - 'host.docker.internal:host-gateway'
        ports:
            - '${APP_PORT:-80}:80'
            - '${VITE_PORT:-5173}:${VITE_PORT:-5173}'
        environment:
            APP_OTHER_ENV: 'new_environment' # The new environment
            WWWUSER: '${WWWUSER}'
            LARAVEL_SAIL: 1
            XDEBUG_MODE: '${SAIL_XDEBUG_MODE:-off}'
            XDEBUG_CONFIG: '${SAIL_XDEBUG_CONFIG:-client_host=host.docker.internal}'
            IGNITION_LOCAL_SITES_PATH: '${PWD}'
        volumes:
            - '.:/var/www/html'
        networks:
            - sail
networks:
    sail:
        driver: bridge

I ended up creating a custom serve command as @MateusBMP suggested. Worked perfectly for my use case locally. Thanks.


ML 4.2: Contrast in Supervised, Unsupervised and Reinforcement Learning (D)

Description
📌  Issues for Week 4
Welcome to 'ML' Team, good to see you here
▶ This issue will helps readers in acquiring all the knowledge that one needs to know about ---- Contrast in Supervised, Unsupervised and Reinforcement Learning
🔴 To get assigned to this issue, add your Batch Numbers mentioned in the spreadsheet of "Machine Learning", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
✔ Domain : Machine Learning
🔴🟡 Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.

"Issue Title" and "PR Title should be the same. Include issue number along with it.

Changes should be made inside the Machine Learning/Machine_Learning/Reinforcement_Learning Branch.

Follow Contributing Guidelines & Code of Conduct before start Contributing.

This issue is only for 'GWOC' contributors of 'Machine Learning' domain.

✅ To be Mentioned while taking the issue :

Full name
Batch Number
GitHub Profile Link
Which type of Contribution you want to make :

[ ] Documentation (Coding in .ipynb file, show the implementation)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎
Domain
Machine Learning
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Name: Yugal Agarwal
Batch - 1
Profile: https://github.com/Yugal41735
Documentation

@Yugal41735 Issue assigned to you, complete this within 3 days.

Yup I will make pr by today 👍
On Sun, 10 Oct 2021, 11:45 Abhishek Sharma, @.***>
wrote:

@Yugal41735 https://github.com/Yugal41735 Complete your previous issue
first.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/issues/5324#issuecomment-939414572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZOLN7752TZOCQ5ZUEQEETUGEVPXANCNFSM5FWCRYXA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Name: A.S.L.Manasa
Batch - 1
Profile: https://github.com/ASLManasa
Documentation

@ASLManasa issue assigned to you, complete this within 3 days.

Tanvi Deshmukh
Batch 5
Plz assign to me

Palamala D Sai Niharika
Batch 1
https://github.com/D-Palamala-Sai-Niharika
Documentation
Plz assign to me

@abhisheks008 made a pr Kindly check it. Apologize for the delay.