text:
优化性能

目前版本性能较差,需要大部分优化,包含

节点布局算法优化
边布局算法优化
拖拽节点位置计算优化
分页布局算法优化

优化过程将记录在此issue

点布局优化
目的: 减少dom操作和复杂计算次数
原计算:

 .attr('x', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
      })
      .attr('y', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
      })
      .transition()
      .duration(1000)
      .attr('cx', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
      })
      .attr('cy', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
      })

总共进行4次复杂计算并且多次操作dom
可以优化为只计算一次,将计算结果插入到原数组中
.attr('x', (node, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        node.x = isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
        return node.x
      })
      .attr('y', (node, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        node.y = isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
        return node.y
      })
      .transition()
      .duration(1000)
      .attr('cx', (node, idx) => {
        return node.x as number
      })
      .attr('cy', (node, idx) => {
        return node.y as number
      })

    sideContainer
      .append('text')
      .attr('id', node => node.id + 'text')
      .style('cursor', 'pointer')
      .attr('text-anchor', 'middle')
      .attr('dominant-baseline', 'middle')
      .attr('fill', '#fff')
      .style('font-size', 14)
      .attr('x', x)
      .attr('y', y)
      .transition()
      .duration(1000)
      .attr('x', (node, idx) => {
        return node.x as number
      })
      .attr('y', (node, idx) => {
        return node.y as number
      })
      .text(node => node.type)
    sideContainer
      .append('text')
      .attr('x', x)
      .attr('y', y + nodeRadius + 10)
      .attr('text-anchor', 'middle')
      .style('font-size', 10)
      .text(item => item.name)
      .attr('id', item => `${item.id}name`)
      .style('opacity', 0)
      .transition()
      .duration(1000)
      .attr('x', (node, idx) => {
        return node.x as number
      })
      .attr('y', (node, idx) => {
        return node.y as number + nodeRadius + 10
      })
      .style('opacity', 1)

拖拽新能优化
目的: 减少dom操作次数
原代码:
.on('drag', function (event: any) {
        const currentElement = d3.select('#drag')
        const tempArr = currentElement.attr("transform").split(",");
        // 获取当前的x和y坐标
        const x = +(tempArr?.[0]?.split("(")[1] || 0);
        const y = +(tempArr?.[1]?.split(")")[0] || 0);
        // 当前坐标加上拖拽的相对坐标
        // 即新坐标相比原坐标的偏移量
        currentElement.attr(
          "transform",
          `translate(${x + event.dx / size}, ${y + event.dy / size})`
        );
      })

可以看到,每次拖拽,都会通过d3获取id=drag的元素,和其内部的transform属性,这方面可以进行优化
优化方法:

使用全局变量记录transform的两个偏移

优化后代码:
.on('drag', function (event: any) {
        // 更新记录
        canvasX += event.dx / size
        canvasY += event.dy / size
        // 当前坐标加上拖拽的相对坐标
        // 即新坐标相比原坐标的偏移量
        currentElement.attr(
          "transform",
          `translate(${canvasX}, ${canvasY})`
        );
      })

点布局优化
目的: 减少dom操作和复杂计算次数
原计算:
 .attr('x', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
      })
      .attr('y', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
      })
      .transition()
      .duration(1000)
      .attr('cx', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
      })
      .attr('cy', (_, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        return isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
      })

总共进行4次复杂计算并且多次操作dom
可以优化为只计算一次,将计算结果插入到原数组中
.attr('x', (node, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        node.x = isInside
          ? x - calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
          : x + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.cos(Math.abs(angle - 90) / 180 * Math.PI)
        return node.x
      })
      .attr('y', (node, idx) => {
        const angle: number = (idx + 1) * maxAngle / (nodes.length + 1) + index * maxAngle
        node.y = isInside
          ? y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
          : y + calcBasicDistence(nodes.length, maxAngle, basicDistence) * Math.sin((angle - 90) / 180 * Math.PI)
        return node.y
      })
      .transition()
      .duration(1000)
      .attr('cx', (node, idx) => {
        return node.x as number
      })
      .attr('cy', (node, idx) => {
        return node.y as number
      })

    sideContainer
      .append('text')
      .attr('id', node => node.id + 'text')
      .style('cursor', 'pointer')
      .attr('text-anchor', 'middle')
      .attr('dominant-baseline', 'middle')
      .attr('fill', '#fff')
      .style('font-size', 14)
      .attr('x', x)
      .attr('y', y)
      .transition()
      .duration(1000)
      .attr('x', (node, idx) => {
        return node.x as number
      })
      .attr('y', (node, idx) => {
        return node.y as number
      })
      .text(node => node.type)
    sideContainer
      .append('text')
      .attr('x', x)
      .attr('y', y + nodeRadius + 10)
      .attr('text-anchor', 'middle')
      .style('font-size', 10)
      .text(item => item.name)
      .attr('id', item => `${item.id}name`)
      .style('opacity', 0)
      .transition()
      .duration(1000)
      .attr('x', (node, idx) => {
        return node.x as number
      })
      .attr('y', (node, idx) => {
        return node.y as number + nodeRadius + 10
      })
      .style('opacity', 1)

进一步结合线布局优化,去除掉属性x和y,只设置cx和cy

因为线布局现在并不需要通过dom操作获取当前节点的坐标,改使用js数组记录的方式(注意,图rerender时需要清除记录值)

线布局优化
目的: 减少dom操作即计算
优化步骤:

舍弃原本通过节点id通过d3操作dom拿到节点坐标画线的方式
画节点的时候将计算后的节点坐标存在nodes数组中,直接取数组元素得到节点坐标绘制边

修改量较大,代码就不贴了

注意: 布局优化并不能优化拖拽画布体验,详情见总结

总结
以上布局优化只能减少首次渲染的时间(经过优化后实测拿到1w2条数据之后可以立即画出图),但是并不能优化拖拽画布的体验,我觉得可能的原因如下

影响拖拽画布性能的根本原因是画布内dom元素的数量

在优化的过程中我发现,如果我们在相同节点数据量的情况下,不绘制边,描述和箭头,拖拽无卡顿显现,此时总共的dom节点数量为3*1w2

ciecle的数量+text(类型)的数量+text(节点名称的数量) * 1w2,包裹他们的g元素数量暂且忽略不计

加上线不绘制描述和箭头,稍有卡顿,不明显,此时总dom节点数量为4*1w2

以上基础加上path的数量1w2

加上描述和箭头, 卡顿,甚至难以拖动此时总dom节点数6*1w2

以上基础加上textPath(描述)``textPath(箭头) * 1w2

总计节点接近10w,还是得想办法减少dom节点的数量

优化修改边性能


text:
重构代码/优化性能

移除对d3的依赖同时支持SSR
重构d3移动画布/重置画布/当前节点居中等功能
使用React18 Hooks/Memo等优化性能

#12

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Sync providers: extract into its own folder

Context 📝
The implementation of sync providers in the plugin is repetitive and can be optimized. The aim of this task is to gather together as much of the UI & logic into its own realm, to set a base that allows us to publish as an independent package that can be flexible enough for future providers.
Acceptance Criteria 🛠

Move all related constants, methods and component into a single folder in the plugin
Improve tests

🎯 A package that lets users create/choose a sync provider, and then have a button that Import variables which would basically just read local variables from Figma, and push those to the repository. So in effect we'd have all of these parts in the Figma plugin already, but we want those to be part of a new plugin that does just that. As in it'd be one-directional for now (pushing to git), but eventually would do both.

⚠ WIP branch: https://github.com/tokens-studio/figma-plugin/tree/feat/3000-extract-sync-providers

repo: tokens-studio/figma-plugin


text:
fix: use std::os::fd on HermitOS

Issue https://github.com/rust-lang/rust/issues/126198 was fixed and added to 1.81.
fixes: #1803

Our MSVR is 1.70, so this will have to wait until we bump it.

Since that bump will be a long time from now, I'm closing this. Thank you @joeydewaal, we'll reopen this once we bump the MSRV.

source: gharchive/pull-request

authors: Thomasdezeeuw joeydewaal

repo: tokio-rs/mio


text:
Core::spawn should expect Error=Void not Error=()

Since spawn never looks at the results of the future, the return value ought to be completely devoid of any useful information to reduce the risk that the user might unintentionally forget about the result.
The current choice of Future<Item=(), Error=()> still has one bit of information: it’s possible to distinguish between Ok(()) and Err(()) results.  It really ought to return Future<Item=(), Error=Void>, which means the Future is guaranteed to succeed.
It’s not a big problem by any means, just kind of quirky in my perspective.

Yes unfortunately there's no shared "void" type right now across these libraries. The futures crate for example has a number of situations where the error should be void vs () as it is today.
This is something that we'll definitely want to evaluate for futures 0.2

What about using the void crate?

I don't think we want to pull in another crate. Either way, changing the type will be a breaking change which requires a version bump.
I think at this point, we'll be better off waiting for upcoming changes to rust-lang to hit stable.

Just for reference, this is being discussed in futures as well: https://github.com/alexcrichton/futures-rs/issues/476
If futures ended up exporting Void I suppose tokio could leverage that?

Indeed!

authors: Rufflewind alexcrichton carllerche srijs vks

repo: tokio-rs/tokio-core


text:
[Backend]: refactor codebase for supporting more providers

Unfortunately mangareader seems down ( showing its for sale ).
Currently manga-api only relies on mangareader for data, but since it went down we gotta change provider.
Well I think its better if we can change whole codebase for supporting different providers, we need to scale ( currently this architecture isnt scalable ).
We will prolly change folder structure as well like
url can be like: /api/<provider>/<query>/
List of manga providers we can use: https://github.com/anshumanv/awesome-anime-sources#manga
Note: we might need to use selenium instead, well but its better if we can do this with selectolax itself.

P.S: mangareader isnt down, I entered wrong url :).
But we need to support multiple providers.
If anyone looking forward to contribute, please write here :heart:

Codebase refactoring is done. :fire:
Now need some more providers: we follow this pattern: provider_service_pattern
Also we take providers with SSR support, otherwise we need to use selenium to trigger javascript.
Way is slower  than selectolax.
To check use curl like this:
curl <provider_site_url>

If you can see full html then that site matches with our case, if the response contains something like:
Enable Javascript like context, then NO.

repo: tokitouq/manga-api


text:
crash on startup with iris enabled fabric 1.21.3

running cpm with iris on 1.21.3 will cause the game to crash on startup
latest.log
crash-2024-10-27_08.46.35-client.txt

I had this issue too

authors: AnukWarrior Lavengale


text:
X11 window is renamed after creation

In X11, using the window builder with with_title creates the window without a title and then very shortly after renames the window as it should.
The problem with that is that my window manager (i3) chooses on which desktop to open windows and whether to put them in floating mode based on their name, and sometimes it catches the window's name before it is changed, causing the window to briefly appear (in my case) in non-floating mode and then immediately after to go in floating mode (as it should be from the start); but the brief non-floating period can mess up other windows opened on the same desktop in i3.
I realize this is a very minor and specific nitpick, but I don't have that problem developing with GLFW, so surely it's possible to set a window's name directly as it is created on X11.

Please open an issue in winit instead: https://github.com/tomaka/winit/issues

authors: carado tomaka

repo: tomaka/glutin


text:
Wire up stop timeout for embedded Jetty server

This PR wires up the jetty stop timeout for use with embedded jetty.
It adds jettyStopTimeout to WireMockConfiguration and changes JettyHttpServer.finalizeSetup() to not overwrite the timeout value on setup.

@tomakehurst Would it be possible to release a new minor version with this change included?

👍
@tomakehurst Any update on the release for this? Thanks

repo: tomakehurst/wiremock

license_source: bigquery


text:
Running on specified GPU

Hi, How to run the analyzer on a second GPU or specified GPU node? For example, pytorch like framework allow us to run on cuda:1. I did not find a way to run this on specified node.

Facetorch indeed allows for the specification of GPU devices, similar to how you would do it in PyTorch. This can be done directly within the configuration files. Here are the steps you can follow to set a specific GPU device for running the analyzer:

Specify the Analyzer Device: In your configuration file, you can explicitly set the GPU device for the analyzer (or here in case you are not using the merged config file). This is done by setting the device in the same format used by PyTorch, for example, cuda:1 for using the second GPU. This setting ensures that all predictors run on the specified GPU.

Individual Predictor Device Configuration: If you require more granular control over the device allocation, such as assigning different predictors to different GPUs, you can do so by modifying the device setting for each predictor. Replace the ${analyzer.device} type placeholder in the configuration file with the specific device string, following the PyTorch format, e.g., cuda:0, cuda:1, etc.

repo: tomas-gajarsky/facetorch


text:
compare_user is a boolean when it shouldn't be

In the admin.py file on line 256 if compare_user := users_map.get(user.name, None) is not None: compare_user becomes a boolean instead of a User object. Re-writing to this should fix it:
compare_user = users_map.get(user.name)
if compare_user is not None:
to_operate = user.member_of - compare_user.member_of

Thanks for reporting this!
Redtape needs a lot of work, but I don't really think there is anything out there yet. So I'll try to make a end of the year push and bring this to a more stable state.

The first step will be to greatly extend our testing pipeline, as this could have been easily caught...

authors: dan-ludwig-vroom tomasfarias

repo: tomasfarias/redtape


text:
🛑 Real-time Markdown editor is down

In 8b27df3, Real-time Markdown editor (https://notas.saiyans.com.ve) was down:

HTTP code: 503
Response time: 5720 ms

Resolved: Real-time Markdown editor is back up in 16fc9c3 after 17 minutes.


text:
Speed up docker build by moving key generation into container startup

While going through the Dockerfile in https://github.com/tomav/docker-mailserver/pull/1194 I noticed a few things that can be done to speedup the container build (and also improve security imho).

during the build freshclam is run in https://github.com/tomav/docker-mailserver/blob/2107793f7f7cf47342f4bcaa2817b946126e25f3/Dockerfile#L103
this action takes a while and also and ultimatively ends with a message that clamd could not be contacted, so maybe it does not even serve a purpose.
-> should be moved into a startup script

mkcert.sh creates a private key for dovecot in https://github.com/tomav/docker-mailserver/blob/2107793f7f7cf47342f4bcaa2817b946126e25f3/Dockerfile#L121
Potentially security relevant
-> should be done per installation in a startup script

the container build created two dhparam files (for dovecot and postfix each) in https://github.com/tomav/docker-mailserver/blob/2107793f7f7cf47342f4bcaa2817b946126e25f3/Dockerfile#L124 and https://github.com/tomav/docker-mailserver/blob/2107793f7f7cf47342f4bcaa2817b946126e25f3/Dockerfile#L184
dhparam should rather be generated per installation and therefore at container startup (which is afaik already the case for the postfix dhparam anyways, meaning that it get generated twice).
-> there should be a single dhparam for the whole container that are used from both dovecot and postfix

what is the purpose of regenerating dhparam via cron in https://github.com/tomav/docker-mailserver/blob/2107793f7f7cf47342f4bcaa2817b946126e25f3/Dockerfile#L185?
-> should be removed, does not feel necessary to me.

For the first point freshclam downloads antivirus definitions. It tries to restart clamd and fails as clamd is not running, but that really doesn't matter, the antivirus definitions have been downloaded successfully. I would like to keep that in the build. If we move it to the startup script and freshclam fails (it does fail from time to time) we will be running without antivirus definitions and even if it succeeds it takes time. During that time we cannot receive messages (if we wait) or alternatively we will receive messages that we cannot check as clamd lacks its definitions.
If we rebuild the image on a daily basis (other JIRA) and run freshclam as part of the build we will always have antivirus definitions that are at most one day old from the get-go. That's not so bad and it is one thing less to do in the rather big startup script!

@fbartels are you working on this or do you want me to grab it?

@erik-wramner no I have not yet started with this. I wanted to finally close hadolint pr first. But you are welcome to take it over.

Solved by #1220.

authors: erik-wramner fbartels

repo: tomav/docker-mailserver


text:
[Q] Which version to download for Windows?

Currently there's 3 versions available for Windows:

0.26e
0.26hHT
0.26HTs

They all appear to be experimental based on the release notes, but there's no explanation anywhere of what the differences between these versions are.
Please provide more comprehensive release notes and update them as necessary if more files are added to a release.

...and it doesn't really matter.  Downloaded and installed one at random, and discovered network sync isn't supported yet.
Would be very nice to list the core features in the Readme and which features are currently supported and which ones aren't. For me, network sync is a crucial feature.
Looking forward to the continued development!  Haven't written any Pascal since Uni or I'd consider helping..

Thanks mwerle, the best way to select your download is from https://github.com/tomboy-notes/tomboy-ng/wiki/Releases
The raw github download pages show all sorts of things.
You are the first (I think) person to ask for network sync.  Can you tell me what network server you are using ?  Snowy and Rainly must be beyond their use by dates, I get the impression people don't trust AUTH2 anymore. ....

Haven't written any Pascal since Uni or I'd consider helping..
Yeah, me too ! I found it very easy to recall. And as a GUI designer, there is no equal.  The sync code is a pretty clear object model, should be easy to slot in a Auth2 client. Please consider......

I use https://github.com/cweiske/grauphel as my network sync server, which plugs into OwnCloud/NextCloud.  I've had pretty poor experiences with using shared drives such as Dropbox in the past so not keen to go back to that.
I'll take a look at the sync code.. but right now pretty busy updating some KSP mods, sorry ;)  Let me create a feature request for that just to track it.

authors: davidbannon mwerle

repo: tomboy-notes/tomboy-ng


text:
CWE-601 Security Vulnerability found in one of the transitive dependencies

Blackduck Scans reported vulnerability

@ganeshkumar-ks-by this package is unmaintained over 4 years. please use @react-google-maps/api instead.

repo: tomchentw/react-google-maps

license: mit


text:
feat(preventDuplicates): Changed to list

The prevent duplicates feature works by checking the previously rendered message with the current message and avoids duplicates. There is a test case which will not pass in the following situation - success('hello') --- followed by --> success('bye') --- followed by--> success('hello'). The last "hello" should not render until the previous "hello" has unmounted.
Now, the code maintains a list of messages that are currently being rendered. This makes sure that aforementioned issue doesn't happen.

@tomchentw The previous pull request helps us avoid the duplicate messages. Kindly approve this pull request since it completes the functionality.

@RangarajKaushikSundar I'd like to invite you to be a collaborator of this project. Are you interested?

@tomchentw I would be happy to.

Released v2.8.0

@RangarajKaushikSundar invited!

authors: RangarajKaushikSundar tomchentw

repo: tomchentw/react-toastr


text:
Benchmarking

Rough benchmarking on trivial hello world, a simple point of comparison.
Requires #9.

Closing in favour of #18

repo: tomchristie/apistar


text:
Pinning Messages

Is it possible to have a toggle on the website/a variable in the command line to have the bot post it's message and immediately pin it to the channel.
Optionally(ideally) message with an @admin (or @stitics) ping in the #gigglebot channel if it received the error that the pins channel is full so that can be corrected before the next one.

Somehow I'm just seeing this now.  Must have been a busy weekend
Absolutely.  I don't know much about pinned messages but I'll look into it

authors: stitics tomgigler

repo: tomgigler/GiggleMe


text:
Provide consumption-friendly event for Cluster Autoscaler's ScaleDown event for CA's ConfigMap

Contact Details
No response
Scenario
Provide consumption-friendly event for Cluster Autoscaler's ScaleDown event for CA's ConfigMap.
See https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-events-are-emitted-by-ca for more information
Relates to #123
Proposed Event Type
TBD
Proposed Event Payload
TBD
Raw Kubernetes Event
TBD
Source Component
Cluster Autoscaler

Requested more information in official event: https://github.com/kubernetes/autoscaler/issues/3991


text:
#83 Add bower.json

Basic Bower json as per spec: https://github.com/bower/spec/blob/master/json.md

Thanks, looks good!

authors: simison tommoor

repo: tommoor/tinycon


text:
IP address blocked when trying to run a search by bouding box.

Hello,
I'm trying to use the crawler to run a bouding box search in Florianopolis, SC, Brazil. But i'm having this output below when i try to run the search. Do you guys have any ideas of what could it be and how to solve it?
2018-09-21 16:30:43,295 INFO    Rectangle calculated: [-27.39, -48.36, -27.83, -48.56]
2018-09-21 16:30:43,295 INFO    Searching rectangle: zoom factor = 0, node = []
2018-09-21 16:30:43,952 WARNING HTTP status 400 from web site: IP address blocked. Waiting 1.0 minutes.
I believe i added all the configs necessary to run it.
Thank you. :)

Just found it.
Forgot to change de api_key.
Thank you.

repo: tomslee/airbnb-data-collection


text:
Fix #302

Fix a crash (ProgrammingError) when attempting to create a schema named like a SQL keyword (select, where, ...)
Allow to create a tenant named with only numbers (123).

@Tberdy Thanks for this

authors: Tberdy tomturner

repo: tomturner/django-tenants


text:
fix: read chunk data only right before sending

This way we are not keeping the whole file in memory which may fail on large files.
Closes #5

This is great thanks a lot @troggy !
This is a breaking change as the MultipartUploadChunk is user facing in some custom handlers, but as stated in the README, this module in its early phase (0.x.x) is subject to breaking changes so I think it's fine.
It makes me think that we definitely need to have some testing on this repo to avoid these kind of situations to go un-noticed.

I added a breaking change label for people to filter out what did change lastly. One on the 1.x.x versions, semver will apply.
I'll merge this now and release right after.

authors: toniopelo troggy

repo: toniopelo/modbox


text:
Google Map features

I just added a Google Map in my portfolio #14. There are many things we can do with this map. Here are some ideas:

center the map based on where the user is
add markers showing things like who has visited my website (connect with Google Analytics API and update real time?) and places that I've been to/want to travel to (could be hardcoded to start with)
add info windows

#14 addresses 1. a marker and a "You are here" infowindow tells user where they are. The map is also centered aroudn there.

Need to error handle when users don't have location service enabled.

Need to error handle when users don't have location service enabled.

Fixed in PR #14


text:
workflows: add --recursive flag to signing process (all)

Fixes #113 according to https://github.com/containers/podman/issues/21209

Strange, apt is trying to install qemu-user-static that does not exist on mirror. Shouldn't the workflow sync the repos beforehand?

#117 fixes the failing checks

No need to wait for the build test here, this won't test the signature step.

authors: RobusTetus travier

repo: toolbx-images/images


text:
Running Balance Not Working - Column Appears, but no number in it

Greetings,
I just enabled the "running balance" feature.
A new column appeared called "running balance."
But there are no numbers in it.
What actually has happened is that the "cleared" icons at the end of each transaction have all moved into the numberless "running balance" column.
Strangely, if I click on the head of the running balance column to sort by the running balance it disappears completely (the whole column).
Then if I click to sort by date the running balance column returns only with the numbers in the right place this time.
Any reloading of the page goes back to the original problem (no numbers in running balance column, just cleared icons).

@netjon if you could post a screenshot that would be great. There might be a fix for this already in the next release but I can take a look regardless when I get a chance

Hello
Josh ,
Here is a screenshot of the problem:  https://s19.postimg.org/ws5q6lkz7/running_balance_problem.jpg
I noticed when taking the screenshot that the numbers actually ARE there, they are just in the wrong places and partially cut off.
I don't know if this is a change or if it is different than when I first noticed the problem.
I added a bit to my original comment as well, probably while you were writing yours.  :-)

Hmm, this is an interesting issue, I think I fixed something similar to this but it would have been some time ago so I don't remember if it's the exact issue but after reading your edits it sounds like it was.
As far as the sorting goes. You must be sorted by date in order to see the Running Balance. I'll probably add that to the settings page for our next release :smile:

Hello again Josh!
Just to be very clear, the problem exists even when sorted by date.
It is only by first trying to sort by the running balance and then going BACK to sorting by date that the problem seems to resolve.
And upon reloading the page, even when sorting by date, the problem reappears.

@NetJon once we've released to 0.5.2, please let us know if you're still experiencing this issue.
There were some changes made to running balance for that release that may have resolved this.

Okay.  When is that being released?

It hasn't been decided but it should be soon

Okay.  Thanks.  :-)

@NetJon 0.5.2 is released!

Any better in 0.5.2?

Haven't had time to test it yet, but I did get your notice of the update.
I'll check soon and let you know.  :-)-------- Original message --------From: Kevin Brown notifications@github.com Date: 7/30/2016  10:36 PM  (GMT-06:00) To: toolkit-for-ynab/toolkit-for-ynab toolkit-for-ynab@noreply.github.com Cc: NetJon tonetjon@gmail.com, Mention mention@noreply.github.com Subject: Re: [toolkit-for-ynab/toolkit-for-ynab] Running Balance Not Working -
Column Appears, but no number in it (#422)
Any better in 0.5.2?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Haven't had time to test it yet, but I did get your notice of the update.
I'll check soon and let you know.  :-)

It works better now.
When scrolling it returns to the appearance in my screenshot above, but when NOT scrolling the column is there with the numbers.
There is also a delay before the column appears.  That is, it appears a moment after everything else, like it is loading separately and last.

@NetJon that's the expectation for the running balance column. Unfortunately it has to go away during the scrolling action because YNAB takes over the page at that time. Once you've stopped scrolling, that's when we can add the column to the page which is why you see the delay.

Alrighty, I'll go ahead and close this issue as it sounds like the original problem is now resolved and the feature is working as designed.

authors: NetJon blargity joshmadewell

repo: toolkit-for-ynab/toolkit-for-ynab


text:
feat: catch errors & render _error page

What kind of change does this PR introduce?
Feature:

Implement ErrorPage rendering
Add support for custom _error page

What is the current behaviour?
Error thrown in user code are not catched and propagated. This doesn't reflect what the output would be in a real situtation for a user and makes it impossible to test "bad scenarios".
What is the new behaviour?
Error page is rendered
Does this PR introduce a breaking change?
Mostly likely no. Unless someone is catching exceptions in their tests.
Other information:
Please check if the PR fulfills these requirements:

[x] Tests for the changes have been added
[ ] Docs have been added / updated

This is just a proof of concept I initially started in https://github.com/toomuchdesign/next-page-tester/pull/88.
It is by no means complete yet:

doesn't work after client side navigation
This PR could also introduce support for 404 page as code seems related to this
Refactors/cleanup

I will be quite busy this week so fell free to work on it if you find some time @toomuchdesign

This is just a proof of concept I initially started in https://github.com/toomuchdesign/next-page-tester/pull/88.
It is by no means complete yet:

doesn't work after client side navigation
This PR could also introduce support for 404 page as code seems related to this
Refactors/cleanup

I will be quite busy this week so fell free to work on it if you find some time @toomuchdesign

Just dropping a note: if on one hand we should aim to replicate what Next.js does (and I see a lot of cases where rendering the expected error or 404 page is clearly an advantage), on the other i wonder whether a user might prefer receiving an error about a route not matching any page. How do you see it?

Just dropping a note: if on one hand we should aim to replicate what Next.js does (and I see a lot of cases where rendering the expected error or 404 page is clearly an advantage), on the other i wonder whether a user might prefer receiving an error about a route not matching any page. How do you see it?

No worries @Meemaw, I'm also going to be considerably busier from now. We definitely did more then I expected, here 🚀 .
I'll check your PR out and try to focus on implementing next/config support.

No worries @Meemaw, I'm also going to be considerably busier from now. We definitely did more then I expected, here 🚀 .
I'll check your PR out and try to focus on implementing next/config support.

Just dropping a note: if on one hand we should aim to replicate what Next.js does (and I see a lot of cases where rendering the expected error or 404 page is clearly an advantage), on the other i wonder whether a user might prefer receiving an error about a route not matching any page. How do you see it?

I think we had similar discussion for the redirect where an option was to return redirect object instead of do it behind the scenes. It just depends where you position the library, e.g. unit or integration testing.
If "error" is returned we are closer to unit testing and would be testing implementation details as opposed to what the "end users" care about. As an end user of an app I don't care if Error is thrown in the app, but how the error is handled, e.g. the error screen I will see.
I personally see this library at the integration level with a strong synergy with @testing-library/react where everything should is tested as it would appear on screen.

Just dropping a note: if on one hand we should aim to replicate what Next.js does (and I see a lot of cases where rendering the expected error or 404 page is clearly an advantage), on the other i wonder whether a user might prefer receiving an error about a route not matching any page. How do you see it?

I think we had similar discussion for the redirect where an option was to return redirect object instead of do it behind the scenes. It just depends where you position the library, e.g. unit or integration testing.
If "error" is returned we are closer to unit testing and would be testing implementation details as opposed to what the "end users" care about. As an end user of an app I don't care if Error is thrown in the app, but how the error is handled, e.g. the error screen I will see.
I personally see this library at the integration level with a strong synergy with @testing-library/react where everything should is tested as it would appear on screen.

Yep, I substantially agree.
I wanted to make sure we are aware of the design decisions we're making. Even thought I'm not a fan of giving flexibility by adding options, I'll try to see whether there's room to optionally throw when a route is not found. Or abandon the idea 👍

Yep, I substantially agree.
I wanted to make sure we are aware of the design decisions we're making. Even thought I'm not a fan of giving flexibility by adding options, I'll try to see whether there's room to optionally throw when a route is not found. Or abandon the idea 👍

From Next.js docs:

pages/_error.js is only used in production. In development you’ll get an error with the call stack to know where the error originated from.

I put it here for reference.

From Next.js docs:

pages/_error.js is only used in production. In development you’ll get an error with the call stack to know where the error originated from.

I put it here for reference.

authors: Meemaw toomuchdesign

repo: toomuchdesign/next-page-tester


text:
[FX-5294] Update build and push image GH Action

FX-5294
Description
Update nodeJS version of build-push-image
How to test

Use this branch in GH Workflow

Development checks

[ ] Add changeset according to guidelines (if needed)

PR commands

List of available commands:

@toptal-anvil ping reviewers - Ping FX team for review

Should there be a changeset?

restored branch for a while

authors: dmaklygin sashuk

repo: toptal/davinci-github-actions


text:
JavaScript error when trying to focus on a form element in another tab

Dears,
I upgraded to Wagtail 1.6
And I have some page types with multiple tabs in the admin interface which contains mandatory fields
and now I'm facing an issue when trying to publish a page with an empty mandatory fields in other tabs
Old behavior:
Page do submit and the editing form is opened again with a red circle on the tab with the missing info
In 1.6:
JavaScript error in the console saying that:
An invalid form control with name='xxxxxxx' is not focusable.

and the page doesn't submit or publish

Hi @muhammad-saleh - thanks for the report. What version of Django are you running?

@gasman Django 1.10

Fixed in #2942
Thank for reporting!

authors: gasman m1kola muhammad-saleh

repo: torchbox/wagtail


text:
Fix isort on drone

isort 4.2.3+ is broken on Drone due to timothycrosley/isort#414. This commit pins isort to 4.2.2, as well as fixing an import order error that snuck in.

Hold up, isort has a new release that apparently fixes this issue. Drone is running as I type. This may not be required.

OK, this PR is no longer required. The newest version of isort fixes the bug. Whether we want to pin isort to a fixed version at some point is a discussion worth having though.


text:
feat: energy consumption and instantaneous power sensors

This PR implements the instantaneous power, and the energy consumption sensors.
This is the first time I am writing a sensor for a HA integration, let me know if there is anything I should improve.
Thanks
/CN

Thanks 👍 Will have a look at it during the weekend

Getting this error when adding the HERU device (removed the device and re-added it)
Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.10/site-packages/homeassistant/helpers/entity.py", line 541, in async_update_ha_state
    await self.async_device_update()
  File "/home/vscode/.local/lib/python3.10/site-packages/homeassistant/helpers/entity.py", line 739, in async_device_update
    raise exc
  File "/workspaces/home-assistant-heru/.devcontainer/hass/custom_components/heru/sensor.py", line 232, in async_update
    float(self.hass.states.get(self._power_entity).state)
TypeError: unsupported operand type(s) for +: 'float' and 'NoneType'

Instantaneous power has a value, but Energy consumption is "Unknown". After a restart of Home Assistant, the error is gone and Energy consumption gets a value.

By the way. I plugged the unit into a Datek APEX smart plug 16A which report wattage. It shows 11W while the Instantaneous power sensor shows 122W... I have a HERU 100

By the way. I plugged the unit into a Datek APEX smart plug 16A which report wattage. It shows 11W while the Instantaneous power sensor shows 122W... I have a HERU 100

That is strange. What is your supply and exhaust fan power (in %)?  I don't have a power measurement device but I do have an energy meter from my electricity provider, I checked the instantaneous power from the phase on which my Heru 100S is plugged in and I have the following when activating/deactivating the boost mode:

My energy consumption equation estimate an increase of 47W when activating the boost, the increase on the energy meter is around 50-60W (the precision of the value is 0.2f in kW). So I think the equation is not too off. I will buy some Shelly Plus 1PM so I can have a more accurate measurement on the unit.
At the end of the day, if we feel that the feature does not bring any improvement (because too inaccurate), we can definitively scrap it :-)

Getting this error when adding the HERU device (removed the device and re-added it)
Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.10/site-packages/homeassistant/helpers/entity.py", line 541, in async_update_ha_state
    await self.async_device_update()
  File "/home/vscode/.local/lib/python3.10/site-packages/homeassistant/helpers/entity.py", line 739, in async_device_update
    raise exc
  File "/workspaces/home-assistant-heru/.devcontainer/hass/custom_components/heru/sensor.py", line 232, in async_update
    float(self.hass.states.get(self._power_entity).state)
TypeError: unsupported operand type(s) for +: 'float' and 'NoneType'

Instantaneous power has a value, but Energy consumption is "Unknown". After a restart of Home Assistant, the error is gone and Energy consumption gets a value.
The same error occurs if I remove and re-add again, so you should be able to reproduce the error

Ok, should be fixed with https://github.com/toringer/home-assistant-heru/pull/7/commits/63281eb8d9c40a34a1cd011a95e43bea78826e86

By the way. I plugged the unit into a Datek APEX smart plug 16A which report wattage. It shows 11W while the Instantaneous power sensor shows 122W... I have a HERU 100

That is strange. What is your supply and exhaust fan power (in %)? I don't have a power measurement device but I do have an energy meter from my electricity provider, I checked the instantaneous power from the phase on which my Heru 100S is plugged in and I have the following when activating/deactivating the boost mode:

My energy consumption equation estimate an increase of 47W when activating the boost, the increase on the energy meter is around 50-60W (the precision of the value is 0.2f in kW). So I think the equation is not too off. I will buy some Shelly Plus 1PM so I can have a more accurate measurement on the unit.
At the end of the day, if we feel that the feature does not bring any improvement (because too inaccurate), we can definitively scrap it :-)

I just realised that my smart plug probably will not measure inductive load. So that might be the reason for the low wattage.

I'm ready to merge 👍  But could you first add the french translation for device_model and possible add a note in the README that the two sensors are calculated?
I will add a note in the release note that the component needs to be reconfigured for existing installs to enable the sensors.

I'm ready to merge +1 But could you first add the french translation for device_model and possible add a note in the README that the two sensors are calculated?
I will add a note in the release note that the component needs to be reconfigured for existing installs to enable the sensors.

I have added the FR translation and updated the README.md file. Before merging the PR, I would like to compare the energy consumption we calculate with what I will measure with the Shelly Plus 1 PM. I will receive them tomorrow, I can do the test over the weekend.

I actually feel a bit embarassed of having been so naive, but it is not that straightforward to estimate the energy consumption as it depends on some factors that we do not have information about, for instance the static pressure or the airflow. If you look at https://fsp.ostberg.com/products/4396/heru-100-s-ec/?region=se&lang=en under the Diagrams section, you can see that given the static pressure, the airflow, and the voltage you will get the current power, which is very far from the equation I have implemented in my PR.
I suggest to reject the PR as we miss the needed variables to have a good energy consumption estimate. Sorry for the troubles!

authors: christian-nils toringer

repo: toringer/home-assistant-heru


text:
CoreContainer#create may deadlock with concurrent requests for metrics

CoreContainer#create registers metrics for the created core quite early, and metrics can be requested for a core that is still being created. If a metrics request calls SolrCore#getSearcher with unlucky timing (race condition), then CoreContainer#create can deadlock.
This problem was described on the users lists: https://lists.apache.org/thread/mvpp1ogkxfdgfx87mdt6ylhqsttoq2dw
We ran into such a deadlock with Solr 9.2.1, a CoreAdmin CREATE request, and a periodic thread that requests all available JMX metrics.
A CoreAdmin CREATE request was received, but its thread waits forever because onDeckSearchers is 1 and _searcher is null (variables checked in heap dump):
"qtp1800649922-28" #28 prio=5 os_prio=0 cpu=757.69ms elapsed=25383.63s tid=0x00007fe6dc9613a0 nid=0x70 in Object.wait()  [0x00007fe6c68ca000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@17.0.8.1/Native  Method)
- waiting on
at java.lang.Object.wait(java.base@17.0.8.1/Unknown  Source)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:2528)
- locked <0x00000000e25dd2c8> (a java.lang.Object)
at org.apache.solr.core.SolrCore.initSearcher(SolrCore.java:1283)
at org.apache.solr.core.SolrCore.(SolrCore.java:1168)
at org.apache.solr.core.SolrCore.(SolrCore.java:1051)
at org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1666)
at org.apache.solr.core.CoreContainer.create(CoreContainer.java:1532)
at org.apache.solr.handler.admin.CoreAdminOperation.lambda$static$0(CoreAdminOperation.java:111)
at org.apache.solr.handler.admin.CoreAdminOperation$$Lambda$437/0x00007fe66048cc60.execute(Unknown Source)
at org.apache.solr.handler.admin.CoreAdminOperation.execute(CoreAdminOperation.java:398)
at org.apache.solr.handler.admin.CoreAdminHandler$CallInfo.call(CoreAdminHandler.java:354)
at org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:219)
There's no way for clients to retry the CREATE request, because CoreContainer rejects additional requests for good reason ("Already creating a core with name ...", see SOLR-14969).
The only solution is to restart Solr.
A thread for metrics was also waiting in the same way:
prometheus-http-1-1" #30 daemon prio=5 os_prio=0 cpu=1212.68ms elapsed=25383.60s tid=0x00007fe620008ac0 nid=0x73 in Object.wait()  [0x00007fe6c680b000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@17.0.8.1/Native  Method)
- waiting on
at java.lang.Object.wait(java.base@17.0.8.1/Unknown  Source)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:2528)
- locked <0x00000000e25dd2c8> (a java.lang.Object)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:2271)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:2106)
at org.apache.solr.core.SolrCore.withSearcher(SolrCore.java:2124)
at org.apache.solr.core.SolrCore.getSegmentCount(SolrCore.java:534)
at org.apache.solr.core.SolrCore.lambda$initializeMetrics$11(SolrCore.java:1360)
at org.apache.solr.core.SolrCore$$Lambda$760/0x00007fe660634ec8.getValue(Unknown Source)
at org.apache.solr.metrics.SolrMetricManager$GaugeWrapper.getValue(SolrMetricManager.java:779)
at org.apache.solr.metrics.reporters.jmx.JmxMetricsReporter$JmxGauge.getValue(JmxMetricsReporter.java:207
This thread gathers multiple metrics one after the other. We can assume, that it had called SolrCore#getSearcher successfully before, and that the previous call has incremented onDeckSearchers to 1.
A previous call to #getSearcher should eventually decrement onDeckSearchers again, and also set the _searcher field, but that's not happening. Normally, this should happen in SolrCore#registerSearcher, but that method is executed on the searcherExecutor, see
https://github.com/apache/solr/blob/releases/solr/9.2.1/solr/core/src/java/org/apache/solr/core/SolrCore.java#L2681
The problem is, that searcherExecutor will never execute #registerSearcher because the executor is still blocked by another job. This is because the core is still being created, see
https://github.com/apache/solr/blob/releases/solr/9.2.1/solr/core/src/java/org/apache/solr/core/SolrCore.java#L1160
"searcherExecutor-14-thread-1-processing-studio" #50 prio=5 os_prio=0 cpu=0.27ms elapsed=25212.18s tid=0x00007fe608146080 nid=0xbd waiting on condition  [0x00007fe6c637a000]
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@17.0.8.1/Native  Method)
- parking to wait for  <0x00000000e738c1a8> (a java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(java.base@17.0.8.1/Unknown  Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@17.0.8.1/Unknown  Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(java.base@17.0.8.1/Unknown  Source)
at java.util.concurrent.CountDownLatch.await(java.base@17.0.8.1/Unknown  Source)
at org.apache.solr.core.SolrCore.lambda$new$3(SolrCore.java:1162)
at org.apache.solr.core.SolrCore$$Lambda$815/0x00007fe6606f3c40.call(Unknown Source)
at java.util.concurrent.FutureTask.run(java.base@17.0.8.1/Unknown  Source)
In summary, we have
thread "qtp1800649922-28" in SolrCore. trying to create a core, which is waiting for
#registerSearcher job in the searcherExecutor work queue, which is waiting to be executed by
thread "searcherExecutor-14-thread-1-processing-studio" which waits for the first thread "qtp1800649922-28" to unblock it

torvalds.dev is analyzing the ticket

repo: torvalds-dev/solr


text:
重力加速度で歩数計の初期値が1になるのを修正

_beforeA の初期値が0であることで電源オン時に重力加速度の影響でカウントが進んで、歩数計の初期値が1になるのを修正しました。
_beforeA = 1.0F と変更します。

良さそうです．ありがとうございます！

authors: s-moa toshi-pono

repo: toshi-pono/poketch


text:
Runtime EXC_BAD_ACCESS in AsyncSequence (SkieSwiftFlow)

We are currently switching from the native Coroutines Plugin to SKIE and are especially interested in the SkieSwiftFlow. We just noticed that we are receiving runtime crashes on iOS, when collecting from the SkieSwiftFlow .
Code
KMP
class SkieTest {
    fun intFlow() = flow {
        do {
            emit(rand())
        } while (true)
    }
}

iOS App
let task = Task {
    let intStream = SkieTest().intFlow()
    for await intValue in intStream {
        Logger().debug("Debug \(intValue)")
    }
}

Error:
Thread 3: EXC_BAD_ACCESS (code=1, address=0x0)
What we already know:
When add a transformation like map or compatMap and just return the element like it came, all is running fine. This is will be our current solution for that problem.
extension AsyncSequence {
    @preconcurrency @inlinable public func toAsyncSequence() -> AsyncMapSequence<Self, Element> { return self.map { element in element } }
}

We also noticed you are doing the same in your example: https://github.com/touchlab/SKIEDemoSample/blob/a9df32055e5d88c39d4dc60ef7dfe06fa49998b6/ios/ios/TickDemo.swift#L24
let secondCounter = TickProvider.shared.ticks()
    .scan(0) { acc, _ in
        acc + 1
    }

Question
Since we need to use this on all SkieSwiftFlows to use it properly it should be handled by SKIE.
Also please note: I did just try this in our current KMP project, so a misconfiguration isn't that unlikely. Our current configuration for SKIE is:
extensions.configure<SkieExtension> {
    analytics {
        enabled.set(false)
    }

    features {
        group("io.ktor.client.plugins.cache.storage") {
            EnumInterop.Enabled(false)
            SealedInterop.Enabled(false)
            FlowInterop.Enabled(false)
            SuspendInterop.Enabled(false)
        }
    }
}

Versions:
skie = "0.5.0"
kotlin = "1.9.10"

In case it's relevant the generated .h file:
__attribute__((objc_subclassing_restricted))
__attribute__((swift_name("SkieTest")))
@interface PrefixSkieTest : PrefixBase
- (instancetype)init __attribute__((swift_name("init()"))) __attribute__((objc_designated_initializer));
+ (instancetype)new __attribute__((availability(swift, unavailable, message="use object initializers instead")));
- (id<PrefixKotlinx_coroutines_coreFlow>)intFlow __attribute__((swift_name("intFlow()")));
@end

Hi! I tried the example code, and it didn't crash. So we need to figure out what is different about your and mine setup.
Likely it will be a different version of something. What version of the following SW do you have?

Coroutines
Xcode
macOS
iOS (for the device that runs the binary)

The SKIE configuration doesn't contain anything that should cause this problem.
Would you be able to create a new project just with this piece of code to see if it still crashes?
The error message points to some null pointer exception - do you know where in the code it crashes (it will likely show you some line in assembly code)?
Also, is the error reliably reproducible for you, and if so how often and how quickly does it happen (for example, it crashes immediately without printing anything vs. it can print +- 100 numbers and then crash)?

I had the same issue today on version 0.5.0 of SKIE. Downgrade back to 0.4.2 and everything works as expected.

@twinkelbauer Could you provide the implementation of the rand Kotlin function you use?

Hello @FilipDolnik,
we are using

coroutines 1.7.3
XCode 15

tools 15
simulator 15 (didn't try on real device yet)
MacOS 14.0
deploymentTarget 15

The error message points to some null pointer exception - do you know where in the code it crashes (it will likely show you some line in assembly code)?

Exactly, here a small dump
`partial apply for thunk for @escaping @callee_guaranteed @Sendable @async () -> (@out τ_0_0):

->  0x1000890bc <+0>:  orr    x29, x29, #0x1000000000000000
    0x1000890c0 <+4>:  sub    sp, sp, #0x20
    0x1000890c4 <+8>:  stp    x29, x30, [sp, #0x10]
    0x1000890c8 <+12>: str    x22, [sp, #0x8]
    0x1000890cc <+16>: add    x29, sp, #0x10
    0x1000890d0 <+20>: ldr    x9, [x22]
    0x1000890d4 <+24>: str    x9, [sp]
    0x1000890d8 <+28>: mov    x8, x29
    0x1000890dc <+32>: sub    x8, x8, #0x8
    0x1000890e0 <+36>: str    x9, [x8]
    0x1000890e4 <+40>: ldr    x0, [x9, #0x18]
    0x1000890e8 <+44>: ldr    x8, [x22]
    0x1000890ec <+48>: mov    x10, x29
    0x1000890f0 <+52>: sub    x10, x10, #0x8
    0x1000890f4 <+56>: str    x8, [x10]
    0x1000890f8 <+60>: str    x8, [x9, #0x10]
    0x1000890fc <+64>: bl     0x102be1af0               ; symbol stub for: swift_task_dealloc

Also, is the error reliably reproducible for you, and if so how often and how quickly does it happen (for example, it crashes immediately without printing anything vs. it can print +- 100 numbers and then crash)?

It just crashes on the first collection so none of the values get ever emitted
I can also validate @PiotrPrus's claim and with 0.4.20 everything works as expected. Going further I checked your tag 0.5.2 from yesterday and there also everything works. So it's just the 0.5.0 version which produces the EXC_BAD_ACCESS.
My solution would then be to use 0.5.2. Is it safe to use yet?

Hi! Yeah, yesterday, we were able to create a reproducer for a similar crash and subsequently fix it in 0.5.2 - so it's good to hear that it also fixed your project. The key to reproducing it was to use XCFramework instead of a regular framework, which is what we use in the tests.

Is it safe to use yet?

Yes, you can go ahead and use it. It's a regular release; we just haven't had the time yet to put out release notes / make a public announcement, which will happen today.

Great! Thanks for your support!

authors: FilipDolnik PiotrPrus TadeasKriz twinkelbauer

repo: touchlab/SKIE


text:
🛑 MSP-Trust is down

In 1765665, MSP-Trust (https://www.hanatrust.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-Trust is back up in 1939794.

repo: touguy/uptime


text:
🛑 TI-DHR is down

In 06e2334, TI-DHR (https://dhr.hanati.co.kr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TI-DHR is back up in 902513c after 10 minutes.


text:
🛑 Fiber Connect is down

In acae875, Fiber Connect (https://www.svpfiber.com) was down:

HTTP code: 503
Response time: 311 ms

Resolved: Fiber Connect is back up in 9b76233 after 20 minutes.

repo: touzesabine/uppdownn


text:
[Documentation]: Version selection for documentation

Is there an existing issue for this?

[X] I have searched the existing issues

What kind of documentation would you like added or changed?
The docs doesn’t have the version selection.
Why is this needed?
No response
Anything else?
No response

/assign @codingjaguar

/assign @shiyu22

/unassign

repo: towhee-io/towhee


text:
add load from yaml interface for training_config

config training_config with yaml

Codecov Report

Merging #577 (1c7e1c5) into training (2fdbafd) will increase coverage by 0.59%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           training     #577      +/-   ##
============================================
+ Coverage     59.36%   59.96%   +0.59%
============================================
  Files           152      152
  Lines          5970     6054      +84
  Branches        867      867
============================================
+ Hits           3544     3630      +86
+ Misses         2196     2195       -1
+ Partials        230      229       -1

Impacted Files
Coverage Δ

towhee/trainer/training_config.py
87.95% <100.00%> (+14.78%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm

authors: codecov-commenter oneseer zc277584121


text:
Update Table options for State Sites

Table content is currently not a good fit for state legislatures.
Amend to the following:
MEMBER [remove, not needed on the typically short state tables]
STATE [remove, irrelevant here]
EVENT TYPE [remove "DC Event," add "Other"]
SORT [remove "by State," add "by Name"]
Also, for state sites please have the default table setting to display ALL events.

For By Name do you mean By Candidate Name?

And specifically By Candidate Last Name?

Yeah, Candidate/Lawmaker Last Name. Sort alphabetically.

authors: JacksonMaxfield nathanmwilliams

repo: townhallproject/townHallProject


text:
The type annotation for the lock_file __init__ parameter is too narrow

BaseFileLock.__init__ annotates lock_file as str | os.PathLike[Any].  However, this excludes bytes which are still the basic representation of paths on most POSIX systems.  The implementation goes on to pass lock_file to os.fspath which both accepts and may return bytes values so there doesn't seem to be any reason to exclude bytes from the annotation.

PR welcome 👍

authors: exarkun gaborbernat

repo: tox-dev/py-filelock

license: unlicense


text:
Update to three.js r71

Sorry for the large PR, there were quite a lot of files in the libs/ directory. The actual compatiblity changes in src/ are quite small.
I tested the demos and examples and everything looks ok except for glamcity.html, which throws an error with the minified glam.min.js. It works with the debug glam.js but looks a bit strange (the building textures are much brighter for some reason). Hopefully you can look into that.

Actually, this PR is ridiculously big. I'll create another PR without the hundreds of library files.

repo: tparisi/glam


text:
Update trace4cats-core to 0.14.4

About this PR
📦 Updates io.janstenpickle:trace4cats-core from 0.14.0 to 0.14.4
📜 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!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.0).
You might want to review and update them manually.
README.md
project/Dependencies.scala

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.janstenpickle", artifactId = "trace4cats-core" }
}]

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

Superseded by #195.


text:
Persistence

I'm still trying to make the time to figure out how to self replicate and create persistence.

os.mkdir(path) is throwing up an error: [Errno 2] No such file or directory: '~/.arm0red'

I can't seem to figure out the "file not found" bug in strChk(). Any clues as to what I'm doing wrong?

Bot now copies itself to hidden dir in home dir before running. But I have yet to implement persistence.

I currently working on using systemd service for persistence.

repo: trackmastersteve/HackServ


text:
Strange behaviour when adding data on the right and left

Lightweight Charts Version: master 9f52e942
Steps/code to reproduce:

Add 2 series
Add whitespace between series
Add data to right series and then to left

Actual behavior:
Points in right seria shift to left on data added to left seria

Expected behavior:
Points in right seria doesn't shift
CodeSandbox/JSFiddle/etc link:
https://jsfiddle.net/beholderrk/83juqxvL/3/

The reason of that is duplicated data. In generateData function you have to start from from date + 1 day (rather that just from from date), and while adding data to the left you have to add N (20 in your sample) bars since N+1 day back. We'll warn about duplicated data in #315

Got it thanks

authors: beholderrk timocov

repo: tradingview/lightweight-charts


text:
feat: Enable entrypoint tls config + TLSOption

Fixes #248
Recreated PR as it became orphaned with the repository migration. Original PR: https://github.com/traefik/traefik-helm-chart/pull/249

@SantoDE  Ping 😄

repo: traefik/traefik-helm-chart


text:
Add two boolean flag to prevent expand or collapse pass through anchored state.

Preview

State
Image

normal usage

shouldAnchoredBeforeExpand

shouldAnchoredBeforeCollapse

enable both flags

Description
In the current version, it is too easy to bypass the anchor level height (It will act like normal bottom sheet behavior).
If there have an intermediate page, it's not easy to scroll in anchor height and make the position locked.
Sometimes, It causes bad user experience.
This problem is caused by the method of shouldExpand and shouldCollapsed.
When the bottom sheet is below the anchor height, the 'shouldExpand' method will return
the value, which depends on the new top value(calculated by the current bottom sheet height and
user's scrolling velocity multiply the friction const value)
large then the anchor height, and make the bottom sheet expand,
so as the 'shouldCollapsed' method.
I add two boolean flags to prevent the behavior above.
Take the 'shouldExpand' for example, if the bottom sheet is above the anchor height but it's not in the anchor state.
It should scroll to anchor level first.
When it comes to collapsing situation, The bottom sheet should collapse from expanded state to anchor height then collapsed state.
Usage
    <LinearLayout
        android:id="@+id/bottom_sheet"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        app:behavior_shouldAnchoredBeforeExpand="true or false"
        app:behavior_shouldAnchoredBeforeCollapse="true of false"
        app:layout_behavior="com.trafi.anchorbottomsheetbehavior.AnchorBottomSheetBehavior"
        />

This Pull Request is pretty old but no comments are added. I think this is a very useful addition to this behavior and I need this too. Please merge or tell what's wrong or missing.

Hi! Thanks for the reply.
I think @justasm 's idea is flexible.
Although I only need the behavior to stop at anchor level then it can expand or collapse in my use case, I found I can add two boolean values to achieve the result.
If there will have a public setter for these constants, the method name should make a developer understand it is related to bypassing the anchor level. (The behavior this PR hope to achieve.)
I think the customization for frictions is really sweet.

I like both approaches. Another thought: Since this behavior still exposes methods of googles default BottomSheetBehavior, it would be easier to use when additional methods stick to the existing naming patterns. In the base Behavior we have a flag called "skipCollapsed" which is pretty much related. For @YuanLiou's approach this means, that names like skipAnchorOnExpand and skipAnchorOnCollapse might be more convenient when used together with skipCollapsed. If skipCollapsed and skipAnchorOnCollapse are set to true, the bottomsheet will transit to hidden state without stopping in between.

I support adding skipAnchoredOnExpand and skipAnchoredOnCollapse.

@justasm what happened? This was actually quite useful

Nothing.
Regardless, we plan to deprecate this library, please consider using Google's Material component BottomSheetBehavior with STATE_HALF_EXPANDED.

Gotcha, thanks!
So if I were to open a PR into this project, it would no longer be considered? ):

Raise an issue first so we can discuss if it makes sense to invest the work. I recommend others to use Google's Material BottomSheetBehavior instead, especially if it supports the behavior you need.

authors: AlejandroHCruz YuanLiou justasm mlilienberg

repo: trafi/anchor-bottom-sheet-behavior


text:
🛑 Anakin is down

In c885f1e, Anakin (https://anakin.langstadlinger.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Anakin is back up in 4590eef.

repo: traktuner/status


text:
MB-15488 Add AOA and payment packet service objects

Jira ticket for this change
Summary
This was part of the work done in https://github.com/transcom/mymove/pull/10246 and is being broken out into its own PR so we can move forward with cleaned up and mergeable parts of the code (since the other PR is a proof-of-concept and shouldn't be merged).
This adds the service objects for creating AOA and payment packets. I left TODO comments as placeholders for things that we haven't sorted out yet, like the SSW creation. I mainly left them to remember that there are still parts missing, but let me know if you think they're more confusing than helpful, or if you think they should be regular comment rather than TODOs.

Main Changes

[x] feat (services): add service to create an AOA packet for a PPMShipment
[ ] add service object to create a payment packet

I haven't gotten to this, but I'm hoping it'll be quick since it'll be similar to the AOA packet service object, just requesting more info from the PPM shipment fetcher and gathering up more uploads to run through the converter.

Other Changes

[x] feat (services): Add service member and orders to PPMShipmentFetcher

This gets us some of the data we'll need for the AOA and Payment packets. Tbh, not sure if this should go here, or if the packet service objects should be using a move/order fetcher in addition to the ppm shipment fetcher. Only reason I chose this for now is that we don't have generic fetchers for those two as far as I know, and it's out of scope to do that too.
refactor (services tests): update the PPMShipmentFetcher tests that use suite.False and suite.True to give more helpful error messages

[x] fix (testdatagen): update make_order to pass assertions along

Previously wasn't passing input assertions to MakeDocument or MakeUserUpload, so if you wanted to stub things out, it would actually still try to create those objects, which can cause some failures.

[x] feat (testdatagen): add ppm make func for approved w/o AOA packet yet

This is helpful for testing the AOA packet creator service object.

Testing Changes

💻
Run Server Tests
make server_test

Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Messages

:book:
:link: MB-15488

  Generated by :no_entry_sign: dangerJS against 678783ada770196f39147b50c12a2a8a31f97188

authors: felipe-lee robot-mymove

repo: transcom/mymove


text:
Mb mb before asdf node changes dont merge

Jira ticket
Summary
Hypothesis: asdf changes could be causing problems with ephemeral deploys
So I made this branch point to the commit right before that was merged into main.
I had to make a base something old because it doesnt let you make a PR without any changes.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the
Login as a

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against cf0415338d217cd4f5301b74bc938ca596031956

authors: mboren robot-mymove


text:
ChatGPTUnofficialProxyAPI Does not work

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
all
Describe the Bug
FetchError: request to https://bypass.duti.tech/api/conversation failed, reason: Hostname/IP does not match certificate's altnames: Host: bypass.duti.tech. is not in the cert's altnames: DNS:

Similar (or same) issue here.
TypeError: Failed to parse URL from
    at Object.fetch (node:internal/deps/undici/undici:11413:11)
    at async fetchSSE (/node_modules/chatgpt/build/index.js:46:15) {
  [cause]: TypeError [ERR_INVALID_URL]: Invalid URL
      at new NodeError (node:internal/errors:399:5)
      at URL.onParseError (node:internal/url:566:9)
      at new URL (node:internal/url:646:5)
      at new Request (node:internal/deps/undici/undici:7002:25)
      at fetch2 (node:internal/deps/undici/undici:10554:25)
      at Object.fetch (node:internal/deps/undici/undici:11411:18)
      at fetch (node:internal/process/pre_execution:230:25)
      at fetchSSE (/node_modules/chatgpt/build/index.js:46:21)
      at /node_modules/chatgpt/build/index.js:556:7
      at new Promise (<anonymous>) {
    input: '',
    code: 'ERR_INVALID_URL'
  }
}

Node.js v18.15.0

NOTE: I strongly recommend using the official API via ChatGPTAPI going forwards. The unofficial API proxies are not robust and will continue to have intermittent downtimes.

authors: ashuvax sam-hieken transitive-bullshit

repo: transitive-bullshit/chatgpt-api


text:
Determine bus routes to support + update constants.js

As I noticed in https://github.com/transitmatters/t-performance-dash/pull/93 — we don't have data for all routes.
Whoever picks this up needs to determine, of the routes we have available, which to support, and then update src/constants.js with stop data for those.
Note: This is a manual process because the data is so sparse. i.e. for the 57 we only have the following directions and stops available—therefore needs to be human curated.
{
    "57": {
        "979": [
            0
        ],
        "899": [
            1,
            0
        ],
        "987": [
            0
        ],
        "1807": [
            0
        ],
        "931": [
            1
        ],
        "912": [
            1
        ],
        "918": [
            1
        ],
        "959": [
            0
        ],
        "966": [
            0
        ],
        "900": [
            1,
            0
        ],
        "903": [
            1
        ],
        "937": [
            1
        ],
        "954": [
            0
        ],
        "9780": [
            0
        ],
        "926": [
            1
        ],
        "913": [
            1
        ],
        "973": [
            0
        ],
        "11780": [
            0
        ]
    }
}

Routes 1 and 28 already supported.
Consider Key Bus Routes. Alternatively, just go down the list by ridership count.
Next up: 66, 114/116/117 (this corridor and others can be done by 'branching'), 57/57A (ew), 23, 111.
Also, SL1/2/3 and SL4/5?

Above is done. Next ones by ridership numbers:
SL1/2/3, SL4/5 (if possible)

39
104/109

32

22 (columbus bus lane)
61/70/170
16
86
34

77 (mass ave buslane focus?)

key route. other key routes: 15, 71, 73

authors: austinjpaul mathcolo

repo: transitmatters/t-performance-dash


text:
Update required node version to 20

CodeQL action have warning

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, github/codeql-action/init@v1, github/codeql-action/autobuild@v1, github/codeql-action/analyze@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Currently the project uses node version 14. We have to update node to version 20, test all works fine, fix a potential problems and update engines in packages.json. Also, let's mention dev requirements in the docs, we should add info about node version, docker and another tools that are required to make build

Is there a way to benchmark performance currently? It might be interesting to see speed changes after upgrading to node 20.

I think we currently no have benchmarks. We should update node just because 14 version is deprecated and do not supported anymore. I will try to add more unit tests in future, it will be useful additionally for measure performance between node versions too.
Potentially, we may have a problems with build the code with a new node version

How do you test ./Dockerfile and thirdparty/bergamot/Dockerfile?

How do you test ./Dockerfile and thirdparty/bergamot/Dockerfile?

We just run a command make buildAll that build all things. If this command fails, then we have broken code

authors: hamirmahal vitonsky

repo: translate-tools/linguist


text:
🛑 TechinAsia_WordPress_API is down

In fdc5939, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 218 ms

Resolved: TechinAsia_WordPress_API is back up in 6a63abf after 9 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_WordPress_API is down

In 4c82489, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 222 ms

Resolved: TechinAsia_WordPress_API is back up in 7b81074 after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 6652cf5, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 242 ms

Resolved: TechinAsia_WordPress_API is back up in 4da2b3d after 7 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In 577104c, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 232 ms

Resolved: TechinAsia_Laravel_API is back up in 320427b after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 3cfad66, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 227 ms

Resolved: TechinAsia_WordPress_API is back up in 4b37607 after 10 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In c3c98c9, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 173 ms

Resolved: TechinAsia_Laravel_API is back up in 4f562ac after 7 minutes.


text:
🛑 TechinAsia is down

In 4010290, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 753 ms

Resolved: TechinAsia is back up in 1adcf8f after 7 minutes.


text:
用组件引入该组件，如何使用调用日历实例

目前用组件方式引入进来， 但是实例没有找到， 也尝试过ref 没找到对应的方法

目前使用的是taro

问题已经解决，可以获取到当前小程序页面的实例， calendar挂在实例上
/**

日历初次渲染完成后触发事件，如设置事件标记
*/
afterCalendarRender = (e) => {
const pageList = Taro.getCurrentPages();
const calendar = pageList[pageList.length - 1].calendar;
this.setState({calendar});
}

问题已经解决，可以获取到当前小程序页面的实例， calendar挂在实例上
/**

日历初次渲染完成后触发事件，如设置事件标记
*/
afterCalendarRender = (e) => {
const pageList = Taro.getCurrentPages();
const calendar = pageList[pageList.length - 1].calendar;
this.setState({calendar});
}

如果需要直接使用 this.calendar，则需要明确 this 指向的是当前页面实例。
直接调用 Taro.getCurrentPages() 去取得当前页面实例也OK。
Taro3.0.5 中提供了获取当前页面实例的方法 getCurrentInstance。


text:
Can't read logs on Firefox

Description
Cannot read logs on Firefox.
It shows strange texts.
Actual behavior
Workflow definition
timezone: UTC

+step1:
  echo>: foo

+step2:
  echo>: bar

+step3:
  echo>: bar

Firefox

Chrome

Version

digdag: current master branch 99c38452cfe1dd62042e6e4 (0.10.2)
Firefox: 88.0 (64-bit)

Other information
Error message in console

Uncaught (in promise) Error: offset is outside the bounds of the DataView
onmessage untar.js:1
r untar.js:1
i untar.js:1
e untar.js:1
r untar.js:1
value model.js:338
promise callbackvalue/< model.js:337
promise callbackvalue model.js:333
value console.jsx:935
callback console.jsx:1025
callback Component.js:38
setTimeout handlert/r.start Component.js:43
callback Component.js:39
setTimeout handlert/r.start Component.js:43
value Component.js:56
React 3
unstable_runWithPriority scheduler.production.min.js:18
React 7
value console.jsx:2185
promise callback*value console.jsx:2183
value console.jsx:2168
React 3
unstable_runWithPriority scheduler.production.min.js:18
React 7
untar.js:1:1120

Hello, @seiyab
Thank you for your report.
I reproduced this issue in my environment.

Digdag: 0.10.2
OS: macOS 11.4
Java: 1.8.0_291
Firefox: 89.0.2
Google Chrome: 92.0.4515.131

mkdir /tmp/digdag
digdag server -O /tmp/digdag -m

digdag init test
cd test
digdag push
digdag start test test --session now

And access http://localhost:65432/sessions/1#logs-+test+repeat1

I bisected and it happens since this commit https://github.com/treasure-data/digdag/pull/591

In Firefox 94.0.2 this seems to be no longer an issue.

Hello, @ehaupt
Thank you for your report!! I also confirmed In Firefox 94.0.2 resolve this issue.
@seiyab Could you test in your environment?

It works fine upgrading Firefox to 94.0.2.
Thank you for notifying!

authors: ehaupt hiroyuki-sato seiyab

repo: treasure-data/digdag


text:
[Bug]: Azure Import process creates 2 prefixes in lakeFS for every folder in ADLS

What happened?
Current Behavior:
Azure Import process creates 2 prefixes in lakeFS for every folder in ADLS
Steps to Reproduce:

Run the import process from UI

8157833.png)
Expected Behavior
Expected Behavior:
How you expected thing to work.
lakeFS Version
0.97.5
Deplyoment
lakeFS Cloud on Azure
Affected Clients
No response
Relevant logs output
No response
Contact Details
amit.kesarwani@treeverse.io

I thought I took care of this already. I'll take a look ASAP

@kesarwam I think this is fixed in 0.98.0. can you please verify with latest version?

@kesarwam also please refer to our docs import section on how to import from an ADLS storage account

authors: N-o-Z kesarwam

repo: treeverse/lakeFS


text:
Add a catch/retry mechanism to lakectl local operations

This enhancement request stems from a bug report about rare failures of lakectl local commits.

@itaiad200 is this issue https://github.com/treeverse/lakeFS/issues/7705 closing this item?

I just ran into an issue where I was running lakectl local clone on about 4TB of data. It was about 1/2 done when one download failed with:
download <path> failed: could not write file '/mnt/data/frames-bbox/<file>': stream error: stream ID 167; INTERNAL_ERROR; received from peer

(I've redacted the actual file path as it contains the name of a confidential partner). The error is likely because the destination volume is an NFS volume and there was some kind of network error.
As a result I had to then cd into that directory and lakectl local pull which first required a diff of what it had pulled and what was in the cloud. As that was about 2TB of data and due to this issue that diff takes a very long time. It's still running now but I suspect it's going to be about the same amount of time as just deleting everything and trying the clone again from scratch.
I'm not sure but I think https://github.com/treeverse/lakeFS/pull/7723 fixed issues with communication with the LakeFS server but I don't think it addressed issues like the above.
In addition to this being a bit slow, manual, and annoying it can be a really significant issue in some cases. We sometimes launch ML training jobs as Argo workflows. The first step in that workflow is to download the relevant training data to faster, local storage. If that fails the entire workflow fails. The initial clone can take about 8 hours so that's a significant issue if it fails after 6 or 7 hours and we have to restart the job.

Just had another one of these after hours of data download. This time it wasn't an NFS volume.
download<path>/camera_b_raw/frames.h5 failed: could not write file '/mnt/data/frames_bbox/<frames>/camera_b_raw/frames.h5': stream error: strea │
│ Error executing command.

As above, I've redacted the full filename a bit.

Like @oliverdain mentioned, #7723 handles retries with lakeFS requests, and won't address issues like the above, where the response failed to be written to the destination file (here).
Like the title suggests, in order to solve this we would have to retry the entire apply flow in situations where it's not lakeFS server requests failing (to avoid multiplying the retries).

I just had another data transfer fail with:
download <redacted>/camera_b_raw/frames.h5 failed: could not write file '/<redacted>/camera_b_raw/frames.h5': stream error: stream ID 325; INTERNAL_ERROR; received from peer

This time I'm using a regular GKE persistent disk not an NFS volume so I think that error is coming from the LakeFS server. This is now the 3rd time in a row my data transfer has failed after about 10 hours.

authors: itaiad200 oliverdain talSofer


text:
There is no lakectl command to check current user

This is an API that we lack that @arielshaqed suggested- both he and I ran into this missing functionality
Story
Basically, when you run lakectl, it looks at your access key and determines what user you are based on that. That user's authorization policies are applied. It is very common that users make a mistake and specify the wrong access key and it takes a lot of effort to debug.
Feature Request
It would be nice if we had a lakectl command. Something similar perhaps to https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sts/get-caller-identity.html

AWS have this (never mind the UX),  e.g.
❯ aws sts get-caller-identity

{
    "UserId": "AROAR3RFY3EGTFAMROWCR:ariels@treeverse.io",
    "Account": "127854500109",
    "Arn": "arn:aws:sts::127854500109:assumed-role/JumpCloudDeveloper/ariels@treeverse.io"
}

authors: arielshaqed nadavsteindler


text:
[Feature Request] : Add value notation for each bar in chart bars

Discussed in https://github.com/tremorlabs/tremor/discussions/804

Originally posted by MenaiAla November 10, 2023
Thank you Tremo team for this amazing project.
In fact, it helps us a lot in the data visualization of our product.
Our users are aged a little bit and I used Tremor to create a page to visualize the data and then allow them to download it as PDF.
However, I would ask if it's possible to annotate the value on the top of each bar.
This is Figma example:

Anf if it's possible in the current version, please could you provide an example because I'm prototyping based on your UI kit and I don't know if it's possible to do it with code.
Thank you

Hey! Might I give it a shot? @severinlandolt

Hey all! I don't know where to start. Adding labels adds so much complexity that we currently don't see it feasible. Especially if labels are added, the line chart and scatter chart should get labels too–and those are even more complex.
There is a reason why almost no SaaS has labels. And they know what data they can expect, we don't.

Hi @severinlandolt ,
looks like this is not priority. but i believe it will improves chart readability.

authors: rajdip-b rupeshpadhye severinlandolt

repo: tremorlabs/tremor


text:
TimePicker Slider Error in version 1.6.1

I downloaded and added this plugin to my project, and seem to have found an issue.  When the time picker comes up, you can use the sliders to set the time and press Done.  You can also just press the Now button and get the current time into the form when pressing Done.
But if you use the sliders and then press Now,  the output changes to aN:aN:aN.  If you try to move the slider after this, I see the error  closestHandle is undefined in Firefox.
I'm using it with the following options:  .timepicker({ timeFormat: 'HH:mm:ss' }).
This error can be duplicated on the sample page on all the examples using a time picker.

UPDATE:  I applied the same fix found in issue 845, but note that this was a different issue.  I did not have the error described in that issue.

repo: trentrichardson/jQuery-Timepicker-Addon


text:
unable to retrieve my timeline

running the code:
from twitter.account import Account
email, username, password = "myemail", "myusername", "mypassword"
account = Account(email, username, password, debug=2, save=True)

latest_timeline = account.home_latest_timeline(limit=100)

print(latest_timeline)

I get the following error:
[success] myusername login success
[{'errors': [{'message': 'Internal: Unspecified', 'locations': [{'line': 3, 'column': 5}], 'path': ['home', 'home_timeline_urt'], 'extensions': {'name': 'OperationalError', 'source': 'Server', 'code': 0, 'kind': 'Operational', 'tracing': {'trace_id': '95318f3a322d7cea'}}, 'code': 0, 'kind': 'Operational', 'name': 'OperationalError', 'source': 'Server', 'tracing': {'trace_id': '95318f3a322d7cea'}}], 'data': {'home': {}}}]

What have I to do?
Thank you.

This is likely due to a pending Arkose challenge or email verification challenge. I'm working on automating the email verification challenges for specific mail clients. For now you'll have to complete the challenges in the web app. I'll be adding some better error messages so this is more easily identified.

repo: trevorhobenshield/twitter-api-client


text:
Fix hardcoded history manager

Related Issue
#540
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have run the make format command to format my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have added my name and/or github handle to AUTHORS.rst
[x] I have added my change to CHANGES.rst
[x] All new and existing tests passed.

Codecov Report

Merging #542 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #542      +/-   ##
==========================================
+ Coverage   97.71%   97.72%   +0.01%
==========================================
  Files          17       17
  Lines         830      834       +4
  Branches      114      114
==========================================
+ Hits          811      815       +4
  Misses          8        8
  Partials       11       11

Impacted Files
Coverage Δ

simple_history/admin.py
98.07% <100%> (+0.03%)
:arrow_up:

...ory/management/commands/clean_duplicate_history.py
100% <100%> (ø)
:arrow_up:

simple_history/utils.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io yetanotherape

repo: treyhunner/django-simple-history