text:
Super confusing error and the plugin randomlyh stopped working

I had been getting:

 ====================
[7/15/2022, 11:53:12 PM] ERROR LOADING PLUGIN homebridge-am43-blinds:
[7/15/2022, 11:53:12 PM] Error: The module '/usr/lib/node_modules/homebridge-am43-blinds/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 83. This version of Node.js requires
NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1189:18)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-am43-blinds/node_modules/@abandonware/bluetooth-hci-socket/lib/native.js:6:15)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)

So I tried uninstalling the plug in and reinstalling. That's when the real trouble started:
npm ERR! code 243
npm ERR! git dep preparation failed
npm ERR! command /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/homebridge/.npm --prefer-offline=false --prefer-online=true --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm ERR! code EACCES
npm ERR! npm ERR! syscall mkdir
npm ERR! npm ERR! path /usr/lib/node_modules/@abandonware
npm ERR! npm ERR! errno -13
npm ERR! npm ERR! Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/@abandonware'
npm ERR! npm ERR!  [Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/@abandonware'] {
npm ERR! npm ERR!   errno: -13,
npm ERR! npm ERR!   code: 'EACCES',
npm ERR! npm ERR!   syscall: 'mkdir',
npm ERR! npm ERR!   path: '/usr/lib/node_modules/@abandonware'
npm ERR! npm ERR! }
npm ERR! npm ERR!
npm ERR! npm ERR! The operation was rejected by your operating system.
npm ERR! npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! npm ERR!
npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! npm ERR! permissions of the file and its containing directories, or try running
npm ERR! npm ERR! the command again as root/Administrator.
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR!     /home/homebridge/.npm/_logs/2022-07-16T05_33_46_980Z-debug-0.log

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/homebridge/.npm/_logs/2022-07-16T05_33_30_242Z-debug-0.log

Operation failed. Please review log for details.

There were some issues with my npm having two separate installations, but I resolved those and still was getting the error.
I saw a few other bugs that told me to run it unsafe, so I ran: sudo npm install -g --unsafe-perm=true --allow-root homebridge-am43-blinds@0.3.0
This yielded:
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/abandonware/noble.git
npm ERR! Warning: Permanently added the ECDSA host key for IP address '140.82.114.4' to the list of known hosts.
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-07-16T05_34_15_912Z-debug-0.log

The entire log file is massive and I can send it over later, but it looks like some weird git hub authentication. I'm starting to think there's an issue with abandonware or something. I have also tried: https://github.com/renssies/homebridge-am43-blinds/issues/40#issuecomment-987732496
anyone else facing this? Any solutions?

The first error you got was because noble (the Bluetooth package this plugin uses) is using bindings to communicate with bluetooth, however these bindings have to be recompiled every time you update node, even for minor versions.
The seconds errors you were getting were because something changed in NPM with install git packages, I've changed how @abandonware/noble is included in the package, this should solve the install issues.
However I've decided to officially deprecate the plugin because it's hard to get bluetooth working stable using either Node or Python, instead I'm now using a ESP32 based bridge. You can read more about it here: https://github.com/renssies/homebridge-am43-blinds/issues/41#issuecomment-1186548675

Hey, yeah I get that. Thanks for your support up till this point. Helped me support pretty janky shades for a year or so. Honesty, I just switched to the mqtt esp32 solution and it's just way more stable. I think pi's just seem to not do super well with Bluetooth and I don't think that's your fault. Noble is weird. Also, yeah am43 Bluetooth is pretty garbage. I ordered some zigbee am43 earlier and I'm happy that they're coming in even if I currently am stable.


text:
Missing .bundle file

After fork/clone repo, update _config.yml and try to execute bundle exec jekyll build a error occur
$ bundle exec jekyll build
Could not locate Gemfile or .bundle/ directory

in master brach

You can try jekyll server instead.

Works :+1:
maybe you can remove bundle exec jekyll build from docs

"jekyll server" works, and "bundle exec jekyll build" is still failing.  Please do update the docs on this.

source: gharchive/issue

authors: Ridermansb Shellcat-Zero renyuanz

repo: renyuanz/leonids

license: mit

license_type: permissive

license_source: bigquery


text:
iOS15，播放器，抖音样式会偶现，但是滑动多条视频之后必现

用的tableView抖音样式，在滑动的时候，发现视频只有声音，没有画面，我通过查看发现，controlView的图层都不见了，但是断点里能打印controlView的值，但是图层就是看不到controlView了，不知道有没有朋友遇到过这个问题，如果遇到，不知道这个该怎么解决

不仅controlView，连ZFPlayerView,presentView，图层里都看不到了 ,playerView的封面，什么都看不到了，不知为啥

目前找到的原因，就是[self.tableView reloadData],在滑动到指定位置的时候，我就去发送请求，此时，数据还没到，我就去播放当前index下标的数据了，正在此时，请求的数据回来了，我刷新了表格，那就好家伙，直接就卡住了

请问你的问题解决了吗。我也遇到跟你一样的问题

我在#1246问题解决了我的问题，你也可以试试能不能解决你的问题

我在看issue的时候发现了这个，标记一下吧 #1246

authors: Mr-lins emiyajin

repo: renzifeng/ZFPlayer


text:
最最下面的的视频白色缓存条及进度条如何隐藏?

我尝试用以下方式都不管用
self.controlView.portraitControlView.slider.hidden = YES;
    self.controlView.bottomPgrogress.hidden = YES;

因为内部使用的是hidden来显示隐藏的，你要是不想显示可以改alpha值为0

authors: renzifeng xiaohange


text:
fix replicate.stream example

The docs for replicate.stream() don't have any input:
for await (const event of replicate.stream("meta/llama-2-70b-chat")) {
    process.stdout.write(`${event}`);
}

See https://github.com/replicate/replicate-javascript/tree/6dd5b21884e5dab8d137818e3c43ab14f4335f30#replicatestream
Let's update this to a working example.

Like this:
const input = {
  prompt: "Can you write a poem about open source machine learning?",
}

for await (const event of replicate.stream("meta/llama-2-70b-chat", { input })) {
  process.stdout.write(event.toString());
};

repo: replicate/replicate-javascript

license_source: github-api


text:
Skip zero-width character render

My game allows the user to enter text, when there is a zero-width character in the text component, the following error is generated causing the game to stop running, so I added a judgment to skip the rendering of the zero-width character.
Uncaught DOMException: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The source width is 0.

https://kaboomjs.com/play?code=eJwlwkEKwjAQBdB15hSfbkygWnsAb%2BFOXMTMQIJtB9IBi6seoF7Sk4j6ePd4Ux19oKTTbLDFcEJk9hdyXYdzliq7GRFPqbp%2FFLaMlGONyaSiTLAsGAvzIAdyJov5pn%2Bv2%2B%2Frv29CSy7poNUfW3wHuoYPK3oqNw%3D%3D&example=add

Yes, thank you!

source: gharchive/pull-request

authors: luluxia slmjkdbtl

repo: replit/kaboom

license: MIT


text:
Fails on this.findTestItem(this.testItems, test.title, playwrightProjectName).id

Hi,
I'm facing to the same issue described in #45
Versions tested :
"@playwright/test": "^1.24.2" "^1.25.1"
"@reportportal/agent-js-playwright": "^5.0.5","^5.0.4"
Reporter agent works well if i run test like this :
test("mytest", async ({ page, browser, context }) => {
//
}

But it will fail if i used describe in list file like :
export default function createTests() {
  test("mytest", async ({ page, browser, context }) => {
  //
  }
}

import { test } from "@playwright/test"
import x from "test.spec"
test.describe(x)

With error in AfterEach step :
/.../node_modules/@reportportal/agent-js-playwright/build/reporter.js:430
                        _b = this.findTestItem(this.testItems, test.title, playwrightProjectName), testItemId = _b.id, attributes = _b.attributes, description = _b.description, testCaseId = _b.testCaseId, predefinedStatus = _b.status;
                                                                                ^

TypeError: Cannot read properties of undefined (reading 'id')

This error occurs regardless of the value in the option includeTestSteps: true|false

Hello @vivienbcr !
Seems like this error occurs because you are using test.describe without a title.
At the moment (versions 5.0.0-5.0.6), the agent uses titles to build a tree of suites.
Therefore, as a workaround, I suggest to provide a title for the test.describe function.
We will fix this issue in future versions.

authors: AmsterGet vivienbcr

repo: reportportal/agent-js-playwright


text:
Make repository private

If this is just for testing, it might be best to make it private to avoid cluttering the organization view

Yes, we can, but I don't have enough rights to make it a private repo.

I think this should be public. The test suite will be an important resource for validating simulator images. We will want developers of simulator containers to use this test suite. In fact, we will want developers to contribute to this -- particularly archives that include models encoded in other languages such as CellML for which we don't yet have examples. For users, the test suite will serve as documentation of how we validated simulator images. For the community, this will also serve as a collection of example archives, which is somewhat lacking.

Makes sense. I was not sure what the intentions were with it. Using it as a common place to store examples is a great idea.

Akhil's intention might have been different. But I think its important for the test suite to be public.

My idea is about saving available OMEX archives that every developer can use for all containers(new one's in the future) for testing locally, which is the same.

Sent: Tuesday, July 07, 2020 at 3:39 PM
From: "Jonathan Karr" notifications@github.com
To: "reproducible-biomedical-modeling/Biosimulations_COMBINE_archive_test_suite" Biosimulations_COMBINE_archive_test_suite@noreply.github.com
Cc: "GMarupilla" marupilla@mail.com, "Comment" comment@noreply.github.com
Subject: Re: [reproducible-biomedical-modeling/Biosimulations_COMBINE_archive_test_suite] Make repository private (#1)

Akhil's intention might have been different. But I think its important for the test suite to be public.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

This is what I started in BioSimulations-utils, along with code to use containers to execute the archives.
This repository now has the archives. The code to execute the archives is still in BioSimulations-utils.

authors: bilalshaikh42 gmarupilla jonrkarr


text:
https://github.com/request/request/issues/3142

Summary

Simplest Example to Reproduce

request({
  method: 'GET',
  url: 'http://example.com', // a public URL that we can hit to reproduce, if possible
  more: { 'options': 'here' }
},

Expected Behavior

Current Behavior

Possible Solution

Context

Your Environment

software
version

request

node

npm

Operating System

Summary
Simplest Example to Reproduce
request({
  method: 'GET',
  url: 'http://example.com', // a public URL that we can hit to reproduce, if possible
  more: { 'options': 'here' }
},

Expected Behavior
Current Behavior
Possible Solution
Context
Your Environment
software	version
request
node
npm
Operating System

repo: request/request


text:
Selection view content should be copy-pasteable

As much as possible of the content in the selection view should be copy-pasteable. That way any interesting data or blueprint options can easily be extracted and re-used elsewhere when debugging or exploring recordings in Rerun.
Example use cases:

Live logging the pose output of a SLAM algorithm, finding five poses that you think make sense for the scene and copying the parameter values to use in another script (that might generate simulated sensor data).
Once #4649 has landed, copy paste the recording id and quickly log some complementary data from a throw away script
Open a folder with images with the viewer -> find a strange looking image -> copy it's path and pass it to another script

Adding on to this, the TextLog fields should also be copy pasteable

authors: genemerewether nikolausWest

repo: rerun-io/rerun


text:
Build error error: couldn't read crates/re_web_viewer_server/src/../web_viewer/re_viewer.js: No such file or directory (os error 2)

Describe the bug
'cargo buildthrowserror: couldn't read crates/re_web_viewer_server/src/../web_viewer/re_viewer.js: No such file or directory (os error 2)`
To Reproduce
Steps to reproduce the behavior:

cargo build

Expected behavior
Should build.
Desktop (please complete the following information):

Ubuntu 22.04.

Rerun version
commit 093fc88c370eba4c6

Unfortunately our in-repo build setup is slightly more complex. Running cargo build will build a lot of extra things that have additional requirements. Have a look at our build instructions on how to get started with the repository
Instead, we're relying on the pixi package manager. Once installed you can simply run pixi run rerun to build & start a debug version of the rerun viewer.

authors: Wumpf galou


text:
Release 0.11 forwardport (things on release branch that should go to main)

What

picked from #4347

Changelog, link fixes, doc fixes, release script fixes etc.
This is a collection of cherry picks from the release branch, some of them squashed and reordered for a more comprehensive commit log
[Draft until the release is actually through.]
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested app.rerun.io (if applicable)
[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

let's go with the release branch direclty - did so on the last few releases


text:
Initial advertising blast

I received a message from @TinaJAZ asking whether we have a small "ramping up for the 2024 Festival" blurb to include in the next issue of The Data Drip newsletter. I've asked when the deadline is.
This is probably something we could reuse and spread far & wide.
What do you think @lwdozal?

This sounds great! I'll start writing something up and send it out for you all to look over.

Here is a ChatGPT-inspired blurb draft. Please comment and edit as you see fit!!
ResBaz 2024: A Call to Innovators and Researchers!
We're thrilled to announce the return of ResBaz (Research Bazaar) 2024! Hosted right here at the University of Arizona, ResBaz champions cutting-edge digital literacy powering today's research frontier which accommodates the needs and preferences of our community members.
ResBaz 2024 will be an arena of collaboration and creativity where researchers from diverse disciplines gather to learn, share, and inspire. This year promises to be more engaging than ever with one day in-person and one day virtual, both days brimming with opportunities to enhance your digital research tools and skills.
Who Should Attend?
ResBaz is open to everyone passionate about research and innovation. Whether you're a seasoned digital researcher, a PhD or research master’s student, or a research technologist, this festival is the perfect venue to broaden your digital horizons. We particularly encourage students and professionals at all levels and from all disciplines to join us in this unique learning experience.
Why Attend?

Learn Next-Gen Skills: Dive into workshops and sessions led by experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? ResBaz is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events designed to make learning enjoyable and memorable.
As we continue to navigate the evolving landscape of modern research, ResBaz 2024 stands as a beacon of innovation and community. Stay tuned for more details on how you can be a part of this transformative event.

Check out the ResBaz2023 program to see what you can expect from this conference.!

Or wait, should I send this out to slack or our discussion board?

Will the other AZ universities host ResBaz at their institutions? Is it ResBaz or ResBaz AZ? What month is ResBaz?
What is this blurb for - pick and choose what one needs depending on the purpose? I tried to tighten it up a bit.
Announcing ResBaz 2024: A Call to Innovators and Researchers!
The University of Arizona will host ResBaz (Research Bazaar) 2024. As always, ResBaz is an arena of collaboration and creativity where researchers from diverse disciplines gather to learn, share, and inspire. This year’s two-day festival promises to be more engaging than ever with one day in-person and one day virtual, but both days brimming with opportunities to enhance your digital research tools and skills.
Yes, You Should Attend
Students and professionals from all disciplines are encouraged to join us. ResBaz is open to anyone passionate about research and innovation – seasoned digital researchers, PhD or research master’s students, research technologists, and the digital literacy curious. This ResBaz festival is the perfect venue to broaden your digital horizons.
Why You Should Attend

Learn Next-Gen Skills: Dive into workshops and sessions led by experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? ResBaz is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events.

ResBaz 2024 is innovative and community-centered. Stay tuned for more details on how you can be a part of this transformative event.
Check out the ResBaz2023 program to see what you can expect at this year’s RezBaz festival!

@lwdozal: Or wait, should I send this out to slack or our discussion board?

This is a fine place to discuss this. Feel free to post the link to this issue in Slack & the discussion board though.

Is there a ResBazAZ and/or ResBaz Festival logo?

Hi @TinaJAZ - I'm tagging you in the slack where I posted logos. You can also find them in this directory.

Hi @TinaJAZ and @lwdozal I copied your draft announcement over to a hackmd in case it's easier to collab there.
https://hackmd.io/@Y70LO71ESz2J0WloxAlrTQ/Hy2xs2Rsp/edit
This link is at the top of our planning committee notes.

Hi @TinaJAZ and @lwdozal I copied your draft announcement over to a hackmd in case it's easier to collab there. https://hackmd.io/@Y70LO71ESz2J0WloxAlrTQ/Hy2xs2Rsp/edit This link is at the top of our planning committee notes.

This is great! Thank you @hidyverse

Hello!! here is the Initial Save-the-Date Email/Slack message I will be sending out next Monday, please let me know if it needs more tweaking. PS I didn't include anything about NAU or ASU and figured we can include them in later emails.
Subject: Announcing ResBaz AZ 2024: A Call to Innovators and Researchers!
ResBaz AZ‘s annual data science festival, 2024, where researchers come together to level-up in digital research tools and skills will be hosted Wednesday, May 15 - Friday, May 17. In the spirit of a marketplace or bazaar, the Research Bazaar, ResBaz is a highly collaborative event where anyone, regardless of discipline or previous experience, can learn, share knowledge, find help, and have fun!
This year’s FREE three-day festival promises to be more engaging than ever for data beginners and digital experts alike with all three days brimming with opportunities to enhance your digital research tools and skills. The general three-day set-up is:
May 15: Online Conference
May 16: Unconference in-person
May 17: Traditional Conference in-person
Why You Should Attend

Learn Next-Gen Skills: Dive into workshops and sessions led by data experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? ResBaz Festival is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events.

ResBaz Festival 2024 is innovative and community-centered. Keep an eye out for speaker and volunteer opportunities, and in the meantime, check out the ResBaz 2023 program to see what you can expect at this year’s #ResBaz2024 festival!

Also, here's a Prospective Instructors/Facilitators Email taken from last year's verbiage (thanks Val!!)
Subject: Research Bazaar 2024 (ResBaz): Call for Instructors, Facilitators and  Volunteers
Hi all,
I am a member of the ResBaz AZ 2024 festival organizing committee. ResBaz AZ, short for Research Bazaar Arizona, is a community and an annual festival-style event that promotes data science literacy across Arizona.
The 6th annual ResBaz AZ festival is happening Wednesday, May 15 - Friday, May 17, 2024. This free, community driven, and highly collaborative event provides members of the university and surrounding communities with opportunities to “level up” in computational and digital tools for research.
We are seeking instructors and facilitators at UArizona, ASU, NAU, and other Arizona research facilities. Specifically, we are looking for volunteers (grad students, post-docs, faculty, etc.) who would be willing to hold/teach/lead a 30-120 minute workshop on a data science topic, or facilitate an unconference session that is a creative and collaborative endeavor. ResBaz AZ’s annual festival is a great opportunity to expand teaching experience in a low stakes and welcoming environment.
Please fill out our survey relaying your interest in teaching a workshop, facilitating an unconference session or volunteering your time. You are also encouraged to share the survey with other potential educators.
Thank you for your consideration!
[your name here]
http://arizona.researchbazaar.org/

I also added both to the github here: https://github.com/resbazaz/festival2024/commit/9287aeb880616ef5ceff6b8c228e65e4c1443e0f

Again, yes, I missed an important meeting. Here’s my input.
Advertising needs to be kept short. Too much trying to define what ResBaz and ResBaz AZ are loses the attention of those who might be interested in attending and it just gets in the way of those who are already familiar. Define them on the website and give some clarity to what and how “level up” means.
Subject: Announcing ResBaz AZ 2024: A Call to Innovators and Researchers!  Perhaps, I am misunderstanding, but the message below is not a call for innovators or researchers. It is merely a save-the-date announcement. At this time, they cannot register to attend or sign up to be a speaker or a volunteer. If it’s a call, it’s a call to hold the date on their calendars and make note of what ResBaz is. If you don’t tell people to put a hold on their calendar now, they will forget. Granted, there are no guarantees that they will  save the date either. Where are the in-person activities taking place?
Subject: Join Us - ResBaz 2024 for Innovators and Researchers!
SAVE-THE-DATE  /  JOIN US  /  SAVE-THE-DATE
ResBaz 2024https://researchbazaar.arizona.edu/ – May 15-17 (– taking place here, where are in-person events?)
ResBaz AZ hosts the annual data science festival, ResBaz, where researchers come together in the spirit of a marketplace or bazaar to level-up in computational and digital research tools and skills. The ResBaz festival is a highly collaborative event where anyone, regardless of discipline or previous experience, can learn, share knowledge, find help, and have fun!  Innovative and community-centered with a commitment to inclusiveness, the festival is scheduled slightly different each day and is open to all:
May 15: Online Conference
May 16: Unconference in-person
May 17: Traditional Conference in-person
Why You Should Join Us

Learn Next-Gen Skills: Dive into workshops and sessions led by data experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? The ResBaz festival is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events.

Put a hold on your calendar for ResBaz 2024 – May 15-17 and note that registration opens in ???.  Look for speaker and volunteer opportunities coming soon. In the meantime, check out the ResBaz 2023 programhttps://researchbazaar.arizona.edu/resbaz/Arizona2023.html to see what you can expect at this year’s #ResBaz2024 festival!
From: Laura W. Dozal @.>
Sent: Wednesday, March 6, 2024 3:20 PM
To: resbazaz/festival2024 @.>
Cc: Johnson, Tina L - (tina) @.>; Mention @.>
Subject: [EXT]Re: [resbazaz/festival2024] Initial advertising blast (Issue #4)
External Email
Hello!! here is the Initial Save-the-Date Email/Slack message I will be sending out next Monday, please let me know if it needs more tweaking. PS I didn't include anything about NAU or ASU and figured we can include them in later emails.
Subject: Announcing ResBaz AZ 2024: A Call to Innovators and Researchers!
ResBazhttps://researchbazaar.arizona.edu/ AZ‘s annual data science festival, 2024, where researchers come together to level-up in digital research tools and skills will be hosted Wednesday, May 15 - Friday, May 17. In the spirit of a marketplace or bazaar, the Research Bazaar, ResBaz is a highly collaborative event where anyone, regardless of discipline or previous experience, can learn, share knowledge, find help, and have fun!
This year’s FREE three-day festival promises to be more engaging than ever for data beginners and digital experts alike with all three days brimming with opportunities to enhance your digital research tools and skills. The general three-day set-up is:
May 15: Online Conference
May 16: Unconference in-person
May 17: Traditional Conference in-person
Why You Should Attend

Learn Next-Gen Skills: Dive into workshops and sessions led by data experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? ResBaz Festival is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events.

ResBaz Festival 2024 is innovative and community-centered. Keep an eye out for speaker and volunteer opportunities, and in the meantime, check out the ResBaz 2023 programhttps://researchbazaar.arizona.edu/resbaz/Arizona2023.html to see what you can expect at this year’s #ResBaz2024 festival!
—
Reply to this email directly, view it on GitHubhttps://github.com/resbazaz/festival2024/issues/4#issuecomment-1981922720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXWBKS6QQRHSNSUTGLUYUX3YW6I7ZAVCNFSM6AAAAABC5BMUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRHEZDENZSGA.
You are receiving this because you were mentioned.Message ID: @.@.>>

ok, I'll send out this email/slack message on Tuesday morning? We have a registration form but waiting to see if it's ready to go. If we get the ok on the initial registration form I'll change the verbiage to "sign-up" instead of "Save the date"
Subject: Announcing ResBaz AZ 2024: Save the date for Innovators and Researchers!
ResBaz AZ hosts the annual data science festival, ResBaz, where researchers come together in the spirit of a marketplace or bazaar to level-up in computational and digital research tools and skills. The ResBaz festival is a highly collaborative event where anyone, regardless of discipline or previous experience, can learn, share knowledge, find help, and have fun!  Innovative and community-centered with a commitment to inclusiveness, the festival is scheduled slightly different each day and is open to all:
May 15: Online Conference
May 16: Unconference in-person
May 17: Traditional Conference in-person
Why You Should Join Us

Learn Next-Gen Skills: Dive into workshops and sessions led by data experts to master the latest digital research tools and techniques.
Collaborate and Network: Connect with like-minded researchers from various fields, fostering interdisciplinary collaboration and community building.
Share Your Knowledge: Have something to teach? The ResBaz festival is the perfect platform to share your skills and contribute to the collective learning experience.
Have Fun: Yes, research can be fun! Engage in exciting activities, contests, and social events.

Put a hold on your calendar for ResBaz 2024 – May 15-17 and registration opens next week! Want to get involved? Look for speaker and volunteer opportunities coming soon.
In the meantime, check out the ResBaz 2023 programhttps://researchbazaar.arizona.edu/resbaz/Arizona2023.html to see what you can expect at this year’s #ResBaz2024 festival!

@channel I'm going to use the our resbaz email to send out the initial registration blast, but I'm wondering who to send it to!!! Should I give you all the final version so we send it our respective departments, or would you like to provide a list of emails for me to contact?

I'm actually just going to send out an initial save the date memo without the form because the forms asks users to check which day they want to participate, but we don't have set sessions or workshops yet so I'm not sure people would know when they want to show up. For example, I usually participate if I'm interested in a specific topic and not the day.

Hi Laura thanks for all your work on this! Let me try to address some of your concerns, here.

I'm actually just going to send out an initial save the date memo without the form

Let's focus on getting the save the date to Tina at DSI for the Data Drip as priority #1. If you have some initial departments to share with, that's great. Let's go ahead and make a list of who we email (in slack for now).
I agree it can go out without the form.

would you like to provide a list of emails for me to contact?

I think this is a good idea! Can you solicit slack #resbaz2024 or even #general channels for thoughts on who to spam with save the dates/registration emails?

going to use the our resbaz email

I've drafted your email there with some updates! LMK if you can't see it.

authors: TinaJAZ hidyverse julianpistorius lwdozal


text:
Cannot render email | TypeError: undefined is not an object (evaluating 'Object.hasOwn(Z,"renderToReadableStream")')

Describe the Bug
I am getting this error when sending email from bun@latest.
TypeError: undefined is not an object (evaluating 'Object.hasOwn(Z,"renderToReadableStream")')
at hasOwn (native:1:1)
at /node_modules/@react-email/render/dist/node/index.mjs:99:14
at G (/node_modules/@react-email/render/dist/node/index.mjs:21:24)
at processTicksAndRejections (native:7:39)

My code sample

import * as React from "react";
import { render } from "@react-email/render";
import { Resend } from "resend";
import MedTravelBooking, {
  MedTravelBookingSubject,
  MedtravelProps,
} from "./emails/medtravel-submission";

export async function sendMedtravelEmailToAdmin(
  email: string,
  data: MedtravelProps,
): Promise<any> {
  try {
    await resend.emails.send({
      from: FROM_EMAIL,
      to: email,
      subject: MedTravelBookingSubject,
      html: await render(<MedTravelBooking data={data} />, {
        pretty: true,
      }),
    });
  } catch (error) {
    console.error(error);
  }
  return true;
}

Which package is affected (leave empty if unsure)
@react-email/render
Link to the code that reproduces this issue

To Reproduce

import * as React from "react";
import { render } from "@react-email/render";
import { Resend } from "resend";
import MedTravelBooking, {
  MedTravelBookingSubject,
  MedtravelProps,
} from "./emails/medtravel-submission";

export async function sendMedtravelEmailToAdmin(
  email: string,
  data: MedtravelProps,
): Promise<any> {
  try {
    await resend.emails.send({
      from: FROM_EMAIL,
      to: email,
      subject: MedTravelBookingSubject,
      html: await render(<MedTravelBooking data={data} />, {
        pretty: true,
      }),
    });
  } catch (error) {
    console.error(error);
  }
  return true;
}

Expected Behavior
--
What's your node version? (if relevant)
No response

Have been having the same problem in Bun. Downgrading to 0.0.20 fixed the problem for me. Seems to have been introduced at some point after that.

Tried it myself on a blank project that just plain console logs a simple email rendered and got no error. Can you share a minimal repo that reproduces the error? @amjed-ali-k

I couldn't reproduce it locally either, happened in the oven/bun:2.0.0 docker image for me

+1 on this, getting same error on bun, ubuntu vps

after a bit of research bun add react@canary react-dom@canary seems to fix my issue
Bun Guide

Reproduction of this issue.
@gabrielmfern  You can find the reprod here.
Run bundled version using bun run start and it will throw the error.
https://github.com/amjed-ali-k/react-email-bun-bundler-bug
here is the screenshot

Should be fixed on the latest canaries!

bun add react@canary react-dom@canary

@gabrielmfern this fixed it for me. Tried all canaries from you guys and didn't fix the issue :)

@thisislvca your problem must be something else then, since it did work just fine in the original problem for this issue
here's the repro that it worked for https://github.com/amjed-ali-k/react-email-bun-bundler-bug

authors: 1finedev amjed-ali-k doepnern gabrielmfern thisislvca

repo: resend/react-email


text:
chore(react-email): add consistent twitch demo link whitespace

This PR moves whitespaces out of link tags to avoid link decorations to extend into whitespace between words like
- please[ reset your account password](https://demo.react.email/preview/twitch-reset-password#)
+ please [reset your account password](https://demo.react.email/preview/twitch-reset-password#)

thanks @Moshyfawn!

authors: Moshyfawn zenorocha

repo: resendlabs/react-email


text:
Update Dockerode to fix local push issue in standalone builds

Dockerode patch (https://github.com/apocas/dockerode/pull/445) has now been merged and released, which should let us fix #824 once and for all.
Change-Type: patch
---- Autogenerated Waffleboard Connection: Connects to #824

I totally agree bumping package version to explicitelly tell that we need that version to fix all known issues, but do we technically need this?
Since the CLI isn't using lock files of any kind, isn't the ^ going to pick the new version on install? (but obviously still have to do a fresh one before building the standalone version)

Since the CLI isn't using lock files of any kind, isn't the ^ going to pick the new version on install? (but obviously still have to do a fresh one before building the standalone version)

Yep, 100%. But this is a bug that specifically affects only the standalone build, so we need a fresh release to fix it, and merging this PR will trigger that nicely. Imo it's nicer to have a separate PR doing that (and thereby have a specific version & release) that fixes this, rather than having the fix bundled into whatever the next PR is that gets merged.
It's also useful to be explicit about the versions we need anyway. If we had a subdependency with a conflicting version for some reason then we could get an older version of Dockerode. With this change, we guarantee we're definitely always going to get a fixed version in future.

authors: pimterry thgreasi

repo: resin-io/resin-cli


text:
Request for Documentation on Devices for MultiContainer Mapping

I need a list of devices that must be mapped through to allow electron to start so that I can segment off my other containers from interfering with the display.

devices:
  - "/dev/tty0:/dev/tty0"
  - "/dev/tty2:/dev/tty2"
  - "/dev/fb0:/dev/fb0"
  - "/dev/input:/dev/input"
  - "/dev/snd:/dev/snd"

This is the devices I used to test.  All other container need to be ran with just the devices they need access to.

repo: resin-io/resin-electronjs


text:
Revisit profiles activation to avoid relying on Maven 'activeByDefaul…

…t' which causes problem when needing to have multiple profiles enabled at the same time.

@kanovotn please have a look (just in case, the profile for eap should still be working fine).

Btw, I had to apply this locally for starting building using JDK 9 (which requires having an additional profile to be enabled only when jdk 9 is on)

repo: resteasy/Resteasy


text:
Speedup exclude/include checking

What does this PR change? What problem does it solve?
Backup (and restore) slow down a lot if a large number of excludes is used, see e.g. #2694. This PR optimizes the pattern processing to reduce the number and size of memory allocations. In total this speeds up the benchmarks by a factor between 5 and 76:
name                          old time/op    new time/op    delta
FilterPatterns/Relative-4       62.1ms ±15%    12.1ms ±23%  -80.56%  (p=0.000 n=9+10)
FilterPatterns/Absolute-4        111ms ±10%       9ms ±11%  -91.87%  (p=0.000 n=10+9)
FilterPatterns/Wildcard-4        393ms ±15%      42ms ± 5%  -89.27%  (p=0.000 n=10+10)
FilterPatterns/ManyNoMatch-4     10.0s ± 3%      0.1s ±20%  -98.69%  (p=0.000 n=10+10)

name                          old alloc/op   new alloc/op   delta
FilterPatterns/Relative-4       16.4MB ± 0%     3.6MB ± 0%  -78.25%  (p=0.000 n=10+9)
FilterPatterns/Absolute-4       31.4MB ± 0%     3.6MB ± 0%  -88.62%  (p=0.000 n=9+10)
FilterPatterns/Wildcard-4        168MB ± 0%      20MB ± 0%  -88.25%  (p=0.000 n=10+10)
FilterPatterns/ManyNoMatch-4    3.23GB ± 0%    0.00GB ± 0%  -99.89%  (p=0.000 n=10+9)

name                          old allocs/op  new allocs/op  delta
FilterPatterns/Relative-4         178k ± 0%       22k ± 0%  -87.50%  (p=0.000 n=10+10)
FilterPatterns/Absolute-4         266k ± 0%       22k ± 0%  -91.67%  (p=0.000 n=10+10)
FilterPatterns/Wildcard-4        1.87M ± 0%     0.09M ± 0%  -95.27%  (p=0.000 n=10+10)
FilterPatterns/ManyNoMatch-4     17.7M ± 0%      0.0M ± 0%  -99.88%  (p=0.000 n=9+10)

TheManyNoMatch test uses 200 exclude patterns which are suffixed such that these do not match any filenames, but require matching against the full pattern which is the worst-case performance wise. Originally I've tried to add all 22k tested filepaths to the filter patterns, however that was way too slow.
Assuming restic should be able to check 20k excludes per second (i.e., 1.2 million excludes per minute), one "op" of the ManyNoMatch benchmark shouldn't take much more than one seconds. With the optimizations I'm currently able to increase the number of exclude pattern to 2000.
Was the change discussed in an issue or in the forum before?
The exclude performance problems were in parts discussed in #2694.
Checklist

[x] I have read the Contribution Guidelines
[x] I have enabled maintainer edits for this PR
[x] I have added tests for all changes in this PR The code already had a lot of tests, I've added some special case tests to increase coverage to 95%
[ ] I have added documentation for the changes (in the manual)
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[x] I have run gofmt on the code in all commits
[x] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

I've fixed the "ManyNoMatch" (previously "Many") benchmark to actually work as intended and to cause the worst-case performance.

Profiling the optimized code now reports that more than half of the time is spent in hasDoubleWildcard. However, optimizing that function away just shifts the costs to some other part of the match function. So it looks like the string comparisons begin to be memory-bound.

Impressive result. I implemented my glob-to-regexp translation idea, and while it gets rid of the allocations, it's almost twice as slow as the current code.

MichaelEischer/restic#1 gives a further 25% speedup on the hardest benchmark.

@greatroar Wow, thanks for the extra speed-up. I've updated the comparison in the PR description, now we're at a speed-up by a smooth factor of 100. 🥳

authors: MichaelEischer greatroar

repo: restic/restic


text:
Updated to use modern Romanian Unicode

Updating to use modern Romanian Unicode as per https://github.com/apache/lucene/pull/13233
> Task :modules:analysis-common:yamlRestTest

REPRODUCE WITH: ./gradlew ':modules:analysis-common:yamlRestTest' --tests "org.opensearch.analysis.common.CommonAnalysisClientYamlTestSuiteIT.test {yaml=analysis-common/20_analyzers/romanian}" -Dtests.seed=97D676B50D8CFDF2 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=ky-Cyrl-KG -Dtests.timezone=Europe/Istanbul -Druntime.java=21

CommonAnalysisClientYamlTestSuiteIT > test {yaml=analysis-common/20_analyzers/romanian} FAILED
    java.lang.AssertionError: Failure at [analysis-common/20_analyzers:951]: tokens.0.token didn't match expected value:
                    tokens.0.token: expected String [absenţ] but was String [absenț]
        at __randomizedtesting.SeedInfo.seed([97D676B50D8CFDF2:1F82496FA370900A]:0)
        at org.opensearch.test.rest.yaml.OpenSearchClientYamlSuiteTestCase.executeSection(OpenSearchClientYamlSuiteTestCase.java:460)
        at org.opensearch.test.rest.yaml.OpenSearchClientYamlSuiteTestCase.test(OpenSearchClientYamlSuiteTestCase.java:433)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1750)

@reta Small PR to fix analyzer REST Integs

./gradlew :rest-api-spec:yamlRestTest  is passing locally for me.

@msfroh @reta Small PR to fix analyzer REST Integs

Thanks @expani !

authors: expani reta

repo: reta/OpenSearch


text:
A way to reduce winapi-*-pc-windows-gnu?

Currently, they are almost 100MB big, which is a bit of a problem when using cargo-vendor.
Is there a way to reduce their size or make them optional?

Those import libraries are necessary when targeting pc-windows-gnu unfortunately, and there's nothing sane I can currently do to improve the situation. However once https://github.com/rust-lang/rust/issues/58713 is implemented I will be able to eliminate them entirely.

I see. Thanks.


text:
Tab for settings dissapeared in Zotero preferences

As described in the headline, I am not able anymore to access the Settings of better-bibtex in Zotero since a recent (I don't know which) update of this great tool. Here my Report-ID: 9SD96RWH-euc
Things I have tried so far without success:

restart Zotero
reinstall Zotero
remove and reinstall better-bibtex (with restarting Zotero several times in between)
disable and enable better-bibtex (with restarting Zotero several times in between)

Support is appreciated and thank you in advance!

Debug log.

Thank you very much for the quick response.
My apologies! I have searched for a duplicate, but couldn't find any - probably used the wrong keywords.

You have nothing to apologize for.

authors: dagdrommer retorquere

repo: retorquere/zotero-better-bibtex


text:
Improve visual design

The visual design is very bare bones. As the default theme, it needs a better look and feel to promote RetroHub.

With the upcoming refactor to Godot 4, it's a good opportunity to completely overhaul this theme, so the theme will be redesigned.

Closed with #44

repo: retrohub-org/default-theme


text:
Investigate --import flag for CI steps

https://github.com/godotengine/godot/pull/90431 adds a new CLI flag to ensure Godot imports the project before attempting to export it. This is needed as otherwise a lot of script/asset errors occur, and the final build is broken.
However, this would imply having to compile a custom editor build just to take advantage of it. For now we are using the timeout hack, but when this makes into a public build, we can switch to the new version.

Also would be a good idea to check if this import step is indeed the root cause of #245.

repo: retrohub-org/retrohub


text:
Log exception messages and do not throw them to user

Depends on implementation #57.

Try static logger or %throwable in Pattern

repo: retverd/jira-progress-reporter


text:
Error: attept to write to not existing history file

Here:
https://github.com/reubeno/brush/blob/main/brush-interactive/src/interactive_shell.rs#L137
If a parent directory not found. Brush can't create a history file and exits with a non informative error:
ERROR error: input error: No such file or directory (os error 2)

In my case it is /Users/ig/.local/state/bash/history

Agreed. Sounds like this should definitely be a non-fatal error (or perhaps quieter warning) instead.
I know there are some outstanding TODOs related to history file management, in general. I don't recall offhand if we're honoring the standard configuration options/variables to customize where the history file is stored, whether it's written or appended to, etc.

It looks like bash does as I suggested earlier -- swallows the error without creating/appending to the history file. I'm proposing a change to do this (see PR link above).

repo: reubeno/brush


text:
How to enable session compression to reduce cookie size?

Hi, I already set the environment variable  KONG_X_SESSION_COMPRESSOR=zlib in my docker-compose.yml, but the cookies are still same size,  more than 5000 bytes. Are there any other parameters I need to set?
This is my docker-compose.yml
version: '3.4'

networks:
  kong-net:

volumes:
  kong-datastore:

services:
  kong-db:
    image: postgres:9.6
    volumes:
      - kong-datastore:/var/lib/postgresql/data
    networks:
      - kong-net
    ports:
      - "5432:5432"
    environment:
      POSTGRES_DB: kong
      POSTGRES_USER: kong
      POSTGRES_PASSWORD: kong

  kong:
    image: revomatico/docker-kong-oidc:2.3.3-1
    volumes:
      - /data/solution/docker/kong/nginx_kong.lua:/usr/local/share/lua/5.1/kong/templates/nginx_kong.lua
      - /data/solution/www:/var/www/
    depends_on:
      - kong-db
    networks:
      - kong-net
    extra_hosts:
      - "sg.digitalgd.com.cn:172.16.0.3"
      - "ywpt.digitalgd.com.cn:172.16.16.43"
    ports:
      - "38000:8000" # Listener
      - "38001:8001" # Admin API
      - "38443:8443" # Listener  (SSL)
      - "38444:8444" # Admin API (SSL)
    environment:
      KONG_DATABASE: postgres
      KONG_PG_HOST: kong-db
      KONG_PG_PORT: 5432
      KONG_PG_DATABASE: kong
      KONG_PG_USER: kong
      KONG_PG_PASSWORD: kong
      KONG_PROXY_LISTEN: 0.0.0.0:8000, 0.0.0.0:8443 ssl
      KONG_ADMIN_LISTEN: 0.0.0.0:8001, 0.0.0.0:8444 ssl
      KONG_PLUGINS: bundled,oidc
      KONG_X_SESSION_COMPRESSOR: zlib

Never used zlib, since we do not use cookie.
However, taking a closer look at the lua-resty-session docs, there were a couple of missing dependencies for zlib. Added them to the dockerfile and created release https://github.com/revomatico/docker-kong-oidc/releases/tag/2.3.3-2.
Can you please test it and see if it works for you? Also some logs would help.

Hi @cristichiru Adding those dependencies should not be required. They are already included in the kong base image:
$ docker run -it --rm kong:2.3.3-alpine luarocks list |egrep -A2 'penlight|lua.ffi.zlib'
lua-ffi-zlib
   0.5-0 (installed) - /usr/local/lib/luarocks/rocks-5.1

--
  penlight
   1.9.2-1 (installed) - /usr/local/lib/luarocks/rocks-5.1

@bigbugbean For me the compression is working with the earlier image already and I have seen it compress cookie by 2-3x. But cookie can still exceed 4kB depending on OIDC provider.
Your compose file replaces /usr/local/share/lua/5.1/kong/templates/nginx_kong.lua file with a custom version. Does your custom file include OIDC plugin related changes (see https://github.com/revomatico/docker-kong-oidc/blob/master/Dockerfile), including:
$ docker run -it --rm revomatico/docker-kong-oidc:2.3.3-1  cat /usr/local/share/lua/5.1/kong/templates/nginx_kong.lua|grep compres
    set $session_compressor ${{X_SESSION_COMPRESSOR}};

thank you @hanlaur for taking a serious look at this. So it should be safe to unpollute an already hacked Dockerfile with those dependencies.

authors: bigbugbean cristichiru hanlaur

repo: revomatico/docker-kong-oidc


text:
Add option/fix for user models with UUIDs

This line from 0b48ae39382cc5fff18a6d53a931cdf65506f99c assumes that all IDs on the user model will be convertible to integers, which isn't the case for UUIDs.
I add a new option: TOS_ID_FUNC that is the callable to use to convert user IDs, and have it default to int for backwards (and very common) compatibility. Developers who have UUIDs on their user models can specify either str or uuid.UUID as the conversion function.

Thanks for the PR!
Now that i'm looking at the diff of the offending commit, i'm wondering why I even bothered adding the int call. Seems that before my changes, the type returned from request.session.get(session_key) was unicode.
Tests seems to pass if I simply remove the int. Did you happen to give that a try? If we can avoid adding more configuration, I think that's the ideal fix.

Good call. I updated the PR, so you will probably want to squash and commit this.
Thanks!
I have a few more fixes/tests coming up as well.

Nice, thanks

authors: blag nicholasserra

repo: revsys/django-tos


text:
Update cats-effect-laws, cats-effect-std to 3.5.2

About this PR
📦 Updates

org.typelevel:cats-effect-laws
org.typelevel:cats-effect-std

from 3.3.14 to 3.5.2
📜 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.typelevel" } ]

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

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

Superseded by #701.

repo: rewards-network/pure-aws


text:
Attribute Replication Cleanup

This PR alters attributes to be replicated more conservatively, so we're not just replicating the entire collection of attributes all at once.

FAttribute now inherits FFastArrayItem.
FUnboundAttributeSet now inherits FFastArraySerializer and thus will use delta updates to replicate attributes.
The above change means that unbound attributes are not created except on the authority, otherwise they get doubled on the first update from an FFastArraySerializer.
BoundAttributes is no longer an instanced struct; it instead binds to the Value, BaseValue, and modifiers for each bound attribute, allowing those float values to be independently updated.
Bound attributes are now sorted by attribute tag when instanciated, ensuring a consistent order for them for purposes of binding.

I've tested this PR in both my own game project and in the GMAS + GMCEx template project, and in both cases it works successfully. However, it would probably be best if one or both of you did a sanity-check pass and tried it in your own game as well!

@reznok - Any thoughts on this, or should we merge it in?

repo: reznok/GMCAbilitySystem


text:
Deprecated tags

//# should be used instead of //@ because its deprecated.

Thanks! It seems there are a couple sourcemap related issues in the build at the moment (eg #23). I haven't had much time to look into it or much luck getting to the bottom of it, unfortunately. I would be happy to accept a PR!

@rfunduk : I will try to make a PR. //@ was generating warnings in our website, thats how I noticed it.

authors: Shafaet rfunduk

repo: rfunduk/jquery-tourbus


text:
Maximum call stack size exceeded

hello, this Adapter always throw Errors in my log. The Data points do refresh, so i'm still able to use this Adapter, but it spams my Log with Error Messages.
the exact log is:

daswetter.0
2018-10-12 09:52:06.015
error
at WS.Transport.onPacket  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8)

daswetter.0
2018-10-12 09:52:06.015
error
at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)

daswetter.0
2018-10-12 09:52:06.015
error
at WS.  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10)

daswetter.0
2018-10-12 09:52:06.015
error
at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14)

daswetter.0
2018-10-12 09:52:06.015
error
at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)

daswetter.0
2018-10-12 09:52:06.015
error
at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

daswetter.0
2018-10-12 09:52:06.015
error
at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16)

daswetter.0
2018-10-12 09:52:06.015
error
at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14)

daswetter.0
2018-10-12 09:52:06.015
error
at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9)

daswetter.0
2018-10-12 09:52:06.015
error
at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12)

daswetter.0
2018-10-12 09:52:06.015
error
RangeError: Maximum call stack size exceeded

daswetter.0
2018-10-12 09:52:06.013
error
uncaught exception: Maximum call stack size exceeded

to solve that issue I need some more information:

how many and which data path do you use?
how often do you call to update?
which system and OS do you use?
are there more and other logs available? Probably you can switch to debug mode and send the log again?

thanks for your fast response, here are the additional Informations:
how many and which data path do you use?
I use all 4 paths (first Link is the standard one, 2. with &v=2.0, 3. with &v=2.0&h=1 and 4. with &v=3.0)
before the addition of the json Data Structure Link in your project it worked fine.
how often do you call to update?
every 30 Minutes
which system and OS do you use?
I use an Rock64(like an Raspberry Pi but with 4GB of Ram) and it runs a nightly Debian build (but it worked on this exact Hardware some Time ago)
are there more and other logs available? Probably you can switch to debug mode and send the log again?
Here they are:

host.ioBroker-Rock64
2018-10-12 18:58:06.962
info
instance system.adapter.daswetter.0 terminated with code 0 (OK)

daswetter.0
2018-10-12 18:58:06.846
debug
update already running

daswetter.0
2018-10-12 18:58:06.845
debug
got undefined days

daswetter.0
2018-10-12 18:58:06.723
debug
calling  forecast hourly JSON:  http://api.daswetter.com/index.php?api_lang=de&localidad=27062&affiliate_id=tzb7n666mtui&v=3.0

daswetter.0
2018-10-12 18:58:06.723
debug
update already running

daswetter.0
2018-10-12 18:58:06.722
debug
hourly forecast done, objects in list 2639

daswetter.0
2018-10-12 18:58:06.417
error
RangeError: Maximum call stack size exceeded     at exports.active (timers.js:152:3)     at createSingleTimeout (timers.js:486:3)     at setTimeout (timers.js:466:10)     at Socket.onHeartbeat (/opt/i

daswetter.0
2018-10-12 18:58:06.417
error
uncaught exception: Maximum call stack size exceeded

daswetter.0
2018-10-12 18:58:06.416
debug
got 129 channels

host.ioBroker-Rock64
2018-10-12 18:58:06.322
info
instance system.adapter.tankerkoenig.0 terminated with code 0 (OK)

tankerkoenig.0
2018-10-12 18:58:06.113
info
objects written

tankerkoenig.0
2018-10-12 18:58:05.811
info
starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v8.12.0

daswetter.0
2018-10-12 18:58:05.106
debug
calling  forecast hourly:  http://api.daswetter.com/index.php?api_lang=de&localidad=27062&affiliate_id=tzb7n666mtui&v=2.0&h=1

daswetter.0
2018-10-12 18:58:05.106
debug
update already running

daswetter.0
2018-10-12 18:58:05.104
debug
5 days forecast done, objects in list 1053

daswetter.0
2018-10-12 18:58:02.622
debug
calling  forecast 5 days:  http://api.daswetter.com/index.php?api_lang=de&localidad=27062&affiliate_id=tzb7n666mtui&v=2.0

daswetter.0
2018-10-12 18:58:02.622
debug
objects in list: 107

daswetter.0
2018-10-12 18:58:02.621
debug
7 days forecast done, objects in list 107

daswetter.0
2018-10-12 18:58:02.369
debug
calling forecast 7 days: http://api.daswetter.com/index.php?api_lang=de&localidad=27062&affiliate_id=tzb7n666mtui

daswetter.0
2018-10-12 18:58:02.369
debug
using new datastructure

daswetter.0
2018-10-12 18:58:02.369
debug
checking data structures

daswetter.0
2018-10-12 18:58:02.369
debug
deleting unused dataset

daswetter.0
2018-10-12 18:58:02.369
debug
set timeout to 300 sec

daswetter.0
2018-10-12 18:58:02.369
info
starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.daswetter, node: v8.12.0

The really strange thing is, that it sometimes work without anny Error, then sometimes it throws only the 2 Errors seen in this log and in a nother Time it throws a larger Error (the one seen in my previous Post).

The log gives two hints:

with "got undefined days" I assume you do not have actual values for json data path (at least for that data call)
"got 129 channels" gives the hint, that we try to remove old data structure (from version 1.x of daswetter-adapter)

So you could try two things:

deactivate json data path (just delete URL in adatpter settings)
disable "delete unused data structure" also in adapter settings

Please do it one by one to see the result. Thanks for your help.

I am facing the same issue...

does disabling of "delete unused data structure" also avoid the error on your system?

does disabling of "delete unused data structure" also avoid the error on your system?

Yes.. After disabling the option everything seems to be fine. :relaxed:

Must be better in 2.7.1: https://github.com/rg-engineering/ioBroker.daswetter/pull/29


text:
--print-traffic not working in Windows binary

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.07.17. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.07.17

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

Description of your issue, suggested solution and other information
print-traffic option not showing any effect in the Windows binary.
PS: Is that related to https://github.com/rg3/youtube-dl/issues/9365 ?

--print-traffic does not work prior to Python 3.5.2. Windows build is built against Python 3.4.4.

Will that change?

What that?

The version of Python that the Windows binary is based on, will it be built with 3.5.2 or higher at a later point to solve the problem?

Using Python 3.5.x version for Windows build means dropping support for Windows XP. Separate 3.4.x and 3.5.x builds may be provided in future however I don't see pressing need for this at the moment.

Duplicate of #9365. Please move to #10014 for further discussion.

authors: dstftw spookyahell yan12125

license: Unlicense


text:
[cookscountry] Restore high bitrate video extraction and avoid certificate errors

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.11.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.11.18

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.cookscountry.com/episode/554-smoky-barbecue-favorites']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2018.11.18
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg N-92266-gbf324359be, ffprobe N-92266-gbf324359be
[debug] Proxy map: {}
[generic] 554-smoky-barbecue-favorites: Requesting header
WARNING: Could not send HEAD request to https://www.cookscountry.com/episode/554-smoky-barbecue-favorites: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)>
[generic] 554-smoky-barbecue-favorites: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)> (caused by URLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)'),))
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph_ixabnp\build\youtube_dl\extractor\common.py", line 605, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph_ixabnp\build\youtube_dl\YoutubeDL.py", line 2211, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 464, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 482, in _open
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph_ixabnp\build\youtube_dl\utils.py", line 1139, in https_open
  File "C:\Python\Python34\lib\urllib\request.py", line 1185, in do_open
...
<end of log>

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--no-check-certificate', '--list-subs', 'https://www.cookscountry.com/episode/554-smoky-barbecue-favorites']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2018.11.18
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg N-92266-gbf324359be, ffprobe N-92266-gbf324359be
[debug] Proxy map: {}
[generic] 554-smoky-barbecue-favorites: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 554-smoky-barbecue-favorites: Downloading webpage
[generic] 554-smoky-barbecue-favorites: Extracting information
[download] Downloading playlist: Smoky Barbecue Favorites
[generic] playlist Smoky Barbecue Favorites: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[Zype] 5b400b834b32992a310622b9: Downloading webpage
[Zype] 5b400b834b32992a310622b9: Downloading m3u8 information
5b400b834b32992a310622b9 has no subtitles
[download] Finished downloading playlist: Smoky Barbecue Favorites
...
<end of log>

Description of your issue, suggested solution and other information
With previous versions of youtube-dl, high bitrate (2GB per episode) H.264 videos were able to be downloaded from cookscountry.com along with the accompanying subtitles. However, on the latest version, the --no-check-certificate argument is needed to download any videos (only the lower bitrate one is available) and subs are not able to be downloaded. Thank you.

With previous version you can't even download this as zype platform was not supported.
As per SSL error - nothing to do with youtube-dl. Most likely you miss some root certificates in your system store. Also no such 2GB per episode is available for this video.

It looks like ATK has switched from Kaltura to Zype.  They used to offer 25Mb/s 1080p streams, but no longer do.

authors: StevenDTX blue240 dstftw


text:
Determining file size without downloading

How do I know the total size of the video without downloading?
Thank you.

@phihag Could you please leave a python example on how to do it. Would be much appreciated. Been looking in all of the repository for one...

Hack /usr/lib/python2.7/site-packages/youtube_dl/downloader/http.py
update line 142 and add there print(data_len)
do not forget delete /usr/lib/python2.7/site-packages/youtube_dl/downloader/http.pyc
to update changes
then you can use --max-filesize 1k to skip downloading

you can use also grep to filter filesize only
for example
youtube-dl -f 22 --max-filesize 1k https://www.youtube.com/watch?v=hfTta26iiJ4|grep "^[0-9]"

authors: Joaobranquinho rikato06 sjurajpuchky


text:
Anime on Demand: Can only download episode 1

Hello, when I want to download a series on Anime on Demand, youtube-dl downloading only episode 1 as many times as there are episodes. You can test it with this: https://www.anime-on-demand.de/anime/152
Another problem is the downloading of trailers. I think nobody wants to download the trailer and it’s really irritating when I want to download only episode X.
Example: When I want to download 3, I need to make “--playlist-items 5”.
Regards.

Post the full output of youtube-dl when run with -v, i.e. add -v flag to your command line, copy the whole output and post it in the issue body wrapped in ``` for better formatting. It should look similar to this:
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.06
[debug] Git HEAD: 135392e
[debug] Python version 2.6.6 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...

Do not post screenshots of verbose log only plain text is acceptable.
The output (including the first lines) contains important debugging information. Issues without the full output are often not reproducible and therefore do not get solved in short order, if ever.

authors: Ninelpienel dstftw


text:
[openload] add oload.site domain

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Openload has another site clone oload.site, this PR adds this site to the _VALID_URL regex.

also an other domain : oload.xyz

@CharifMakaoui just wanted to add it, but it was already added in e944737c597a2f5e8e6ade93a25fc812119d4eb9 by dstftw

authors: CharifMakaoui steebchen


text:
[rtve] Add new extractor for rtve infantil

Updated RTVE extractor for download shows from http://www.rtve.es/infantil/

Merged, thanks.

sorry for the errors and thanks a lot for the merge...

No problem.
Do you want to be listed in the AUTHORS file? If so, under which name?

Of course,  Eduardo Ferro Aldama :-)
Thanks

authors: eferro jaimeMF


text:
🛑 Sito Web is down

In 6becc73, Sito Web (https://www.comune.preganziol.tv.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sito Web is back up in cea15a0 after 6 minutes.

repo: rglauco/upptime


text:
Fixing DevicePlugin upgrade from v1.x to v2.x (#679)

In v1.x we had 2 type of Daemonsets: DevicePlugin and ModuleLoader, which could be distingished by the DaemonsetRole label In v2.x, there only 1 type of daemonset, DevicePlugin, so the DaemonsetRole labels was removed.
During DevicePlugin reconciliation, reconcile get all the device plugin Ds based only on module name label, which means that in case there is a v1.1 ModuleLoader DS running it will also be chosen. Once reconciler tries to reconcile ModuleLoader DS, it will fail
This PR, updates the function that chooses the DevicePlugin DS, by removing old ModuleLoader Ds based on Role label

/assign @ybettan

/test images

/lgtm
/retest

/test images

/test e2e

/test e2e-hub

/test ci-bundle-operator-bundle

/test ci-bundle-hub-operator-bundle

/test e2e-hub

/cherry-pick release-2.0

MGMT-16246

authors: qbarrand ybettan yevgeny-shnaidman


text:
Issue in grab_node_ext_ips (shared-utils)

Found an issue here:
The task "deploy-metallb" always failed for us because the node_ip could not be determined correctly.
For our DHCP network we have the network 192.168.70.0/24.
In the line here: https://github.com/rh-ecosystem-edge/ztp-pipeline-relocatable/blob/main/shared-utils/common.sh#L364C185-L364C185
the part "| select(. | contains("192.168.7") | not)" ensures that the networks:
192.168.7[0..9].0/XX are also sorted out. The addition of a point settles the issue:
"| select(. | contains("192.168.7.") | not)".
Resolution
$ oc get agent xxxxx-xxxxxxx-xxxxxxx-xxxxxxxxxx  --no-headers -ojson -n line-138-v12 | jq -r "(.status.inventory.interfaces[] | select(.name=="eno1")).ipV4Addresses[] | select(. | contains("192.168.7") | not)"
--> no output
$ oc get agent xxxxx-xxxxxxx-xxxxxxx-xxxxxxxxxx--no-headers -ojson -n line-138-v12 | jq -r "(.status.inventory.interfaces[] | select(.name=="eno1")).ipV4Addresses[] | select(. | contains("192.168.7.") | not)"
--> 192.168.70.27/24 (NodeIP)

@schmti you suggestion to fix this issue looks reasonable to me. Would you be so kind to submit a pull request with the fix? I would happily review and merge it.

@jhernand on which branch do you want the MR?
greets

@jhernand on which branch do you want the MR? greets

In the main branch, please.

authors: jhernand schmti


text:
Change error exit codes to help identify docker run errors from conta…

…iner errors
Signed-off-by: Sally O'Malley somalley@redhat.com

I think this will eventually satisfy  https://bugzilla.redhat.com/show_bug.cgi?id=1097344 and https://bugzilla.redhat.com/show_bug.cgi?id=1097334

Please submit upstream.  You still have a bogus white space field in your patch, and you need to write a big comment on what you are doing.
Cut and paste Regan's name to your pull request also. So you both get credit.

will do.

(Here are the test conditions I ran)
#/bin/bash
Test changes to api/client/run.go error codes
echo 'docker run contained process exits 1, expect 1:'
docker run fedora /bin/false; echo $?
echo
RESULT:    1
echo 'docker run non-existing image, expect 126:'
docker run foo; echo $?
echo
RESULT:    Unable to find image 'foo:latest' locally
                   Pulling repository foo
                   126

echo 'docker run image ok, cmd does not exist, expect 126:'
docker run fedora foo; echo $?
echo
RESULT:    exec: "foo": executable file not found in $PATH
                  126

echo 'docker run contained cmd could not execute, expect 127:'
docker run fedora /bin/foo; echo $?
echo
RESULT:    exec: "/bin/foo": stat /bin/foo: no such file or directory
                  127

echo 'docker run no errs, contained no errs, expect 0:'
docker run fedora /bin/true; echo $?
echo
RESULT:    0

I've replaced this pr with https://github.com/rhatdan/docker/pull/77

authors: rhatdan sallyom

repo: rhatdan/docker


text:
Error on non-existing arguments/parameters

This patch adds __slots__ to all API classes that use setattr magic and kwargs for function parameters. Besides reducing memory and speeding up access, the main point of this change is that a typo when calling a function will result in an error, rather than silently setting non-existing properties.
In [1]: import ev3dev.ev3 as ev3
In [2]: m = ev3.MediumMotor()
In [3]: m.run_to_abs_pos(position_sp=72*20, speed_sd=500, stop_action='coast')
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-08bcba75fb47> in <module>()
----> 1 m.run_to_abs_pos(position_sp=72*20, speed_sd=500, stop_action='coast')

/home/robot/ev3dev-lang-python/ev3dev/core.py in run_to_abs_pos(self, **kwargs)
    799         """
    800         for key in kwargs:
--> 801             setattr(self, key, kwargs[key])
    802         self.command = self.COMMAND_RUN_TO_ABS_POS
    803

AttributeError: 'MediumMotor' object has no attribute 'speed_sd'

Currently the last line would just set the speed_sd property on the object, without doing anything, leaving it up to you to figure out why your motor went berserk or did nothing at all.
With the proposed change, you get instant feedback that you're doing something stupid.

What is _bin_data_size, what is it used for, and what is that piece of code trying to do? Obviously a class with __slots__ has no __dict__, but it seems adding it to __slots__ and checking for None would have the same effect? The property is not used anywhere else in the project, so maybe it could also just be a local variable?

What is _bin_data_size, what is it used for, and what is that piece of code trying to do?

_bin_data_size stores the size of raw binary data to read from the sensor (see bin_data here).
In the code the field is used as a cache to store the value (and save an access to bin_data_format attribute). Initializing it with None should work as well.

If this makes property access faster it would be nice to see some timeit before and after. Could be a worthy addition to the release notes, since speed improvements help to cut latency on control loops.

yep I will give it a try

I'm not sure what a good test is to test performance of this change, TBH probably most time is spend talking to the kernel, compared to one dictionary lookup.
I fixed the data size, which was rather straightforward.
The helper classes require a bit more thought. __slots__ don't mix well with multiple inheritance. The internet consensus seems to be that if you run into this you're using __slots__ wrong. It is suggested that they are a memory optimisation, not a means to "freeze" classes. The "Pythonic" way that is suggested is to overwrite __setattr__, which would make things slower, if anything, though the impact is probably manageable.
As it stands now, using the helper classes would add an internal dict, allowing undefined attributes as before.

I think this one needs some more testing. I cannot pinpoint what is wrong but when using this patch my robot failed to solve the rubiks cube three times in a row, without this patch it can solve it everytime.  All motors look like they are rotating the correct amount (the cube would get jammed up otherwise) but I suspect one is turning in the wrong direction in some scenario.

Weird. No errors? (or things that swallow errors) If the robot is deterministic, I suppose you could use the same scramble and see where it goes wrong. Or just plain old printf debugging.Ik might be able to do some more testing, but simple things seemed to work and without knowing more it's hard to know where to look.Is this robot of yours one I can reproduce with my own ev3 (software and instructions available), or a custom monster with tons of extra parts?

Is this robot of yours one I can reproduce with my own ev3 (software and instructions available), or a custom monster with tons of extra parts?

This is not my robot, but I believe its built according to these instructions: http://mindcuber.com/mindcub3r/mindcub3r.html.
And the program is here: https://github.com/rhempel/ev3dev-lang-python/tree/develop/demo/MINDCUB3R

MINDCUBER is a good way to test, a lot of things have to be perfect for it to solve the cube.  I'm actually using my own cube solver now, if you have a 42009 (the big crane) then you can build it.  I need to put together instructions though.
Let me do this, I can put the cube back in the same scrambled state and record a video of it being solved with and without your patch.  Then I can compare the two videos side by side and see where it is behaving differently. That should help narrow it down a bit.

Ignore what I said, I suspect I have an error on my end.

A simple performance test shows there is a bit of improvement, or at least it is definitely not worse:
Before
>>> import timeit
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[4.144548124999972, 3.950399667000056, 4.128440291999993]
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.9438115419999917, 4.096679416999962, 3.8801820420000013]
>>>

After
>>> import timeit
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.8830312090000234, 4.003896959000031, 3.78919083400001]
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.8567800419999685, 3.932827876000033, 3.8972169590000476]
>>>

But I think the main idea here was to help users by catching semantic errors early.

Thanks!

Awesome. Still curious what happened on @dwalton76 's end though.

I have a bug where I sometimes assign the wrong color to a cube square based on the RGB values. In a nutshell you have 54 RGB tuples and from that you have to assign each square to be one of the six colors of the Rubik's cube. I had this fairly rock solid but have been working on this code to make it support 4x4x4, 5x5x5, etc cubes and must have introduced a bug because when I took a video of it solving with your patch in place I noticed that it got some of the color assignments wrong.

In another run I was able to solve a cube with your patch applied so the motor movements seem to be fine.

authors: ddemidov dwalton76 ensonic pepijndevos


text:
Fix bug unable to find tripleo schemas outside repo

When running a command like cibyl --jobs periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-internal-wallaby --pipeline check-rdo --project tripleo-downstream-trigger-nested-virt --ip-version against a zuul source, we get an error:
  File "/home/jgilaber/redhat/cibyl/tripleo/insights/interpreters.py", line 105, in __init__
    super().__init__(data, schema, overrides, validator_factory)
  File "/home/jgilaber/redhat/cibyl/tripleo/insights/interpreters.py", line 63, in __init__
    validator = validator_factory.from_file(schema)
  File "/home/jgilaber/redhat/cibyl/tripleo/utils/json.py", line 52, in from_file
    with open(file, 'r') as buffer:
FileNotFoundError: [Errno 2] No such file or directory: 'tripleo/_data/schemas/environment.json'
``
The default path to look for json schemas specified in the tripleo library
was specified as a relative path, which if run from a random
location would not find the schema files. This was solved by changing
the paths and making them relative to the tripleo package path, so it
can be located from any working directory.

The PR includes also one integration test that reproduced the issue for each of the interpreter classes (Environment, FeatureSet, Nodes and ReleaseInterpreters).

I am aware of that happening and I cover it by just setting the working directory from where the run is made. The working directory should be the project's root, which is what tox uses:

Would that not be enough?

For development maybe, but I for example have a folder dedicated to running cibyl, with different config files and other stuff, and run the commands from there. Also, after release, the users might run from some arbitrary path, and we can't expect them to run from the installation path.

I don't know. I imagine Cibyl will be mostly installed through PIP, and I have it installed through that on a virtual env where I have not had this problem. My insistence falls in that I assumed the project's root to be the start of any relative paths and this here is not the only place that will need to get changed.

Do you only run it through the IDE? Let me propose an scenario to make sure we are both on the same page. Let's imagine a user creates a virtualenv in ~/cibyl and installs cibyl via pip. If we don't merge this change, then the user will need to cd to ~/cibyl/lib/python-sth/site-packages/ to run cibyl from there, right? How do you imagine the users will run cibyl?

Ok, that's a reasonable change. While I do it, are there any other parts of the tripleo library that would require a similar change?

On tripleo I don't think so, but on cibyl there are. The good thing is that they are on the unfinished tests support for the Zuul-CI, so once I start with that again I will have this on my mind.
Great finding and great solution. It is not straightforward at all and I can see me spending some time to find it.

Ah, ok I see. Good to know then, I've updated the PR with the mentioned changes.

authors: cescgina jsanemet

repo: rhos-infra/cibyl


text:
Adapter storage

This is a change to how we think about storage with ProtocolAdapters. Previously I suggested that we have the Adapters inherit the same storage layout as the Instruments like InstrumentStorageV2 and so on.
But there are a few problems with this approach:

There is effectively no separation of storage between instruments and adapters
The new vault contracts will have to inherit the storage layout of both instruments and adapters which will make the situation very hairy
We need a single source of truth for adapter-specific states, it does not make sense to store adapter states on every single instance of Instrument contracts

Some initial thoughts on issues that may arise:

Right now we limit the write functions like setIdToAddress to instruments only. But what if an attacker took control of an instrument contract? They would be able to alter the state across multiple adapters, effectively infecting all our instruments.

@chuddster wdyt about this approach?

@chuddster wdyt about this approach?

I see, so you are decoupling storage between charm adapter and instrument to prevent single point of failure for an attack, make more dynamic? sgtm

Closing as it's already merged

authors: chuddster kenchangh

repo: ribbon-finance/structured-products


text:
Add total number of features & genes to check_fasta_gff?

Having recently used the newly refactored (#25) check_fasta_gff tool on the [example-datasets/#10 fly dataset] transcriptome files (https://github.com/riboviz/example-datasets/issues/10#issuecomment-782101703), I was wondering if a useful addition to the output might be the total number of features in the .gff.
Currently, the output is reported thus:
# Created by: RiboViz
# Date: 2021-02-18 19:42:25.510660
# Command-line tool: /exports/eddie3_homes_local/fanders6/riboviz/riboviz/riboviz/tools/check_fasta_gff.py
# File: /exports/eddie3_homes_local/fanders6/riboviz/riboviz/riboviz/check_fasta_gff.py
# Version: commit 7e62c9f8da4f66f9c18aca30394f44fa4a7fa1ef date 2021-01-20 10:18:00-08:00
# fasta_file: A-Dm_2014/Dmel_filtered.fasta
# gff_file: A-Dm_2014/Dmel_filtered_UTRreplace.gff3
# start_codons: ['ATG']
# NoStopCodon: 6953
# NoStartCodon: 6948
# InternalStopCodon: 6596
# IncompleteFeature: 33
# SequenceNotInGFF: 0
# SequenceNotInFASTA: 0
# MultipleCDS: 0
# DuplicateFeatureId: 0
# NoIdName: 0
# DuplicateFeatureIds: 0
Sequence	Feature	Issue	Data
CG33282-RB	31165	InternalStopCodon
CG10019-RD	31215	InternalStopCodon
CG43707-RI	31219	InternalStopCodon
lectin-28C-RB	31764	IncompleteFeature
lectin-28C-RB	31764	NoStopCodon	AGN
lectin-28C-RB	31764	InternalStopCodon
# ...
# a bunch more features & such.

While I'm not an expert in estimating the "usual" amount of issues in a .gff, it definitely would be more intuitive if I knew what proportion of all the features had an issue reported here, so I could decide to either:
a) bin the whole lot and start again after putting out the fire, or:
b) whether it's just in need of some selective tweaking to improve, or,
c)  if the transcriptome files are entirely fine to use as-is.
Currently, I need to do a few extra steps to figure out the number of features held in the .gff file and then do some envelope maths to get a better idea what's happening.  Given that the code is already checking uniqueness of feature IDs etc, then this might not be too much of a stretch?
@ewallace It'd be good to hear your thoughts on this, you've probably got a better feel for what you're looking for.

(Added to 'to review' so we can discuss at the dev meeting where to put this ticket)

I think we should do this, adding both:

total number of sequences in fasta file - should be easy as it's counting the number of keys in the dict of sequences
total number of features of each kind in gff file - counting CDS features is easy so the right place to start

This should be just a couple of lines of code.

Plus updates to riboviz.test.test_check_fasta_gff.

Commit 8e3603b of check-fasta-gff-total-features-genes-280 adds support for printing number of sequences, number of features, number of CDS features, and adding this to the TSV file header also.
$ python -m riboviz.tools.check_fasta_gff \
    -f data/yeast_CDS_w_250utrs.fa \
    -g data/yeast_CDS_w_250utrs.gff3 \
    -o check_data_CDS.tsv -v
...
Configuration:
fasta_file	data/yeast_CDS_w_250utrs.fa
gff_file	data/yeast_CDS_w_250utrs.gff3
start_codons	['ATG']

Metadata:
NumSequences	5812
NumFeatures	17436
NumCDSFeatures	5812

Issue summary:
Issue	Count
InternalStopCodon	17
NoStartCodon	1
DuplicateFeatureId	0
...

$ cat check_data_CDS.tsv
...
# fasta_file: data/yeast_CDS_w_250utrs.fa
# gff_file: data/yeast_CDS_w_250utrs.gff3
# start_codons: ['ATG']
# NumSequences: 5812
# NumFeatures: 17436
# NumCDSFeatures: 5812
# InternalStopCodon: 17
# NoStartCodon: 1
# DuplicateFeatureId: 0
...
Sequence	Feature	Issue	Data
Q0050	Q0050	InternalStopCodon
Q0055	Q0055	InternalStopCodon
Q0060	Q0060	InternalStopCodon
...

Created PR #299.

Merged and closed #299.

authors: FlicAnderson ewallace mikej888

repo: riboviz/riboviz


text:
🛑 FIR is down

In d011dba, FIR ($FIR_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FIR is back up in b138482 after 12 minutes.

repo: ricardoheil/test-uptime


text:
problem in viewing .srt

(base) ryanshenefield@Ryans-MBP ~ % /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -dump Type | grep -B10 -e "tags:.*srt"
type id:                    com.github.riccoyu.qlsubtitles.subrip (0x13f88)
bundle:                     Quick Look Subtitles (0xde7c)
uti:                        com.github.riccoyu.qlsubtitles.subrip
localizedDescription:       "en" = ?, "LSDefaultLocalizedValue" = "SubRip"
flags:                      active  exported  trusted (0000000000000051)
icons:                      0 values (180092 (0x2bf7c))
                            {
                            }
reference URL:              http://en.wikipedia.org/wiki/SubRip
conforms to:                public.plain-text
tags:                       .srt
--
--------------------------------------------------------------------------------
type id:                    com.goodsnooze.srt (0x5820)
bundle:                     MacWhisper (0x172c)
uti:                        com.goodsnooze.srt
localizedDescription:       "en" = ?, "LSDefaultLocalizedValue" = "Subtitle file"
flags:                      active  exported  trusted (0000000000000051)
icons:                      0 values (27740 (0x6c5c))
                            {
                            }
conforms to:                public.plain-text
tags:                       .srt, text/plain
--
tags:                       .bib

--------------------------------------------------------------------------------
type id:                    cz.wz.zuggy.subrip (0x58b8)
bundle:                     iA Writer (0x175c)
uti:                        cz.wz.zuggy.subrip
localizedDescription:       "Base" = ?, "de" = ?, "en" = ?, "es" = ?, "fr" = ?, "it" = ?, "ja" = ?, "ko" = ?, "LSDefaultLocalizedValue" = "SubRip", "pt" = ?, "ru" = ?, "zh-Hans" = ?, "zh-Hant" = ?
flags:                      active  imported  trusted (0000000000000041)
reference URL:              http://zuggy.wz.cz
conforms to:                public.plain-text
tags:                       .srt

type id:                    com.goodsnooze.srt (0x13c90)
bundle:                     MacWhisper (0xc088)
uti:                        com.goodsnooze.srt
localizedDescription:       "en" = ?, "LSDefaultLocalizedValue" = "Subtitle file"
flags:                      active  exported  trusted (0000000000000051)
icons:                      0 values (158320 (0x26a70))
{
}
conforms to:                public.plain-text
tags:                       .srt, text/plain
type id:                    com.github.riccoyu.qlsubtitles.subrip (0x1440c)
bundle:                     Quick Look Subtitles (0xe298)
uti:                        com.github.riccoyu.qlsubtitles.subrip
localizedDescription:       "en" = ?, "LSDefaultLocalizedValue" = "SubRip"
flags:                      active  exported  trusted (0000000000000051)
icons:                      0 values (181900 (0x2c68c))
{
}
reference URL:              http://en.wikipedia.org/wiki/SubRip
conforms to:                public.plain-text
tags:                       .srt

MacWhisper app exports a new UTI "com.goodsnooze.srt", which is "strong" to the os. QLSubtitles does not recognize this UTI. And there is no successful preview.
Fixed this issue in a new release

MacWhisper app exports a new UTI "com.goodsnooze.srt", which is "strong" to the os. QLSubtitles does not recognize this UTI. And there is no successful preview.
Fixed this issue in a new release

Thanks for your work, I tried again...(⊙o⊙)…The new version doesn't work for me either...😅

MacWhisper app exports a new UTI "com.goodsnooze.srt", which is "strong" to the os. QLSubtitles does not recognize this UTI. And there is no successful preview.
Fixed this issue in a new release

Thanks for your work, I tried again...(⊙o⊙)…The new version doesn't work for me either...😅

Please check:

[ ] delete every copy of the old version QLSubtitles app, empty trash, make sure only the newer version app left
[ ] if it doesn's work, try to reboot your mac

MacWhisper app exports a new UTI "com.goodsnooze.srt", which is "strong" to the os. QLSubtitles does not recognize this UTI. And there is no successful preview.
Fixed this issue in a new release

Thanks for your work, I tried again...(⊙o⊙)…The new version doesn't work for me either...😅

Please check:

[x]  delete every copy of the old version QLSubtitles app, empty trash, make sure only the newer version app left
[x]  if it doesn's work, try to reboot your mac

Cheked both. Didn't work...

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1500 in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @09libihao, @yumiao1121, @NiuwenC, @vlyl, @SamuelLin, @killerjun, @leeseon, @qingche123, @LovesAsuna, @NOMAD-design-arch, @xielingfan, @zhujunxi, @y3zha, @friendlysxw, @hadesvip, @flyer88, @mili-tan, @yesmeck, @cos-mos, @yuler, @XTeam-Wing, @ciknight, @Gradven, @justskinny5, @dasajia2lang, @philphp, @Kur1sut1na, @ruansheng8, @terry108, @aliray, @dasferco, @n1318914, @paopaolin, @randomzgm, @qgy123, @xiantao75, @we1h0, @sidgwick, @airkaikai, @alexyu1989, @Tian2000, @vyyq, @XingGX, @zamia, @Serena1993, @GrayLocus, @yansunbao, @MMHKP, @11lin, @wwwjf

authors: Ryan-the-hito kusamanetworkss parallaxlogicdevelopment riccoyu ryanwuson

repo: riccoyu/QLSubtitles


text:
优化日志输出多行消息的方法

优化日志输出多行消息的方法，使得收到的消息显示在一行中，便于日志记录
就改了一行还好意思提PR

__repr__ 输出来是字符串形式的消息吗，确定不是列表形式的？

__repr__ 输出来是字符串形式的消息吗，确定不是列表形式的？

不好意思刚刚脑袋抽风忘记加str()了

authors: mnixry richardchien

repo: richardchien/nonebot