text:
#5 Adding DSL to define properties

user is able to specify

default value
if field is required
validator

validation messages displayed in the props dialog

I propose the following DSL:
fork {
    config {
        cloneFiles()
        moveFiles(mapOf(
                "/com/company/aem/example" to "/{{projectGroup|substitute(\".\", \"/\")}}/{{projectName}}",
                "/Example" to "/{{projectLabel}}",
                "/example" to "/{{projectName}}"
        ))
        replaceContents(mapOf(
                "com.company.aem.example" to "{{projectGroup}}.{{projectName}}",
                "com.company.aem" to "{{projectGroup}}",
                "Example" to "{{projectLabel}}",
                "example" to "{{projectName}}"
        ))
    }
    defineProperties(mapOf(
            "aemSmbDomain" to {
                required()
                defaultValue = "Damian is cool"
                validator = {
                }
            },
            "aemInstanceLocalJarUrl" to {
                required()
                validator = {
                    if (!it.contains("@")) error("Oh, this is not an email!")
                }
            }
    ))
}

In validator dsl please change receiver instead of using 'it'

How about introducing new type of field, checkbox / boolean?

Maybe we'll should inverse logic because most of fields will be 'required', so that maybe you need to make it required by default an introduce instead 'optional' method

PR updated, I will update README in next PR.
New DSL looks like this:
fork {
    properties(mapOf(
            "enableSmbClient" to {
                type = CHECKBOX
                defaultValue = "true"
            },
            "aemInstanceAuthorHttpUrl" to {
                defaultValue = "http://localhost:4502"
                validator = {
                    if (!value.startsWith("http", ignoreCase = true)) error("This is not an HTTP URL!")
                }
            },
            "aemInstanceAuthorJvmOpts" to {
                optional()
                defaultValue = "-server -Xmx1024m -XX:MaxPermSize=256M -Djava.awt.headless=true"
                validator = {
                    if (!value.startsWith("-")) error("This is not a JVM option!")
                }
            },
            "aemSmbUsername" to {
                defaultValue = System.getProperty("user.name")
            },
            "aemSftpPassword" to {
                type = PASSWORD
            },
            "projectGroup" to {
                defaultValue = "org.neva"
            }
    ))
    config {
        cloneFiles()
        moveFiles(mapOf(
                "/com/company/aem/example" to "/{{projectGroup|substitute(\".\", \"/\")}}/{{projectName}}",
                "/Example" to "/{{projectLabel}}",
                "/example" to "/{{projectName}}"
        ))
        replaceContents(mapOf(
                "com.company.aem.example" to "{{projectGroup}}.{{projectName}}",
                "com.company.aem" to "{{projectGroup}}",
                "Example" to "{{projectLabel}}",
                "example" to "{{projectName}}"
        ))
    }
}

I added two new types: PATH & URL and default validation for them. By default properties whose names end with "path" or "url" get those types. This can be overridden.

I alredy pushed updates to reflect new features in README.

authors: mierzwid pun-ky

repo: neva-dev/gradle-fork-plugin


text:
Seeds have wrong name

Both cabbage seeds and tomato seeds don't have seed in their names:

Hello @SandWoodJones, thanks for the report, it will be fix by issue #13 that updates all translations files.

This isn't actually fixed by the translation file update. The problem is that BlockItems don't have their own translation string and just reuse the block's name. Seeds should be AliasedBlockItem instead.

source: gharchive/issue

authors: SandWoodJones Zifiv erisdev

repo: newhoryzon/farmers-delight-fabric

license: MIT

license_type: permissive

license_source: github-api


text:
[Swiftype] Add meta tags to details pages

Summary
Add the following <meta> tags to the <head> of all quick start detail pages so we can use that in swiftype search queries.
The theme's SEO component does this automatically by looking at the domain of a given site's siteUrl (set in gatsby-config.js). We will need to include a way to pass the type for quick starts (because they live on developer subdomain) as a prop to override this default behavior.
<meta class="swiftype" name="type" data-type="enum" content="io">

Add a <meta> tag for each keyword associated with a quick start:
<meta class="swiftype" name="tags" data-type="string" content="TAG_NAME_1">
<meta class="swiftype" name="tags" data-type="string" content="TAG_NAME_2">

Add a <meta> tag for the quick start name:
<meta class="swiftype" name="quick_start_name" data-type="string" content="QUICK_START_NAME">

the content should populate with quickstart.title field.
Notes
In order to see those meta tags in development, I think you may have to run a build.
Acceptance criteria

[ ] On each quick start details page, the above meta tags are in the <head> element
[ ] On each quick start page, the only type field is quick_starts (and not developer)

Relavant link
Theme's SEO component

@roadlittledawn i see the site type here as both "io" and "quick_starts" and somehow my change ended up being "quickstarts" 😂 which one of these would you prefer?

my bad. didn't get a chance to update all the tickets to use same value. i believe we said we'll go with quickstarts

authors: LizBaker roadlittledawn

repo: newrelic/developer-website


text:
Change "contributing" link in docs sidebar to point to README

Summary
On the docs site, I'd like the "contributing" link here to go to the README for the docs site, not the CONTRIBUTING file

Possible Solution
This appears to be set in packages/gatsby-theme-newrelic/gatsby-node.js:
      return repository
        ? `${repository}/blob/${branch || DEFAULT_BRANCH}/CONTRIBUTING.md`
        : null;

@jpvajda FYI

@austin-schaefer you can configure this in Gatsby-config.js! If you add a contributingUrl property to siteMetadata (per the docs), this will update that link.

Here is where you'll want to add it: https://github.com/newrelic/docs-website/blob/develop/gatsby-config.js#L27

I don't agree with this. Contributing tells you all you need to know to contribute (hence the name) the readme is just getting you up and running.

One other thing I'll mention here is that in talking with @bradleycamacho, I think the idea long-term was to point to the contributing docs in the docs site itself since these are super helpful for everyone.

Yeah, I chatted with @mmfred about this recently.
The current plan is:
Next sprint I will go through the contributing file again and rewrite a significant portion of it. Originally I left content contribution in there since it made sense to me at the time, but I now realize we definitely should have a specific doc for content contributions. I'll port EVERYTHING content contribution related out of the contributing file.
I suggest we hold off on this for a few weeks and until I get that work done.

@bradleycamacho Sounds good! Can you add a note to your ticket to look at this link as part of that work? I'll close this issue for now.
@jpvajda : I like Jerel/Bradley's suggestion of linking to an actual HTML page on it once we have that written into the style guide. I'd like to keep the sidebar space in particular focused on first-time contributors and small contributions.

@austin-schaefer Created DOC-6667 with a link to this issue

authors: austin-schaefer bradleycamacho jerelmiller jpvajda

repo: newrelic/gatsby-theme-newrelic


text:
Reference classFile variable when logging exceptions in ClassTransformWrapperTask

Came across an exception in one of our engineers builds today which looks a little like the following:
Caused by: groovy.lang.MissingPropertyException: Could not get unknown property 'classJar' for task ':app:newrelicTransformClassesForGoogleDebug' of type com.newrelic.agent.android.ClassTransformWrapperTask.
	at org.gradle.internal.metaobject.AbstractDynamicObject.getMissingProperty(AbstractDynamicObject.java:85)
	at org.gradle.internal.metaobject.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:62)
	at com.newrelic.agent.android.ClassTransformWrapperTask_Decorated.getProperty(Unknown Source)
	at com.newrelic.agent.android.ClassTransformWrapperTask$_transformClasses_closure1$_closure2$_closure5.doCall(ClassTransformWrapperTask.groovy:101)
	at jdk.internal.reflect.GeneratedMethodAccessor2490.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at com.newrelic.agent.android.ClassTransformWrapperTask$_transformClasses_closure1$_closure2.doCall(ClassTransformWrapperTask.groovy:71)

Digging into the NewRelic agent Gradle Plugin source, I noticed there's a variable used in an catch-block which isn't actually defined. Falling in to this catch block would cause an unrelated exception in the build, which is a little misleading.
I've referenced the nearest equivalent to other logger.error calls in this class, but there are further improvements that could be added here, including passing the caught fileException to the logger. This would show the cause of the error in the Gradle stacktrace:
--- logger.error("[ClassTransform] [${classFile.path}] ${fileException.message}")
+++ logger.error("[ClassTransform] [${classFile.path}]", fileException)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

source: gharchive/pull-request

authors: CLAassistant jamiesanson

repo: newrelic/newrelic-android-agent


text:
Cannot read properties of undefined (reading 'stopTimer')

I am using browser agent for my Next JS application.
I am getting this error (Cannot read properties of undefined (reading 'stopTimer')) reported on my sentry very frequently.

@Pranav2111 we need more information to go on. What version of the agent are you using? Is this the NPM package or how is the agent installed? What version of node, npm, nextjs, etc? Drop a copy of your package.json and code where you are instrumenting the agent if it is the npm package. Whats the stack trace for the error? Please provide as much detail as possible when reporting issues to open source projects. Thanks.

We had another report of this same issue, and I suspected the area of source of it, but thank you for giving us the trace to confirm! Will be spinning up a bug ticket for this.

We are encountering the same issue, which started to happen on June 27 in our React App.

We have been encountering the same issue since June 28  in Angular 17 app.
T.abortin https://js-agent.newrelic.com/nr-spa-1.261.1.min.js at line 2 : 65690

n.<anonymous>in https://js-agent.newrelic.com/nr-spa-1.261.1.min.js at line 2 : 61759
Object.emitin inline code at line 37 : 9898
anonymousin https://js-agent.newrelic.com/nr-spa-1.261.1.min.js at line 2 : 94242

The same error appears for the nr-spa.1.261.2 started 27 of June as well

this error is going alongside with undefined is not an object (evaluating 'this.scheduler.stopTimer') error as well which happens in Chrome and Safari on Mac only.

i guess line 208 in the unminified code should be this.scheduler?.stopTimer() ?

We've been getting this error sporadically starting June 27 at 3:34 AM US/Central. (Didn't seem high priority given the low % of page loads it was happening on.)
Unhandled error
TypeError: Cannot read properties of undefined (reading 'stopTimer')
Location
https://js-agent.newrelic.com/nr-spa-1.261.1.min.js:2 - T.abort

Today we started getting this slightly different message:
Unhandled error
TypeError: this.scheduler is undefined
Location
https://js-agent.newrelic.com/nr-spa-1.261.2.min.js:2 - abort

we need more information to go on. What version of the agent are you using?

Just newrelic_rpm (9.8.0)

Is this the NPM package or how is the agent installed?
What version of node, npm, nextjs, etc?

nodejs 16
yarn 1.22
Although, any tooling is being injected by newrelic_rpm which we installed ~3 months ago at v 9.8.0. (We'll look at updating it to 9.11 this week, but that seems unrelated in our case)

We've been seeing quite a bit of these in the last week, which is clogging up our error notifications a bit. I cannot see the JIRA issue linked to see what the status is.
Thanks for working on this, either way!

This is the top of our list this week, so please wait for a patch in the next few days.

authors: Pranav2111 YesThatAllen cwli24 jaohaohsuan lluchez patrickhousley rylanb zboris

repo: newrelic/newrelic-browser-agent


text:
Please provide an ARM64 docker image or a multi platform image

Feature Description
The official newreliccli docker image on dockerhub only supports linux/amd64 https://hub.docker.com/r/newrelic/cli/tags.
ARM64 builds are available https://github.com/newrelic/newrelic-cli/releases/tag/v0.73.3 but there's no official docker image with ARM support.
Having this officially supported would make using the newrelic cli on ARM machines with docker containers that little bit easier.
Describe Alternatives
The alternative is to simply build my own image via downloading the appropriate binary from the github releases.
Additional context
Basic scenario: Imagine having some ARM virtual machines that perform certain pipeline steps (self-hosted runners - GitLab, GitHub etc). There might be steps that want to use the newrelic cli (creating a change marker for a deployment for example). Having an ARM64 image or even better, a multi-platform image would make this scenario that little bit smoother by supporting a more diverse set of hardware configurations.
Thanks :+1:

Thanks for inquiry @artlist-scottambrose. This seems like a reasonable ask. I can't provide an exact timeline, but we'll see where we can fit this in. 👍

We also looking for ARM64 docker image

repo: newrelic/newrelic-cli


text:
Fix pytest test filtering when running tox

Overview
Removing the [] broke pytest filtering when I switched the tests to wrap pytest in coverage. This reverts that change.
Before fix this would not filter the tests:
tox -e python-cross_agent-pypy-without_extensions -- -k test_collector_hostname
With this fix now it does.

Codecov Report

Merging #823 (0d2ae36) into main (c2d4629) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #823      +/-   ##
==========================================
- Coverage   76.40%   76.38%   -0.03%
==========================================
  Files         198      198
  Lines       19327    19327
  Branches     3307     3307
==========================================
- Hits        14766    14762       -4
  Misses       3716     3716
- Partials      845      849       +4

see 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter hmstepanek

repo: newrelic/newrelic-python-agent


text:
App does not initialize

Description
The latest version of this app (main) does not initialize and just displays

The currently deployed version (1.3.1) is working fine.
Steps to Reproduce

Clone the main branch of this repository
npm install
npm run start
Navigate to the local app in New Relic
Notice the message

Expected Behaviour
The app loads without an issue.
Relevant Logs / Console output
There were no errors in the logs.
Your Environment

NR1 CLI version used: @datanerd/nr1/1.32.0 darwin-x64 node-v10.16.3
Browser name and version: Chrome 89.0.4389.90 (Official Build) (x86_64)
Operating System and version: MacOS Big Sur 11.2.3

Thanks Alex. Replicated here. Seems to be failing locally but the version in the New Relic app catalog works just fine.
Looks like the query for accounts is returning NULL, but the query ran independently against the account returns results fine. Investigating to see why this weirdness might be happening.

@aswanson-nr looks like it may just be a New Relic staff impact. If you remove your profile and regenerate it in your CLI. It began working again for me no problem.

@goldenplec You were completely right! Looks like it was user error! Sorry to take up your time.

authors: aswanson-nr goldenplec


text:
Make textwrap in 'save' configurable

Hello,
when saving articles, lines are wrapped so that the resulting textfile has 80 columns. The same is true when piping an article through a script. While this certainly aids readability, it is not optimal for all users and in particular, when piping an article to a script (which then typically unwraps again to parse the headers).
Therefore, it would be nice to introduce a 'wrap-on-save-and-pipe' (the name can definitely be improved) configuration option which stores the maximum linewidth. By default it should be 80 and a value of 0 means that wrapping is disabled.

There's an issue about pipe-to already: #833.
I'm ok with adding an option for this, but I think pipe-to and save should have separate ones because there is no inherent connection between those two operations, and I don't think it make sense to couple their settings.

I agree that pipe-to and save should have sepearate options.

Everything I said in https://github.com/newsboat/newsboat/issues/833#issuecomment-873462365 applies here too.

authors: Minoru herrsimon

repo: newsboat/newsboat


text:
Enqueueing podcasts can result in duplicate filenames

Newsboat version: 426e911e980492fd569618384121c1cc2810b718 (current master)
Config file (copy from ~/.newsboat/config or ~/.config/newsboat/config):
# Empty

Steps to reproduce the issue:

Add https://feeds.simplecast.com/XA_851k3 (Stack Overflow Podcast) to the urls file

In Newsboat, enqueue multiple items from the feed

Start podboat, observe that multiple entries have the same download location.

Other info you think is relevant:
It would be useful if Newsboat would check if a filename already exists in the queue file before adding it.
Newsboat already looks through the file to check if the download URL is present so we are looping through the file anyway.

Agreed. The question is: what to do about it? File managers usually append "(1)", "(2)" and so forth, perhaps we should do the same? This might conflict with the files that are already in the download directory.

Agreed. The question is: what to do about it? File managers usually append "(1)", "(2)" and so forth, perhaps we should do the same? This might conflict with the files that are already in the download directory.

I would prefer showing an error in the status line and returning false from the process_operation() function (for https://github.com/newsboat/newsboat/issues/1137) if the filename already occurs in the queue file.
Main reason: It makes sure people will notice if their configuration does not work well for certain feeds (e.g. in the case of https://feeds.simplecast.com/XA_851k3, the filename is always default_tc.mp3).
Then, they could change the configuration appropriately or even apply a specific workaround to the offending feed (when  per-feed settings are supported: https://github.com/newsboat/newsboat/issues/83).

I would prefer showing an error in the status line and returning false from the process_operation() function (for https://github.com/newsboat/newsboat/issues/1137) if the filename already occurs in the queue file.
Main reason: It makes sure people will notice if their configuration does not work well for certain feeds (e.g. in the case of https://feeds.simplecast.com/XA_851k3, the filename is always default_tc.mp3).
Then, they could change the configuration appropriately or even apply a specific workaround to the offending feed (when  per-feed settings are supported: https://github.com/newsboat/newsboat/issues/83).

Good point, I agree. By "changing the configuration appropriately", you mean changing  download-filename-format to include more info like episode's title, right?

Good point, I agree. By "changing the configuration appropriately", you mean changing  download-filename-format to include more info like episode's title, right?

Yes, that is exactly what I had in mind.

Yes, that is exactly what I had in mind.

authors: Minoru dennisschagt


text:
Poblems with CSI extraction

Grateful for your excellent job!
I use the Raspberry Pi 3B+, with kernel 5.10.92. Unfortunately I ran into the following issues while capturing CSI:

After executing the install scripts, when cursor on the wifi icon, it shows 'no wireless interface found' is that normal?
I connect the raspi and laptop with an ethernet cable,  making laptop connected to the mobile hotspot, then I ran the command
 mcp -C 1 -N 1 -c 36/80
ifconfig wlan0 up
then ran ip link show wlan0 to find the mon0'Mode is Down, which dont seems right
I ran the following command as instructed
nexutil -Iwlan0 -s500 -b -l34 -vKuABEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
iw dev wlan0 interface add mon0 type monitor
ip link set mon0 up
then ran ip link show wlan0 to find the mon0'Mode is Down, which dont seems right either
I ran tcpdump -i wlan0 dst port 5500 -vv -w output.pcap -c 1000 and got feedback Got 0

It'll be of great help if you would fix the issues above for me. Thx!
@zeroby0

How did you fix it?


text:
2단계 - 요금 조회

리뷰 요청 드립니다! 감사합니다 :)

리뷰 반영하여 수정했습니다. 확인 부탁드립니다!

repo: next-step/atdd-subway-fare


text:
2주차 미션 Step1

안녕하세요 리뷰어님,
2주차 Step1 미션 리뷰 요청드립니다.
잘 부탁드리겠습니다.

안녕하세요 한솔님~ 꼼꼼한 피드백 감사합니다.
피드백 주신 사항들 반영하여서 다시 리뷰요청 보냅니다
이번 미션 하면서 제일 걸렸던 점은, mock 테스트 만들 때 Line과 Station의 id를 임의로 부여하기 위해 id까지 설정해주는 생성자를 추가로 집어넣었습니다. 그런데 제가 하면서도 해당 방법이 뭔가 짜고 치는 고스톱 같다는 느낌을 받았는데, 달리 뾰족한 수가 떠오르지 않아 그냥 이렇게 진행하였습니다..
이번에도 잘 부탁드리겠습니다
감사합니다.

repo: next-step/atdd-subway-path


text:
Step4 -요금조회

안녕하세요 준철님😁
지난주에 정신이 없던 상태에서 작업하던 내용을 전부 날려버리고 새로 진행하느라 거의 10일만에 4단계를 진행하게 되었네요 😅
요금 할인 정책과 관련해서 인터페이스로 처리할 수 있을것 같았는데 생각처럼 쉽지가 않았습니다.
모든 할인 정책도 최단거리를 조회할 때 처리를 할지 조회한 후 로그인유저를 판단해서 처리할지 등과 같은 부분을 생각해보니 쉽지 않더라구요.
피드백 부탁드립니다!

#tag @neojjc2

repo: next-step/atdd-subway-service


text:
feat(VocalGuildChannel): add VocalGuildChannel.members_count

Summary

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

What's a VocalGuildChannel ?
What is the aim of this PR?
The function right above where you edited also supposedly returns the same thing:
"""List[:class:Member]: Returns all members that are currently inside this voice channel."""
It's like making an extra property for len(Channel.members) - like making an extra property for len(guild.members)

member_count not members_count
Guild.member_count exists because that is provided by discord - is used especially when members intent is not enabled

repo: nextcord/nextcord


text:
Unqualified symbol when built in CI

I recently refactored my aoc solution repo to clean up the index, and after that commit; the CI complains with
:path-fn must be a qualified symbol pointing at an existing var
Despite that still being the case. What's even stranger is it only occurs in CI...

As above, when I clone a fresh repo there's no such error; so I'm completely stumped here :sweat_smile: Any ideas?

No good resolution here; I wasn't aware :paths can take wildcards so I just went for that instead now.

My first guess would be a classpath issue. Could the var be in a path brought in by an alias and not in use in CI?

My first guess would be a classpath issue. Could the var be in a path brought in by an alias and not in use in CI?

Potentially, but that doesn't explain how it was only failing in CI. I tried the same steps in a fresh Ubuntu image locally and it worked fine :/

authors: elken mk

repo: nextjournal/clerk

license: ISC


text:
Have utils.timeit return two elements not n elements

In utils.py, utils.timeit can return a tuple with n elements instead of a tuple with two elements. We would like utils.timeit to return a tuple with two elements where the first element may be another tuple and the second element is the timing information.
This requires changing lines like a1, a2, a3, a4, dt = utils.timeit(..)(...) to a, dt = utils.timeit.
More comments can be found in this function, utils.py:timeit.

Why is this preferred? This would always require an additional line to
parse the outputs
On Wednesday, February 3, 2016, Scott S. notifications@github.com wrote:

In utils.py, utils.timeit can return a tuple with n elements instead of a
tuple with two elements. We would like utils.timeit to return a tuple with
two elements where the first element may be another tuple and the second
element is the timing information.
This requires changing lines like a1, a2, a3, a4, dt =
utils.timeit(..)(...) to a, dt = utils.timeit.
More comments can be found in this function, utils.py:timeit
https://github.com/nextml/NEXT/blob/master/next/utils/utils.py#L322.
—
Reply to this email directly or view it on GitHub
https://github.com/nextml/NEXT/issues/92.

For the rewrite we’re using
alg_response, dt = utils.timeit(…)(…)
self.myApp.f(*alg_response)

which we can’t do if dt is included in the algorithm response (we don’t want to enforce that app developers include dt as their last argument.
On February 3, 2016 at 7:15:36 PM, Kevin Jamieson (notifications@github.com) wrote:
Why is this preferred? This would always require an additional line to
parse the outputs
On Wednesday, February 3, 2016, Scott S. notifications@github.com wrote:

In utils.py, utils.timeit can return a tuple with n elements instead of a
tuple with two elements. We would like utils.timeit to return a tuple with
two elements where the first element may be another tuple and the second
element is the timing information.
This requires changing lines like a1, a2, a3, a4, dt =
utils.timeit(..)(...) to a, dt = utils.timeit.
More comments can be found in this function, utils.py:timeit
https://github.com/nextml/NEXT/blob/master/next/utils/utils.py#L322.
—
Reply to this email directly or view it on GitHub
https://github.com/nextml/NEXT/issues/92.

—
Reply to this email directly or view it on GitHub.

Makes sense. Thanks
On Wed, Feb 3, 2016 at 5:18 PM, Scott S. notifications@github.com wrote:

For the rewrite we’re using
alg_response, dt = utils.timeit(…)(…)
self.myApp.f(*alg_response)

which we can’t do if dt is included in the algorithm response (we don’t
want to enforce that app developers include dt as their last argument.
On February 3, 2016 at 7:15:36 PM, Kevin Jamieson (
notifications@github.com) wrote:
Why is this preferred? This would always require an additional line to
parse the outputs
On Wednesday, February 3, 2016, Scott S. notifications@github.com wrote:

In utils.py, utils.timeit can return a tuple with n elements instead of a
tuple with two elements. We would like utils.timeit to return a tuple
with
two elements where the first element may be another tuple and the second
element is the timing information.
This requires changing lines like a1, a2, a3, a4, dt =
utils.timeit(..)(...) to a, dt = utils.timeit.
More comments can be found in this function, utils.py:timeit
https://github.com/nextml/NEXT/blob/master/next/utils/utils.py#L322.
—
Reply to this email directly or view it on GitHub
https://github.com/nextml/NEXT/issues/92.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub
https://github.com/nextml/NEXT/issues/92#issuecomment-179561295.

Closed by b0d0b1694fa90eaf662c14b2693f1e2046e66525

authors: kgjamieson scottsievert

repo: nextml/NEXT

license_source: bigquery


text:
🛑 /getCommentsByUrl - Get comments list by video URL is down

In 0823898, /getCommentsByUrl - Get comments list by video URL (https://nextpost.tech/tiktok-api/getCommentsByUrl?video_url=https%3A%2F%2Fwww.tiktok.com%2F%40onerepublic%2Fvideo%2F7141505394869898538%3Fis_copy_url%3D1%26is_from_webapp%3Dv1&cache_timeout=0&license_key=$API_KEY) was down:

HTTP code: 400
Response time: 6404 ms

Resolved: /getCommentsByUrl - Get comments list by video URL is back up in ea74306.

repo: nextpost-tech/tiktok-status


text:
context color easy access

now that the context colors are defined in components/types and have the type enum it's a bit difficult to reference it,
so I think either types should be exported in the Components object, or the type should be altered so that simply predefined string could be used

is it solved in https://github.com/nexys-system/tailwind-react-ui/blob/master/src/lib/components/type.ts#L17 @NatalieKapitonova

repo: nexys-system/tailwind-react-ui


text:
Chain proteinfold output to msa input

Description of feature
Chain proteinfold output to msa input

Solved in #176

repo: nf-core/multiplesequencealign


text:
WIP feat: jupyter notebook for api access demonstration

This feature adds a jupyter notebook to demonstrate the basic interactions the the API of the handle server.

For bystanders: This is not merged yet because the handle API is currently revised.

Superseded by #25

authors: dalito markdoerr


text:
 html tag does not display properly

Not sure if issue here or elsewhere, but the <kbd> ... </kbd> html tag does not display as button but rather monospace or similar in Safari and Firefox.

Can you add a screenshot?

On macOS it's the same in Safari, Firefox, Chrome

This seems to be a macOS styling decision then.
Not sure if this must be changed then?

Well, it's honestly still annoying.
I've tested html+css outside the knowledge base and was able to display a key properly with
kbd {
  padding:0.1em 0.6em;
  border:1px solid #ccc;
  font-size:11px;
  font-family:Arial,Helvetica,sans-serif;
  background-color:#f7f7f7;
  color:#333;
  -moz-box-shadow:0 1px 0px rgba(0, 0, 0, 0.2),0 0 0 2px #ffffff inset;
  -webkit-box-shadow:0 1px 0px rgba(0, 0, 0, 0.2),0 0 0 2px #ffffff inset;
  box-shadow:0 1px 0px rgba(0, 0, 0, 0.2),0 0 0 2px #ffffff inset;
  -moz-border-radius:3px;
  -webkit-border-radius:3px;
  border-radius:3px;
  display:inline-block;
  margin:0 0.1em;
  text-shadow:0 1px 0 #fff;
  line-height:1.4;
  white-space:nowrap;
}

(stack overflow styling, source: https://stackoverflow.com/questions/51641086/how-to-insert-the-so-like-kbd-effect-into-my-html-based-presentation)
However adding this to src/style/style.css didn't affect how it's displayed. Does fornax automatically overwrite the style sheet or pull from somewhere else?

Adding the style snipped from above to style.css works without issue for me,
I would recommend changing padding to padding: 0.1em 0.6em 0.1em 0.4em;, looks a bit better on windows at least, not sure about others

authors: Brilator Freymaurer


text:
Script type="application/ld+json" do not produce any output

From the readme this...
<Helmet>
      <script type="application/ld+json">{`
         {
             "@context": "http://schema.org"
         }
     `}</script>
    </Helmet>

should be a supported script but it doesn't seem to produce any output.
Reading the test here it seems that tags without src are not accepted, and this obviously could be the root cause of the issue.

Close this cause the problem is not present in the latest version.

It seems that I have the issue on the latest version. (5.2.0) Any idea of what happen ?

Oups.. seems that I forgot
{helmet.script.toComponent()}

authors: VincentCtr umbobabo

repo: nfl/react-helmet

license: mit


text:
Neon.Temporal status

Hey team - I hope you're all well!
I got in touch back in April with @jefflill over email about Cadence/Temporal and your .NET libraries. We (Ionburst) have been looking at integrating Temporal into our stack for a while - and as a .NET Core shop, we're interesting in using Neon.Temporal.
We've been keeping an eye on progress until we had time to start exploring Temporal fully. We're now in that place, so I was hoping to find out if Neon.Temporal is ready to use? I appreciate it's still under active development and we're not looking for a production-ready release, just something we can start to play around with.
Alongside that, we're more than happy to be guinea pigs and help with bug testing and scale/load-testing further down the line.
Cheers! 😄

HI: We're all doing fine and I hope you are too,
We're excited to see Temporal v1 launch.  We started the Temporal port a few months ago but sidelined it for several weeks while Temporal was making their final breaking changes and one of started a new job.
We're planning on getting started back into this beginning next week.  As you probably remember, the current Cadence implementation is actually based on the Cadence GO client and a wrapper program we developed that uses HTTP to proxy calls from .NET our GO proxy and then on to the Cadence server.  We're going to continue with this strategy for Temporal in the near term, but we hope to build our proxy as a DLL/shared library and drop the HTTP stuff and just marshal data between .NET and GO in memory buffers.  We experimented this briefly a year ago and has some problems which we now believe were unrelated.  This will be quite a bit nicer.
Neon.Cadence has been in serious test/production for a year or so now by a sister company and we really haven't seen much trouble (although traffic is pretty low).  These services are deployed as .NET Core to Linux containers running in Kubernetes.  We've seen 2-3 cases where the .NET side lost connectivity with the GO proxy and we had to restart the containers (there's a way to detect this situation from .NET).  We hope this will be moot after we convert to DLLs.
It's too early to give you an ETA on this.  We'll need to get back into this for a few week.  I'm crossing my fingers that perhaps we'll see something beginning to work in 4-6 weeks.
There are a couple important gaps right now in Cadence and Temporal being a port, has the same issues:

There's currently no way for a workflow to wait for one of multiple things to happen, like waiting for one of two child workflows to complete or a signal to be received.  We believe we've thought this through.  This will take a bit of refactoring.

We also haven't doing anything around workflow unit testing support yet.

Our plan is to:

Publish one or more alpha releases in maybe 4-6 weeks when most things work again (excluding the multi-wait and unit testing)
After we've added the multi-wait and unit testing and it looks reasonable, we'll start doing preview releases and we'll port our sister companies production cluster over.
Our thinking is that we'll continue doing preview releases into 2021 that are still based on the GO proxy but expected to be usable for production.
Q1 2021, we're planning on beginning a native gRPC implementation and dropping the GO proxy completely,  I haven't scoped how much work this will be (but hope springs eternal, so hopefully it won't be too bad).  Once this is complete and it looks good we'll make this a production release.

I expect the native gRPC production release to work much the same as he GO proxied one.  I think the main changes will be that some of the API methods will no longer be async and I think we'll be able to replace some of the workflow/activity futures related classes with standard .NET Task semantics.  We ended with more async APIs than are really necessary due to the additional layer of async-ness due to the HTTP communication with the GO proxy.
We really do welcome your interest and would love to have more eyes to be sure we get it right.  I've been super excited about this stuff since I saw Maxim do a Cadence talk 3-4 years ago.  I think the .NET community will love it.
--Jeff    jeff@lilltek.com
@johncburns1
@marcusbooyah

Fantastic, thanks for the update!

Hi there, how has this situation developed? Best, Robert

@surumadurum thanks for checking in! Naturally our development slowed down a bit due to unforeseeable circumstances (COVID).   We are still actively working on Neon.Temporal and it is nearing stability.
At the moment we are wrapping up Exceptions and Exception handling.  Once Exception handling is complete, Neon.Temporal will be usable featuring much of the same functionality Neon.Cadence provides.  After this initial port is complete we plan to implement the features mentioned here by @jefflill.
Thanks for the patience and if you have any more specific questions or just want an update please do not hesitate to reach out!

This has been on the back burner but we just decided to restart the effort because the current Cadence/Temporal implementations have stopped working on the latest .NET SDKs due to ASP.NET runtime conflicts.
We currently deploy a GOLANG proxy process that communicates with Cadence/Temporal servers and then bridge calls from the C# side to the proxy via HTTP.  The new plan is to convert the proxies to shared libraries (DLLs on Windows) so we'll be able to just do in-process calls.  We has this close to working a couple years ago but we had to move on to other priorities,
We're going to track this effort here: #1295
The Temporal implementation is otherwise fairly far along.  @johncburns1 has some error handling work remaining and I believe there were still a few unit test failures.

authors: jefflill jishf johncburns1 surumadurum

repo: nforgeio/neonKUBE


text:
Invariant Violation on loading the react component.

Hi ,
I'm seeing the below error
angular.js:13550 Invariant Violation: ReactCompositeComponent.render(): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.
at invariant (http://localhost:8080/bower_components/react/react.js:18893:15)
Below is the piece of code, Just tried to run based on the first set of instructions in the doc
<!DOCTYPE html>

    <meta charset="UTF-8">
    <link href="css/bootstrap.min.css" rel="stylesheet"/>
    <link href="css/font-awesome.min.css" rel="stylesheet"/>
    <link href="css/bootstrap-select.min.css" rel="stylesheet"/>
    <link rel="stylesheet/less" type="text/css" href="css/index.less"/>

    <react-component name="HelloComponent" props="person" watch-depth="reference"/>

Your render function is returning a string. Remove the single quotes and error should stop.

repo: ngReact/ngReact


text:
modified grep so daX are added to list

With current script on my system, only drives that use the built-in chipsets (Intel et al) get the nomenclature adaX. The rest of the drives, on LSI HBAs, have the nomenclature daX and thus were omitted by current script.  Made a minor change that rectifies this.

Thank you for your contribution! I totally forgot about the da prefixed devices :)

You're welcome, my pleasure

repo: ngandrass/freenas-spindown-timer


text:
Remove FIXME for de-duping matches

Per the ticket, I'm not able to reproduce the issue. It may have been fixed already, so closing out the ticket and removing the FIXME. If it pops up again in the future, we can reopen.
Closes #662

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

here is an example of to reproduce duplicated matches:
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: test
spec:
  parentRefs:
    - name: gateway
  hostnames:
    - "cafe.example.com"
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /coffee
          headers:
            - name: version
              value: v2
      backendRefs:
        - name: coffee-v2-svc
          port: 80
    - matches: # same matches
        - path:
            type: PathPrefix
            value: /coffee
          headers:
            - name: version
              value: v2
      backendRefs:
        - name: coffee-v1-svc # different destination
          port: 80

leads to:
    location /coffee_prefix_route0 {
        internal;

        proxy_set_header Host $gw_api_compliant_host;
        proxy_pass http://default_coffee-v2-svc_80$request_uri;
    }

    location /coffee_prefix_route1 {
        internal;

        proxy_set_header Host $gw_api_compliant_host;
        proxy_pass http://default_coffee-v1-svc_80$request_uri;
    }

    location /coffee/ {
        set $http_matches "[{\"redirectPath\":\"/coffee_prefix_route0\",\"headers\":[\"version:v2\"]},{\"redirectPath\":\"/coffee_prefix_route1\",\"headers\":[\"version:v2\"]}]";
        js_content httpmatches.redirect;

    }

    location = /coffee {
        set $http_matches "[{\"redirectPath\":\"/coffee_prefix_route0\",\"headers\":[\"version:v2\"]},{\"redirectPath\":\"/coffee_prefix_route1\",\"headers\":[\"version:v2\"]}]";
        js_content httpmatches.redirect;

    }

where $http_matches includes duplicated matches (they test the same header for the same value).
if you put the conflicting rules above in different HTTPRoutes resources, you will duplicate matches too.
Also, it looks like we have a bug here. I would expect that for resolving conflicting rules, because the rule coffee-v2-svc goes before  the rule coffee-1-svc in the HTTPRoute, it will win.   @kate-osborn  thoughts?

@pleshakov Good find, I think the example you provided is different from what caused the original bug to be found. In that case, we had duplicate matches forwarding to the same place, so they were redundant. In this case, they are different backends, so technically not redundant, but more of a conflict defined by the user. The ordering may be a bug as you mentioned, and the duplicate matches should be taken care of in this case so only the winning backend is forwarded to.
Since this was intended to be an unscheduled, one-day task, I can close this PR and copy your comment into the bug so we can better schedule it in the future since there appears to be real work to be done here.

authors: pleshakov sjberman

repo: nginxinc/nginx-kubernetes-gateway


text:
Fix to allow importing and exporting the list of redirects by exporti…

If you currently use the Misdirection ModelAdmin module to export the list of redirect and try to re-import it back into the CMS, several fields are missing from the exported sheet and redirects to Pages aren't restored to the right PageID.
This PR solves this issue by exporting all available fields defined in the LinkMapping object.

Thanks for this! Sorry for taking a while to get to it, but I'll be looking at merging this one soon. Any chance of resolving the merge conflicts please?

@nglasl this can be closed now as I have incorporated this fix into my PR.

authors: jvdanker nglasl wilr

repo: nglasl/silverstripe-misdirection


text:
Support CAA Records

It would be nice if the UI would support CAA records.

Just add it to RECORDS_ALLOW_EDIT, and it should work just fine.

How do you do this? where is this property defined? file?

@bitsofinfo, in config.py.

ref: #197

authors: bitsofinfo jallakim ngoduykhanh techhelper1

repo: ngoduykhanh/PowerDNS-Admin


text:
Feature request: Changelog file

Hi - Great work being done by the NGRX team and community. I hope to see this effort goes long way.
Can someone please add/maintain a changelog file for this project. Will make it easier to check if there are any breaking changes in newer versions or perhaps some cool new feature has been introduced.

See https://github.com/ngrx/platform/issues/99

authors: hassanasad robwormald

repo: ngrx/store


text:
JSON Schema Field Order

Question
Is it possible to render fields in a specific order specified by a JSON schema? right now my API returns an object and its properties appear in a different order every-time I query it.
Is it possible to provide ngx-formly a JSON schema property to render those fields in a specified order?
example:
{
    "title": "Display Types",
    "type": "array",
    "items": {
        "type": "object",
        "required": [
            "id",
            "display"
        ],
        "order": ["id", "display"], //<--- Is it possible or already a feature to do something like this?
        "properties": {
            "display": {
                "description": "what is the display type?",
                "type": "string",
                "enum": [
                    "GRID",
                    "FORM"
                ]
            },
            "id": {
                "description": "Name of display type",
                "type": "string"
            }
        }
    }
}

use map options to adjust the generated FormlyFieldConfig:
function orderSchemaFields(mappedField: FormlyFieldConfig, mapSource: JSONSchema7) {
  if (schema.order) {
    ...
  }

  return mappedField;
}

...
this.formlyJsonschema.toFieldConfig(schema, { map: orderSchemaFields });

repo: ngx-formly/ngx-formly


text:
Disable option on select field

Question
How to disable options for a select?
I know it is possible by registering in the fields like this:
templateOptions: {
    label: 'Label 1',
    options: [
        {
            label: "Option 1",
            value: 1,
            disable: true
        },
        {
            label: "Option 2",
            value: 2
        }
    ]
}

But I would like to disable an option of a select according to some condition. Is there any way to do this?

use disabled instead:
{ value: 1, label: 'Option 1', disabled: true }


text:
The current configuration of Emscripten with PTHREAD_POOL_SIZE=32 for multi-threading may be causing memory wastage

About this config:
https://github.com/ngxson/wllama/blob/65bbcc07c52d9105936bcd783e3e718ca93d1c5f/scripts/docker-compose.yml#L35
Some people recommend using PTHREAD_POOL_SIZE=navigator.hardwareConcurrency, so it won't create more workers than the number of logical processors available to run threads on the user's computer:

https://github.com/emscripten-core/emscripten/issues/14407#issuecomment-861038985
https://www.jackyoustra.com/blog/binary-analysis#multithreading-discovered-later-in-the-story

I believe that would already be an improvement.

But then I started thinking of some other option, which I don't know if it would work, but could prevent any waste of resources: to use PTHREAD_POOL_SIZE=self.WLLAMA_PTHREAD_POOL_SIZE.
By doing so, you could set self.WLLAMA_PTHREAD_POOL_SIZE = nbThreads before the multi-thread/wllama.js script is initialized, below line 156 here:
https://github.com/ngxson/wllama/blob/65bbcc07c52d9105936bcd783e3e718ca93d1c5f/src/wllama.ts#L155-L157
Do you think it's doable?

Thanks for pointing that out. Yes, it should be doable.
It would be even better to have PTHREAD_POOL_SIZE to be exactly equal to nbThreads. I'll need to dive into the source code of emscripten to see if it's possible for not.

I've also read that setting threads to half of those available works better, as the thread normally can't all be fed optimally.
See: https://github.com/tangledgroup/llama-cpp-wasm/issues/1

@flatsiedatsie By default, on multi-thread build, we already take half number of available threads (hardwareConcurrency / 2).
This is also true for native version of llama.cpp, not just wllama, because nowadays CPU usually have 2 threads per 1 core, but these 2 threads share the same SIMD component.

authors: felladrin flatsiedatsie ngxson

repo: ngxson/wllama


text:
[Feature Request] Ability to get entire file's contents from templates

In my use-case, I have templates to generate a summary of an entire note, and to generate action-items from daily logs. It would be convenient for my templates to automatically reference all content in a file rather than having to select it all each time.

use the new {{content}} variable

authors: haouarihk tylermenezes

repo: nhaouari/obsidian-textgenerator-plugin


text:
Uncaught TypeError: Cannot read property '1' of null

Describe the bug
Input plain text html in the markdown editor, then click WYSIWYG to switch WYSIWYG mode. This cause the TypeError
Screenshots

@Aaron-Hu
Is there a reason to use it like this?
Using the html document itself is unlikely to be good for security.


text:
fix: Make popups absolutely positioned AND children of the toolbar (fix #151, #155)

I can't seem to be able to reopen https://github.com/nhnent/tui.editor/pull/195, this is a continuation of that PR that makes popups be children of the toolbar (I tried absolutely positioning the toolbar and both headings and table popups work correctly).
If you have any other issues with this PR, please don't close it so I can resolve them. I will try my best to see this fixed in the end :)

Thank you @jkelin
I changed some code from you.
merging it.

I noticed you made changes on the master of your repo.
Making changes on fix branch make your life easier to follow our master.
I always squash merge onto the master branch. 🥂

Awesome, thank you for very much for seeing this through.
Your suggestions are very sound, it is obvious that I don't contribute to OSS as much as I should :)

I'm looking forward to another contribution from you 😉
Have a good day @jkelin

authors: jkelin kyuwoo-choi


text:
Automatically setup package.json for Functions

Describe the solution you'd like
Automatically setup package.json when saying Y to Do you want to install Web or Front-end templates: and selecting Node. This would make it a little more obvious on the initial setup.

Users may not always want to run npm init to setup package.json. For example, during CI/CD or deployment pipelines.
We were trying to avoid launching commands on user's behalf as much as possible.

authors: jmarbutt mrinalwahal

repo: nhost/cli


text:
Error when using access token with GraphQL in Node.js environment

Describe the bug
I am using nhost-js 3.1.10 in a Node.js environment.
I want to use an existing access token with the built-in GraphQL client, but requests fail.
To Reproduce
const nhost = new NhostClient({
    subdomain: process.env.NHOST_SUBDOMAIN,
    region: process.env.NHOST_REGION,
})
nhost.graphql.setAccessToken(accessToken)

const { data, error } = await nhost.graphql.request(
    `
    mutation ($name: String!) {
        insert_dummy_things_one(
            object: {name: $name}
        ) {
           name
        }
    }
    `,
    { name: 'foo' }
  )

Error:
[
  {
    message: 'no mutations exist',
    extensions: { path: '$', code: 'validation-failed' }
  }
]

GraphQL server log mentions x-hasura-role: public which should be anonymous for the given access token:
2024-10-30 14:23:45 {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"192.168.65.1","method":"POST","status":200,"url":"/v1/graphql"},"operation":{"error":{"code":"validation-failed","error":"no mutations exist","path":"$"},"query":{"type":null},"request_id":"11df46d0-4c77-41fc-b1f8-d473483db496","request_mode":"error","response_size":68,"uncompressed_response_size":68,"user_vars":{"x-hasura-role":"public"}},"request_id":"11df46d0-4c77-41fc-b1f8-d473483db496"},"level":"error","span_id":"15c529f304d03154","timestamp":"2024-10-30T13:23:44.771+0000","trace_id":"2a3b07efed30d3fe8d87ad775d8aab07","type":"http-log"}

Expected behavior
The mutation is executed for the user who is authenticated by the given token.
Additional context

Using the same query and token via the dashboard works fine
Using the same query and token via an HTTP client works fine
nhost.storage.setAccessToken(accessToken) works fine

Hello,
thanks for th message, I am afraid I can't replicate though. This works fine (excuse the terrible js, not my cup of tea):
import { NhostClient } from '@nhost/nhost-js'

const nhost = new NhostClient({
    subdomain: 'local',
    region: 'local'
})
nhost.graphql.setAccessToken('asdasd')

async function main() {
    const signinResp = await nhost.auth.signIn({
        email: 'asd@asd.com',
        password: 'asd@asd.com'
    })

    if (signinResp.error) {
        // marshal error
        throw new Error(signinResp.error)
    }

    nhost.graphql.setAccessToken(signinResp.session.accessToken)

    const { data, error } = await nhost.graphql.request(
        `
        mutation ($name: String!) {
            insertAnimal(
                object: {name: $name}
            ) {
               name
            }
        }
        `,
        { name: 'foo3' }
    )

    console.log(data)
    console.log(error)
}

main()
    .then(() => console.log('worked'))
    .catch(err => console.error('Error:', err));

The permissions:

And running it:
$ node accesstoken.js
{ insertAnimal: { name: 'foo' } }
null
worked

Make sure the access token is valid as if it isn't valid for some reason (i.e. expired or wrong signature), hasura will just ignore it.
Regards

authors: dbarrosop stefan-girlich

repo: nhost/nhost


text:
Internal: Restructure ONS mortality data preparation workflow

Instead of multiple code sections for downloading CSV/XLS files that are then stored within the package directory, we should use functions that read in data directly from the URLs, process the data structures and bind them together without saving intermediate files to disk.
Or amend the workflow entirely to use the Nomis API.
However, the documentation for this package says that this data is for teaching purposes - I'm not sure if it's just the data itself that is used for this, or whether the data preparation process itself is part of a set of teaching materials.
I'm happy to do the work to amend the workflow for this dataset, if this issue is approved. But it would mean rewriting the current data preparation vignette as well.

I'm not sure this needs doing to be done, as you pointed out, because the original reason was to give NHS-like data for training.  The was what Zoe used to prepare it, rather than being a workflow for people to follow.  Depends on what you want to do with the package.

The vignette I wrote was to explain how I built the dataset but I'm totally in favour of a replacement of that with a reworking using the Nomis API - unless that's another API package?

Another idea @francisbarton is to write the rework but as a blog for the NHS-R website Quarto site? I think this package needs simpler examples of how to use the data but the higher level information is still incredibly useful.

authors: Lextuga007 chrismainey francisbarton

repo: nhs-r-community/NHSRdatasets


text:
🛑 Core is down

In c02e4d4, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in 3d1ca5c after 13 minutes.

repo: nhs-work/test-upptime


text:
🛑 Core is down

In 48cc61a, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in 06da6cf after 4 minutes.


text:
🛑 Core is down

In 009c216, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in 895d0f5 after 14 minutes.


text:
🛑 Core is down

In f3f48d7, Core ($CORE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Core is back up in eacff93 after 12 minutes.


text:
Check for replacement content for point 17 in service standard

Point 17 in the standards has a couple of broken links in the ‘Read more about this’ section:

NHS digital reference data registers (NHS Digital - beta)
Use of FHIR-based APIs (NHS Digital - beta)

Having looked at the NHSD site, it appears that The NHS digital, data and technology standards framework pages have been retired. You can view a version of them via The National Archives.
Broken links have been removed but do we need to replace the content?

Original content - we need to check if these resources need replacing and link to them if so.

This is a more up to date page on FHIR: https://digital.nhs.uk/services/fhir-apis.

repo: nhsuk/nhsuk-service-manual


text:
changes for axe instamine logs

please

no need to change this on the code, just use the config file

authors: GamerzRiot nicguzzo

repo: nicguzzo/deepslateinstamine


text:
Add ngrok-operator?

https://github.com/zufardhiyaulhaq/ngrok-operator

See #5231

repo: nicholasdille/docker-setup


text:
Bug Report Not related to Plaid [SearchActivity - FAB animation]

Hi Nick,
Please can you help me for an animation of your FAB in the SearchActivity activity (this problem report has nothing to do with your application, but I took an animation of your Plaid project to run the same animation on my application that I develop)
Screenshot GIF

If you agree to give me a shot I will detail my problem
As on the image GIF: I open my application and I press the floating action button, the animation runs perfectly, similarly for the return animation ... But the animation runs that once, when I press the floating action button again the animation does not run at all
Sorry for the GIF quality

Hi. Happy to take a look if you can give more details. I'll close this issue as it's not related to Plaid, but we can keep talking.

On a onclick listener I use the  TransitionManager class to make the FrameLayout visible
if (switch_list_content.getVisibility() == View.GONE)
{
    TransitionManager.beginDelayedTransition(root, getTransitionInflater().inflateTransition(R.transition.main_show_switch_list));

    switch_list_fab.setVisibility(View.INVISIBLE);
    switch_list_content.setVisibility(View.VISIBLE);
    switch_list_scrim.setVisibility(View.VISIBLE);
}

And on another onclick listener I use the TransitionManager to make the FrameLayout` disappear
if (switch_list_content.getVisibility() == View.VISIBLE)
{
    TransitionManager.beginDelayedTransition(root, getTransitionInflater().inflateTransition(R.transition.main_hide_switch_list));

    switch_list_content.setVisibility(View.GONE);
    switch_list_scrim.setVisibility(View.GONE);
    switch_list_fab.setVisibility(View.VISIBLE);
}

The animation I use is the CircularReveal of your SearchActivity activity (as in the GIF image)
When I press on my first onclick listener the CircularReveal animation runs and my FrameLayout become visible
When I press my other onclick listener the CircularReveal animation also runs and my FrameLayout disappears
But when I press again on my first onclick listener the animation does not run anymore, even though the animation no longer, the FrameLayout disappears anyway ....
The CircularReveal animation runs once, beyond that, the animation no longer executes in spite of that, the FrameLayout disappears and still appears, like this it completely ignores the animation
main.xml
<android.support.design.widget.CoordinatorLayout
...>

    <FrameLayout

        ...>
            RecyclerView
            Toolbar
    </FrameLayout>

    <FrameLayout
        ...>      <!-- View for circular reveal animation -->
    </FrameLayout>

</android.support.design.widget.CoordinatorLayout>

main_show_switch_list.xml
<?xml version="1.0" encoding="utf-8"?>
<transitionSet
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto">

    <transition
        class="com.msay2.copy_manager.transition.CircularRevealVisibility"
        app:startRadius="@dimen/fab_radius"
        android:duration="400"
        android:interpolator="@android:interpolator/fast_out_slow_in">

	<targets>
            <target android:targetId="@id/switch_list_content"/>
        </targets>
    </transition>
    <fade
        android:duration="300"
        android:interpolator="@android:interpolator/fast_out_linear_in">

	<targets>
            <target android:targetId="@id/switch_list_scrim"/>
        </targets>
    </fade>

</transitionSet>

main_hide_switch_list.xml
<?xml version="1.0" encoding="utf-8"?>
<transitionSet
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto">

    <transition
        class="com.msay2.copy_manager.transition.CircularRevealVisibility"
        app:endRadius="@dimen/fab_radius"
        android:duration="300"
        android:interpolator="@android:interpolator/fast_out_slow_in">

	<targets>
            <target android:targetId="@id/switch_list_content"/>
        </targets>
    </transition>
    <fade
        android:duration="300"
        android:interpolator="@android:interpolator/fast_out_linear_in">

	<targets>
            <target android:targetId="@id/switch_list_scrim"/>
        </targets>
    </fade>

</transitionSet>

CircularRevealVisibility.java
package com.msay2.copy_manager.transition;

import com.msay2.copy_manager.R;

import fr.yoann.dev.preferences.utils.AnimUtils;

import android.support.annotation.IdRes;
import android.support.annotation.NonNull;

import android.animation.Animator;
import android.content.Context;
import android.content.res.TypedArray;
import android.graphics.Point;
import android.transition.TransitionValues;
import android.transition.Visibility;
import android.util.AttributeSet;
import android.view.View;
import android.view.ViewAnimationUtils;
import android.view.ViewGroup;

public class CircularRevealVisibility extends Visibility
{
    private Point center;
    private float startRadius;
    private float endRadius;
    private @IdRes int centerOnId = View.NO_ID;
    private View centerOn;

    public CircularRevealVisibility()
    {
        super();
    }

    public CircularRevealVisibility(Context context, AttributeSet attrs)
    {
        super(context, attrs);

        TypedArray a = context.obtainStyledAttributes(attrs, R.styleable.CircularRevealVisibility);

	startRadius = a.getDimension(R.styleable.CircularRevealVisibility_startRadius, 0f);
        endRadius = a.getDimension(R.styleable.CircularRevealVisibility_endRadius, 0f);
        centerOnId = a.getResourceId(R.styleable.CircularRevealVisibility_centerOn, View.NO_ID);

	a.recycle();
    }

    public void setCenter(@NonNull Point center)
    {
        this.center = center;
    }

    public void centerOn(@NonNull View source)
    {
        centerOn = source;
    }

    public void setStartRadius(float startRadius)
    {
        this.startRadius = startRadius;
    }

    public void setEndRadius(float endRadius)
    {
        this.endRadius = endRadius;
    }

    @Override
    public Animator onAppear(ViewGroup sceneRoot, View view, TransitionValues startValues, TransitionValues endValues)
    {
        if (view == null || view.getHeight() == 0 || view.getWidth() == 0)
	{
		return null;
	}
        ensureCenterPoint(sceneRoot, view);
        return new AnimUtils.NoPauseAnimator(ViewAnimationUtils.createCircularReveal(view, center.x, center.y, startRadius, getFullyRevealedRadius(view)));
    }

    @Override
    public Animator onDisappear(ViewGroup sceneRoot, View view, TransitionValues startValues, TransitionValues endValues)
    {
        if (view == null || view.getHeight() == 0 || view.getWidth() == 0)
	{
		return null;
	}
        ensureCenterPoint(sceneRoot, view);
        return new AnimUtils.NoPauseAnimator(ViewAnimationUtils.createCircularReveal(view, center.x, center.y, getFullyRevealedRadius(view), endRadius));
    }

    private void ensureCenterPoint(ViewGroup sceneRoot, View view)
    {
        if (center != null)
	{
		return;
	}
        if (centerOn != null || centerOnId != View.NO_ID)
	{
            View source;
            if (centerOn != null)
	    {
                source = centerOn;
            }
	    else
	    {
                source = sceneRoot.findViewById(centerOnId);
            }
            if (source != null)
	    {
                int[] loc = new int[2];
                source.getLocationInWindow(loc);

                int srcX = loc[0] + (source.getWidth() / 2);
                int srcY = loc[1] + (source.getHeight() / 2);

		view.getLocationInWindow(loc);
                center = new Point(srcX - loc[0], srcY - loc[1]);
            }
        }
        if (center == null)
	{
            center = new Point(Math.round(view.getPivotX()), Math.round(view.getPivotY()));
        }
    }

    private float getFullyRevealedRadius(@NonNull View view)
    {
        return (float)Math.hypot(Math.max(center.x, view.getWidth() - center.x), Math.max(center.y, view.getHeight() - center.y));
    }
}

Try adding a breakpoint in onAppear and onDisappear. Are they being called? Are they creating the reveal animation?

So, yes, the onAppear and onDisappear methods are called ...
The circular animation is created because I get some data, center, centerOn, startRadius ... and more.
i debbug my application with a debbuger on Android smartphone
I modified my XML file of animation of enter
main_show_switch_list.xml
<?xml version="1.0" encoding="utf-8"?>
<transitionSet
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto">

    <transition
        class="com.msay2.copy_manager.transition.CircularRevealVisibility"
        app:startRadius="@dimen/fab_radius"
        android:duration="400"
        android:interpolator="@android:interpolator/fast_out_slow_in">

	<targets>
            <target android:targetId="@id/switch_list_content"/>
        </targets>
    </transition>
    <transitionSet
        android:interpolator="@android:interpolator/linear_out_slow_in">

        <targets>
            <target android:targetId="@id/switch_list_scrim"/>
        </targets>

        <fade android:duration="500"/>

        <transition
            class="com.msay2.copy_manager.transition.CircularRevealVisibility"
            app:centerOn="@id/switch_list_fab"
            android:duration="280" />
    </transitionSet>

</transitionSet>

onAppear :
center = Point(414, 734);
centerOn = null
centerOnId = value of my Floating Action Burton id
startRadius = 0.0
endRadius = 0.0
onDisappear :
center = Point(336, 366);
centerOn = null
centerOnId = -1
startRadius = 0.0
endRadius = 42.0

I put breakpoints everywhere to get more detailed information

repo: nickbutcher/plaid


text:
chore(deps): replace jest with vitest

Let me know if there are any concerns with this. E2E and Unit tests will not be able to be split (although all E2E tests are ignored right now). We can likely re-write the e2e tests with something like playright.

I don't want to do this just yet! Yes we need to fix e2e, and yes they should run in CI. Right now, I run them at leat locally sometimes, but I wouldn't want them to be coupled with unit tests as it would slow down normal development

I don't want to do this just yet! Yes we need to fix e2e, and yes they should run in CI. Right now, I run them at leat locally sometimes, but I wouldn't want them to be coupled with unit tests as it would slow down normal development

I agree with that. This PR can be left for awhile and I will work on implementing the e2e tests better. We can look at it again once I get some more work done on it.

@jordanshatford no rush on this. I'd like to arrive at a good architecture for our tests first before switching the whole tooling, that's a way bigger problem. Are Angular e2e tests working for you?

@jordanshatford no rush on this. I'd like to arrive at a good architecture for our tests first before switching the whole tooling, that's a way bigger problem. Are Angular e2e tests working for you?

They are not

authors: jordanshatford mrlubos


text:
[DO-NOT-MERGE] Update bindings generation to mainline

The generated bindings are now installed in include/isl/cpp.h

Note that only the last three commits are specific to this repo.
The others come from mainline.
The plan is to have the bindings be automatically generated in a separated branch.
The advantage is that it is automated.  The disadvantage is that they are only generated
off the ntv_dev branch, so changes need to be merged in this repo before the super project
can be updated to point to the right commit.
Some settings to the repo need to be changed before this commit can be merged.

repo: nicolasvasilache/isl


text:
create html and css file

https://user-images.githubusercontent.com/61630442/137597649-9faafb69-0f57-46c9-8394-83bd09833b83.mp4
@nidhisingh-1  please review and merge myPR
closes  issue #44
Thank you :)

amazing work!


text:
Add the option to hide on sidebar

This would avoid having the admin panel visible even for non-admin users, for example, and avoiding confusion if another dashboard for users alarm panel/card exists on the sidebar.
Would be great for example to have on integration page the option "open weui", like for Supervisors integrations.

Your request is implemented in the latest release (v1.8.0).
Please update Alarmo locally and check whether it works as you intended.
If so, you can close the issue. Otherwise, please let me know.
Thanks for the help 👍

@nielsfaber thank you for that, really appreciated.
Unfortunately I'm unable to see any option for the feature anywhere after the update, where should it be visible?

It’s not an option. The alarmo panel will simply be hidden for non-admin HA users.
I think this is similar to other integrations (like hacs).

Oh, Ok, understood. Yes, confirmed it's working, not visible for non-admin users

authors: nielsfaber srodighiero

repo: nielsfaber/alarmo


text:
Fix Eslint issues

Description
There are currently ESlint violations in the CI build for PRs, such as missing explicit any and unused vars,etc. We need to fix these issues
Steps to reproduce?
Run npm lint at root of the project
npm run lint

References
Sample build link: https://github.com/nightwatchjs/html-reporter/actions/runs/8119655363/job/22241267328?pr=42

hey @vaibhavsingh97 there are some types which set as any so those should be changed also ?

Hello @vaibhavsingh97 , I have looked into the issue and removed the unused vars for this error '_ctx' is defined but never used. But, what approach would be the correct fix for this warning Unexpected any. Specify a different type  :-

adding proper suitable types in place of any.
alternatively, just put unknown in place of any to bypass the warnings.

Please let me know which approach I should take? Also, will you please assign this issue to me?

Hi, I was trying to solve this issue and while I was doing that I could remove most of the linting errors except a few (2 of them intentionally because I don't have a very deep understanding of the types in this repo).
But just when I had build the project to test before opening the PR there seemed to be quite a few issues mainly with 2  files -

src/components/EnviornmentDropDown/index.tsx

src/components/Summary/utils.ts

There seems to be an issue with the interfaces for IEnvironmentDropdownData and EnvironmentData
I am open to discuss on this issue would really appreciate some suggestions before opening a PR.
Thanks!

Hello @vaibhavsingh97 i had resolved this issued of ESling fixing issue  in the new branch Ankuristic/Ankuristic:fixing_eslint_issue . please  check and merge the issue

hey @vaibhavsingh97 can I work on this??

@vaibhavsingh97 i would love to work on this issue. please assign it to me.

repo: nightwatchjs/html-reporter


text:
Unable to invoke environment variables in calling move-node-to-workspace

Describe the bug
I was trying to move node to previous focused workspace, but unfortunately, it doesn't work if it is called by hotkeys. It works when it is called in zsh. It could probably caused by parsing the command incorrectly like using ' instead of " in bash script, and so it treated the env var as a plain text.
The config is as follows:
# Send node to prev workspace
    alt-shift-tab = ['move-node-to-workspace $AEROSPACE_PREV_WORKSPACE', 'workspace $AEROSPACE_PREV_WORKSPACE']

While typing aerospace move-node-to-workspace $AEROSPACE_PREV_WORKSPACE in zsh works.

It's not a bug. TOML string is not shell. And even if it was, nobody told that those environment variables would be accessible there
Related: #278

repo: nikitabobko/AeroSpace


text:
Issues bundling large project on mac

We were glad to see 4.1.2 came out with some additional fixes focused on trying to not require the workarounds for mac. (#116, etc).
However, we are still running into the error require is not defined
Relevant section:
    files: testFiles, // about 100 files
    preprocessors: {
      'app/**/*.js': ['coverage'], // couple hundred files
      'js-tests/src-test/**/*.js': ['browserify'] // couple hundred files
    },

A bundle delay of 2000 works for me on my computer with this project, however one of my colleagues needs a bundle delay of 4500 before it starts working.
For both of us, this fix still seems to work: https://github.com/TheSavior/karma-browserify/pull/1 without specifying a bundle delay at all.
We don't want to be using a forked repo to solve this problem, and I understand that this fix can cause some confusing error messages in a few states.
I don't think further increasing the bundle delay is the right solution since it is inherently flaky and wholly dependent on the size of the project. Is there any way to add a bit more logic to the fix in the PR such that it won't hide easier to understand error messages, but will improve the behavior for waiting for files?

Out of curiosity, are you and/or your colleague using an SSD? We should fix this issue at the root but I am interested to know why the symptoms vary so considerably.

I'm on a 15" Macbook Pro, he is on a 13" Macbook Pro, both with SSDs.

Bizarre. No idea why the discrepancy would be so huge with similar hardware.

A colleague of mine had the bundle delay fixes event though he was using an SSD, too. His problems are fixed though with the latest version of karma-browserify.
We are working on a code base with 104+ (lib) and 74+ (test) files respectively without problems.
The only thing I can think of is some sort of interaction between the coverage preprocessor and karma-browserify. Try to switch to browserify-istanbul and see if it resolves your issues.

We've turned off coverage completely to no change. :-(

Too bad that did not do the trick. Unfortunately I see no way we can reproduce this issue.
Feel free to reopen your bug if you set up an example project that shows the expected behavior. In the mean time, you'd need to rely on your fork.

authors: TheSavior bendrucker nikku

repo: nikku/karma-browserify


text:
ios15系统下，似乎不支持中文

在ios15版本，如果元素中有中文，会导致生成图片的时间非常慢，并且生成的图片不会显示所有中文，并且img图片也会丢失
in iOS15

确定了！！  如果dom中有中文，在iOS15系统下， 将导致无法渲染文字和图片！！！！

这个BUG排斥了我6个小时， 一次偶然的情况下，我把标签中的中文全部删掉缓存了一串11111111，就正常渲染了

The CI with iOS 15 simulator renders chinese just fine https://html2canvas.hertzen.com/tests/?browser=Safari_IOS_15&test=/tests/reftests/text/lang/chinese.html, could you please provide a repro of where it doesn't work.

我也遇到这个问题，有中文直接会自动刷新页面

authors: H-Sven niklasvh tianlei1990


text:
Update index.html

Description
Added a new h1 tag
Additional Context

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

authors: nikohoffren tmsagarofficial

repo: nikohoffren/fork-commit-merge


text:
The admin should be able to de-activate an existing user in their organization so that when people leave they can be removed from seeing senstive financial data

Acceptance Criteria:

[x] Should have a button in the Admin panel in front of all users that de-activates them
[ ] Should not be able to de-activate themselves
[x] Should show a confirmation screen before de-activating the user to avoid accidental clicks
[ ] Should allow de-activated users to be re-activated
[x] Should not remove the user from the system and should merely soft-delete / mark them as inactive

Could you please assign this issue to me? Thanks!

@kitallis @dvenkatr I had added the soft-delete functionality. There's a trash-can icon that appears for each user which when clicked does the soft deletion for that user and removes them from the view. However, the All Users view, when loaded on its own displays this deleted user with a de-activated status.
We will either have to choose between:-
1> Only displaying active users. Removing the user on deletion would be consistent with this.
2> Displaying both active and de-activated users. In which case, we'll need to change the post-delete display show that the deleted user is displayed as de-activated and not removed.
I'm in favor of 1.
2 can be confusing for the admin. Either the admin will be interested in actions pertaining to active users or de-activated ones but not both together. Hence the UI should be task/status-specific and optimized for the more expected/usual case. Also 2 can lead to the admin mistakenly deleting an already deleted user. This won't cause problems but it's best we make the UI restricted to prevent it.
I suggest 1 with future modifications to toggle the All Users between active and de-activated with possible actions (Delete, Re-activate) appearing contextually.
1 would also address https://github.com/nilenso/kulu-backend/issues/13

@kitallis @dvenkatr Re-activation should perhaps be a separate issue and left out of scope from this?

Done with

https://github.com/nilenso/kulu-backend/pull/18
https://github.com/nilenso/kulu-website/pull/18

Also takes care of #13

@kitallis @dvenkatr I had added the soft-delete functionality. There's a trash-can icon that appears for each user which when clicked does the soft deletion for that user and removes them from the view. However, the All Users view, when loaded on its own displays this deleted user with a de-activated status.
We will either have to choose between:-
1> Only displaying active users. Removing the user on deletion would be consistent with this.
2> Displaying both active and de-activated users. In which case, we'll need to change the post-delete display show that the deleted user is displayed as de-activated and not removed.
I'm in favor of 1.
2 can be confusing for the admin. Either the admin will be interested in actions pertaining to active users or de-activated ones but not both together. Hence the UI should be task/status-specific and optimized for the more expected/usual case. Also 2 can lead to the admin mistakenly deleting an already deleted user. This won't cause problems but it's best we make the UI restricted to prevent it.
I suggest 1 with future modifications to toggle the All Users between active and de-activated with possible actions (Delete, Re-activate) appearing contextually.
1 would also address #13
If we go ahead with 1, we can remove the status from display as it becomes redundant then.

sounds like the best option to me. I also agree that re-activation can be tackled later (or not at all at the moment).

Should only admins be able to de-activate other users (and admins)? I think that should be the case. Thoughts?

@murtaza0xFF Yes, this ability should be available for only admins. Other users should not even be seeing this option.

authors: kitallis murtaza0xFF timmyjose trycatcher

repo: nilenso/kulu-backend


text:
Treat impacted parameters from downstream dependencies as triggered fixes.

Resolves #64 by treating impacted parameters by downstream dependencies as triggered fixes while processing public methods.
It also resolves issue with updating the stored impacts in downstream dependencies after each injection to prevent double counting.

@lazaroclapp This PR is ready for review. This changes made a lot of issues to avoid double counting since we are treating impacted parameters as triggered fixes. It also includes a refactoring to clean instantiating explorers since downstream dependency analysis is added as part of the explorers. Please let me know if you prefer to break this PR into multiple PRs. Thank you very much :)

Taking a look... not sure if I'll be able to finish my pass tonight, but for now, one thing worth pointing out is that the description for this PR seems incomplete, at the very least this is also solving the separate issue of the shared library models directory... (I think that would be an argument for it to be split into multiple PRs, each addressing a different bug or feature, but I also think we are short on time, so let me take a look as is, just make sure we document what this PR is actually changing 🙂 )

Hi @lazaroclapp, thank you very much for the review, I resolved your comments and left a question. This is ready for another review. Thanks.

🚀

Thank you very much for the review, I created all the requested issue. Will land this now. 🙂

authors: lazaroclapp nimakarimipour

repo: nimakarimipour/NullAwayAnnotator


text:
[161] Setup targets with Tuist

Resolves https://github.com/nimblehq/ios-templates/issues/161
What happened

Update Tuist template to have following targets:

<ProjectName>
<ProjectName>UnitTests
<ProjectName>UITests

Insight

Add unit and UI tests example files.
We will need a script to update the folder name later. For example, update ProjectNameTests to be DemoTests

Proof Of Work

Please remove 2 directories Resources and Sources at the root directory since it empty now.

Please remove 2 directories Resources and Sources at the root directory since it is empty now.

@phongvhd93 Do you mean ProjectName/Resources and ProjectName/Sources? There are no empty Resources and Sources directories at the root directory on my local. 😅

repo: nimblehq/ios-templates


text:
Update Template test

What happened
We need to adjust the template test a bit in order to create more addons (web addons, API addons,...) in the next coming PR, also separate the job to Variant test and Template test, it's easy to understand than the current version
Insight

Update the README content, so contribute will know where to put the spec file.
Adjust the Makefile to test addons and variant

Proof Of Work
1/ The test should be passed.

2/ Readme content

@andyduong1920 It would be great to port this changes to the Github actions PR once merged 🙏

@andyduong1920 It would be great to port this changes to the Github actions PR once merged 🙏

I will forward it to Hoang as he maintains that PR :D

repo: nimblehq/rails-templates


text:
Build app for Windows

Please, build the first release for Windows system (64-bit only):

ldm-0.x.y-win.msi as a stand-alone installer for Windows (done),
ldm-0.x.y-win.zip as ready-to-run version packed to archive.

Once done, please start releasing this file type along with others in our Releases section. Thank you!

All done in release 0.2.1

authors: MadejaMaciej mrfatguy

repo: niner-games/lost-dutchman-mine


text:
feat:可否添加一个取消图片文件名显示

你当前使用的 Halo 版本
2.7.0
你当前使用的 Dream 版本
1.0.3
描述一下此特性
可否添加一个取消图片文件名显示，有时候不想显示上传文件的文件名，可否添加全局按钮进行关闭或开启
附加信息
No response

可通过自定义css实现，后续版本迭代此功能

authors: Mr-dadong nineya


text:
Canonicalize "." to "."

"." is a legal path, if the string is empty after canonicalization
return ".".

Fixes #1075

Is it good enough for your purposes to detect "." early on and return immediately in that case?
Do you have your build files in your checkout? Or do you need to glob in your build outputs directory? Why do you have a dependency on "."?

Blueprint should canonicalize paths, but I could imagine a situation where a ninja variable contains .., so a/$var would expand to a/.. and canonicalize to ., and that canonicalization can't happen in the generator.
The dependency on . is caused by support for optional directories.  Ninja is run from the top-level of the source tree (for legacy reasons), with the outputs placed in another directory.  In a simplified case, Blueprint will attempt to parse a/Blueprint, but if a/ doesn't exist it adds a dependency on . to the rule that regenerates build.ninja.  When a new file is created in . the generator re-runs to parse the newly-created file.  In practice we add an extra restat rule between the . dependency and the generator that reruns the glob that the generator cares about, if the resulting file list doesn't change the generator is not rerun.

Depending on a directory doesn't mean anything useful on Windows fwiw, but maybe Blueprint doesn't care.

Blueprint doesn't run on windows, but why wouldn't dependencies on a directory work in windows?

Maybe I misinterpreted what the dependency is for, but if a file changes in
a directory on Windows the mtime of the directory isn't necessarily
modified. So it doesn't tend to be overly useful.
On Jan 12, 2016 3:52 PM, "colincross" notifications@github.com wrote:

Blueprint doesn't run on windows, but why wouldn't dependencies on a
directory work in windows?
—
Reply to this email directly or view it on GitHub
https://github.com/ninja-build/ninja/pull/1076#issuecomment-171103187.

Actually, I can't find a reference for that now. It may have only applied
to FAT. Sorry for the non-sequitur noise.
On Jan 12, 2016 4:02 PM, "Scott Graham" sgraham@gmail.com wrote:

Maybe I misinterpreted what the dependency is for, but if a file changes
in a directory on Windows the mtime of the directory isn't necessarily
modified. So it doesn't tend to be overly useful.
On Jan 12, 2016 3:52 PM, "colincross" notifications@github.com wrote:

Blueprint doesn't run on windows, but why wouldn't dependencies on a
directory work in windows?
—
Reply to this email directly or view it on GitHub
https://github.com/ninja-build/ninja/pull/1076#issuecomment-171103187.

The behavior on linux (and hopefully the same on windows) is for the directory mtime to change if an entry is added to or removed from the directory, but not if a file in the directory is changed.

Sounds like nobody remembers why this is not allowed, and it fixes a valid use-case. Let's merge this.

Oh, and thanks for the patch!

authors: colincross nico sgraham

repo: ninja-build/ninja


text:
Add tvOS platform support

Added tvOS platform support to the podspec file. Tested and works great!
This is my first contribution to github ever, so if something is missing or incorrect, please let me know!

Thanks, nice to have!

@BennetLinden: According to Podspec Syntax Reference, we should use [platform].deployment_target instead, I've already updated this on new release though. PRs always welcome. 😃

Good to know! Thanks for the update!

authors: BennetLinden ninjaprox

repo: ninjaprox/NVActivityIndicatorView


text:
[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:33:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 16957
Event details in Zabbix: http://192.168.232.99/tr_events.php?triggerid=23483&eventid=16957

Problem has been resolved in 30m 0s at 11:03:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 16957


text:
使用translucentStatusBar时，如果有标题，如何设置标题不和状态栏重叠？

是为标题设置一个顶部的padding吗

是可以这么做，记得切换的时候移除 padding 就好了。
可是我觉得你这种情况不该用这个方法。。
Sent from Mail Master
在2017年07月22日 17:24，Rain 写道： 是为标题设置一个顶部的padding吗
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/niorgai/StatusBarCompat","title":"niorgai/StatusBarCompat","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/niorgai/StatusBarCompat"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"使用translucentStatusBar时，如果有标题，如何设置标题不和状态栏重叠？ (#25)"}],"action":{"name":"View Issue","url":"https://github.com/niorgai/StatusBarCompat/issues/25"}}}

那该用什么？还是本来就处理了这种情况。
Sent from my iPhone

On 23 Jul 2017, at 1:21 PM, JQ notifications@github.com wrote:
是可以这么做，记得切换的时候移除 padding 就好了。
可是我觉得你这种情况不该用这个方法。。
Sent from Mail Master
在2017年07月22日 17:24，Rain 写道： 是为标题设置一个顶部的padding吗
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/niorgai/StatusBarCompat","title":"niorgai/StatusBarCompat","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/niorgai/StatusBarCompat"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"使用translucentStatusBar时，如果有标题，如何设置标题不和状态栏重叠？ (#25)"}],"action":{"name":"View Issue","url":"https://github.com/niorgai/StatusBarCompat/issues/25"}}}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

我在文档中写的是我提供了两种兼容模式。
着色模式是把 ContentView 填充在状态栏下面，然后状态栏单独着色。
全屏模式是把 ContentView 填充整个屏幕，包括状态栏。
我认为你该用 setStatusBarColor 方法。
Sent from Mail Master
在2017年07月23日 14:18，Rain 写道： 那该用什么？还是本来就处理了这种情况。
Sent from my iPhone

On 23 Jul 2017, at 1:21 PM, JQ notifications@github.com wrote:
是可以这么做，记得切换的时候移除 padding 就好了。
可是我觉得你这种情况不该用这个方法。。
Sent from Mail Master
在2017年07月22日 17:24，Rain 写道： 是为标题设置一个顶部的padding吗
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/niorgai/StatusBarCompat","title":"niorgai/StatusBarCompat","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/niorgai/StatusBarCompat"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"使用translucentStatusBar时，如果有标题，如何设置标题不和状态栏重叠？ (#25)"}],"action":{"name":"View Issue","url":"https://github.com/niorgai/StatusBarCompat/issues/25"}}}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/niorgai/StatusBarCompat","title":"niorgai/StatusBarCompat","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/niorgai/StatusBarCompat"}},"updates":{"snippets":[{"icon":"PERSON","message":"@WooYu in #25: 那该用什么？还是本来就处理了这种情况。\n\nSent from my iPhone\n\n\u003e On 23 Jul 2017, at 1:21 PM, JQ \u003cnotifications@github.com\u003e wrote:\n\u003e \n\u003e \n\u003e 是可以这么做，记得切换的时候移除 padding 就好了。\n\u003e 可是我觉得你这种情况不该用这个方法。。\n\u003e Sent from Mail Master\n\u003e 在2017年07月22日 17:24，Rain 写道： 是为标题设置一个顶部的padding吗\n\u003e \n\u003e —You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.\n\u003e \n\u003e \n\u003e \n\u003e \n\u003e \n\u003e \n\u003e \n\u003e \n\u003e {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/niorgai/StatusBarCompat","title":"niorgai/StatusBarCompat","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png\",\"avatar_image_url\":\"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png\",\"action\":{\"name\":\"Open in GitHub","url":"https://github.com/niorgai/StatusBarCompat\"}},\"updates\":{\"snippets\":[{\"icon\":\"DESCRIPTION\",\"message\":\"使用translucentStatusBar时，如果有标题，如何设置标题不和状态栏重叠？ (#25)"}],"action":{"name":"View Issue","url":"https://github.com/niorgai/StatusBarCompat/issues/25\"}}}\n\u003e —\n\u003e You are receiving this because you authored the thread.\n\u003e Reply to this email directly, view it on GitHub, or mute the thread.\n\u003e \n"}],"action":{"name":"View Issue","url":"https://github.com/niorgai/StatusBarCompat/issues/25#issuecomment-317232109"}}}

@WooYu 解决了吗

解决了谢谢

authors: WooYu niorgai

repo: niorgai/StatusBarCompat


text:
Open an existing xlsx file. If LastRowNum is 15, add a picture on line 16 .IPicture Resize() method locks application execution

Open an existing xlsx file. If LastRowNum is 15, add a picture on line 16 .IPicture Resize() method locks application execution
#685 #858 #425
vsersion:2.5.6
sdk:.net 6.0
os:windows 11

demo

repo: nissl-lab/npoi


text:
Version 3 configuration on Hoobs

Please note that the config using web-ui-x on hoobs is incorrect, it tries to add an accessory and not a platform.
I've configured it maually and it works great.

can it be just cache of the old plugin? have you notice any problems in the config schema?

what happen now if you remove the plugin and re-add? still uses accessory?

I deleted the plugin, restarted the homebridge service and than installed as new.
When pressing the configuration button it tries to add an accessory.
Maybe it's a cache issue. Let's see if anybody else has this.
Anyway, thanks for the amazing work you do here, as mentioned the plugin works when configured manually

I did get another similar feedback from a user... but I think it was a cache issue because it was resolved after another deletion and reboot

authors: galzil nitaybz

repo: nitaybz/homebridge-switcher-boiler


text:
nitsmell : Add code smell detection

Adding code smell detection :

Long class
Long method parameter list
Long size method
Feature envy

Adding a visitor to analyse the contents of the methods

ok to test

tests are OK (module Java & race conditions).
A final(?) review is requested.

I just saw one last change. I need to replace the mclassdef.mpropdefs by mclassdef.collect ...

Good job, ok to merge!

authors: Delja Morriar privat

repo: nitlang/nit


text:
keymaps for gg and G

Hi, nice plugin!
can you please add an example of gg and G mappings?
Thanks.

		function()
			local screen_h = vim.opt.lines:get() - vim.opt.cmdheight:get()
			local target_line = vim.api.nvim_win_get_cursor(0)[1] + screen_h / 2
			local step = screen_h / 2 / 50
			if step < 1 then
				step = 1
			end

			require("scroll").scroll(target_line, function(current_line)
				return {
					next_line = current_line + step,
					-- 10ms
					delay = 10,
				}
			end)
		end,

Code above is the example for <C-d>. You just need to specify three arguments.

target_line: where you want to go
next_line: where you are for next step
delay: time waiting for next step

For gg, just modify target_line to 0, and next_line should be smaller than the current_line, maybe you can use next_line = current_line - step.

next_line and delay could be used to control your smooth strategy.

For G, you can use vim.api.nvim_buf_line_count(0) to get buffer line cout.

authors: mosheavni niuiic


text:
kmailtransport-akonadi missing

Needed for connecting to Exchange Web Services (Microsoft-hosted e-mail systems).
This seems to be also missing from upstream nixpkgs but this should be a convenient time to add it.

Actually isn't kmailtransport it? I'm also pretty sure I've seen the Akonadi EWS resource being built.

Hmm, seems like it should Just Work unless it's broken. Will investigate later and reopen if I find something actionable.


text:
Get SO_PEERCRED working on all Linux targets

These were disabled for ARM way back in 0db6ed1a28b4fb4d408cd9b7c4dba0a79bccf1f7 and 09c00ed7d9d92db2a79baa3ed212e7e239edceb9. Try to enable them for all arches and Android as well, since the removal wasn't really explained and I see no reason why this shouldn't work.

CI passes, so I've squashed and added a changelog entry.

@berkowski @Susurrus can you comment about why these socket options were disabled?  Is there any problem with reenabling them?

They were disabled at the time to get nix passing arm-based tests.  There's been a lot of changes in the upstream libs since then so maybe a few missing symbols were added?
I don't have the knowledge to say definitively whether that flag is valid on all platforms.  I'd trust it is if libc exports it at this point.

@berkowski do you recall if the arm-based tests were failing deterministically, or intermittently?

@asomers, I don't remember specifics, sorry.  Most of my effort at that time was just getting nix (and libc) to compile under the new architectures exposed by trust.  I'd guess that I was chasing down compile-time issues rather than run-time test failings.

bors r+

authors: asomers berkowski jonas-schievink

repo: nix-rust/nix


text:
Add missing nil in the util function spec

In the sample function examples, we can pass nil to the normalize function, but this is missing from the spec.

Thanks!

authors: RodolfoSilva nkezhaya