Correction for raw affiliation MIP -
Motricité, interactions, performance UR 4334 / Movement - Interactions - Performance

Correction needed for raw affiliation MIP -
Motricité, interactions, performance UR 4334 / Movement - Interactions - Performance
raw_affiliation_name: MIP -
Motricité, interactions, performance UR 4334 / Movement - Interactions - Performance
new_rors: ;04q2ax456
previous_rors:
works_examples: W4386614227
contact: 7dc947521fc811cdcd2813885e8f7300:2699af666e211653b11e7a892f4059 @ univ-nantes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Unable to change profile picture

Unable to change my profile pic in gatsby starter blog I tried and committed to github multiple times but the change is not reflected!

Unable to change my profile pic in gatsby starter blog I tried and committed to github multiple times but the change is not reflected!

For the changes to reflect, u will to put your profile pic file name in bio.js file .
Follow these steps .
content>assets>upload ur profile pic here.
Then , content>src>components>bio.js . Now in bio.js file on line 15 put your profile pic file name there.
Commit your chnges . And Done . Profile pic will be uploaded

Unable to change my profile pic in gatsby starter blog I tried and committed to github multiple times but the change is not reflected!

For the changes to reflect, u will have to put your profile pic file name in bio.js file .
Follow these steps .
content>assets>upload ur profile pic here.
Then , content>src>components>bio.js . Now in bio.js file on line 15 put your profile pic file name there.
Commit your chnges . And Done . Profile pic will be uploaded

Thanx! it helps.


Keep track of time when in Interrupted, Finished or Refreshed state

Dog fooding this feature for the past few weeks revealed that a tweak is needed in order to make this complete. Grace time is acceptable when going from focused to finished. But allowing leniency when going from refreshed to focused is detrimental to keeping up with the task. Breaks are invariably extended, and the entire work-break cycle falls apart.
Remove the grace period after the relaxed state is complete, and always automatically transition back to the focused state after the break period is over.


define_plu_com_squareup_okio__okio resource is generated twice

Environment is the same as in previous issues except that I've removed dependency on BigImageViewer and GlideImageLoader.
About libraries version is now 8.0.0-b01 but issue also occurs in a06-a08.
aboutlibraries.xml contains 2 strings with the same id:
<string name="define_plu_com_squareup_okio__okio"></string>
<string name="define_plu_com_squareup_okio__okio">owner</string>

It looks like each other string resource related to okio, apart from that one is duplicated (not empty) I've checked few ones.
Here are my quick workarounds: https://github.com/DroidsOnRoids/AboutLibraries/commits/feature/aboutlibs_next_gen
Proper solution needs to be cleaner.

hmmm I will have to investigate.
do you have the dependency which causes this? theoretically it should be impossible that you h ave the same dependency twice

I'd love to try to reproduce it as equal as possible

It's a multi-module project with dozens of dependencies.
Here are fragments of dependency graph containing okio:
|    \--- com.squareup.leakcanary:leakcanary-android:2.1
|         +--- com.squareup.leakcanary:leakcanary-android-core:2.1
|         |    +--- com.squareup.leakcanary:shark-android:2.1
|         |    |    +--- com.squareup.leakcanary:shark:2.1
|         |    |    |    +--- com.squareup.leakcanary:shark-graph:2.1
|         |    |    |    |    +--- com.squareup.leakcanary:shark-hprof:2.1
|         |    |    |    |    |    +--- com.squareup.leakcanary:shark-log:2.1
|         |    |    |    |    |    |    \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.50 -> 1.3.61 (*)
|         |    |    |    |    |    \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.50 -> 1.3.61 (*)
|         |    |    |    |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.3.50 -> 1.3.61 (*)
|         |    |    |    |    \--- com.squareup.okio:okio:2.2.2
|         |    |    |    |         \--- org.jetbrains.kotlin:kotlin-stdlib:1.2.60 -> 1.3.61 (*)
|         |    |    |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.3.50 -> 1.3.61 (*)
|         |    |    |    \--- com.squareup.okio:okio:2.2.2 (*)

|    +--- com.github.ChuckerTeam.Chucker:library:3.0.1
|    |    +--- org.jetbrains.kotlin:kotlin-android-extensions-runtime:1.3.41 -> 1.3.61
|    |    |    \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.61 (*)
|    |    +--- org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.3.41 -> 1.3.61 (*)
|    |    +--- com.google.code.gson:gson:2.8.5
|    |    +--- com.squareup.okhttp3:okhttp:3.12.2
|    |    |    \--- com.squareup.okio:okio:1.15.0 -> 2.2.2 (*)

@koral-- hmmm that doesn't seem to be it. could it be that you have 2 different build variants?

Just adding those dependencies does not result in the problem

Yes, I have 3 build types (and 0 flavors) so 3 varinats.
Chucker is only dependency in 2 of them.
Leakcanary in 1 of 2 above.

I have the feeling that this is the problem. and that version is different in those 2 variants. as such the componentIdentifier does not match

Yep, they depend on different okio versions: com.squareup.okio:okio:1.15.0 -> 2.2.2 (*)

Your fix seems to be fine though. based on the fact that we require the xml parsing first to get the proper unique ID (which is without the version)
Will do a b02 and then slow down with updates again :D


Add Heartbeat and Deviation to Contract Pages

data.chain.link is a very inefficient way for a customer to see heartbeat and deviation thresholds for feeds, and some feeds are not visualized on that page. As such, there is no way for a user to find this information in some cases, or in the best case scenario, it will take them a while to obtain the information.
I propose adding a column for deviation and a column for heartbeat on these pages, just like we have for decimals.
https://docs.chain.link/docs/ethereum-addresses/
https://docs.chain.link/docs/binance-smart-chain-addresses/
https://docs.chain.link/docs/matic-addresses/
https://docs.chain.link/docs/xdai-price-feeds/
https://docs.chain.link/docs/huobi-eco-chain-price-feeds/
https://docs.chain.link/docs/avalanche-price-feeds/

I agree that this information is currently difficult to find, or impossible without contacting the team in some cases. However, I wonder whether this data fits here, or if it should live somewhere else.
The current fields (decimals and address) directly affect the consumer contract. Both are critical in consuming the data. We know that these pages are used primarily for copy-pasting. If we add heartbeat and deviation, I worry that we're muddying this very targeted water with less important info.
That's my gut, open to opposing view though.

See the image below for the suggested approach. I've been informed that this is something that we're frequently asked about, so we should go ahead and do this.

fixed with #189


Place fish prompt in /etc/fish/functions/fish_prompt.fish to allow user override

The fish prompt is currently placed in /etc/fish/conf.d/fish_prompt.fish. Normally, fish_prompt.fish is expected to contain an function and is put in a functions directory, either /etc/fish/functions by default, or overridden by a user in ~/.config/fish/function. Fish will then autoload the function when it's needed.
I'm not 100% sure of the specific load order, but it seems like having the function fish_prompt in /etc/fish/conf.d/fish_prompt.fish means that a user's custom fish_prompt.fish is never loaded. This can be confirmed by removing /etc/fish/functions/fish_prompt.fish and seeing your custom fish_prompt.fish loaded as expected.

Marked as a draft. It looks like the codespaces that's live right now is behind master 😅  Trying to figure out if it is still a problem or not in master.

Thank you for this! I don't think we have any regular fish users as reviewers for this image :)


Implement models/views/etc. for models, jobs and worker nodes

Implement the required models, views, etc. for the following pieces of functionality:

deep-learning models
jobs/job templates
worker nodes

See the documentation

This functionality is implemented as of commit d8df6245c5a2445f9f9ab727f3ecf4ddfb33b5d8


Example submenu

On your example page, you show a good example of double wheel nav. but it doesnt work well because all the subemenu is reachable (by click i mean) even the slices hidden.
Indeed you are only setting the opacity of your svg wich make it fade away but still clickable. I have resolve this on my application by setting the visibility attribute to 'hidden' to all the nav slices (svg object) in my menu programmatically.

@ThomBian Thanks for your feedback!
I modified the submenu example, here I my preferred solution:
//Hide submenu
wheel.navItems[0].navItem.hide();
//Show submenu
wheel.navItems[0].navItem.show();


plasma: 5.10.5 -> 5.11.0

Motivation for this change
KDE Plasma feature release!
Cryfs support is removed from the new plasma-vault feature as I do not want to package & maintain this.
Also had to update Digikam and libqtav as Digikam would not build.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/) (not all but I have tested getting a fully functional desktop)
[x] Fits CONTRIBUTING.md.

cc @ttuegel

Do you have any problems with SDDM after this update?
I'm also using qt 5.9.2, but that worked before the update without any problems.

@bkchr I'm not aware of any problems though I have only tested with auto login.

@bkchr This only happens with the breeze theme, not with the official sddm themes.

Nice that you can reproduce it. Any idea what could be the problem?

We are still using sddm 0.15 while 0.16 was just released so maybe upgrading that as well helps?

@peterhoeg I tried that and it does not resolve the issue.

Thanks! I'll check this out in a bit.
Regarding plasma-vault, have you checked that it works with encfs?

@ttuegel Yes I tested it out and it works fine.

@adisbladis I can't see any reason for the segmentation fault in the SDDM greeter, either. It might help if you rebuilt Qt with debugging enabled.

With cryfs in master, do you feel like adding back the cryfs support to the vault?

Sddm works on my PC with Nvidia GPU, but on my Laptop with Intel GPU is segfaults. Maybe it is somehow related to the GPU?

Maybe it is somehow related to the GPU?

That is possible.
We may need to give serious consideration to dropping SDDM. From reading Mesa bug reports, it turns out that KDE upstream does not test anything involving Xorg and their developers only use Wayland, implying that they do not test SDDM either.

@peterhoeg I've added back cryfs support to vault. Thanks for the cryfs package :)
@ttuegel I'm also getting the crash with current mesa from master.

I'm also getting the crash with current mesa from master.

master has mesa-17.1.10, but staging has mesa-17.2.2.
If the crash is fixed with mesa-17.2.2, then we can just wait. Otherwise, we will need to file a bug report upstream with KDE.

Some users have reported that running SDDM with HiDPI enabled causes crashing due to some problem in Qt. The Plasma theme may exercise some bad code path. We should try disabling HiDPI as in sddm/sddm#701.

@ttuegel Beatiful! That was it.
I applied the fix as a patch changing the default behaviour (hidpi off by default).
I considered just changing the nixos service but felt this was more appropriate and easier to track with the next sddm upgrade when this will hopefully have been fixed.

Ahh that is nice. I have a question regarding Wayland, @ttuegel do you think we could start to enable it in nixos for kde?

do you think we could start to enable it in nixos for kde?

Not yet. Just like we have a custom startkde script to start an X11 session, we need custom startplasma and startplasmacompositor scripts.

@adisbladis hmm, for me it still does not work :/ Did you also upgrade your mesa?

@bkchr No I did not upgrade my mesa. I saw in the sddm issue tracker that there are a lot (at least 3) of these issues causing similar symptoms.

@adisbladis I tried to find the commit that is responsible for the linker error. Git bisect says that the following commit is the first one, where the build fails: https://github.com/NixOS/nixpkgs/commit/d32f7f4bb3b6a80fa79f097881b92bcebf702478
This does not look that suspicious ^^

Updated PR to plasma 5.11.1.
Also applied a commit from @bkchr that disables the gold linker for all things Qt.
This fixes linker errors with plasma-integration after qtuickcontrols2 was added as a dependency.
Presumably fixes some other packages too.

hmm, for me it still does not work :/ Did you also upgrade your mesa?

@adisbladis
I tried again with 4a55bbb, and I still get a blank screen with SDDM, too.

@ttuegel Interestingly enough I get the same behaviour now after rebasing even with the patch applied so it seems like we have uncovered yet another bug in sddm.

digikam and libqtav were merged to master, dropped those commits and rebased.

we have uncovered yet another bug in sddm.

Nope, we're hitting this QML cache invalidation bug:
https://bugreports.qt.io/browse/QTBUG-62302
You can work around it by removing /var/lib/sddm/.cache/sddm-greeter/qmlcache.
I will see about backporting this patch to our Qt. 😃

Ohh nice for finding that!

Merged in f7de0da188781aea2a4bf2b17e1fbaf8d65925da.

Has anybody else been unable to launch KDE since the upgrade to plasma 5.11? I have 2 machines here and while one is perfectly fine, the other just shows a black screen after logging in from sddm. I need to manually wipe /var/lib/sddm/.cache/sddm-greeter/qmlcache for sddm to come up despite @ttuegel rm in the setup script as well. All I see is kded5 core dumping.

I had the same problem for my laptop, I also needed to rm the directory by hand. But I don't know if I need to do that everytime.

the other just shows a black screen after logging in from sddm

This doesn't sound like an issue with the SDDM cache, it sounds like an issue with the qmlcache for Plasma! Do you have any qmlcache directories in $HOME?

Ohh, for me this happened to be SDDM crashing.


Temporary redirect to image URL when using serve view

When using the image_url template tag, and the serve view configured to redirect rather than serve directly, the redirect is handled permanently. This means if the image changes, the originally redirected URL becomes incorrect, as eg the S3 file key has changed.
This PR changes the redirect to be temporary, but adds a cache header to attempt to recover some performance lost from clients needing to check the redirect more often.

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[x] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[x] Please list the exact browser and operating system versions you tested:
[x] Please list which assistive technologies [^3] you tested:

[x] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

@zerolab all good from my end. Thanks.


Enhanced configuration

[ ] 1. Store config in the environment

According to 12 factor's config specification. Our configuration still in python code.

We need to enhance it using environment or dotenv.

[x] 2. Optimized the stage template code

#153


 We either need to speed them up, or have a better placeholder or both.

the documentation dropdown animation speed needs to be increased (@tripodsan)


Terminal tab hover is often in the way of clicking

Here the area is so small that I cannot click anymore:

Oh I think I know why this wasn't happening automatically, fix coming.


Add Twighlight Forest Integration

Duplicate what they had in the past. They won't add it back again, so safe to add.

I was about to say that it already had integration lol.
I guess they removed it in 1.19, and if so I'm kinda wondering why.


Docker Quickstart Failure to Write/Read Configuration File

Steps:
Follow quickstart guide: https://openziti.github.io/ziti/quickstarts/network/local-with-docker.html
On the step of running the docker run command it attempts to write a file, then read a second file. Neither files exist despite logged as created.

Also same issue while running through the compose file as well if that's helpful

i must admit - i've not tried to run these from within windows. Looks like it needs a caveat indicating to change the paths accordingly if you're going to use windows (or we need to provide the actual windows equivalents)

can you provide the exact setup you have - as well as the exact command you ran for each screenshot?


[Feature Request] Add element by element tensor reduction

Greetings,
Motivation
I am currently refactoring my VQ-VAE-2 repo to use :hugs: Accelerate (among other changes). I really want to use it in a data parallel context, but there is a missing feature in the library that is blocking this.
Although all-reduce ops exist in the library such as accelerate.utils.reduce, I want a method that preserves the dimensions of the tensors, simply performing the reduction element by element across processes. This is so I can calculate some statistics to update the vector quantisation codebook using EMA. The aforementioned function will instead collapse the tensor into a 0-dim tensor, which is not useful to me.
Feature
To be explicit, suppose we have a tensor x with value [1, 2, 3] on process 1 and [3,2,1] on process 2, I want a function that can return the element-by-element all-reduce (assuming sum reduction) result [4,4,4].
It would be nice to have other reductions available too.
The code could perhaps look like this:
import accelerate
accelerator = accelerate.Accelerator()

# generate a per process tensor
x = torch.rand(4, 4)
x = accelerator.tensor_reduce(x)
# or
x = accelerator.reduce(x, keepdims=True)
# or, use the `accelerate.utils.reduce` version
print(x) # returns result with same shape as original tensor, but with updated values

I feel the latter fits better into the current API.
I could use accelerator.gather and then perform the sum after, however I think a dedicated reduce op would be more efficient.
I'm aware that this feature kinda goes beyond data parallelism into tensor parallelism. However, in my use case this just updates the codebook directly in the forward pass and does not take part in autograd at all. So despite this basically being a limited form of data parallelism, it is no more complicated that reduce ops we already do for metrics and the like. Hence, I think it could be in scope for accelerate.
Thanks!

It would be valuable to have more reduction operations indeed. Would you like to open a PR to add this one? Relying on the existing gather to make sure it works on all kinds of distributed setups out of the box.

I can create a PR as an initial POC. Do you think the interface with keepdims is the best option?
However using gather (I think) is less efficient than using reduce ops as we will at some point store all x tensors to be reduced on all processes. Ideally we would do a real reduce using whatever chosen backend, however I wouldn't know how to do that.

Hi, any thoughts on the above? i.e. a separate function or try and integrate it with the existing reduce functions? Happy to make a PR but don't want to make something that doesn't fit with design philosphy of this library.

Hello @vvvm23, I feel this is already supported. Below is the sample code and output:

Code: test_reduce_elementwise.py:

from accelerate import Accelerator
import torch

if __name__ == "__main__":
    accelerator = Accelerator()
    #print(accelerator.state)

    if accelerator.process_index == 0:
        tensor_to_reduce = torch.tensor([1.,2,3])
    else:
        tensor_to_reduce = torch.tensor([3.,4,0])
    tensor_to_reduce = tensor_to_reduce.to("cuda")
    #print(tensor_to_reduce)

    reduced_tensor = accelerator.reduce(tensor_to_reduce)
    print(reduced_tensor)

Output of command accelerate launch --num_processes=2 --multi_gpu test_reduce_elementwise.py:

[18:11:44] WARNING  The following values were not passed to `accelerate launch` and   launch.py:1074
                    had defaults used instead:
                            `--num_machines` was set to a value of `1`
                            `--mixed_precision` was set to a value of `'no'`
                            `--dynamo_backend` was set to a value of `'no'`
                    To avoid this warning pass in values for each of the problematic
                    parameters or run `accelerate config`.
tensor([4., 6., 3.], device='cuda:1')
tensor([4., 6., 3.], device='cuda:0')

Isn't this what you mentioned in the issue description?

Hello @vvvm23, I feel this is already supported. Below is the sample code and output:
1. Code: `test_reduce_elementwise.py`:

from accelerate import Accelerator
import torch

if __name__ == "__main__":
    accelerator = Accelerator()
    #print(accelerator.state)

    if accelerator.process_index == 0:
        tensor_to_reduce = torch.tensor([1.,2,3])
    else:
        tensor_to_reduce = torch.tensor([3.,4,0])
    tensor_to_reduce = tensor_to_reduce.to("cuda")
    #print(tensor_to_reduce)

    reduced_tensor = accelerator.reduce(tensor_to_reduce)
    print(reduced_tensor)

2. Output of command `accelerate launch --num_processes=2 --multi_gpu test_reduce_elementwise.py`:

[18:11:44] WARNING  The following values were not passed to `accelerate launch` and   launch.py:1074
                    had defaults used instead:
                            `--num_machines` was set to a value of `1`
                            `--mixed_precision` was set to a value of `'no'`
                            `--dynamo_backend` was set to a value of `'no'`
                    To avoid this warning pass in values for each of the problematic
                    parameters or run `accelerate config`.
tensor([4., 6., 3.], device='cuda:1')
tensor([4., 6., 3.], device='cuda:0')

Isn't this what you mentioned in the issue description?

That is.. interesting. I am running on CPU as I don't currently have access to a GPU. If I remove the .to("cuda") part of your code I get a different result:
> accelerate launch --num_processes=2 --cpu test_reduce_elementwise.py
The following values were not passed to `accelerate launch` and had defaults used instead:
	`--num_machines` was set to a value of `1`
	`--mixed_precision` was set to a value of `'no'`
	`--dynamo_backend` was set to a value of `'no'`
To avoid this warning pass in values for each of the problematic parameters or run `accelerate config`.
tensor([1., 2., 3.])
tensor(6.)

I am using accelerate==0.15.0

Hello @vvvm23, in the above example of CPU, could you uncomment #print(accelerator.state). I feel num_processes is 1, wherein there is only one tensor and the reduce is simply summing that tensor which is expected behaviour

Num processes: 1
Process index: 0
Local process index: 0
Device: cpu
Mixed precision type: no

So, num_processes is indeed 1, despite me specifying 2.

[...] the reduce is simply summing that tensor which is expected behaviour

I really feel like it shouldn't be the expected behaviour. If the point of accelerate is to separate model code and the like from parallel execution strategies, why does the shape of the output vary depending on the number of processes? It feels strange to me that the output of an operation in my model changes depending on the execution strategy, when the idea is to abtract away this complexity.
It should be worth saying, that when I originally made this issue I was testing on (a single) GPU, so this isn't a CPU only issue.

To be explicit, suppose we have a tensor x with value [1, 2, 3] on process 1 and [3,2,1] on process 2, I want a function that can return the element-by-element all-reduce (assuming sum reduction) result [4,4,4]

Hello, if it was single GPU, then there is no concept of multiple processes but that was the main point mentioned in issue description. I think I am confused wrt what the issue is. Could you please provide a minimal reproducible example for us to deep dive.

@vvvm23 to see just what our current reduce implementation is, I've dropped it below. You can see that on a single GPU (or on CPU), it calls .sum() or .mean() depending on the reduction specified, otherwise calls the appropriate reduction otherwise:
        if state.distributed_type == DistributedType.TPU:
            xm.all_reduce("sum", cloned_tensor)
            return cloned_tensor
        elif state.distributed_type.value in CUDA_DISTRIBUTED_TYPES:
            torch.distributed.all_reduce(cloned_tensor, ReduceOp.SUM)
            return cloned_tensor
        else:
            if reduction == "sum":
                return cloned_tensor.sum()
            else:
                return cloned_tensor.mean()

I am also now a bit confused as to what exactly is the need :) https://github.com/huggingface/accelerate/blob/main/src/accelerate/utils/operations.py#L416-L446

Sorry yes, I think I confused myself too :,)
I think basically I was expecting zero code change when running the same code in a single or multi process context. So, I can develop my code on a single GPU and wrap any tensors that would need to be reduced in the future in a accelerator.reduce(...).
So, when only one process is in use, I expected it to behave as an identity operation. When multiple are in use, I expected it to perform the cross-process reduction. In any case, I expected the output shape to remain the same on all processes, so not to break any future computation using that tensor. However, depending on the number of processes the shape can remain the same, or collapse to a 0-dim tensor.
I think the confusion arose because I found this behaviour when developing on one GPU, but as I don't have multiple GPUs I executed the reproducer code I posted on multiple CPUs - which as we just saw does not actually seem to use multiple processes, even when it is specified to do so as a launch parameter.

To put it into context of what I was trying to achieve in my project, take a look at the commented out lines here
What I see when I uncomment that line is embedding_onehot_sum become a 0-dim tensor when I want it to remain as a n-dim tensor. From what I understand from the discussion so far, if I were to run the same code on 2 processes, it would now return a n-dim tensor - the correct answer.
This feels strange to me, as now I need to write extra code to handle the single process case when I thought the idea for accelerate is to abstract away logic like this.


[Bug][Lake] LOGGING_DIR is not writable by default

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
LOGGING_DIR is not writable on the apache/devlake Docker images. This results in an unhandled exception and crash of the lake container when logs aren't able to write to the devlake.log file on /app/logs.
What do you expect to happen
App should not crash if logs are unwritable.
How to reproduce
Run it on a k8s cluster where the default user is not root and the seucrityContext has non-root settings.
Anything else
Override of LOGGING_DIR works, but it's a hacky workaround to overcome a simple solution (which is a directory permissions fix).
Version
v0.18.0
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

@cicdguy Looks good to me, thanks for volunteering, and happy coding. 😊


[RELEASE-1.8] Update golang version to 1.19 for build images

What this PR does / why we need it:

Updates golang version to 1.19 for build images

Which issue(s) this PR fixes:
JIRA: SRVCOM-2370
Does this PR needs for other branches:
Will do manual cherry-pick for 1.9
Does this PR (patch) needs to update/drop in the future?:
NONE

As per Slack Discussion:
/override "ci/prow/410-e2e-aws-ocp-410"
/override "ci/prow/411-e2e-aws-ocp-411"
/override "ci/prow/412-e2e-aws-ocp-412"

For builds to pass, https://github.com/openshift-knative/serverless-operator/pull/2029 is needed.

/retest

/lgtm


404 Not Found

I have this error, what can i do?
robi@robis-thinkpad:~/MagicMirror$ sudo ./install.sh
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen....
Verbindungsaufbau zu nodejs.org (nodejs.org)|<IP_ADDRESS>|:443... verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 404 Not Found
2016-04-08 18:32:12 FEHLER 404: Not Found.

It seems it can't find the file:
https://nodejs.org/dist/latest/node-v5.10.1-linux-x86_64.tar.gz

This filename is generated based on the architecture you're currently running. What Raspberry Pi and Operating System are you running?

I try it on a ThinkPad with Unbuntu 15.10 Intel® Core™ i5-2520M CPU @ 2.50GHz × 4
uname -m
x86_64

The installer is Raspberry only. On Ubuntu, make sure the latest Node.js is installed. And then run: 'npm install' from the MagicMirror folder.
After the installation you can start the app via 'npm start'.

Great! Thank you

Question
How can i restart the mirror on the Desktop after going out with alt?

npm start

hmm.. on the wrong place?
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose config Skipping project config: /home/robi/.npmrc. (matches userconfig)
5 verbose stack Error: ENOENT: no such file or directory, open '/home/robi/package.json'
5 verbose stack     at Error (native)
6 verbose cwd /home/robi
7 error Linux 4.2.0-35-generic
8 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
9 error node v5.10.1
10 error npm  v3.8.3
11 error path /home/robi/package.json
12 error code ENOENT
13 error errno -2
14 error syscall open
15 error enoent ENOENT: no such file or directory, open '/home/robi/package.json'
16 error enoent ENOENT: no such file or directory, open '/home/robi/package.json'
16 error enoent This is most likely not a problem with npm itself
16 error enoent and is related to npm not being able to find a file.
17 verbose exit [ -2, true ]

OK STOP !
I found it ".. run from the MagicMirror Folder"
Is there a way to make a Desktop Icon with this Command to Open the Mirror from Desktop without the Terminal?

No idea yet ... If you find out how, please let us know so we can add it to the readme. (or send a pull request.)

Should be possible with a .desktop file. Google something like ".desktop run shell  script" for details, but I have not tried it.

Am 08.04.2016 um 22:12 schrieb Michael Teeuw<EMAIL_ADDRESS>No idea yet ... If you find out how, please let us know so we can add it to the readme. (or send a pull request.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Thank you. I try this and its work! :-)
Create a yourname.desktop file in your /home/user/Desktop/ directory that looks like this:
THIS IS MY EXAMPLE
PUT YOUR OWEN PATH AND NAME INTO
[Desktop Entry] Name=MagicMirror Comment=Startet den Spiegel Exec=/bin/bash -c "cd /home/robi/MagicMirror&&npm start" Icon=/home/robi/MagicMirror/mirror.png Type=Application Terminal=false
Thanks for help.

Interesting! Thanks. I'll create a MagicMirror Icon soon, and add the above file to the repo so anyone can use it.

FYI, the following file would work for most people:
[Desktop Entry]
Name=MagicMirror
Comment=Start MagicMirror
Exec=/bin/bash -c "cd ~/MagicMirror&&npm start"
Icon=~/MagicMirror/mirror.png
Type=Application
Terminal=false


1.1 b3 Task setting search Fatal error

hi,
Admin page "Task setting search"
blank white page
Fatal error: Call to undefined function loadPaymentGateways() in /.........../public_html/sources/admin/ManagePaid.controller.php on line 216

It was fixed after the release of B3 with a9ce796dc8a6eeee88a918aea1f249b815e6b6eb merged in #2732

Oh... and thanks for the report! :smile:


[Bug][Seatunnel-web] Task instance filter is not working as expected

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

Task instance filter is not working as expected.
Behaviour should be same as the task filter. It should return all the task execution instances containing given jobDefineName name.

Upgrade of logback is causing problem. lets revert it to version 1.2.3.

SeaTunnel Version
NA
SeaTunnel Config
NA

Running Command
NA

Error Exception
NA

Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots

Filtering with API_JOB but it is returning all the jobs which is not correct
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

PR is merged https://github.com/apache/seatunnel-web/commit/36c85cc4884cb6015eaaeb4f4e88d26f1e3d2080


additional labels for http metrics

Is your feature request related to a problem? Please describe.
i would like to have some additional labels for the http metrics http_server_duration_average_us_total and http_server_client_average_us_total
these include: http_verb, status code http_route
for route, i think we can try to infer the route template to not pollute with to many labels
i.e if we see /api/v1/customers/1 + /api/v1/customers/2 +  /api/v1/customers/3 we can infer the route to be /api/v1/customers/$id or something like that, we can think of a logic to try to infer that
Describe the solution you'd like
change the ebpf probes to extract method, status code and route from the http request, and add it as labels to the existing metrics
Describe alternatives you've considered
No response
Additional context
No response

It's yours @NimrodAvni78 !

Awesome @NimrodAvni78 ! It will be a good capability to add!
I’d really love to see a design that would preserve the current system’s O(1) cost of handling each incoming event, because this property has been extremely useful in providing predictable performance for users.
My intuition is this is achievable, e.g., decide to handle at most N path components (say N=5) and use a hash table to keep collected metrics and which templates have been inferred. If inference logic can work “on-line” (i.e., logic can find templates as samples are coming in one at a time, without batch-processing) and is O(1) for that inference, that means inference and collection are both O(1).
The framework offers hash tables and infra to output metrics for items stored in those  hash tables (which all current metrics use).
For transparency I’m unavailable to have a discussion about this in the next few weeks (I’m on leave). Happy to discuss in September if you haven’t finished this already :)
Excited to see where you take this!


Broadcasting with 0-length dimension fails

Appears that when trying to broadcast with a 0-length dimension, Dask Array fails. In contrast, NumPy is able to handle this case and correctly. An example of the behavior is shown below and the conda environment used is included right afterwards.
Example:

In [1]: import numpy

In [2]: import numpy as np

In [3]: import dask

In [4]: import dask.array

In [5]: import dask.array as da

In [6]: a = np.ones((0, 1))

In [7]: b = np.ones((1, 5))

In [8]: a * b
Out[8]: array([], shape=(0, 5), dtype=float64)

In [9]: d_a = da.from_array(a, chunks=1)

In [10]: d_b = da.from_array(b, chunks=1)

In [11]: d_a * d_b
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-11-dcbc414326f9> in <module>()
----> 1 d_a * d_b

/zopt/conda2/envs/test/lib/python3.6/site-packages/dask/array/core.py in __mul__(self, other)
   1416
   1417     def __mul__(self, other):
-> 1418         return elemwise(operator.mul, self, other)
   1419
   1420     def __rmul__(self, other):

/zopt/conda2/envs/test/lib/python3.6/site-packages/dask/array/core.py in elemwise(op, *args, **kwargs)
   2518     shapes = [getattr(arg, 'shape', ()) for arg in args]
   2519     shapes = [s if isinstance(s, Iterable) else () for s in shapes]
-> 2520     out_ndim = len(broadcast_shapes(*shapes))   # Raises ValueError if dimensions mismatch
   2521     expr_inds = tuple(range(out_ndim))[::-1]
   2522

/zopt/conda2/envs/test/lib/python3.6/site-packages/dask/array/core.py in broadcast_shapes(*shapes)
   2490         if any(i != -1 and i != 1 and i != dim and not np.isnan(i) for i in sizes):
   2491             raise ValueError("operands could not be broadcast together with "
-> 2492                              "shapes {0}".format(' '.join(map(str, shapes))))
   2493         out.append(dim)
   2494     return tuple(reversed(out))

ValueError: operands could not be broadcast together with shapes (0, 1) (1, 5)

Environment:

name: test
channels:
- conda-forge
- defaults
dependencies:
- appnope=0.1.0=py36_0
- blas=1.1=openblas
- bokeh=0.12.9=py36_0
- ca-certificates=2<IP_ADDRESS>=0
- certifi=2<IP_ADDRESS>=py36_0
- click=6.7=py36_0
- cloudpickle=0.4.0=py36_0
- dask=0.15.4=py_0
- dask-core=0.15.4=py_0
- decorator=4.1.2=py36_0
- distributed=1.19.2=py36_0
- heapdict=1.0.0=py36_0
- ipython=6.2.1=py36_0
- ipython_genutils=0.2.0=py36_0
- jedi=0.10.2=py36_0
- jinja2=2.9.6=py36_0
- libgfortran=3.0.0=0
- locket=0.2.0=py36_1
- markupsafe=1.0=py36_0
- msgpack-python=0.4.8=py36_0
- ncurses=5.9=10
- numpy=1.13.3=py36_blas_openblas_200
- openblas=0.2.19=2
- openssl=1.0.2l=0
- pandas=0.20.3=py36_1
- partd=0.3.8=py36_0
- pexpect=4.2.1=py36_0
- pickleshare=0.7.4=py36_0
- pip=9.0.1=py36_0
- prompt_toolkit=1.0.15=py36_0
- psutil=5.3.1=py36_0
- ptyprocess=0.5.2=py36_0
- pygments=2.2.0=py36_0
- python=3.6.3=0
- python-dateutil=2.6.1=py36_0
- pytz=2017.2=py36_0
- pyyaml=3.12=py36_1
- readline=6.2=0
- setuptools=36.3.0=py36_0
- simplegeneric=0.8.1=py36_0
- six=1.11.0=py36_1
- sortedcontainers=1.5.7=py36_0
- sqlite=3.13.0=1
- tblib=1.3.2=py36_0
- tk=8.5.19=2
- toolz=0.8.2=py_2
- tornado=4.5.2=py36_0
- traitlets=4.3.2=py36_0
- wcwidth=0.1.7=py36_0
- wheel=0.30.0=py_1
- xz=5.2.3=0
- yaml=0.1.6=0
- zict=0.1.3=py_0
- zlib=1.2.8=3

Put together a fix in PR ( https://github.com/dask/dask/pull/2784 ).


Date field dropdown locale settings.

Hello Grist team!
I ask you to consider the possibility of setting up a drop-down calendar for date field, such as localization, setting the beginning of the working week.

Repeating my point from the accidental duplicate #1104: roughly half of the world uses Monday as start of the week, rather than Sunday. I'm not sure if this should be a column-level setting, or a global setting (based on system locale), or both (to allow overriding the system locale with a custom column locale).

Grist's ease of use is innovative!
But it's a pity that some lack of i18n is discouraging adoption. Unfortunately, many clients in our country evade product when the calendar month or week is in foreign language. bootstrap-datepicker has i18n feature already you know, so I wish it will be easy to reflect the language settings. Other i18n features works well, so It would be great if you could give this issue a higher priority. I am really glad if there is a way to customize bootstrap-datepicker in Grist.
Thank you.


Do not use Intune in your examples

Hi,
You are using Intune in your examples. Until Intune is free, please document how certificates are published without it.
TIA

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

ID: 43c175ce-52a4-8b46-716f-106b4d55106c
Version Independent ID: 374a7e9d-6e4f-f188-328b-4ca2651a9481
Content: Configure Azure AD joined devices for On-premises Single-Sign On using Windows Hello for Business - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-base.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

Hello @arcotek-ltd ,
please document how certificates are published without it - you cannot add certificate as trusted to AAD joined computers without intune. There is an option to add certificate manually to each computers' "Trusted root certification authorities" container, but it obviously is not appropriate for enterprises.
Thank you

@arcotek-ltd - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by MaratMussabekov so we will close this issue.
Thank you for your contribution to make the docs better! Much appreciated!


Add .git after github link in order to make the file properly

Change https://github.com/personalrobotics/apriltags-cpp to https://github.com/personalrobotics/apriltags-cpp.git so that it can download and make the file successfully.

Looks good.  I'm not sure how this was working for other people before.


Runtime panic when running unit-tests against go-mod-messaging module

The current code base of master branch will encounter runtime panic, as shown below, when running make test:
Moreover, we shall also consider to apply DevOps process to this module, so any new code commits could be verified.
CGO_ENABLED=1 GO111MODULE=on go test ./... -coverprofile=coverage.out ./...
?   	github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg	[no test files]
--- FAIL: TestClientCreatorTLS (0.00s)
    --- FAIL: TestClientCreatorTLS/Skip_TLS_Config_from_PEM_Block_for_non-supported_TLS_protocols (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x6cbb0d]

goroutine 32 [running]:
testing.tRunner.func1.1(0x7071c0, 0x963b00)
	/usr/local/go/src/testing/testing.go:1072 +0x30d
testing.tRunner.func1(0xc000153b00)
	/usr/local/go/src/testing/testing.go:1075 +0x41a
panic(0x7071c0, 0x963b00)
	/usr/local/go/src/runtime/panic.go:969 +0x1b9
github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/mqtt.TestClientCreatorTLS.func1(0xc000153b00)
	/home/judehung/MyDev/DevRepos/EdgeX/go-mod-messaging/internal/pkg/mqtt/client_test.go:444 +0x1ad
testing.tRunner(0xc000153b00, 0xc00004b650)
	/usr/local/go/src/testing/testing.go:1123 +0xef
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1168 +0x2b3
FAIL	github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/mqtt	0.009s
ok  	github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/redis/streams	0.014s	coverage: 77.1% of statements
?   	github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/redis/streams/mocks	[no test files]
--- FAIL: TestPublish (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5d78d6]

goroutine 8 [running]:
testing.tRunner.func1.1(0x60d6c0, 0x98bc50)
	/usr/local/go/src/testing/testing.go:1072 +0x30d
testing.tRunner.func1(0xc0000da300)
	/usr/local/go/src/testing/testing.go:1075 +0x41a
panic(0x60d6c0, 0x98bc50)
	/usr/local/go/src/runtime/panic.go:969 +0x1b9
sync.(*Mutex).Lock(...)
	/usr/local/go/src/sync/mutex.go:74
github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/zeromq.(*zeromqClient).bindToPort(0xc0000a3180, 0xc000018b60, 0xc, 0x0, 0x0)
	/home/judehung/MyDev/DevRepos/EdgeX/go-mod-messaging/internal/pkg/zeromq/client.go:235 +0x56
github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/zeromq.(*zeromqClient).Publish(0xc0000a3180, 0x0, 0x0, 0x646052, 0x3, 0xc000018b40, 0xa, 0xa, 0x0, 0x0, ...)
	/home/judehung/MyDev/DevRepos/EdgeX/go-mod-messaging/internal/pkg/zeromq/client.go:70 +0x268
github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/zeromq.TestPublish(0xc0000da300)
	/home/judehung/MyDev/DevRepos/EdgeX/go-mod-messaging/internal/pkg/zeromq/client_test.go:112 +0x125
testing.tRunner(0xc0000da300, 0x65a8f8)
	/usr/local/go/src/testing/testing.go:1123 +0xef
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1168 +0x2b3
FAIL	github.com/edgexfoundry/go-mod-messaging/v2/internal/pkg/zeromq	0.006s
ok  	github.com/edgexfoundry/go-mod-messaging/v2/messaging	0.003s	coverage: 85.7% of statements
ok  	github.com/edgexfoundry/go-mod-messaging/v2/messaging/mqtt	0.003s	coverage: 100.0% of statements
ok  	github.com/edgexfoundry/go-mod-messaging/v2/messaging/redis	0.003s	coverage: 100.0% of statements
ok  	github.com/edgexfoundry/go-mod-messaging/v2/pkg/types	0.004s	coverage: 90.9% of statements
FAIL
Makefile:6: recipe for target 'test' failed
make: *** [test] Error 1

These changes did pass Verify checks. Unit tests passed.
https://jenkins.edgexfoundry.org/blue/organizations/jenkins/edgexfoundry%2Fgo-mod-messaging/detail/PR-91/2/pipeline
This is very strange. After I rebase my master and run unit tests I am again getting original failure, but not the panic shown here. :-(
investigating ....

After redoing my fork to ensure my code is actuate for master branch, my unit tests failures are resolved and can not reproduce this  panic issue.

@jim-wang-intel was able to reproduce panic on his Linux system and we root caused it to code that should have always panic.
The strange thing is this should have caused panic on my Widows system and in the CI verify job, but didn't. :-(


rework CMK Helm chart to allow scaling up and down

This patch replaces cmk cluster-init deployment with Helm templates.
Single Daemonset is created to run init, discover and install commands
in the initContainers, then reconcile and nodereport are started as
regular running containers in the Pod. Using nodeAffinity allows for
scaling and provides idempotency between subsequent deployments.
It also fixes issue where helm delete --purge command would remove
cluster-init pod and RBAC/serviceaccount only, leaving any other resources
in not fully functional state.

@lmdaly @michaelspedersen could you please take a look?

While I don't know the exact details on how CMK deploys through cluster-init, I like the idea of running it as a daemonset. I also haven't tested out the update, but if it deploys as expected for you then I think it is good

CMK cluster-init creates pretty much similar set of K8s resources, but does it from the Python code, also for some reason creates separate daemonsets for each of the nodes and some installation steps are performed using job-like pods, which isn't the most elegant solution. But the biggest motivation was to be able to uninstall/reinstall/scale up CMK using Helm only - in the first version of the Helm chart only cluster-init was deployed with helm, so deleting Helm chart was deleting only the cluster-init pod, leaving everything up and running else like nothing happened.
@hey lmdaly, do you think could we go ahead and merge this PR?

@przemeklal would it be possible to remove CMK using the CMK uninstall in a Helm chart? How this way allow for scale up, when a new node is added the helm chart is just deployed there?

would it be possible to remove CMK using the CMK uninstall in a Helm chart?

Unfortunately no. helm delete can only remove resources that it created itself during helm install - if anything else is created (by cluster-init for example), Helm isn't aware of them and has no idea that something extra should be removed. cluster-init and uninstall commands in the CMK basically overlap with the Helm functionality.

How this way allow for scale up, when a new node is added the helm chart is just deployed there?

Helm chart is deployed cluster-wide only once. But it creates a single DaemonSet for CMK to run on all nodes automatically - when the new Kubernetes node is added, CMK pod is created automatically on this new node with init, install, discover executed first as the initContainers and then reconcile and nodereport running as usually - but everything is part of a single DaemonSet. This was also impossible with the cluster-init.
There's also an option to set nodeAffinity (cmk_hosts_list value in the Helm values) - in that case all nodes are added to the nodeAffinity in the DaemonSet spec and pods are scheduled only on the matching nodes. This is also mutable - helm upgrade will update the DaemonSet spec with new values.
Also - there's nothing really new that isn't in the CMK repo already - we already had separate example pod specs for all commands there.

@przemeklal okay thanks for the explanations, LGTM to me then


Enhancement [dark mode]

Enhancement [dark mode]

Please assign this to me. as I want to work on this issue

Please assign this issue to me under gssoc'24

Hello I am Gargi! I work with html,css,js,react.js and so on and am eager to learn more. I'd appreciate being assigned this task for GSSoC 24. I have used it in one of my projects and can work on it.

I've implemented this feature in my previous projects, showcasing my ability to enhance user experience through customization. With my expertise in front-end development, I'm confident I can integrate this feature smoothly into your project.
@khushi-joshi-05 could you please assign me

I've recently raised a PR in a project on the same issue and showcased my skills on the same. I request you to kindly assign me this project under GSSOC'24.
@khushi-joshi-05 can you please assign me this issue


Lanbon L8 build error using platformio-core

Perform all steps below and tick them with [x]

[x] Check the related part of the Documentation
[x] Update hasp-lvgl to the latest version
[x] Reproduce the issue and describe all steps

Describe the bug

Build for Lanbon L8 fails with:
Error: The program size (1447642 bytes) is greater than maximum allowed (1441792 bytes)
Nevertheless tried to flash to the unit, that didn't produce an error. But the device doesn't boot, only a white screen appears.
To Reproduce

Set up a platformio-core environment. (note: Tasmota builds correctly in the same environment).
Clone repo
Create platformio_override.ini where I only uncomment user_setups/esp32/*.ini and lanbon_l8
Build with pio run 2>&1 | tee build.log

See: build.log
Expected behavior

Have a build without errors.
Screenshots or video

The recent espressif v3.1.0 is quite a bit larger then v3.0.0, causing the build to fail.
I pinned it to the previous platform =<EMAIL_ADDRESS>for Lanbon L8 builds now.

OK testing...

Still not good: build.log

Which branch are you building?

The default one which comes with git clone --recursive https://github.com/fvanroie/hasp-lvgl as stated in the main readme.

OK I need to investigate this a bit further. In the meantime, you can use the auto-compiled binary from https://github.com/fvanroie/hasp-lvgl/actions/runs/622049076. The linux build seems to build find, while on Windows it fails...

I'm on Linux too..

Maybe because BLE stack included with Lanbon L8?
Compiling .pio/build/lanbon_l8/lib079/BLE/BLE2902.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLE2904.cpp.o
Archiving .pio/build/lanbon_l8/libb0f/libAceButton.a
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEAddress.cpp.o
Indexing .pio/build/lanbon_l8/libb0f/libAceButton.a
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEAdvertisedDevice.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEAdvertising.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEBeacon.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLECharacteristic.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLECharacteristicMap.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEClient.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEDescriptor.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEDescriptorMap.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEDevice.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEEddystoneTLM.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEEddystoneURL.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEExceptions.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEHIDDevice.cpp.o
Archiving .pio/build/lanbon_l8/lib083/libConsoleInput.a
Archiving .pio/build/lanbon_l8/libda1/libEEPROM.a
Indexing .pio/build/lanbon_l8/lib083/libConsoleInput.a
Indexing .pio/build/lanbon_l8/libda1/libEEPROM.a
Compiling .pio/build/lanbon_l8/lib079/BLE/BLERemoteCharacteristic.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLERemoteDescriptor.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLERemoteService.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEScan.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLESecurity.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEServer.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEService.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEServiceMap.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEUUID.cpp.o
Archiving .pio/build/lanbon_l8/lib06a/libPubSubClient.a
Indexing .pio/build/lanbon_l8/lib06a/libPubSubClient.a
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEUtils.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/BLEValue.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/FreeRTOS.cpp.o
Compiling .pio/build/lanbon_l8/lib079/BLE/GeneralUtils.cpp.o

Afaik this device doesn't support Bluetooth so maybe this just takes up the space?

I succeeded to create an image which fits in by removing robotocondensed_regular_28_nokern.c.
Since it doesn't seem support LATIN-2 or Unicode chars, it needs replacement anyway (at least for me)

0.4.0-dev now builds like this:
Visual Studio + Platformio on a Linux desktop environment:
Flash: [==========]  97.9% (used 1411030 bytes from 1441792 bytes)
Platformio-Core only on a linux VM envoronmnt:
Flash: [==========]  100.5% (used 1448530 bytes from 1441792 bytes)
Really strange...

The partition size for 0.4.0-dev is now increased to 2Mb.

Great! What's the flash size of Lanbon L8 btw?

It's 8Mb

Thx


basic auth test failing

The basic auth tests are failing.
22-5326/kfctl-2cc7/.cache/manifests exists; not resyncing " filename="kfconfig/types.go:460"
util.py                     71 INFO     time="2019-10-29T15:50:17Z" level=warning msg="Backfilling auth; this is deprecated; Auth should be explicitly se
t in Gcp plugin" filename="gcp/gcp.go:1931"
util.py                     71 INFO     time="2019-10-29T15:50:17Z" level=error msg="Could not configure basic auth; environment variable KUBEFLOW_USERNA
ME not set" filename="gcp/gcp.go:1938"

So looks like an issue with the test.

Here's the problem
https://github.com/kubeflow/kubeflow/blob/618c77bef8e8672e2df174bf25659a3dbfcb9982/py/kubeflow/kubeflow/ci/kfctl_go_test_utils.py#L243
We need to update the test to work with v1beta1

Here's the latest periodic run.
http://testing-argo.kubeflow.org/workflows/kubeflow-test-infra/kubeflow-periodic-master-kfctl-go-basic-auth-7210-3f73?tab=workflow
Build and deploy are succeeding and most KF tests are passing; e.g. kfctl_is_ready.
It looks like pytorch job and katib are failing.
There's a related issue: kubeflow/testing#509
To properly report the test results.
I'm going to mark this as fixed and open up specific bugs about katib and pytorch.


could potplay added as a support player type

Thank you for this excellent project. I set this theme with Kisaki which in wallpaper engine, looks perfect.
I use potplayer as my music player, it allow me play music with folders not playlist like other music player.
So is there any chance add it as a player, thanks again.

Unfortunately, it looks like PotPlayer does not expose its media playback controls for external programs to access like Windows Media Player or AIMP does, so that is difficult if not impossible to do unless the developers of PotPlayer changes this themselves. A user in the official Rainmeter forums had requested the same media player support in this thread here and appears to have reached the same conclusion.
If you are not completely committed to using PotPlayer, I can at the very least suggest AIMP as a feasible alternative as this is my music player of choice and it can work on a folder management system, which is how I personally organize my music as well. If not sold on the idea, most players supported natively by Rainmeter listed at the bottom of their NowPlaying documentation page as far as I understand are non-streaming based players and should fulfill your folder-organization needs perfectly if you are willing to switch.
Otherwise, I apologize since the MusicPlayer skin cannot interface with PotPlayer because it does not give control access to any external programs whatsoever, Rainmeter included. You can, however, still rewire the MusicApp to open PotPlayer on mouse click by rewiring the skin and changing its "Execution" parameter appropriately. If you use this idea, the MusicPlayer skin will become fully obsolete, and the AudioVisualizer skin will be unable to display the song title and album during playback (it will still show audio levels perfectly as it measures the system sound). However, if these consequences are negligible to you, then this is the best alternative I can recommend.

I tried AIMP, MusicBee and many other music players before, potplayer is easier to use for me, but it's not the only option.
This is kind of my own issue, thank you for taking time reply this.


Terminal blank

With the new public beta v50, it is making the terminal not work. The screen is completely blank and you can't exit out of the terminal. If mod is removed, it takes away Aquatis and Orion.

I've been having this same exact issue, it's so annoying I hope they fix it

The most you can do is download 1.0.7 or some other version im not checking all of them. cuz it works, it just doesn't display the moon list for some reason...

Still persisting post-beta :/ Hope it gets fixed soon

Hi, If your testing out the experimental v50 beta please report issues on the Lethal Company Modding discord where I have a thread about the matter! Not a big fan of Discord for forum type stuff in general but the beta is released so I can hopefully knock out issues asap and Discord is nice for me to help understand and troubleshoot these kind of errors, Thanks!

Sadly the discord link is not working. May want to add an invite to the discord server as well. So I tested each version to see what would work and what wouldn't.
1.1.6 - Not Working - Blank in game terminal - Errors in log
1.1.5 - Not Working - Blank in game terminal - Errors in log
1.1.4 - Not Working - Blank in game terminal - Errors in log
1.1.3 - Not Working - Blank in game terminal - Errors in log
1.1.2 - Not Working - Blank in game terminal - Errors in log
1.1.1 - Not Working - Blank in game terminal - Errors in log
1.1.0 - Not Working - Blank in game terminal - Errors in log
1.0.7 and Earlier - Partially Working - Terminal Accessible - Cannot View Moons - No Errors in Log

I would like a discord invite aswell, really waiting for the mod aswell :)

https://discord.com/channels/1168655651455639582/1228961224126103632

Try download this dll and replace old https://github.com/IAmBatby/LethalLevelLoader/tree/main/Thunderstore/plugins
Worked for me on v50 with Westley moons also replace LethalExpansionCore to LethalExpansionCorePatch

I fixed it: Download a mod called LethalModDataLib. For some reason it isn't listed as a dependancy on thunderstore but it does need it to work in the newer versions. Hope this helps.

I installed LethalModDataLib and it still isn't working, I'll be using the 1.0.7 version until they update it.

Only issue i've come across with the Pineguys fix is that it doesn't seem to spawn any spike traps.  Everything else seems pretty stable though

Pineguys reupload of that patch is not created by Pineguy nor is it a fully fledged fix, I'd personally suggest abstaining from using it.

Sadly the discord link is not working. May want to add an invite to the discord server as well. So I tested each version to see what would work and what wouldn't.
1.1.6 - Not Working - Blank in game terminal - Errors in log 1.1.5 - Not Working - Blank in game terminal - Errors in log 1.1.4 - Not Working - Blank in game terminal - Errors in log 1.1.3 - Not Working - Blank in game terminal - Errors in log 1.1.2 - Not Working - Blank in game terminal - Errors in log 1.1.1 - Not Working - Blank in game terminal - Errors in log 1.1.0 - Not Working - Blank in game terminal - Errors in log 1.0.7 and Earlier - Partially Working - Terminal Accessible - Cannot View Moons - No Errors in Log

Posting the errors in the logs maybe helpfully as well. 📦

On April 20th today, the LE author re uploaded a LE preview version on Thunderstore. Will future LLL versions reconsider compatibility with LE due to this?

Also same, with this (I dont even have a G Drive, wth?)
[Info   : Unity Log] Set interminalmenu to true: True
[Info   : Unity Log] Caught error while entering computer terminal. Exiting player from terminal. Error: System.NullReferenceException: Object reference not set to an instance of an object
  at LethalLevelLoader.Patches.TerminalLoadNewNode_Prefix (Terminal __instance, TerminalNode& node) [0x00001] in G:\Unity\LethalLevelLoader\LethalLevelLoader\General\Patches.cs:273
  at (wrapper dynamic-method) Terminal.DMD<Terminal::LoadNewNode>(Terminal,TerminalNode)
  at (wrapper dynamic-method) Terminal.DMD<Terminal::BeginUsingTerminal>(Terminal)
[Info   : Unity Log] Quit terminal; inTerminalMenu true?: {playerScript.inTerminalMenu}

Closed as Lethal Expansion is now deprecated.


Refactor apiconfig interfaces

This takes us from 6 layers of indirection to 2. It's still not perfect.

/assign @mikehelmick

/hold until @mikehelmick approves

/lgtm
/approve

/unhold


feat: dereferncing

looks good. have you got any place where you use this yet or maybe a test?

I did use it in a project of mine :>
But don't have any tests tho

I just published your changes under 0.1.1
Thank you for the contribution 👍


Add support: Credential Vault

Add support for credential-vault.
Please assign to me as I have the code ready. (PR #175)

This is blocked because the early adopter credential vault API isn't idempotent. n executions of monaco results in n different credentials.

@Dynatrace-Adam-Gardner I corrently don't see why this shouldn't work with monaco. The API fulfills our criteria for an "easy-to-add-api": https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/credential-vault/
For troubleshooting, can you apply a credentials-vault config and use the MONACO_REQUEST_LOG env var and post the log file here?
e.g.:
MONACO_REQUEST_LOG=requests.log ./monaco ...

This happens after the first run and on subsequent runs it stays like this. I never see a PUT.
url: https://abc123.live.dynatrace.com/api/config/v1/credentials
method: GET
==========
url: https://abc123.live.dynatrace.com/api/config/v1/credentials
method: POST
content:
{"description":"Sample set of credentials for API documentation","name":"Sample Credentials","ownerAccessOnly":"true","password":"1234abcd","scope":"SYNTHETIC","type":"USERNAME_PASSWORD","user":"foo"}
==========

Figured it out. I needed to add propertyNameOfGetAllResponse: "credentials",

Yes, the propertyNameOfGetAllResponse is a new property, which needs to be set for some APIs. In case you missed it - we ramped up on the documentation for adding new APIs recently :muscle::
https://github.com/dynatrace-oss/dynatrace-monitoring-as-code/blob/main/docs/how-to-add-a-new-api.md


importFixes: Skip alias when testing isTypeOnlySymbol

Fixes #27317

@RyanCavanaugh Should port to ts3.1?

When will this fix be released?

@morrisondavid It's already available in typescript@next. It should also be included in the next<EMAIL_ADDRESS>release.


proper recover after a database resetting

Describe the bug
we already have a recovery technique that reinitializes the database after a db reset happens to create the needed tables.
https://github.com/threefoldtech/tfgrid-sdk-go/blob/c4ed7152b9e68236ad29899aa65bda51a29d1073/grid-proxy/internal/explorer/db/postgres.go#L673-L682
but it is not complete because it depends on other tables created by the indexer, so at the end the recovery fails.
ERROR:  current transaction is aborted, commands ignored until end of transaction block

a restarting for the server should migrate the indexers (gpu/health) tables and make things work, but it would be better if we included these migrations in the recovery step.
To Reproduce

restart the database while the proxy server is running

it is already done here https://github.com/threefoldtech/tfgrid-sdk-go/blob/0552f9961c051f3c5158b702254f5d8c8009796d/grid-proxy/internal/explorer/db/postgres.go#L771


Weather forecast ignores "maxNumberOfDays"

Hi there,
currently the config parameter "maxNumberOfDays" of the module "weatherforecast" seems to be ignored - at least it does not work increasing it to more than 7 days. That is because the API needs an additional parameter "cnt", which indicates how many days are to be retrieved. Adding it to the weatherforecast.js in line 305 solves the issue for me:
params += "&cnt=" + this.config.maxNumberOfDays;
Best regards,
Mirko

Please send a PR.
Thanks!

params += "&cnt=" + (((this.config.maxNumberOfDays < 1) || (this.config.maxNumberOfDays > 128)) ? 40 : this.config.maxNumberOfDays);

Maybe add a "Good first bug" to this Issue so people who want to start helping can fix it? Otherwise I will do it sooner than later ;-)

params += "&cnt=" + (((this.config.maxNumberOfDays < 1) || (this.config.maxNumberOfDays > 128)) ? 40 : this.config.maxNumberOfDays);

I the documentation it said:
How many days of forecast to return. Specified by config.js

Possible values: 1 - 16
Default value: 7 (7 days)
This value is optional. By default the weatherforecast module will return 7 days.

I think only a limit of 16 would be nice.
And i don't think anyone need a forecast of more than 16 days.

And i don't think anyone need a forecast of more than 16 days.

and more importantly, can you GET  a forecast from any api for more that 15 days?

Well I can make it work up to 17  after there is no answer.

Still seems to be an issue
https://forum.magicmirror.builders/topic/13187/weatherforecast-showing-only-two-days/6

I wanted to add a comment here that this issue is not actually "fixed" as the new version now reverts forecasts back to showing only two days (at least when using the Free API). In doing some research, it appears that the actual URL being used to retrieve the forecast is not the correct / current one.
From what I can tell, the base URL is being built out as:
https://api.openweathermap.org/data/2.5/forecast??id={id}&appid={API key}
According to the API docs, it should be built out as:
https://api.openweathermap.org/data/2.5/onecall?lat={lat}&lon={lon}&exclude={part}&appid={API key}


🐛 Remove requirement to specify CAPIProvider secret

What this PR does / why we need it:
This change improves the process of CAPIProvider creation. Users don’t need to specify spec.configSecret at all times, in order to get default set of enabled features, such as ClusterClasses or MachinePools, + provider specific features.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #787
Special notes for your reviewer:
Checklist:

[x] squashed commits into logical changes
[ ] includes documentation
[x] adds unit tests
[x] adds or updates e2e tests

Thanks @Danil-Grigorev. If using this "minimal" CAPIProvider yaml and, for example, wanting to enable Cluster Classes, is it not required to pass the CUSTER_TOPOLOGY environment variable to the provider?

@salasberryfin Yes, there is a test case for that also https://github.com/rancher/turtles/pull/788/files#diff-4f7dd9c7662f229992f65de2f22cd082cb79ba691af9062fed41ae5e472180c7R97


Instance groups from multi zone cluster

Please correct me if wrong, but the readme basically takes the first instance group from an existing cluster and configures the load balancer to use this as the backend in a backend service.
Note - I was following the example here as a basis to work from.
As is, will this module support multi zone clusters? i.e. a cluster that has say 3 instance groups. Given the output from the google_container_cluster is a list here, im not sure how I can go about iternating over that particular list within the backends segment of this load balancer. i.e.
  backends = {
    "0" = [
      {
        # Each node pool instance group should be added to the backend.
        group = "${var.backend}"
      },
    ]
  }

I could manually add numbers from the list, eg. if the output was called: TARGET_GROUP_URLS
I could do the following:
  backends = {
    "0" = [
      {
        # Each node pool instance group should be added to the backend.
        group = "${var.TARGET_GROUP_URLS[0]}"
        group = "${var.TARGET_GROUP_URLS[1]}"
        group = "${var.TARGET_GROUP_URLS[2]}"
      },
    ]
  }

However if my cluster may have many node pools, I may not know the end number of target groups. So the above would work but only if I know exactly the number of URLS to expect.
Is there any way to populate recursively using count based on the length of the the var?
Or am I missing something and I don't need to provide all the instance group urls specifically?

Any info on this one?

Hi @hawksight and @mkozjak. Thank you for your interest in the project! I apologize for the extreme delay in responding.
You can specify multiple backend objects for each index in the backends input, but each backend object can only specify one group. I think it should be possible to dynamically build the backends input using for expressions.

Thanks @aaron-lane - I've been using this module as the basis of my own for a long time.
Being able to loop through the backends so that the number of them is not longer hard coded is now possible for creation using a dynamic block.
Also to answer my own original question - yes this module will support multi zone clusters and cluster with multiple node pool. You just have to ensure you get the complete list of instance_groups in order to populate the group value of the backends input of this module.
The same limitation seems to apply that you will need to know up front how many instance_groups your going to have. In reality I find I do know as we are fairly static in the group respect. Your mileage may vary.
I just checked through this module's recent code for your 0.12 TF support where you use a dynamic block here similar to what I have in my own module
  dynamic "backend" {
    for_each = var.backend_group_list
    content {
      group = backend.value
      // adding null values otherwise reapplication fails
      balancing_mode               = null
      capacity_scaler              = null
      description                  = null
      max_connections              = null
      max_connections_per_instance = null
      max_rate                     = null
      max_rate_per_instance        = null
      max_utilization              = null
    }
  }

Where backend_group_list = data.google_container_cluster.information.instance_group_urls.
I set null here so that the default apply without having to know them.
Have you seen any problems updating load balancers after they are initially built? I find my code currently works to build, but tf apply on a plan once the backend_service resources are built comes back with errors. I've got an issue open here but wondered if you might have come across the errors I've seen when updating the module?

I am not familiar with the issue that you're describing but I have not worked extensively with this module. If you think there is work needed on the module after https://github.com/terraform-providers/terraform-provider-google/issues/3937 is addressed then please do open a new issue here.
I'm closing this issue since you've managed to answer your own question. :smile:


THINK/THOUGHT langchain refactor

The introduction of chains introduced several issues with THINK / THOUGHT messages:

usage is not reported in responses from langchain chains.
a chain can have multiple THINK/THOUGHT messages since there are multiple

Plan:

update IxCallbackManager to record THINK / THOUGHT for all LLM calls, including usage
likely need to update TaskLogMessage to have root and parent

root for querying message root message stream
parent to build message stream tree
IxCallbackManager needs to support building this tree

add a RUN_START/END message to be represent the bounds of a chain run.

Update messages reference parents accordingly
Update UI accordingly

This likely isn't relevant anymore since the model has changed some to account for nesting.  Streaming support likely should change in some way, but need to consider stream_log and intermediate action streaming as well.


Fix usage of plugin metadata annotations

Annotations for an extension/plugin should be defined in package.json at rancher.annotations object so that the annotations are correctly copied when generating a Helm chart and correctly used in the dashboard.
Fixes https://github.com/rancher/dashboard/issues/9501

Closed in favor of https://github.com/rancher/dashboard/pull/9544


request to remove "Show my Wallet Address" in Settings

Reassign to Chintan if you agree. The button is already there in Wallet tab, do you still need it there in "Settings"?

Yes. Because many users got used to it. The primary placement is in the Settings, then for convenience, you can also see this in the Wallet tab. There is a chance that someone misses the one in the wallet tab.


Improve UI by changing background image.

I would like to change the background image to a visually appealing picture.
Please assign me this under GSSOC'23.

I would like to work on this issue under GSSOC'23. I would appreciate if the issue is assigned to me.


Remove type of service in service host constructors

When I look at samples or tests, there is for example:
new SimpleInjectorServiceHost<GreetingService>(_container, typeof(GreetingService))

The second argument in the constructor ( typeof(GreetingService)) is redundant. It is givven by the generic type <GreetingService>. So it can be simplified to
new SimpleInjectorServiceHost<GreetingService>(_container)

I suggest to add new constructor for SimpleInjectorServiceHost which call the original construtor:
public SimpleInjectorServiceHost(Container container, params Uri[] baseAddresses)
	: this(container, typeof(TServiceType), baseAddresses)
{
}

Of course the same with NinjectServiceHost.
The original constructor can be marketd as [Obsolete].
Or the original one can be replaced, but this is incompatible change.

I have a memory that this parameter was needed for some reason. Try submitting a PR with the new ctor overload and leave the existing ctor in place for now. Thanks!

I'll do it after the PR #1 will be accepted, will I?

PR #3 is ready.

Thanks!

Resolved by OR #5.


ExponentialSubsecond strategy

Introduce a roko.ExponentialSubsecond to define exponential back-off more granular than one second.
Here's the existing roko.Exponential across 10 attempts, with 1, 2 and 3 second base — it only handles integer seconds, so there's no possible curves between these. Note that it always starts at 1 second for the first attempt — the adjustment input can change this, but doesn't influence the curve. The gentlest growth (base = 2 seconds) reaches a full minute in 5–6 attempts.

Here's the new existing roko.ExponentialSubsecond across 10 attempts, showing initial delays of 100ms, 1 second and 5 second base (but any number of milliseconds is supported).

Across 10 attempts, this:

grows from 100 milliseconds to 1 second
grows from 1 second to ~30 seconds
grows from 5 seconds to ~5 minutes

These seem like generally useful curves.
Here's the detailed examples from the tests & code comments:
//   100ms → 133ms → 177ms → 237ms → 316ms → 421ms → 562ms → 749ms → 1000ms
//   1.0s  → 1.5s  → 2.4s  → 3.7s  → 5.6s  → 8.7s  → 13.3s → 20.6s → 31.6s
//   5s    → 9s    → 14s   → 25s   → 42s   → 72s   → 120s  → 208s  → 354s

For a usage example, I'd like to use this in https://github.com/buildkite/agent/pull/2028 for artifact update retries, with an initial delay of 500ms, which would grow to ~10 seconds delay across 10 attempts, spending a total of ~70 seconds waiting between tries.

We might want to make the 16 configurable, but seems YAGNI

Yeah my main reluctance was:

it's hard to name,
it's hard to (nicely) make it an optional argument with a default value,
YAGNI, 16 is probably fine for everyone.

I'll wait to see if @moskyb has feedback before merging.


The connect does not work properly on FreeBSD

@hannesm got the issue on FreeBSD, it seems that the connect does not have the same semantic across platform. Indeed, Windows already has its own connect implementation. You should test it.

Fixed by c6e024a.


Flow thinks that a function is a map type as long as the function type is the same as the value type of the map

I would not think that this should type check, but it does, because flow sees () => 3 as the value of the $call property.
type Example = () => number
const x: { [key: string]: Example } = () => 3

https://flowtype.org/try/#0C4TwDgpgBAogHgQwLZgDbQLxQBQEooYB8UAdgK5IBGEATgFADGA9iQM7BRwBcUA3lAG0A1hBA92NAJYkA5gF0e8ZGmgBfAjnxEoAZjpA
This is a refinement of #2543

Let's just merge this into https://github.com/facebook/flow/issues/2966


Negative numbers work in filter for data viewer

For https://github.com/microsoft/vscode-jupyter/issues/6869

Seems like the functional test are no longer being used

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[x] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #7115 (36e05f3) into main (d3cf20b) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #7115   +/-   ##
=====================================
- Coverage     65%     64%   -1%
=====================================
  Files        363     363
  Lines      22917   22917
  Branches    3436    3436
=====================================
- Hits       14931   14894   -37
- Misses      6670    6715   +45
+ Partials    1316    1308    -8

Impacted Files
Coverage Δ

.../datascience/editor-integration/codeLensFactory.ts
53% <0%> (-10%)
:arrow_down:

src/client/terminals/codeExecution/helper.ts
13% <0%> (-6%)
:arrow_down:

...ient/datascience/raw-kernel/rawNotebookProvider.ts
70% <0%> (-3%)
:arrow_down:

...datascience/editor-integration/codelensprovider.ts
63% <0%> (-3%)
:arrow_down:

src/client/datascience/jupyter/jupyterNotebook.ts
50% <0%> (-2%)
:arrow_down:

...client/datascience/kernel-launcher/kernelDaemon.ts
53% <0%> (-2%)
:arrow_down:

...datascience/editor-integration/cellhashprovider.ts
69% <0%> (-1%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
67% <0%> (-1%)
:arrow_down:

src/client/datascience/baseJupyterSession.ts
64% <0%> (+<1%)
:arrow_up:

.../datascience/notebook/notebookControllerManager.ts
86% <0%> (+1%)
:arrow_up:

... and 1 more


The website's job section pages  are  displayed well when zooming in and out

Description  : When zoom in and zoom out the pages from the job section, all the content is displayed well.
Precondition :  the website is up and runing

Step 2 : Open one of the jobs.
Expected result :  The page with the details of the job is displayed.

Step 4 :  For each level of the zoom verify also Text Readability.
Expected results : Text should remain within its container and not require horizontal scrolling.

Step 5 : For each level of zoom verify also Images and Media.
Expected results :  images and graphics resize correctly without distortion or loss of quality.

Step 6:  For each level of zoom verify also Interactive Elements
Expected results : Buttons, links, and other interactive elements remain accessible and functional.

Step 7 : Repeat these steps for few jobs pages.
Expected results : Everything should be well displayed.


Document volume.kubernetes.io/gid annotation

Documentation for this feature: https://github.com/kubernetes/kubernetes/pull/20490

Hi,  I think the yaml file "volume.kubernetes.io/gid" should be "pv.beta.kubernetes.io/gid"

@pmorie @wongma7 Is this still accurate after https://github.com/kubernetes/kubernetes/pull/29119 and could you please assign someone to take it over.

@pmorie I created a new pr https://github.com/kubernetes/kubernetes.github.io/pull/938

Closing this since it was moved to  #938


C++ Program to find GCD of a number in a given Range  using segment Trees

Great work @actinium213 please give this repo a star if it really helped you to complete your PR.
Also follow me for follow back if you want to get connected with me for any such open source contribution program. Thank you 😊


Multi-Language support

Could we use something like this https://github.com/kurtsson/jekyll-multiple-languages-plugin ?
At least we can use {{ site.lang }} part to use in links

@captn3m0 ping?

Hard to do at the moment - unless we're translating all the text as well (which needs a lot more effort), plus not every combination in site.lang will be supported by links upstream - might result in broken links unless we're careful.

Happy to look at PRs that try to tackle this, but this is low priority for me, especially if the main usecase is improved links (which we work around by preferring canonical non-localized URLs).

could use a crowdin plugin automation to translate all needed text


Introduce new error code for cloud provider request throttling

/kind enhancement
This PR moves the cloud provider request rate limit exceeded error code handling from the ERR_INFRA_QUOTA_EXCEEDED error code (non-retyable) to a new error code ERR_INFRA_REQUEST_THROTTLING (retryable). So now all kind of rate limit errors will be automatically retried. This should fix issues like #3775 where the Shoot is marked as Failed right away (hence manual retry is needed) when a transient rate limit error occurs.
Fixes #3775
Release note:

Shoot operations that error due to cloud provider rate limit exceeded errors are now classified with the new `ERR_INFRA_REQUEST_THROTTLING` error code. Previously these errors were classified as `ERR_INFRA_QUOTA_EXCEEDED` and they were no longer retried. The new error code `ERR_INFRA_REQUEST_THROTTLING` is classified as retryable and such errors will be now automatically retried.

/invite @rfranzke @vpnachev @vlerenc

However, we should change the "retryable" part so that we allow the limits to recover in case they exceed.

I don't have a good implementation idea for now.
Even if we manage to tweak the retry mechanism in the shoot controller, I think that this won't influence the retry mechanism in the provider extensions for example. If I am not wrong , DefaultControllerRateLimiter is used currently by the provider extensions. So, if for example an Infrastructure fails to be deleted because of rate limits exceeded error, then the corresponding resource will be requeued and retried according to the DefaultControllerRateLimiter -> which more or less means to use the ItemExponentialFailureRateLimiter -> aggressive backoffs on rate limit errors. So even if we tweak the shoot controller, the provider extension can retry with aggressive backoffs and exhaust the cloud provider rate limits.

@ialidzhikov What about the approach of setting the shoot to Failed, but have a new controller in GCM which auto-retries shoots failed due to rate limits after some time? This is not relying on any internal workqueue, plays well together with the extensions, and is even resistent against controller restarts (with a new queue and backoffs).

@ialidzhikov What about the approach of setting the shoot to Failed, but have a new controller in GCM which auto-retries shoots failed due to rate limits after some time? This is not relying on any internal workqueue, plays well together with the extensions, and is even resistent against controller restarts (with a new queue and backoffs).

Thanks for your proposal.  new controller in GCM which auto-retries shoots [...] can do the trick of course, but I don't think it is a sustainable solution. It increases the coupling between gardenlet and gardener-controller-manager and the overall complexity.
So, if currently we have concerns about aggressive backoffs for the Infrastructure controllers that are likely to cause rate limit exceeded errors for accounts that host huge amount of Shoots, then probably we can try to adapt the RateLimiter for the infrastructure controller. https://github.com/kubernetes-sigs/controller-runtime/pull/731 makes possible to supply a custom RateLimiter. I think that the default DefaultControllerRateLimiter might be too aggressive especially for Infrastructure reconciliations. In most of the cases NewItemExponentialFailureRateLimiter(5*time.Millisecond, 1000*time.Second) will be the one that will give the higher backoff. Having in mind the exponential backoff definition baseDelay*2^<num-failures>, this RateLimiter will give the following backoffs for the first 8 failures:
1 - 10ms
2 - 20ms
3 - 40ms
4 - 80ms
5 - 160ms
6 - 320ms
7 - 640ms
8 - 1280ms
...

You can see that the first 7 backoffs are less than 1s which seems to be aggressive enough. The maxDelay of 1000s (16.67m) also seems aggressive enough.
If we tweak this for example with NewItemExponentialFailureRateLimiter(50*time.Millisecond, 2000*time.Second), we the following backoffs
1 - 100ms
2 - 200ms
3 - 400ms
4 - 800ms
5 - 1600ms
6 - 3200ms
7 - 6400ms
8 - 12800ms
...

and a maxDelay of 2000s (33.33m). Which is much less aggressive for an Infrastructure reconciliation -> less load on cloud provider APIs.
Also in the gardenlet ComponentConfig we have retryDuration that defaults to 12h. If the Shoot errors for 12h, then it will be set to Failed and no longer retried.
On the other hand we have the shoot controller that "requests" infrastructure reconciliations with the gardener.cloud/operation=reconcile annotation and I guess this ignores any kind of backoff in the infrastructure controller. So the custom RateLimiter would only help for having less aggressive backoffs on Infrastructure deletion? We would also need to tweak the Shoot controller RateLimiter to be less aggressive?

I now added<PHONE_NUMBER>be880d854b450b60022cc4ef269349 . It adapts the shoot, infrastructure and worker controllers to use RequeueAfter with a constant backoff when there is a rate limit error.
I didn't took the approach with new controller in GCM which auto-retries shoots [...] because even today we have the issue that hibernation with schedule and maintenance activities do not happen if the gardener-controller-manager is down - see https://github.com/gardener/gardener/issues/1278 for more details. So I still don't think that it is a good approach to take Shoot reconciliation decisions outside of gardenlet.

I wonder if the extension controllers (infra, worker) should rather exit w/o re-enqueuing and we leave it up to the Gardenlet to reconcile the shoot after a while (like here 10 Mins). Then the Infrastructure or Worker resource will be reconciled automatically, right?

Hm, what about the retries in the deletion flow? As far as I see currently gardenlet only deletes the Infrastructure/Worker and waits until the resource is removed from the store. I think in this case we cannot leave it up to gardenlet and in the deletion flow we rather rely on the backoff in the extension controller.

I wonder if the extension controllers (infra, worker) should rather exit w/o re-enqueuing and we leave it up to the Gardenlet to reconcile the shoot after a while (like here 10 Mins). Then the Infrastructure or Worker resource will be reconciled automatically, right?

Hm, what about the retries in the deletion flow? As far as I see currently gardenlet only deletes the Infrastructure/Worker and waits until the resource is removed from the store. I think in this case we cannot leave it up to gardenlet and in the deletion flow we rather rely on the backoff in the extension controller.

I see, you're right. The only point I see here is, that we probably reconcile Infrastructure or Worker twice.
My theory:

Gardenlet triggers Infrastructure reconciliation in reconcile flow
Extension controller reconciles Infrastructure and hits rate limit error -> enqueue after 10 min
Gardenlet exists flow and enqueues shoot after 10 min
Extension controller reconciles Infrastructure after enqueuing from (2.)
Gardenlet starts shoot flow after enqueuing from (3.)
Gradenlet triggers another reconciliation for Infrastructure
Extension controller reconciles Infrastructure again

I see, you're right. The only point I see here is, that we probably reconcile Infrastructure or Worker twice.
My theory:

Gardenlet triggers Infrastructure reconciliation in reconcile flow
Extension controller reconciles Infrastructure and hits rate limit error -> enqueue after 10 min
Gardenlet exists flow and enqueues shoot after 10 min
Extension controller reconciles Infrastructure after enqueuing from (2.)
Gardenlet starts shoot flow after enqueuing from (3.)
Gradenlet triggers another reconciliation for Infrastructure
Extension controller reconciles Infrastructure again

You are right. I can reproduce this. I was assuming that requeues that occur while an item is being processing are ignored but it is not the case. :(

We had a discussion with @rfranzke and @timuthy on this topic. We decided to proceed with the new controller in GCM which auto-retries shoots failed due to rate limits after some time approach. This approach has the advantage that the Shoot will be in Failed state until upcoming retry, hence according to the extensibility contract the extension controllers won't retry the failed operation in the meantime. It should be also resilient to Pod restarts to make sure that we don't retry abnormally when GCM/gardenlet is in CrashLoopBackOff.
I will rework the change and probably open new PR (as this one is already long one to follow).


csharp: The C# API should allow more asynchronous operations

What feature or improvement would you like to see?
The C# API should allow more asynchronous operations. Currently, it only supports ExecuteQueryAsync and ExecuteUpdateAsync.

More broadly, there should also be a clear theory of sync/async including preferences for which to implement in the "pure C#" case and how. (The import/export case is going to be governed by the limitations of the C API.)


Cache-Control: no-cache

Changes:

Sets Cache-Control header to no-cache for all static assets served by our fileserver
Changes the permanent redirects to temporary ones to disable browser caching

Both changes seek to address weird browser caching behaviour that @vividviolet and I observed during testing.

Looks good but can we update the tests?
https://github.com/Shopify/shopify-cli-extensions/blob/477e86a20f02638b48e0ec3b04b49c912b114d94/api/api_test.go#L226
I wonder why they are not failing 🤔

I had missed the crucial one. Tests are updated now and all redirects are now temporary.


⚠ Bofrost.fr has degraded performance

In 0a01cde, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1154 ms

Resolved: Bofrost.fr performance has improved in 982c1d2 after 304 days, 7 hours, 37 minutes.


Port .travis.yml to GitHub Actions

No build was triggered, because YAML was invalid, and GitHub didn't tell anything.


Configure the server URL for local use with an environment variable

Allow to configure the server URL for local use with an environment variable
TODO: Update the wiki when merged
Self-proofreading checklist

[X] Did I use eslint and black formatters
[X] Is my code clear enough and well documented

Changes
The current configuration for local use requires the user to modify several files.
Also, it is not foolproof as new media won't be served correctly (like the form attachments).
This solution will allow to easily configure the local environment, without modifying code, and, therefore, without the risk of committing local configuration.
How to test
Launch ngrok, copy the URL, and add it into your .env file like so:
SERVER_URL=<copied URL>

Launch docker and go to the form API, the URLs should be absolute instead of relative.

FYI, this is the currently documented way of setting up Iaso for mobile use: https://github.com/BLSQ/iaso/wiki/Development-environment#1---setup-ngrok

1 - Setup Ngrok
Download and setup Ngrok on https://ngrok.com/. Once Ngrok installed and running you must add your ngrok server url in settings.py by adding the following line :

FILE_SERVER_URL = os.environ.get("FILE_SERVER_URL", "YOUR_NGROK_SERVER_URL")

After this step you have to import settings.py and add FILE_SERVER_URL to forms.py in iaso/models/forms as shown on the following lines :

"file": settings.FILE_SERVER_URL + self.file.url,
"xls_file": settings.FILE_SERVER_URL + self.xls_file.url if self.xls_file else None


feat: Create players query

Resolve #7, #9

@Airaken I added a bit more structure to this Pr. please take a look at it.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DOC: Simplify ImageJ initialization

@ctrueden please take a look.

Thanks @thewtex. Code looks right to me. As long as the notebook still runs, then :+1: to merge.


missing field errors displayed original field name instead of renamed

closes #63

travis-failure is due to rustc-serialize failing

Thanks!


Add bug solution/fix to bug discussion page

Hey,
I think it would be good to include how your CIFAR-10 convergence problem was solved. At the moment the discussion page just includes problem details.
Good to hear you got it working.

Hi @thundergolfer - I've added some more details everywhere, let me know if you're interested in anything else.
-Brandon.

 If you are interested in using the DenseNet code in this repository, make sure your PyTorch version contains this patch and was downloaded after 2017-02-10.
There is no link in the text.

@TontonTremblay - did you expect a link for this patch? I meant to refer to the PR that I linked in the sentence before, but for clarity I just added a link around this patch too.


Port GitHub Pages's Git Root Reset Functionalities

Description
Since I already got the GitHub Pages CI recipes at hand, I should port it in for seamless execution.
Expected Behavior
Publishing to GitHub Pages is seamless.
Current Behavior
Publishing to GitHub Pages requires manual work.
Associated Data Files
No response

Completed.


skpm publish returns error

Hi there,
I've been trying to publish my plugin, but every time I run skpm publish 1.0.0 it returns the following error:
Error: Command failed: npm version 1.0.0 -m "Publish %s release :rocket:" --allow-same-version
npm ERR! code 1
npm ERR! Command failed: git commit -m Publish 1.0.0 release :rocket:

I've removed every release and tag from my repo and also removed any pull request from the plugin directory, but it still returns this error. I just want to publish v1.0.0.
Any clues why this might be happening?
Thanks in advance!

Hi, I had the same problem and I solved by publishing the package into npm first: https://docs.npmjs.com/updating-your-published-package-version-number


travis: test more go versions

tip is failing https://travis-ci.org/vbatts/tar-split/jobs/210745272
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

Oh good to know. I had assumed the short version would just do that.
On Mon, Mar 13, 2017, 20:11 Tianon Gravi<EMAIL_ADDRESS>wrote:

@tianon commented on this pull request.
In .travis.yml
https://github.com/vbatts/tar-split/pull/38#discussion_r105802391:

@@ -1,8 +1,10 @@
language: go
go:

tip

1.6.2

1.5.4

1.8

1.7

1.6

1.5

If you add .x to the end of these, Travis will resolve that to the latest
minor release of each version (ie, 1.8.x will be just 1.8, but 1.7.x will
be 1.7.5)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vbatts/tar-split/pull/38#pullrequestreview-26698765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEF6ZPr2QGxLCaJ5rFWoyWxHskdIiSAks5rldsrgaJpZM4Mb52b
.

it's a monotonic time. Work around, like so :point_right:  https://github.com/golang/go/commit/0e3355903d2ebcf5ee9e76096f51ac9a116a9dbb

fixed it


[E2E] Fix cleanup of kind cluster when standalone-cluster or management-cluster delete fails

What this PR does / why we need it
Fixes cleanup of kind cluster when standalone-cluster or management-cluster delete fails. Also removes unnecessary cleanup of kind cluster
Details for the Release Notes (PLEASE PROVIDE)
NONE

Which issue(s) this PR fixes
Fixes: #2533
Describe testing done for PR
--
Special notes for your reviewer
--

This PR might have some conflicts once #2510 has been merged


Adds autofocus to the quick add modal

Just started using Todoist today and immediately wanted to install it on every device I own  :smile:
I came across a weird focus handling bug when using the quick add global key event.
Instead of focusing on the text input, it went directly to the schedule section.

I'm using Ubuntu 18.04 so I don't know if this is a problem on other distros too but it seems like #53 should be fixed too. (I couldn't reproduce the behavior)

Awesome change! Thanks a lot @Jrprogrammer
I also copied the listener to beta.html (recently added by @ceiphr) and merged this PR manually.
Thanks again