text:
Error adding ticket sales to building

URL
No response
How to reproduce the issue?
On the dev environment, this seems to have been resolved or does not seem to be an issue. I could not directly find the related change. If it exists, this issue can simply be linked to said change and be closed.

add a building (e.g. building=yes)
add the "ticket sales" preset.
throws some empty warnings with errors in the console and then blocks further interaction (mainly reselecting the object after canceling out.)
undo(, then go into and cancel out of the save menu) to regain the ability to interact with the object. (switching tabs shortly may also help if the undo/save button can't be interacted with)

Uncaught TypeError: Cannot read properties of undefined (reading 'en')
    at r.languageName (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:4:23922)
    at validationIssue.message (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:10:25116)
    at HTMLSpanElement.<anonymous> (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26:23533)
    at Selection.each_default [as each] (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2:19012)
    at o (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26:23506)
    at Selection.call_default [as call] (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2:18558)
    at a (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26:22621)
    at Selection.call_default [as call] (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2:18558)
    at l (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:19:4312)
    at Selection.call_default [as call] (id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2:18558)
r.languageName @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:4
message @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:10
(anonymous) @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26
each_default @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2
o @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26
call_default @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2
a @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26
call_default @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2
l @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:19
call_default @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2
n @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:19
call_default @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2
reRender @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:19
(anonymous) @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26
requestIdleCallback (async)
(anonymous) @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:26
call @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:38
(anonymous) @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:11
Promise.then (async)
d.validate @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:11
n.choose @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:23
(anonymous) @ id-072ff9dbedfd7c677e735e44abb42e92be82b1a975cc4d5b550daaf556f909e4.js:2

Screenshot(s) or anything else?

Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.25.2
Which browsers are you seeing this problem on?
Chrome

setting the area=yes preset then adding the building=yes tag.

Drawing an area, then adding the building=yes Building preset and finally adding the shop=ticket Ticketseller preset.

version of Chrome
2./3. Both are outdated, in this case. Chrome 109.0.5414.120 on Windows 7. I don't think either has much influence on one specific preset, however.

Works for me on Chrome 114.0.5735.199 on Windows 10. I tried with the osm.org locale set to nl to see if that had any impact.
Can you try updating Chrome? It would narrow down what the difference is.

This issue should now be fully redundant, as it's working for me.


text:
Remove Typo in core.yaml

straighted to straightened

@manfredbrandl Thanks for catching this!

source: gharchive/pull-request

authors: manfredbrandl quincylvania

repo: openstreetmap/iD

license: ISC

license_type: permissive

license_source: github-api


text:
[BUG] QuickOpen 多选框点击后会立即消失

描述你的问题（Describe the bug）

点击这里不仅没有选中，还会消失
复现路径（To Reproduce）

预期表现（Expected behavior）

问题截图（Screenshots）

环境信息（Environment）

OS: [e.g. macOS 11.2 Apple M1/Windows10/Windows11]
Browser [e.g. chrome, safari]
OpenSumi Version [e.g. 2.13.0]

补充信息（Additional context）

这个是怎么触发的呢？我已经装了 Java 插件了

这个是怎么触发的呢？我已经装了 Java 插件了

source action... -> generate constructors

给个代码示例吧

复现了

source: gharchive/issue

authors: Ricbet bytemain

repo: opensumi/core

license: MIT


text:
【bug】卸载插件后，activityBar的图标不会消失

没有修改任何代码，看了一下, 好像是 ide-extension-manager 里没有调用uninstall，

@xiadd 可以调试看一下，目前插件副作用的卸载依赖这里这段逻辑，如果没调用应该就不会有效果 https://github.com/opensumi/core/blob/b118fa495ecbd84b19fc2658b1664b25f394a852/packages/extension-manager/src/browser/vsx-extension.service.ts#L143

@xiadd   这个问题是出现在某个版本之后的吗？还是你的预期效果？

repo: opensumi/ide-startup


text:
Handling failed render in oc-client

So there is pretty much no way to tell that component failed to render for some reason, outside of error in console, but thats not really helpful.
The whole solution will be something like
// oc-client.js:382
oc.renderByHref($component.attr('href'), function(err, data){
    if(err || !data){
-      $component.html('');
+     $component
+         .attr('data-rendering', 'false')
+         .attr('data-rendered', 'false')
+         .html('');
+      oc.events.fire('oc:failed', { originalError: err, data: data });
        logger.error(err);
        return callback();
    }

    processHtml($component, data, callback);
});

@zoilorys sorry for the huge delay on answering to this.
I think your idea of firing a new event with the details is very good.
Would you be able to attempt a PR with this?
Thanks!

@zoilorys I like the idea.
FYI: we recently moved the oc-client-browser code in its own repo -> https://github.com/opencomponents/oc-client-browser/ would you like to attempt a PR there? Happy to help if you need anything to make this happen!

authors: matteofigus nickbalestra zoilorys

repo: opentable/oc

license: mit

license_source: bigquery


text:
are microRNAs in the genes' dictionary for text mining?

User at a workshop expected to see IBD associated with mir21 based on this paper https://www.nature.com/articles/ncomms13507.
No associations for mir21 at all: https://www.targetvalidation.org/target/ENSG00000284190).
We need to check with Europe PMC if microRNAs are included (or not) in their genes dictionary.
We do use this paper as text mining evidence for the association between IBD and VMP1, which overlaps with mir21: https://www.targetvalidation.org/evidence/ENSG00000062716/EFO_0003767?view=sec:literature

Many microRNAs either don't have associations in our Platform or when they do the evidence is Genetic associations or RNA expression, not text mining.

Confirmed with ePMC that microRNAs are not included.  Closing this ticket as additional work will be scoped and covered under new proposal.

authors: ElaineMcA deniseOme

repo: opentargets/platform


text:
feat(core): audit logging

Adds audit logging level to internal logger
Closes #730

Can we abstract this to define enumerated events and the service? I'm concerned that without predefined events it's going to be hard to document and if we don't automatically scope to a service then there could be naming conflicts with the events.

@strantalis informed me that there is already a plan in place that will address my concerns!

authors: jrschumacher pbacon-blaber

repo: opentdf/platform


text:
TypeError: Miner.init() got an unexpected keyword argument 'config'

While running the miner script getting the following error:
TypeError: Miner.__init__() got an unexpected keyword argument 'config'

Script:
yusuf@miner:~/tao-mining/prompting$ python3 neurons/miners/zephyr/miner.py --netuid 1 --wallet.name m2 --wallet.hotkey m2h --neuron.model_id HuggingFaceH4/zephyr-7b-beta --axon.port 8890

Any python guru here knows why?

I'm not sure why you would be seeing this error, but I would recommend just starting from scratch. Are you sure that you did python -m pip install -e . ?

closing because it's stale.

authors: mccrindlebrian yusufseyrek

repo: opentensor/prompting


text:
[Epoch Improvement] Use only validator stake in epoch

[Epoch Improvement] Use only validator stake in epoch
Now explicitly masks out non-validators from active_stake, and does not just rely on masking in the weights:

Main benefit is that stake-weighted median should now be sparse and much faster, due to non-validator stake giving zero weights being factored out.
Ensures that the majority (kappa) value is now exact, no longer offset by zero-weighting non-validator stake.

@opentaco LGTM but can you also increase spec_version to 109?

authors: opentaco shibshib

license: Unlicense


text:
[bbr] validate BBR configuration

This PR makes sure BBR configuration is valid according to Thread Spec. 5.21.3.3.

Added one more check that MLR timeout >= MLR_TIMEOUT_MIN (300) required by Thread Spec.
@librasungirl @jwhui

repo: openthread/openthread


text:
[CLI] add bdx perf feature to CLI app

This PR adds BDX Perf feature to OT CLI app. This is an application-level
feature to test the performance of BDX-like (Bulk Data Exchange) traffic
in Matter. In specific, this
feature generates similar traffic pattern as the synchronous mode of
BDX protocol. The flow is like:

This PR implements this feature in cli and add some unit tests.

It may be arguable if we want to add this feature to OpenThread. I was doing some internal performance testing and have completed the code. So I directly made a PR. It's fine if you think we'd better not put this into OT.
I think this feature can be helpful when we want to do some performance testing. This feature is totally in application level and doesn't change OT core at all. And I disable it by default. So I think we can add this feature. @jwhui @abtink

Thanks @Irving-cl
I agree this may be useful but I am on the fence whether it make sense to add it in OT or not.
Some initial suggestions/thoughts:

I don't think adding this implementation/feature in CLI is a good idea.
CLI should be focused on providing command line support for OT public APIs (we should avoid adding new code/logic in CLI)
If we decide to add this, I suggest to add it as a utility module in src/core/utils (similar to PingSender) and provide public API for it:

This way you can access all the core-internal types and definitions (Timer, Message, etc) in the implementaion

Close this temporarily. May re-open it in the future. with more discussion and agreement.

authors: Irving-cl abtink


text:
🐛 [Bug]: grid 配置{ storage: 'local', simple: true }控制台有警告

Version
latest
Vue Version
latest
Link to minimal reproduction

配置 :setting="{ storage: 'local', simple: true }"属性
Step to reproduce

What is expected
No response
What is actually happening
No response
What is your project name
https://opentiny.design/vue-playground?cmpId=grid-toolbar&fileName=toolbar/insert-delete-update.vue&apiMode=Options&mode=pc&theme=default
Any additional comments (optional)
No response

This problem is fixed in 3.17.0 version

authors: falcon-jin gimmyhehe

repo: opentiny/tiny-vue


text:
MockTracer use text map propag as default constructor

Resolves #177

Coverage increased (+1.5%) to 75.593% when pulling 7574312cc6c7fac4fbcec141c8a5dd7101cf56e1 on pavolloffay:mock-use-text-map-propag-be-default into a0fc80516b3ad1ce8fd45e7d0fc27529ea3b0c0b on opentracing:master.

If there are no issues I will merge in 48h.
cc @opentracing/otsc @opentracing/otiab

Coverage increased (+1.0%) to 74.086% when pulling b06ecb4598a598e6b59f188f0a99c71f969e3a12 on pavolloffay:mock-use-text-map-propag-be-default into e000eb0c62ee3149ae272c6c197bfc039d2c2749 on opentracing:master.

anybody from @opentracing/otsc to approve the PR?

Coverage increased (+0.9%) to 75.602% when pulling cfd8e1983d2fd6ce6cbc29c4433f341658da75af on pavolloffay:mock-use-text-map-propag-be-default into dd75c9dc3bb887ae90533ba22bba8d0ed51c94a3 on opentracing:master.

@pavolloffay Was thinking if we should re-target this to 0.31 directly (as that's the new defacto 'upstream' branch). Let me know, as I could re-target it myself (so we can enjoy it for RC 2 ;) )

As a reference, I re-targeted this patch for v0.31.0 - and the result is here: https://github.com/pavolloffay/opentracing-java/commits/master. @pavolloffay hope this helps to get it integrated soon ;)

Was thinking if we should re-target this to 0.31 directly (as that's the new defacto 'upstream' branch). Let me know, as I could re-target it myself (so we can enjoy it for RC 2 ;) )

@carlosalberto what about rebasing v0.31 against the master before publishing RC2?

@pavolloffay That's actually a good idea. So, lets merge this change and to the rebase later today.

+1 IIR there are more commits in master than in v0.31.. I will merge

authors: carlosalberto coveralls pavolloffay

repo: opentracing/opentracing-java


text:
🛑 [CN] OpenUPM Website Packages is down

In cf02b6a, [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 f4f01dc after 13 minutes.

repo: openupm/upptime-openupmcn


text:
🛑 [CN] OpenUPM Website Packages is down

In 5cb2b51, [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 22c4275 after 14 minutes.


text:
🛑 [CN] OpenUPM Website Packages is down

In 680cc9a, [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 c8e8467 after 7 minutes.


text:
Not able to login to CVAT UI which is deployed in AWS EC2 instance

I have installed CVAT in AWS EC2 instance and after starting all docker containers I am not able to login from UI, getting 500 Internal Server Error in browser console. However, I can able to access Django admin page where I can all created users. In docker logs cvat_proxy I can see http error codes but no other information/recommendation available in logs.
Screenshots

Error on UI Page loading

Error on Login

Django Admin Page

Referred following resources for resolution, but nothing worked

Official installation guide for AWS
Followed solution in Cannot deploy CVAT on AWS EC2 instance
Referred related PR Fix AWS deployment and updated docker-compose.override.yml, like :

version: "2.3"

services:
  cvat_proxy:
    environment:
      ALLOWED_HOSTS:
      CVAT_HOST: ec2-34-196-74-213.compute-1.amazonaws.com

Additional Information

cvat_proxy_logs.txt

Docker Version : Docker version 20.10.14, build a224086

CVAT Version : [1.4.0] - 2021-05-18

OS Version : Ubuntu VERSION="20.04.3 LTS (Focal Fossa)

@KushBhatnagar , do you have the same issue with CVAT v2.1.0?

@nmanovic :  I am using older version(1.4.0) because I need to migrate data from another instance to this AWS EC2 instance. In running instance we are using this older version, and according to official CVAT backup guide  version of CVAT should be same in both machines.
However, I did tried to install new version(2.1.0) in the same EC2 instance but there is no cvat_proxy server running and I am not able to access the UI.

docker-ps output

UI Page Error

@nmanovic  : Any update on this issue?

@KushBhatnagar , why do you try to open port 80 on the latest screenshot? Traefik is the cvat_proxy. Try to access 8080 port. It should work.
Also if you need to migrate data, the approach is right. Need to install 1.4.0 first and after that upgrade it till 2.1.0. Could you please share logs for docker containers? I will try to help and investigate. Just run docker logs cvat > cvat.log and share with me cvat.log. If you like, you can send it privately (e.g. using gitter).

@nmanovic , I am not sure about Traefix port. I have not changed anything in the setup and trying to access 8080 port only.
Please the cvat.log from 1.4.0 version.

@KushBhatnagar , it cannot be logs from 1.4.0. OPA was introduced in v2.0.0, but in your logs I see:
equests.exceptions.ConnectionError: HTTPConnectionPool(host='opa', port=8181): Max retries exceeded with url: /v1/data/users/allow (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f61811f6c70>: Failed to establish a new connection:

@nmanovic : I have installed 1.4.0 only, I am attaching CHANELOG.md from the installation folder to verify this please take a look. I have captured the cvat logs again but here also I can see 'OPA', not sure why this is coming.
CHANGELOG.md
cvat.log
However, as suggested in previous comments I did install new version 2.1.0 in the same EC2 instances but I have stopped/removed those containers and deleted the setup. Is there something else I need to check regarding this?

@nmanovic : Do you have any input or update on this?

@nmanovic : I have installed 1.4.0 only, I am attaching CHANELOG.md from the installation folder to verify this please take a look. I have captured the cvat logs again but here also I can see 'OPA', not sure why this is coming.
CHANGELOG.md cvat.log
However, as suggested in previous comments I did install new version 2.1.0 in the same EC2 instances but I have stopped/removed those containers and deleted the setup. Is there something else I need to check regarding this?

The reason is ： execute the command ‘’export CVAT_HOST=<YOUR_DOMAIN>“； but I don't know how to solve it;

@nmanovic : Any update on this issue? It's a kind of blocker for particular release. Any kind of input will be helpful

Try to add slash at the end of login endpoint:
localhost:8080/auth/login/
instead of
localhost:8080/auth/login

Try to add slash at the end of login endpoint:
localhost:8080/auth/login/ instead of localhost:8080/auth/login

@Pepslee  : I have tried this but nothing has changed

Hi there, I had exactly the same issue and in my case it was related to the missing /cvat/apps/iam/rules folder. This folder is only available on git repo and it is a strong dependency of CVAT OPA. In my case I fell in error because I only downloaded the docker-compose.yml file, without considering the remaining part of git repo.
I hope it will help you too. 👋🏻

@azhavoro , please cover the case in your guide. I will close the issue. @KushBhatnagar , we are going to provide add step by step guide how to upgrade CVAT. I hope such questions will be less in the future.

authors: KushBhatnagar Pepslee a873054267 drivo nmanovic

repo: openvinotoolkit/cvat


text:
Bug in mot_format.py

According to the MOT data format spec, "All frame numbers, target IDs and bounding boxes are 1-based" (quote from https://github.com/dendorferpatrick/MOTChallengeEvalKit/tree/master/MOT#data-format). If this claim is correct, there is a bug in mot_format.py.
When testing the CVAT tool, which uses datumaro, I failed to import a MOT dataset with an error "ValueError: Unknown internal frame id -1\n". To debug, I installed CVAT in developer mode (with VS code) and found two issues that lead to the cause of this error, where one affects this repository. In mot_format.py on line 147 (latest develop branch) there are the following lines:
for row in csv.DictReader(csv_file, fieldnames=MotPath.FIELDS):
    frame_id = int(row['frame_id'])
    item = items.get(frame_id)

Since items contains frame ids that start with zero, the item with id zero never gets accessed in this loop because frame_id starts with 1 when mot annotation files is loaded. Also, a possible overrun can occur when frame_id equals the length of the sequence (which is possible since its base-1).
My suggested fix:
for row in csv.DictReader(csv_file, fieldnames=MotPath.FIELDS):
    frame_id = int(row['frame_id']) - 1 # one based frame ids
    item = items.get(frame_id)

Hi, thank you for reporting the problem! As I see, we already subtract 1 in the CVAT format handler.

Yes I use a seqinfo file. I also reported a bug on the CVAT repo that is related this this one https://github.com/openvinotoolkit/cvat/issues/3940 (I included a description of the .zip file I used). Since datumaro returned zero indexed item ids, regardless of my suggested fix, the -1 in CVAT format handler is wrong and also contributed to this problem. But indeed its a good thing to review the indexing logic. However, it would be nice if this issue got fixed as soon as possible.

Yes I use a seqinfo file.

Then, probably, the fix should be done here: https://github.com/openvinotoolkit/datumaro/blob/develop/datumaro/plugins/mot_format.py#L125-L126
We should just start from 1 instead of 0.

We should just start from 1 instead of 0.

That also works and does not require modifications to the CVAT tool.
I implemented the following to test your suggestion:
if self._seq_info:
            for frame_id in range(1, self._seq_info['seqlength'] + 1):  # base-1 frame ids
                items[frame_id] = DatasetItem(
                    id=frame_id,

And it works!
Shall I make a PR for this?

Glad to hear this.

Shall I make a PR for this?

Yes, it would be great!

authors: maartenvds zhiltsov-max

repo: openvinotoolkit/datumaro


text:
Add --save flag to persist defaults into the manifest

--save should be conservative: add new actions, leave the existing ones in the manifest intact. We might want a prune command to remove manually deleted actions.

Eventually we could also have a --onlysave flag to only update the manifest without deployment.

Actually, you would create a new manifest (new name) so perhaps a different switch would be in order.  typically, this would be considered a "rewrite" or "flattening" with the purpose of collapsing not only the deployment values, but also any imports as well (and their namespaces).

I was more envisioning the scenario where devs start by implementing several actions and then want to automatically update the manifest.
--save is not the right way. We probably want another command, like sync.

Hi @lionelvillard after adding managed deployments, do we still need support for these different flags?

I think we still need the "sync" capability, but it's not critical. I don't think we need a flag. Instead it should be a new command.

authors: lionelvillard mrutkows pritidesai

repo: openwhisk/openwhisk-wskdeploy


text:
Github webhook enhancements

Resolves #886 #910
Call whisk.error() with the actual error object received.
Call whisk.error() when the status code from Github is something other than 200.
Allow the repository parameter to optionally be specified as <organization>/<repoName> so that it can be used to track repositories that aren't directly owned by the user.

@psuter @rabbah @starpit Would you mind having a look at this? I believe all the returns are in order: One when lifeCycleEvent is CREATE and one for all other cases.

Merged as 9fceba2ee3f9a06e6466f6fe71f2d1235c4dbde1.

authors: bjustin-ibm psuter

repo: openwhisk/openwhisk


text:
Luci Statistics Disk Space Usage Missing Fields

PROBLEM: From collectd df plugin page we get that it is capable of reporting space in both bytes and percentage, but these options are missing on LUCI / Statistics / Setup / General Plugins / Disk Space Usage / Additional Field.
REQUEST: Please add boolean fields for ValuesAbsolute and ValuesPercentage.
USE CASE: I am collecting to InfluxDB which stores free, used and reserved spaces in different rows of the database, and AFAIK it can not yet perform math across rows. I am plottig with Grafana, which also can't combine multiple separate queries. The problem is solved with collectd reporting percentage, but LUCI got in the way.

Could you please check this pullrequest if this works for you?
https://github.com/openwrt/luci/pull/4267
I must mention that I did not do a test, because I do not use the module.
But from the best of my knowledge and belief I would say that this could solve your problem.

@lhartmann does this P/R fixes your issue?

authors: feckert lhartmann

repo: openwrt/luci


text:
luci-proto-modemmanager: add peerdns option

ModemManager is a layer 3 "protocol", so there should be an option to allow users to ignore operator-supplied DNS(s).
Tested on Banana PI BPI-R4 (MediaTek Filogic 880, MT7988A), current snapshot, Google Chrome 126.0.6478.127.
Question: should I touch the PKG_VERSION of luci-proto-modemmanager since there's no change there?

This is only available, from my point of view, if the modemmanager is using the ppp https://github.com/openwrt/packages/blob/master/net/modemmanager/files/lib/netifd/proto/modemmanager.sh#L101C3-L101C13 to start a connection.

This is only available, from my point of view, if the modemmanager is using the ppp https://github.com/openwrt/packages/blob/master/net/modemmanager/files/lib/netifd/proto/modemmanager.sh#L101C3-L101C13 to start a connection.

Umm...it is a PPP connection in my case, but no authentication is required. I don't see that option in the Luci interface without this change. I'm all ears if there's a better way. Also, peerdns should apply to DHCP as well.

I have now had a look at the modemmanager proto.
That's basically correct, but we still have to do something in modemmanger proto to get it right.
At first we have check as in the umbim and uqmi if peerdns is enabled. Currently we always set for the static part (ipv4/ipv6) dns1-ipv4, dns2-ipv4 , dns1-ipv6 and dns2-ipv6 independently of the peerdns configuration value. In order for the correct behavior and independently of ppp, static or dhcp, we would also have to check whether peerdns is set. And only if peerdns is set, then and only then we should set the dns1 or dns2.

Thank you for the explanation, @feckert . My apologies, but I thought my modem (RM500Q-GL) was using the PPP method, but it turned out to be Static, and for some reason, the peerdns option is working.
Syslog excerpt:

Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): IPv4 connection setup required in interface wwan: static
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding IPv4 address [redacted], netmask 255.255.255.248
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding default IPv4 route via [redacted]
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding primary DNS at [redacted]
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding secondary DNS at [redacted]
Wed Jul 17 03:55:39 2024 daemon.notice netifd: Interface 'wwan' is now up
Wed Jul 17 03:55:39 2024 daemon.notice netifd: Network device 'wwan0' link is up
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): IPv6 connection setup required in interface wwan: static
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding IPv6 address [redacted], prefix 64
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding default IPv6 route via [redacted]
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding primary DNS at [redacted]
Wed Jul 17 03:55:39 2024 daemon.notice netifd: wwan (4912): adding secondary DNS at [redacted]
Wed Jul 17 03:55:39 2024 user.notice firewall: Reloading firewall due to ifup of wwan (wwan0)
Wed Jul 17 03:55:39 2024 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?

ifconfig output:

wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:[redacted]  P-t-P:10.38.141.252  Mask:255.255.255.248
inet6 addr: [redacted]/128 Scope:Global
inet6 addr: fe80::128e:bf8d:8744:745/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1400  Metric:1
RX packets:19097 errors:0 dropped:0 overruns:0 frame:0
TX packets:36672 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4958872 (4.7 MiB)  TX bytes:6267750 (5.9 MiB)

By working, I mean the DNSes from the mobile network weren't picked up by Dnsmasq as indicated in /tmp/resolv.conf.d/resolv.conf.auto. My custom v4 and v6 servers are there instead under # Interface wwan. I also found the IPv4 DNSes from the mobile network in /tmp/resolv.conf.ppp which was modified or created around the same time as shown in the log.
I'd like to do things properly, but I'm not sure if I can get my modem to use DHCP or PPP for testing.

Unfortunately, I accidentally tore off the lid of my RM500Q-GL when replacing the heatsink. I have no actual need for a 5G modem, so won't be buying another. Closing this pull request since I can't work on it anymore.

authors: feckert memoz


text:
Wrong stablehlo.add semantics for booleans in docs

What happened?
StableHLO spec says that stablehlo.add op on booleans should behave as "logical OR".

but that's not the logical behavior nor the implementation (which is "logical XOR").
Steps to reproduce your issue
Using Reactant (which is a Julia frontend to Enzyme + XLA), we can see that it behaves as a logical XOR:
julia> a = ConcreteRArray([false, false, true, true])
4-element ConcreteRArray{Bool, 1}:
 0
 0
 1
 1

julia> b = ConcreteRArray([false, true, false, true])
4-element ConcreteRArray{Bool, 1}:
 0
 1
 0
 1

julia> @jit Ops.add(a, b)
4-element ConcreteRArray{Bool, 1}:
 0
 1
 1
 0

Version information
No response

CC @wsmoses

Hi @mofeing, the spec is reflective of the behavior that XLA follows. I'm not familiar with Reactant -- is it using StableHLO apis that incorrectly results in the XOR behavior?

Sample file:
$ cat /tmp/t.mlir
func.func @main() -> tensor<4xi1> {
  %c = stablehlo.constant dense<[false, false, true, true]> : tensor<4xi1>
  %c_0 = stablehlo.constant dense<[false, true, false, true]> : tensor<4xi1>
  %0 = stablehlo.add %c, %c_0 : tensor<4xi1>
  return %0 : tensor<4xi1>
}

Using StableHLO reference interpreter:
$ stablehlo-translate --interpret /tmp/t.mlir
tensor<4xi1> {
  [false, true, true, true]
}

Using HLO Runner:
$ run_hlo_module /tmp/t.mlir  --platform=cpu --input_format=stablehlo --print_literals
** Result with test runner Host **
pred[4] {0, 1, 1, 0}
Running HLO module with runner Interpreter...
... compiled and ran in 0.00130981s.
execution time for runner Interpreter: 0.000424s.

** Result with reference runner Interpreter **
pred[4] {0, 1, 1, 0}

Indeed looks like the XLA behavior is XOR, perhaps a bug in the spec.

i see, so stablehlo.add on booleans is a "saturating add" rather than a "overflowing add". I always considered "overflowing add" (logical XOR) to be the correct behavior because that's what you use when implementing an integer adder on electronics.
anyway, yes, there seems to be a mismatch between XLA and StableHLO spec for this op. should I move the issue to XLA then?

authors: GleasonK ghpvnist mofeing

repo: openxla/stablehlo


text:
[Discussion] How about deprecating kubelet certificate management mode (Yurthub shares certificates with Kubelet) in future releases？

What would you like to be discussed:

In future versions, yurthub and kubelet shared certificate mode will be removed and the related interface will be deprecated.
At the same time, in the process of using the current OpenYurt version, the system prompts the user that the certificate sharing with kubelet is no longer supported in the later version.

Why is this needed:

Certificate rotation problem may occur when Yurthub shares certificates with Kubelet：
When Yurthub shares a certificate with Kubelet, if the Kubelet certificate expires during the cloud-side disconnection, yurthub that shares the kubelet certificate will also not work. In this case, Kubelet cannot update the node certificate through Yurthub. For this reason, Yurthub proposes its own certificate management mode, hubself (The related PR is here).

In ordinary use, users are not aware of the option to share with kubelet certificates:
At present, the default certificate mode of Yurthub is hubself mode, which is also the certificate management mode recommended by the community. From the perspective of users, when using yurtctl to convert Kubernetes cluster or nodes, adding nodes to OpenYurt cluster, the hubself certificate management mode is used default. Users are not aware of the kubelet sharing mode unless they manually deploy or change Yurthub.

Due to the above two main reasons, and in order to avoid users' confusion about these two modes, can we gradually stop the maintenance and support of the mode of Yurthub sharing kubelet certificate, and delete this mode in the future version?

@qclc Thank you for raising issue.
There are literally no users using kubelet mode, so i agree with you that remove kubelet certificate mode from yurthub.

@qclc would you can take over and remove kubelet mode from yurthub?

@qclc would you can take over and remove kubelet mode from yurthub?

Yes, I am willing to take over and remove kubelet mode from yurthub.

authors: qclc rambohe-ch

repo: openyurtio/openyurt


text:
0755 dirmode replaced by Const

0755 dirmode replaced by Const

/lgtm
/approve


text:
Should we drop the native elasticsearch transport?

Currently, the zipkin-server bundles a dep on elasticsearch 2.x drivers (which themselves pull deps on guava). The 2.x drivers are incompatible with later versions of Elasticsearch, and cannot coexist since the 2.x and 5.x libraries use the same class names. We need to decide what do do about it.
The ES dependency is needed for the transport protocol. The transport protocol is only used by java clients or a "tribe node". Incidentally, not all java clients support the transport protocol, either. For example, elasticsearch's spark support uses http, and the elasticsearch rest client does as well. There are some advantages to the native protocol around multiplexing, but it adds a weight to the project I don't think we can afford.
We made "elasticsearch-http" to support amazon deployments which only support http. Incidentally we also use http in zipkin-dependencies, too, as that's what spark supports. Recently (1.20), we decoupled  "elasticsearch-http" from the native elasticsearch driver. In doing so, we solved the case where custom servers were blocked from using ES 5.x libraries (#1431). We also dodged a guava dependency which held users back to version 18. However, we doubled our maintenance as changes to http or the transport codebases need to be synchronized. This also linearly impacts CI time.
At the moment, eventhough from a library component pov we are decoupled, the default server packages the transport protocol. This means we are still effectively limited by the library dependencies and also the double-maintenance until we change.
I recommend that we drop the transport codebase, with some warning, and coerce ES_HOSTS to use http ports instead. In this case, it would act just like the spark job which does the same thing.
@openzipkin/elasticsearch what do you all think?

Drop it like it's hot

+1 for dropping the native driver.

SGTM!

+1

We are deploying Zipkin Server with an Elasticsearch backend, and would actually prefer to use the HTTP rather than the transport protocol.

going to drop this shortly

https://github.com/openzipkin/zipkin/pull/1547 drops this

authors: ImFlog adriancole anuraaga dan-tr mansu shakuzen

repo: openzipkin/zipkin


text:
ui: Buffer underflow

FAT [20121023-18:33:11.993] ZipkinWeb: java.nio.BufferUnderflowException
FAT [20121023-18:33:11.993] ZipkinWeb:     at java.nio.Buffer.nextGetIndex(Buffer.java:498)
FAT [20121023-18:33:11.993] ZipkinWeb:     at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:355)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedBinaryAnnotation.toJson(json.scala:19)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceTimeline$$anonfun$toJson$10.apply(json.scala:79)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceTimeline$$anonfun$toJson$10.apply(json.scala:79)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:194)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:194)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:60)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:44)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.TraversableLike$class.map(TraversableLike.scala:194)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.collection.mutable.ArrayBuffer.map(ArrayBuffer.scala:44)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceTimeline.toJson(json.scala:79)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceCombo$$anonfun$toJson$12.apply(json.scala:95)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceCombo$$anonfun$toJson$12.apply(json.scala:95)
FAT [20121023-18:33:11.993] ZipkinWeb:     at scala.Option.map(Option.scala:133)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.conversions.json$WrappedTraceCombo.toJson(json.scala:95)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.web.App$$anonfun$12$$anonfun$apply$23.apply(App.scala:236)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.zipkin.web.App$$anonfun$12$$anonfun$apply$23.apply(App.scala:235)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$$anonfun$map$1$$anonfun$apply$10.apply(Future.scala:503)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Try$.apply(Try.scala:13)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$.apply(Future.scala:98)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$$anonfun$map$1.apply(Future.scala:503)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$$anonfun$map$1.apply(Future.scala:503)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$$anonfun$flatMap$1.apply(Future.scala:477)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Future$$anonfun$flatMap$1.apply(Future.scala:476)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Promise$$anonfun$transform$1.apply(Future.scala:883)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Promise$$anonfun$transform$1.apply(Future.scala:879)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Promise$$anonfun$respondWithoutChaining$1.apply(Future.scala:868)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.util.Promise$$anonfun$respondWithoutChaining$1.apply(Future.scala:863)
FAT [20121023-18:33:11.993] ZipkinWeb:     at com.twitter.concurrent.IVar$$anonfun$runqs$1.apply$mcV$sp(IVar.scala:174)
FAT [20121023-18:33:11.993] ZipkinWeb:     (...more...)

Closing due to lack of activity.

authors: eirslett franklinhu


text:
UI slow if the aggregation creates too many buckets

the aggregation zipkin servers sent to Elasticsearch as below:
{
"_source": false,
"aggs": {
"name": {
"terms": {
"field": "name",
"size": 2147483647
}
}
},
"query": {
"bool": {
"filter": {
"bool": {
"must": [{
"range": {
"timestamp_millis": {
"from": 1531825045984,
"include_lower": true,
"include_upper": true,
"to": 1531911445984
}
}
},
{
"term": {
"localEndpoint.serviceName": "mobileuser-service"
}
}]
}
}
}
}
}
Warning: 299 Elasticsearch-6.3.0-424e937 "This aggregation creates too many buckets (10001) and will throw an error in future versions. You should update the [search.max_buckets] cluster setting or use the [composite] aggregation to paginate all buckets in multiple requests." "Wed, 18 Jul 2018 08:21:04 GMT"

[ ] Question.

What is this aggregation used for ?
How to resolve this issue?

do you have variables in your span names? Span names should be fixed
cardinality. If you have something like an http route, make sure this is
used instead of paths with variables in it.
https://github.com/openzipkin/brave/tree/master/instrumentation/http#http-route-cardinality
https://github.com/openzipkin/zipkin-api/blob/master/zipkin.proto#L108
https://github.com/openzipkin/zipkin-api/blob/master/zipkin2-api.yaml#L312

Thanks for the quick response.   We are using Spring Cloud -Dalston RELEASE with sleuth.  By default, it puts variables in the span name.

I just tested the lastest Spring Cloud and found the cardinality has been fixed in this Finchley RELEASE,  like span name: " get /user/{userId}"


text:
Enables tracing of zipkin itself when SCRIBE_HOST or SCRIBE_PORT are set

If SCRIBE_HOST or SCRIBE_PORT are set, Finagle's DefaultTracer
sends all traces to the specified destination, often the
zipkin-collector. Otherwise, the DefaultTracer is disabled.
This applies to the zipkin-web and zipkin-query services, which are
now labeled correctly as services. zipkin-collector has tracing
explicitly disabled to discourage cyclic relationships.

cc @kristofa @yurishkuro

ok much cleaner impl now, based on advise from @kristofa and feedback from @yurishkuro
zipkin traces now appear as services "zipkin-web" and "zipkin-query"

Tested with:
$ bin/collector
$ SCRIBE_PORT=9410 bin/query
$ SCRIBE_PORT=9410 bin/web
$ curl -s localhost:8080/api/services
# now see services pop up!
$ curl -s localhost:8080/api/services
["zipkin-query","zipkin-web"]

I was not familiar with the DefaultTracer.self approach. Using the NullTracer is also better than having sample rate = 0.  :+1:

authors: adriancole kristofa


text:
Don't try to auto update if the data service can't be stopped

Right now, on automatic update, if this error occurs:
[2023-10-24T08:24:11.398Z] ERROR    ZitiUpdateService.UpdateService    Timout while trying to stop service!    System.InvalidOperationException: Cannot stop ziti service on computer '.'. ---> System.ComponentModel.Win32Exception: The service has not been started
   --- End of inner exception stack trace ---
   at System.ServiceProcess.ServiceController.Stop()
   at ZitiUpdateService.UpdateService.StopZiti()

The application will continuously try to update but never succeed because the data service is hung somehow. The user will need to restart Windows, or terminate the ziti-edge-tunnel service before updating can continue. This should be logged and probably surfaced as an error/message to the user to reboot/take action.

the monitor service will forcefully terminate the data service now

repo: openziti/desktop-edge-win


text:
verify Ziti's server cert

zrok should verify Ziti's server certificate before transmitting the Ziti login password

A new zrok controller config directive like ca_certs or tls_trust_bundle would be great. It could accept a PEM bundle as a string or file path or both.

While working my way back to this, I've mitigated the risk in my zrok instances with two approaches in this order:

two containers (sidecar pattern) or processes sharing a network interface and communicating exclusively via IPC over IP on the loopback interface (ziti mgmt API is not exposed nor published)
two containers in an isolated bridge network communicating exclusively at layer 2 (LAN) (ziti mgmt API is exposed but not published)

repo: openziti/zrok


text:
skydive operator

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

[ ] Has you operator 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

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

Your submission should not

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

Operator Description must contain (in order)

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

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] 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 a PR against this repo and explain your need
2 For more information see here

cfcc7a4 belongs to sepparate PR 1211

@sa-cloud, please fix the following:

PR form is empty, please fill it.
squash your commits
you are trying to edit both kubernetes and openshift operator, bear in mind that kubernetes is #1211 already

repo: operator-framework/community-operators


text:
upstream-community-operators [N] [CI] topolvm-operator (1.0.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
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?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?
[x] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

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

Operator Description must contain (in order)

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

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] 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

/merge possible

authors: framework-automation little-guy-lxr


text:
Investigation: Quality of Life improvements to CRD Upgrade Safety validations

@joelanford and I have noticed that a few operators from the operatorhub.io catalog fail the CRD preflight checks on upgrades due to "unknown changes" having occurred.
We should do some investigation to see what changes are commonly being failed on, if they are valid non-breaking changes, and what updates could be made to the validations to increase the QoL of users.

One that I recall failing during an upgrade was argocd

repo: operator-framework/operator-controller


text:
Add Operator metering component to tectonic-feature catalog

Adds the operator-metering component to the tectonic-feature catalog. This isn't tectonic specific, and in-fact, this wouldn't work by default on Tectonic, so this location is temporarily until we have multiple catalogs.

What's your goal with this? tectonic-features is one of two catalogs shipping with tectonic 1.9, so we do have multiple catalogs already.
If you just want validation of your manifests and such we're working on some tooling for another repo that will do that.

authors: chancez ecordell


text:
Add upstream catalog

This adds the operatorhubio catalog as a default catalog for upstream releases.
Also added in the operatorstatus changes to the chart from #748

/test unit

/test e2e-aws-olm

/retest

/test e2e-aws-olm


text:
Resolve dependencies manager detects conflicting when mixing dep and module in one project

Feature Request
Is your feature request related to a problem? Please describe.
We had a problem (right now, we used a workaround) in camel-k problem https://github.com/apache/camel-k
When project could use in the same time mixing dep and module dependencies managers, the 'operator-sdk build' command always use dep whether GO111MODULE set or not.
Right now, dependencies manager detection mechanism starts with looking for gopkgTOMLFile or goModFile and next for just GO111MODULE.
Describe the solution you'd like
It would be nice to change priority for detecting dependencies manager.

first, look for GO111MODULE settings
if it set to "on" check for goModFile
if not set or set to auto, look for goModFile or gopkgTOMLFile

I'm ready to provide fix for this solution. Any feedback's are appreciate.

@shawn-hurley , @jmrodri, @hasbro17 @LiliC could you please to look at this request. If it suitable, i can provide a PR for it. Thank you.

@joelanford could you please to look at this issue also?

@dmvolod I'm not opposed to accepting a change for this (assuming @estroz agrees with the logic). However, we're planning to completely drop support for dep when Go 1.13 is released. If history is any indication, that should be sometime this month, so it might make sense to just wait for that.

@joelanford this priority change is ok with me. @dmvolod feel free to submit a PR, or I can whip one up. Thanks!

Thanks @joelanford and @estroz for response.
I will provide PR as well as submit a new issue related to the "dep drop support" and assign it with Go1.13 release milestone (https://github.com/golang/go/milestone/83) for tracking, and could help with it if possible.

@dmvolod the SDK has upgraded to go 1.13 and dropped support for dep/Gopkg.toml in new projects. We recommend upgrading to v0.12.0. If you still have trouble with your dual dependency management issue, feel free to submit a patch PR to the v0.11.x branch and we can look into getting that merged. I will reopen this issue if that is the case.

authors: dmvolod estroz joelanford

repo: operator-framework/operator-sdk


text:
preserveUnknownFields is removed from CRDs by operator-sdk generate bundle

Bug Report
We need to explicitly set preserveUnknownFields: false to support upgrades between v1beta1 CRDs and v1 CRDs. In the past, we've used YAML post-processing on the CRD files to set this property explicitly. I'm working on upgrading our project to Operator SDK v1.3.2, and so now we can leverage kustomize for some of this "post-processing" of CRDs.
I've configured kustomize patches, for example:
$ cat config/crd/patches/pruning_in_datapowerservices.yaml
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: datapowerservices.datapower.ibm.com
spec:
  preserveUnknownFields: false

I have validated those are outputting correctly for our two CRDs:
$ kustomize build config/manifests | grep preserveUnknownFields
  preserveUnknownFields: false
  preserveUnknownFields: false

Our bundle make target looks like this:
# Generate bundle manifests and metadata.
bundle: manifests kustomize
        operator-sdk generate kustomize manifests
        cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
        $(KUSTOMIZE) build config/manifests | operator-sdk generate bundle $(BUNDLE_METADATA_OPTS)

As the kustomize build config/manifests is the input to operator-sdk generate bundle, and I know the properties exist in that input, it narrows the point of omission to the operator-sdk copying of these files to the bundle/manifests output directory.
What did you do?
make bundle
What did you expect to see?
CRDs output in bundle/manifests should retain preserveUnknownFields: false.
CRDs output in bundle/manifests should match the output from kustomize build config/manifests.
What did you see instead? Under which circumstances?
The preserveUnknownFields property is stripped from the CRDs when placed into bundle/manifests.
$ grep -R -c preserveUnknownFields bundle/manifests
...
bundle/manifests/datapower.ibm.com_datapowermonitors.yaml:0
bundle/manifests/datapower.ibm.com_datapowerservices.yaml:0
...

Environment
Operator type:

/language go

Kubernetes cluster type:
OCP 4.6 / 4.7
$ operator-sdk version
operator-sdk version: "v1.3.2", commit: "5dd883dc90085da6a6e75bb05443b4d491a39143", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
go version go1.15.8 linux/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0+d670f74", GitCommit:"d670f744c7507b1afebfa72ef3f79bf924ad5467", GitTreeState:"clean", BuildDate:"2021-05-21T13:35:23Z", GoVersion:"go1.15.7", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution

Additional context

@aharbis One more way could be to set this in controller-gen options. Can you try setting this in Makefile (similar to this): https://github.com/operator-framework/operator-sdk/blob/6351af55dd38c88ca19114d0c165eadec5c82143/testdata/go/v3/memcached-operator/Makefile#L41

@varshaprasad96 Yes, except that's broken for v1 CRDs: https://github.com/kubernetes-sigs/controller-tools/issues/476

If this happens soonish we can backport it to a patch release for 1.12.0, but otherwise we think this is fine for 1.13.0.

We investigated the issue, and found that the kustomize generates the yaml fields by taking inputs from the patch/ dir, while generating bundle we Marshal the crd to bytes so that it is written to a file. While marshalling, as the preserveUnknownFields has the omitempty tag on it, its default value is false and hence its not explicitly written. This brings us to the same problem as faced in controller-gen which is mentioned in here.
The only option we found it to write it explicitly into yaml file using script.
Script is:
function generate_preserveUnknownFieldsdata() {
    for j in config/crd/patches/*.yaml ; do
        if grep -qF "preserveUnknownFields" "$j";then
            variable=`awk '/metadata/{flag=1} flag && /name:/{print $NF;flag=""}' "$j"`
            for k in config/crd/bases/*.yaml ; do
                if grep -qF "$variable" "$j";then
                    filename=`awk 'END{ var=FILENAME; split (var,a,/\//); print a[4]}' "$k"`
                    awk '/^spec:/{print;print "  preserveUnknownFields: false";next}1' "bundle/manifests/$filename" > testfile.tmp && mv testfile.tmp "bundle/manifests/$filename"
                fi
            done
        fi
    done
}

generate_preserveUnknownFieldsdata

Also, modified the make bundle in Makefile as shown in below:
.PHONY: bundle
bundle: manifests kustomize ## Generate bundle manifests and metadata, then validate generated files.
	operator-sdk generate kustomize manifests -q
	cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
	operator-sdk bundle validate ./bundle | ./preserve_script.sh

We are planning to document these as a FAQ to the docs section.

We investigated the issue, and found that the kustomize generates the yaml fields by taking inputs from the patch/ dir, while generating bundle we Marshal the crd to bytes so that it is written to a file. While marshalling, as the preserveUnknownFields has the omitempty tag on it, its default value is false and hence its not explicitly written. This brings us to the same problem as faced in controller-gen which is mentioned in here.
The only option we found it to write it explicitly into yaml file using script.
Script is:
function generate_preserveUnknownFieldsdata() {
    for j in config/crd/patches/*.yaml ; do
        if grep -qF "preserveUnknownFields" "$j";then
            variable=`awk '/metadata/{flag=1} flag && /name:/{print $NF;flag=""}' "$j"`
            for k in config/crd/bases/*.yaml ; do
                if grep -qF "$variable" "$j";then
                    filename=`awk 'END{ var=FILENAME; split (var,a,/\//); print a[4]}' "$k"`
                    awk '/^spec:/{print;print "  preserveUnknownFields: false";next}1' "bundle/manifests/$filename" > testfile.tmp && mv testfile.tmp "bundle/manifests/$filename"
                fi
            done
        fi
    done
}

generate_preserveUnknownFieldsdata

Also, modified the make bundle in Makefile as shown in below:
.PHONY: bundle
bundle: manifests kustomize ## Generate bundle manifests and metadata, then validate generated files.
	operator-sdk generate kustomize manifests -q
	cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
	operator-sdk bundle validate ./bundle | ./preserve_script.sh

We are planning to document these as a FAQ to the docs section.

authors: aharbis jberkhahn laxmikantbpandhare varshaprasad96


text:
GoDaddy DynDNS update through Godaddy API

Add plugin for Dynamic DNS updates for Godaddy using the API.

This is not a core-related issue.
Please open an Issue at https://github.com/opnsense/plugins/issues

repo: opnsense/core


text:
PHP Warning:  Illegal string offset 'descr' in /usr/local/etc/inc/config.inc on line 317

Describe the bug
After upgrade to 19.1.1, I removed the "monitor IP address" on my gateway interface.
Afterwards, I get tons of messages like this:
[14-Feb-2019 10:36:54 Europe/Helsinki] PHP Warning:  Illegal string offset 'descr' in /usr/local/etc/inc/config.inc on line 317
[14-Feb-2019 10:36:54 Europe/Helsinki] PHP Warning:  Illegal string offset 'ipaddrv6' in /usr/local/etc/inc/config.inc on line 318
[14-Feb-2019 10:36:54 Europe/Helsinki] PHP Warning:  Cannot assign an empty string to a string offset in /usr/local/etc/inc/config.inc on line 318
[14-Feb-2019 10:36:54 Europe/Helsinki] PHP Warning:  Illegal string offset 'ipaddr' in /usr/local/etc/inc/config.inc on line 319
[14-Feb-2019 10:36:54 Europe/Helsinki] PHP Warning:  Cannot assign an empty string to a string offset in /usr/local/etc/inc/config.inc on line 319

To Reproduce
See above.
Expected behavior
No such messages.
Relevant log files
See above
Environment
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.27 Safari/537.36
FreeBSD 11.2-RELEASE-p8-HBSD  31af16db12b(stable/19.1) amd64
OPNsense 19.1.1 35cd081ca
Plugins os-dyndns-1.12_1 os-openconnect-1.3.3
Time Thu, 14 Feb 2019 10:58:36 +0200
OpenSSL 1.0.2q  20 Nov 2018
PHP 7.1.26

it looks like a defective config.xml, could you inspect /conf/config.xml and see if there are any empty sections the<interfaces>section?  (perhaps dump the config section here, without ip addresses)

<interfaces>
    <lan>
      <if>igb0</if>
      <descr>LAN</descr>
      <enable>1</enable>
      <lock>1</lock>
      <spoofmac/>
      <ipaddr>172.16.0.1</ipaddr>
      <subnet>12</subnet>
      <ipaddrv6>track6</ipaddrv6>
      <track6-interface>wan</track6-interface>
      <track6-prefix-id>0</track6-prefix-id>
    </lan>
    <enc0>
      <internal_dynamic>1</internal_dynamic>
      <enable>1</enable>
      <if>enc0</if>
      <descr>IPsec</descr>
      <type>none</type>
      <virtual>1</virtual>
    </enc0>
    <wan>
      <if>igb3</if>
      <descr>WAN</descr>
      <enable>1</enable>
      <lock>1</lock>
      <spoofmac/>
      <blockpriv>1</blockpriv>
      <blockbogons>1</blockbogons>
      <ipaddr>dhcp</ipaddr>
      <dhcphostname/>
      <alias-address/>
      <alias-subnet>32</alias-subnet>
      <dhcprejectfrom/>
      <adv_dhcp_pt_timeout/>
      <adv_dhcp_pt_retry/>
      <adv_dhcp_pt_select_timeout/>
      <adv_dhcp_pt_reboot/>
      <adv_dhcp_pt_backoff_cutoff/>
      <adv_dhcp_pt_initial_interval/>
      <adv_dhcp_pt_values>SavedCfg</adv_dhcp_pt_values>
      <adv_dhcp_send_options/>
      <adv_dhcp_request_options/>
      <adv_dhcp_required_options/>
      <adv_dhcp_option_modifiers/>
      <adv_dhcp_config_advanced/>
      <adv_dhcp_config_file_override/>
      <adv_dhcp_config_file_override_path/>
    </wan>
    <opt2/>
  </interfaces>

I don't know what <opt2/> is or where it came from, will delete it.

I think that fixed it.

a config import perhaps? or did it right after a specific action?

No import. I updated to 19.1.1 and made that one change in the GUI (see my first message above.)

can you check your config history what exactly changed after this action? this sounds a bit odd, if opt2 was never there,  it would be quite unexpected to add entries in this area.
Only thing that seems to be editing interfaces in that section should be
https://github.com/opnsense/core/blob/936a50ba957e7c1ad3917d37b446bf199844b6ee/src/www/system_gateways.php#L104-L106
Which is triggered after gateway removal.

How do I check my config history?

System->Configuration->History

opt2 seems to only show up in this snippet in my config before the 19.1.1 update:
    <gateway_item>
      <interface>opt2</interface>
      <gateway>dynamic</gateway>
      <name>VPN_TUM_DHCP</name>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr/>
      <avg_delay_samples/>
      <avg_loss_samples/>
      <avg_loss_delay_samples/>
      <monitor_disable>1</monitor_disable>
    </gateway_item>

And then in one of the new configs during the upgrade, this line was added to <interfaces>:
    <opt2/>

we might be close, can you dump the full diff with opt2 in it? There might be something of value in the description.

random thought: sounds like a case of auto-vivification through config_read_array()

@fichtner likely, I can probably fix the effect, but it might be good to know where this came from.

You mean the full diff from before the 19.1.1 update to the last one after?

no, only the one where <opt2/> enters

--- config-1548056906.3826.xml	2019-01-21 09:48:26.382737000 +0200
+++ config-1550133326.6421.xml	2019-02-14 10:35:26.642320000 +0200
@@ -356,6 +356,7 @@
       <adv_dhcp_config_file_override/>
       <adv_dhcp_config_file_override_path/>
     </wan>
+    <opt2/>
   </interfaces>
   <dhcpd>
     <lan>
@@ -934,109 +935,14 @@
   </widgets>
   <revision>
     <username>root@172.19.235.111</username>
-    <time>1547720498.0493</time>
-    <description>Saved Widget System Log Filter Setting</description>
+    <time>1550133281.272</time>
+    <description>/system_gateways_edit.php made changes</description>
   </revision>
   <OPNsense>
     <captiveportal version="1.0.0">
       <zones/>
       <templates/>
     </captiveportal>
-    <proxy version="1.0.1">
-      <general>
-        <enabled>0</enabled>
-        <icpPort/>
-        <logging>
-          <enable>
-            <accessLog>1</accessLog>
-            <storeLog>1</storeLog>
-          </enable>
-          <ignoreLogACL/>
-          <target/>
-        </logging>
-        <alternateDNSservers/>
-        <dnsV4First>0</dnsV4First>
-        <forwardedForHandling>on</forwardedForHandling>
-        <uriWhitespaceHandling>strip</uriWhitespaceHandling>
-        <useViaHeader>1</useViaHeader>
-        <suppressVersion>0</suppressVersion>
-        <VisibleEmail>admin@localhost.local</VisibleEmail>
-        <VisibleHostname/>
-        <cache>
-          <local>
-            <enabled>0</enabled>
-            <directory>/var/squid/cache</directory>
-            <cache_mem>256</cache_mem>
-            <maximum_object_size/>
-            <size>100</size>
-            <l1>16</l1>
-            <l2>256</l2>
-            <cache_linux_packages>0</cache_linux_packages>
-            <cache_windows_updates>0</cache_windows_updates>
-          </local>
-        </cache>
-        <traffic>
-          <enabled>0</enabled>
-          <maxDownloadSize>2048</maxDownloadSize>
-          <maxUploadSize>1024</maxUploadSize>
-          <OverallBandwidthTrotteling>1024</OverallBandwidthTrotteling>
-          <perHostTrotteling>256</perHostTrotteling>
-        </traffic>
-      </general>
-      <forward>
-        <interfaces>lan</interfaces>
-        <port>3128</port>
-        <sslbumpport>3129</sslbumpport>
-        <sslbump>0</sslbump>
-        <sslurlonly>0</sslurlonly>
-        <sslcertificate/>
-        <sslnobumpsites/>
-        <ssl_crtd_storage_max_size>4</ssl_crtd_storage_max_size>
-        <sslcrtd_children>5</sslcrtd_children>
-        <snmp_enable>0</snmp_enable>
-        <snmp_port>3401</snmp_port>
-        <snmp_password>public</snmp_password>
-        <ftpInterfaces/>
-        <ftpPort>2121</ftpPort>
-        <ftpTransparentMode>0</ftpTransparentMode>
-        <addACLforInterfaceSubnets>1</addACLforInterfaceSubnets>
-        <transparentMode>0</transparentMode>
-        <acl>
-          <allowedSubnets/>
-          <unrestricted/>
-          <bannedHosts/>
-          <whiteList/>
-          <blackList/>
-          <browser/>
-          <mimeType/>
-          <safePorts>80:http,21:ftp,443:https,70:gopher,210:wais,1025-65535:unregistered ports,280:http-mgmt,488:gss-http,591:filemaker,777:multiling http</safePorts>
-          <sslPorts>443:https</sslPorts>
-          <remoteACLs>
-            <blacklists/>
-            <UpdateCron/>
-          </remoteACLs>
-        </acl>
-        <icap>
-          <enable>0</enable>
-          <RequestURL>icap://[::1]:1344/avscan</RequestURL>
-          <ResponseURL>icap://[::1]:1344/avscan</ResponseURL>
-          <SendClientIP>1</SendClientIP>
-          <SendUsername>0</SendUsername>
-          <EncodeUsername>0</EncodeUsername>
-          <UsernameHeader>X-Username</UsernameHeader>
-          <EnablePreview>1</EnablePreview>
-          <PreviewSize>1024</PreviewSize>
-          <OptionsTTL>60</OptionsTTL>
-          <exclude/>
-        </icap>
-        <authentication>
-          <method/>
-          <realm>OPNsense proxy authentication</realm>
-          <credentialsttl>2</credentialsttl>
-          <children>5</children>
-        </authentication>
-      </forward>
-    </proxy>
     <AcmeClient version="1.4.0">
       <settings>
         <enabled>0</enabled>
@@ -1340,7 +1246,18 @@
         </rule>
       </rules>
     </TrafficShaper>
-    <IDS version="1.0.1">
+    <Netflow version="1.0.0">
+      <capture>
+        <interfaces>lan</interfaces>
+        <egress_only>wan</egress_only>
+        <version>v9</version>
+        <targets>127.0.0.1:2056</targets>
+      </capture>
+      <collect>
+        <enable>1</enable>
+      </collect>
+    </Netflow>
+    <IDS version="1.0.2">
       <rules>
         <rule uuid="0cfbac13-74a4-4e2f-a7de-a09b5719041c">
           <sid>2210057</sid>
@@ -1652,7 +1569,110 @@
         <LogPayload>0</LogPayload>
       </general>
     </IDS>
-    <monit version="1.0.5">
+    <proxy version="1.0.2">
+      <general>
+        <enabled>0</enabled>
+        <icpPort/>
+        <logging>
+          <enable>
+            <accessLog>1</accessLog>
+            <storeLog>1</storeLog>
+          </enable>
+          <ignoreLogACL/>
+          <target/>
+        </logging>
+        <alternateDNSservers/>
+        <dnsV4First>0</dnsV4First>
+        <forwardedForHandling>on</forwardedForHandling>
+        <uriWhitespaceHandling>strip</uriWhitespaceHandling>
+        <useViaHeader>1</useViaHeader>
+        <suppressVersion>0</suppressVersion>
+        <VisibleEmail>admin@localhost.local</VisibleEmail>
+        <VisibleHostname/>
+        <cache>
+          <local>
+            <enabled>0</enabled>
+            <directory>/var/squid/cache</directory>
+            <cache_mem>256</cache_mem>
+            <maximum_object_size/>
+            <size>100</size>
+            <l1>16</l1>
+            <l2>256</l2>
+            <cache_linux_packages>0</cache_linux_packages>
+            <cache_windows_updates>0</cache_windows_updates>
+          </local>
+        </cache>
+        <traffic>
+          <enabled>0</enabled>
+          <maxDownloadSize>2048</maxDownloadSize>
+          <maxUploadSize>1024</maxUploadSize>
+          <OverallBandwidthTrotteling>1024</OverallBandwidthTrotteling>
+          <perHostTrotteling>256</perHostTrotteling>
+        </traffic>
+        <parentproxy>
+          <enabled>0</enabled>
+          <host/>
+          <port/>
+          <localdomains/>
+          <localips/>
+        </parentproxy>
+      </general>
+      <forward>
+        <interfaces>lan</interfaces>
+        <port>3128</port>
+        <sslbumpport>3129</sslbumpport>
+        <sslbump>0</sslbump>
+        <sslurlonly>0</sslurlonly>
+        <sslcertificate/>
+        <sslnobumpsites/>
+        <ssl_crtd_storage_max_size>4</ssl_crtd_storage_max_size>
+        <sslcrtd_children>5</sslcrtd_children>
+        <snmp_enable>0</snmp_enable>
+        <snmp_port>3401</snmp_port>
+        <snmp_password>public</snmp_password>
+        <ftpInterfaces/>
+        <ftpPort>2121</ftpPort>
+        <ftpTransparentMode>0</ftpTransparentMode>
+        <addACLforInterfaceSubnets>1</addACLforInterfaceSubnets>
+        <transparentMode>0</transparentMode>
+        <acl>
+          <allowedSubnets/>
+          <unrestricted/>
+          <bannedHosts/>
+          <whiteList/>
+          <blackList/>
+          <browser/>
+          <mimeType/>
+          <safePorts>80:http,21:ftp,443:https,70:gopher,210:wais,1025-65535:unregistered ports,280:http-mgmt,488:gss-http,591:filemaker,777:multiling http</safePorts>
+          <sslPorts>443:https</sslPorts>
+          <remoteACLs>
+            <blacklists/>
+            <UpdateCron/>
+          </remoteACLs>
+        </acl>
+        <icap>
+          <enable>0</enable>
+          <RequestURL>icap://[::1]:1344/avscan</RequestURL>
+          <ResponseURL>icap://[::1]:1344/avscan</ResponseURL>
+          <SendClientIP>1</SendClientIP>
+          <SendUsername>0</SendUsername>
+          <EncodeUsername>0</EncodeUsername>
+          <UsernameHeader>X-Username</UsernameHeader>
+          <EnablePreview>1</EnablePreview>
+          <PreviewSize>1024</PreviewSize>
+          <OptionsTTL>60</OptionsTTL>
+          <exclude/>
+        </icap>
+        <authentication>
+          <method/>
+          <realm>OPNsense proxy authentication</realm>
+          <credentialsttl>2</credentialsttl>
+          <children>5</children>
+        </authentication>
+      </forward>
+      <pac/>
+    </proxy>
+    <monit version="1.0.8">
       <general>
         <enabled>1</enabled>
         <interval>120</interval>
@@ -1690,6 +1710,7 @@
         <start/>
         <stop/>
         <tests>f2d43bc3-88a6-45bf-aac2-483df4ecd8ba,bcf48782-9f0c-45f7-9c49-16c48d72fa18,513e1101-af59-4311-898d-542fc8090fca,f5e5112f-7a19-4533-8b84-a9898aea1259</tests>
+        <depends/>
       </service>
       <service uuid="116d6a44-b480-4e13-9b06-db46c11040fc">
         <enabled>1</enabled>
@@ -1704,73 +1725,119 @@
         <start/>
         <stop/>
         <tests>d721ba33-04c5-4372-8754-4a729cdbf603</tests>
+        <depends/>
+      </service>
+      <service uuid="81965ca1-7676-4cad-97f8-28127f6b4857">
+        <enabled>0</enabled>
+        <name>carp_status_change</name>
+        <type>custom</type>
+        <pidfile/>
+        <match/>
+        <path>/usr/local/opnsense/scripts/OPNsense/Monit/carp_status</path>
+        <timeout>300</timeout>
+        <address/>
+        <interface/>
+        <start/>
+        <stop/>
+        <tests>2b0a6649-f5f4-4baf-a533-e6db61a6da71</tests>
+        <depends/>
+      </service>
+      <service uuid="95c90b08-89f6-49bd-ac5d-93dd2de0cab9">
+        <enabled>0</enabled>
+        <name>gateway_alert</name>
+        <type>custom</type>
+        <pidfile/>
+        <match/>
+        <path>/usr/local/opnsense/scripts/OPNsense/Monit/gateway_alert</path>
+        <timeout>300</timeout>
+        <address/>
+        <interface/>
+        <start/>
+        <stop/>
+        <tests>eeef9f94-0371-4862-83f9-c8265342570a</tests>
+        <depends/>
       </service>
       <test uuid="d5484575-629e-4c93-bf4e-64e30b2b3100">
         <name>Ping</name>
+        <type>Custom</type>
         <condition>failed ping</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="defffb09-3cdc-47d7-aecc-47caba7e1095">
         <name>NetworkLink</name>
+        <type>Custom</type>
         <condition>failed link</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="af5260a9-1a20-4f77-a708-683be955f6c0">
         <name>NetworkSaturation</name>
+        <type>Custom</type>
         <condition>saturation is greater than 75%</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="f2d43bc3-88a6-45bf-aac2-483df4ecd8ba">
         <name>MemoryUsage</name>
+        <type>Custom</type>
         <condition>memory usage is greater than 75%</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="bcf48782-9f0c-45f7-9c49-16c48d72fa18">
         <name>CPUUsage</name>
+        <type>Custom</type>
         <condition>cpu usage is greater than 75%</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="513e1101-af59-4311-898d-542fc8090fca">
         <name>LoadAvg1</name>
+        <type>Custom</type>
         <condition>loadavg (1min) is greater than 8</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="f5e5112f-7a19-4533-8b84-a9898aea1259">
         <name>LoadAvg5</name>
+        <type>Custom</type>
         <condition>loadavg (5min) is greater than 6</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="2c659629-c91a-46b0-b9a0-e156674d5582">
         <name>LoadAvg15</name>
+        <type>Custom</type>
         <condition>loadavg (15min) is greater than 4</condition>
         <action>alert</action>
         <path/>
       </test>
       <test uuid="d721ba33-04c5-4372-8754-4a729cdbf603">
         <name>SpaceUsage</name>
+        <type>Custom</type>
         <condition>space usage is greater than 75%</condition>
         <action>alert</action>
         <path/>
       </test>
+      <test uuid="2b0a6649-f5f4-4baf-a533-e6db61a6da71">
+        <name>ChangedStatus</name>
+        <type>Custom</type>
+        <condition>changed status</condition>
+        <action>alert</action>
+        <path/>
+      </test>
+      <test uuid="eeef9f94-0371-4862-83f9-c8265342570a">
+        <name>NonZeroStatus</name>
+        <type>Custom</type>
+        <condition>status != 0</condition>
+        <action>alert</action>
+        <path/>
+      </test>
     </monit>
-    <Netflow version="1.0.0">
-      <capture>
-        <interfaces>lan</interfaces>
-        <egress_only>wan</egress_only>
-        <version>v9</version>
-        <targets>127.0.0.1:2056</targets>
-      </capture>
-      <collect>
-        <enable>1</enable>
-      </collect>
-    </Netflow>
+    <OpenVPNExport version="0.0.1">
+      <servers/>
+    </OpenVPNExport>
   </OPNsense>
   <cert>
     <refid>5b233a9d17063</refid>
@@ -1826,10 +1893,6 @@
       <ipprotocol>inet</ipprotocol>
       <interval/>
       <descr>Interface WAN dhcp Gateway</descr>
-      <avg_delay_samples/>
-      <avg_loss_samples/>
-      <avg_loss_delay_samples/>
-      <monitor>1.1.1.1</monitor>
       <defaultgw>1</defaultgw>
       <latencylow>10</latencylow>
       <latencyhigh>30</latencyhigh>

@larseggert can you also give the description of the configuration change, it should say which page modified it

ok, a bit unexpected "system_gateways_edit.php made changes"

ah it's in the revision, right, sorry for the noise

I think this was when I removed the monitoring IP

ok, with https://github.com/opnsense/core/commit/621f84e900f5ea17c58bf665573b9d13f4344f59 we should be able to prevent this from happening. I'm just not sure why it entered here, maybe there was mention of it in the gateways from a previous change.

@larseggert thanks for reporting!

I know this is already fixed, I have a system with 19.1.4 and when creating an interrface called DMZ_TP_VM I get:
PHP Warning:  Illegal string offset 'if' in /usr/local/etc/inc/interfaces.inc on line 3452
And the UI is a bit scambled:

Oh, forget it, there was an empty <wan/> in config.xml

@mimugmail I see, there's a loop over $config['interfaces'] in convert_real_interface_to_friendly_interface_name()

Yes, I removed the wan from config.xml, assigned another interface and wan is there again :/

@mimugmail it  probably won't fit 19.1.4, but this https://github.com/opnsense/core/commit/c6f8c46709ea3d4cc8b7afaa6f4fff72aa6845c1 should fix it.

authors: AdSchellevis fichtner larseggert mimugmail


text:
Aliases URL Tables (IPs) does not work correctly

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

[+] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[+] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I have an alias URL Tables (IPs) - mail gmail

Firewall>Diagnostics:

my PC

URL Tables (IPs) does not contain real addresses 108.177.14.108 and 108.177.14.109.
Software version used and hardware type if relevant, e.g.:
OPNsense 22.7_4-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1q 5 Jul 2022

https://serverfault.com/questions/1008483/how-does-google-return-a-different-a-record-every-time

OPNsense lookup IP *.gmail.com on other DNS? DNS server for computer is OPNsense (gateway). OPNsense use a different DNS? о_О   should return the same ip for computer and OPNsense
PC (mail client)  __ DNS request imap.gmail.com  __ -> from gateway opnsense -> gateway opnsense __ DNS request from 8.8.8.8___ ->  8.8.8.8 answer "imap.gmail.com -108.177.14.109

For geo/load balancing google dns records have short TTLs and authoritative servers mixing returning addresses so any host that tries to resolve *.Gmail.com may receive different answer on each try. IMHO it's not the best idea to try to use google dns records to filter google mail traffic. I would try to use ports and "google subnets" alias (see link in first answer)

authors: Anywake kulikov-a


text:
Issue Report - FreeOTP Unknown Issuer in Issuer Field

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

[Yes] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[Yes] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I have encountered an issue with FreeOTP on OPNsense where the issuer field displays as "unknown." This occurs when attempting to use FreeOTP for two-factor authentication within the OPNsense environment.
To Reproduce
Steps to reproduce the behaviour:

Install FreeOTP on a device.
Set up two-factor authentication in OPNsense using FreeOTP.
Generate a token and observe the issuer field.

Expected behaviour
I expected the issuer field in FreeOTP on OPNsense to display the correct and expected issuer information.  Unfortunately i don't see an option to set the issuer field.
Screenshots

Additional context
I do not get this error on Google Authenticator, it displays the hostname given to the OPNsense correctly.
Kindly provide steps to resolve this issue.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1 (amd64).

probably better ask them what they need to display an issuer... you can find their GitHub repo's at https://github.com/freeotp

probably better ask them what they need to display an issuer... you can find their GitHub repo's at https://github.com/freeotp

Hi, sure will do.
FYI: with pfSense it displays as FreeRadius Server since external authentication is built into that package.
Thanks.

Hi @AdSchellevis,
I get here following https://github.com/freeotp/freeotp-android/issues/387 and analyze URI returned by OPNsense in this comment https://github.com/freeotp/freeotp-android/issues/387#issuecomment-1926668075.
Just to know, did you except $config['system']['hostname'] to be viewed as the issuer here?

@joggee-fr yes, usually it shows user@domain in these type of apps.

@AdSchellevis
As I understand the docs on OTP URI format, in the case otpauth://totp/User1@Mail_VPN?secret=, User1@Mail_VPN is the account name. FreeOTP seems to choose to display the issuer but none is precised here.
OPNsense:User1@Mail_VPN would certainly display OPNsense as issuer for example. Or it seems it can also be added as URI parameters OPNsense:User1@Mail_VPN?secret=&issuer=OPNsense.

I don't mind adding an issuer, but I don't expect them to have a logo on their end....

@joggee-fr can you try https://github.com/opnsense/core/commit/12001a32f2605c7356c82f6ac26803d80a686fcd ? install via:
opnsense-patch 12001a3

@Gaitonde007, as you are the initial reporter could you give this patch a test?

@Gaitonde007, as you are the initial reporter could you give this patch a test?

Hi @joggee-fr , I have tested on Android and it works as expected. Issue on IOS still persists.
Thanks

@Gaitonde007, I am not aware of the iOS version of the FreeOTP application. However, did you open an issue there?

authors: AdSchellevis Gaitonde007 joggee-fr


text:
Web-Portal blog needs update

IMHO NOT an un-important question
Why did the blog stop in 2023 and no advertising of 24.1 and more?
Yes there may be other sources of information but the OPNsense blog could be easily continued as an instrument of marketing and information on the home page.  Furthermore, the "Blog" button sits quite prominent besides the "Download" button on the web top menu of your most beloved project home page.  Did I miss something or am I wrong?
ref

https://opnsense.org/blog/
https://opnsense.org/about/road-map/
https://forum.opnsense.org/

Just curios and just asking.
Keep on the good work and prosper.
🌻
Important notices
Our forum is located at https://forum.opnsense.org , please consider joining discussions there in stead of using GitHub for these matters.
Before you ask a new question, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

@Zweihorn the blog was merely a copy of the messages posted on the forum, manually copied periodically, it didn't add very much. We changed the widget on our end to use the feed via https://forum.opnsense.org/index.php?board=11.0&action=.xml;limit=20;type=rss2
When we're upgrading the project website, we have to see what we will do with it, currently we don't actively write blog postings, but in the future you never know.

@AdSchellevis  THX - However, the core web problem and IMHO quite misleading first impression to interested newcomers still remains apparently.
Why not just making a last and only blog post reading:

Please find more current information at

https://opnsense.org/about/road-map/
https://forum.opnsense.org/

Supposedly an easy and simple task.  Hope this helps.
🌻

@Zweihorn good point, I'll see what we can do.

However, the core web problem and IMHO quite misleading first impression to interested newcomers still remains apparently.

I can't agree more here. The blog menu item is quite prominent in the top menu, if the last blog item is from Juli 2023, the project seems kinda dead. Which isn't the case.
You really want to update those blogs if you are serious about the business IMO.

You really want to update those blogs if you are serious about the business IMO.

The rebranding of both the company and project has been going on for at least a year now and requires a lot of work so the modification of the old pages are just where strictly necessary and the blog just isn't one of them. We're on it. It would be nicer to not read such blanket statements.

To be fair the messenger has been dead for a couple of years. Random blanket statements are a waste of time and motivation.

feeds from forum now https://opnsense.org/blog/

Thank you so much!!

authors: AdSchellevis Zweihorn fichtner melroy89


text:
Fix DUID - LL description in Settings | Interfaces

Very nice catch, thanks! ❤

authors: GMazzocato fichtner


text:
Every ACME Automation results in Crash Report

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

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug
Everytime I run an Certificate Deployment it results in an Crash Report. I tried with deployment to Synology NAS and Proxmox.
I have a "fresh" installation of OPNsense it never worked.
To Reproduce
Steps to reproduce the behavior:

Go to Services > ACME Client > Certificates
Click on 'Run Automations'
See error

Expected behavior
Deploy the SSL Certificate to Proxmox / Synology NAS.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
Crash Report:
[16-Feb-2024 09:09:50 Europe/Berlin] PHP Fatal error:  Uncaught TypeError: proc_open(): Argument #2 ($descriptor_spec) must be of type array, null given in /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeAutomation/Base.php:133 Stack trace: #0 /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeAutomation/Base.php(133): proc_open('/usr/local/sbin...', NULL, NULL, NULL, Array) #1 /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeAutomation/Base.php(106): OPNsense\AcmeClient\LeAutomation\Base->runAcme() #2 /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeCertificate.php(606): OPNsense\AcmeClient\LeAutomation\Base->run() #3 /usr/local/opnsense/scripts/OPNsense/AcmeClient/lecert.php(188): OPNsense\AcmeClient\LeCertificate->runAutomations() #4 /usr/local/opnsense/scripts/OPNsense/AcmeClient/lecert.php(199): main() #5 {main}   thrown in /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeAutomation/Base.php on line 133
No error logs under:
Services > ACME Clients > Logs (Debug 3 enabled)
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant.
User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
FreeBSD 13.2-RELEASE-p9 stable/24.1-n254969-8659880248c SMP amd64
OPNsense 24.1.1 516bda3fc
Plugins os-acme-client-4.0
Time Fri, 16 Feb 2024 09:12:14 +0100
OpenSSL 3.0.13
Python 3.9.18
PHP 8.2.15

i think it discussed at https://github.com/opnsense/plugins/issues/3790 and the fix is planned for 4.1 release https://github.com/opnsense/plugins/pull/3806/files

repo: opnsense/plugins


text:
Automatic backup via WebDAV(S) / FTP(S) [ / SMB / NFS]

Currently, automatic backup is only possible on proprietary Cloud of Google. For security reasons, it should at least be possible to sync via WebDAV(S) on self-installed Nextcloud / ownCloud Installations and maybe also on self-hosted FTP(S) servers (for example in the local network, or secured over internet).
In the best case, SMB / NFS is also supported, in case of local RAID systems, but what I really need is WebDAVS synchronization for Nextcloud. Better stay safe than sorry, right?
(Maybe I should have posted this at core not plugins, if so, my fault, sorry, but I am not sure if this is a core functionality or plugin maybe? Then it is right here...)

@Addy90 config backup is a core feature. I will close this ticket because it belongs to core - please create a new one there.
I can create a script for Nextcloud (WebDAV) but I dislike the idea of SMB on OPNsense. FTP is not encrypted which is not a good idea for a config file containing lots of passwords and FTP is known to have issues with firewalls and NAT devices. I am not sure about NFS.
There is or was some code in development to upload the config file via SCP (SSH) and I do have a script for SFTP which will very likely not be included in a base install of OPNsense due to its dependencies.


text:
Metastore java

Updated read me for metaStoreToADW java example

Closing

repo: oracle-samples/oracle-dataflow-samples


text:
OCI - Resource Principal security

OCI integration
The Resource Principal Security is currently not implemented and should be.
Resource principal allows authentication against OCI using the current resource (such as a function in OCI).
#2894 brings in a class that currently throws UnsupportedOperationException.

We have deprecated our own OCI integration and we recommend using OCI SDK.

repo: oracle/helidon


text:
chore: Add PyPI heuristics check

PR Message:
Implemented PyPI's heuristics check to detect suspicious packages using seven key heuristics.
TODO List:

[x] Implement PyPI's heuristics check to detect the suspicious packages with seven heuristics
[x] Implement confidence policy
[ ] Design the DB table to store the proper result
[ ] Create src/macaron/malware_analyzer/ directory and move this check there.
[ ] Update documentation to reflect the new heuristics and their usage
[ ] Write unit tests to ensure the reliability and accuracy of the heuristics implementation

@Yao-Wen-Chang When you address an issue mentioned in a comment, you can put the link to the commit next to the comment indicating that it has been resolve. Something like this would be extremely helpful for my review. Thanks!
Fixed this in https://github.com/oracle/macaron/pull/750/commits/d6684088dbe7792731240709d73a17de1eba73ad

authors: Yao-Wen-Chang tromai

repo: oracle/macaron


text:
Add a test to change WebLogic credentials

This PR adds a test for WebLogic server admin credentials change test for domains running in persistent volumes.

Please update the PR with Jenkins results.

Changes looks good. Are the latest Jenkins runs clean?

Changes looks good. Are the latest Jenkins runs clean, let me know. I can approve.

Yes the description includes the latest test results.

Changes looks good. Are the latest Jenkins runs clean, let me know. I can approve.

Yes the description includes the latest test results.

Yes, I saw it later and approved, Thanks.

authors: sankarpn vanajamukkara

repo: oracle/weblogic-kubernetes-operator


text:
Token contract is empty

Token contract source code is empty: https://github.com/oraclesorg/treasury/blob/master/contracts/TestToken.sol.
Let's create extension of mintable token with tokenDepositEvent  at transfer method.

Why mintable? Mintable or not does not affect on transfer method. I suggest just StandardToken.

@vbaranov we will create all tokens (252,460,800) on the right side before the token sale start. After crowd sale ends we will send exact amount of sold tokens in coins from multisig to the treasury. Buyers will exchange tokens to coins. Unsold tokens will be on the contract of the right side of the bridge.
I don't understand either why do we need mintable token here.

Maybe, it's my misunderstanding. Let me explain.
I make tests for bridge this way:

I create mintable token
mint hardcap of crowdsale to master of ceremony address
join mintable token to the right side of the bridge
tokens are transfered to user address from master of ceremony during buying

How to fill master of ceremony balance without minting?

why do we need to mint token? we can specify the number of tokens and owner (master of ceremony) as a const in StandardToken, right?

How to fill master of ceremony balance without minting?

Just put desired number of tokens into balances[msg.sender] in the Token constructor. Like that done in TestToken: https://github.com/oraclesorg/treasury/blob/master/contracts/TestToken.sol#L12

Ok, I see. Thanks.

authors: igorbarinov lorien vbaranov

repo: oraclesorg/treasury


text:
Cannot read property subscribe of undefined

I might vrery well have been wrong at some point,
When I'm trying to instantiate the Orbitdb document store, that error appear:

ipfs-pubsub.js:16 Uncaught TypeError: Cannot read property 'subscribe' of undefined(…)

I am using ipfs-api, in the browser.

Thanks for reporting the issue! Can you you try installing ipfs-api with npm install @haad/ipfs-api and then require it as const ipfsApi = require('@haad/ipfs-api') and let me know if that works?
We're in the process of releasing go-ipfs 0.4.5 and orbit-db is using the very latest (and experimental) version from a fork of ipfs-api.
Hope this helps!

Hi,
following your advice, I downloaded, ipfs-go version 0.4.5-dev and used the @haad/ipfs-api package
I now get a 500 server error

POST http://localhost:5001/api/v0/pubsub/sub?discover=true&arg=restaurants&stream-channels=true 500 (Internal Server Error)

followed by

pubsub.js:59 Uncaught TypeError: Cannot set property 'cancel' of undefined(…)

here is my code
const Orbitdb = require('orbit-db');
const IpfsApi = require('@haad/ipfs-api');

class IpfsStore {
    node: any;
    restaurant: any;
    constructor() {
        this.node = IpfsApi( 'localhost', '5001');
        const orbitdb = new Orbitdb(this.node);
        try {
            this.restaurant = orbitdb.docstore('restaurants');
        } catch (e) {
            console.log(e);
        }
    }
}

I somehow manage to use the docstore by passing { subscribe: false } in the config object

Thanks @ticruz38 for the details! This helps. There's couple of things going on here but a bug you've just found is that the error message doesn't bubble up correctly (shouldn't be uncaught), so this is something we need to fix in orbit-db.
Passing { subscribe : false } makes orbit-db to NOT replicate with other users. Your errors comes from the replication part of the code, so that makes sense. I'll look into to this.
Meanwhile, can you confirm which version of orbit-db you have installed? Do npm ls orbit-db. If you're not on 0.16.0-beta.x, could you try and install 0.16.0-beta.1 and run it again (just to make sure you're on the latest version).
If you're on 0.16.0-beta1, then what you probably need is the 0.4.5-pre1 version of go-ipfs which is not officially released yet but can be downloaded from https://dist.ipfs.io/go-ipfs/v0.4.5-pre1. This build contains the pubsub feature that orbit-db depends on.
Oh, also, I think you have to do this.node = new IpfsApi(...) with the new keyword.

I did download the ipfs executable you sent to me, started the daemon, instantiate IpfsApi properly with the new keyword, I am on orbitdb 0.16.0-beta1, but still got the same errors. I can't use any of the store provided by orbitdb...

Sorry for your troubles. There's one more thing to try and if that doesn't make it work, I'll need to take a deeper look as I fix things.
Did you run the go-ipfs binary with --enable-pubsub-experiment (probably not since I didn't advice so)? Try that and if it doesn't work, let me know.

Don't be sorry, I am thankful for your help and for the library!
Putting the flag on the daemon removed the errors above, sadly I'm unable to put data in the docstore but also in the kvstore, when I put something in the store I get this:

OrbitDB.js:103 Uncaught (in promise) Error: Hash can't be null!(…)

well, my node_modules might have been spoil, with all the install workaround, cleaning them and make an npm install solve the problem. Thanks!

I run into the same problem as I was upgrading ipfs and orbit-db to   "ipfs": "^0.30.1",
"orbit-db": "^0.19.9"
Needed to have in ipfsConfig following the Orbitdb ToDo Example pattern

 // Configuration for IPFS instance
    const ipfsConfig = {
        repo: '/conceptipedia/mobile/ipfs',
        EXPERIMENTAL: {
            pubsub: true,
        },
        config: {
            Addresses: {
                Swarm: [
                    // Use IPFS dev signal server
                    // '/dns4/star-signal.cloud.ipfs.team/wss/p2p-webrtc-star',
                    '/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star/'
                ]
            },
        }
    }

authors: gyuri-lajos haadcode ticruz38

repo: orbitdb/orbit-db