CRI: remove deprecated config properties (auths, configs, mirrors)

Remove the following config properties in /etc/containerd/config.toml:

Property Group
Property
Deprecation release
Target release for removal
Recommendation

[plugins."io.containerd.grpc.v1.cri".registry]
auths
containerd v1.3
containerd v2.0 ✅
Use ImagePullSecrets. See also #8228.

[plugins."io.containerd.grpc.v1.cri".registry]
configs
containerd v1.5
containerd v2.0 ✅
Use config_path

[plugins."io.containerd.grpc.v1.cri".registry]
mirrors
containerd v1.5
containerd v2.0 ✅
Use config_path

The toml properties are still kept for printing human-readable errors, but the properties will be completely removed in v2.1.
Depends on:

[ ] https://github.com/kubernetes/test-infra/issues/31851
[x] https://github.com/containerd/containerd/pull/9778

cc @thockin @dims

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/containerd_containerd/9766/pull-containerd-node-e2e/1754745360544174080
{ failed [FAILED] Unexpected error:
    <*fmt.wrapError | 0xc0000bd900>:
    validate service connection: validate CRI v1 runtime API for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /run/containerd/containerd.sock: connect: no such file or directory"
    {
        msg: "validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial unix /run/containerd/containerd.sock: connect: no such file or directory\"",
        err: <*fmt.wrapError | 0xc0000bd8e0>{
            msg: "validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial unix /run/containerd/containerd.sock: connect: no such file or directory\"",
            err: <*status.Error | 0xc0009d58f0>{
                s: {
                    s: {
                        state: {
                            NoUnkeyedLiterals: {},
                            DoNotCompare: [],
                            DoNotCopy: [],
                            atomicMessageInfo: nil,
                        },
                        sizeCache: 0,
                        unknownFields: nil,
                        Code: 14,
                        Message: "connection error: desc = \"transport: Error while dialing: dial unix /run/containerd/containerd.sock: connect: no such file or directory\"",
                        Details: nil,
                    },
                },
            },
        },
    }
occurred
In [SynchronizedBeforeSuite] at: k8s.io/kubernetes/test/e2e_node/e2e_node_suite_test.go:235 @ 02/06/24 06:17:10.719
}

https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/containerd_containerd/9766/pull-containerd-node-e2e/1754745360544174080/artifacts/tmp-node-e2e-f8fc27d0-cos-beta-109-17800-66-81-system.log
Feb 06 06:17:06 tmp-node-e2e-f8fc27d0-cos-beta-109-17800-66-81 containerd[3207]: containerd: load required plugin io.containerd.grpc.v1.cri: unable to load CRI image service plugin dependency: invalid cri image config: `mirrors` is no longer supported since containerd v2.0, please use `config_path` instead

We'll need the prowjob to be updated to remove its use of mirrors.

I guess we should postpone this to v2.1

Can some one give me a example for correct config file about the "config_path" property ?


anchors for debug do not line up

The anchors defined in the ini files of demo/resources/debug don't line up in some cases. edit and make per-frame perfect

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22574909-anchors-for-debug-do-not-line-up?utm_campaign=plugin&utm_content=tracker%2F7646105&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F7646105&utm_medium=issues&utm_source=github).

Fixed in latest merge to develop branch.
https://github.com/hypatia-engine/hypatia/commit/0d1c4f8e85581295499842968ee0ecb548ec92af


feat(ops): support np.argpartition

Adds support for the numpy.argpartition operation.

Note
This is still a work in progress as the TF implementation is failing unit tests.
Any feedback on how to adjust the PR is appreciated! 🙏

Codecov Report
Attention: Patch coverage is 44.23077% with 29 lines in your changes are missing coverage. Please review.

Project coverage is 54.75%. Comparing base (99fdbf7) to head (d4c4963).

Files
Patch %
Lines

keras/src/backend/tensorflow/numpy.py
6.25%
15 Missing :warning:

keras/src/backend/torch/numpy.py
7.69%
12 Missing :warning:

keras/src/backend/jax/numpy.py
50.00%
1 Missing :warning:

keras/src/ops/numpy.py
94.73%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19588       +/-   ##
===========================================
- Coverage   76.47%   54.75%   -21.72%
===========================================
  Files         496      496
  Lines       44828    44880       +52
  Branches     8330     8336        +6
===========================================
- Hits        34280    24572     -9708
- Misses       8806    18710     +9904
+ Partials     1742     1598      -144

Flag
Coverage Δ

keras
54.75% <44.23%> (-21.58%)
:arrow_down:

keras-jax
?

keras-numpy
54.75% <44.23%> (-0.02%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

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

@fchollet
Thanks for the feedback! I'm working to fix the TF implementation.
Hopefully, this will be ready in the following days.

@fchollet
Changed the approach a bit for TF, tests are green.
Please let me know if further changes are needed 💪

Torch tests seem to fail on GPU with device placement issues: https://btx.cloud.google.com/invocations/43f688ba-e1b0-4100-8725-1b7756581e52/targets/keras%2Fgithub%2Fubuntu%2Fgpu%2Ftorch%2Fcontinuous/log

I think in the line out = torch.cat([bottom_ind, top_ind], dim=x.dim() - 1) we have one input on CPU and one on GPU. we should figure out why that happens and fix it.

I fixed it. The issue was the use of torch.ones (which does not have automated device placement) instead of ops.ones (which does).

@fchollet
Thanks for the fix and the explanation! 👍
Is there a public link for contributors to check on these post-merge builds? 🤔


Correction on fixing CDK cluster destroyed issue when the perf-test job is aborted

Description
After the testing from the previous fix, we found the CDK cluster was still not destroyed due to assuming role issue; hence, we want to update the role to fix it.
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/2504
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #3438 (4f02e74) into main (ac0cfcf) will decrease coverage by 0.29%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #3438      +/-   ##
==========================================
- Coverage   91.74%   91.46%   -0.29%
==========================================
  Files         172      172
  Lines        4991     4991
==========================================
- Hits         4579     4565      -14
- Misses        412      426      +14

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


added a comment about adding listeners in constructor

Thanks but refused - this concerns mrdoob's Stat class and this should be fixed in the original library.


ENH: Improve typing of some general functions

[X] Tests added: Please use assert_type() to assert the type of any return value

@Dr-Irv it is green now.


'Icon' was called on null

════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following NoSuchMethodError was thrown building CurvedDrawer(dirty, dependencies: [Directionality, MediaQuery], state: _CurvedDrawerState#8b6a1(ticker inactive)):
The getter 'icon' was called on null.
Receiver: null
Tried calling: icon
The relevant error-causing widget was:
CurvedDrawer file:///D:/workspace/flutter/projects/kf_drawer/lib/main.dart:75:18
When the exception was thrown, this was the stack:
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:53:5)
#1      _CurvedDrawerState.build. (package:curved_drawer/curved_drawer.dart:180:34)
#2      MappedListIterable.elementAt (dart:_internal/iterable.dart:417:29)
#3      ListIterable.toList (dart:_internal/iterable.dart:221:19)
#4      _CurvedDrawerState.build (package:curved_drawer/curved_drawer.dart:182:22)

i had the same question,and  had emil writer

by the way have you resolved this ?

I have not, been working on other items. I'll address when when I get a chance.
Sent from my iPhone
On Mar 27, 2020, at 10:40 AM, suo801<EMAIL_ADDRESS>wrote:

by the way have you resolved this ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/undrbridge/curved_drawer/issues/1#issuecomment-605068120, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOM2REGX3NE4KGLH3CB7MWTRJTCFHANCNFSM4KVHVSLA.

Thank you. I will keep an eye on the results. And I'm working on it myself

wow,i just resolved.i made it! 我去掉了列表赋值
//    _items = widget.items.map((item) {
//      DrawerNavItem(
//        icon: item.icon,
//        label: item.label,
//        color: widget.labelColor,
//        background: widget.buttonBackgroundColor,
//        size: widget.width / 3,
//      );
//    }).toList();
下面直接用widget.items，而不用_items，因为这里循环赋值有问题。

Hi there , it's not work @suo801 , do you have another solve for it ?

In curved_drawer.dart,
List<DrawerNavItem> _items = [];
replace to map by :
widget.items.forEach((item) {
      _items.add(DrawerNavItem(
        icon: item.icon,
        label: item.label,
        color: widget.labelColor,
        background: widget.buttonBackgroundColor,
        size: widget.width / 3,
      ));
    });

Thank you vilain-corentin, i had the same issue and this resolved my issue

It isn't working. Is there any other way to solve this?

first  - in file "curved_drawer.dart" line №65 init _items like this -  List _items = new List();
second - from line 70 to 78 delete this code
_items = widget.items.map((item) {
DrawerNavItem(
icon: item.icon,
label: item.label,
color: widget.labelColor,
background: widget.buttonBackgroundColor,
size: widget.width / 3,
);
}).toList();
3 replece like this:
for(var item in widget.items){
final navItem = new DrawerNavItem(
icon: item.icon,
label: item.label,
color: widget.labelColor,
background: widget.buttonBackgroundColor,
size: widget.width / 3,
);
_items.add(navItem);
}
for me it works

It isn't working, is there another way to solve this?

None of them are working :(

In curved_drawer.dart,
List<DrawerNavItem> _items = [];
replace to map by :
widget.items.forEach((item) {
      _items.add(DrawerNavItem(
        icon: item.icon,
        label: item.label,
        color: widget.labelColor,
        background: widget.buttonBackgroundColor,
        size: widget.width / 3,
      ));
    });

Not Working

#5 Put a return statement or replace it with arrow function

Anyone find the solution? :/

Please write the whole updated code.

In curved_drawer.dart,
List<DrawerNavItem> _items = [];
replace to map by :
widget.items.forEach((item) {
      _items.add(DrawerNavItem(
        icon: item.icon,
        label: item.label,
        color: widget.labelColor,
        background: widget.buttonBackgroundColor,
        size: widget.width / 3,
      ));
    });

Please write the whole code

just change code in the line just like this photo that will resolve problem
https://ibb.co/h20k2cc

Use custom code
https://github.com/Riya28042000/curved_drawer/blob/master/pubspec.yaml

This flutter dependency is  showing error.
Use the Custom Curve Drawer in Flutter
Git hub Link :- https://github.com/Vishesht/Curved-Drawer-Flutter

+1

Fixed with simple solution is that
Code:
 _items = widget.items.map((item) {
      DrawerNavItem(
        icon: item.icon,
        label: item.label,
        color: widget.labelColor,
        background: widget.buttonBackgroundColor,
        size: widget.width / 3,
      );
    }).toList();

Replace with 👍
Add return statement
_items = widget.items.map((item) {
      return DrawerNavItem(
        icon: item.icon,
        label: item.label,
        color: widget.labelColor,
        background: widget.buttonBackgroundColor,
        size: widget.width / 3,
      );
    }).toList();


Configurable batching

This adds support for the configurable batching behaivor in #133. It deprecates Cmd.batch and Cmd.sequence in favor of Cmd.list. List takes an array of cmds and an options object. It still needs updates (tests, docs, typescript typings), but I think the code should be good to go and ready to be looked at.
There are 2 options for list: batch and sequence (yes the old cmd names. I think they make the most sense). The sequence option decides between parallel vs series (like Cmd.batch vs Cmd.sequence), and is off by default. The batch option decides whether to dispatch the actions as they are ready or all at once at the end (the current behavior for both). It will be disabled (no batching) by default, which means the default Cmd.list has slightly different behavior than batch/sequence.
Cmd.batch(arr) === Cmd.list(arr, {batch: true})
Cmd.sequence(arr) === Cmd.list(arr, {sequence: true, batch: true})

Other names that were considered were for

Cmd.list: Cmd.group, Cmd.array
batch: group/groupCmds
sequence: series

I'm going to add README changes and typings changes and tests still, just wanted to get this initial implementation out there.
This change can be released as part of 4.x and then in 5.0 we can do the breaking portions of the change, which include removing Cmd.batch and Cmd.sequence and changing the default behavior of combineReducers to not batch child cmds.

The implementation looks good.
Left a few very minor comments.

@farism i made some implementation changes since you looked. mostly focused around keeping the behavior that the dispatch method returns a promise that waits for all resulting actions to complete. Now that still works because executePromise resolves with an empty array, but not until the nested actions are all dispatched and processed.

This PR seems like an attempt to simplify the API by combining two similar commands under one, and using options to disable current behavior. I like the concept of using an options parameter instead of a long series of individual params, some of which maybe optional. But when I see lots of options, some of which are not needed in all cases, that comes off as a code smell indicating a method is doing too many things and needs to be broken up into multiple specific sub methods. We're not at the point where you have tons of options, but they're being used here for divergent needs.
I like the existing names for these actions, they are explicit and fairly intuitive in their purpose. I'm also a fan of a stable api, where core methods do not get renamed or repurposed often or at all.
My suggestion would be to keep Cmd.Batch and Cmd.Sequence as is, and add an options param to toggle the existing batching of when actions are dispatched. This would be a breaking change if the default is batch=false which would give you the performance benefit of early dispatches.
If you still want to rename Cmd.Batch to something else, what about Cmd.Parallel or Cmd.Independant.

What does everyone else think about @jarekb84 's comment? @ashishsc @farism @willisplummer ?I'll try to summarize the reasons I merged batch and sequence.

Whether a list of cmds is run in series or in parallel, the concept of running a bunch of Cmds is basically the same. They may completely different implementations under the hood, but from the user's perspective they are very similar. I worry about adding too many methods to the top level API because I think it could confuse newcomers more about which they should use. Run, map, action and none are all very clear and distinct about how they are different, and list (or whatever we call it) would fit in with that group well. Adding 2 very similar methods to the top level API though would make it more confusing IMO.
In most scenarios, I see parallel unbatched groups (aka Cmd.list with no options) being the right choice to run a group of Cmds. Occasionally, you may want to run them in series, and occasionally, you want to batch the results and send them at the end, but those should be an exceptional choice choice and not worth adding a whole new top level Cmd for. Having both in the top level API makes the seem equally normal choices when they are not.
The old Cmds both have batching enabled, but I'd like the new default to be batching disabled (and parallel not series). It's harder to change the default behavior if we don't deprecate the old methods because we can't warn in the previous major version of deprecation and force them to address the new behavior.

I think that @jarekb84 brings up a good point, but I believe that breaking changes are going to happen, and as long as we stick to semver, proper docs, and a deprecation cycle, it's not a huge deal. We could even backport the configurable batching for sequence and batch and default to true to give current 3.0 and 4.0 api consumers the feature.
But I mostly agree with @bdwain on all three points, and particularly the first one. Running a list of commands is a single concept, and the way and order they are resolved feels like a piece of configuration.
Deprecating the old API isn't just about simplifying it but also about training users on the generic concept.

I think this is a fine change. Breaking changes will happen as @farism change. I personally prefer to have separate names for the functions rather than have an option object, but I agree that from a user's perspective it doesn't matter until they need to dig deeper

Cool. Thanks for the feedback everyone. I think I'm going to go with the single list Cmd like originally planned. It's a little more verbose if you don't want to un the Cmds in parallel, but I think that's a good thing because it'll encourage people to use the parallel non-batched version by default, . Almost all of the the time, you should be able to use Cmd.list with no options.


Change localize field to be readonly.

Just a simple code improvement. It's better to have thing as readonly if possible.

This is my favourite PR on the station 👍


Problem about uv_async_t coalesces calls

Version: 1.13
Platform: Darwin zanarpro 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64 i386 MacBookPro11,3 Darwin

I saw a hint in the document:

Warning libuv will coalesce calls to uv_async_send(), that is, not every call to it will yield an execution of the callback. For example: if uv_async_send() is called 5 times in a row before the callback is called, the callback will only be called once. If uv_async_send() is called again after the callback was called, it will be called again.

How about uv_async_send() two different handles? Will this function swallow one of the callback function?
eg:
uv_async_send(async_1);
uv_async_send(async_2);

One of the problem is Node.js cares_wrap.cc (https://github.com/nodejs/node/blob/v8.3.0/src/cares_wrap.cc#L681):
dns.resolve4(..., function() {});
dns.resolve4(..., function() {});

Refs: https://github.com/nodejs/node/pull/13050

No, each async handle will get its callback called in that case.

Thanks.


changed teams page so that there the teams are now in collapsable but…

…tons

Hi @iRTerence ! I am not sure if it is appearing correctly on my browser, For me, they are hidden when I view the page, and then when I click the corresponding button, I see all of the members of that particular section. Is this how it should function at the moment?

Will be implementing changes

Hi @christianarab, let me know what you think of the newest changes


feat/api_update: update integration of low level api

Updated Low Level APIs integration to support latest launcher.

This change is

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)


fix: combo of settings file and arguments

Description
Please describe the change you have made.
Checklist:

[ ] Tests added/updated.
[ ] Documentation updated.
[ ] Changelog updated in CHANGELOG.md.
[ ] Version bumped. If triggering a new release is desired, bump the version number in pyproject.toml per semantic versioning.

👍 Fixing the bug Vegard reported here, right?
Can we also deal with what he mentioned in his next post? If I read the code correctly, we still would have to specify cogshop_version = "" (and not just omit it) if shop_as_a_service (?) I'll leave that up to you.

This is covered by these changes, you don't need to pass in the cogshop_version. You can either add the config in the TOML file, or as arguments to the client constructor (and the later take precedence)


Put URL in the Candidate Set

Add validation for presence of url, the contemporary pocket primary key of record, in candidates before sticking them in DynamoDB.
As of this PR metaflow will add url to the SQS Queue: https://github.com/Pocket/dl-metaflow-jobs/pull/84
This PR is to the lambda that gets the candidate sets off the SQS Queue and puts them into DynamoDB. Now they will have their urls in there.
Benefits

See aforementioned PR.

Risks

We need to check if there is some kind of row size limit in Dynamo DB, and if so how close we are to it, and if we're close, whether adding a url to each of our candidates puts us over that limit. My hope on this is 'no' but if the answer is 'yes' things get more complicated.

Here's a change to fix the failing test_lambda check: https://github.com/Pocket/recommendation-api/pull/642

This work has been dropped. If we want to circle back we can revisit.


Bounding box for points is wrong

🐛 Bug
Something's off with the bounding box calculation for points:

import napari
import numpy as np

img = np.random.rand(5, 4, 6)
pts = np.array([[0, 0, 0], [5, 5, 5]])

v = napari.Viewer(ndisplay=3)

il = v.add_image(img)
il.bounding_box.visible = True
pl = v.add_points(pts, size=1)
pl.bounding_box.visible = True

Likely a 0.5 offset issue.

It should be napari from the main branch. Bounding boxes are implemented but not released yet.

@brisvag : this is fixed on main for me now (maybe from https://github.com/napari/napari/pull/5751), so closing. Re-open if you find otherwise.


Dependented pods are prebuilt also?

I do not want dependented pods are  prebuilt. how can I do it.

my all  dependented pods are
how can i keep the original pod sources
dependented pods

You could set the binary flag for the dependency pods explicitly in the podfile


CLI docs for avn service sstableloader command

What should we add to our content collections?
Documenting the avn service sstableloader that Aiven provides for Cassandra services
Please fork the cli-avn-service branch, have a look at the integration page for an example
Is this something you would work on yourself?
[ ] I plan to open a pull request for this

Command purposes are described here: https://help.aiven.io/en/articles/3147884-using-sstableloader-to-migrate-your-existing-cassandra-cluster-to-aiven (for reference)


Zoom issues

Users are experiencing issues with the zooming feature. It resets the previously made changes.

No longer an issue


libclang can't find stddef.h

Usage as described in README.md is fine but more recent versions of clangd, as on my computer, fail with the following message during 'stepu':
["Lexical or Preprocessor Issue:'stddef.h' file not found"] Python Exception <class 'RuntimeError'> Failure during libclang parsing:  Error occurred in Python command: Failure during libclang parsing

That's when you use LD_LIBRARY_PATH to point to a fresh LLVM/clang build

This may be related to an issue described in the docs - basically, some built-in includes are located relative to the clang binary and have to be manually added to library-using code. Hard-coding this in getASTNode seems to work around the problem.


To redirect the canvas

When the user clicks the submit button the canvas should be drawn on the next page .

[ ] Make the main page more cleaner
[ ] The size of main canvas needs to be increased

Can I work on this issue?

Can I work on this issue?

sure you can

Hai, I have been trying to pass user input variables between webpages (the main page where we take user input & canvas page) via sessionStorage / localStorage. Is there any efficient method available for the above issue?

Hai, I have been trying to pass user input variables between webpages (the main page where we take user input & canvas page) via sessionStorage / localStorage. Is there any efficient method available for the above issue?

Hi Please join the Gitter chat , so that we can take certain suggestions from mentors as well and get this issue resolved asap


Test with the new reverted workflows

Explanation

To check
With the if !cancelled fix in this PR

[x] Skip Coverage comment - https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/pull/19#issuecomment-2305840499 ; with no kt file changes detected in the PR.
[ ] Pass Coverage case with min threshold -
[x] Pass Coverage case with test file exemption - https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/pull/19#issuecomment-2305670545
[ ] Pass Coverage case with source file incompatible exemption
[ ] Pass Coverage with override min threshold exemption
[x] Fail Coverage case with min threshold - https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/pull/19#issuecomment-2305868740
[x] Concurrency cancel - stack trace
[x] Combined report
[ ] auto merge with fail should not merge
[ ] auto merge with pass should merge
[ ] merge to base branch without any issues

Essential Checklist

[ ] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
[ ] Any changes to scripts/assets files have their rationale included in the PR explanation.
[ ] The PR follows the style guide.
[ ] The PR does not contain any unnecessary code changes from Android Studio (reference).
[ ] The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
[ ] The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included
Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

ok this works so only thing that will require a fix is with skip coverage status

Ah as expected

since there are no changes, the Run Coverage got skipped - skipping evaluate (no report being generated) - https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/actions/runs/10516147614/job/29137736271?pr=19
causing no report to fetch in the upload comment job - https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/actions/runs/10516147482/job/29137917461?pr=19

so to fix this

there needs to be a way to still generate the skip coverages
lets start with !cancelled conditional runs (that should still trigger on pass or fails but not sure about skips that's the most concerning part)

As expected it fails both the generate and coverage check status result: https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/actions/runs/10516492176/job/29139363674?pr=19, while still uploading the fail coverage report comment: https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/pull/19#issuecomment-2305868740

The concurrency did work -https://github.com/Rd4dev/Oppia-Android-Fork-from-Fork/pull/19/checks?check_run_id=29139637796

Enabling auto merge with min threshold fail status - it shouldn't merge!

Awesome so it failed to merge as it had failure check, so now will leave with passing case that should pass and merge it and run the set of merge base branch runs........

Last thing I wanted to see - 🤕

So the concurrent workflows in the develop cancel out each other. :|
Let me try doing the pr number reference and see if that could help.


fix(docs): add scheduler to custom provider example

Hey, I just made a Pull Request!
Fixes #25463
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

hey @freben if you take a look at my entity provider in issue #25404 it looks like the only thing called once the provider is installed is only the connect, or at least from all the logger I have that one was the only one appearing in the terminal.

@camilaibs I can take a look, does that same approach work for the old backend? This section of the docs still has both.

Yeah should be the same calls. The new backend system at the end of the day mainly deals with dependency injection; the actual services and stuff is mostly exactly the same

@freben This should be updated with the latter 2 of your recommendations!

TY so much for this ❤


chore: Typo in Parameter Object description

I believe this should say ...named location...

i also updated the casing of Runtime Expression in links.  There were a few upper and a few lowercase


New sample: NMEA Location Data Source

This sample demonstrates how to parse NMEA sentences and use the results to show device location on the map. The sample does not implement the non-compulsory option to retrieve real-time NMEA sentences either from a dongle or GPS
Sample Design link.

Thanks for the catch Soren! I have gone ahead and added those changes.


Add logos to new account screen

Added logos for each node/wallet option when setting up a new account
Screenshot:

I am open to any feedback and suggestions if anyone wants to change anything i've done here! :)

Cool, looks a lot better already.
Would say that the logo's of LNDHub & LNbits should be a bit more in balance with the other logo's (too big currently).
For the logo's I'd say we use SVG instead of .png?

👍 for SVGs also adding @johnsBeharry for a UI review

Ok I have made them all the same size and converted from PNG to SVG. I found an online converter tool to do this, however it looks like some of the colors changed a bit when doing that. If anyone knows a better way to convert the images just let me know. Please let me know what you guys think of this iteration:
Screenshot:

Here's another version where the LND logo has a blue background:

I would prefer the logo's to appear without a background.

converted from PNG to SVG.

do you know if these projects provide SVG version of the logo? those would have better quality and can easily be scaled then.

I'll look into finding the official SVGs for each project tonight. I agree that would be much better.

So far I haven't had any luck finding SVGs for all the projects. I found one in the lnbits repo but did not see one in LNDhub or LND. I asked in the LND Slack group if there was an SVG icon for developers but did not get a response. I tried contacting the BlueWallet guys over e-mail and did not hear back yet either.
So for now we can either use PNGs with the correct colors or use the SVGs with the slight color variations from converting them. Or just wait to merge this PR until we can track down the official SVGs.

So it looks like not every project has an official SVG logo. I have changed this PR back to using the PNGs for now. My vote would be to use those rather than convert the logos and cause some distortions.

Here's another option for everyone to consider, I changed to the Blue Wallet logo as suggested by @MoritzKa and I also removed the forced rounding and let each logo have its own shape.

This one probably looks the best IMO but if we can agree on feedback then maybe we can merge.
I know @dylancom would like ones without background but with my limited design skills I haven't been able to make PNGs without backgrounds while also making them all appear the same size. Because a 200x200 image with no background will look smaller than one with a background. So if anyone else wants to send me some of their own images I can use those and post screenshots.

I wonder how to create a logo without background out of the LNbits logo for instance. The latest update is a great improvement for the extension. Let's ask for feedback in the community call and decide.

We didn't bring up this PR in today's meeting but is there anything anyone else wants me to do for this one?

It is a great improvement.
What do you think, @johnsBeharry ?

Ok @johnsBeharry was nice enough to provide some uniform images that we have been looking for. So now they are all the same size and look good, here's what the updated version looks like:

He also gave an alternative option for the Alby logo:

Johns also gave us a yellow version which I personally like better but we can take a vote on it:

I would also choose the yellow background for the logo. But the extension design is not final anyway.
So let's go with the full body Alby logo (not just head) on a white background.

Here's what that version looks like:

I like it! @johnsBeharry can you review

Oh sorry I see everyone wants the white background, I just need Johns to put the white version back on dropbox and then I can make the final changes.

ok, we need to merge the conflict and then get decide and get this in!

so it is very likely that we get the Galoy connector in and we should directly plan that we will have an icon for it

OK I have merged the conflicts, yep we can for sure add a Galoy logo as well. Maybe johns has one that is formatted the same as the others? Also the current version of this PR is using the yellow, full-body Alby logo just so everyone knows, but it can be changed still.


Ui143 validate archive type

Partly fixes: https://github.com/epinio/ui/issues/143 (missing the front-end validation)

Codecov Report

Merging #1624 (225c850) into main (c8ad720) will decrease coverage by 54.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main   #1624       +/-   ##
==========================================
- Coverage   62.67%   8.59%   -54.08%
==========================================
  Files         167      83       -84
  Lines       12351    8140     -4211
==========================================
- Hits         7741     700     -7041
- Misses       3622    7394     +3772
+ Partials      988      46      -942

Flag
Coverage Δ

acceptance-api
?

acceptance-apps
?

acceptance-cli
?

unittests
8.59% <0.00%> (-0.04%)
:arrow_down:

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

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b96fd2e...225c850. Read the comment docs.

I checked it on branch and verified that now there is a warning on the upload step if the file is not supported:

@jimmykarily I understand here is where the front-end validation was placed and not earlier, right?

@mmartin24 this PR implements only the backend validation. The front-end one (which should come eariler) will happen on the UI repository.

thank you @jimmykarily, then I guess this ticket (https://github.com/epinio/ui/issues/143) should be closed once that earlier ui implementation is ready, unless you think is better to split it.


Please update the document to reflect that Shared service plan is/will not supported for azure function app.

In the function app service plan page: https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale#overview-of-plans, it says function app can be created in dedicated service plan.
but per testing, function app cannot be created in Shared service plan(a kind of dedicated service plan). it will throw error:
Function apps are not supported in Free or Shared App Service Plans.

Could you please update this document to reflect this change? Note that this change should be in progress region by region, so currently, a few regions don't have this error, but it might be failed in the future.

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

ID: 06436739-8586-23b1-6b69-1960e93c26be
Version Independent ID: 8f7abfae-cf6d-56cb-1d20-f02041a6f6d9
Content: Azure Functions scale and hosting
Content Source: articles/azure-functions/functions-scale.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@imeya
Thanks for your feedback! We will investigate and update as appropriate.

hello @YashikaTyagi-MSFT , @ggailey777 , any update on this issue? Thanks.

The supported App Service plans are documented here:  https://learn.microsoft.com/azure/azure-functions/dedicated-plan
Do you not consider this sufficient?

Hi @ggailey777 , thanks for the document. I think it's better to point it out that Shared / Free service plan is not supported here:


Add finalize option to quickpay at capture

Add the ability to finalize the transaction when doing a partial capture so the transaction doesn't remain open
http://doc.quickpay.dk/api/messagetypes.html#index6h2

Hi @askehansen,
I'm thinking a unit test verifying that we're passing the right value for each of the cases would be helpful for this pull request.  Many of the gateways have unit tests using CommStub to assert such things.
Thanks!

Im not quite sure what you mean?

Here's an example in the Stripe unit tests verifying that the right things get passed to the gateway:
https://github.com/Shopify/active_merchant/blob/f8998d6747a9d99fc727731d4f1c9e9690001a3e/test/unit/gateways/stripe_test.rb#L506-L512
Does that help explain?

Yea thanks, i'll do that

I just added some tests

Looks great @askehansen!  Just merged it.  Thanks!


typescript types not published

cosmiconfig: 5.2.1
ls node_modules/cosmiconfig/dist
cacheWrapper.js    getDirectory.js       index.js    readFile.js
createExplorer.js  getPropertyByPath.js  loaders.js

Types will be published with v6 once it is released. Until then, use @types/cosmiconfig


Feature request: Add annotation(s) into the legend

For we can create the chart with the legend and can show or hide it by selecting the legend.
Do we have any ways to add the annotation into the legend?

@HuongSakada my personal opinion, that's not possible because legend items are representing a dataset or data of dataset. In this case you would like to have a legend item to a chart element.
I guess (but correct me if I'm wrong), you want to have the possibility to show and hide the annotation on demand.
If you are using the last pre-release v1.0.0-beta.2, this is possible by display options and of course an external HTML "controller" which can enable or disable the display of the label.

@HuongSakada my personal opinion, that's not possible because legend items are representing a dataset or data of dataset. In this case you would like to have a legend item to a chart element.
I guess (but correct me if I'm wrong), you want to have the possibility to show and hide the annotation on demand.
If you are using the last pre-release v1.0.0-beta.2, this is possible by display options and of course an external HTML "controller" which can enable or disable the display of the label.

Yes, you are right. If we want to show the legend it must be added in datasets.
So I have a trick, add it as data in datasets of type: 'line' with data: []. I don't think a good solution but it can help.
{
    type: 'line',
    label: 'The legend label',
    backgroundColor: 'red'
}

Yes, you are right. If we want to show the legend it must be added in datasets.
So I have a trick, add it as data in datasets of type: 'line' with data: []. I don't think a good solution but it can help.
{
    type: 'line',
    label: 'The legend label',
    backgroundColor: 'red'
}


Added

Added name

Thanks @silpat, however I don't see what you were trying to do.
Please read the specs in the README, and feel free to create another PR


Visual Entity Navigator gives a TypeError when Load from Github! is clicked

Visual Entity Navigator gives a TypeError when "Load from Github!" button is clicked:
TypeError: NetworkError when attempting to fetch resource.
/core/applicationCommon/foundationCommon/crmCommon/solutions/portals/AdPlacement.cdm.json

Hi @emres - is it possible you have an ad blocker on in your browser? We've seen this previously, due to the name of the entity some ad blockers will prevent it from loading. Let me know if you disable the ad blocker and still have the issue.

Indeed! Just tried it with a browser that didn't have any ad blockers, and this time it worked like a charm! Could be good if you put this as an explanation somewhere close to the Visual Entity Navigator link.
Thanks for your quick and to-the-point support again!


Bump envoy version to 1.14.4

As per title. This bumps the image to Maistra's 2.0.0 image, which has envoy 1.14.4.
The regex configuration got dropped and replaced as shown.
/assign @jmprusi @davidor

/lgtm


WX: max_fps (and fix request_draw on Windows)

Closes #209, and also adopts (configurable) fps limiting.

LGTM


Remove version: 360.360SE version 13.1.5360.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://down.360safe.com/se/360se13.1.5360.0.exe
OK
(Automated message - build 923)

Close with reason: Package still available;


HTTPRequest.set_tls_options to TLSOptions.client_unsafe() isn't working anymore in Godot 4.3

Tested versions
reproducible in Godot 4.3
not reproducible in Godot 4.2.2
System information
Window 10
Issue description
HTTPRequest.set_tls_options( TLSOptions.client_unsafe() ) should disable TLS handshake validation.
But when calling a Server with a self signed certificate the error "E 0:00:02:0815   _do_handshake: TLS handshake error: -9984
<C++-Quelle>   modules/mbedtls/stream_peer_mbedtls.cpp:89 @ _do_handshake()" appears.
That wasn't so ingodot 4.2.2
Steps to reproduce
extends HTTPRequest

func _ready() -> void:
	var opts =  TLSOptions.client_unsafe()
	print("Unsafe:", opts.is_unsafe_client())
	set_tls_options( opts )
	request("https://URL_TO_UNSAFE_SERVER", [], HTTPClient.METHOD_POST, "")

Minimal reproduction project (MRP)
issue.zip

Fixed in https://github.com/godotengine/godot/pull/96172 , see https://github.com/godotengine/godot/issues/96170 for details.


Payload overwritting

Ensure the payload for an entity is never overwritten when parsing the response.
Added tests for this case.

Coverage decreased (-4.4%) to 95.361% when pulling df9f5a86e95a8b71f0730e26fb40d6928931d0bf on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage increased (+0.007%) to 99.751% when pulling 5b2666ff718a8034c6e29469f0ea9365742ec66c on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage increased (+0.007%) to 99.751% when pulling 5b2666ff718a8034c6e29469f0ea9365742ec66c on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage decreased (-4.4%) to 95.361% when pulling ecb14a946812cae84d67d0ba3fcd7b05932490da on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage increased (+0.007%) to 99.751% when pulling b954d11b19359d06de7046aa76e64df4df6ea8b0 on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage increased (+0.007%) to 99.751% when pulling 273357e771e30dcc4259d58a07c091dbffac76ef on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.

Coverage increased (+0.007%) to 99.751% when pulling ce19470e0fc933bd4e4667bbb2dfc6a1d99af87b on bugfix/payload-overwrite into dca78f9776d0f64f93081909b62a5c7ddb344681 on master.


Add Jinzhong's Post

Not sure why the test won't run on this pull request but going to force a merge anyway. Looks good to me!


Read permissions of entities within flex-model or flex-context

Currently, the API forbid users to use a storage power sensor that doesn't belong to them. Nonetheless, we are not checking that the entities within the flex-context and flex-model are readable by the user.
This fact could be used in a malicious way:
I think someone could exploit this fact to leak data, specially, inflexible device power. I would follow these steps:

Create a battery that is own by the "attacker" with an very large capacity with initial SOC = 100%
Set a site capacity constraint of 0 which forces the battery to supply the same energy to the inflexible device.
Set an efficiency to 1, constant price and prefer_charge_sooner = False
Add the target device as an inflexible device
Run a storage scheduler

This would make the battery track the power of the inflexible device and would get the data from any sensor.
Adapted from https://github.com/FlexMeasures/flexmeasures/pull/897#discussion_r1396033138
I suggest to create a utility function that checks if a user has the right access the data that is being used.

I recommend to use flexmeasures.auth.policy.check_access(), which is also the central call in @permission_required_for_context.
As to the best place to use this, maybe an extra decorator:
@permission_required_for_context("create-children", ctx_arg_name="sensor")
@check_read_permission_in_flex_model_and_context()
def trigger_schedule(

which checks if the args have a "flex-model" or "flex-context", and then checks_access for each sensor we know can be in there, for the current_user and the "read" permission.

tagging @GustaafL


[Backport 2.x] Bump Tika from 2.4.0 to 2.5.0 addressing CVE-2022-33879.

Description
Backport #4791 to 2.x.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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

Codecov Report

Merging #4794 (9239f20) into 2.x (a90fd73) will increase coverage by 0.04%.
The diff coverage is 62.30%.

@@             Coverage Diff              @@
##                2.x    #4794      +/-   ##
============================================
+ Coverage     70.62%   70.66%   +0.04%
- Complexity    57126    57463     +337
============================================
  Files          4585     4617      +32
  Lines        274526   276032    +1506
  Branches      40233    40387     +154
============================================
+ Hits         193876   195052    +1176
- Misses        64403    64718     +315
- Partials      16247    16262      +15

Impacted Files
Coverage Δ

...main/java/org/opensearch/gradle/PublishPlugin.java
43.43% <0.00%> (-0.45%)
:arrow_down:

...ava/org/opensearch/client/RestHighLevelClient.java
41.75% <0.00%> (-2.27%)
:arrow_down:

...apshots/restore/RestoreSnapshotRequestBuilder.java
15.78% <0.00%> (-0.88%)
:arrow_down:

...er/src/main/java/org/opensearch/client/Client.java
40.00% <ø> (ø)

.../org/opensearch/client/support/AbstractClient.java
34.50% <0.00%> (-0.20%)
:arrow_down:

...main/java/org/opensearch/common/lucene/Lucene.java
67.30% <ø> (+1.48%)
:arrow_up:

...rg/opensearch/common/settings/ClusterSettings.java
91.89% <ø> (ø)

.../java/org/opensearch/common/util/FeatureFlags.java
50.00% <ø> (ø)

...ateway/TransportNodesListGatewayStartedShards.java
51.00% <0.00%> (+13.42%)
:arrow_up:

...index/codec/PerFieldMappingPostingFormatCodec.java
64.28% <ø> (ø)

... and 597 more

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


README.md : Correct website url

Current demo url has a - attached that prevents it to open.

Thank you.


Fix with-strict-csp example

The with-strict-csp example uses dynamic nonces that need to be generated on every request.
Since automatic-static optimization this example was broken, because static rendering doesn't work with this strategy.
This PR explicitly opts into ssr.
close #11929

I think we should figure out a better solution for this as everything is becoming increasingly static.

We already have an example that uses hashes instead of nonces.
Thats why I fixed this one and didn't change it.

Let's replace this example then maybe 🤔

Solved in #13221

Would be nice to have a little section in the documentation. It's quite an important topic.

I've been trying to get this to work on my site and while adding the meta tag in _document.js does work, report-uri or Content-Security-Policy-Report-Only is not supported in the meta tag.
With CSP being a bit tricky to setup it would be nice to be able to test this in prod with just reporting turned on for a while to monitor the reports before going all in.
Is there a way to generate the hash for NextScripts in server.js and add as a header or is there a way to pass a nonce to static pages and use that instead?

@jamieholliday  for CSP is not supported cross-browser, and doesn't work in chrome. The only bulletproof way to set CSP is headers. https://caniuse.com/mdn-http_headers_csp_content-security-policy_meta-element-support
I'm having similar issue with Gatsby.js

@JustFly1984 as far as CSP not supported cross browser this looks pretty good for my use case as I dont need IE support https://caniuse.com/contentsecuritypolicy2 - however it looks like Next only supports the meta tag option for nonce (which I think I need becuase GTM) becuase of the static pages. As more stuff is getting static it seems it would be worth solving. I've tried using headers in next.config.js but looks like they are set only once and therefore wont give a unique value


Add a license

Hi, can you add a license to this tool? I would like to use it, but not sure if I can.
Thanks!

No problem! Just added the MIT license.


Backend - LinkedIn Login Integration

Will reference an example at https://github.com/denisbakhtin/oauth2-example/blob/master/linkedin/linkedin.go

Seems like we might not be able to get user's profile. As stated in https://docs.microsoft.com/en-us/linkedin/shared/references/v2/profile/lite-profile r_liteprofile permission only allow access to these 4 fields:

id
firstName
lastName
profilePicture

The change happened after they moved to v2 API https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/migration-faq?context=linkedin/consumer/context. Not a blocker, but kind of defeats the reason of choosing LinkedIn than other OAuth providers

Partial complete in #56, able to oauth redirect and retrieve first/last name, email. Just missing database persistence.
@kajalsinha will help to create the right code structure and implement data persistence

@ivanfoong @subhransu , I will start working on this one now.

marking this as closed as LinkedIn Login flow is working. I will create separate issues for profile/onboarding API.


[zh-cn] sync finalizers.md

Sync file:
content/zh-cn/docs/concepts/overview/working-with-objects/finalizers.md

/lgtm


Add passed style for the Table of Contents Links

Description
This PR adds a passed attribute to the links of the Table of Contents. This allows for further distinction of where exactly on the page you are.
Additionally, to prevent the links getting too dark, the "default" color has been changed from --sl-color-gray-3 to --sl-color-gray-2.
I've added this because I am porting a page from MkDocs (Material) to Starlight, and this was something that I missed with Starlight.
Before:

After:

Hello! Thank you for opening your first PR to Starlight! ✨
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any issues you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🤩

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Hi @jumpingpxl! Thanks for the PR — I appreciate your interest in contributing.
I’m not 100% confident that we want to make this change. It is a cool effect, but I think it actually makes it less clear what the currently highlighted item is at a quick glance because the contrast between the current item and the items below it is quite low with the items lower on the page arguably being more prominent than the current item:

For the future, it’s always better to first open a feature request discussion before creating a PR to chat through details of an idea and find out if there are other users who would appreciate a change. That also helps the team evaluate the need for work on something.


Error 400 on GSuite marketplace

Love gcalendarsync. Went to use add-on in sheets today and it was no longer present. Unable to find in Google Marketplace either. I wonder if something happened after your last push 2 days ago?
Error 400 on marketplace https://gsuite.google.com/marketplace/app/gcalendar_sync/831559814916
Just letting you know.
Thanks

I haven't actually changed anything in the add-on in a year. Some people were having issues, which seemed to be caused by needing to authorize the script again. I bumped the version number and re-deployed hoping that would fix the issue. But it didn't seem to update at first. I changed some Marketplace settings, and it seems I've re-triggered the Google review process. There are a dozen issues Google wants me to resolve and I just don't have the time to deal with it.
Sorry it's not working any more. Google is making the process of publishing add-ons too difficult to do as a hobby project.

Oh no this is so unfortunate. This was the only bare bones sync add-on I could find. Is it gone for good? Any way I can add it to my scripts myself script.google.com ?  Thanks for your work and time, I appreciated it for over a year multiple times a day.

I haven't actually changed anything in the add-on in a year. Some people were having issues, which seemed to be caused by needing to authorize the script again. I bumped the version number and re-deployed hoping that would fix the issue. But it didn't seem to update at first. I changed some Marketplace settings, and it seems I've re-triggered the Google review process. There are a dozen issues Google wants me to resolve and I just don't have the time to deal with it.
Sorry it's not working any more. Google is making the process of publishing add-ons too difficult to do as a hobby project.

Hey Dave - your add-on is amazing and my team has come to rely on it for our scheduling workflow - would it be possible for you to post the source code for the new version (allowing multiple sheets/calendar syncing) to github so I could save it as a dedicated script on our scheduling document? Please let me know - thanks so much.

OH NO!  I have almost 50 employees using this tool and they've loved it - such a great tool.  Is there a chance the requirements will be taken care of so that it can get republished?

Seriously, oh no! How can we get this back up and running?! Dave have you thought about starting a Patreon? We will buy you coffee and sandwiches forever to use this amazing tool.

Joining the "oh no" here!
If anyone found a solution for this incredible add-on that does not work anymore- please share it with the world!
Dave, your add-on is really helpful! hope you could upload it once again for us

Since there is no confirmation that Dave will continue to develop, and I have not found a single fork that has progressed on its own.
Maybe you could use the old version.
https://github.com/Davepar/gcalendarsync/tree/master/priorversion
It is done differently and has gcalendarsync.js that you can insert into the Script Editor.
The folder also contains instructions on how to do this.
It’s not as good as the last one but if you don’t have anything at the moment you can try it. And it's easier to make minor changes if you're not used to Clasp.
This may help until you find another suitable add-on.

Since there is no confirmation that Dave will continue to develop, and I have not found a single fork that has progressed on its own.
Maybe you could use the old version.
https://github.com/Davepar/gcalendarsync/tree/master/priorversion
It is done differently and has gcalendarsync.js that you can insert into the Script Editor.
The folder also contains instructions on how to do this.
It’s not as good as the last one but if you don’t have anything at the moment you can try it. And it's easier to make minor changes if you're not used to Clasp.
This may help until you find another suitable add-on.

I tried using the old version but i get the error "TypeError: Cannot read property 'getEvents' of null" right away and what to do with her - I don't know

Since there is no confirmation that Dave will continue to develop, and I have not found a single fork that has progressed on its own.
Maybe you could use the old version.
https://github.com/Davepar/gcalendarsync/tree/master/priorversion
It is done differently and has gcalendarsync.js that you can insert into the Script Editor.
The folder also contains instructions on how to do this.
It’s not as good as the last one but if you don’t have anything at the moment you can try it. And it's easier to make minor changes if you're not used to Clasp.
This may help until you find another suitable add-on.

I tried using the old version but i get the error "TypeError: Cannot read property 'getEvents' of null" right away and what to do with her - I don't know

I had this Error as well and then found a superfluous "<" sign in line 8. Maybe you have the same problem.
After I deleted that I got another error message saying "Exception: The starting column of the range is too small.". This was because in the Add-on version I used row one of the spreadsheet for the Calendar-ID. For the script you can't have an emtpy first row. You have to have your headers in row one.
Another thing I had to change is the colors from their names to their numbers ("GRAY" --> "8").
The only thing not working is the All-day check-box
Unfortunately every time I sync it asks me if want to delete 70 events which it just immediately recreates. If anybody knows why this is I'd be glad to find out.

Since there is no confirmation that Dave will continue to develop, and I have not found a single fork that has progressed on its own.
Maybe you could use the old version.
https://github.com/Davepar/gcalendarsync/tree/master/priorversion
It is done differently and has gcalendarsync.js that you can insert into the Script Editor.
The folder also contains instructions on how to do this.
It’s not as good as the last one but if you don’t have anything at the moment you can try it. And it's easier to make minor changes if you're not used to Clasp.
This may help until you find another suitable add-on.

I tried using the old version but i get the error "TypeError: Cannot read property 'getEvents' of null" right away and what to do with her - I don't know

I had this Error as well and then found a superfluous "<" sign in line 8. Maybe you have the same problem.
After I deleted that I got another error message saying "Exception: The starting column of the range is too small.". This was because in the Add-on version I used row one of the spreadsheet for the Calendar-ID. For the script you can't have an emtpy first row. You have to have your headers in row one.
Another thing I had to change is the colors from their names to their numbers ("GRAY" --> "8").
The only thing not working is the All-day check-box
Unfortunately every time I sync it asks me if want to delete 70 events which it just immediately recreates. Even if I don't change any details. If anybody knows why this is I'd be glad to find out. It won't let me run the script again for a certain amount of time if I added too many events.

Make a backup copy!!!! Beware I  have very limited knowledge about google script.
You need to assign
a variable calendar ID number from your calendar as in this example.
var calendarId =<EMAIL_ADDRESS>no <or> sign
Try this:
deploy, test deployments, select type, google workspace add on, test latest code
save project with new name
click on script function onopen to select and run debug
When asked
verify app (advanced go to update calendar) alow
check if Calendar Sync menu is added to the google sheet. (inline with file, edit view, ...)
delete first line in Calendar tab with sheet ID as it is hard-coded in script.

deploy, test deployments, select type, google workspace add on, test latest code
save project with new name

I can't save this because it sais "To test deployment as Add-on, update the manifest file with Add-on details"
But my only problem is the You have been creating or deleting too many calendars or calendar events in too short a time. Please try again later.-Error. I have about 500 Events already synced to the calendar. If I add one more event and don't change anything for any other event it gives me that error.
I know there is the var THROTTLE_SLEEP_TIME = 200; var MAX_RUN_TIME = 5.75 * 60 * 1000; but I don't know how to use it and I'm not sure if that's acutally the problem.

I've been debugging a bit and could prove that the skript is indeed recreating loads of unaltered events even though the skript already created them (I let it altert mit when it creats new IDs, except it is dublicating events with the exact same ID). Hence why I go over my limit.  I don't know how to fix it yet but will update.

How can I, a person without strong programming skills, overcome the error problem - You have been creating or deleting too many calendars or calendar events in too short a time. Please try again later. ?
I have 8 calendars and only two have more than 1800 entries
I do not understand how the developer was able to get around this problem, when I used the application from the marketplace, I synchronized it several times a day and there were no problems, can someone tell me.
I have already tried changing the source code from the recommendations above - it did not help

In my attempt using the old version, I stumbled upon the [https://github.com/Davepar/gcalendarsync/blob/82cfcdaef51aac52bc8c980e33c9aa87bdaf92fd/priorversion/gcalendarsync.js#L149](following block):
function eventDifferences(convertedCalEvent, sev) {
  var eventDiffs = 0 + /* ... */;

  if (eventDiffs > 0 && convertedCalEvent.guests) {
    // Use a special flag value if an event changed, but it has guests.
    eventDiffs = EVENT_DIFFS_WITH_GUESTS;
  }
  return eventDiffs;
}

Is there a reason for the if statement to exist? In that case, if there's a single change to the event, the script wants to delete the calendar event and create a new one. Commenting out the if-block didn't seem to break anything.

NOOOOO, just as I have just amended my spreadsheet to accommodate for the add-on and ready to go live it dies....
@Davepar I must say sick add-on you made tho, it was definitely 1 of the best options out there.
I even created a Github account just to find out whats happening hahaha.
Is there any way we can help?

I haven't actually changed anything in the add-on in a year. Some people were having issues, which seemed to be caused by needing to authorize the script again. I bumped the version number and re-deployed hoping that would fix the issue. But it didn't seem to update at first. I changed some Marketplace settings, and it seems I've re-triggered the Google review process. There are a dozen issues Google wants me to resolve and I just don't have the time to deal with it.
Sorry it's not working any more. Google is making the process of publishing add-ons too difficult to do as a hobby project.

Hi Dave! I have some experience developing in Google Apps Script. Maybe open sourcing the latest version may let the community with the issues Google is pointing out?
Such a bummer to hear the news since this was a great add-on :(


Resource are corrupted after recompiling

If you recompile an apk file in json-mode you get corrupted language files. It looks like that utf-8 is not supported. Just for your information: original resources.arsc is 19mB, the file after recompiling is 24mB. Feel the difference.
If you recompile an apk file in xml-mode you get some files corrupted. Thus if I put resources.arsc and res folder into original apk I get wrong scrollbar color.

Attach your apk

If you recompile an apk file in json-mode you get corrupted language files. It looks like that utf-8 is not supported. Just for your information: original resources.arsc is 19mB, the file after recompiling is 24mB. Feel the difference.

I decompiled-compiled your apk the file size is almost identical 19.1Mb. But file size doesn't matter, it could happen due to strings encoding or rearranging entry configs.

If you recompile an apk file in xml-mode you get some files corrupted.

Which files ?

Thus if I put resources.arsc and res folder into original apk I get wrong scrollbar color.

Some resource paths maybe different , the two resources are identical but doesn't mean the same.

First screenshot: original resources. The second one: xml recompilation.

Are you kidding? Json mode: original file is 70582959 bytes. Recompiled one is 80497395 bytes. Original recources.arsc is 19082920 bytes, recompiled - 25630892. Right now I have recompiled the result of the first recompilation. Here you are: apk is 92593421 bytes, resources.arsc is 37724524 bytes. How can it be right if resources file grows every time?
JFYI, Apktool always gives the same resources independently the number of recompilations.

Here I am trying to help, but you are impolite.
Don't come here again!

Impoliteness is when someone consider himself infallible.  I will go but it won't make your project to work correctly. Good luck.


⚠ Bofrost.at has degraded performance

In 3d890e7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 910 ms

Resolved: Bofrost.at performance has improved in e631a18 after 13 minutes.


Katib: Add KATIB_POSTGRESQL_SSL_MODE variable of Katib DB Manager

This follow-up PR reflects a change from https://github.com/kubeflow/katib/pull/2266, which introduced a new environment variable option to allow users to specify the value of Postgres sslmode.
It updates Katib DB Manager part of Environment Variables for Katib Components.

@andreyvelich PTAL, thanks a lot.

/assign @andreyvelich

@andreyvelich Thanks for your approval !


www/caddy: Add option to compile only the needed DNS Provider

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.
The problem is, that the current caddy build is unmaintainable, because the DNS Provider modules are creating incompatibilities between each other. This can happen at any time, because of the dependency structure of golang. Also, this kind of build is not recommended by the developers, only the DNS module that is used, should also be compiled in. https://caddy.community/t/having-trouble-with-reproducable-builds-with-caddy-dns-providers/23238
Describe the solution you'd like

The caddy-custom binary build in opnsense ports will exclude all DNS Provider modules, and only add the NTLM and Dynamic DNS non standard modules.
There will be a button in the GUI called "Compile DNS Provider", which resides in the Dynamic DNS Tab, with an explanation.
When pressed, it will trigger a REST API call, and an action, which will trigger a php script.
Inside this script, there is a new function that will  read the currently selected dns provider from the model, then use "caddy add-package MODULENAME", which can compile a new module in on the fly by downloading a new caddy binary from the caddy repo and replacing the current one with the new one. (https://caddyserver.com/docs/command-line#caddy-add-package)
To validate this, another function will call "caddy list-modules --skip-standard" and parse the non standard modules. https://caddyserver.com/docs/command-line#caddy-remove-package
This can be rolled back with https://caddyserver.com/docs/command-line#caddy-remove-package - which can be used to recompile excluding the DNS Provider module.

Describe alternatives you've considered

The alternative would be, that this kind of setup would be possible in the CLI, and there is information in the GUI for the user which cli action is necessary for their chosen DNS Provider to start working. I have seen other Plugins support this CLI only approach, most recent example is Crowdsec with their .yaml parsers, or using the crowdsec hub for additional modules.
Another alternative would be, to totally remove the current DNS Provider, DnyDns and DNS-01 challenge features. Though that would definitely cripple the usecases of the plugin a lot.

Additional context

This kind of solution undermines the packet manager. The binary of the new compiled version is a different one than the installed one. Their SHA hashes differ, don't know if the paket manager will remove or replace this custom binary in the future.
It's not update persistent. As soon as a new packet is pushed from the OPNsense ports, it will overwrite the custom one of the user. That means the user will have to customize it again afterwards.

All in all, this is the biggest issue my plugin is facing right now, and whichever solution is chosen will have ups and downs. There is no perfect solution right now.
Short term solution

Offering customized help text in the GUI that's context sensitive to the currently chosen DNS-Provider with the shell commands needed to install it, would be the best short term solution. The features used are marked "Experimental" in Caddy v.2.7.6, so there is no indication how this will play out in future versions. Spending lots of effort in a GUI implementation without a feature being marked as "stable" is not really in my interest.
The current input validation already prevents mistakes, because it will give feedback when a DNS Provider is missing and won't start Caddy.

Example of a successful module addition:
root@OPNsense:/usr/local/bin # caddy add-package github.com/caddy-dns/cloudflare
2024/03/24 07:27:54.625 INFO    this executable will be replaced        {"path": "/usr/local/bin/caddy"}
2024/03/24 07:27:54.625 INFO    requesting build        {"os": "freebsd", "arch": "amd64", "packages": ["github.com/caddy-dns/cloudflare"]}
2024/03/24 07:27:55.178 INFO    build acquired; backing up current executable   {"current_path": "/usr/local/bin/caddy", "backup_path": "/usr/local/bin/caddy.tmp"}
2024/03/24 07:27:55.178 INFO    downloading binary      {"destination": "/usr/local/bin/caddy"}
2024/03/24 07:27:57.807 INFO    download successful; displaying new binary details      {"location": "/usr/local/bin/caddy"}

Module versions:

dns.providers.cloudflare v0.0.0-20231220181002-8789126791ed

  Non-standard modules: 1

  Unknown modules: 0

Version:
v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=

2024/03/24 07:27:57.894 INFO    upgrade successful; please restart any running Caddy instances  {"executable": "/usr/local/bin/caddy"}

Example of a successful module removal:
root@OPNsense:/usr/local/bin # caddy remove-package github.com/caddy-dns/cloudflare
2024/03/24 07:29:27.523 INFO    this executable will be replaced        {"path": "/usr/local/bin/caddy"}
2024/03/24 07:29:27.523 INFO    requesting build        {"os": "freebsd", "arch": "amd64", "packages": []}
2024/03/24 07:29:28.150 INFO    build acquired; backing up current executable   {"current_path": "/usr/local/bin/caddy", "backup_path": "/usr/local/bin/caddy.tmp"}
2024/03/24 07:29:28.150 INFO    downloading binary      {"destination": "/usr/local/bin/caddy"}
2024/03/24 07:29:30.674 INFO    download successful; displaying new binary details      {"location": "/usr/local/bin/caddy"}

Module versions:

  Non-standard modules: 0

  Unknown modules: 0

Version:
v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=

2024/03/24 07:29:30.755 INFO    upgrade successful; please restart any running Caddy instances  {"executable": "/usr/local/bin/caddy"}

To be frank I'd advise against making a barely manageable dyndns subsystem more complex and I believe that loading binary files from a remote location is a security risk we do not want to be introducing in the public plugins repo. Let alone the work for code and the risk for regressions that cannot be traced.
Cheers,
Franco

@fichtner If that's the case I have to remove the whole DNS Provider feature. I haven't expected this to turn out like this when I implemented it.
Current state of the DNS Provider feature:

It is very hard to maintain
Introduces regressions randomly
Is a pain to compile reproducible
Procompiling all of them is not supported in this way by the caddy developers.

The way forward:

Since this plugin supports custom certificates, people who need the DNS-01 challenge could use the acme client plugin to get a wildcard certificate for the subdomain feature.
And people who need DynDNS could use the ddclient plugin.
This will create a clear separation of concerns.

All in all, I leave this decision up to you, and I will follow what you suggest as the best way forward.

Most of these problems appear to be inherent to DynDNS as we have seen over the years (individual hobby projects glued together not supported by enterprises at all) and the way caddy outsources them to avoid trouble in their own project.
My recommendation is to leave the current state as it is, only improve with actual user reports and confirmations and/or consider removal of actually broken integrations later on.
What do you think?

We already can't leave it as it is anymore, since the libdns version of cloudflare was bumped, and that makes it collide with most other already compiled dns providers.
Next time you try to build caddy-custom it will fail. (Already checked that with opnsense tools)
If this current feature set should be retained, we have to fork the currently DNS Provider Plugins, and use the forked ones as build reference.
Or... -I have to check that-, specify the exact git commit hashes when compiling from their repos, so that it doesn't pull latest with all plugins, but the state we know that works.

@fichtner Yup, specifying the commit hash makes the build go through.
2024/03/24 09:56:13 [INFO] Build complete: ./caddy
2024/03/24 09:56:13 [INFO] Cleaning up temporary folder: /tmp/buildenv_2024-03-24-0954.3907689736
[20240324095613] ===> Staging for caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>_15
[20240324095613] ===> Generating temporary packing list
install  -s -m 555 /usr/obj/usr/ports/www/caddy-custom/work/caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>/caddy /usr/obj/usr/ports/www/caddy-custom/work/stage/usr/local/bin
[20240324095613] ====> Compressing man pages (compress-man)
[20240324095613] ===> Staging rc.d startup script(s)
[20240324095613] ===> Installing for caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>_15
[20240324095613] ===> Checking if caddy-custom is already installed
[20240324095613] ===> Registering installation for caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>_15
Installing caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>_15...
Creating package for bash-5.2.26_1
bash-5.2.26_1 already packaged, skipping...
Creating package for caddy-custom-<IP_ADDRESS>.<IP_ADDRESS>_15

So I will put the commit hashes behind each of the plugins I use. And if a plugin breaks in the future we will remove it.

Sounds like a plan. I haven’t noticed it breaking yet but I can confirm that nightly didn’t build caddy-custom after checking the log.

https://github.com/opnsense/ports/pull/190
https://github.com/opnsense/tools/pull/400
Ran the build a few times, always works, always takes the same sources. I think it might be fixed for a while now.

The current build with the commit hashes is successful. I will keep an eye out for the state of these plugins. The current issues seem mitigated for now.
A DNS provider plugin will be removed if:

they're unmaintained for too long (like years of no updates)
they make build problems
users report errors with the functionality

A DNS Provider plugin will be added if:

it's explicitely requested
it doesn't conflict with the build
it is in the caddy-dns repository and doesn't look unmaintained

@Monviech yep, good policy

Adding a list about the current state of DNS Plugins:
Compare to: https://github.com/caddy-dns
Compiled:
Current Plugin version v1.5.2

cloudflare
duckdns
digitalocean
dnspod
hetzner
godaddy
gandi
ionos
desec
porkbun
route53
acmedns
netlify
namesilo
njalla
vercel
googleclouddns
alidns
powerdns
tencentcloud
dinahosting
metaname
hexonet
ddnss
linode
mailinabox
ovh
namecheap
azure
openstack-designate

** Not part of the build: **

dnsmadeeasy
bunny
civo
scaleway
acmeproxy
inwx
netcup
namedotcom
easydns
infomaniak
directadmin
hosttech
rfc2136
loopia
mythicbeasts
glesys
dynv6
vultr - Doesn't play nice in the build due to different libdns version
nicrudns - Repo is empty
transip - Repo is empty
google-domains - Public Archive (Unmaintained, legacy)


DO NOT MERGE: example discourse embed

NO MERGE NO MERGE NO MERGE
(I disabled CORS for expediency, and even if I didn't this code is gross).
A demo to show what it would look like to have discussions from Discourse displayed contextually in the docs site

Example pages:

Materializations
Tests
DevHub Home

What's in it

There's two visualisation options - a basic list of just topic names, or a more expansive version with the name of the poster and metadata on popularity. We can show/hide any parts of the metadata we like (e.g. maybe we don't want post date, and we might put the like/reply count at the right hand side of the panel), I just don't have the CSS chops to make that work.
Optionally, a Create new topic button.
Right now I'm showing stuff from the last quarter; we can also choose week/month/year/all time. The inline ones are based on view count, the DevHub home one is sorted by "top"


Add mustSupport to data requirements gather

DataRequirements needs to support specification of the elements referenced for data used in the measure.
Add this capability to the data requirements visitor and ensure it is reported as part of the data requirements analysis for measure calculations.

Resolved in #217


health: Implement multistream status integrated with stream status

This is to implement processing of the Multistream webhook events sent by mist-api-connector, in
order to provide a target-specific Multistream status on the stream health dashboard.
Implemented this as a separate reducer, which felt like a nice experience/validation of the code architecture,
but showed how the root "conditions" object might need some improvement. Let's see how this evolves.

Tested running everything but mist/mapic locally, then fabricated some fake events directly on rabbitmq to see analysis happening. Worked like a charm.


Memory Overflow using std::vector of buffers

Hi,
I'm curious what is going on with the memory management when using sycl::buffer inside of std::vector.
I have a very small example program:
#include <sycl/sycl.hpp>
#include <vector>
using namespace sycl;

int main()
{
    queue myQueue;
    auto dims = sycl::range<3>{64, 64, 64};
    std::vector<sycl::buffer<sycl::float2, 3>> vectorOfBuffers;

    for (int index = 0; index < 10000; index++)
    {
        sycl::buffer<sycl::float2, 3> complexIn{dims};
        myQueue.submit([&](sycl::handler &cgh)
                       {
                        sycl::accessor Matrix{complexIn, cgh, sycl::write_only, sycl::no_init};

                        // Ensycl::queue a parallel kernel iterating on a N*M 2D iteration space
                        cgh.parallel_for(dims, [=](sycl::id<3> index) {
                        sycl::float2 temp = {
                            index[2] + index[1] * dims[1] + index[0] * dims[0] * dims[0], 1.0f};
                        Matrix[index] = temp;
                        }); });

        vectorOfBuffers.push_back(complexIn);
    }
}

Compiling for nvidia gpu and running this program gives me the following errors:
/hipSYCL/src/runtime/dag_direct_scheduler.cpp:109 @ ensure_allocation_exists(): dag_direct_scheduler: Lazy memory allocation has failed.
/hipSYCL/src/runtime/cuda/cuda_allocator.cpp:48 @ allocate(): cuda_allocator: cudaMalloc() failed (error code = CUDA:2)

I'm curious what is going on. From monitoring I can see that the GPU memory slowly fills up and then probably overflows.
Why is all the data from the buffers allocated all the time on the GPU?
Shouldn't SYCL be able to copy data to the GPU only when necessary and keep the rest on the host or copy it back to the host when not needed anymore?
Kind regards

Why is all the data from the buffers allocated all the time on the GPU?
Shouldn't SYCL be able to copy data to the GPU only when necessary and keep the rest on the host or copy it back to the host when not needed anymore?

In theory, yes. In practice, no SYCL implementation does this to my knowledge. It's just too hard to know if/when data will be needed again on GPU, and you really don't want to pay the price for unnecessary data transfers because memory eviction heuristics fail.
For best performance, the most reliable strategy is therefore usually to just use persistent allocations. This is also what allows extensions such as hipSYCL's buffer-USM interoperability: https://github.com/illuhad/hipSYCL/blob/develop/doc/buffer-usm-interop.md
The behavior of the hipSYCL runtime with respect to buffers is described in more detail here: https://github.com/illuhad/hipSYCL/blob/develop/doc/runtime-spec.md (note the section "persistent allocations")
If you want things like oversubscription of GPU memory (it will probably always cost you performance, so I'd not recommend it), you can use shared USM allocations. If backends support it, it will be mapped to memory that automatically migrates between host and device using pagefaulting mechanisms. In this case, oversubscription is managed at the driver level which is probably a better approach if you really need it.


SignUp Form UI Improvements

Problem
User does not understand what to enter in the last 3 leave boxes
Fixes

Add info Icon.
Add Label.

@wimpywarlord I would like to contribute to this issue. Thanks!

Sure go ahead


Low gear ratios cause "Infeasible Problem"

This year, our robot had a very low gear ratio (3.14 : 1 to be precise). However, when I enter this gear ratio into Choreo, I always get an "Infeasible Problem Detected" and the path will not generate. Our settings are shown below.

Is there any way to work around or fix this? We would love to use Choreo, but we have just defaulted to telling it our robot weighs 120kg to get it to accelerate slowly enough.

Have you tried using a lower motor torque?
I can look into this issue this week.

@ThatChair would you be able to share your choreo file? You can use the "export diagnostic report" in the menu to generate the zip file

Sorry for the late reply, but I don't see the diagnostic report button. When I pull up the menu, all I see is this:

That button was added after the 2024.2.3 release.

Okay, here it is (in a zip because Github wont let me upload it):
testAuto.zip

The specifics seem to work in the new 2025 beta.


no audio coming out

i have it connected but when i play it on the wii mote i hear a click

I have the exact same issue, i've tried older versions of it, still haven't found a fix, let me know if you do!

i have it connected but when i play it on the wii mote i hear a click

i have the same problen with the wii mote plus inside


Add complete support for .NET files

You should add support for these text files that are very used in every middle-to-big .NET project:

.csproj (fundamental!)
.sln (fundamental!)
.nuspec
.props
.target
.config

I would need sample file content for any of these if I was to add support for them to PreviewCode.


Missing License

Your repository is missing a license file. Is it open source? And if so, could you specify the license?

Added MIT license to repo.

Many thanks! Could you please consider doing the same also for your marketDB project, as I'm curious if it might be of use for a current project of mine.

yes sure, will add it too

Hi, the license statement says that the copyright holder of this code is Paul Chiusano. Are you sure?

ouch, copy-pasta from scalaz ;)


update to latest conferences

moved latest conferences to past section
added latest ReactEurope 2020

@katcita thank you!


OSX 'make install' fails but manual codesign $GOPATH/bin/dlv completes build

What version of Delve are you using (dlv version)?
1.0.0-rc.1

What version of Go are you using? (go version)?
go version go1.8 darwin/amd64

What operating system and processor architecture are you using?
macOS Sierra 10.12.5

What did you do?
make install

What did you expect to see?
scripts/gencert.sh || (echo "An error occurred when generating and installing a new certicate"; exit 1) go install -ldflags="-s" github.com/derekparker/delve/cmd/dlv codesign -s "dlv-cert"  /bin/dlv

What did you see instead?
scripts/gencert.sh || (echo "An error occurred when generating and installing a new certicate"; exit 1) go install -ldflags="-s" github.com/derekparker/delve/cmd/dlv codesign -s "dlv-cert"  /bin/dlv /bin/dlv: No such file or directory

This was resolved by running codesign $GOPATH/bin/dlv

looks like you didn't have GOPATH defined when you ran make.

I thought the same but echo $GOPATH directly after make install had
failed reported the correct path and immediately after that codesign -s "dlv-cert" $GOPATH/bin/dlv worked. I hadn't set $GOPATH in the meantime
and its been setup correctly on my system for a very long time.
On 21 June 2017 at 10:57, Alessandro Arzilli<EMAIL_ADDRESS>wrote:

looks like you didn't have GOPATH defined when you ran make.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/derekparker/delve/issues/891#issuecomment-310030342,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHuMggsx8QiSwsu6CCHiOrmngMtESgyks5sGOjwgaJpZM4OAqOC
.

Very odd, I don't see what else could cause this.

Arrgh, that's a bit of scripting I wrote. 👼
Hmmm, maybe it's something to do with $GOPATH not being exported correctly in some cases...
I'll try to get time to investigate this over the weekend.

@jasonrharris Actually, would you have time to check if the latest master branch source still gives the problem?

export GOBIN=$GOPATH/bin

Given the changes to how we build and sign the executable (we moved from Makefile to a go script), I think this isn't relevant anymore.


Grid Item Context Menu UI tweaks

The new designs for the dashboard have tightened up the context menu a bit.
Old menu:

New menu:

Forgot this menu is attached to the other popover menus that I already updated. (#1490)


Bump tags for UBI-based Dockerfile

Signed-off-by: Juan Antonio Osorio<EMAIL_ADDRESS>
What type of PR is this?
/kind bug
/kind failing-test
What this PR does / why we need it:
We're running into issues with the UBI build. So this bumps the
checksums to the latest ones in order to fix this.
Which issue(s) this PR fixes:
None
Does this PR have test?
The UBI build.
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Codecov Report

Merging #1089 (a54ede5) into main (e259f4f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1089   +/-   ##
=======================================
  Coverage   50.13%   50.13%
=======================================
  Files          42       42
  Lines        4789     4789
=======================================
  Hits         2401     2401
  Misses       2309     2309
  Partials       79       79


Typescript definition of keys does not work with subsets of string.

type E = 'monday' | 'tuesday' | 'wednesday';
const s = new MultiSet<E>();
let day: E;
for ([day] of s.keys()) {
  console.log(day);
}

I expect s.keys() to be of type IterableIterator<E>, but it is of type IterableIterator<string>

What makes this confusing is that hovering over keys()  in VSCode shows this:

So perhaps it's a vscode or Typescript version issue?

pebcak


Ability to expire Hydras when using Summoner

This is a feature request for the ability to expire or somehow clear out old Hydra instances created by a Summoner. I'm using robohydra to run as a mock api for some BDD tests and using a summoner enables us to run the tests in parallel and enable/disable the scenarios independently. However, once a test has run we will never reuse that Hydra.
At the moment it looks like the hydras are just stored in a plain object (e.g. https://github.com/robohydra/robohydra/blob/master/lib/robohydrasummoner.js#L20) so I'm guessing the memory footprint will gradually increase. We could replace this with something like https://github.com/isaacs/node-lru-cache and unused Hydras would drop off after a certain limit is exceeded.

That's a good point. Something I don't like about the automatic clean-up of hydras is that they can contain state (dynamically created heads, active scenario, values of variables in certain plugins, etc) so removing a hydra and then using it again won't necessarily have the same result.
That's why I'd rather go for some explicit removal. I guess that, in your case, it would be enough to make an API call in the teardown method or similar.
I was actually considering making an API and maybe an admin UI to see the different active hydras, but I didn't know how much summoners would be used, and I thought it wasn't worth the effort.
What do you think about this approach, would that fit your usecase?

Yes - explicit removal would certainly meet our requirements. As you suggested we could delete it in the teardown for the tests. It would be nice to have it part of the REST api but a UI would be fine too (which we'd access with Selenium/Webdriver).

You can have a look at the hydra-deletion branch and see if that seems enough:
https://github.com/robohydra/robohydra/tree/hydra-deletion

Looks pretty good to me. A couple of minor things I noticed were:

There is a button to delete the default Hydra but I'm guessing this doesn't really do anything. I thought it might delete and then recreate it but the Started time in the page footer doesn't change.
The response from the REST deletion is the the list of summoner hydras. It makes sense in the UI to return to this list but I wouldn't expect a restful deletion to return anything (apart from appropriate response code). https://github.com/robohydra/robohydra/commit/f2a7c8ac0417aedf4e93a49ff0dc604d28059d98#diff-845fcfc13ab990b982166f930797e544R515

Neither of these are big problems - in general looks great. Thanks

Thanks for your feedback! About (1), it's actually a bug, the "Started" time is completely broken and I never noticed :-(
I've also changed the REST deletion response to use status code 204 No Content and an empty response body.
See the updated branch for the Started time fix.

This is now in master BTW.

Brilliant - thanks.


Add subtype to the Pause Switch

Fixes #114
When having multiple Services of the same type, we need to provide a subtype or home bridge will fail. Now, with the addition of the rooms' switches, we need to provide a subtype name to the Pause switch

Make sure that the switches can be scattered in different rooms)

@afharo Tested?

Tanks @afharo


Listing Appointment Function

Implement listing appointment function with command : list or list

Resolving the user story under #13


emoji picker: Show name of emoji in emoji picker.

It would be great to have the name of the emoji appear somewhere (other than the title text) when you hover or move the selector box over it. Currently I find myself hovering over the emoji, waiting for the title text, and it also makes it feel less usable from the keyboard.
I'm not sure I quite like how Slack does it, but it has one example of what it could mean to show the name of the emoji on hover.

Does any of these two look good enough?

Looks great!

@lonerz Which of the two in particular?

I think the second looks better.

I think I like the second one better as well.
Also, I think we should show only one name: either the canonical name, or the name that the user is completing to get that emoji. (E.g. if they are typing 'calend' we should show calendar, if they are typing 'dat' we should show date, and if they are typing nothing we should just show the canonical name).

I agree with the consensus here on how this should look :)

One minor edit to what I said above: for the reactions picker, we should allow you to type in anything, but at the bottom we should show only the canonical name, since that is what your reaction will be.
For the compose picker, I think what I said still makes sense :).


Consolidate on FIXTURE_DIR assignments

Because ETOOMANYFIXTUREDIRS.
We define FIXTURE_DIR all over the place, and we don't need to.

@miq-bot add_label core, refactoring

cc/ @Fryguy

Fixed to use Pathname; see comment for ApplicationRecord::


feat(connector): [Bambora] Use connector_response_reference_id as reference to the connector #2324

Type of Change

[x] New feature

Description
The connector_response_reference_id parameter has been set for the Bambora Payment Solutions for uniform reference and transaction tracking.
File Changes

[x] This PR modifies the Bambora Transformers file.

Location- router/src/connector/bambora/transformers.rs
Motivation and Context
This PR was raised so that it Fixes #2324  !
How did you test it?

I ran the following command, and all the errors were addressed properly, and the build was successful.

cargo clippy --all-features

The code changes were formatted with the following command to fix styling issues.

cargo +nightly fmt

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code

Please review and suggest changes, if any. Thanks.
cc: @srujanchikke @swangi-kumari

Hey @Rutam21 ,
Thanks a bunch for all your contributions! We've got a little something for you to show our appreciation.
Just take a moment to fill out this form, and get ready for some awesome swag coming your way.
Thanks!