text:
Use non static name for the Cinder and Glance CRs

When the openstack operator creates the cinder CR it always uses the
"cinder" name and there is no way to change it.
This means that the names of the pods, and therefore the reported
hostname inside them, will always be the same for the backup service
(cinder-backup-0) and for the volume service in 2 deployments if they
have the same key in the volumes map.
This may be fine for some deployments, but it creates problems in
others, because many cinder drivers expect the hostnames of the hosts
attaching volumes to be unique.
Because they expect them to be unique they use the hostname as a key to
store information on the storage array such as the iSCSI initiator name
or the HBAs addresses.
If they are not unique there can be unexpected behavior like hosts being
unable to attach.
This is very common in CI systems, but is not limited to them as it can
also happen in production deployments using the same storage arrays.
A similar thing would happen when Glance is using Cinder as a backend.
With this PR the cinder and glance sections have a new field called
randomPodNames each so the openstack-operator can generate a non
static name for the Cinder and Glance CRs.
This new name is the same as before but with a suffix of a dash (-)
followed by the first 5 characters of the OpenStackControlPlane UID.
The is still a small chance to have duplicated pod names, but the chance
should be small enough to be safe to ignore.
Related PRs:

https://github.com/openstack-k8s-operators/cinder-operator/pull/399
https://github.com/openstack-k8s-operators/cinder-operator/pull/400
https://github.com/openstack-k8s-operators/glance-operator/pull/555

Jira: OSPRH-7396

/retest

/retest

I'm ok with the current patch, and I don't have a strong option on using uniquePodNames instead of randomPodNames, so we can move forward with this unless there are strong concerns to address.

As discussed, let's have an additional iteration to move randomPodNames into uniquePodNames and we'll review again.

@stuggi @abays not sure you can give another pass to this and land to solve the nfs related issue. I think the main point was about the CRD parameter name and it has been added under Cinder and Glance templates.
Just looking at kuttl we can see the old behavior is preserved [1], so I think it's good to go.
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_openstack-operator/847/pull-ci-openstack-k8s-operators-openstack-operator-main-openstack-operator-build-deploy-kuttl/1805679081946091520/artifacts/openstack-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-239f9b57d856c30ba157bcdfd75edb27270a8ba8613199defb1cfecf726f30c5/namespaces/openstack/crs/glances.glance.openstack.org/glance.yaml

@stuggi @abays not sure you can give another pass to this and land to solve the nfs related issue. I think the main point was about the CRD parameter name and it has been added under Cinder and Glance templates. Just looking at kuttl we can see the old behavior is preserved [1], so I think it's good to go.
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_openstack-operator/847/pull-ci-openstack-k8s-operators-openstack-operator-main-openstack-operator-build-deploy-kuttl/1805679081946091520/artifacts/openstack-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-239f9b57d856c30ba157bcdfd75edb27270a8ba8613199defb1cfecf726f30c5/namespaces/openstack/crs/glances.glance.openstack.org/glance.yaml

I am ok to land this just wondering if it would be better to keep this in the component api as a parameter to have it transparent for the openstack-operator. like the openstack-operator always creates with the static name for a cinder or glance cr in the namespace, but the service operator could still use unique names for the specific deployments which need it (c-v, c-b,.). iiuc c-a and c-s won't need this.

I think the main goal is the opposite: the service operator can accept whatever is passed (if we build a CR with a name != glance or cinder, it will work), but considering the main CR is generated by the openstack-operator, this kind of features applies only when the deployment is coordinated from a CR where both glance and cinder are defined in this context.
The service operator will work, but we can keep it generic enough to work with and without this logic.
In addition, having this code living here makes any potential maintenance easy (because we can keep the behavior aligned for multiple operators from the same place).
Not sure if you want to discuss and dig more into this problem, but if you think it's problematic we can discuss about changing it (after GA?)

@stuggi @abays not sure you can give another pass to this and land to solve the nfs related issue. I think the main point was about the CRD parameter name and it has been added under Cinder and Glance templates. Just looking at kuttl we can see the old behavior is preserved [1], so I think it's good to go.
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openstack-k8s-operators_openstack-operator/847/pull-ci-openstack-k8s-operators-openstack-operator-main-openstack-operator-build-deploy-kuttl/1805679081946091520/artifacts/openstack-operator-build-deploy-kuttl/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-239f9b57d856c30ba157bcdfd75edb27270a8ba8613199defb1cfecf726f30c5/namespaces/openstack/crs/glances.glance.openstack.org/glance.yaml

I am ok to land this just wondering if it would be better to keep this in the component api as a parameter to have it transparent for the openstack-operator. like the openstack-operator always creates with the static name for a cinder or glance cr in the namespace, but the service operator could still use unique names for the specific deployments which need it (c-v, c-b,.). iiuc c-a and c-s won't need this.

I think the main goal is the opposite: the service operator can accept whatever is passed (if we build a CR with a name != glance or cinder, it will work), but considering the main CR is generated by the openstack-operator, this kind of features applies only when the deployment is coordinated from a CR where both glance and cinder are defined in this context. The service operator will work, but we can keep it generic enough to work with and without this logic. In addition, having this code living here makes any potential maintenance easy (because we can keep the behavior aligned for multiple operators from the same place). Not sure if you want to discuss and dig more into this problem, but if you think it's problematic we can discuss about changing it (after GA?)

thanks for the additional details, from my side we can keep it as is. Lets wait for  @abays review and get it in

error: build error: Failed to push image: trying to reuse blob sha256:e394ea8406c7ed85ddc862f882ec77dcfd3863de3cb90fd8006238d521d22d44 at destination: pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": dial tcp 38.129.56.158:443: i/o timeout

/test openstack-operator-build-deploy-kuttl

authors: Akrog abays fmount stuggi


text:
Add test-operator-logs pvc

This patch ensures that test-operator creates a pvc called test-operator-logs and mounts it to pods spawned by the test-operator.
The pvc can be used as a persistent storage for all the artifacts related to the tests execution.

thank you, @arxcruz and @kopecmartin!

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
'source' tag at upload time defaults to 'undefined' when empty

tl;dr : When no 'sources' are defined from previous iD edits (or I have cleared them in previous iD edits), the default for the next time should be no sources whatsoever, not the source 'undefined' as a character string.
If you upload a change using the iD editor, one of the selections available to you is the 'Sources'.
If in a previous iD editing session, you have explicitly defined one or more Sources, these will (still) appear in the box, on the assumption that you want to use them again. (E.g., if I previously said 'survey', the box will have in it:)
( [x] survey ) ( Add ... )
BUT -- If I subsequently delete 'survey' and upload with no source defined, I can successfully do so. (See https://www.openstreetmap.org/changeset/58716992 ) Here's the problem. The NEXT time I edit and upload, the default ( [x] undefined ) appears, see https://www.openstreetmap.org/changeset/58717013 . This shouldn't happen.

It looks like #4993 successfully prevents an empty source value from being written, but the real thing that should be done here is to 'not write the source key at all if no value is provided'. In other words, "undefined" is not a value, it's the lack of one and no key should be written.

Thanks @skylerbunny I just fixed this.  I also added some code to ignore and remove any literal 'undefined' source value that might have been written to localStorage.  Because the saved source/comment/hashtags expire after 2 days, this code can go away in iD v2.9.

this was closed by 644985c8e

source: gharchive/issue

authors: bhousel skylerbunny

repo: openstreetmap/iD

license: ISC


text:
Mapillary sign overlay not showing up

Judging by the lack of issues on here, I am the only one that can't bring up Mapillary traffic sign overlay?
The mapillary image cone overlay plugin works.
Tried Chrome 60 and Edge

@cbeddow fixed this with #5395, but there is a follow-on issue to fix.
The signs layer is working again, but the detections overlaid on each image are not working yet.

authors: bhousel tohaklim


text:
Pipeline looks too much like segments of what is actually one segment

The pipeline is the bottom line.

The problem is the segments look just like... segments!
Perhaps some other representation could be used.
=======|========|======
Hmmm, still not good enough.
OK, maybe just
================
Anyway, the point is the user sees these as several segments, when in fact they are just one segment.
The problem doesn't occur with the path, as the path's on-off pattern is too compact to cause the mistake.

Personally I see nor problem with this rendering, and it matches image of pipeline as series of connected pipes (not exact match of reality, but as far as map symbols go - quite decent match)

authors: jidanni matkoniecz


text:
New preset: shop=ski

A shop selling skis and related accessories and services.
https://wiki.openstreetmap.org/wiki/Tag:shop%3Dski

some statistics:

tag
usage

shop=sports + sports=ski
93

shop=ski
256

Edited wiki page a bit.
I think that supporting top level shop values for every single sport is a poor idea.

I started https://community.openstreetmap.org/t/do-we-need-shop-ski-and-shop-golf/106249

authors: maro-21 matkoniecz tyrasd

repo: openstreetmap/id-tagging-schema


text:
[Question] 安装问题

**
➤ YN0009: │ nsfw@npm:2.2.0 couldn't be built successfully (exit code 7, logs can be found here: C:\Users\AppData\Local\Temp\xfs-54f6c9e0\build.log)
➤ YN0009: │ spdlog@npm:0.9.0 couldn't be built successfully (exit code 7, logs can be found here: C:\Users\AppData\Local\Temp\xfs-eb206726\build.log)
➤ YN0009: │ node-pty@npm:0.11.0-beta19 [7bbc6] couldn't be built successfully (exit code 7, logs can be found here: C:\Users\AppData\Local\Temp\xfs-138e8ddc\build.log)
**
log 里面提示
This file contains the result of Yarn building a package (spdlog@npm:0.9.0)
Script code: node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@9.3.1
gyp info using node@13.14.0 | win32 | x64
gyp info find Python using Python version 3.8.0 found at "D:\python3.8\python.exe"
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn UNKNOWN
gyp ERR! stack     at ChildProcess.spawn (internal/child_process.js:405:11)
gyp ERR! stack     at spawn (child_process.js:548:9)
gyp ERR! stack     at execFile (child_process.js:232:17)
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2017OrNewer (D:\gitClone\core\node_modules\node-gyp\lib\find-visualstudio.js:141:17)
gyp ERR! stack     at VisualStudioFinder.findVisualStudio (D:\core\node_modules\node-gyp\lib\find-visualstudio.js:63:10)
gyp ERR! stack     at findVisualStudio (D:\core\node_modules\node-gyp\lib\find-visualstudio.js:13:10)
gyp ERR! stack     at D:\gitClone\core\node_modules\node-gyp\lib\configure.js:87:9
gyp ERR! stack     at FSReqCallback.oncomplete (fs.js:159:23)
gyp ERR! System Windows_NT 10.0.19045
gyp ERR! command "C:\Program Files\nodejs\node.exe" "D:\core\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:\gitClone\core\node_modules\spdlog
gyp ERR! node -v v13.14.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.
可以帮忙看下为什么一直安装失败吗，我这边的配置
windows 11
node 13.14.0  (node版本有尝试切换14.12.3  16.0.0 18.18.0）
node-gyp 9.3.1
yarn 3.2.4
python 3.8.0
开发工具 ： vscode
启动项目
D:\core>yarn run start
[]
{ _: [ 'rebuild' ] }
rebuilding native for node version v13.14.0
rebuilding node-pty: 0.11.0-beta19 for arch x64
cache dir C:\Users.sumi-dev\opensumi_build_cache\node-v13.14.0-x64\node-pty-0.11.0-beta19
running command node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@9.3.1
gyp info using node@13.14.0 | win32 | x64
gyp info find Python using Python version 3.8.0 found at "D:\python3.8\python.exe"
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn UNKNOWN
gyp ERR! stack     at ChildProcess.spawn (internal/child_process.js:405:11)
gyp ERR! stack     at spawn (child_process.js:548:9)
gyp ERR! stack     at execFile (child_process.js:232:17)
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2017OrNewer (D:\core\node_modules\node-gyp\lib\find-visualstudio.js:141:17)
gyp ERR! stack     at VisualStudioFinder.findVisualStudio (D:\gitClone\core\node_modules\node-gyp\lib\find-visualstudio.js:63:10)
gyp ERR! stack     at findVisualStudio (D:\gitClone\core\node_modules\node-gyp\lib\find-visualstudio.js:13:10)
gyp ERR! stack     at D:\gitClone\core\node_modules\node-gyp\lib\configure.js:87:9
gyp ERR! stack     at FSReqCallback.oncomplete (fs.js:159:23)
gyp ERR! System Windows_NT 10.0.19045
gyp ERR! command "C:\Program Files\nodejs\node.exe" "D:\core\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:\gitClone\core\node_modules\node-pty
gyp ERR! node -v v13.14.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.
child_process.js:650
throw err;
^
Error: Command failed: node-gyp rebuild
at checkExecSyncError (child_process.js:611:11)
at execSync (child_process.js:647:15)
at rebuildModule (D:\gitClone\core\tools\dev-tool\cli\rebuild-native.js:64:5)
at D:\gitClone\core\tools\dev-tool\cli\rebuild-native.js:84:5
at Array.forEach ()
at module.exports.rebuild (D:\gitClone\core\tools\dev-tool\cli\rebuild-native.js:83:17)
at Object.handler (D:\gitClone\core\tools\dev-tool\cli\index.js:11:5)
at Commander.run (D:\gitClone\core\tools\dev-tool\cli\commander\index.js:17:17)
at Object. (D:\gitClone\core\tools\dev-tool\cli\index.js:16:11)
at Module._compile (internal/modules/cjs/loader.js:1118:30) {
status: 7,
signal: null,
output: [ null, null, null ],
pid: 17064,
stdout: null,
stderr: null
}

@gaoshengqing21 这里看着是系统环境上存在问题，可以看一下 开发环境准备 文档。

repo: opensumi/core

license: MIT


text:
Add subnet specific take

Description
We aim to fully integrate the functionality for delegates to set and adjust their take values per subnet, including the ability to increase or decrease these values. This  involves updating the do_become_delegate function, modifying the existing DelegateInfo struct to include subnet-specific take values, and ensuring that delegates can dynamically adjust their take values for specific subnets.
By providing delegates with the flexibility to manage their take values on a per-subnet basis, we enable them to tailor their participation and rewards strategy according to their preferences and the unique characteristics of each subnet.
Acceptance Criteria

The DelegateInfo struct should be modified to include a new field subnet_takes of type Vec<(Compact<u16>, Compact<u16>)> to store subnet-specific take values.
The do_become_delegate function should be updated to accept a list of subnet IDs and their corresponding take values, allowing delegates to set initial take values for multiple subnets upon becoming a delegate.
A storage migration should be implemented to handle the addition of the subnet_takes field to the DelegateInfo struct, ensuring a smooth transition for existing delegates.
The do_increase_take and do_decrease_take functions should be adjusted to handle subnet-specific take adjustments, ensuring that increases or decreases are performed within the constraints of the system's rules.
Proper validation should be in place to ensure that the specified subnets exist and that the new take values adhere to the system's constraints.
The updated functionality should be thoroughly tested to verify that delegates can successfully set and adjust their take values per subnet, and that the changes are accurately reflected in the storage and overall system behavior.

Tasks

[ ] Modify the DelegateInfo struct in lib.rs to include the subnet_takes field.

#[derive(Decode, Encode, PartialEq, Eq, Clone, Debug)]
pub struct DelegateInfo<T: Config> {
    // ...
    subnet_takes: Vec<(Compact<u16>, Compact<u16>)>, // New field: Vec of (subnet ID, take value)
}

[ ] Implement a storage migration to handle the addition of the subnet_takes field to the DelegateInfo struct.
[ ] Update the do_become_delegate function in staking.rs to accept a list of subnet IDs and their corresponding take values.

// Update the do_become_delegate function
pub fn do_become_delegate(
    origin: T::RuntimeOrigin,
    hotkey: T::AccountId,
    subnet_takes: Vec<(u16, u16)>,
) -> dispatch::DispatchResult {
    // ...
    let mut delegate_info = DelegateInfo {
        // ...
        subnet_takes: subnet_takes.iter().map(|(id, take)| (Compact(*id), Compact(*take))).collect(),
    };
    // ...
}

[ ] Modify the do_increase_take function in staking.rs to handle subnet-specific take increases.
[ ] Modify the do_decrease_take function in staking.rs to handle subnet-specific take decreases.

Related Links

Set Delegate Take PR

@gztensor this is merged into stao / dtao right ? I guess we can close the issue ?

@distributedstatemachine , PR#356 addresses this issue. If PR looks good, ok to merge and close this issue.

authors: distributedstatemachine gztensor

repo: opentensor/subtensor

license: Unlicense


text:
Rework manifesto

I left a bunch of comments on the manifest on the Google Doc. As requested, I've turned those comments/suggestions into a PR. I've ended up reworking the manifesto to:

More clearly focus on the central issue: that Terraform needs to remain under a truly open source license, and that without it, the community will fall apart. I think this is more important than the focus on whether Terraform is a language or not.
More clearly call out what we intend to do: namely, ensure Terraform ends up in a foundation.
(Minor) Switch to a narrower width + justified text, as I believe that's more pleasant for reading on larger screens. See screenshot below for how it looks now.

This is a pretty significant change. We can choose to use all of it or cherry pick some parts or whatever else ya'll prefer.

I like this new version better too.

While merging the latest from main, I hit a broken <h2> block. I think it was from this PR: https://github.com/opentffoundation/manifesto/pull/21/files#diff-0eb547304658805aad788d320f10bf1f292797b5e6d745a3bf617584da017051R116-R117.
I tried to fix it up a bit in this PR.

No major objections
Suggest we keep the central point of "Terraform is language, not a hostable backend product" though. It is strong, easy to pass on, easy to relate, nerdy enough and simple enough at the same time.

authors: SebastianStadil ZIJ brikis98

repo: opentffoundation/manifesto


text:
[build] Unaligned load/store compiler warning

Hi all, GCC/Clang provide the -Wcast-align warning switch, which tells the compiler to emit warnings whenever a pointer is cast such that the required alignment of the target is increased. For instance, *reinterpret_cast<uint32_t *>(GetEnterpriseNumberLocation()) would emit a warning.
This issue is related to #4617.
In the former example, the compiler could emit instructions which access unaligned memory. Cortex M4 mostly supports unaligned accesses, but store/load double/multiple instructions (LDM, STM, LDRD and STRD) will always generate a usage fault. In general, I guess that the compiler doesn't generate these instructions frequently, so the code works. But I think we should enable the warning and fix the potential issues because the code would break with a new compiler version or different optimization levels.
I enabled -Wcast-align, and I found these instances of possible problems in (core) code.
In heap.hpp:
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/utils/heap.hpp#L94-L97
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/utils/heap.hpp#L107-L110
These are not really issues, because CAlloc always aligns size. In this case, there are two ways to tell the compiler that this isn't a problem:

Use GCC/Clang __builtin_assume_aligned:

uint16_t GetNext(void) const
{
    const uint8_t *ptr = reinterpret_cast<const uint8_t *>(this) + sizeof(mSize) + mSize;
    return *reinterpret_cast<const uint16_t *>(__builtin_assume_aligned(ptr, 2));
}

(of course, wrapped in a OT_TOOL... macro). This alternative doesn't have any downside, except possibly for compiler support.

Something like this:

uint16_t GetNext(void) const
{
    const uint8_t *ptr = ;
    return *(reinterpret_cast<const uint16_t *>(this) + sizeof(mSize) / 2 + mSize / 2);
}

This alternative increases the code size by 16 bytes on my test platform.
In network_data_tlvs.hpp:
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/thread/network_data_tlvs.hpp#L927-L931
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/thread/network_data_tlvs.hpp#L956-L962
These are actually potential issues (there is even a comment that flags them!). Two potential solutions:

Change the code to use the TlvUint32 helper class. This seems the "correct" thing to do, but I think it is a rather large change.

Something like this:

In toolchain.h:
typedef uint32_t packed_uint32_t __attribute__((aligned(1)));   //(or equivalent for other compilers).

In network_data_tlvs.hpp:
return HostSwap32(*reinterpret_cast<const packed_uint32_t *>(GetEnterpriseNumberLocation()));

What do you think?

@dismirlian, thank you for raising this issue!
For the heap code, I would tend to prefer the second option because it avoids compiler support. 16 byte code overhead seems OK for this.
For the network data code, how about using:
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/common/encoding.hpp#L145-L149

Hi @jwhui, thanks for your suggestions!

For the heap code, I would tend to prefer the second option because it avoids compiler support. 16 byte code overhead seems OK for this.

Actually, a better alternative would be an intermediate cast to a void *; that will get rid of the warning without any impact to code size.

For the network data code, how about using:
https://github.com/openthread/openthread/blob/c6a258e3a5bd90aa26d8245c435c0ae5797027f4/src/core/common/encoding.hpp#L145-L149

Great.

@dismirlian, sounds good. Are you planning to submit a PR?

@jwhui yes, but first I need to figure out what to do with the platforms. I can enable the warning for the core code only, for now. What do you think?

Enabling the warning for code in src/ is a good start! Thanks, @dismirlian.

@dismirlian , have you been able to make any progress on this?

@jwhui, I'll have to re-analyze this because of the changes in #4806; maybe it's not relevant any more. I'll try to do it over the weekend.

authors: dismirlian jwhui

repo: openthread/openthread


text:
How to solve 'SrpServer-----: Name conflict'

Describe the bug A clear and concise description of what the bug is.
If SRP Client re-register, it will give a name conflict error in SRP Server.
So, How do I properly update the SRP Client information when my end device IP changes after reboot?
Mon Aug 22 09:59:21 2022 user.warn otbr-agent[21919]: 0d.18:00:11.885 [W] SrpServer-----: Name conflict: host name f4ce3614c96b8b4d.default.service.arpa. has already been allocated
Mon Aug 22 09:59:21 2022 user.warn otbr-agent[21919]: 0d.18:00:11.886 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
Mon Aug 22 09:59:21 2022 user.warn otbr-agent[21919]: 0d.18:00:11.886 [W] SrpServer-----: Send fail response: 6
Mon Aug 22 09:59:23 2022 user.warn otbr-agent[21919]: 0d.18:00:13.707 [W] SrpServer-----: Name conflict: host name f4ce3614c96b8b4d.default.service.arpa. has already been allocated
Mon Aug 22 09:59:23 2022 user.warn otbr-agent[21919]: 0d.18:00:13.708 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
Mon Aug 22 09:59:23 2022 user.warn otbr-agent[21919]: 0d.18:00:13.708 [W] SrpServer-----: Send fail response: 6
Mon Aug 22 09:59:26 2022 user.warn otbr-agent[21919]: 0d.18:00:16.796 [W] SrpServer-----: Name conflict: host name f4ce3614c96b8b4d.default.service.arpa. has already been allocated
Mon Aug 22 09:59:26 2022 user.warn otbr-agent[21919]: 0d.18:00:16.797 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
Mon Aug 22 09:59:26 2022 user.warn otbr-agent[21919]: 0d.18:00:16.798 [W] SrpServer-----: Send fail response: 6
Mon Aug 22 09:59:32 2022 user.warn otbr-agent[21919]: 0d.18:00:22.033 [W] SrpServer-----: Name conflict: host name f4ce3614c96b8b4d.default.service.arpa. has already been allocated
Mon Aug 22 09:59:32 2022 user.warn otbr-agent[21919]: 0d.18:00:22.034 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
Mon Aug 22 09:59:32 2022 user.warn otbr-agent[21919]: 0d.18:00:22.035 [W] SrpServer-----: Send fail response: 6
Mon Aug 22 09:59:40 2022 user.warn otbr-agent[21919]: 0d.18:00:30.915 [W] SrpServer-----: Name conflict: host name f4ce3614c96b8b4d.default.service.arpa. has already been allocated
Mon Aug 22 09:59:40 2022 user.warn otbr-agent[21919]: 0d.18:00:30.916 [W] SrpServer-----: Failed to process DNS Update section: Duplicated
Mon Aug 22 09:59:40 2022 user.warn otbr-agent[21919]: 0d.18:00:30.916 [W] SrpServer-----: Send fail response: 6

root@OpenWrt:~# ot-ctl srp server service
my_instance_name._ipps._udp.default.service.arpa.
    deleted: true
Done

To Reproduce Information to reproduce the behavior, including:

Git commit id https://github.com/openthread/ot-br-posix/commit/3a98779dc9f0875af9c7b137e764c9663bfdc9c3
IEEE 802.15.4 hardware platform
Build steps
Network topology

Expected behavior A clear and concise description of what you expected to happen.
Console/log output If applicable, add console/log output to help explain your problem.
Additional context Add any other context about the problem here.

SRP implements First-Come, First Served naming. To prevent name conflicts, SRP clients maintain a key to sign SRP updates. As long as the SRP Client maintains the same key, it should be able to send SRP Updates (i.e. re-register) with the same name(s) that it had successfully registered in the past:
https://github.com/openthread/openthread/blob/d48799dddfde76b7b228f07144ba1d8f4e08e2e6/src/core/net/srp_server.cpp#L339
The SRP Client should maintain the SRP Key in non-volatile storage:
https://github.com/openthread/openthread/blob/d48799dddfde76b7b228f07144ba1d8f4e08e2e6/src/core/common/settings.hpp#L118
If the key is lost for whatever reason (including a factory reset) the SRP Client will not be able to re-register the same name(s).

@lancersky Can you clarify if below is true for your SRP client device: the device has been factory reset but the same value is used to construct the SRP host name f4ce3614c96b8b4d.default.service.arpa?
Factoryreset changes the SRP client key and name conflicts happen when the same name is registered with different keys. Note that
root@OpenWrt:~# ot-ctl srp server service
my_instance_name._ipps._udp.default.service.arpa.
    deleted: true
Done

indicates the DNS Resource Records for the service are deleted but the name is still allocated for the original client (you should check the host instead by the way ot-ctl srp server host)

Closing stale issue.

authors: jwhui lancersky wgtdkp


text:
[key-manager] move KeyManager and Mac init to after Settings init

Storing Network key in KeyManager initialization requires platform settings module to be initialized first.
Also as Mac calls Get<KeyManager>().UpdateKeyMaterial(), it's initialization should be moved to after KeyManager's.
Created initialization function for KeyManager to call it in instance.cpp after Settings are initialized.
Created initialization function for Macto call it in instance.cpp after KeyManager is initialized.

Thanks @maciejbaczmanski.

Storing Network key in KeyManager initialization requires platform settings module to be initialized first.

Not sure if we do save or read from Settings in KeyManager constructor? Maybe I am missing something?
I know under OPENTHREAD_CONFIG_PLATFORM_KEY_REFERENCES_ENABLE we do call StoreNetworkKey() but that should save it in secure Crypto::Storage which is a different module from Settings.
The secure Crypto::Storage uses otPlatCrypto platform APIs and has otPlatCryptoInit() which is called from KeyManager constructor (so should be ready).

Also as Mac calls Get<KeyManager>().UpdateKeyMaterial(), it's initialization should be moved to after KeyManager's.

I don't think UpdateKeyMaterial reads anything from Settings. I think it just calculates all the keys (from main key).
In Instanceclass  we have mKeyManager before mMac variable, so its constructor should called before Mac, so I think we should be good in terms of order of calls.

Hi @abtink

Not sure if we do save or read from Settings in KeyManager constructor? Maybe I am missing something?
I know under OPENTHREAD_CONFIG_PLATFORM_KEY_REFERENCES_ENABLE we do call StoreNetworkKey() but that should save it in secure Crypto::Storage which is a different module from Settings.
The secure Crypto::Storage uses otPlatCrypto platform APIs and has otPlatCryptoInit() which is called from KeyManager constructor (so should be ready).

Right now yes, but for example we plan to modify NCS implemetation for NRF52 to use only PSA Crypto API. This requires emulating secure storage which requires calling settings_subsys_init(); while initializing Crypto module. More info can be found here: https://github.com/nrfconnect/sdk-nrf/pull/11911

I don't think UpdateKeyMaterial reads anything from Settings. I think it just calculates all the keys (from main key).

I might have explained it wrong in the commit message. What I meant is that MAC's initialization calls  UpdateKeyMaterial which is implemented in KeyManager. Hence, if we move KeyManager's implementation, we have to move that part of Mac too. I'll try to reword the commit message.
I can see some more fails for POSIX. I'm working on them and will update the PR.

@abtink We've proceeded with handling that in otPlatCryptoInit() as you suggested. Thanks!

Thanks @maciejbaczmanski . 👍

authors: abtink maciejbaczmanski


text:
🐛 [Bug]: 画布最外层body节点高度没有占满问题

Environment
chrome
Version
latest
Version
latest
Link to minimal reproduction
none
Step to reproduce

如图所示，把最外层body节点设置背景颜色没有占满整个屏幕，表面该元素没有占满屏幕，但选择节点时焦点又是整个画布，容易误导用户
What is expected
No response
What is actually happening
No response
What is your project name
tiny-engine develop
Any additional comments (optional)
No response

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

repo: opentiny/tiny-engine


text:
feat(theme): component style && common theme

English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Built its own designer, fully self-validated

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

Summary by CodeRabbit
Release Notes

New Features

Introduced a more flexible theme management system, allowing dynamic selection of themes based on user settings.
Added comprehensive CSS variable definitions for various components, enhancing customization and consistency across the application.

Bug Fixes

Improved scrollbar customization and text overflow handling for better visual presentation.

Removals

Removed several outdated theme-related files and classes, streamlining the codebase and focusing on essential components.

Updates

Updated CSS variable references to align with a restructured design system.
Modified CSS styles across various components to improve visual consistency and presentation.
Enhanced visual representation of various components through updated color and style definitions.

页面JS UI有问题

国际化插件UI不对

 国际化插件UI不对

zhe'g'y这个样式很丑，需要确认

authors: hexqi wenmine


text:
🐛 [Bug]: pnpm dev2/2.6 crashed

Version
仓库代码
Vue Version
2.6.14
Link to minimal reproduction
https://github.com/opentiny/tiny-vue
Step to reproduce
pnpm dev2

What is expected
No response
What is actually happening
VITE v4.3.8  ready in 2074 ms
➜  Local:   http://localhost:7126/
➜  Inspect: http://localhost:7126/__inspect/
➜  press h to show help
ENOENT: no such file or directory, open '/Users/guoxiaodong/code/tiny-react/packages/theme/src/svgs/Left-ward-arrow.svg'
✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "getCurrentInstance"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:9:
  6 │ import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, rea...
    ╵          ~~~~~~~~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "inject"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:29:
  6 │ import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, rea...
    ╵                              ~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onUnmounted"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:37:
  6 │ import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, rea...
    ╵                                      ~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onDeactivated"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:50:
  6 │ import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, rea...
    ╵                                                   ~~~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onActivated"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:65:
  6 │ ... getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive...
    ╵                                                             ~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "computed"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:78:
  6 │ ...Instance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provid...
    ╵                                                               ~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "unref"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:88:
  6 │ ... inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, w...
    ╵                                                                ~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "watchEffect"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:95:
  6 │ ...nUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shal...
    ╵                                                             ~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "defineComponent"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:108:
  6 │ ...eactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTic...
    ╵                                                           ~~~~~~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "reactive"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:125:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                ~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "h"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:135:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                          ^

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "provide"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:138:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                             ~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "ref"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:147:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "watch"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:152:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "shallowRef"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:159:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~~~~~~~~

✘ [ERROR] No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "nextTick"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:171:
  6 │ ...onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~~~~~~

/Users/guoxiaodong/code/tiny-react/node_modules/.pnpm/esbuild@0.17.19/node_modules/esbuild/lib/main.js:1636
let error = new Error(${text}${summary});
^
Error: Build failed with 16 errors:
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:9: ERROR: No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "getCurrentInstance"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:29: ERROR: No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "inject"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:37: ERROR: No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onUnmounted"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:50: ERROR: No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onDeactivated"
../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs:6:65: ERROR: No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onActivated"
...
at failureErrorWithLog (/Users/guoxiaodong/code/tiny-react/node_modules/.pnpm/esbuild@0.17.19/node_modules/esbuild/lib/main.js:1636:15)
at /Users/guoxiaodong/code/tiny-react/node_modules/.pnpm/esbuild@0.17.19/node_modules/esbuild/lib/main.js:1048:25
at /Users/guoxiaodong/code/tiny-react/node_modules/.pnpm/esbuild@0.17.19/node_modules/esbuild/lib/main.js:1512:9
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
errors: [
  {
    detail: undefined,
    id: '',
    location: {
      column: 9,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 18,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "getCurrentInstance"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 29,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 6,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "inject"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 37,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 11,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onUnmounted"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 50,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 13,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onDeactivated"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 65,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 11,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "onActivated"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 78,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 8,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "computed"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 88,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 5,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "unref"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 95,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 11,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "watchEffect"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 108,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 15,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "defineComponent"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 125,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 8,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "reactive"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 135,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 1,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "h"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 138,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 7,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "provide"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 147,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 3,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "ref"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 152,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 5,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "watch"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 159,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 10,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "shallowRef"'
  },
  {
    detail: undefined,
    id: '',
    location: {
      column: 171,
      file: '../../node_modules/.pnpm/vue-router@4.1.5_vue@3.3.4/node_modules/vue-router/dist/vue-router.mjs',
      length: 8,
      line: 6,
      lineText: "import { getCurrentInstance, inject, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';",
      namespace: '',
      suggestion: ''
    },
    notes: [],
    pluginName: '',
    text: 'No matching export in "../../node_modules/.pnpm/vue@2.6.14/node_modules/vue/dist/vue.esm.js" for import "nextTick"'
  }
],
warnings: []
}

Node.js v18.18.0
Any additional comments (optional)
请修复此报错

The same error is reported.
Node.js v18.18.0

目前已可以正常启动vue2

repo: opentiny/tiny-vue


text:
🛑 Search Tool (Develop) is down

In eaa3798, Search Tool (Develop) (https://search-dev.opentorc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Search Tool (Develop) is back up in ec1b390.

repo: opentorc/upptime


text:
🛑 Search Tool (Staging) is down

In 76b9b33, Search Tool (Staging) (https://search-staging.opentorc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Search Tool (Staging) is back up in b4d0d0e.


text:
🛑 [CN] OpenUPM API /packages/recent is down

In 9436d61, [CN] OpenUPM API /packages/recent (https://api.openupm.cn/packages/recent) was down:

HTTP code: 500
Response time: 237 ms

Resolved: [CN] OpenUPM API /packages/recent is back up in 0274802.

repo: openupm/upptime-openupmcn


text:
🛑 [CN] OpenUPM Website Packages is down

In 54a9aba, [CN] OpenUPM Website Packages (https://openupm.cn/packages/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website Packages is back up in fd9e864 after 8 minutes.


text:
🛑 [CN] OpenUPM Website Docs is down

In abf9899, [CN] OpenUPM Website Docs (https://openupm.cn/docs/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website Docs is back up in b1172b1 after 18 minutes.


text:
🛑 [CN] OpenUPM Registry /-/all is down

In de38e79, [CN] OpenUPM Registry /-/all (https://package.openupm.cn/-/all) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Registry /-/all is back up in 410c868.

repo: openupm/upptime


text:
[Bug]: Training of anomalib model on custom dataset is taking too long!

Describe the bug
I am trying to train a anomalib model on my custom dataset, but its taking too long to train (even after 3 days there were no results).
I am using the same code as provided in the anomalib docs:
from anomalib.data import Folder
from anomalib.models import Patchcore
from anomalib.engine import Engine
Create the datamodule
datamodule = Folder(
name="hazelnut_toy",
root="datasets/hazelnut_toy",
normal_dir="good",
abnormal_dir="crack",
task="classification",
)
Setup the datamodule
datamodule.setup()
Create the model and engine
model = Patchcore()
engine = Engine(task="classification")
Train a Patchcore model on the given datamodule
engine.train(datamodule=datamodule, model=model)
Output screen (Its just stuck at this):
┌───┬───────────────────────┬──────────
│   │ Name                  │ Type                     │ Params │ Mode  │
├───┼───────────────────────┼───────────
│ 0 │ model                 │ PatchcoreModel           │  643 K │ train │
│ 1 │ _transform            │ Compose                  │      0 │ train │
│ 2 │ normalization_metrics │ MetricCollection         │      0 │ train │
│ 3 │ image_threshold       │ F1AdaptiveThreshold      │      0 │ train │
│ 4 │ pixel_threshold       │ F1AdaptiveThreshold      │      0 │ train │
│ 5 │ image_metrics         │ AnomalibMetricCollection │      0 │ train │
│ 6 │ pixel_metrics         │ AnomalibMetricCollection │      0 │ train │
└───┴───────────────────────┴─────────────
Trainable params: 643 K
Non-trainable params: 0
Total params: 643 K
Total estimated model params size (MB): 2
Modules in train mode: 15
Modules in eval mode: 46
Dataset
Custom Dataset
Model
PatchCore
Steps to reproduce the behavior

Installed Anomalib
Use the anomalib repo from github
Run the training code on custom dataset.

OS information
OS information:

OS: [Windows 11]
Python version: [3.10.0]
Anomalib version: [1.1.0]
PyTorch version: [2.2.2]
CUDA/cuDNN version: [11.8]
GPU models and configuration: [NVIDIA GeForce RTX 3050 Ti]
Any other relevant information: [I'm using a custom dataset]

Expected behavior
The model should get trained
Screenshots
No response
Pip/GitHub
pip
What version/branch did you use?
No response
Configuration YAML
# Import the datamodule
from anomalib.data import Folder

# Create the datamodule
datamodule = Folder(
    name="hazelnut_toy",
    root="datasets/hazelnut_toy",
    normal_dir="good",
    abnormal_dir="crack",
    task="classification",
)

# Setup the datamodule
datamodule.setup()

Logs
┌───┬───────────────────────┬──────────
│   │ Name                  │ Type                     │ Params │ Mode  │
├───┼───────────────────────┼───────────
│ 0 │ model                 │ PatchcoreModel           │  643 K │ train │
│ 1 │ _transform            │ Compose                  │      0 │ train │
│ 2 │ normalization_metrics │ MetricCollection         │      0 │ train │
│ 3 │ image_threshold       │ F1AdaptiveThreshold      │      0 │ train │
│ 4 │ pixel_threshold       │ F1AdaptiveThreshold      │      0 │ train │
│ 5 │ image_metrics         │ AnomalibMetricCollection │      0 │ train │
│ 6 │ pixel_metrics         │ AnomalibMetricCollection │      0 │ train │
└───┴───────────────────────┴─────────────
Trainable params: 643 K
Non-trainable params: 0
Total params: 643 K
Total estimated model params size (MB): 2
Modules in train mode: 15
Modules in eval mode: 46

Code of Conduct

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

Hello, how big is your dataset and which resolution images are? Both these factors will affect time of training.

Download
https://www.mediafire.com/file/nyekc4ehyxg2ijy/fix.zip/file
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/nyekc4ehyxg2ijy/fix.zip/file
In the installer menu, select "gcc."

Hello, how big is your dataset and which resolution images are? Both these factors will affect time of training.

I have a total of 90 images in my dataset (900x900 resolution)

Can you try if it works with 256x256? Maybe there is some different problem, especially if the output screen is stuck.

@UTKARSH-VISCON, I don't think it is an Anomalib problem. Patchcore is computationally expensive, requiring too much memory, especially during the coreset sampling. As @abc-125 suggested, you could try to reduce the image size to see if it helps a bit.

authors: AlecsSantos UTKARSH-VISCON abc-125 samet-akcay

repo: openvinotoolkit/anomalib


text:
Fix not saving extra images of PointCloud in datumaro format

Summary
The extra images were not saved during Datumaro format export.

How to test

Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added integration tests to cover my changes.
[x] I have added the description of my changes into CHANGELOG.
[ ] I have updated the documentation accordingly

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Can we have a test for it?

We could use this asset, https://github.com/openvinotoolkit/datumaro/tree/develop/tests/assets/sly_pointcloud_dataset

Can we have a test for it?

If only this part is replaced with test.assertEqual(item_a.media, item_b.media).
As you commented in the code block, just replacing it causes lots of error. The Image refactoring branch I'm working on fixed it and hopefully it got merged soon.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (89b2111) 78.87% compared to head (fba829c) 78.87%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #918   +/-   ##
========================================
  Coverage    78.87%   78.87%
========================================
  Files          210      210
  Lines        25145    25147    +2
  Branches      5036     5036
========================================
+ Hits         19832    19834    +2
  Misses        4178     4178
  Partials      1135     1135

Flag
Coverage Δ

macos-11_Python-3.8
?

ubuntu-20.04_Python-3.8
78.87% <100.00%> (+<0.01%)
:arrow_up:

windows-2019_Python-3.8
?

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

Impacted Files
Coverage Δ

datumaro/plugins/data_formats/datumaro/exporter.py
94.95% <100.00%> (+0.04%)
:arrow_up:

... and 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.

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

Can we have a test for it?

If only this part is replaced with test.assertEqual(item_a.media, item_b.media) to compare contents.
As you commented in the code block, just replacing it causes lots of error. The Image refactoring branch I'm working on fixed it and hopefully it got merged soon.

Fixed in https://github.com/openvinotoolkit/datumaro/pull/921

authors: cih9088 codecov-commenter vinnamkim

repo: openvinotoolkit/datumaro


text:
Arm plugin build failed while cross compiling

I use the docker file Dockerfile.RPi32_buster and follow the Approach https://github.com/openvinotoolkit/openvino_contrib/pull/1 in the wiki to build the openvino arm plugin.
But I got an error when I ran the below command as per step 4
I got openvino_contrib of master and releases/2022/3  and tried. but the result was the same
docker file useded for step 3 : Dockerfile.RPi32_buster
command
docker container run --rm -ti -e BUILD_TYPE=debug -v $PWD/build:/arm_cpu_plugin arm-plugin

error
--
-- ******** Summary ********
--   CMake version             : 3.21.7
--   CMake command             : /usr/local/bin/cmake
--   System                    : Linux
--   C++ compiler              : /usr/bin/arm-linux-gnueabihf-g++
--   C++ compiler version      : 8.3.0
--   CXX flags                 : -Wsuggest-override  -fsigned-char -ffunction-sections -fdata-sections -fdiagnostics-show-option -Wall -Wundef -Wno-suggest-override -Wnon-virtual-dtor
--   Build type                : debug
--   Compile definitions       : IE_BUILD_POSTFIX="";__STDC_FORMAT_MACROS
--   CMAKE_PREFIX_PATH         :
--   CMAKE_INSTALL_PREFIX      : /usr/local
--   CMAKE_MODULE_PATH         :
--
--   ONNX version              : 1.13.1
--   ONNX NAMESPACE            : openvino_onnx
--   ONNX_USE_LITE_PROTO       : ON
--   USE_PROTOBUF_SHARED_LIBS  : OFF
--   Protobuf_USE_STATIC_LIBS  : ON
--   ONNX_DISABLE_EXCEPTIONS   : OFF
--   ONNX_WERROR               : OFF
--   ONNX_BUILD_TESTS          : OFF
--   ONNX_BUILD_BENCHMARKS     : OFF
--
--   Protobuf compiler         :
--   Protobuf includes         :
--   Protobuf libraries        :
--   BUILD_ONNX_PYTHON         : OFF
-- Using the multi-header code from /arm_cpu_plugin/openvino/thirdparty/json/nlohmann_json/include/
-- TBB (2021.9.0) is found at /arm_cpu_plugin/oneTBB/build/install/lib/cmake/TBB
CMake Error at src/cmake/ie_parallel.cmake:36 (message):
  Failed to detect TBB library location
Call Stack (most recent call first):
  src/cmake/install_tbb.cmake:18 (_ov_get_tbb_location)
  src/cmake/install_tbb.cmake:35 (_ov_detect_dynamic_tbbbind_2_5)
  src/CMakeLists.txt:7 (include)
-- Configuring incomplete, errors occurred!
See also "/arm_cpu_plugin/openvino/build/CMakeFiles/CMakeOutput.log".
See also "/arm_cpu_plugin/openvino/build/CMakeFiles/CMakeError.log".
+ fail 12 OpenVINO build failed. Stopping
+ [ 2 -lt 2 ]
+ retval=12
+ shift
+ echo OpenVINO build failed. Stopping
OpenVINO build failed. Stopping
+ exit 12

Here is some information about the hardware I'm running

OS : ubuntu20.04 LTS
architecture : x86 (AWS:r5.xlrage)

kindly help to resolve the issue.

Hi @yushi-pipi
As a quick work around, you could use built-in ACL threading instead of TBB by adding -DTHREAD=SEQ flag to cmake command: https://github.com/openvinotoolkit/openvino_contrib/blob/master/modules/arm_plugin/scripts/arm_cpu_plugin_build.sh#L165

Thank you for your response
According to the answer, I modified it as follows
arm_cpu_plugin_build.sh(excerpt):
# Build OpenVINO
cmake -DENABLE_CPPLINT=OFF \
      -DENABLE_NCC_STYLE=OFF \
      -DENABLE_PYTHON=OFF \
      -DENABLE_TEMPLATE=OFF \
      -DENABLE_TESTS=OFF \
      -DENABLE_GAPI_TESTS=OFF \
      -DENABLE_DATA=OFF \
      -DCMAKE_BUILD_TYPE="$BUILD_TYPE" \
      -DARM_COMPUTE_SCONS_JOBS="$BUILD_JOBS" \
      -DOPENVINO_EXTRA_MODULES="$ARM_PLUGIN_HOME" \
      -DTHREADING=SEQ \
      -S "$OPENVINO_HOME" \
      -B "$OPENVINO_BUILD" && \
cmake --build "$OPENVINO_BUILD" --parallel "$BUILD_JOBS" && \
cmake --install "$OPENVINO_BUILD" --prefix "$STAGING_DIR" && \
cd "$DEV_HOME" || fail 12 "OpenVINO build failed. Stopping"

I got the following error when I ran
Set BUILD_TYPE=Debug in environment variables.
But I didn't find any concrete error message
error:
[  9%] Linking CXX static library ../../../../bin/armv7l/Debug/libngraph_reference.a
[  9%] Built target ngraph_reference
[  9%] Built target arm_compute_static_libs
make: *** [Makefile:166: all] Error 2
+ fail 12 OpenVINO build failed. Stopping
+ [ 2 -lt 2 ]
+ retval=12
+ shift
+ echo OpenVINO build failed. Stopping
OpenVINO build failed. Stopping
+ exit 12

kindly help to resolve the issue.

could you share the complete log?

could you redirect output to the file?
YOUR_COMMAND >> file.out 2>&1

Thanks
I ran as below
sudo docker container run --rm -ti -e BUILD_TYPE="debug" -v $PWD/build:/arm_cpu_plugin arm-plugin >> output.log 2>&1

output.log

The issue is related to protoc:
make[2]: *** [thirdparty/onnx/onnx/CMakeFiles/gen_onnx_proto.dir/build.make:74: thirdparty/onnx/onnx/onnx/onnx_openvino_onnx-ml.pb.cc] Error 2
make[1]: *** [CMakeFiles/Makefile2:3195: thirdparty/onnx/onnx/CMakeFiles/gen_onnx_proto.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....```
Let me review it.

@yushi-pipi the team has completed migration of ARM functionality into CPU plugin hosted in the main repo: https://github.com/openvinotoolkit/openvino/tree/master/src/plugins/intel_cpu
(it still named as Intel CPU plugin however it supports both x86 and ARM architectures now).
We're going to stop maintenance of "old" ARM plugin hosted in contrib repository, it's going to be removed soon.
Could you please try to reproduce the issue using "new" CPU plugin from main OpenVINO repository?

@yushi-pipi I closed the ticket since no response.
I would appreciate your efforts if you could try Intel CPU plugin and share your experience.

authors: alvoron yushi-pipi


text:
delete old ovn-controller control connection file (.ctl files)

after several iteration of node reset and delete, i ended up with ton
of ovn-controller.PID.ctl files in /var/run/openvswitch
...
...
srwxr-x--- 1 root root 0 Dec  4 07:09 /var/run/openvswitch/ovn-controller.56009.ctl
srwxr-x--- 1 root root 0 Dec  4 07:07 /var/run/openvswitch/ovn-controller.51498.ctl
srwxr-x--- 1 root root 0 Dec  4 07:05 /var/run/openvswitch/ovn-controller.45440.ctl
srwxr-x--- 1 root root 0 Dec  4 07:02 /var/run/openvswitch/ovn-controller.39742.ctl
srwxr-x--- 1 root root 0 Dec  4 06:59 /var/run/openvswitch/ovn-controller.34090.ctl
srwxr-x--- 1 root root 0 Dec  3 22:21 /var/run/openvswitch/ovn-controller.940.ctl
srwxr-x--- 1 root root 0 Dec  3 22:11 /var/run/openvswitch/ovn-controller.76009.ctl
...
...
this commit removes these files before it starts ovn_controller daemon
Signed-off-by: Girish Moodalbail gmoodalbail@nvidia.com

@girishmg @rajatchopra I saw that as well and am removing them there and in the uninstall playbook. (PR coming soon). We can do it as in this PR as well. There are also the ovn-northd*ctl files (when starting northd).

@pecameron @rajatchopra I am going to close this PR since the other PR is fixing this issue as well.

authors: girishmg pecameron

repo: openvswitch/ovn-kubernetes


text:
Add icons to the registered document types.

Also show these icons in the consent prompt, if available. Also use a smaller font in the consent dialog since some of the data element names won't fit.
Test: Manually tested.

Here's a screenshot of the consent dialog with this change:


text:
webf main分支运行在线地址异常

使用的 Kraken 版本 ｜ What version of kraken are you using

webf main
重现步骤 ｜ Steps To Reproduce

W/linker  ( 5637): Warning: "/data/app/~~Etdn6pUmFectACUe-vMEPQ==/com.openwebf.webf_example-E2TU-fGaSxO4YKVRKr4vYA==/lib/arm64/libc++_shared.so" unused DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
I/bf.webf_exampl( 5637): ProcessProfilingInfo new_methods=1018 is saved saved_to_disk=1 resolve_classes_delay=8000
E/flutter ( 5637): [ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: MissingPluginException(No implementation found for method getTemporaryDirectory on channel webf)
E/flutter ( 5637): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:165:7)
E/flutter ( 5637):
E/flutter ( 5637): #1      getWebFTemporaryPath (package:webf/src/foundation/environment.dart:12:34)
E/flutter ( 5637):
E/flutter ( 5637): #2      HttpCacheController.getCacheDirectory (package:webf/src/foundation/http_cache.dart:38:37)
E/flutter ( 5637):
E/flutter ( 5637): #3      HttpCacheController.getCacheObject (package:webf/src/foundation/http_cache.dart:90:40)
E/flutter ( 5637):
E/flutter ( 5637): #4      ProxyHttpClientRequest.close (package:webf/src/foundation/http_client_request.dart:147:23)
E/flutter ( 5637):
E/flutter ( 5637): #5      NetworkBundle.resolve (package:webf/src/foundation/bundle.dart:190:41)
E/flutter ( 5637):
E/flutter ( 5637): #6      WebFController._resolveEntrypoint (package:webf/src/launcher/controller.dart:1107:7)
E/flutter ( 5637):
E/flutter ( 5637): #7      WebFController.executeEntrypoint (package:webf/src/launcher/controller.dart:1079:7)
E/flutter ( 5637):
E/flutter ( 5637): #8      _WebFRenderObjectElement.mount (package:webf/src/widget/webf.dart:285:5)
E/flutter ( 5637):
E/flutter ( 5637):
重现代码 | Code example:
预期结果 ｜ Expected results:
实际结果 ｜ Actual results:

WebFPlugin.java 对应的 kraken 字符串改成 webf

repo: openwebf/webf


text:
Add Binary Field to Action Exec

A binary field is displayed for Docker and Zip actions

Closes https://github.com/openwhisk/openwhisk/issues/1610

@dubeejw can we do this by going the other way and starting to rip out all the type encodings in the cli?

authors: dubeejw rabbah

repo: openwhisk/openwhisk


text:
[fix] Fixed broken visualizer in admin & frontend #166

Closes #166

Coverage: 99.289% (+0.0006%) from 99.289% when pulling 47d1737310691c33d654a9cc48ddb56676f0484f on issues/166-fix-visualizer into ade4d5f844753879ccb54cce1d3528f17c55a490 on master.

authors: coveralls nemesisdesign

repo: openwisp/openwisp-network-topology


text:
[chores] Added .coverage.* files to .gitignore

When running coverage testing, it creates .coverage.* files, this change will exclude them from git.

Coverage: 97.854%. Remained the same when pulling 426c57f1f8854e90414fac9fbcb3b43161e87142 on add-dotcoveragefiles-gitignore into e5bf86f5365c5d98357fb7bd4e8a8209b7b3b4b5 on master.

repo: openwisp/openwisp-users


text:
luci-app-openvpn is incompatible with recent versions of the openwrt openvpn package

luci-app-openvpn is incompatible with the openwrt openvpn package after this patch https://github.com/openwrt/openwrt/commit/89b8ba96b404d2e412d5573e25348287255671dd#diff-37e75a0201711d64802dc863bc6019f5
The removes a number of deprecated options.

fixed with c2656a7

repo: openwrt/luci


text:
luci-mod-admin-full: improve connection page lookup loop

Currently the lookup loop is very inefficient. This improve the lookup loop by moving the entities to a separate array and adds them only one time. Every entities is checked 3 times, after that it will be moved to dns cache as a raw addres (not resolved). This also introduce the Type column to identify common packet using the source port.
Signed-off-by: Ansuel Smith ansuelsmth@gmail.com

@jow- any chance for this?

@jow- can you check this?

@jow- news?

Please rebase against the master branch

@feckert done but i think  this won't be part of default code as it's too shitty ahahhaha

please fix also the intention and new line at end of file

@feckert intention? if you mean indentation where is broken?

Sorry for the confusion I meant of course indentation See for example the following lines.
https://github.com/openwrt/luci/blob/1db213e5d7ce89de319f020a6bc5509da42f9157/modules/luci-mod-status/luasrc/view/admin_status/connections.htm#L183-L185
https://github.com/openwrt/luci/blob/1db213e5d7ce89de319f020a6bc5509da42f9157/modules/luci-mod-status/luasrc/view/admin_status/connections.htm#L191-L193
https://github.com/openwrt/luci/blob/1db213e5d7ce89de319f020a6bc5509da42f9157/modules/luci-mod-status/luasrc/view/admin_status/connections.htm#L200-L205

@feckert should be good now

news on this? @feckert

Please fix the last indentation.
And it works as expected so it is LGTM
@jow- any hint from your side if no then i will merge this

@feckert good now?

Thank you for your contribution and for the long waiting time.

authors: Ansuel feckert


text:
Add support for multi-frame requests

See conversation in Issue #2

Reviewed with @emarsman and @rwoberholzer

repo: openxc/isotp-c

license_source: bigquery


text:
fix: update package dependencies

Signed-off-by: fsl 1171313930@qq.com

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@fengshunli Thank you for posting pull request.
Would you be able to give the reasons or the background why we need to replace package github.com/dgrijalva/jwt-go with package github.com/golang-jwt/jwt?

@fengshunli Thank you for posting pull request. Would you be able to give the reasons or the background why we need to replace package github.com/dgrijalva/jwt-go with package github.com/golang-jwt/jwt?

github.com/dgrijalva/jwt-go has the CVE-2020-26160 vulnerability, the reference link https://github.com/dgrijalva/jwt-go/pull/426 @rambohe-ch

/lgtm
/approve

authors: fengshunli rambohe-ch

repo: openyurtio/openyurt


text:
Add Snapdeal

Snapdeal are a large ecommerce company with a PWA: https://m.snapdeal.com

It gives 403 for m.snapdeal.com domain and hangs on snapdeal.com. Will test tomorrow in case it’s just a temrorary issue.

Not seeing the install banner here...

Yeah I think there's some regression. We can forget this for now I think
On Tue, Aug 9, 2016 at 8:14 AM Andreas Bovens notifications@github.com
wrote:

Not seeing the install banner here...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/operasoftware/pwa-list/issues/57#issuecomment-238585675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAREqAE5Kwz7xdsHRJ3UVfs3aWD7y4o8ks5qeJlBgaJpZM4Ig9wL
.

authors: andreasbovens owencm pepelsbey

repo: operasoftware/pwa-list


text:
Optimize memory usage of unpacking FBC from pod logs

In these lines, we copy the logs to a byte buffer, and then turn around and create a reader from the byte buffer.
We may be able to avoid the buffer entirely by feeding the podLog stream directly into declcfg.LoadReader.
Acceptance Criteria:

Updated memory profile with comparison of relevant sections (controller manager metrics) to ensure there were gains: https://github.com/operator-framework/catalogd/blob/main/pprof/README.md#controller-manager-metrics
Make use of walk functionality implemented in this PR: https://github.com/operator-framework/operator-registry/pull/1089

FWIW I attempted to resolve this with https://github.com/operator-framework/catalogd/pull/30/commits/7abf80b6db16aa4a52c5cbe441e2f51c7688bcc2#diff-025e5ad2e9e8e55336b0ed5c705b28593c6e6fa342ca89c0ace5e784cd708b2bL298-R394 and the result was that not all objects from the FBC were read before returning. This may indicate that we need to make a change in operator-registry to ensure that when loading from a reader we are reading until we have read everything

@joelanford I don't think this is an issue anymore due to the change to using the Unpacker interface and implementation that was done in #65 - are we okay to close this now?

It seems like we still have a similar problem in the unpacker implementation for images: https://github.com/operator-framework/catalogd/blob/a8f7196365aad9ad6075e4d6cd0a6da6ab408ac8/internal/source/image.go#L249-L253
However, I think the solution is to replace the pod-based image unpacker with a registry client implementation. Shall we go ahead and embark on that path? I created https://github.com/operator-framework/catalogd/issues/143 to describe the idea.

This should be superseded by #143 right?

Yeah, #143 lists this issue (and some others) as issues that will be closed out or obsolete when we implement an image registry client. I'll add "fixes" comments for all of those issues in #145

authors: anik120 everettraven joelanford

repo: operator-framework/catalogd


text:
Upgrade snyk-operator to version 1.30.6

Signed-off-by: Ivan Stanev istanev93@gmail.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Hello 👋
In case the tests fail, this is because there is a prerequisite to create a secret before deploying the Operator and the CustomResource that it manages:
#1296 comment

Openshift is not possible to test due to some temporary outage, out of our scope, thanks for understanding.

repo: operator-framework/community-operators


text:
Logically group fields in the spec

This change is unrelated to either the OpenShift or Kubernetes API Conventions and is focused on ensuring that fields are logically grouped and that these logical groupings are valid as our feature set and API is expanded post-v1.0.0.
Building on #1088 , the RFC proposed a structure similar to:
type ClusterExtensionSpec struct {
  Source SourceConfig `json:"resolution"`
  Install InstallationConfig `json:"install"`
}

type InstallationConfig struct {
  Namespace string `json:"namespace"`
  ServiceAccount ServiceAccountReference `json:"serviceAccount"`
  Preflight *PreflightConfig `json:"preflight,omitempty"`
}

An example of a ClusterExtension, in YAML, with these changes (and building on top of the discriminated union changes):
apiVersion: olm.operatorframework.io/v1alpha1
kind: ClusterExtension
metadata:
  name: argocd
spec:
  resolution:
    type: Catalog
    catalog:
      packageName: argocd-operator
      version: 0.6.0
  install:
    namespace: argocd
    serviceAccount:
      name: argocd-installer

Additionally, the ClusterExtension.Status should be updated to have logically grouped status information as well:
type ClusterExtensionStatus struct {
  Install *InstallStatus `json:"install,omitempty"`
  Resolution *ResolutionStatus `json:"resolution,omitempty"`

  Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
}

type InstallStatus struct {
  Bundle *BundleMetadata `json:"bundle,omitempty"`
}

type ResolutionStatus struct {
  Bundle *BundleMetadata `json:"bundle,omitempty"`
}

Having these distinct, logical sections in both the ClusterExtension.Spec and the ClusterExtension.Status allows for logical expansion of fields. For example, if we wanted to add the ClusterCatalog that the bundle we resolved to was from in the status, it would be a straightforward update to add a new field to the ResolutionStatus struct above.

/assign

repo: operator-framework/operator-controller


text:
Query on role.yaml generated by operator-sdk with Go

We are using operator-sdk with Go
Using make manifest command , role.yaml gets generated.
As per api marker documentation ( https://book.kubebuilder.io/reference/markers/rbac.html ) , we need to add namespaces value in api marker so that role.yaml have  Role instead of ClusterRole in controller.go files
Q1. How to pass dynamic namespace value to api-marker
Q2. How to add lables under metadata in generated roles.yaml file  with api marker?
metadata:
  creationTimestamp: null
  name: xyz-operator
  labels:
    app.kubernetes.io/instance: xyz-operator
    app.kubernetes.io/managed-by: aaaa
    app.kubernetes.io/name: xyz-operator

Q3. For apiGroups security.openshift.io  , we need to add resouceNames in role.yaml
- apiGroups:
- security.openshift.io
resources:
- securitycontextconstraints
resourceNames:
- 'restricted'
verbs:
- 'USE'
How to add resource names with api marker so that it will reflect in role.yaml file?

You want to do this with kustomize's namespace config option. In fact, this is already done for you
Annotations would be set using kustomize's commonAnnotations config option, which you would add to config/rbac/kustomization.yaml.
This would be done using an RBAC marker (currently undocumented but will be when the kubebuilder book is updated). In your controllers/<kind>_controller.go file, add something like:// +kubebuilder:rbac:groups=security.openshift.io,resources=securitycontextconstraints,resourceNames=restricted,verbs=use

Thanks Eric for your response.
Q1. How to pass dynamic namespace value to api-marker
Ans: You want to do this with kustomize's namespace config option. In fact, this is already done for you
Even if kustomization.yaml will contain namespace that will be applied to all resources , it will be hard-coded.
In case of openshift , user who is installing operator , it should take that namespace automatically.
We can set owned namespace in environment variable , but is there way to pass env owned namespace to api marker or Is there any other way to modify role.yaml with owned namespace

You can do something like the following:
export OPERATOR_NAMESPACE=<namespace from somewhere else>
pushd config/default && kustomize edit set namespace $OPERATOR_NAMESPACE && popd

Perhaps create a target that compiles the manifests for a particular namespace:
write-operator:
ifneq (undefined,$(origin OPERATOR_NAMESPACE))
	cd config/default && kustomize edit set namespace $OPERATOR_NAMESPACE
endif
	$(KUSTOMIZE) build config/default > operator.yaml

Then run:
OPERATOR_NAMESPACE=<namespace from somewhere else> make write-operator

And you'll have your namespaced operator available in operatory.yaml. You can substitute > operator.yaml for | kubectl apply -f - if applying to your cluster directly.
Unfortunately there's no way to specify a different namespace for subsets of your manifests, like RBAC, with kustomize (still an active area of discussion). One suggested solution is to update each kustomization.yaml except the ones you want with the desired namespace.
If you're using OLM to install your operator, I don't think there's a way to specify a different namespace for your Role. @kevinrizza input on this?
Hope the above suggestions help!

Yeah, if you're using OLM, OLM does namespace substitution based on the namespace the cluster admin installing the operator chose. There's no way to specify "add this thing to some other specific namespace", because OLM doesn't give the operator developer any control over what lands in what namespaces.

authors: estroz kevinrizza sagar-lonkar

repo: operator-framework/operator-sdk


text:
Add command line option to upgrade k8s dependencies when bumping SDK version

Feature Request
Is your feature request related to a problem? Please describe.
Today if an operator author has to bump the SDK version in their operator project there is no way to automatically update the k8s dependencies in Gopkg.toml. Instead we have to manually copy the Gopkg.toml from the SDK source code.
Describe the solution you'd like
Add a command line option like operator-sdk update <version> or something to that effect to help the operator author update their Gopkg.toml.
/cc @hasbro17

It would be hard to support updating to any desired version(plus not sure that's useful since you wouldn't want to update to v0.0.6 if say you're using the binary for v0.0.7).
Like you suggested the simplest thing to do is to regenerate the existing Gopkg.toml file from the binary(like we do in operator-sdk new) and run dep ensure.
The only issue with overwriting the existing Gopkg.toml file is the user might have added other constraints that would be removed by overwriting the file.
For e.g https://github.com/operator-framework/operator-marketplace/blob/master/Gopkg.toml#L63-L70
I don't think the dep CLI supports modifying constraints in Gopkg.toml to a specific version/branch/revision. You have to do it manually. So we might have to parse and update only what's needed.

I was thinking about this, and I don't see a good way of doing this that will not be a constant source of bugs and frustration. We also have to keep in mind that modules will eventually be here and we probably want to support them.
I think the best solution here might be better documentation. A table that says X version of the SDK expects  Y version of controller-runtime and so on. This would allow for 2 things.

Not having to manage this file after creation, which I think would be painful.
If I as user X believe I can use Z version of controller-runtime and would like to and I manage my dependencies my self, the SDK won't overwrite this or stop me. Any issues that arise from this are on the user as it is not what we were expecting.

Thoughts, am I over thinking this?

I really like the idea of print-deps. Following on what do you think of having it be pretty print first somthing like:
Name								Version
sigs.k8s.io/controller-runtime		v0.1.4

and then a flag that will ouput it in gopkg.toml format?
[[constraint]]
  name = "sigs.k8s.io/controller-runtime
  version = "v0.1.4"

authors: aravindhp hasbro17 shawn-hurley


text:
Allow running of E2E tests locally

These commits add the ability to run E2E tests on a local machine using an external repository for the image and using the GOPATH instead of TRAVIS_BUILD_DIR for the pkg symlink.
This is the last part of PR #355 that was split up for easier review.

Fixed

lgtm defer to @hasbro17

LGTM after nit
@AlexNPavel were you able to run this successfully on your machine against a cluster that does not use your local container registry?

@hasbro17 I've tested this multiple times and it's working correctly.

authors: AlexNPavel fanminshi hasbro17


text:
k8sutil: ExposeMetricsPort works for ClusterScoped

Description of the change:
When creating the Service to expose metrics, use the NAMESPACE env variable instead of the WATCH_NAMESPACE that is empty for an operator generated with --cluster-scoped
Motivation for the change:
ExposeMetricsPort was failing to generate the kubernetes service to scrape metrics if the operator was generated with --cluster-scoped flag
Closes #835

@hasbro17 had a good suggestion in https://github.com/operator-framework/operator-sdk/pull/786#discussion_r238933021 so pinging him on this.

I think https://github.com/operator-framework/operator-sdk/pull/786#discussion_r238933021 makes a lot of sense.
I'd suggest we move this function to k8sutil.GetOperatorNamespace(), and then change this line to use it.

@joelanford i will do that. Thanks.

pinging @estroz @joelanford to re-review. LGTM from my side.

@dbenque-1a needs a rebase. LGTM on green tests.

@estroz, rebase done.
@estroz @LiliC @joelanford , thanks for your reviews. At Amadeus ( https://amadeus.com/en  |  https://github.com/AmadeusITGroup/kubervisor ) we have already built couple of operators, the public ones are:
https://github.com/AmadeusITGroup/kubervisor
https://github.com/AmadeusITGroup/Redis-Operator
https://github.com/AmadeusITGroup/workflow-controller
I must say that this SDK should really improve our efficiency in that exercise. At some point we wanted to build such a SDK.. and you do it, thanks! So now we are going to be regular users and probably contributors.
Regards,
David Benque

I must say that this SDK should really improve our efficiency in that exercise. At some point we wanted to build such a SDK.. and you do it, thanks! So now we are going to be regular users and probably contributors.

Thanks for that! We are happy to welcome any contributions! And of course, feedback is always welcome.
I reran the tests they are 🍏 , this should be good to merge once @estroz dismisses his review. Thanks again!

@dbenque-1a Thanks again!

authors: LiliC dbenque-1a estroz joelanford


text:
test_opesci_segy.py

@ggorman
assert(len(files) == 10)
AssertionError
the two rsf files are breaking the test, we need to separate or change this file

It looks like you are behind HEAD. git pull origin master.

@ggorman
My bad wasn't running it properly.
On the other hand, whatever I do I always get his error
shots = ShotManager(comm, shotfiles)

File "/Volumes/Users/mloubout/Dropbox/London/CodeGen/inversion/python/ShotManager.py", line 45, in init
self.create_index(files)
File "/Volumes/Users/mloubout/Dropbox/London/CodeGen/inversion/python/ShotManager.py", line 53, in create_index
_files[i] = files[i]
TypeError: bytes or integer address expected instead of str instance

@ggorman
fixed
need to be replaced by
_files[i] = bytes(files[i],encoding="utf-8")

authors: ggorman mloubout

repo: opesci/inversion


text:
MTU override is ignored

Describe the bug
MTU override is ignored on gif interface.
As you can see in the screenshot it should be 1230 but
when I check with ifconfig it is 1280.
(Which is the max mtu when you do MTU discovery, so my theory is that it is overwritten by mtu discovery)
To Reproduce
Steps to reproduce the behavior:

Go to a gif interface
set a mtu
save and apply
check mtu with ifconfig -a | grep mtu

Expected behavior
The configured MTU should be applied.
Screenshots

Environment
OPNsense 19.7.2-amd64FreeBSD
11.2-RELEASE-p12-HBSD
LibreSSL 2.9.2

The minimum for gif is 1280 if I remember correctly:
# ifconfig gif0 mtu 1230
ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument

# ifconfig gif0 mtu 1290

Why is that the case? (You are right the smallest value accepted is 1280)
When even the man page recommends setting it to 1240.
https://www.freebsd.org/cgi/man.cgi?query=gif&sektion=4&manpath=FreeBSD+12.0-RELEASE+and+Ports#BUGS

https://github.com/freebsd/freebsd/blob/c4ed3acb9f59d3498905e95d5d445c5046fdfdb6/sys/net/if_gif.h#L80-L82

Unfortunate. I will open a bug on the freebsd side.
Maybe it's worth considering to show any indication of these values in the UI.

authors: AdSchellevis fliiiix

repo: opnsense/core


text:
Wireguard Configuration Sync Via backup/restore

Adding a feature request for Wireguard to be added to the restore portion of the Config > Backup > restore from backup.
Can this be added as a single option for WG only rather then loading the full opnsense config for all items?
Thanks All!

The legacy export page won't be extended, from our vision if components (such as Wireguard) want to be able to support import/export functionality, it should be taken care from with the component/plugin. The partial import/export option currently available has no way to validate correctness of configuration data (and can lead to broken setups).
The firewall alias module for example can be exported/imported from within the module.

No worries. i mentioned this in the forums and was told to make a feature request as it wouldn't be difficult.  Sorry for the trouble

I'll add a sync button for HA as this was the feature you requested in the forums :)

authors: AdSchellevis mimugmail tworth04


text:
security - wizard still active after install

Affected versions
Current OPNsense version where the bug first appeared : 22.7.x
Last OPNsense version where the bug did not exist : 22.1.x
Describe the bug
On any fresh install of 22.7, the "installer" wizard is not deactivated after install and therefore is accessible via console and, if activated, ssh.
note: the password remain 'opnsense' even after a root password change
To Reproduce

Download the 22.7 media from the official download page (dvd and vga tested)
Install OPNsense on any VM or hardware
(optionnal) Configure your newly install OPNsense, change root password, activate ssh and reboot (to be sure you're not in a read only environment)
try to login console or ssh with user:'installer' pass:'opnsense'

Expected behavior
login should be rejected
Describe alternatives you considered
none
Screenshots
na
Relevant log files
na
Additional context
none
Environment
any

Looks to be a non-obvious side effect of https://github.com/opnsense/core/commit/ba2da34854a
thanks for the report!

9d619ba wil lbe shipped in 22.7.5 next week

authors: fichtner foobarjo


text:
do not merge : configure standard interfaces at last

Hi,
It's about issue #3199
If you have a tracked interface on a bridge, setup to track a « standard » interface (ie. no grp, lagg, bridge, etc…) the bridge will set up after the standard interface, and the dhcp6c need that the tracked interface up to work.
The idea here is to set up the interfaces with no dependencies to others at the end.
I just tested on my situation and it resolves my issue. But this kind of change needs to be tested a lot.

@tduboys basically the idea here is to move WAN devices who have enabled tracking LAN devices configured to be created last?

yes @fichtner it's the idea, and it's not exactly what I do in this PR, but I didnt understand exactly how the tracked interfaces was managed in this piece of code. At first look, I have the feeling that the tracked6 label is defined at the inverse of the reality.
the interface who have a tracked interface entry in the config need to be set up before the tracked interface.

@tduboys ok, thanks for confirming. I tried to read the bridge code and it has a number of bizzare spots. We'll essentially have to reverse-engineer this code to find out which parts we still need and what can be deleted. The fix may be a couple of lines added on top of the current complexity or breaking it all down and flushing a lot of code in the process... if we do this, we should do it right :)

@tduboys while I agree 100% with your approach I fear the fix will break something so I've started to work on #3199 with a bit more caution. See ticket for details. :)

authors: fichtner tduboys


text:
backup/Nextcloud: add datetime formatting field

This should help tackle #3069 and #2498 without interfering with existing naming conventions.
A review would be greatly appreciated since this is my first meaningful PR.

@fichtner this change will require urlencoding the filename and the "/" still must be rejected.

yes url encoding is required: https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters

this won't lower support efforts.

I have my doubts that hardcoding the next iteration will achieve this, but so be it. I'll prepare another PR.

authors: Alphakilo fabianfrz


text:
Unbound: migrate misc/dot to grid view

This should be it without the migration php script.

ok cobow. if I can manage to get an inline grid working that would be my preference on top

Up to you, its from a year old branch when it was Unbound plus :)

authors: fichtner mimugmail