text:
Informs acknowledgement

Hi,
We have a distributed application running as containers. I need some help to set the source address for the acknowledgment packet going out of pysnmp.
So, this is our workflow:

The agent sends the informs to the application (running on server 1)

Application forwards the UDP packet to the informs processing app (running on server 2) --> It's for load balancing.

Server 2 receives and process the informs, sends the acknowledgment back to the Agent. This is done by the SNMP engine --> But the source IP is for the ack packet is set to the server 2 IP.

And our agent drops the acknowledgment bcos the informs were sent to the server 1.
Is there any way I can set the source address for the ack packet? Need some help.
Code:
from pysnmp.carrier.twisted.dgram import udp

self.snmp_engine = engine.SnmpEngine()
udp_transport.addressType().setLocalAddress(('1.2.3.4', 0))
        udp_transport.openServerMode(('::', self.informs_port))
        udp_transport.enablePktInfo()

        config.addTransport(
            self.snmp_engine,
            udp.domainName,
            udp_transport
        )

Note : I am using twisted udptransport.
Sa.

In my case, the source IP is reset to a different IP, with this doesn't it need to recalculate the checksums??

I am pretty sure pysnmp should not and in fact it does not mess with IP/UDP checksums. I believe this is done by the TCP/IP stack in the kernel (or even by the NICs now days). If checksum calculation is offloaded to the NIC, I can imagine tcpdump might not see the final checksum in the outgoing traffic.
It would be helpful if you paste some network related code - what you ended up with for the time being?

Did you manage to override source IP in responses? I think it's doable, but I am not sure that necessary API is exposed especially for Twisted.

@etingof  No. I am not able to. I have been looking at the code and realized that we need to have Python 3 to spoof the local address.
For ex:
https://github.com/etingof/pysnmp/blob/master/pysnmp/carrier/sockmsg.py#L104
This is what I am thinking for spoofing the address with twisted:  We make a custom twisted.internet.udp.Port implementation where self.socket.send and self.socket.sendto in write are replaced with calls to sendmsg similar to what pysnmp does. Then we will replace the twisted dispatcher with our custom implementation.

repo: etingof/pysnmp


text:
[Feature Request] On all videos?

Hi!
Could you make it work on most videos on the web? Not just on youtube or vimeo.
That would be awesome. I don't think there's an extension on Firefox that do this.
Thank you for your consideration.

This is really a bit difficult to support every video site.
Maybe you can try another add-on: Maximize Video.
Thanks for your feedback.

What about just supporting generic HTML5 videos like the original extension did? That would be a good step.

Most of the videos on the Internet are embedded in iframe. The receipt of the contents of the iframe prohibits the CORS.
Probably it's possible to do if the video tag is directly on the page. It can be moved to the markup of the window that plugin opens.

How did Opera achieve it? Is that something that only FF can do and not an option with the extensions?

I think Opera feature is working a completely different manner. I would guess that they do some magic with the video output (mirror it in a popup) since you need the original tab open and video plays in sync (popup and tab). For this you probably need to bypass some web extension restrictions.

source: gharchive/issue

authors: LeGiTiM Luxian Skylion007 ettoolong rshadow

repo: ettoolong/PopupVideo

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 nginx is down

In fcb2720, nginx (https://nginx.eugene.ng) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nginx is back up in 5fea6bc after 1 hour, 16 minutes.

repo: eugeneyng/upptime


text:
Bug with display of multiple instances of widget on the same form

Given I am on the Form with 2 dynamic-relation-dropdown fields
- User field
- Product field
And I choose values for Product relation (second field) with autocomplete
Then I expect to see list of products
Actual: I see list of users instead of products.
            E.g. I always see results of the first field.

Explanation:

This is due to strange behavior of OctoberCMS AJAX handlers, where variables like $this->valueFrom, $this->formField always pre-populated with the first field.
Need to implement workaround to receive field name from additional post parameter.

Dear euknyaz, first of all great job for tue plugin.
I just reproduced bug, please find workaround or if you want I can help.
I also added ability to reset inserted value if you are interested in..
I will soon add X icon to reset value near dropdown icon, sometimes is very useful to remove inserted value..
To achieve modification I moved control partial in a widget directory:
public function render()
{
$this->prepareVars();
//return $this->makePartial('~/modules/backend/formwidgets/relation/partials/_relation.htm');
return $this->makePartial('plugins/euknyaz/relationdynamicdropdown/widgets/select2/_relation.htm');
}

makePartial('~/modules/backend/widgets/form/partials/_field_'.$field->type.'.htm', ['field' => $field]) ?>
    reset

Regards

makePartial('~/modules/backend/widgets/form/partials/_field_'.$field->type.'.htm', ['field' => $field]) ?>
    reset

authors: euknyaz msomma


text:
Configure speed_sp before executing rotate() and rotateTo()

This is connected to issue #663. When motors are after reset, they have their speed_sp set to zero. When a run command is invoked in this state, the motor (and the library while in blocking mode) freeze, because the kernel regulator considers the motor to be stalled.

Tested on 4.14.117-ev3dev-2.3.4-ev3 that medium motor works.

+1 for this merge, it bit me again today.

@jabrena

Next week, I will check the example provided in the issue:
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/663
And I will review the PR

I have provided a summary of the issue here: https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/663#issuecomment-527112606

Superseded by https://github.com/ev3dev-lang-java/ev3dev-lang-java/pull/689

source: gharchive/pull-request

authors: JakubVanek jabrena salamanders

license: mit

license_source: bigquery


text:
[Bug] Miniflare 3 Uncaught (async) RangeError: Maximum call stack size exceeded

Minimal reproduction repository - https://github.com/AdiRishi/worker-wrangler3-otel-test
In order to produce the error, hit the / (root route).
Error - Uncaught (async) RangeError: Maximum call stack size exceeded
[mf:inf] Ready on http://127.0.0.1:8787/
[mf:inf] GET / 200 OK (18ms)
✘ [ERROR] Uncaught (in promise) RangeError: Maximum call stack size exceeded

  private _getContextManager(): ContextManager {
  ^
      at ContextAPI2._getContextManager
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@opentelemetry/api/src/api/context.ts:90:2)
      at ContextAPI2.active
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@opentelemetry/api/src/api/context.ts:60:16)
      at getActiveConfig
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/config.ts:117:24)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:133:24)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)
      at checkedFetch
  (/private/var/folders/__/f61lsp8x76551yjyz09hv0800000gp/T/tmp-40750-tWTIkkwORzHD/checked-fetch.js:22:19)
      at apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/fetch.ts:137:19)
      at proxyHandler.apply
  (/Users/arishi/playground/cloudflare/worker-otel/node_modules/@microlabs/otel-cf-workers/src/instrumentation/common.ts:25:18)

✘ [ERROR] Uncaught (async) RangeError: Maximum call stack size exceeded

I think I have found the culprit, which is a function called checkedfetch in wrangler. They use the esbuild define to swap that out for the global fetch to wrap it and do some checks.
But I think it ends up with that function calling itself. I am not sure if it is something I can fix in this library or if I should fix it in wrangler, because this is probably an issue with any library that wants to proxy the native fetch function (not that many libraries would want to do that, but still)

Ahh I see, so basically this piece of code gets messed up when the esbuild define swaps out the fetch function?
export function instrumentGlobalFetch(): void {
	globalThis.fetch = instrumentFetcher(fetch, (config) => config.globals.fetch)
}

Just a suggestion, I know this isn't ideal, but maybe this library should just export a custom fetch function like
import { instrumentedFetch as fetch } from '@microlabs/otel-cf-workers'

function test() {
    fetch() // this function is instrumented. And esbuild define won't replace it (maybe)
}

An approach like this might allow us to get around the issue you described? But again, I know the ideal DX would be for a developer to not have to think about this at all.

While we could certainly export a fetch function, I a) think that esbuild would still catch it as it is still a global fetch function and b) I absolutely wouldn't want to compromise our DX for a feature in wrangler that is there to catch obscure edge case errors only in development.
So the proper way forward is to fix this in wrangler, because we are just the first to want to proxy the global fetch function. But I will see if there is a work-around I can implement in this library in the meantime. But this would be an internal one only, not going to change the external interface because of it.

@evanderkoogh I don't have a specific thought, but maybe you can do some sort of branding check w/ symbols to break the loop? Don't have a good specific suggestion though.

The proxy solution seems to work just fine in wrangler, just need to wrangle someone to merge it (see what I did there?!)
But I ran into an other issue about me being too smart for my own good (which happens a lot tbf).
But that means the export was done in the inline request, which was killed after the returning of the response. So need to figure out the best way to deal with that. But that shouldn’t be too much of an issue.

Ok.. So all problems should be solved with 1.0.0-alpha.5 as soon as wrangler releases a new version with my PR in it: https://github.com/cloudflare/workers-sdk/pull/3497

Hmmm @evanderkoogh I was testing 1.0.0-alpha.5 on wrangler 2 and saw this error whenever my worker included a fetch call.
[mf:err] GET /: TypeError: Cannot read properties of undefined (reading 'globals')

Is this related to the issue we're seeing here in wrangler 3? Seems like it involves the global fetch function. Not sure if your PR will address this in wrangler 2. But maybe it doesn't need to if we consider wrangler 2 old now.
PS. This error can be seen in commit 88bf99c3373d135ab5a14e1a7861d06a15f2aa8a on the worker-wrangler2-otel-test repository.

Also, I won't want to celebrate early or anything, but I just tested 1.0.0-alpha.5 against wrangler 3.1.1 and it's working!! :)

authors: AdiRishi RichiCoder1 evanderkoogh

repo: evanderkoogh/otel-cf-workers


text:
Add a linter for the js code

Thinking of using standard.

Fixed in https://github.com/evansiroky/timezone-boundary-builder/commit/98b199387082ff01cf581a2188aedac1af479690.

repo: evansiroky/timezone-boundary-builder


text:
🛑 www.actionherojs.com is down

In 685d42c, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in b570743.

repo: evantahler/upptime


text:
🛑 www.actionherojs.com is down

In 7c42108, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 6cd6987.


text:
🛑 www.actionherojs.com is down

In 765a9ad, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 3bee89e.


text:
Some changes.

Formatting and grammar in the README file.
Add colorama package suggestion on Windows to the README.md.
Add support for choosing the fatal message - it defaults to "Fatal error: Program stopped.".

Thank you for your contribution!

Any time. :)

authors: TheTechRobo evasseure

repo: evasseure/cprint


text:
Offline Inverter prevents evcc from start

Describe the bug
i have two inverters.
One goes offline in the evening, the other is handling the battery and therefore always online.
If my Symo 8.2 is offline evcc won't start and throw the following error message.
  cannot create meter 'my_fronius_pv2': cannot create meter 'template': cannot create meter 'modbus': dial tcp 192.168.215.190:502: i/o timeout
Steps to reproduce
Try to start with an offline inverter
Configuration details
tariffs:
    currency: EUR
    grid:
        type: fixed
        price: 0.2369
    feedin:
        type: fixed
        price: 0.075

meters:
  - name: my_fronius_smartmeter
    type: template
    template: fronius-gen24
    usage: grid
    host: 192.168.215.156
  - name: my_fronius_pv1
    type: template
    template: fronius-gen24
    usage: pv
    host: 192.168.215.156
  - name: my_fronius_pv2
    type: template
    template: sunspec-inverter
    host: 192.168.215.190
  - name: my_byd_battery
    type: template
    template: fronius-gen24
    usage: battery
    host: 192.168.215.156

chargers:
  #- type: template
  #template: go-e-v3
  #host: 192.168.211.204
  #name: wallbox1
- type: template
  template: go-e-v3
  host: 192.168.211.33
  name: wallbox2

loadpoints:
- title: go-e rechts
  charger: wallbox2
  mode: pv
  phases: 0
  mincurrent: 6
  maxcurrent: 16
  resetOnDisconnect: true
  enable:
    threshold: 0
    delay: 1m
  disable:
    threshold: 0
    delay: 1m

site:
  title: xxxx
  meters:
    grid: my_fronius_smartmeter
    pv:
      - my_fronius_pv1
      - my_fronius_pv2
    battery: my_byd_battery
  bufferSoc: 95
  prioritySoc: 99

Log details
Feb 25 21:53:23 evcc evcc[1541]: [main  ] FATAL 2023/02/25 21:53:23 cannot create meter 'my_fronius_pv2': cannot create meter 'template': cannot create meter 'modbus': dial tcp 192.168.215.190:502: i/o timeout
Feb 25 21:53:23 evcc evcc[1541]: [main  ] FATAL 2023/02/25 21:53:23 will attempt restart in: 5m0s

What type of operating system are you running?
Linux
Version
evcc version 0.113.2

Das ist in der Tat blöd. Zu Zeitpunkt wo die Geräte angelegt werden, wissen wir noch nicht, dass es "nur" um PV geht und der Fehler deshalb ignoriert werden könnte. Workarounds:

WR extern auslesen und die Werte per MQTT zur Verfügung stellen
WR ganz weg lassen- PV Leistung ist ohnehin nur für Optik relevant, gesteuert wird über Netzbezug

repo: evcc-io/evcc


text:
Bar chart to show percentage?

I'm trying to figure out if its possible to render a bar chart where the yAxis values are 0, 25%, 50%, 75%, and 100% and the data is something like this:
[
  { name: 'a', value: 8 },
  { name: 'b', value: 10 },
  { name: 'c', value: 21 },
  { name: 'd', value: 47 },
  { name: 'e', value: 14 },
]

What I'm seeing now is this:

What I'm trying to do (ignore the tooltip):

Hi @adamgruber, thanks for the issue!
Have you tried setting .hasPercentage(true)?
Also, if you can provide a Codepen example I will be able to help you better!

@Golodhros I made a sandbox and messed around with it. Using the percentageAxisToMaxRatio option I can force the chart to always show 100% as the max value. However, I still am unable to configure the yAxis to show ticks for 0, 25%, 50%, 75%, 100%
https://codesandbox.io/s/async-snow-73mw7

Ahh, the ticks issue!
Ticks in D3.js are something magic, we can try to influence them, but we don't have full control over them. If you set 3 ticks you would get 0, 50% and 100%, but I think that's as close as you can get.
I am sorry, there is no solution for this!

authors: Golodhros adamgruber

repo: eventbrite/britecharts


text:
Enable support for simple querying from IMongoDbReadModelStore

I wanted to raise this to open discussions.
Within EventFlow there was a pull request #20 made which added some simple find methods to the InMemoryReadModelStore. I believe these would be very useful within the IMongoDbReadModelStore, preventing the need to go outside of EventFlow and query mongodb directly.
My view is that InMemoryReadModelStore shouldn't be the only query option, some will be just too complex and require bare metal access. However similar methods to the ones in InMemoryReadModelStore could be useful.
I am happy to put a pull request in, however would be good to get agreement on the interface

Exposing the MongoDb find code could allow access to the database within the EventFlow framework preventing users from needing to maintain their own access code and MongoDb instance. A suggested method for IMongoDbReadModelStore could be...
public interface IMongoDbReadModelStore<TReadModel> : IReadModelStore<TReadModel>
   where TReadModel : class, IReadModel, new()
{
    public static Task<IAsyncCursor<TReadModel>> FindAsync<TReadModel>(
	Expression<Func<TReadModel, bool>> filter,
	FindOptions<TReadModel, TReadModel> options = null,
	CancellationToken cancellationToken = null)
}

Hi Ed,
Would it be at all possible to include the ability to provide an expression to perform OrderBy actions on the dataset with properties of the read model.  Such as order by OrderDate Desc, Surname, Price Descending.

@edwardwilson  my apologies for the lack of communication from our side. will make an effort to be more helpful going forward.
happy with your proposal but why static?
@wingnut808: sorting can be provided by the FindOptions<TReadModel, TReadModel> options

seems it like it might work 👍
       public async Task<IAsyncCursor<TReadModel>> FindAsync(
            Expression<Func<TReadModel, bool>> filter,
            FindOptions<TReadModel, TReadModel> options = null,
            CancellationToken cancellationToken = default(CancellationToken))
        {
            var readModelDescription = _readModelDescriptionProvider.GetReadModelDescription<TReadModel>();
            var collection = _mongoDatabase.GetCollection<TReadModel>(readModelDescription.RootCollectionName.Value);

            return await collection.FindAsync(filter, options, cancellationToken);

        }

@janfeyen My mistake, the method signature was grabbed from MongoDb. I removed this IMongoCollection<TDocument> collection, but didn't notice the static was still there.
Completely agree with your above implementation. I will get it put into a branch and open a pull request. I think it is great to allow access to the same underlying MongoDb instance as the rest of the read store for more complex querying from query handlers.

authors: edwardwilson janfeyen wingnut808


text:
assets_update_version error

2015-04-18 12:15:26 executing symfony:assets:update_version' --> Updating assets_version`

executing "find /home/example/dev.acme.com/releases/20150418051523/web/css /home/example/dev.acme.com/releases/20150418051523/web/images /home/example/dev.acme.com/releases/20150418051523/web/js -type f -printf '%Ts\n' | sort -n | tail -1"
servers: ["127.0.0.1"]
[127.0.0.1] executing command
[err :: 127.0.0.1] find: /home/example/dev.acme.com/releases/20150418051523/web/css' [err :: 127.0.0.1] : No such file or directory find: /home/example/dev.acme.com/releases/20150418051523/web/images': No such file or directory
[err :: 127.0.0.1] find: `/home/example/dev.acme.com/releases/20150418051523/web/js': No such file or directory
command finished in 128ms
Latest assets version: (0)
executing "echo 'parameters:\n    assets_version: 0' |  tee /home/example/dev.acme.com/releases/20150418051523/app/config/assets_version.yml"
servers: ["127.0.0.1"]
[127.0.0.1] executing command
** [out :: 127.0.0.1] parameters:\n    assets_version: 0
command finished in 126ms

I think capifony 2.8.4 has a bug in assets_update_version. Capifony 2.8.3 is still okay!
assets_version.yml content:
parameters:\n    assets_version: 0

We're having some issues with this after updating from 2.8.3 -> 2.8.5 for the Composer fix.
Correct me if I'm wrong, but shouldn't this command be run after composer has installed dependencies and the cache is warmed up etc?

I used v2.8.4 not v2.8.5. I think there are some issues from symfony:assets:update_version in v2.8.4. Everything is okay in v2.8.3. Errors as I showed above.

Same worked for me, rolled back to 2.8.3, couldnt resolve the error in 2.8.5

authors: aaslocum tomtomau tunh

repo: everzet/capifony


text:
Update assets of dev bundles

I have some assets of bundles used in dev mode (like https://github.com/CoreSphere/ConsoleBundle and https://github.com/sensiolabs/SensioDistributionBundle) that needs to be installed after deploy. How do I do that ?
Thanks.

no one ? :/

Here is the answer
namespace :deploy do
  desc "Install all assets with symlinks"
    task :assets do
    run("cd #{deploy_to}/current && php app/console assets:install web --symlink")
  end
end

after "deploy", "deploy:assets"


text:
Update reject and filter to accept Objects

All inclusive!!

This PR address issue#117.

Adds a type rep for Object in the internal folder to implement a common filter.
Update point-free filter to work with Object values.
Update point-free reject to work with Object values.
fix up some existing specs for both filter and reject

Coverage remained the same at 100.0% when pulling 5188c05c5c41c0b5f3c44a822ce09fab17daf7c4 on reject-filter-obj into c1d1fe1900d583b0606ec4c748b4e16c32825384 on master.

Coverage remained the same at 100.0% when pulling 5188c05c5c41c0b5f3c44a822ce09fab17daf7c4 on reject-filter-obj into c1d1fe1900d583b0606ec4c748b4e16c32825384 on master.

Coverage remained the same at 100.0% when pulling 5188c05c5c41c0b5f3c44a822ce09fab17daf7c4 on reject-filter-obj into c1d1fe1900d583b0606ec4c748b4e16c32825384 on master.

authors: coveralls evilsoft

repo: evilsoft/crocks

license: ISC


text:
ios linking

hi i am getting this error i have installed Firebase pod poited RNFIRMessasing.h but still error
any help regarding linking is good
regards
thanks
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_RNFIRMessaging", referenced from:
      objc-class-ref in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

** BUILD FAILED **

The following build commands failed:

	Ld build/Build/Products/Debug-iphonesimulator/KurumsalB2CBETA.app/KurumsalB2CBETA normal x86_64
(1 failure)

solved with : react native, ios linking

repo: evollu/react-native-fcm


text:
Update sbt to 1.9.6

About this PR
📦 Updates org.scala-sbt:sbt from 1.6.2 to 1.9.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Pull Request Test Coverage Report for Build 6208471262

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.1%) to 70.807%

Totals

Change from base Build 2227406282:
3.1%

Covered Lines:
114

Relevant Lines:
161

💛  - Coveralls

Superseded by #144.

authors: coveralls scala-steward

repo: evolution-gaming/sequentially


text:
Update akka-actor, akka-testkit to 2.6.8

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-testkit

from 2.6.4 to 2.6.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch

Pull Request Test Coverage Report for Build 81

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 87.302%

Totals

Change from base Build 79:
-0.4%

Covered Lines:
55

Relevant Lines:
63

💛  - Coveralls

repo: evolution-gaming/serially


text:
Update scalatest to 3.2.18

About this PR
📦 Updates org.scalatest:scalatest from 3.2.16 to 3.2.18
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #172.

repo: evolution-gaming/sstream


text:
Howto launch

Hi,
I'm sorry but I can't use pydashie.
I don't know how I could access to web interface
Thanks by advance
Best Regards

Well it looks like you are running python2.6 so you would need to use scl (assuming you are on rhel/centos) to get to python27 as detailed here:
http://developerblog.redhat.com/2014/02/27/using-pythons-virtualenv-with-rhscl/
Additionally I had to install some extra packages to get the java runtime to work:
sudo yum install nodejs
sudo yum search libhttp_parser
sudo yum install http-parser
sudo yum install libuv -y
I think there are easier ways, but this got me going on centos6.

authors: pydubreucq sanderant

repo: evolvedlight/pydashie


text:
[Snyk] Security upgrade requests from 2.25.0 to 2.32.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

566/1000  Why? Recently disclosed, Has a fix available, CVSS 5.6
Always-Incorrect Control Flow Implementation SNYK-PYTHON-REQUESTS-6928867
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview 86d23237-413e-4d36-8107-dd4eefb5c091
blueprint

/qovery  preview aa879f73-0195-4e3e-ad3b-64ac8ebf3967
matang-env

/qovery  preview afb4eb55-9a99-4985-8ed2-f3661c8dbc91
new-env

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

Write comments that add new information that doesn’t exist in the code

repo: evoxmusic/ShortMe-URL-Shortener


text:
Timeout too short

Thank you for this program.
I am very close to getting it working on my Raspberry Pi 4, but I believe the timeout is too short for my system. It takes longer than 18 seconds for nrsc5 to lock on to a signal and play audio. As a result, when I use yellowShoes, it generates an error log that looks like the beginning of an nrsc5 console output about to begin playing a stream. I think it needs just a few more seconds for audio to begin.
I believe the yellowShoes timeout is currently set at 18 seconds. When I play nrsc5 without yellowShoes on the same device, it takes 20+ seconds, but it does seem to work. I found someone else who identified this issue here, but I don't know how to increase the timeout so that I can use yellowShoes.
Thank you again.

Thank you for taking the time to file this report. I will look into making playerTimeout  a tunable setting. Until then, can you please try changing it by hand and see if it works better for you?
user@lego:~/git/yellowShoes$ sed -i 's/18000/30000/g' static/page.html

In the example above, I've changed it from 18000 to 30000 milliSeconds.
Please give this a try and report back!

Thank you! This worked wonderfully. It was just what I was looking for.
I wasn't savvy enough to find where in the program the timeout was coded.
It's up to you whether to make the timeout a tunable setting - I'm satisfied regardless.
Thanks again!

Glad to hear it worked for you!
I've gone ahead and made and published the changes in branch tunableTimeO:
https://github.com/evuraan/yellowShoes/tree/tunableTimeO
Changes:

playerTimeout raised to 30 seconds
set playerTimeout section in settings -

Please give it a try, and let me know how it goes. I am looking to merge to main in a few days of scream tests.

It worked for me - I replaced the html file as you described and I can now access the menu item where I can change the timeout. Thank you again!

Changes merged to main, published 1.09d-ui-1.5f release.

authors: danburd evuraan

repo: evuraan/yellowShoes


text:
Feature/Create JSDocs

@exadel-inc/ui-playground-team

:tada: This PR is included in version 1.0.0-beta.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: exadel-inc/ui-playground


text:
'Generator[Dict[str,pyobj]]' object has no attribute 'to_py'

Hello,
Getting below error:
internal.codon:592:36-49: error: 'Generator[Dict[str,pyobj]]' object has no attribute 'to_py'
├─ :942:942: error: during the realization of to_py(slf: Tuple[pyobj,Generator[Dict[str,pyobj]]])
├─ python.codon:1187:19-35: error: during the realization of to_py(self: Tuple[pyobj,Generator[Dict[str,pyobj]]])
├─ load_access_log_file.py:110:13-72: error: during the realization of call(self: pyobj, *args: Tuple[pyobj,Generator[Dict[str,pyobj]]], **kwargs: KwTuple.N0)
╰─ load_access_log_file.py:146:1-52: error: during the realization of bulk_index_to_elasticsearch(es: pyobj, index: str, folder_path: str, chunk_size: int)
Code:
def bulk_index_to_elasticsearch(es, index, folder_path, chunk_size=10000):
    """Index logs to Elasticsearch in bulk."""
    count = 0
    for chunk in read_logs_with_pandas(folder_path, chunk_size):
        count = count + 1
        try:
            elasticsearch.helpers.bulk(es, doc_generator(chunk, index))

        except elasticsearch.helpers.BulkIndexError as e:
            print(f"{len(e.errors)} documents failed to index.")
            for error in e.errors:
                # Each 'error' is a dictionary representing the error details
                print(error)
        print("Indexed: " + str(count * chunk_size))

Kindly advise

Codon generators are currently not translatable to Python. You can collect them (via list()) and pass them to Python function.

repo: exaloop/codon


text:
Error：Tuple from_py overload match problem

The following code snippet will result in a compilation error
@python
def t3() -> tuple[pyobj, pyobj, pyobj]:
    return (1, 2, 3)

@python
def t2() -> tuple[pyobj, pyobj]:
    return (1, 2)

@python
def t33() -> tuple[pyobj, pyobj, pyobj]:
    return (1, 3, 5)

def test1(a, b, c):
    return a + b + c

def test2(a, b):
    return a + b

print(test1(*t3()))
print(test2(*t2()))
print(test1(*t33()))

test_py_dec.py:10:1-41: error: 'Tuple[pyobj,pyobj,pyobj]' does not match expected type 'Tuple[T1,T2]'
╰─ test_py_dec.py:21:14-17: error: during the realization of t33()

Hi @victor3d
Thank you for reporting this---looks like a typechecker bug. Will need to check what is going on here.

Fixed in #604.


text:
🛑 Portfolio is down

In 4d5a0dc, Portfolio ($SECRET_P_SITE) was down:

HTTP code: 404
Response time: 461 ms

Resolved: Portfolio is back up in 1182240.

repo: exand/upptime


text:
[Opinions] Consider using our own MIME type and extension

I have plans to implement file sharing and file handling features for Excalidraw. For these to work properly, we should store files with their own extension (bikeshedding proposal: .excalidraw) and probably mint a new MIME type (bikeshedding proposal: application/vnd.excalidraw+json), albeit this is probably more of academic nature. At this point, I would like to get your thoughts on switching from .json to .excalidraw (or whatever the bikeshedding results in). Thanks!

Have you tried to download a file?! We are already using .excalidraw as an extension.

@lipis we actually don't when using Native File System API.

[W]e actually don't when using Native File System API.

This is https://github.com/WICG/native-file-system/issues/80 and then the current MIME type taking precedence: https://github.com/excalidraw/excalidraw/blob/722c498abea3ca3a000f7384f5d6611c2fd5bd73/src/data/json.ts#L33
So if the legacy approach already uses .excalidraw, can I safely assume you're fine with it in the general case?

https://github.com/excalidraw/excalidraw/blob/722c498abea3ca3a000f7384f5d6611c2fd5bd73/src/data/json.ts#L31
OK.. haven't see what is actually going on.. but yes, I'm down to have a proper MIME and .excalidraw extension for all.

authors: dwelle lipis tomayac

repo: excalidraw/excalidraw


text:
Remove the "options" shorthand

In the README we define a shortcut to include options with a sub-tree even though we are using the shorthand notation:

or, if you are using the shorthand for a single subtree, set options under an options key:
root: intro
options:
  caption: Subtree Caption
  hidden: False
  maxdepth: 1
  numbered: True
  reversed: False
  titlesonly: True
items:
- file: doc1
  options:
    titlesonly: True
  items:
  - file: doc2

I'd be inclined to just force people to use the "verbose" subtrees method, rather than special casing a new keyword:
root: intro
subtrees:
- caption: Subtree Caption
  hidden: False
  maxdepth: 1
  numbered: True
  reversed: False
  titlesonly: True
  items:
  - file: doc1
    subtrees:
    - items:
      - file: doc2
      titlesonly: True

Since we require more "verbosity" in the case of specifying options (via introducing a new keyword), I feel like we might as well just use re-use a pre-existing verbose structure, rather than defining a new one. What do you think @chrisjsewell ?

let's just keep it as-is, I agree it's nicer to not force people to use part: in jupyter book

repo: executablebooks/sphinx-external-toc


text:
robot-simulator: Rewrite tests to use hspec with fail-fast.

Rewrite tests to use hspec.
Remove old tests.
Add tests to match x-common.
Remove import of Robot in test suite.
Remove export of Robot in example solution.
Remove export of Robot in stub solution.
Remove instructions to derive (Eq, Ord) in stub.

Related to #211.
This exercise is too distant from what is defined in x-common, so it will probably be good to rewrite it. I tried to leave comments about the deviations to make the task easier.
I also simplified the interface so that it's not necessary to export the Robot data type. This is recommended for better modularization and allows more creative solutions.

:+1: if you add the missing space

authors: petertseng rbasso

repo: exercism/xhaskell


text:
Verify "Largest Series Product" exercise implementation

There was some confusion in this exercise due to the ambiguous use of the term consecutive in the README. This could be taken to mean contiguous, as in consecutive by position, or as in consecutive numerically. The the README has been fixed (https://github.com/exercism/x-common/pull/200).
Please verify that the exercise is implemented in this track correctly (that it finds series of contiguous numbers, not series of numbers that follow each other consecutively).
If it helps, the canonical inputs/outputs for the exercise can be found here:
https://github.com/exercism/x-common/blob/master/largest-series-product.json
If everything is fine, go ahead and just close this issue. If there's something to be done, then please describe the steps needed in order to close the issue.

This is not a problem with the Scala exercise.

authors: kytrinyx ricemery

repo: exercism/xscala


text:
Make this an EIP

This interface would be useful as a standard. I propose writing an EIP and submitting it to the EIPs repository at https://github.com/ethereum/EIPs.
If you don't want to do it, I might :)

This interface would be useful as a standard. I propose writing an EIP and submitting it to the EIPs repository at ethereum/EIPs.
If you don't want to do it, I might :)

Sure. Would be great. This was the interface we used for CFA btw:
https://github.com/exo-digital-labs/ERC721R/blob/main/contracts/cryptofighters/IERC721R.sol
Happy to help around an official EIP as well.

Would you be okay if I released the interface (and/or a modification of it) under CC0?

Would you be okay if I released the interface (and/or a modification of it) under CC0?

Yes, I'm fine with that

See https://eips.ethereum.org/EIPS/eip-5507. All discussions should be moved to https://ethereum-magicians.org/t/eip-5507-refundable-nfts/10451.


text:
[Feature Request] Timestamp on EOL wh connection

When you set a connection EOL pathfinder should mark the time into the db and show it (maybe as mouseover), so people get an idea about "how long" this thing is already EOL.

Technically you can see this on the info menu when right clicking on the map.  The only thing to be careful of is if the linkage is updated the timer will change to whatever was most recently done to update it.
http://imgur.com/h7Ydlpp

It is a nice workaround for now, thanks! Although a bit flunky, seeing that people touch stuff all the time, but better then nothing atm.
Still giving that table another row with a timestamp and show that on mouseover shouldnt be to hard to implement and it would give a solid answer to the question when it was set and not rely on chance that this was indeed the last edit

Can it also be implemented based around the type of connection if the sig details are recorded to auto purge the hole from the map?
Yes we may not know when the hole spawned but if the timer to purge it is set to Max 24 hours that will ensure the old sigs are purged from the DB to save space and clean up systems once the connection dies.

I added a new "EOL timer" to the map
The timestamp for "set to EOL" on connections, is now stored in system_signature table.
There is a new "show EOL timer" icon available to show that information on a map

This will be awesome showing the EOL Timers..

It´s already implemented and waiting for the next release (probably this weekend)

authors: Bingmano Tupsi dnolen exodus4d rmcginnis


text:
Refactor certbot-dns-exonet to current Exonet standards

What does it do?

Refactor plugin to current Exonet standards.
Bump python version to a minimum of python 3.7.2 and maximum of python 3.10.
Improve structure of plugin.

Check readme for changes in usage.
Squash and merge pls.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@faaebed). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             master       #22   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         3
  Lines             ?       101
  Branches          ?         4
==========================================
  Hits              ?       101
  Misses            ?         0
  Partials          ?         0

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

authors: Brianvanwessel codecov-commenter

repo: exonet/certbot-dns-exonet


text:
When updating datarule 'rule' it says it updates it but does not

$ exo spec CIK spec.yaml --create
Running spec on: RID
updated rule for datarule_event_log_timeout
$ exo spec CIK spec.yaml
Running spec on: RID
spec expects rule for datarule_event_log_timeout to be:
{"timeout": {"repeat": false, "timeout": 3888000}}
...but it is:
{"timeout": {"repeat": false, "timeout": 6000}}

I can't reproduce it. Are we on the same version?
$ exo --version
Exosite Command Line 0.9.16
$ CIK1=`curl cik.herokuapp.com`
$ exo info $CIK1 highTemp | jq .description.rule
{
  "timeout": {
    "repeat": false,
    "timeout": 3888000
  }
}
$ vi testspec.yaml
$ exo spec $CIK1 testspec.yaml --create
Running spec on: f84cee4c8ae88b72de4b512f63af05186d7e31b5
updated rule for highTemp
$ exo spec $CIK1 testspec.yaml
Running spec on: f84cee4c8ae88b72de4b512f63af05186d7e31b5
$ cat testspec.yaml
dataports:
    - alias: temp
      format: float

datarules:
    - alias: highTemp
      format: float
      subscribe: 21483ca91fab9c1c8b5f087c835a3a49cc6b7e6c
      rule: {"timeout": {"repeat": false, "timeout": 6000}}
$ exo info $CIK1 highTemp | jq .description.rule
{
  "timeout": {
    "repeat": false,
    "timeout": 6000
  }
}

I see this issue only if I have retention set in the datarule.
$ cat repro.spec
dataports:
-   alias: device_event_log
    format: string
datarules:
-   alias: datarule_event_log_timeout
    format: integer
    retention:
        count: 10
        duration: infinity
    rule:
        timeout:
            repeat: false
            timeout: 3888000
    subscribe: device_event_log
$ CIK=`curl cik.herokuapp.com`
######################################################################## 100.0%
$ exo spec $CIK repro.spec --create
Running spec on: 43c5030ab69ef2e0f7bf08b2762a278a119546c6
device_event_log not found.
Creating dataport with name: device_event_log, alias: device_event_log, format: string
datarule_event_log_timeout not found.
Creating datarule with name: datarule_event_log_timeout, alias: datarule_event_log_timeout, format: integer, rule: {'timeout': {'repeat': False, 'timeout': 3888000}}
$ vi repro.spec
$ exo spec $CIK repro.spec --create
Running spec on: 43c5030ab69ef2e0f7bf08b2762a278a119546c6
updated rule for datarule_event_log_timeout
$ exo spec $CIK repro.spec
Running spec on: 43c5030ab69ef2e0f7bf08b2762a278a119546c6
spec expects rule for datarule_event_log_timeout to be:
{"timeout": {"repeat": false, "timeout": 6000}}
...but it is:
{"timeout": {"repeat": false, "timeout": 3888000}}
spec expects subscribe for datarule_event_log_timeout to be 5461692a907e4336c4856a99f934ce662d451928, but they are not.

Fixed in 0.9.17

authors: dweaver maanenson

repo: exosite/exoline


text:
spec --create with subscriptions doesn't always work.

spec --create with subscriptions doesn't always work.
Sometime you get a dataport without the subscription.  Need to investigate and narrow down failure cases.

This may have been fixed in 0.9.17. Let me know if you see it again.

authors: dweaver tadpol


text:
Post install hook failing on ios build

Build/Submit details page URL
https://expo.dev/accounts/ahmedprusevic/projects/polaris/builds/b3057f65-7eb8-4b53-a245-55ba8cb894c2
Summary
Running post install hook on eas pipeline fails on ios, it is trying to run openapi-generator-cli generate command which is supposed to make http request to my server (not sure weather this makes any change) ,
node version in nvm is v18.18.0 to match the one from the image
It is passing on android build so really wierd issue
Managed or bare?
Bare
Environment
expo-env-info 1.2.1 environment info:
    System:
      OS: macOS 15.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
      Yarn: 1.22.22 - ~/.nvm/versions/node/v20.15.1/bin/yarn
      npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
    Managers:
      CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1
    IDEs:
      Android Studio: 2024.1 AI-241.19072.14.2412.12360217
      Xcode: 16.1/16B40 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~51.0.36 => 51.0.36
      expo-router: ~3.5.23 => 3.5.23
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.74.5 => 0.74.5
      react-native-web: ~0.19.10 => 0.19.12
    npmGlobalPackages:
      eas-cli: 13.2.3
    Expo Workflow: bare

Detailed check results:

The following issues were found when validating your dependencies against React Native Directory:
No metadata available: @dev-plugins/react-query, @hookform/resolvers, date-fns, i18next, jotai, lodash.debounce, react-native-chart-kit, styled-components, zod
Advice:
- Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

The following packages should be updated for best compatibility with the installed expo version:
  expo@51.0.36 - expected version: ~51.0.39
  expo-dev-client@4.0.27 - expected version: ~4.0.29
  expo-router@3.5.23 - expected version: ~3.5.24
  expo-splash-screen@0.27.6 - expected version: ~0.27.7
  react-native-svg@15.7.1 - expected version: 15.2.0
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies
Advice: Use 'npx expo install --check' to review and upgrade your dependencies.

Error output
No response
Reproducible demo or steps to reproduce from a blank project
try running openapi-generator-cli generate command that fetches schema from some server in eas-build-post-install hook on ios build

I'm not sure what's wrong here, but can you just try to run it as npx -y @openapitools/openapi-generator-cli ...?

I've tried that as well (still failing) attaching screen shot for the reference

what does openapischema.js do inside?

Just generates openapitools.json based on env copying file contents here
const output = {
  $schema:
    "./node_modules/@openapitools/openapi-generator-cli/config.schema.json",
  spaces: 2,
  "generator-cli": {
    version: "7.10.0",
    generators: {
      "v3.0": {
        generatorName: "typescript-axios",
        output: "openapi",
        // eslint-disable-next-line no-undef
        inputSpec: `${process.env.EXPO_PUBLIC_API_URL}/swagger/doc.json`,
      },
    },
  },
}
const jsonString = JSON.stringify(output)

fs.writeFileSync("openapitools.json", jsonString)

double checked weather env variable is present in eas.json it is, since the same command passes for android build

authors: ahmedprusevic szdziedzic

repo: expo/eas-cli


text:
[eas-cli] add isGitWorkingTreeDirty to EAS Update publish command

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Builds track if the git working tree was dirty, but updates do not:
https://github.com/expo/eas-cli/pull/1499#pullrequestreview-1165131094
How
I added isGitWorkingTreeDirty to the PublishUpdateGroupInput payload and also showed the asterisk at the end of the commit in the publish command summary if the working tree was dirty.
Test Plan
I tested with a local build of the CLI and the website to render the dirty state asterisks:

TODO: update with website screenshot

/changelog-entry [new-feature] [add isGitWorkingTreeDirty to EAS Update records]

/changelog-entry new-feature add isGitWorkingTreeDirty to EAS Update records


text:
Integration with TabBarIOS

I'm new to react native and am hoping someone can provide some tips or steer me in the right direction regarding integrating ex-navigator with TabBarIOS. Currently my layout looks like below with the Menu a TabBarIOS component. My question is, how can integrate routes into the menu? Or do the ExNavigator 'scenes' have to encapsulate the menu components? This last option isn't really good for my layout though. BTW I'm using redux and did read about using actions to change routes, is that something I should look at?
Appreciate any help.
render() {
  return (
    <View style={styles.container}>
      <ExNavigator
        initialRoute={Router.getHomeRoute()}
        style={{flex: 1}}
        sceneStyle={{paddingTop: 64}}
      />
      <Menu router={Router} />
    </View>
   )
 }

This repo has an example using ExNavigator and TabNavigator. Setup should be the same with TabBarIOS: https://github.com/wesley1001/ex-navigator-tabnavigator-demo

@samuelkraft this looks perfect. Had a feeling the router might have to render the tab bar. Thanks for the help!

authors: pulpfree samuelkraft

repo: exponentjs/ex-navigator


text:
Add NetHunt to companies using express.

Thank you for your great work! We are tour fans) ❤
Please add us to the list of companies 🙏🏻

Hey @SvitlanaTsupryk-jul18! Thanks for your PR! Unfortunately it can't be accepted because we are no longer extend this list of companies.
You can check relevant discussion - https://github.com/expressjs/discussions/issues/105

Hey @SvitlanaTsupryk-jul18! Thanks for your PR! Unfortunately it can't be accepted because we are no longer extend this list of companies.
You can check relevant discussion - https://github.com/expressjs/discussions/issues/105

Thanks 🙂

Thanks 🙂


text:
deps: basic-auth@^2.0.1

Updated as part of this: https://github.com/expressjs/discussions/pull/290
deps: basic-auth@^2.0.1

Thanks for your contribution @Machinarius! :heart:
The CI is failing as Node@0.8 does not support ^, so I flagged this PR as a major change that will be included in the next major release of this library.

authors: Machinarius UlisesGascon

repo: expressjs/morgan


text:
Rprint macros

Add a family of printing macros (resolves #36)
There's an automated test in a separate commit.  I don't know how much value this is really adding, but was curious whether it was even possible, without resorting to extra helper scripts.  The answer is yes, but it's a little finicky.  Note that I had to remove a call to end_r elsewhere in the test suite because -- while R still mostly works after calling this -- its tmp directory no longer exists, so the fifo trick I used in the rprintln! test won't work.

Out of interest.
end_r is a problem with tests as if you shut R down, it can't be restarted.
We still have problems with concurrent tests as R is strictly single threaded
and will crash if run concurrently in a single process.

I think the "concurrent testing" issues are a little different, in that R is very non-thread-safe (global variables, I guess).
But even with a single thread running tests, calling end_r is problematic since I'm not sure there's a trustworthy way of knowing which tests are going to be run last.  In my hands, just exiting without calling end_r doesn't seem to cause any problems, but might be worth thinking about ways to call it at the end of the test run anyway.
I don't believe Rust has an official "call before exit" API, but I think we could install a bog standard atexit function...

authors: andy-thomason dasmoth

repo: extendr/extendr


text:
SKIP Exception if used in @BeforeSuite - throws null pointer exception

LearnTestNG.zip
If we use SKIP Exception in the @BeforeSuite then ITestListener throws null pointer exception, also all the test skips and executed(failed), so we can see the entry as Test1 (skipped) and Test1(Failed).

@sen1983  thank you, I am able to reproduce.

Hi Anshoo,
Still we are getting the same issue, Please include @BeforeSuite with Skip Exception in Class1 and when executed throws null pointer exception.
extentreports-testng-adapter-master.zip

Ok, so the same issue within onTestFailure.  What baffles me is that getThrowable() is null on both skipped and failure.  I will push the fix in a few mins.

Hi Anshoo,
I was the facing the same exception again but later identified the root cause. Actually I am using TestNG 6.14.3 eclipse plugin. Then I have downgraded the TestNG version to 6.9.10 and it is working fine.
Could you please fix the same for the latest version of the TestNG 6.14.3?
Thanks
Senthil

I am unable to reproduce using testng:6.14.3 with the last commit.

Hi Anshoo,
Its not working, believe me still this issue exists with ITestListener. Attached the project below i have included only ITestListener listener alone for testing.
TestNGAdapter.zip
I have just added Skip exception in beforesuite and a new test for skip exception.
Please check it and let me know if anything I did wrong in the code.

Please try with the attached:
TestNGAdapter.zip

Thanks for the update, now its executing fine, but the report is incorrect, so raising new issue.


text:
Support google workload identity federation

Support for workload identity federation using credential configuration files.
Currently, if the credential configuration files is specified as secretAccessKeySecretRef, the following error will occur.
failed to create GCP secretmanager client: failed to process the provided JSON credentials: google: read JWT from JSON credentials: 'type' field is "external_account" (expected "service_account")

we have similar setup:

manually created workload identity federation pool (with expected audience)
attach connected service account
generate service account credentials (without secret)

sample:
{
  "type": "external_account",
  "audience": "//iam.googleapis.com/projects/<projectID>/locations/global/workloadIdentityPools/<poolName>/providers/<providerName>",
  "subject_token_type": "urn:ietf:params:oauth:token-type:jwt",
  "token_url": "https://sts.googleapis.com/v1/token",
  "service_account_impersonation_url": "https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/<serviceAccountName>@<projectID>.iam.gserviceaccount.com:generateAccessToken",
  "credential_source": {
    "file": "/var/run/secrets/tokens/psat",
    "format": {
      "type": "text"
    }
  }
}

So need to exchange this credentials + SA token (see credential_source) for GCP token.
CRD might look something like:

apiVersion: generators.external-secrets.io/v1alpha1
kind: GCRAccessToken
metadata:
  name: gcr-gen
spec:
  projectID: "my-project"
  auth:
    jwt:
        workloadIdentityPool: foo
        provider: bar
	    serviceAccountRef:
	        name: service-account-token-to-use
	    	audience:
	    	  - foo
	    	  - bar

Let me reopen it, seems there is interest and this is a good opportunity to contribute :)

Any plans to support Workload Identity Federation?

Any updates on the matter?
It would be highly useful to let applications running on-premises or on other cloud providers use workload identity federation to authenticate to GCP secret Manager. (Also applies for GCRAccessToken generator)

I would also like to see support for this for similar reasons, but I think there are two different use cases here:

Use workload identity federation strictly to access secrets. For this I would propose a CRD extension. ESO should request a token using the K8s TokenRequest API for the specified k8s service account.
With this it is possible to specify the namespace of the service account in the principal.
Example:

apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
  name: gcp-store
  namespace: external-secrets
spec:
  provider:
    gcpsm:
      projectID: project-id
      workloadIdentityFederation:
        serviceAccountRef:
          name: team-a
          namespace: team-a-ns # only for cluster stores

(Alternatively we could add a federated flag and still use the existing workloadIdentity).
This would mean we have to generate the GOOGLE_APPLICATION_CREDENTIALS ourselves, similar to https://github.com/external-secrets/external-secrets/issues/1946#issuecomment-1667630229

Add something that actually generates GCP tokens (i.e. does the token exchange) and provides it in a secret, so it can be used for applications that cannot be used with workload identity federation.
Sounds like an interesting idea, but feels a bit out-of-scope for ESO. I also have no idea how to do this token exchange.

Add something that actually generates GCP tokens (i.e. does the token exchange) and provides it in a secret, so it can be used for applications that cannot be used with workload identity federation.
Sounds like an interesting idea, but feels a bit out-of-scope for ESO. I also have no idea how to do this token exchange.

This can actually be a Generator. we have similar Generators for AWS regarding STS tokens being cooked.
However - it is good to mention that these type of features are really community driven. Maintainers will do that if they wish to do so - maintainer focus would either be things critical to the project or maintenance activities.
If you still need the feature, but don't have the in-house knowledge to contribute back to the project - I'd suggest to go for vendors/consultancy companies to do that for you. Or alternatively, reach out to one of the contributors/maintainers for and negotiate a bounty 😄

Sorry, my comment wasn't meant as a "please implement that for me" 😄  but rather as looking for feedback on the ideas, especially the CRD change and that these are two different things (re. original commenters). Should have phrased that differently.
I will probably tackle the first one myself, as I have use for that.

Sorry, my comment wasn't meant as a "please implement that for me" 😄 but rather as looking for feedback on the ideas, especially the CRD change and that these are two different ideas (re. original commenters). Should have phrased that differently.
I will probably tackle the first one myself, as I have use for that.

No worries!
Re: WorkloadIdentityFederation vs WorkloadIdentity - I think adding a new WorkloadIdentityFederation block works just fine, and it is easily forward/backwards compatible. However, do note the namespaces on ClusterSecretStores need to be a pointer, as if the user does not provide a namespace, we should use the namespace of the referrent ExternalSecret (this is a somewhat hidden feature of Referent Authentication)

authors: MariusSchiffer gusfcarvalho moolen nerahou nikotih tetsuya28 tetwatan

repo: external-secrets/external-secrets


text:
Make azure unit tests follow the pattern that we are using everywhere

Table driven with tweak anonymous functions. Basically all providers are doing that, and we can adapt azure to follow same pattern.

@humrenan wants to Take over this one. Marking him here so we know :)

Closed by https://github.com/external-secrets/external-secrets/pull/584

authors: knelasevero sebagomez


text:
Build TCP connection, packet framing, RLPx, DevP2P Wire Protocol and Eth Wire Protocol

This patch starts to build TCP sessions and packet framing into ExWire. Once we get done framing (and protocol negotitation), we'll have a more or less working RLPx implementation (though, there's lot of details to fill in). Currently, a lot of code is dumped where it needs to be to get things to work (e.g. TCP should really call our to stub code). Additionally, we're only just beginning to get the framing code to work (the spec is, yet again, under-documented or strictly incorrect, so we're basing it off a mix of Geth and Parity's code). Luckily, geth included a test case so that's good. All in all, at this point, we can connect to a TCP node, negotiate keys and try to send packets. The key exchange (ECIES) looks to be right based on test cases, but I'm not 100% positive the derived keys are correct yet (see the TCP module). Luckily, the clients are pretty happy to accept and report any isuses, so we'll be able to diagnose anything that's incorrect after we finish our framing and de-framing code.

@masonforest This should be ready to review. We can now connect and pull blocks from a DevP2P peer :D :D :D :D

Yeah, I'll merge now and then go back and clean up some of the functions. It'll be nice to have this mostly done and get to move on to more fun things (like syncing the entire blockchain :))


text:
Feedback aiXcelerate Aachen 2022

Feedback:

search function for callpaths in selection view to filter the callpaths
gui does not work/start on newer MacOS versions
some gui functions including weak/strong scaling selection, all right click menus, do not work when using x-/port forwarding when running extrap-gui on the cluster
measurement points plot is showing data incorrectly when using only one parameter (not very intuitive for users that don't know about it)
weak/strong scaling selection missing for other input methods than Cube files... would be easier for the user if extra-p automatically multiplies the number of processes with the measured metric than doing it manually...

Gui does not work/start on newer MacOS versions is adressed in 5bce7e9

Ignore:

some gui functions including weak/strong scaling selection, all right click menus, do not work when using x-/port forwarding when running extrap-gui on the cluster

Tool is not intended to be used like that.

repo: extra-p/extrap


text:
🛑 Extratone is down

In 9a18e8b, Extratone (https://www.extratone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Extratone is back up in 3997682.

repo: extratone/up


text:
Add Github Sponsor or other way to "tip"

I would love to support development financially.

Hi Mike!
Glad to hear you'd like to support development. However we're not trying to make money on the project and your activity already quite useful, thank you! If you'd like to do something else for the project, please just share it with your colleagues, we will be very grateful!

Will do! I will be following development for sure and thank the team for the excellent work. I wish I was stronger in Swift/SwiftUI to jump into some issues that prevent some more advanced used cases, like nested Grid preference issue #16.

repo: exyte/Grid


text:
Feature requirement: Support IOS 10.x

My company works with ipads 4th gen :(
latest ios is 10.3 :(
Is there a way to support ios 10?

SwiftUI is supported only on iOS 13 and higher. So there is no way to run it on iOS 10.

authors: denis-obukhov sdyalor


text:
Adds support for iOS 18

swiftui-itrospect already has support for iOS 18.
fixes #57

Oh, I'm sorry I didn't notice this was a PR, I should've merged it of course( Ina any case thank you for your work, have a great day!

repo: exyte/ScalingHeaderScrollView