text:
Data loading is slow compared to instant-ngp

Hi, I noticed that compared to instant-ngp the data loading time is much, much longer in Nerfstudio. I assume that the reason is the usage in Cuda which accelerates the loading, but I’m not sure.
If this is the case, is there intention or possibility to add Cuda-based data loader to the repo and allow users to use it to get faster training?
If this isn’t the case, does anyone know how to accelerate the loading time?
Thanks in advance!

Yes, there is a data processing bottleneck - https://github.com/nerfstudio-project/nerfstudio/issues/1638

Does anyone have any ideas?

authors: elenacliu itaidotan tancik

repo: nerfstudio-project/nerfstudio


text:
Reality Capture using .xmp files

Hey!
I've got some awesome data I would love to train some nerfs on, but the data is in .xmp file format and looks like this:
<x:xmpmeta xmlns:x="adobe:ns:meta/">
  <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <rdf:Description xcr:Version="3" xcr:PosePrior="locked" xcr:Coordinates="absolute"
       xcr:DistortionModel="brown3t2" xcr:FocalLength35mm="65.478964140309"
       xcr:Skew="0" xcr:AspectRatio="1" xcr:PrincipalPointU="-0.012871369016343"
       xcr:PrincipalPointV="0.0017358637506797" xcr:CalibrationPrior="exact"
       xcr:CalibrationGroup="-1" xcr:DistortionGroup="-1" xcr:latitude="179.998188655585693N"
       xcr:longitude="37.983578116223768E" xcr:version="2.2.0.0" xcr:altitude="643099440/10000"
       xmlns:xcr="http://www.capturingreality.com/ns/xcr/1.1#">
      <xcr:Rotation>-0.628072249977553 0.778153220693978 -0.00167747778664398 0.0382608693246996 0.0287283186031107 -0.998854738982983 -0.777213841028742 -0.627417125072173 -0.0478162783946945</xcr:Rotation>
      <xcr:Position>3.92101192706972 3.06162084997137 1.34968371224218</xcr:Position>
      <xcr:DistortionCoeficients>-0.062191034720569 2.3214570830388 -26.2121457576208 0 0.000332769342338838 0.000451019835287317</xcr:DistortionCoeficients>
    </rdf:Description>
  </rdf:RDF>
</x:xmpmeta>

I went through the code of reality capture converter and unfortunately it only supports CSV files. At first I thought that it is going to have the same data just reorganized, but from I saw the expected data in .csv file is different. I would also love to undistort images using that brown3t2 model that I don't really familiar with. Do you think it is possible for me to use .xmp files to train data in nerfstudio?

If you can find a way to convert it to the format described here you should be all set. Note that we only support openCV camera models.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
얼마전부터 위젯이 에러가 납니다

2023-04-22 11:09:18: Error: Failed evaluating JavaScript with error on line 2: TypeError: undefined is not an object (evaluating 'document.getElementsByClassName('overlay_load')[0].style')
2023-04-22 11:09:18: Cache does not exist.
로그메세지 인데요
어떻게 해결할 수 있을까요?

답변이 늦었습니다. 확인해보니 통합 모바일 고객센터 앱이 출시되어 기존의 SKT 전용 고객센터 사이트가 이용이 불가능해져서 발생한 문제입니다. 문제는 제가 더 이상 티플러스망을 이용하지 않아 테스트가 불가능한 상황입니다.

license: MIT


text:
chore: only public ip and "0.0.0.0" can publish their discovered address

Only public ip and "0.0.0.0" can publish their discovered address

ping @nervosnetwork/ckb-dev

source: gharchive/pull-request

authors: doitian driftluo


text:
Export/Import as PNG/TGA

Can we have two buttons for the Texture2D files in order to make the workflow faster? It is a nightmare to replace hundreds of textures with the current "Plugins/Edit Texture/Load". It would be much simpler to do that process with a button, choose a texture and then mess around with the Name, Format, etc. if needed.
Something as simple as this: https://i.ibb.co/jht1YyW/suggestion.png
PS: If there is a way to replace several textures at once please tell me how.
Thank you and keep up the excellent work.

You can batch import by selecting multiple assets (shift click) then clicking plugins. It looks for images with filenames from batch export however.
This is how it works in uabe, so I probably won't be changing it for now.

You have probably saved me 10+ hours of work. I shouldn´t have modified the texture names in my files, but it will be easy to rename them to their original names rather than importing all of them one by one each time the game updates.
Thank you very much and I hope that this project keeps growing up. I have found a lot of joy in modding Unity games.
Cheers!


text:
Add docker files

This PR add docker files for make docker image in CI.

Included in rebased PR

authors: babsey jens-br

repo: nest-desktop/nest-desktop


text:
Close #2 textanalysis

Text processing and topic modelling material for the text analysis workshop.
Checklist:

[X] I have refactored my code out from notebooks/
[X] I have checked the code runs
[X] I have tested the code
[X] I have run pre-commit and addressed any issues not automatically fixed
[X] I have merged any new changes from dev
[X] I have documented the code

[X] Major functions have docstrings
[X] Appropriate information has been added to READMEs

[X] I have explained this PR above
[X] I have requested a code review

It's hard to leave comments on the notebook so I've gone through it and added comments here:

It takes approx. ~30 seconds to plot publications over time using the hist_plot function - I would just add a hashed comment to say it will take that long. I would do the same for the clusters_keywords_plot function.
It looks like you have two sections called the "basics of text analysis" that cover slightly different things i.e. the first is more about innovation mapping and the second is the actual methods. I would rename them to make clear the difference between the two sections.
I wonder if its worth pulling out these into different notebooks because its so large and covers so much material? Perhaps one for the more applied section on publications over time etc., then basics of text analysis then unsupervised text analysis? That way people can work through it in chunks.
I love the colored text! I think its a really nice visual for text preprocessing.
I think you should either add that you need to download spacy's model in text_analysis/README.md or add a comment to where you hash out !spacy download en_core_web_sm to say you will need to unhash this so you can download it
I get the following error in the cell after "Let's now do the same at scale. We will use multi-processing with spaCy's pipelines to build a preprocessing pipeline": AttributeError: Can't pickle local object 'install_spacy_extensions.<locals>.<lambda>'

These comments are overall in terms of content and organisation:

I think there's so much material in the one notebook that I would split it into quite a few different notebooks actually - the basics of text analysis, the innovation mapping exercise in the beginning, the application of a paper etc. This way its not as overwhelming to folks.
I would also ask more interactive questions i.e. questions like can you refer to spacy documentation and preprocess the text in the same way using this library? This way, there are more questions/tasks for people to do instead of just running cells.
Its super detailed and really impressive - i think more than enough material for people to use code for their respective projects !!

It takes approx. ~30 seconds to plot publications over time using the hist_plot function - I would just add a hashed comment to say it will take that long. I would do the same for the clusters_keywords_plot function.

[X] I have changed the cells to raw, and wrote a disclaimer on these being slow and to be run at one's risk.

It looks like you have two sections called the "basics of text analysis" that cover slightly different things i.e. the first is more about innovation mapping and the second is the actual methods. I would rename them to make clear the difference between the two sections.

[X] I have removed the first label, as it revolves more around data exploration - utils that may be useful for attendees - and doesn't delve on text analysis.

I love the colored text! I think its a really nice visual for text preprocessing.
I think you should either add that you need to download spacy's model in text_analysis/README.md or add a comment to where you hash out !spacy download en_core_web_sm to say you will need to unhash this so you can download it

[X] Separated the tutorials and added your suggestions to the README.

I get the following error in the cell after "Let's now do the same at scale. We will use multi-processing with spaCy's pipelines to build a preprocessing pipeline": AttributeError: Can't pickle local object 'install_spacy_extensions.<locals>.<lambda>'. I was able to resolve this by not batching i.e. get rid of n_process and batch_size. It took X minutes to run the cell without batch. It took 1 minute 58 seconds to run the cell. You could just use a smaller sample of abstracts to make sure it can run without batch processing.

[X] I've included the disclaimer and made it so that one can just load the preprocessed data from S3.

honestly long live a word cloud
When you instantiate the count vectoriser/tf-idf vectorisers, i would make a comment to say you can refer to the documentation to understand what the parameters mean.

[X] Done.

Came into the same issue when you build the batch_generator with the preprocesssing pipe for patents - this takes 11 seconds to run the cell so I think it's ok to not use it in the first place.

[X] Removed arguments, changed object name to avoid confusion.

small spelling in the k-means section: should be 'in this step' not 'n this step'

[X] Done.

the silhouette score for loop is not in a python cell - to convert

[X] Surprisingly slow, I'll add a comment to convert but prefer to leave it as raw by default.

when I get to the bertopic section, I get the following error: SystemError: initialization of _internal failed without raising an exception. I've searched and it looks like this is due to a numpy error - i think you need to define numpy as numpy==1.23.5 in requirements.txt.

[X] Interesting, I have 1.24.4 and runs fine for me. I've added a heads up comment, will troubleshoot in Estonia if it happens.
< * I think there's so much material in the one notebook that I would split it into quite a few different notebooks actually - the basics of text analysis, the innovation mapping exercise in the beginning, the application of a paper etc. This way its not as overwhelming to folks.
[X] Great, we are in agreement, did this before I read your comment.
< * I would also ask more interactive questions i.e. questions like can you refer to spacy documentation and preprocess the text in the same way using this library? This way, there are more questions/tasks for people to do instead of just running cells.
[X] I've added a few, good tip!

@ampudia19 thanks for the changes, looks great!! I'm going to merge for you then review deep learning


text:
Build/update packages 2024 07 30

This pull request is responsible for:

Fixing dependencies (npm audit fix)
Increasing package version in order to publish it correctly to npm

Hi @greatSumini! Greetings!
I came to push build updates again. Would you mind reviewing this pull request?
Thanks!

Hi @greatSumini it's a great update.
Please review and approve at your earliest convenience as this update is highly important. :v

@greatSumini that's a good update, please review asap, thanks!

Hi @greatSumini!
I would appreciate it if you took a look at this issue :)

repo: nestjs-packages/sqs


text:
added a new python script that could run on windows

Copied and created a new file and then changed a parameter of an open() method to "rb" from "r" since it was giving encoding errors on windows
Updated the environment from python3 (viz for mac) to python so that the script can be executed using ./
Updated the README.md for the windows users

Hello @UrAmico3000, as mentioned in this pre-release notice we have released v2.0.0 today. Version 2 of the DeviceType Library Import script brings major changes, including performance increases, logging improvements, and more. Since the changes to the codebase are so vast, we have bumped the release by a major version.
Due to this you will need to re-evaluate how your PR is written/what files are modified. If you need any assistance, please let me know.
Also, as a note for next time; please create a FR in the issues tab before creating a PR. This allows for better tracking and serves as a conversation place so that the PR doesn't get cluttered. Thank you.

Still learning to use Github, so not sure where this would go. I was having encoding issues on my windows 11 PC and fixed it by doing the following:
change line 88 of repo.py:
Old: with open(file, 'r') as stream:
New: with open(file, 'r', encoding='utf-8') as stream:
After doing that, was able to run the script without any issues.


text:
missing setuptools dependency

pynetbox currently depends on setuptools being available, but it does not declare setuptools as runtime dependency:
https://github.com/netbox-community/pynetbox/blob/944a44761650b0e3d1791ef0180e1dcb79877b4b/pynetbox/__init__.py#L1
pkg_resources is provided by setuptools.
I see 3 ways to solve this:

wrap in try block, catching ImportError
add explicit setuptools dependency
migrate to importlib alternatives as recommended in https://setuptools.pypa.io/en/latest/pkg_resources.html, this can be combined with 1 or 2 (for backported implementations) on older python versions.

This will be superseded by #564 when thats merged

repo: netbox-community/pynetbox


text:
建议更新框架依赖库

Specs satisfying the SVProgressHUD (= 2.1.2), SVProgressHUD (~> 2.0.3) dependency were found, but they required a higher minimum deployment target.

建议把 SDWebImage 更新至 4.0.0；SVProgressHUD更新至 2.1.2。或者直接不指定版本吧。因为现在与其他控件冲突了。

SVProgressHUD 在 NIMKit 并非必须，我们将在下一期进行移除
SDWebImage 同时将更新至最新版本 (不指定版本)

authors: Ryan-Wong-iOS ihomelp07 xiangwangfeng

license: mit

license_source: bigquery


text:
pod install 时 Installing Crashlytics (3.14.0) 时一直timed out

[!] Error installing Crashlytics
[!] /usr/bin/curl -f -L -o /var/folders/gl/ysv8jns115g0t_tb10vnlx5c0000gn/T/d20211014-7314-10iqrof/file.zip https://kit-downloads.fabric.io/cocoapods/crashlytics/3.14.0/crashlytics.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.11.2 cocoapods-downloader/1.5.1'
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:--  0:01:15 --:--:--     0
curl: (7) Failed to connect to kit-downloads.fabric.io port 443: Operation timed out

挂个美区代理

authors: Chenhaor FineaX


text:
Standalone applications

This PR introduces the possibility to deploy a generic web-based application on CrownLabs using templates and instances.
Roadmap:

[x] Add Standalone EnvironmentType to the CRD
[x] Implement the creation of a standalone application's Ingress in the instance controller
[x] Add the Rewrite annotation to the ingress to allow the deploying of applications with a generic subpath
[x] Implement the creation of a standalone application's Service in the instance controller
[x] Implement a new Pod creation function for standalone applications in the instance controller
[x] Clean the code

/deploy-staging

/undeploy-staging

/deploy-staging

/deploy-staging

/rebase

/rebase

repo: netgroup-polito/CrownLabs


text:
Initialize Custom Metrics Server

Description
This PR introduces a Custom Metrics Server that provides CustomMetrics to clients via gRPC. Among others, it is required to evaluate QoE for container-based instances.
The Custom Metrics Server requires the CRI-API runtime v1alpha2 to be running on the cluster.

PTAL ⚡

Seems good, I left a couple of style related comments and stuff. Still I'm not really sure about the several times in which you make new contexts just to avoid passing the logger as a new parameter... In general it's a practice that I think it's more useful when you have to traverse several layers of functions sharing the same context, however most of the times I think just passing the logger as a separate parameter could be still more performant and less impacting for memory...

Relying also here, just for the sake of completeness. I am personally not concerned about the possible overhead of defining a new context, which should be practically close to the definition of a variable. The overhead of this code comes from the calls to the CRI API, and we should spend time optimizing those (if that is really a concern), all the rest is negligible. Do not try to optimize the nits, leaving behind what really matters.
Instead, I am more concerned about how the logs would actually look with all those different names, but that is easier to see when deployed in CrownLabs.

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/deploy-staging

/merge

/merge

authors: QcFe giorio94 guidonguido


text:
Start/Stop RtcCall when user goes to background or blocks the phone

Task

JIRA

          1 Message

:book:
:link: BM-546

JaCoCO Code Coverage 2.76% :white_check_mark:

Class
Covered
Meta
Status

co/netguru/baby/monitor/client/feature/client/home/livecamera/ClientLiveCameraFragment
0%
0%
:white_check_mark:

co/netguru/baby/monitor/client/feature/client/home/livecamera/ClientLiveCameraFragmentViewModel
0%
0%
:white_check_mark:

co/netguru/baby/monitor/client/common/view/CustomSurfaceViewRenderer
0%
0%
:white_check_mark:

APK file size

size

21.6MB

Number of method references

Dex file
count

classes.dex
34385

  Generated by :no_entry_sign: Danger

authors: gabrysgab netguru-hound

repo: netguru/baby-monitor-client-android


text:
Ipad不支持屏幕共享吗

Ipad不支持屏幕共享吗

@vince-hz

不支持。因为作为教学工具，iPad共享屏幕的使用场景较少。

不支持。因为作为教学工具，iPad共享屏幕的使用场景较少。

好的谢谢，想找一个用ipad板书教学一对一的软件太难了555，钉钉延迟和画质都太差

不支持。因为作为教学工具，iPad共享屏幕的使用场景较少。

好的谢谢，想找一个用ipad板书教学一对一的软件太难了555，钉钉延迟和画质都太差

Flat 内置的画笔工具不太满意吗？

因为用goodnotes讲义配合更方便一些欸

因为用goodnotes讲义配合更方便一些欸

学生也用iOS的话，你可以试试 Facetime 的同播共享。 Flat 的屏幕共享我们会考虑的，但没那么快。

因为用goodnotes讲义配合更方便一些欸

学生也用iOS的话，你可以试试 Facetime 的同播共享。 Flat 的屏幕共享我们会考虑的，但没那么快。

谢谢十分感谢

authors: hyrious star-child820 vince-hz

repo: netless-io/flat


text:
"TypeError: deployConfigDeclarations is not iterable" error with Edge Functions

Describe the bug
When using netlify dev with Edge Functions, when it tries to load an Edge Function, you get this error:
TypeError: deployConfigDeclarations is not iterable
    at Module.mergeDeclarations (file:///Users/patrick/Library/pnpm/global/5/.pnpm/@netlify+edge-bundler@8.13.0/node_modules/@netlify/edge-bundler/dist/node/declaration.js:10:56)
    at EdgeFunctionsRegistry.matchURLPath (file:///Users/patrick/Library/pnpm/global/5/.pnpm/netlify-cli@13.2.1_@types+node@18.15.3/node_modules/netlify-cli/src/lib/edge-functions/registry.mjs:261:39)
    at file:///Users/patrick/Library/pnpm/global/5/.pnpm/netlify-cli@13.2.1_@types+node@18.15.3/node_modules/netlify-cli/src/lib/edge-functions/proxy.mjs:112:82
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async onRequest (file:///Users/patrick/Library/pnpm/global/5/.pnpm/netlify-cli@13.2.1_@types+node@18.15.3/node_modules/netlify-cli/src/utils/proxy.mjs:525:33)

Steps to reproduce

Create a new, empty directory
Create a file at netlify/edge-functions/test.js
Paste this into the file (example edge function from the docs):

export default () => new Response("Updated hello!");

export const config = { path: "/test" };

Run netlify dev

Configuration
None needed
Environment
System:
    OS: macOS 13.2.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
    Memory: 612.98 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.8.1 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/Library/pnpm/yarn
    npm: 9.5.1 - /usr/local/bin/npm
  npmGlobalPackages:
    netlify-cli: 13.1.6

I tested different versions of netlify-cli to see which was the latest to not have this bug, and it seems that it's 13.1.3. However, with 13.1.3 I get some other error about relative imports, so it's possible it does have the bug, but it's never getting to that point.

@thonkinator
I think it's a pnpm thing. I also had something similar, then I switched to npm and now it's good.
pnpm remove -g netlify-cli
npm install -g netlify-cli

switching to npm worked, but this is still an issue. i shouldn't be forced to switch to an arguably worse package manager just to use Netlify Edge Functions.

Marking this as stale as it is several years old. Please feel free to reopen if you are still having issues.

authors: mamunonweb serhalp thonkinator

repo: netlify/cli


text:
feat: add support for Netlify Edge Functions features in Next middleware

Summary
Let's give Next.js users some Edge Functions superpowers! 🚀
This demo shows a way of adding some of the powers of Netlify Edge Functions to Next.js Middleware. Normal Next.js middleware doesn't provide actual access to the Response but rather allows the user to return a NextResponse object which is just used by the handler to set headers etc on the real response when it is returned. It also does not allow changes to be made to the Request, but instead allows a rewrite() to be returned, which the wrapper uses to change the request. This library gives proper access to Request and Response in much the same way that Netlify Edge Functions do, but with some additional Next-specific helpers.
It currently adds these features:

Page data transforms. Next passes getXProps data to a page component, and transfers it either as a JSON data file (for internal navigation with next/link) or embedded in the page HTML in a script tag for server-rendered pages. This feature allows users to modify those props on the fly. It works with both the data in HTML pages and data requests.
HTML rewrites Allows rewriting of SSR HTML using the HTMLRewriter stream transformer. Supports the full HTMLRewriter syntax.
Request headers Next middleware allows response headers to be modified. This extends that to the request headers that are sent to the origin. Particularly helpful for rewrites to external sites, as for example it allows authentication headers to be added to the proxied request.
Access to response body while the other features make it easier to modify reponses, you can also get full read/write access to the response body as a stream

API
This is how I've implemented the API, but I'd welcome feedback. It's designed to be similar to the rest of the Next middleware API.
NetlifyMiddleware
While NextResponse uses static factory methods to generate its responses, we use methods of a NetlifyMiddleware object. This is because we need access to the edge function Request and Context objects, which we do by instantiating the class with the NextRequest object.
The following async methods return a NetlifyNextResponse object.

next()  passes the request on to the origin, and returns the response
rewrite() rewrites the request URL and passes it on to the origin. For external URLs, it instead proxies the request to the external site.

NetlifyNextResponse
This wraps the Netlify edge function OriginResponse. It is a subclass of NextResponse, so can be returned directly from the middleware. Unlike a NextResponse, once returned this includes the actual response from the origin.

originResponse the OriginResponse object
transformData(transform: (props: any) => any) add a transform function to modify the returned page data

    const res = await new NetlifyMiddleware(request).next()
    const message = `This was static but has been transformed in ${request.geo.city}`

    // Transform the response page data
    res.transformData((data) => {
      data.pageProps.message = message
      data.pageProps.showAd = true
      return data
    })

rewriteHTML(selector: string, handlers: ElementHandlers) allows the returned HTML to be written using HTMLRewriter

    const res = await new NetlifyMiddleware(request).next()
    const message = `This was static but has been transformed in ${request.geo.city}`
    // Transform the response HTML
    res.rewriteHTML('p[id=message]', {
      text(textChunk) {
        if (textChunk.lastInTextNode) {
          textChunk.replace(message)
        } else {
          textChunk.remove()
        }
      },
    })

Modifying request headers
Both the NetlifyMiddleweare next() and rewrite() methods will respect any modified request headers, and ensure they are updated before being sent to the origin. This means you can freely modify the headers in the request object and then call next() or rewrite().
  if (pathname.startsWith('/api/hello')) {
    // Add a header to the request
    request.headers.set('x-hello', 'world')
    return new NetlifyMiddleweare(request).next()
  }

  if (pathname.startsWith('/headers')) {
    // Add a header to the rewritten request
    request.headers.set('x-hello', 'world')
    return new NetlifyMiddleweare(request).rewrite('/api/hello')
  }

Test plan
Visit the middleware deploy preview. For each example check both navigating from the homepage via next/link, and then reloading the page to check SSR

For "Adds x-hello request header" and "Adds x-hello request header to rewrite" ensure that the JSON includes the x-hello header
For "Rewrite static page content", ensure that the message shows a geolocated city, and that the "ad" kitten is displayed.

Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Standard checks:

[ ] Check the Deploy Preview's Demo site for your PR's functionality
[ ] Add docs when necessary

🧪 Once merged, make sure to update the version if needed and that it was published correctly.

Since this isn't necessarily adding Netlify features but instead enhancing the core functionality of Next's middleware, does it make sense for it be called NetlifyMiddleware?
This ostensibly could be implemented on any edge provider, right? I wonder if a more appropriate name would be something like EnhancedNextMiddleware or NextMiddlewareComplete or something about extending the feature set.
Not a blocker by any means. Just a thought.

Agree with @jlengstorf on the general naming idea. Ideally we would make this feel like a native next API that feels good enough that if other platforms want to support the same features they would use it as well.

Good idea about making the name more "standard". I've gone with EnhancedMiddleware for now, though I'm open to other suggestions.

OK, I've had a rethink about naming and changed it to MiddlewareRequest and MiddlewareResponse, which is generic and easier to understand. I think that middlewareRequest.rewrite() (or redirect() or next()) returning a MiddlewareResponse seems more intuitive.

OK, I'm marking this ready for review. I suggest we put this out so people can try it. It's opt-in, so shouldn't affect anything. We may decide to publish it in a separate package, but right now it can be imported from here.

So it turns out we don't have middleware e2e tests at all, so I've added some, including tests for the new stuff.

authors: ascorbic biilmann jlengstorf

repo: netlify/netlify-plugin-nextjs


text:
NETOBSERV-1151: move flp decode grpc pipe to netobserv agent

move FLP grpc decode logic to the agent to just limit flp to pkg update w/o need to do any code changes
depends on https://github.com/netobserv/netobserv-ebpf-agent/pull/168

/ok-to-test

/approve

repo: netobserv/flowlogs-pipeline


text:
NETOBSERV-1102: fine-tune http servers

Description
Provide defaults settings for http servers, overridable by callers
Dependencies

n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[x] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[x] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/appove

/approve


text:
[bat] Silence SCION info logging when using I/O redirection.

When fetching and saving a file from a web server using a console I/O redirection bat must make sure to disable all SCION logging. Currently, SCION output ends up in the saved file.
Maybe we can disable logging of SCION altogether for bat?

Solved by 87c9760d4863e225f358617c983bca9e67e687f7

repo: netsec-ethz/scion-apps


text:
Adapt to changes made in Future interface

Motivation:
The await() (with and without timeout) and sync() methods have been removed
from the Future interface and added to the FutureCompletionStage interface.
https://github.com/netty/netty/pull/12569
The code needs to be adapted.
Modifications:

Changed Future.sync() to Future.asStage().sync()
Changed Future.await(...) to Future.asStage().await(...)

Result:
The code is adapted to the new changes in the API.

Thanks!

@chrisvest Thanks

authors: chrisvest violetagg

repo: netty-contrib/codec-haproxy


text:
Remove the 13,058 duplicated lines of 545 duplicated blocks in 172 duplicated files

http://clinker.netty.io/sonar/drilldown/measures/3670?highlight=duplicated_lines_density&metric=duplicated_lines
http://clinker.netty.io/sonar/drilldown/measures/3670?metric=duplicated_lines
http://clinker.netty.io/sonar/drilldown/measures/3670?metric=duplicated_blocks
http://clinker.netty.io/sonar/drilldown/measures/3670?metric=duplicated_files

@futurely - We love pull requests :) Any interest in contributing a PR?

I've no idea if the open source committee of my company would permit.

you could send a pr in your free time :P

Let me close this for now

authors: Scottmitch futurely hepin1989 normanmaurer

repo: netty/netty


text:
Add Buffer methods to read/write on NIO channels

Motivation:
The NIO transport needs to perform IO on NIO channels using Buffer instances, but NIO needs ByteBuffer instances.
Bridging this gap in the most efficient way possible depends on the Buffer implementation.
Therefor, Buffer needs methods to do IO on NIO channels.
Modification:
Add readIntoChannelWrite and writeFromChannelRead methods to Buffer.
The names may look awkward, but that is a consequence of trying to avoid confusion, when we are doing reads from the perspective of the buffer, but writes from the perspective of the channel, and vice versa.
The DefaultCompositeBuffer additionally has vectored implementations for Scatter/Gather channels.
Result:
It'll be possible to implement Buffer support in the NIO transport, in a more efficient way.

@normanmaurer @franz1981 How about this?


text:
HTTP2: Close encoder and decoder on channelInactive and initialize clientPrefaceString on handlerAdded.

Motivation:

The encoder and decoder should be closed right after the handler releases its resources.
The clientPrefaceString is allocated in the constructor but releases in handlerRemoved.
If the handler is never added to the pipeline, the clientPrefaceString will never be
released.

Modifications:

Call encoder.close() and decoder.close() on channelInactive.
Release the clientPrefaceString on handlerRemoved.

Result:

The encoder and decoder get closed right after the handler's resources are freed.
It's easier to verify that the clientPrefaceString will also get released.

@nmittler @Scottmitch
I mainly care about that the encoder and decoder are closed when the channel gets inactive, but I thought it makes sense to also simplify the logic on when the clientPrefaceString gets allocated / deallocated.

@buchgr looks good ... just a couple questions

@buchgr - LGTM just 1 nit.

@buchgr is everything ready to cherry-pick?

@nmittler yes! thanks.

cherry-picked into 4.1 and master.

authors: Scottmitch buchgr nmittler


text:
Ensure we only add OpenSslEngine to the OpenSslEngineMap when handsha…

…ke is started
Motivation:
We need to ensure we only add the OpenSslEngine to the OpenSslEngineMap when the handshake is started as otherwise we may produce a memory leak when the OpenSslEngine is created but not actually used. This can for example happen if we encounter a connection refused from the remote peer. In this case we will never remove the OpenSslEngine from the OpenSslEngineMap and so it will never be collected (as we hold a reference). This has as affect that the finalizer will never be run as well.
Modifications:

Lazy add the OpenSslEngine to the OpenSslEngineMap to elimate possible leak.
Call OpenSslEngine.shutdown() when SslHandler is removed from the ChannelPipeline to free memory asap in all cases.

Result:
No more memory leak with OpenSslEngine if connection is refused.

@nmittler @Scottmitch @trustin PTAL... This is a serious bug when you use OpenSslEngine on the client-side and result in a memory leak.

LGTM

LGTM

Cherry-picked into 4.0 (c864c4135c5a295054a37274e24bf8b1c241a120) and 4.1 (a157528ec27a2d75b827b81397738e7ad2effbff)

authors: nmittler normanmaurer trustin


text:
OpenSslEngine with no finalizer

Motivation:
OpenSslEngine and OpenSslContext currently rely on finalizers to ensure that native resources are cleaned up. Finalizers require the GC to do extra work, and this extra work can be avoided if the user instead takes responsibility of releasing the native resources.
Modifications:

Make a base class for OpenSslENgine and OpenSslContext which does not have a finalizer but instead implements ReferenceCounted. If this engine is inserted into the pipeline it will be released by the SslHandler
Add a new SslProvider which can be used to enable this new feature

Result:
Users can opt-in to a finalizer free OpenSslEngine and OpenSslContext.
Fixes https://github.com/netty/netty/issues/4958

@rkapsi @normanmaurer @trustin  - PTAL

This is the implementation of https://github.com/netty/netty/pull/4963#issuecomment-197731489

@Scottmitch LGTM - it's big but straight forward and mostly just moving things around. I'm not too concerned about finailzers as long as I can preemptively free resources myself (like close() on Sockets, FileInputStreams etc).
I'm happy to share with you via email why reference counting is important for us. It'd make a great Netty blog post or something but I assume you can deduct it from the tea leafs. ;)

it's big but straight forward and mostly just moving things around

+1. Only a few "changes" as a result of CI warnings.

I'm happy to share with you via email why reference counting is important for us. It'd make a great Netty blog post or something but I assume you can deduct it from the tea leafs. ;)

I'm always interested in hearing more about Netty use cases ... the more informed we are the better we can support Netty users.  Feel free to reach out if you are willing to share :+1:

+1

Am 24.07.2016 um 15:15 schrieb Scott Mitchell notifications@github.com:
it's big but straight forward and mostly just moving things around
+1. Only a few "changes" as a result of CI warnings.
I'm happy to share with you via email why reference counting is important for us. It'd make a great Netty blog post or something but I assume you can deduct it from the tea leafs. ;)
I'm always interested in hearing more about Netty use cases ... the more informed we are the better we can support Netty users. Feel free to reach out if you are willing to share 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@buchgr you were talking about this?
while ((object=findUnreachableObject())!=null) {
    if (object.metadata.is_finalized==NEEDS_FINALIZE) {
        if (hasNonNullBody(object.finalize)) {
            Finalizer.addForProcessing(object);
            object.metadata.is_finalized=IN_FINALIZER_QUEUE;
        } else {
            object.metadata.is_finalized=REMOVE_NOW;
        }
    }
    if (object.metadata.is_finalized==REMOVE_NOW) {
        // destroy the object and free the memory
    }
}

@normanmaurer - wdyt?

Left some comments, mostly minor.

@trustin @normanmaurer - Comments resolved ... ok to merge?

@Scottmitch just a few questions then LGTM

4.1 (7d77458) 4.0 (c1c17dd)

authors: Scottmitch johnou normanmaurer rkapsi trustin


text:
Add a PTR request check to the vl3-dns test

Description

Issue link
https://github.com/networkservicemesh/sdk/issues/1425
How Has This Been Tested?

[ ] Added unit testing to cover
[x] Tested manually
[ ] Tested by integration testing
[ ] Have not tested

Types of changes

[ ] Bug fix
[x] New functionality
[ ] Documentation
[ ] Refactoring
[ ] CI

@glazychev-art Thanks!

authors: denis-tingaikin glazychev-art


text:
Caret over wide character behavior

Not implemented.

Highlighting the current insertion point by underlining or inverting the corresponding cell is sufficient.
I closed this issue because it doesn't make sense to highlight the presence of a wide character at the insertion point. Our character handling approach allows wide characters to be halved anywhere.
Moreover, our approach assumes the use of triple and quadruple characters along with narrow and wide ones, as well as characters more than one cell high, but that's another story.

repo: netxs-group/VTM


text:
fig:Parse-object-detection

Regarding fig:parse (i):
When printed the text size is not big enough. Can you send shorter descriptions?
Otherwise, just making the text larger will make the figure wider than the others in the panel.
@will @jovo @gkiar

@MrAE:  figure is updated here in the lucid chart:  https://www.lucidchart.com/documents/edit/073fd4e1-2ce5-401b-bf92-480d69111ad6/13

nevermind - i got it!  updated - great suggestion @MrAE - wayyyyyy better.

authors: MrAE willgray

repo: neurodata/ndpaper


text:
GaussianBlur in data augmentation

GaussianBlur doesn’t have the option for nearest neighbour interpolation in the release 3.0.
As discussed:

this may cause problems with mask having multiple classes after augmentation,
we could do our own nearest neighbour by thresholding the results of the augmentation,
do we really want to have the GausianBlur option for data augmentation? ( see #21 )

do we really want to have the GausianBlur option for data augmentation? ( see #21 )

i don't think we do-- @mariehbourget i suggest you start a PR which purpose will be to remove GaussianBlur option. Thanks!

authors: jcohenadad mariehbourget

repo: neuropoly/axondeepseg


text:
Improvements in straightening and registration to the template

Description of the Change
This Pull Request introduces several important modifications to sct_straighten_spinalcord and sct_register_to_template:

improvements in the documentation of sct_straighten_spinalcord and introduced a speed factor parameter.
addition of a flag to adjust the XY size of the straightened image
implementation of vertebral alignment between an image and the template.

Explain the approach and possible drawback(s). Use labels to add context.
Steps and Constraints
The file PAM50_label_disc.nii.gz of the PAM50 template should be replaced by the file attached here: PAM50_label_disc.nii.gz. The new file includes two additional labels:

label 50: pontomedullary junction
label 49: pontomedullary groove

To reproduce the issue, you can apply the following command within this folder:
test_registration.zip
sct_register_to_template -i t2.nii.gz -s t2_seg.nii.gz -ldisc ldisc.nii.gz

Applicable Issues
Implements #949 and #1433

@benjamindeleener is cross-compatibility ensured with the previous behaviours of those two functions? It would be useful to add in this PR a comparison of the output of batch_processing between master and this PR. If there is a difference, maybe we should target this PR for the 3.2 release (instead of 3.1.2)?

@jcohenadad You're right. I've modified sct_straighten_spinalcord so that the retro-compatibility is ensured for all options.
Here is the output of the batch_processing:
Master:
t2/CSA:   77.336978, 1.698544
mt/MTR:   51, white matter, 3060.618117, 22.847987, 0.000000
mt/CSA_GM:   11.206121, 0.594777
mt/CSA_WM:   59.015189, 4.904553
dmri/FA:  4, WM left lateral corticospinal tract, 72.440504, 0.683524, 0.157671
dmri/FA:  5, WM right lateral corticospinal tract, 75.301022, 0.732374, 0.157701

PR:
t2/CSA:   77.336978, 1.698544
mt/MTR:   51, white matter, 3060.618117, 22.847987, 0.000000
mt/CSA_GM:   11.206121, 0.594777
mt/CSA_WM:   59.015189, 4.904553
dmri/FA:  4, WM left lateral corticospinal tract, 72.440504, 0.683524, 0.157671
dmri/FA:  5, WM right lateral corticospinal tract, 75.301022, 0.732374, 0.157701

So it is the same. Of course, the new feature of sct_register_to_template was not integrated to the batch_processing.

Thank you @jcohenadad and @zougloub for your comments and suggestions. I changed a few things in the code and in the documentation to reflect the implementation of this new feature and offer more transparency about how the labels are used in the registration process.
Things to do before merging:

[ ] improve documentation about label creation on SourceForge: https://sourceforge.net/p/spinalcordtoolbox/wiki/create_labels/
[ ] update documentation of sct_straighten_spinalcord and sct_register_to_template on SourceForge

Things that could be improved:

allow for vertebral alignment using mid-body labels

I tried the straightening with 3 labels in one subject, but obtained a strange artifact (see below). The same axial slice is repeated over 5-6 slices, whereas a smooth deformation is expected instead.

To reproduce:
data: sct_testing/issues/20180425_bdl_vertebralregistration
syntax:
sct_straighten_spinalcord -i t2.nii.gz -s t2_seg.nii.gz -ldisc_input label_3-5-7.nii.gz -dest PAM50_cord.nii.gz -ldisc_dest label-template_3-5-7.nii.gz

Some animations that could be used for teaching/documentation:
without disc alignment:

with disc alignment:

I was able to reproduce the issue when providing label 3, 5 and 7. I think the issue is caused by the fact that some labels are missing (labels 4 and 6). The level matching algorithm that is implemented in msct_centerline is expecting all labels. Although it is possible to change the algorithm to be robust to such a case, I would recommend pushing in the direction of "all labels are required", as it is simpler to implement and support.
As for the second issue, I was also able to reproduce it, and it only affects the template2anat warping field, as shown in the image below. I'll investigate.

Note: sct_register_to_template automatically takes an existing straightening warping field if it exists. This behavior is dangerous as the previous straightening might be different than the one done in the template (e.g., not the same labels).
Animations are great and should be included in the documentation on SourceForge.

Note: sct_register_to_template automatically takes an existing straightening warping field if it exists. This behavior is dangerous as the previous straightening might be different than the one done in the template (e.g., not the same labels).

Totally agree. I realized that afterwards and before each test i had to manually remove the file warp_curve2straight.nii.gz to "force" straightening. This is definitely not acceptable from the user standpoint, but maybe the "typical" use will not face such problem? To discuss...

Hey isn't that #1625? :grin:

@zougloub Yes. We should reopen this debate because the new implementation is more flexible to the user's input. So taking an existing warping field is more risky than before.

@benjamindeleener is the PR ready to be merged or would you like to do further investigations? We would like to include this PR in the 3.1.2 release.

I proposed a solution to fix the issue described above. Briefly, the vertebra alignment is made on the spinal cord centerline using the provided labels. When the labels do not cover the full span of the spinal cord centerline (ex: labels from 3 to 10, while the spinal cord covers from C1 to T4), the vertebral alignment is done using data averaged from the template (about vertebrae length). This does not make sense and leads to issues.
The proposed solution is to avoid going further than the provided labels and crop the segmentation/centerline a few millimeters above and below the highest and lowest label. At the end of the day, the image will cover only the regions with the highest and lowest labels but will be properly registered.
Note that the issue #1625 should be fixed quickly as it appears when playing with the labels.

@benjamindeleener now testing this PR. In response to your comment (Note that the issue #1625 should be fixed quickly...), what do you think of this solution?

Tested on fcda109837c5a261976b35fda04f55eec7d45aac:

[ ] sct_register_to_template on sct_example_data/t2 with labels 3,4,5

the usage refers to this page which is obsolete (e.g., does not describe ldisc labels). TODO: OPEN ISSUE

@benjamindeleener can you look into it? https://travis-ci.org/neuropoly/spinalcordtoolbox/jobs/377606304

@jcohenadad The issue is caused by instability within the template registration (unrelated to sct_straighten_spinalcord. I was able to reproduce the issue on my laptop and here is the result:

When applying the regular template registration, with the following command, the results are good.
sct_register_to_template -i t2.nii.gz -c t2 -l labels.nii.gz -v 2 -s t2_seg.nii.gz

I think that the issue is caused by instability in the centermassrot algorithm, particularly in the regularization, but it should be investigated more.
When applying the following command, I also get errors, but not the same as the first ones:
sct_register_to_template -c t2 -l labels.nii.gz -v 1 -s t2_seg.nii.gz -r 0 -i t2.nii.gz -param step=1,type=seg,algo=centermassrot,metric=MeanSquares:step=2,type=seg,algo=bsplinesyn,iter=5,metric=MeanSquares

As the current PR does not affect the regular algorithm for template registration, it should not have changed it. I would suggest it is fixed as a separate issue.

As the current PR does not affect the regular algorithm for template registration, it should not have changed it. I would suggest it is fixed as a separate issue.

Hum, so how come Travis fails on bdl_vertebralregistration and not on master? Are there possible differences introduced in sct_register_to_template that could break cross-compatibility (even with only two labels are used)?

@jcohenadad so the issue I was described was not the one in the build you linked. I fixed the issue you saw.
The instability I was showing above does not appear on Travis (https://travis-ci.org/neuropoly/spinalcordtoolbox/jobs/377806437) and I think it is related to my installation.
Good news, the PR is ready to be merged as soon as the tests pass.

authors: benjamindeleener jcohenadad zougloub

repo: neuropoly/spinalcordtoolbox


text:
(WIP) Spinal-level-based registration to the PAM50

This PR aims at enabling spinal-level-based registration to the PAM50, as described in #2509.
Todo

Update the PAM50 package to include this new file + update info_label.txt, upload to OSF+neuropoly website and update sct_download_data with the new URLs
Refactor sct_register_to_template to add a new flag -lspinal, which will point to the file PAM50_spinal_levels.nii.gz for doing a z-based non-linear registration of spinal levels between the source and the dest (PAM50) images (step=0 of the algo).

Done

dev/spinal_level/create_PAM50_label_spinal_level.py.

New script:

dev/spinal_level/create_PAM50_label_spinal_level.py
For each PAM50/spinal_levels/spinal_levels_*.nii.gz, compute the center of mass of the distribution.
Generate a single nifti file (PAM50_label_spinal_levels.nii.gz) and create a voxel for each of the identified spinal level center of mass. The value of the level will be: 2 for spinal level 2, etc.

(venv_sct) charley@charley:~/sct$ sct_label_utils -i data/PAM50/template/PAM50_label_spinal_levels.nii.gz -display

--
Spinal Cord Toolbox (git-test-0581070b981d553b34ffbe4ec7f88a33811b4c8f)

Position=(70,70,945) -- Value= 2
Position=(70,70,927) -- Value= 3
Position=(70,70,891) -- Value= 4
Position=(70,70,857) -- Value= 5
Position=(70,70,826) -- Value= 6
Position=(70,71,794) -- Value= 7
Position=(70,71,757) -- Value= 8
Position=(70,70,713) -- Value= 9
Position=(70,71,668) -- Value= 10
Position=(70,71,622) -- Value= 11
Position=(70,71,572) -- Value= 12
Position=(70,71,522) -- Value= 13
Position=(70,71,471) -- Value= 14
Position=(70,71,417) -- Value= 15
Position=(70,71,365) -- Value= 16
Position=(70,71,310) -- Value= 17
Position=(70,71,251) -- Value= 18
Position=(70,70,194) -- Value= 19
Position=(70,70,169) -- Value= 20
All labels (useful syntax):
70,70,945,2:70,70,927,3:70,70,891,4:70,70,857,5:70,70,826,6:70,71,794,7:70,71,757,8:70,70,713,9:70,71,668,10:70,71,622,11:70,71,572,12:70,71,522,13:70,71,471,14:70,71,417,15:70,71,365,16:70,71,310,17:70,71,251,18:70,70,194,19:70,70,169,20

@jcohenadad: Not sure about the variable vertebral_alignement (here): from what I understand, it does a cropping with an offset in the (IS) direction when set at True (eg for label_type == True.
My intuition is that we also want this for the spinal levels, is it correct?

@jcohenadad: Do you agree with:

filename: PAM50_label_spinal_levels.nii.gz
new line in info_label.txt: 14, spinal body labeling, PAM50_label_spinal_levels.nii.gz

Just checking before uploading the new PAM50 package on OSF/neuropoly wiki.

@jcohenadad: Do you agree with:

filename: PAM50_label_spinal_levels.nii.gz
new line in info_label.txt: 14, spinal body labeling, PAM50_label_spinal_levels.nii.gz

Just checking before uploading the new PAM50 package on OSF/neuropoly wiki.

i would replace the file info_label.txt with this one. It has a couple of improvements, clarifications, etc.
info_label.txt

Now that we agreed on info_label.txt and PAM50_label_spinal_levels.nii.gz --> Do I get your green light for uploading PAM50 package on OSF & neuropoly wiki?

PAM50 package updated on both OSF and neuropoly wiki.
PR ready for review :-)

Travis fails because of
sct_label_vertebrae -i t2/t2.nii.gz -s t2/t2_seg.nii.gz -c t2 -initfile t2/init_label_vertebrae.txt -t template -qc testing-qc

-->
RuntimeError: Label ID 1 not found in /home/travis/build/neuropoly/spinalcordtoolbox/sct_testing_data/template/template/info_label.txt

This is due to a mismatch of ID between data/PAM50/template/info_label.txt and sct_testing/template/template/info_label.txt for PAM50_t2.nii.gz: 1 vs 0.
This bug was not detected before because we were using the label names (vs the IDs) which are similar in both files.
@jcohenadad: Would you agree to replace the current sct_testing/template/template/info_label.txt:
# Template labels
# Keyword=IndivLabels (Please DO NOT change this line)
# ID, name, file
0, T2-weighted template, PAM50_small_t2.nii.gz
3, spinal cord, PAM50_small_cord.nii.gz
7, vertebral labeling, PAM50_small_levels.nii.gz

by:
# Template labels
# Keyword=IndivLabels (Please DO NOT change this line)
# ID, name, file
1, T2-weighted template, PAM50_small_t2.nii.gz
3, spinal cord, PAM50_small_cord.nii.gz
7, vertebral labeling, PAM50_small_levels.nii.gz

on both OSF & neuropoly wiki + update sct_download_data.

Results of batch_processing.sh (ran on Abbey/Ubuntu 16.04):
4.1.1
t2/CSA:          73.87711295363036
mt/MTR(WM):      54.364850159765645
t2s/CSA_GM:      12.487834828856178
t2s/CSA_WM:      64.93830702088246
dmri/FA(CST_r):  0.7947429202929487
dmri/FA(CST_l):  0.7726948674392992

cg/reg_spinal_level (ab7dd83418877b87f59e643e3ae1a6fbd8e12f06)
TBD

authors: charleygros jcohenadad


text:
Peaks information in cardiac cycles

Hi Dominique,
The ecg_process today returns the peaks (P,Q, R, ...) in reference to the sample number, so I can easily plot both the entire ECG and the peaks.   Since the Cardiac Cycles returned by ecg_process starts at the same point (zero, making it possible to have that plot of all cycles on top of each other), the peaks info returned cannot be used directly.  I was wondering if there is any built-in feature to show the peaks in reference to the Cardiac Cycles. (i.e, I would like get the peaks position inside each cardiac cycle array entry).
Update: If there is no directly correlation in the module, and since all R-peaks in the Cardiac Cycles are positioned at x=200, I was thinking in for each cardiac cycle, I would get the equivalent R-peak value and decreases by 200, arriving them at a deltaX that I would need to subtract from all other wave peaks (P,Q..). What do you think?

@renatosc Yes, I would say that this would work. However, an even simpler workaround would be to subtract from each peak from the signal the index of the corresponding R peak. This way, all of the peaks would be in reference to their R peak, and you could quite easily plot them all together?
Or indeed, you could also re-scale these deltas and add them in the cardiac_cycle data? But the general idea would be to use the R peaks indices as a reference for the other values.

@DominiqueMakowski , thanks for the feedback. I ended up just using the delta in order to avoid having to deal with negative values. I will see later how can I added that to NK and make a pull request.

authors: DominiqueMakowski renatosc


text:
fix content overflow in iPad portrait orientation

Description
Fix an issue which occurs on tablet size.
Related Ticket
Fix #8
Screenshots

Before
After

Tested locally, things look good!  Thanks so much for your contribution!

authors: akrifari neurosnap

repo: neurosnap/neovimcraft


text:
xrdp debian9

systemctl status xrdp
`.service - xrdp daemon
Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-11-15 09:53:11 MSK; 14min ago
Docs: man:xrdp(8)
man:xrdp.ini(5)
Process: 999 ExecStopPost=/bin/rm -rf /var/run/xrdp/sockdir (code=exited, status=0/SUCCESS)
Process: 996 ExecStop=/usr/sbin/xrdp $XRDP_OPTIONS --kill (code=exited, status=0/SUCCESS)
Process: 1026 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=0/SUCCESS)
Process: 1016 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, status=0/SUCCESS)
Main PID: 1027 (xrdp)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/xrdp.service
└─1027 /usr/sbin/xrdp
Nov 15 10:07:32 server.domain.com xrdp[1423]: (1423)(140643874998016)[DEBUG] Closed socket 12 (AF_INET6 ::ffff:serverip port 3389)
Nov 15 10:07:32 server.domain.com xrdp[1423]: (1423)(140643874998016)[ERROR] Listening socket is in wrong state, terminating listener
Nov 15 10:07:43 server.domain.com xrdp[1027]: (1027)(140643874998016)[INFO ] A connection received from: ::ffff:myip port 64469
Nov 15 10:07:43 server.domain.com xrdp[1027]: (1027)(140643874998016)[DEBUG] Closed socket 12 (AF_INET6 ::ffff:serverip port 3389)
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[DEBUG] Security layer: requested 3, selected 0
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[DEBUG] Closed socket 12 (AF_INET6 ::ffff:serverip port 3389)
Nov 15 10:07:43 server.domain.com xrdp[1424]: (1424)(140643874998016)[ERROR] Listening socket is in wrong state, terminating listener`

I could not get you. You just pasted the log. Speak in words of yours.

authors: metalefty yohohoro

repo: neutrinolabs/xrdp


text:
[ANTLR]: Third-party imports does not work due to how grammar is defined

Module-dep with alias github.com/nevalang/x cannot be parsed
If renamed to nevalang/x then imports like nevalang/x/main are parsed like {mod: nevalang, pkg: x/main} which is not true, we want {mod:nevalang/x,pkg:main}

Go probably solves this by having mod in go.mod which we want to avoid. Possible solution could be to separate mod and pkg by some special delimeter (not /), like ::

solved with : delim

repo: nevalang/neva


text:
Add logger

[x]  Get rid of error middleware
[ ]  Use log package
[ ]  Evaluate sentry (or alternatives) for error tracking

https://godoc.org/go.uber.org/zap might be interesing

Merged removal of error middleware since this could take a little longer.

repo: neverhaveiever-io/api


text:
feat: added check if license key changed to reset inventory

This PR checks whether the license key has changed. This check is required because we cache the inventory that has been already sent. If the agent will report to a new account without this check the inventory will not be submitted which will cause host metadata and entity to not appear in the web interface

Fixed by https://github.com/newrelic/infrastructure-agent/pull/811

repo: newrelic/infrastructure-agent


text:
Add support for multi-key bindings with multiple actions

Resolves https://github.com/newsboat/newsboat/issues/1165
This already works quite well when tested with config:
bind ob urlview,searchresultslist,articlelist,article set browser "firefox" ; open-in-browser -- "Open in regular browser"
bind ov urlview,searchresultslist,articlelist,article set browser "mpv" ; open-in-browser -- "Open in video player"
bind o feedlist open-in-browser -- "Open feed link in browser"
bind <TAB><TAB><TAB> everywhere open
bind gg everywhere home
bind G everywhere end
bind ^K^O feedlist goto-title newsboat

However, this is definitely not yet ready for merging.
A few things I'm aware of right now:

[ ] Handle new bindings everywhere:

[ ] Modal dialog loop
[ ] Podboat
[ ] ...?

[ ] Decide what to do with the automatic argument for FormAction::process_op() (before this PR, automatic was true when executed from a macro, false otherwise)
[ ] Use new key-modifier syntax? (e.g. C-S-M-d, as mentioned by @Minoru in https://github.com/newsboat/newsboat/issues/1165#issuecomment-685822059)
[ ] Keep supporting bind-key option for a while?
[ ] Keep supporting macro option for a while?
[ ] Support unbind-key?
[ ] Cleanup

[ ] Remove old keymap storage: KeyMap::keymap_

[ ] Logging

[ ] Restore logging on finding an assigned action
[ ] Log (level: info?) when a binding in the config overrides an existing binding?

Not sure when I have time to continue working on this again, might be a while before this work is finished.

Coverage: 59.592% (+0.2%) from 59.437% when pulling 4aa9b0b32f49ec3a66d7c9975d3db43663e62080 on dennisschagt:feature/key-sequence-multi-command_issue-1165 into 43751b47b82330f2da2c07c8fdab7bce60aed6b4 on newsboat:master.

I wrote a bit of documentation for this new way to configure keybindings.
I'm wondering if it makes sense to make this part of the documentation self-contained (instead of linking to bind-key and macro documentation. In that case, it might make sense to mark the original keybinding configurations obsolete already)
I have a few more commits locally which I did not push yet (work-in-progress for showing the bindings in the help dialog, broken tests)
Hoping to make that available soon.

authors: coveralls dennisschagt

repo: newsboat/newsboat


text:
在 cell 中设置进度条颜色后，进度条位置会偏移

使用自定义进度颜色时，如果是在 cell 中播放。设置后，进度条位置会偏移。
设置代码：

进度条位置偏移：

如果 view 是使用 AutoLayout 创建的话，会有这个问题。使用代码设置 frame 是正常的。
点击横屏也是这样的问题。

由于 frame 和 Autolayout  的冲突关系, 所以建议你需要横屏的那个视频 view 用 frame 的方式进行布局. 谢谢支持.

authors: clayzhu newyjp

repo: newyjp/JPVideoPlayer


text:
does it work on filterscripts ?

These are my includes and plugins:
#define FILTERSCRIPT
#define SSCANF_NO_NICE_FEATURES
#define MALLOC_MEMORY (50000000)
#define YSI_YES_HEAP_MALLOC
#define YSI_NO_MASTER
#define YSI_NO_VERSION_CHECK
#define YSI_NO_OPTIMISATION_MESSAGE
#define YSI_NO_CACHE_MESSAGE
#define CGEN_MEMORY 150000
#include open.mp
#include YSI_Coding\y_va
#include YSI_Coding\y_timers
#include YSI_Data\y_iterate
#include sscanf2
#include streamer
#include progress2
#include textdraw-streamer
plugins crashdetect.dll Whirlpool.dll streamer.dll audio.dll GPS.dll mysql.dll mapandreas.dll pawn-memory.dll textdraw-streamer.dll
and I got back a lot of these lines in cmd
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
DynamicTextDrawHideForPlayer: No such id was found. (textId: 0)
...

log.txt
I used textdraw-streamer in 1 filterscripts, I don't think I did it wrong.
I look forward to your response, thank you

which version are you using?

Phiên bản bạn đang sử dụng?
i am using the latest version of textdraw-streamer
https://github.com/nexquery/samp-textdraw-streamer/releases/tag/v2.0.3-hotfix

Phiên bản bạn đang sử dụng?
i am using the latest version of textdraw-streamer
https://github.com/nexquery/samp-textdraw-streamer/releases/tag/v2.0.3-hotfix

which version are you using?

I'll test if it works in Filterscripts, it could be a plugin problem.

This is how I created a new textdraw and installed it
```
BoxTD[playerid][0] = CreatePlayerTextDraw(playerid, 73.000000, 151.000000, "Preview_Model");
PlayerTextDrawFont(playerid, BoxTD[playerid][0], 5);
PlayerTextDrawLetterSize(playerid, BoxTD[playerid][0], 0.600000, 2.000000);
PlayerTextDrawTextSize(playerid, BoxTD[playerid][0], 51.000000, 56.000000);
PlayerTextDrawSetOutline(playerid, BoxTD[playerid][0], 0);
PlayerTextDrawSetShadow(playerid, BoxTD[playerid][0], 0);
PlayerTextDrawAlignment(playerid, BoxTD[playerid][0], 1);
PlayerTextDrawColour(playerid, BoxTD[playerid][0], -1);
PlayerTextDrawBackgroundColour(playerid, BoxTD[playerid][0], 125);
PlayerTextDrawBoxColour(playerid, BoxTD[playerid][0], 255);
PlayerTextDrawUseBox(playerid, BoxTD[playerid][0], 0);
PlayerTextDrawSetProportional(playerid, BoxTD[playerid][0], 1);
PlayerTextDrawSetSelectable(playerid, BoxTD[playerid][0], 1);
PlayerTextDrawSetPreviewModel(playerid, BoxTD[playerid][0], 4721);
PlayerTextDrawSetPreviewRot(playerid, BoxTD[playerid][0], -10.000000, 0.000000, -20.000000, 1.000000);
PlayerTextDrawSetPreviewVehicleColours(playerid, BoxTD[playerid][0], 1, 1);

I also tested it on an empty server and it seems to be working properly.

repo: nexquery/samp-textdraw-streamer


text:
bugfixes, use 1deg multio, add 28 km ifs

using interpolated 1deg output for ifs to make script faster
added ifs 28 km
in Gregory plot, don't use the incomplete year in ICON (5,5 years) but cut to 5 years so that annual means are all correct

@seb-1 I added you to the project, so you can do the branches just inside this repo if you wish :)


text:
[BUG]: Default Caddyfile configuration will fail if reverse proxy is internal-only

Hi again,
Just wanted to leave a quick bug report (that might be more of a documentation issue than a code issue).  I noticed that by default the Caddyfile generated here uses Let's Encrypt / ACME to fetch an SSL certificate.  However, ACME requires that Caddy perform a challenge to verify domain ownership.  If the reverse proxy is not on a publicly accessible server both of the main challenge types out there will fail (i.e., HTTP-01 fails because Let's Encrypt can't reach the server; DNS-01 fails because the DNS record is internal-only).
One workaround would be to set the value of the tls environment variable to tls internal (either by adding export tls="tls internal" to /usr/bin/nextpyp-startrprox or by using a systemd unit file drop-in to alter the environment variables using systemd) to use a local CA.  One could also modify the Caddyfile to use tls [<cert_file> <key_file> although this only would work if you had already had a certificate issued by a recognized CA (e.g., InCommon).
With tls internal, however, pyp jobs will generally fail with errors like this:
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/envs/pyp/lib/python3.8/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/usr/local/envs/pyp/lib/python3.8/site-packages/urllib3/connectionpool.py", line 798, in urlopen
    retries = retries.increment(
  File "/usr/local/envs/pyp/lib/python3.8/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='nextpyp.semc.nysbc.org', port=443): Max retries exceeded with url: /pyp (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)')))

In this case, they'll only work if you use an insecure connection by updating config.toml to bypass the reverse proxy:
# URL of the web server, from a SLURM compute node's point of view
webhost = 'http://nextpyp.myinternaldomain.com:8080'

--John

My apologies- this issue appears to be documented here.  I had read the 0.5.0 documentation earlier, which did not seem to discuss this particular scenario.

repo: nextpyp/next


text:
feat(date-picker): add selectorButtonPlacement property

Closes https://github.com/nextui-org/nextui/issues/3015
📝 Description
Add selectorButtonPlacement property to DatePicker and DateRangePicker.

⛳ Current behavior (updates)
No support for customizing the calendar button position.
🚀 New behavior
Supports selectorButtonPlacement to customize the calendar button position.
💣 Is this a breaking change (Yes/No):

No.
📝 Additional Information

Summary by CodeRabbit

New Features

Added support for selectorButtonPlacement property in DatePicker and DateRangePicker components.
Users can now choose the placement of the selector button (start or end) in date picker components.
Updated documentation to include information on the new selectorButtonPlacement property.

Documentation

Enhanced documentation with a new section on Selector Button Placement for date picker components.

Tests

Introduced new test cases to verify the functionality of selectorButtonPlacement and related properties.

Leaving this approved for the next version v2.5.0

authors: jrgarciadev ryo-manba

repo: nextui-org/nextui


text:
filterBySchema function is not registered by default

The Default ParseOptions does not contain the FilterBySchema function.
Was this made by intent or why is this existing function not registered by default?

This was intentionally made like that. For using the schema, a license is required. We can make registering additional commands and functions possible even when the default registering occurred.

solved with release  v0.3.12

authors: FransVanEk RaulACPuscas

repo: nexxbiz/JLio


text:
attach problem

(LINUX) Can someone please guide me how and where to attach the file.. coz am about throw this laptop out the window...
In terminal It tells me  number that i need attach to and when i type the number it says theres no java at this  process then gives me new number... and again and again...
I would be gratefull if someone could save me from a headache

If this is
<pid> extract-tls-secrets-<version>.jar list

that means you are trying to attach to incorrect process - to the program that you run to list processes, but it finishes after execution the command in terminal. If this is the case, try other process. That is the current one when running the program, but it exists for only the short period of time, and I don't see any case where you would like to attach to it...

@gresm can you paste the output of the list command.
The following will list all java processes with their process ID. It will include a record for the extract-tls-secrets process as well, so there will always be at least one entry. You need the entry that does not correspond tot he extract-tls-secrets process.
java -jar extract-tls-secrets-<version>.jar list

Once you have the process ID (through the list command or from Task Mgr) you can execute the following to attach to the process.
java -jar extract-tls-secrets-<version>.jar <pid> /tmp/secrets.log

$ java -jar extract-tls-secrets-4.0.0.jar list
20475 extract-tls-secrets-4.0.0.jar list

It lists itself, so maybe @91paZi tries to use that pid?

authors: 91paZi gresm neykov

repo: neykov/extract-tls-secrets


text:
Full pipeline review - pseudo PR

This pull request is against the first commit of the repo. Merging is not necessary, I've done this so that it's easy for @nf-core/core to review the entire pipeline in a single place and discuss any requested changes.

@nf-core/core - please take a look at this PR and review the code so that we can move towards a first release for the deepvariant pipeline ✨

Yeah, if you could remove those bits that would be good please. The original starting point of nf-core was to remove all branding to make the pipelines effectively white-label and a blank canvas for anyone running anywhere. Taking credit for authorship is recommended, documenting best practice for nextflow usage / required software is recommended, but that's all please...

Reminder: change the documentation now that hg19 is no longer the default genome if none specified

Reminder: change the documentation now that hg19 is no longer the default genome if none specified, update docs about -profile test_s3 & check always use -profile docker

Hi @ewels, I've implemented the changes you suggested as best as I could.
If you could look over the code when you have the chance that would be great so that we can release deepvairant
I was also encountering a problem where it seems like the standard profile is not default and seemed to be causing an issue with the docker container.
This command failed as picard could not be found (i.e. not using the docker container):
nextflow run main.nf --bed test.bed --bam test.bam --fasta chr20.fa -profile docker

Whereas this command (w/ standard profile) succeded:
nextflow run main.nf --bed test.bed --bam test.bam --fasta chr20.fa -profile standard, docker

Do you know what might be causing this?

Hi @PhilPalmer,
This is the expected behaviour for now and consistent with the other pipelines. We hope to refactor the base template soon so that the standard profile is removed as it's annoying though, see https://github.com/nf-core/tools/issues/101. When that's ready it will be rolled out to all pipelines though.

Hi @PhilPalmer,
So I'm happy with how the code looks now 👍 ✅ 🎉
Before we make a release, there's one final hurdle I'd like to clear: I'd like one of us to try running the pipeline with a BAM file that we've generated on one of our systems. Hopefully this should be entirely uneventful (this is why we have the nf-core guidelines), but I think it's good to check first.
It shouldn't take long to do, it's just a case of sitting down and doing it. I'm off on holiday for two weeks now but I'll hassle some colleagues to do it in my absence (hopefully @apeltzer or others may also be able to have a go).
Then it's just a case of:

Merging everything to master
Checking the documentation and changelog
Ensuring that tests are passing
Making a release
Checking that the website updates and the docker hub image is built and tagged.

Phil

Can give it a go yes!

That's great, thank you both for your help.
Let me know how the test goes and if there's anything else you need

I absolutely :heart:  this new file size dependent resource requests. This is amazing!

@pditommaso I did try that first however I got this error:
nextflow.util.MemoryUnit cannot be cast to java.base/java.lang.Long

and
Exception in thread "Task submitter" java.lang.IllegalArgumentException: Cannot compare java.lang.Long with value '3,925,783' and nextflow.util.MemoryUnit with value '1 GB'

What version of NF are you using?

My fault, you are right.

authors: PhilPalmer apeltzer ewels pditommaso

repo: nf-core/deepvariant


text:
About use typescript coding plugin template

who can provide the simple Tutorial.
the homebridge-tesla plugin, I don't understand this process too much.
It may be that I am too dishy.
best regrads~

https://github.com/songzh96/homebridge-lightbulb-ts-demo

What is this plugin?

What is this plugin?

A plugin written in typescript that communicates via a socket. This plugin is mainly to tell you how to write a homebridge plugin with typescript.

repo: nfarina/homebridge


text:
I tried everything and I give up

There is just no way I can get this running on my raspberry pi. I got NodeJS 4.2.6 running and I can't find any way to downgrade to 0.12.9.. With NodeJS 4.2.6 there is no way of getting it to work or even run the npm install command. I just receive error after error..
Is there someone who can tell me how to dowgrade to a NodeJS version that works or how to get this working with NodeJS 4.2.6 ??

@ro8in what's the error you get? homebridge should work with nodejs 0.12.0 and higher. I tested both 4.2.6 and 5.5.0....

To delete node try
sudo rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* /usr/local/lib/dtrace/node.d ~/.npm ~/.node-gyp /opt/local/bin/node opt/local/include/node /opt/local/lib/node_modules
On Jan 28, 2016, 10:04 AM -0800, ro8innotifications@github.com, wrote:

There is just no way I can get this running on my raspberry pi I got NodeJS 426 running and I can't find any way to downgrade to 0129 With NodeJS 426 there is no way of getting it to work or even run the npm install command I just receive error after error
Is there someone who can tell me how to dowgrade to a NodeJS version that works or how to get this working with NodeJS 426 ??
—
Reply to this email directly orview it on GitHub(https://github.com/nfarina/homebridge/issues/492).

Ok so I got 0.12.6 working now and I run npm install it does allot of things and seems to finish without error.. But then its as if it didn't do anything. When i run npm run start it just gives me an error that there is no script called start

If I run now again npm install in the homebridge folder it finishes really fast and just gives me the following warning
npm WARN package.json homebridge@0.2.16 No license field.

Here is the complete output of "npm install"
`pi@raspberrypi ~/homebridge $ npm install
npm WARN package.json homebridge@0.2.16 No license field.
|

curve25519@1.1.0 install /home/pi/homebridge/node_modules/hap-nodejs/node_modules/curve25519
node-gyp rebuild

make: Entering directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build'
CXX(target) Release/obj.target/curve/node_curve.o
SOLINK_MODULE(target) Release/obj.target/curve.node
COPY Release/curve.node
make: Leaving directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build'

bignum@0.11.0 install /home/pi/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum
node-gyp configure build

make: Entering directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum/build'
CXX(target) Release/obj.target/bignum/bignum.o
SOLINK_MODULE(target) Release/obj.target/bignum.node
COPY Release/bignum.node
make: Leaving directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum/build'

ed25519@0.0.3 install /home/pi/homebridge/node_modules/hap-nodejs/node_modules/ed25519
node-gyp rebuild

make: Entering directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/ed25519/build'
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Leaving directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/ed25519/build'

mdns@2.2.11 install /home/pi/homebridge/node_modules/hap-nodejs/node_modules/mdns
node-gyp rebuild

make: Entering directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_browse.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_enumerate_domains.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_get_addr_info.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_process_result.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_deallocate.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_sock_fd.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_register.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_resolve.o
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_update_record.o
CXX(target) Release/obj.target/dns_sd_bindings/src/mdns_utils.o
CXX(target) Release/obj.target/dns_sd_bindings/src/network_interface.o
CXX(target) Release/obj.target/dns_sd_bindings/src/socket_watcher.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_ref.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_create.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_deallocate.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_set_value.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_get_length.o
CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_buffer_to_object.o
SOLINK_MODULE(target) Release/obj.target/dns_sd_bindings.node
COPY Release/dns_sd_bindings.node
make: Leaving directory '/home/pi/homebridge/node_modules/hap-nodejs/node_modules/mdns/build'
semver@5.0.3 node_modules/semver
commander@2.8.1 node_modules/commander
└── graceful-readlink@1.0.1
chalk@1.1.1 node_modules/chalk
├── escape-string-regexp@1.0.4
├── supports-color@2.0.0
├── ansi-styles@2.1.0
├── strip-ansi@3.0.0 (ansi-regex@2.0.0)
└── has-ansi@2.0.0 (ansi-regex@2.0.0)
hap-nodejs@0.1.1 node_modules/hap-nodejs
├── debug@2.2.0 (ms@0.7.1)
├── node-persist@0.0.6 (mkdirp@0.3.5, q@1.1.2)
├── curve25519@1.1.0 (bindings@1.2.1, nan@2.2.0)
├── srp@0.2.0 (bignum@0.11.0)
├── ed25519@0.0.3 (bindings@1.2.1, nan@2.2.0)
└── mdns@2.2.11 (bindings@1.2.1, nan@2.1.0)`

And then if I ls in the homebridge folder i see only the following files
pi@raspberrypi ~/homebridge $ ls -l
total 48
drwxr-xr-x 2 pi pi  4096 Jan 28 19:36 bin
-rw-r--r-- 1 pi pi   599 Jan 28 19:36 config-sample.json
drwxr-xr-x 3 pi pi  4096 Jan 28 19:36 example-plugins
drwxr-xr-x 2 pi pi  4096 Jan 28 19:36 lib
-rw-r--r-- 1 pi pi 10172 Jan 28 19:36 LICENSE
drwxr-xr-x 7 pi pi  4096 Jan 28 19:36 node_modules
-rw-r--r-- 1 pi pi   774 Jan 28 19:36 package.json
-rw-r--r-- 1 pi pi 10318 Jan 28 19:36 README.md

Try doing a global install: npm install -g homebridge and running DEBUG=* homebridge -D in your home dir ~/

I actually managed to get it running by just typing the command homebridge.. Why is every tutorial saying npm start run in the same folder?? Are those outdated or so?

@ro8in which tutorial are you referring to?

For example this one
https://www.domoticz.com/wiki/Homekit_Siri

We should create some official steps in the wiki. That may alleviate the amount of install issues that open up.

I think the easiest way to get it running is through docker:
https://github.com/patrickbusch/homebridge-docker
all the node stuff etc is working in this docker image

I completely agree. Im ussually pretty good at this. I can get most stuff running without reading even half the manual.. I got over 15 years of linux expirience and this was the first time in years i was pulling my hairs out and took my personal walk of shame to ask for help on the forums..
But to be honest most atleast domoticz related homebridge install tutorials mention exactly the same way, use npm run start to start it up.. I would love to help to write this on the wiki, but in all honesty I did so many things today im not sure now anymore what was good and not..

Haven't checked tho but not sure if theres docker available on raspbian yet..

it is. I have it running on mine. http://blog.hypriot.com/getting-started-with-docker-on-your-arm-device/

authors: KhaosT damianromanowski julianfez ro8in snizzleorg


text:
[PR] Update to SAFE stack v2.2 & Migrate to MySql #32

This issue is related to the pull request #32 .
The following list of points is copied from the pull request:
Update to only dotnetcore3.1 projects
simplify paket groups
[BUGFIX] Error with Fable solved by setting the version for Fable.SimpleJson to 3.11.0
Migrate database from MSSQL to MySql
-> Add docker-compose.yml file for MySql+Adminer instance
-> Add db.sql dump file to initialize Swate DB to MySql docker instance
-> Adjust fake.fsx to automatically start docker-compose with "OfficeDebug" target
Update README with information about docker.

In addition i though about automaticall adding the LocalConnectionString to the user secrets, but was unsure if this is wanted.
If you found room for improvement or want something changed, just tell me.

Applied requested changes:
Apply Requested Changes According to PR #32
- Return to previous fake-cli version 5.20.3
- Fix typo in README.md
- Return to inline dependencies in build.fsx
- Allow users to set MySql password during setup with optional paramater
- Remove Client side user secret

I tried to solve the problems you had running this on your machine;
Bug-Fix:

- add Fable.Elmish to Client paket.references
- add testApi and increase specificity of api forwarding
- add install.cmd and related info to README.md
- revert build.fsx inline dependencies to paket build-group


text:
[Bug]: term search only yields very few and confusing results

Contact Details
No response
What happened?
For instance, searching for Arabidopsis just yields "Arabidopsis thaliana metabolite"

What did you expect?
No response
Host
Applies to All
Host Details
any
Swate version
v1.0.0-alpha.11

Yeah database seems to have an issue, i'll contact Marcel.

@Zerskk "reset" the database and now all terms should be included again

authors: Brilator Freymaurer


text:
飞书应用推送出错

2024-05-09 16:12:13,209 - 1260736-MainThread -       _query_task.py[line: 61] - ERROR: 【bilibili】推送通道【推送通道_飞书自建应用】出错：Invalid URL '': No scheme supplied. Perhaps you meant https://?
Traceback (most recent call last):
File "/home/aio-dynamic-push-master/query_task/_query_task.py", line 59, in push
target_push_channel.push(title, content, jump_url, pic_url)
File "/home/aio-dynamic-push-master/push_channel/feishu_apps.py", line 40, in push
img_key = self._get_img_key(pic_url)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/aio-dynamic-push-master/push_channel/feishu_apps.py", line 88, in _get_img_key
response = requests.get(pic_url, verify=False)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/sessions.py", line 575, in request
prep = self.prepare_request(req)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/sessions.py", line 486, in prepare_request
p.prepare(
File "/usr/local/lib/python3.11/dist-packages/requests/models.py", line 368, in prepare
self.prepare_url(url, params)
File "/usr/local/lib/python3.11/dist-packages/requests/models.py", line 439, in prepare_url
raise MissingSchema(
requests.exceptions.MissingSchema: Invalid URL '': No scheme supplied. Perhaps you meant https://?

麻烦提供下用户id或者动态id，这个是动态图片下载时报错了，从日志上看是图片 url 缺少了 scheme（http:// 或 https://）
猜测可能是叔叔改了图片返回的格式

麻烦提供下用户id或者动态id，这个是动态图片下载时报错了，从日志上看是图片 url 缺少了 scheme（http:// 或 https://）
猜测可能是叔叔改了图片返回的格式

2024-05-09 16:12:12,950 - 1260736-MainThread -    query_bilibili.py[line:312] -  INFO: 【B站-查询直播状态-B站】【机智大灯灯】开播了，准备推送：【歌势】可爱如我
2024-05-09 16:12:13,209 - 1260736-MainThread -       _query_task.py[line: 61] - ERROR: 【bilibili】推送通道【推送通道_飞书自建应用】出错：Invalid URL '': No scheme supplied. Perhaps you meant https://?
Traceback (most recent call last):
File "/home/aio-dynamic-push-master/query_task/_query_task.py", line 59, in push
target_push_channel.push(title, content, jump_url, pic_url)
File "/home/aio-dynamic-push-master/push_channel/feishu_apps.py", line 40, in push
img_key = self._get_img_key(pic_url)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/aio-dynamic-push-master/push_channel/feishu_apps.py", line 88, in _get_img_key
response = requests.get(pic_url, verify=False)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/sessions.py", line 575, in request
prep = self.prepare_request(req)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/requests/sessions.py", line 486, in prepare_request
p.prepare(
File "/usr/local/lib/python3.11/dist-packages/requests/models.py", line 368, in prepare
self.prepare_url(url, params)
File "/usr/local/lib/python3.11/dist-packages/requests/models.py", line 439, in prepare_url
raise MissingSchema(
requests.exceptions.MissingSchema: Invalid URL '': No scheme supplied. Perhaps you meant https://?
完整的是这样的，是直播状态检测

无法复现，但我更新加了日志打印，可以重新拉镜像观察一下 ec559eb0c036e56d002521035828ac154aecd1cf

发现后面的推送又正常了

等加上webhook参数再重新拉取吧，顺便问一下小红书那个报错正常吗

小红书报错正常，偶发风控，不会影响后续查询

authors: Arukassss nfe-w

repo: nfe-w/aio-dynamic-push


text:
automated deactivation of accounts end of season

As NFFTT staff I want the system to automatically deactivate everyone at the end of the season so that I don't have to do it manually.

I've run the task to deactivate all non admins for last year
It's based on cutoff date - basically when you sign up it sets your membership end date to March 31st of next year, and we deactivated everyone who had a membership end date before March 31st 2025.
This may not be quite right - I added it to the weekly agenda

authors: RachelNFFTT mveytsman

repo: nfftt/portal


text:
[FEATURE REQ] Archive data more frequently during season

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe.
Getting the latest depth_chart data Thursday is a little late when trying to create stat predictions for the upcoming week. Most fantasy players are adjusting lineups starting Tuesday morning so it'd be great if datasets like depth_chart could be refreshed daily during the season so that the latest data is always available. I'm happy to help PR this if there's interest.
Describe the solution you'd like
Datasets like depth_chart are refreshed daily during the NFL season.
Describe alternatives you've considered
No response
Additional context
I'm building stat predictions using this data and depth_chart data is a key piece of my prediction, so I don't want to release any predictions until that is refreshed for the week. This means I won't be able to get predictions out til Thursday instead of Tuesday.
Thanks so much for this project, by the way. It's really great to have such a high quality dataset available.

https://github.com/nflverse/nflverse-rosters/blob/3637c34ed6dce797be59caae16271634161ab3a3/.github/workflows/update_depth_charts.yaml#L3
Depth charts are updated daily at 7:00 UTC

oh my bad! I was going off the cron in the github actions yaml. Thanks!

Ah, in this repo? We archive all data in the github releases once a week in-season. Jobs generally have their own schedule.

yeah, sorry. was referring to this: https://github.com/nflverse/nflverse-data/blob/main/.github/workflows/run_archive.yaml#L4
good to know these will be daily though! Do you have any idea when the first 2024 depth chart will be published?

@dschuler36 We pull depth charts from the NFL API. Rather frustratingly, it typically takes until after week one games for these depth charts to populate in the API--then moving forward, each week's depth charts are available ahead of that week's games. So, the typical timeline is:
Week 1 games are played
Week 1 and 2 depth charts become available in the API
Week 2 games are played
I understand that this isn't ideal, unfortunately, we don't produce the depth charts ourselves, and we're at the mercy of the NFL API on this one.

thanks for the details, John! No worries, I can compile manually for now until they're available. Thanks for all the help

repo: nflverse/nflverse-data


text:
Context menus not always opening from grids

From Layers or Feature List (anywhere there's a grid), do left click, right click, left click, right click.  The context menu will not open on the second right click.  The selected row can even be changed a number of times and the context menu will still fail consistently on the second attempt.  On the third right click, the menu will open.

Workarounds in feature-list.spec.js need to be removed after this is fixed.

repo: ngageoint/opensphere


text:
Load from saved offline pickle of the input from dataloader

Simple change to load Python dict of inputs load from a pickle rather than needing preprocessed data. This is only for testing.

Implemented in https://github.com/ngaloppo/PGP/commit/8a0b719a7c3012e850bbf82b7c38126db162e11f. Let me know if that works for you. Sorry for the double work!

authors: ashishbdatta ngaloppo

repo: ngaloppo/PGP


text:
GOOD

It's amazing.

Thanks You !!!

repo: ngdangtr/F-Tool


text:
The redux state is not submitted

I use
applyMiddleware(
  ravenMiddleware('https://***@app.getsentry.com/***')),
  thunk,
  logger
);

I can see the breadcrumbs:
redux   MY_ACTION   00:45:53

but there is no state in the "Additional Data".
If I insert a fake error here https://github.com/ngokevin/redux-raven-middleware/blob/master/index.es6#L27 the state will be submitted, but otherwise, looks like the error doesn't come out of next(action)

So apparently it's only supposed to give you the Redux state for issues in your Reducer and Action.
It didn't work for me either and I ended up add it to the Raven callback in another thread suggested here.
In my configureStore.js createStore() function
         applyMiddleware(middleware, createDebounce(), thunkMiddleware,              // We init Raven here, so we can use RavenMiddleware to get:             // 1) Redux action breadcrubms (useful for debugging)             // 2) current state of the store (not working here, so we use the dataCallback to insert out own)         	RavenMiddleware(         		'***sentry dsn***,                 {                     release: '2.0',                     dataCallback: (data) =>                      {                         callbackRavenMiddleware(data);                     }                 }         	)         )
dataCallback is called just before an error is sent to Sentry.
In my app.js I have this function exported
export function callbackRavenMiddleware(data) {     if (!(data.extra && data.extra.state))      {         try          {             data.extra.state = store.getState();         }          catch (expt)          {             console.log(expt);         }     }     return data; }
The reason I have it in app.js is because store.getState() needs to be the current store and you can't do this in configureStore.js because that's where the store is created.
So far this is working for me. So in the end raven-redux-middlware just gives me the action breadcrumbs which are still pretty useful. It's not working for me to show the current state of the store.

I've implemented an alternative library which, after each action, attaches the current state to Raven as context. This means that all exceptions will include your current state as context, not just exceptions encountered within your reducer.

Thx @captbaritone, exactly what I was looking for.
I stared your repo 😏

authors: NameFILIP akhayoon captbaritone tomaswitek

repo: ngokevin/redux-raven-middleware


text:
Issue with server side rendering

var _Raven = window.Raven; errors out when server side rendering is done.
When we import import ravenMiddleware from 'redux-raven-middleware'; for redux integration with raven, server side doesn't have window object due to which the above mentioned line errors out.
We can add conditional execution of this middleware but since the declaration is done at compile time we're unable to escape that

So to circumvent this a little bit, I added this work around,
    if (typeof window === 'undefined') {
    return store => next => action => next(action); //eslint-disable-line
  }

  Raven = require('raven-js');
    if (typeof window === 'undefined') {
    return store => next => action => next(action); //eslint-disable-line
  }

  Raven = require('raven-js');
  if (!Raven.isSetup()) {
    ...etc
  }

Prevents raven from getting required on the server side.

Are you still encountering this error?

authors: abhinavsingi captbaritone philipchmalts


text:
formControl.setValue doesn't remove/add conditional fields in the form

Description
I want to add/remove some controls based on the value of other controls in the form. In some cases the value has to be set programatically using setValue and it doesn't work.
Minimal Reproduction
StackBlitz
Your Environment

Angular version: 13.3.11
Formly version: 6.0.1

Additional context

I'm calling setValue from a wrapper
In the above reproduction, it works when I wrap it in a setTimeout, but it's not reliable and doesn't help in my actual project ☹

just to understand the request, do you means the model value should be updated instantly when calling setValue?
or are you looking for an alternative way to get notified when the model is updated?

Doesn't have to be instant. Just want a way to ensure the model & other controls are updated. I'd have been okay with setTimeout if it's reliable, but it sometimes does not work in my case though it works in the example I provided.

Try this:
this.options.fieldChanges
  .pipe(
    filter(({ field, type }) => type === 'valueChanges' && this.field === field),
    tap(() => console.warn(this.model)),
  )

Hmm... Works here, but fieldChanges isn't emitting at all, in my project. Any hunch on what could be wrong?

Think I found the issue. In my wrapper code, I have the following.
<ng-container *ngIf="canShowFields" #fieldComponent></ng-container>

canShowFields is false when when I setValue, and becomes true later only.
Changing it to the following solved the issue
<div [class.d-none]="!canShowFields">
  <ng-container #fieldComponent></ng-container>
</div>

Thanks for your prompt response anyway, appreciate it man!

repo: ngx-formly/ngx-formly


text:
feat(json-schema): move 'null' type to @formly/core

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
Null type for json-schema needs to be implemented manually.
What is the new behavior (if this is a feature change)?
Null type for json-schema is added to @formly/core
Please check if the PR fulfills these requirements

[X] The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[X] A unit test has been written for this change.
[X] Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
[X] My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)

Other information:
I think it makes most sense to add the null type to core, but open for other suggestions.
I had to get rid of the form-field wrapper, not sure if that's an issues.
@aitboudad what do you think?

Well, I'm not clearly sure about that move :thinking:, null in json-schema is used to display title and description an may also render error message for that reason we've used form-field wrapper.
I'd prefer to not hurry for null, object and array types. They should the latest part in json-schema roadmap.

That makes total sense @aitboudad - I'm closing this for now. Let's take another look at it further down the line :)

authors: aitboudad beeman