Dashboard not updated after renaming repo

The link on the dashboard always reflects the original repository name.
Steps to reproduce:

Create new repo testproj
Rename repo to actual-proj
Check dashboard

user created repository user/testproj

which takes you to a 404
Thanks for this project. Gogs rocks! Can't wait for pull requests

Hi, thanks your feedback!

user created repository user/testproj

I don't this should be updated, because you created as user/testproj

I'm closing it with the release, feel free to reopen it if you want to continue discussion. :smiley:

I think it should be updated since you're usually using the Dashboard as some kind of quick access to get to certain things. For instance after renaming a repository I can't even click on the commit hashes anymore since it redirects you to something like: domain.com/username/oldprojectname/commit/....
It's annoying and I really don't see a single reason to not fix this. @Unknwon reopen it please.
His example is probably bad since he only showed the create notification which really should stay like this, since as you've noted since he created it as user/testproj, but for every other interaction like opening issues, pushing commits etc. the links MUST be updated or it's just a huge mess.

@kasoki I've moved your request into https://github.com/gogits/gogs/issues/1566 .


remove table event handlers in treetablesource

Fixes #_____ - Include a terse summary of the change or which issue is fixed.
Pull Request checklist:

[ ] I've named my PR in the form of "Fixes #issue. Terse description."
[ ] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[ ] My code follows the Terminal.Gui library design guidelines
[ ] I ran dotnet test before commit
[ ] I have made corresponding changes to the API documentation (using /// style comments)
[ ] My changes generate no new warnings
[ ] I have checked my code and corrected any poor grammar or misspellings
[ ] I conducted basic QA to assure all features are working

Nice, this could avoid problems reusing with multiple sources.  Thanks!


Encode static-final constant fields as Singletons

... so that when their values change, the APIs change and downstream consumers are invalidated. See #1967
There are 3 TODOs in the code currently:

We re-parse the classfile for every final field we encounter; should instead plumb through a lazy val for the parsed representation
Could skip parsing for non-static fields, since javac won't inline them
Should add a negative test, split out a JavacForUnitTests class, and move the new test to the appropriate package

Hi @stuhood,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Typesafe Contributors License Agreement:
http://www.typesafe.com/contribute/cla

Can one of the admins verify this patch?

@jsuereth, @eed3si9n : I believe this one is ready for review... would you mind taking a look?

@stuhood on it now, sorry for delay.

This LGTM.  My comments are all very minor, but usability related.   Can't wait to see more of these :)

Skimming on BART,  I'm wondering whether the compiler's ConstantType is available here? When type checking, a final val without an expected type is typed as a ConstantType that tracks its value, denoting it can be constant folded. In general, it's not safe to do this for a SingletonType. I'll have a deeper look at the latest when M2 is out.

@adriaanm We may need to add a new subclass to denote ConstantType.   you're right that may be better as an option in the future.   Shouldn't be a difficult change to make.   Let use know after M2 :)

Cleanups look great!, just waiting on @adriaanm if he has any concerns over how we've encoded the types of the constant pool

This is great stuff, thanks! I added a suggestion or two.

Thanks @adriaanm, all good points.

This needs notes as well btw.

@dwijnand , @adriaanm : I believe I've addressed your feedback. Thanks!

LGTM

Thank you! I love the template approach to testing compilation. Hypnotoad approves.


On grommet.io the "start coding" section, there playground code has a bunch of white space after the code sample

From @L0ZZI
https://github.com/grommet/grommet-docs/issues/320

@ShimiSun Turns out this is a default setting in Monaco Editor, but there's a flag to disable it which makes it so there's only as much space in the editor as there is code, and then expands as necessary. I'm opening up a PR now with the change!


Update by query

Fixes #446.  Rebased pr #453 onto master.

@gilbode ?

@lior-k - not sure what you're asking but I'm not a committer so if you're asking why this isn't merged I can't answer that

Maybe due to the "1 failing check"

@lior-k the failures have nothing to do w/ this PR, I rebased and am now getting failures that there are other PRs for.

@joschi - can you please help with this merge?

@lior-k See #538 and #540.

Thanks for merging @ferhatsb


HDDS-5312. Intermittent failure in SCM Ratis integration test

What changes were proposed in this pull request?

Mini cluster in SCM HA tests waits for two events sequentially:

SCM leader election
datanode registration, pipeline creation
The same 2 minutes timeout applies to both of these separately.

This change makes single SCM with Ratis enabled also wait for leader election, to allow for time spent to start up Ratis.  Most timeouts are observed in tests with such setup (single SCM with Ratis).

Increase frequency of pipeline creation attempts for some integration tests.

Fix BackgroundPipelineCreatorV2#stop(): the thread was always considered "not running" due to wrong condition for return value of compareAndSet (returns true if update is successful).

Guard oneShotRun value assignment in notifyEventTriggered by serviceLock, similar to other access in shouldRun.

https://issues.apache.org/jira/browse/HDDS-5312
How was this patch tested?
Regular CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/914869219
20x repetitions of affected tests:
https://github.com/adoroszlai/hadoop-ozone/runs/2764193856

Thanks @GlenGeng and @elek for the review.


403 Forbidden when Folder and File share name (e.g. hello/ and hello.html)

Hey Netlify :heart:,
Thanks for all the amazing work you do! I found a small bug with netlify dev — its behavior is inconsistent with deployed Netlify when you have a folder and file with the same name.
- Do you want to request a feature or report a bug?
Report a bug.
- What is the current behavior?
When you have a folder and a file with the same name and visit the path, you see the file contents when deployed on Netlify, but you get a 403 Forbidden error with netlify dev.
For example, let's say we have a folder hello/ and a file hello.html. When requesting /hello,

Netlify displays the contents of hello.html
netlify-dev responds with 403 Forbidden

- If the current behavior is a bug, please provide the steps to reproduce.
For netlify dev:
git clone https://github.com/FinnWoelm/netlify-same-name-for-folder-and-file
netlify dev

Visit localhost:8888/static and see 403 Forbidden.

For deployed Netlify:
Visit https://same-name-for-folder-and-file.netlify.app/hello and see contents of hello.html

- What is the expected behavior?
netlify dev should match the behavior of deployed Netlify and display the contents of hello.html.
- Local Environment Information
────────────────────┐
 Environment Info   │
────────────────────┘

  System:
    OS: Linux 5.4 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
  Binaries:
    Node: 12.14.1 - ~/.nvm/versions/node/v12.14.1/bin/node
    npm: 6.13.7 - ~/.nvm/versions/node/v12.14.1/bin/npm
  Browsers:
    Firefox: 78.0.2
  npmGlobalPackages:
    netlify-cli: 2.58.0

netlify-cli/2.58.0 linux-x64 node-v12.14.1

How to Fix:
The issue, I believe, is that static-server (used by netlify-cli) responds with 403 Forbidden when requesting a path that matches a directory. The solution is to make a small change in https://github.com/netlify/cli/blob/932022588ea85a83ba94f5b755a9a1ea052bab93/src/commands/dev/index.js#L130
Replace
if (proxyRes.statusCode === 404) {

with
if (proxyRes.statusCode === 404 || proxyRes.statusCode === 403) {

I've already tried this locally and it fixes the problem. What do you think about this solution?
Let me know if I can help or provide any more information!
Thanks for all your amazing work :raised_hands:
Finn

I just wanted to follow up on this :) Let me know if I can provide any more information or if there is anything else I can do. ✨

Will it be helpful if I make a PR for this change?
It should require only a single change in https://github.com/netlify/cli/blob/932022588ea85a83ba94f5b755a9a1ea052bab93/src/commands/dev/index.js#L130
Replace
if (proxyRes.statusCode === 404) {

with
if (proxyRes.statusCode === 404 || proxyRes.statusCode === 403) {

Sorry for the late follow @FinnWoelm. A PR would be great.
You can see our contribution guidelines here:
https://github.com/netlify/cli/blob/master/CONTRIBUTING.md

No worries! I just created the PR :) Let me know if there's something I should improve!


Delete Bolt DB file upon error by opening

Coverage remained the same at 76.178% when pulling 627c03fa02db70e152281f3da5d92a888c118b77 on rastislavszabo:procmgr into 415598ba0dbe2611326b77ad97ab00fa7db6f4fa on contiv:dev.


How are you going to support compatibility with dask-cuda?

At this moment dask-cuda team is not going to support pip package, only conda(https://github.com/rapidsai/dask-cuda/issues/166).
Dask and distributed version >= 2 is not compatible with dask-cuda==0.6.0(https://github.com/rapidsai/dask-cuda/issues/161). It looks compatible with dask==1.2.2 distributed==1.28.1.

It's on pip now.  :-)


Crash selecting iMessage

When I tick "iMessage Attachments" crashes with this log:

Process:               Clean Me [11386]
Path:                  /Volumes/VOLUME/*/Clean Me.app/Contents/MacOS/Clean Me
Identifier:            com.KevinDeKoninck.Clean-Me
Responsible:           Clean Me [11386]
2   com.KevinDeKoninck.Clean-Me   	0x0000000105aab3dc $s8Clean_Me14ViewControllerC18updateSelectedSizeyyF + 13868
3   com.KevinDeKoninck.Clean-Me   	0x0000000105aa7d4a $s8Clean_Me14ViewControllerC13switchToggledyySo8ITSwitchCF + 58
4   com.KevinDeKoninck.Clean-Me   	0x0000000105aa7d8c $s8Clean_Me14ViewControllerC13switchToggledyySo8ITSwitchCFTo + 60
14  com.KevinDeKoninck.Clean-Me   	0x0000000105ab72bd main + 13
       0x105a97000 -        0x105ac7fff +com.KevinDeKoninck.Clean-Me (1.3.0 - 0) <76C62394-7615-3B57-BDA4-6986D6BAFA33> /var/folders/*/Clean Me.app/Contents/MacOS/Clean Me
       0x105b16000 -        0x105b1dff7 +org.cocoapods.ITSwitch (1.0.0 - 1) <0162A26E-71FF-3E33-BF4F-D341DA17F904> /var/folders/*/Clean Me.app/Contents/Frameworks/ITSwitch.framework/Versions/A/ITSwitch
       0x105b2f000 -        0x105b36fff +org.cocoapods.LetsMove (1.22.0 - 1) <6449B8B1-896C-332A-A96B-EBB112F9342B> /var/folders/*/Clean Me.app/Contents/Frameworks/LetsMove.framework/Versions/A/LetsMove
       0x105b48000 -        0x105b4dfff +org.cocoapods.STPrivilegedTask (1.0.1 - 1) <90B227E1-DBB1-3FB1-A6C3-BB1FE9E20A7B> /var/folders/*/Clean Me.app/Contents/Frameworks/STPrivilegedTask.framework/Versions/A/STPrivilegedTask
       0x105b5b000 -        0x105b6fff7 +libswiftAppKit.dylib (5.0.1 - 1<IP_ADDRESS>) <D4ADA7ED-045A-3188-B27B-77190B2C2AB5> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftAppKit.dylib
       0x105b96000 -        0x105f07fff +libswiftCore.dylib (5.0.1 - 1<IP_ADDRESS>) <615B6BA6-9261-3E3C-8B96-3631F82CB6ED> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftCore.dylib
       0x1061f7000 -        0x1061ffff7 +libswiftCoreData.dylib (5.0.1 - 1<IP_ADDRESS>) <5E44560F-E7E9-38A6-834E-2A074E7B8DE2> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftCoreData.dylib
       0x106215000 -        0x106218fff +libswiftCoreFoundation.dylib (5.0.1 - 1<IP_ADDRESS>) <6A3CCDE3-7D7C-3138-BA9E-450EE8050451> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftCoreFoundation.dylib
       0x106222000 -        0x106231fff +libswiftCoreGraphics.dylib (5.0.1 - 1<IP_ADDRESS>) <69604F9F-30C8-3A06-833A-ED5138863931> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftCoreGraphics.dylib
       0x106256000 -        0x10625bffb +libswiftCoreImage.dylib (5.0.1 - 1<IP_ADDRESS>) <F7DF78C4-31E2-3B26-B44E-8366203C7CFE> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftCoreImage.dylib
       0x106266000 -        0x10626dff7 +libswiftDarwin.dylib (5.0.1 - 1<IP_ADDRESS>) <5B606C8D-32D8-35F1-9C66-9768CD77D545> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftDarwin.dylib
       0x106285000 -        0x10629dff7 +libswiftDispatch.dylib (5.0.1 - 1<IP_ADDRESS>) <A6BFD858-5189-3AD6-BDCE-55B54E8A65A7> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftDispatch.dylib
       0x1062dc000 -        0x106474ff7 +libswiftFoundation.dylib (5.0.1 - 1<IP_ADDRESS>) <27879CE7-D9E8-302F-9441-90469210382E> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftFoundation.dylib
       0x1065f9000 -        0x1065fcff3 +libswiftIOKit.dylib (5.0.1 - 1<IP_ADDRESS>) <7463EAC3-0567-36E1-9265-8DC6CB27D0FE> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftIOKit.dylib
       0x106609000 -        0x106612fff +libswiftMetal.dylib (5.0.1 - 1<IP_ADDRESS>) <AC4D8124-6103-3670-BDC8-F82C8137E789> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftMetal.dylib
       0x106622000 -        0x106626ff7 +libswiftObjectiveC.dylib (5.0.1 - 1<IP_ADDRESS>) <215B8B77-2CC8-3B21-8776-3FD77FA61E26> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftObjectiveC.dylib
       0x106635000 -        0x10663bff7 +libswiftQuartzCore.dylib (5.0.1 - 1<IP_ADDRESS>) <5E7ADEA1-D57F-355A-B040-37EA7644B7C8> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftQuartzCore.dylib
       0x106644000 -        0x10666cffb +libswiftSwiftOnoneSupport.dylib (5.0.1 - 1<IP_ADDRESS>) <4967F114-F6F1-3DC2-A9A2-289B8EFA48E3> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftSwiftOnoneSupport.dylib
       0x1066a3000 -        0x1066a6fff +libswiftXPC.dylib (5.0.1 - 1<IP_ADDRESS>) <20D6FD3A-991A-3910-B591-5AFE536A463C> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftXPC.dylib
       0x1066af000 -        0x1066b6ff7 +libswiftos.dylib (5.0.1 - 1<IP_ADDRESS>) <2D505BB9-864A-3ADE-B301-65169DC47AD0> /var/folders/*/Clean Me.app/Contents/Frameworks/libswiftos.dylib

Maybe is because I've never opened iMessage, and there is no valid path. If this is the case a sanitation before creating the queue should work.

Just ticking it should be a problem, so I'll have to check this one. Thanks for reporting!

I can't really reproduce it, but checking the switch doesn't check the system, it only updates the selected sizes... I'll update the binary soon, can you test it if it still happens?

Sorry mate, I unmacOS myselft, the company is in full dystopian mode now.
unix [~] $ uname -a
Linux tux 4.15.0-30deepin-generic #31 SMP Fri Nov 30 04:29:02 UTC 2018 x86_64 GNU/Linux

Hi @nodefive, @franck-nadeau
First of all, Sorry for my delayed response. I made this app when I was following a course on iOS programming (>3yrs ago), but my main job turned out to be a linux system engineer focussed on containerised deployments in the cloud. So I lost touch with Swift and iOS/macOS app development... Usually I don't have any time (or i don't feel like it) to smash some bugs in the code 😟
I'll try to be more responsive in the future.
You can find the latest changes here: https://github.com/Kevin-De-Koninck/Clean-Me/releases/tag/v1.4.0
I'll close this issue for now and I'll reopen if the issue still exists.
Again, sorry for the delayed response.
Kevin

as soon as https://github.com/Homebrew/homebrew-cask/pull/83128 closes, brew cask will have the correct version


fix issue 14605 - RefAppender fails isOutputRange

https://issues.dlang.org/show_bug.cgi?id=14605

@aG0aep6G any news?

@aG0aep6G any news?

Opened alternative PR #3497 which makes std.traits.hasMember forward to __traits(hasMember, ...).

@aG0aep6G should probably close this - alternative fix was pulled


Exception should be thrown in registerNativeAdFactory:factoryId:nativeAdFactory:

At https://github.com/googleads/googleads-mobile-flutter/blob/main/packages/google_mobile_ads/ios/Classes/FLTGoogleMobileAdsPlugin.m#L168-L170, the exception is just created, but not thrown; I suspect it should be, much like https://github.com/googleads/googleads-mobile-flutter/blob/main/packages/google_mobile_ads/ios/Classes/FLTAdInstanceManager_Internal.m#L249-L251 ✌🏻

@msbit Thanks for reporting this. Labeling the issue for further insights.

We’re closing this issue due to inactivity. If you’re still impacted, please create a new issue via the Developer Forum.


Remove "namedColor" duplicates that Xcode generates sometimes

Sometimes when assigning a Named Color inside the storyboard, Xcode adds a duplicated entry for the same namedColor in the storyboard's xml. This can be easily seen, even without using this tool, just start assigning the same Named Color to different places, and you should see the duplicated entry in the xml.
If you re-open the interface builder, Xcode should display a warning about that and then it will remove the duplicated entry. I found an open radar for that: https://openradar.appspot.com/35172913
If we run SwiftColorGen, it will not remove the duplicated entry and when the Interface Builder reloads, the user will have the false impression, the tool introduced an error.
Considering that, a enhancement can be made:
Everytime SwiftGen runs, it should ensure there's no duplicates in the namedColor keys in the storyboard xml's.

Moving issue to the SwiftColorGenLibrary repo


feat(cert): set the dns cache ttl for the temporary created txt record for the dns challenge

Description

Set the dns cache ttl for the temporary created txt record for the dns challenge
This uses the same value as the Kafka CNAME record TTL value which is 300 seconds
Verification Steps

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA have been completed
[ ] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer
[ ] All PR comments are resolved either by addressing them or creating follow up tasks
[ ] Required metrics/dashboards/alerts have been added (or PR created).
[ ] Required Standard Operating Procedure (SOP) is added.
[ ] JIRA has been created for changes required on the client side

Hi,
Could you expand on the motivation of this change and give some additional context around it?
Thanks

I see this PR has conflicts and there are still ongoing hardening work on certificate management service that are of higher priority than this. I'll close the PR for now.


Validation Error found Langsmith

[x] This is actually a bug report.
[ ] I am not getting good LLM Results
[ ] I have tried asking for help in the community on discord or discussions and have not received a response.
[ ] I have tried searching the documentation and have not found an answer.

What Model are you using?

[ ] gpt-3.5-turbo
[ ] gpt-4-turbo
[ ] gpt-4
[ x] Other (please specify): Azure OpenAI gpt-35-turbo-16k

Describe the bug
I'm defining a Pydantic class to structure the output of LLM evaluation. When the function asks for integers only, it works perfectly. However, when asking for an explanation string along with the integer, the function throws an error. I only see the error when looking at the traces in LangSmith.
To Reproduce
The following code works without errors:
from pydantic import BaseModel, Field

class EvaluationTest(BaseModel):
    about_the_organization: int = Field(ge=1, le=5)
    project_overview: int = Field(ge=1, le=5)
    scope_of_work: int = Field(ge=1, le=5)
    deliverables: int = Field(ge=1, le=5)
    proposal_format: int = Field(ge=1, le=5)
    rfp_issuer_scoring_method: int = Field(ge=1, le=5)

evaluation_test = client.chat.completions.create(
    model=deployment_name,
    response_model=EvaluationTest,
    messages=[
        {
            "role": "system",
            "content": """
            Evaluate the quality of the content in each section of the business proposal outline.
            For each section, provide a score from 1 to 5, where 5 is perfect.
            """,
        },
        {
            "role": "user",
            "content": f"Here is the outline: {markdown_content}"
        },
    ]
)

But this code throws an error:
from pydantic import BaseModel, Field

# Define a Pydantic model for the evaluation results
class EvaluationResult(BaseModel):
    about_the_organization: int = Field(ge=1, le=5)
    about_the_organization_rationale: str
    project_overview: int = Field(ge=1, le=5)
    project_overview_rationale: str
    scope_of_work: int = Field(ge=1, le=5)
    scope_of_work_rationale: str
    deliverables: int = Field(ge=1, le=5)
    deliverables_rationale: str
    proposal_format: int = Field(ge=1, le=5)
    proposal_format_rationale: str
    rfp_issuer_scoring_method: int = Field(ge=1, le=5)
    rfp_issuer_scoring_method_rationale: str

evaluation_results = client.chat.completions.create(
    model=deployment_name,
    response_model=EvaluationResult,
    messages=[
        {
            "role": "system",
            "content": """
            Evaluate the quality of the content in each section of the business proposal outline.
            For each section, provide a score from 1 to 5, where 5 is perfect.
            Additionally, provide a rationale for the given score.
            """,
        },
        {
            "role": "user",
            "content": f"Here is the outline: {markdown_content}"
        },
    ]
)

Expected behavior
I expected a structured output with an integer rating and a string explanation without errors.
Screenshots
Taken from Langsmith tracing

The error was resolved by improving the class structure as follows:
from pydantic import BaseModel, Field

class SectionEvaluation(BaseModel):
    score: int = Field(ge=1, le=5)
    rationale: str

class EvaluationResult(BaseModel):
    about_the_organization: SectionEvaluation
    project_overview: SectionEvaluation
    scope_of_work: SectionEvaluation
    deliverables: SectionEvaluation
    proposal_format: SectionEvaluation
    rfp_issuer_scoring_method: SectionEvaluation


not able to compile code when using zip (was able to compile using version 2.3.0)

The following code cannot be compiled in v4.0. It was compilable in version 2.3.0. I am not sure if it is intended or not.
auto ZipAndAdd(const rxcpp::observable<int> & in1, const rxcpp::observable<int> & in2) {
    return in1.zip(in2);
}

It gave errors as follows:

rx-observable.hpp(1123): error C2672: 'observable_member': no matching overloaded function found

Removing the const on the second argument declaration fixed this error.

Thanks you for the report!
this is not expected. the major version changes were due to a large change in how the operators were defined.
This should be fairly easy to fix in struct member_overload<zip_tag>. except I cannot see any obvious mistake..


Please provide Windows WHLs for jax and jaxlib

That would help all Windows users immensely.

This remains out of scope for us currently. You can read more about Windows build/installation in the installation section of the project readme and in discussion on issue #5795.

But aren't the jax devs the best ones to be able to supply wheels?  If anything it should be totally "in scope" for you guys?
Building locally for Windows has been a constant problem for myself and others on Windows.

My reason for closing this is that it is a duplicate of #5795, and it's best to track things in one place. Your feedback is useful, and it might invite more discussion. I'm mainly trying to redirect it to the right place.


Allow fully qualified typenames for scope

And add better error message when more than one match is found.

7b4353c8f55a6bdd186b6012fd044738610dfb4d


[3.8.x][fips] Jdbc -grouped - added fips profile for mysql

cherry-picked 47f9761f952181b54cdf1ac14014c2ea55548e3b
Upstream PR: https://github.com/apache/camel-quarkus/pull/6266

@JiriOndrusek if you rebase on the latest work from upstream 3.8.x it should fix the build issue.


Docker Version Dependent

While running Docker 1.7.1 I received the following error:
/app/entrypoint.sh: line 36: NGINX_PROXY_CID: unbound variable

After upgrading to 1.9.1, this was resolved.  I didn't do any research, but it might be worthwhile to note version issues in the README since jwilder/nginx-proxy does support 1.7.1.

Same for me, updating docker fixed.

Yes currently this container only work with docker 1.9.1.
I'm working on a version that will work on all docker version

Done by 6f731e4716df67d5f0138f39d7d0c756145d4ae4


What is the relationship between this project and lmfit?

I am a contributor https://github.com/lmfit/lmfit-py project, which has related functionality. I see that @newville has some commits in here, so I'm sure you're aware.
I like the idea of a lightweight library that does bounded least-squared fitting -- lmfit has many features and APIs, and it can seem a little heavy sometimes. Should we think about rebasing parts of lmfit onto this?

My take is that leastsqbound an lmfit share some functionality but have a different approaches to  library designed and intended audience.  leastsqbound tries to solve a single issue, having a limited-requirement, drop in replacement for scipy.optimize.leastsq that supports defining double or single sided bounds on the fitting parameters.  lmfit is a more complete solution to least squares fitting that is very user friendly thanks to named parameters and other niceties.  Both packages enforced the boundary condition using MINUIT style parameter transformations, or at least lmfit used to use these, I have not kept up with the packages development.
It may be possible to re-use portions of one of the packages in another but I think the overlap may be minimal.  leastsqbound is only 380 lines of code and the 2/3 of that is a copy of scipy's leastsq function.  I'm open to an collaboration or joint development if there is a plan you had in mind.
Also, should mention that @nmayorov did some GSoC work on bounded least-squares optimization in SciPy that also may be related to leastsqbound and lmfit.  The nmayorov/bounded-lsq repository gives some details.

That sounds right to me. I will close this issue -- I'm not chomping at the bit to refactor lmfit and I agree it's not clear it would be worthwhile anyway. It's just nice to have a record of the connection on github.

Hi, actually my GSoC work is already part of scipy. If you are interested take a look at the documentaiton http://scipy.github.io/devdocs/generated/scipy.optimize.least_squares.html#scipy.optimize.least_squares

@danielballan @jjhelmus @nmayorov Basically lmfit stole the MINUIT bounds (and especially how to remap that onto the covariance matrix and uncertainty estimates) from leastsqbounds.py.
Using Parameters does make lmfit slightly heavier than leastsq(), but otherwise the minimize() is pretty similar.
As for the GSOC work to add a different (and probably better) bounds implementations into scipy.optimize.leastsq(), I say GREAT!  Let's include that too!

@nmayorov That is great news.  I've very excited that a good bounded least squares has made it into SciPy, great work!  Is this had been available years ago I do not think leastsqbound would exist.  Once SciPy 0.17.0 is released I'll add a note in the readme letting users know about this feature in SciPy and recommending they use it rather than leastsqbound.


Bug report: Fails to install litecoin

Description of issue
brew cask install litecoin fails when trying to install the application. It seems like it doesn't have permissions to move the the application in place, but I can run touch /Applications/Litecoin-Qt.app just fine.
I have tried remove all my casks and reinstalling everything from scratch, doesn't seem to help.
Output of brew cask install litecoin --verbose
==> Downloading https://download.litecoin.org/litecoin-<IP_ADDRESS>/osx/litecoin-<IP_ADDRESS>-osx.dmg
Already downloaded: /Users/linus/Library/Caches/Homebrew/litecoin-<IP_ADDRESS>.dmg
==> Verifying checksum for Cask litecoin
==> Moving App 'Litecoin-Qt.app' to '/Applications/Litecoin-Qt.app'
Error: Permission denied - (/usr/local/Caskroom/litecoin/<IP_ADDRESS>/Litecoin-Qt.app, /Applications/Litecoin-Qt.app)
  Most likely, this means you have an outdated version of homebrew-cask. Please run:

      brew uninstall --force brew-cask; brew untap phinze/cask; brew update; brew cleanup; brew cask cleanup

  If this doesn’t fix the problem, please report this bug:

      https://github.com/caskroom/homebrew-cask#reporting-bugs

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:519:in `rename'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:519:in `block in mv'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1558:in `block in fu_each_src_dest'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1574:in `fu_each_src_dest0'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1556:in `fu_each_src_dest'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:508:in `mv'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:50:in `move'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:26:in `block in install_phase'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:43:in `block in each_artifact'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:42:in `each'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:42:in `each_artifact'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/artifact/moved.rb:22:in `install_phase'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/installer.rb:137:in `block in install_artifacts'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/installer.rb:134:in `each'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/installer.rb:134:in `install_artifacts'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/installer.rb:77:in `install'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli/install.rb:23:in `block in install_casks'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli/install.rb:19:in `each'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli/install.rb:19:in `install_casks'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli/install.rb:8:in `run'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli.rb:83:in `run_command'
/usr/local/Library/Taps/caskroom/homebrew-cask/lib/hbc/cli.rb:121:in `process'
/usr/local/Library/Taps/caskroom/homebrew-cask/cmd/brew-cask.rb:26:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Library/brew.rb:22:in `require?'
/usr/local/Library/brew.rb:93:in `<main>'
Error: Kernel.exit

Output of brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
    numpy

Warning: Your Xcode (7.3) is outdated
Please update to Xcode 7.3.1.
Xcode can be updated from the App Store.

Output of brew cask doctor
==> macOS Release:
10.11
==> macOS Release with Patchlevel:
10.11.4
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p648
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
Homebrew 0.9.9 (git revision cab97c; last commit 2016-06-27)
Homebrew/homebrew-core (git revision d647; last commit 2016-06-28)
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew Repository Path:
/usr/local
==> Homebrew Origin:
https://github.com/Homebrew/brew.git
==> Homebrew-cask Version:
0.60.0 (git revision f911; last commit 85 minutes ago)
==> Homebrew-cask Install Location:
<NONE>
==> Homebrew-cask Staging Location:
/usr/local/Caskroom
==> Homebrew-cask Cached Downloads:
/Users/linus/Library/Caches/Homebrew
/Users/linus/Library/Caches/Homebrew/Casks
6 files, 472.5M (warning: run "brew cask cleanup")
==> Homebrew-cask Default Tap Path:
/usr/local/Library/Taps/caskroom/homebrew-cask
==> Homebrew-cask Alternate Cask Taps:
<NONE>
==> Homebrew-cask Default Tap Cask Count:
3203
==> Contents of $LOAD_PATH:
/usr/local/Library/Taps/caskroom/homebrew-cask/lib
/usr/local/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Contents of $RUBYLIB Environment Variable:
<NONE>
==> Contents of $RUBYOPT Environment Variable:
<NONE>
==> Contents of $RUBYPATH Environment Variable:
<NONE>
==> Contents of $RBENV_VERSION Environment Variable:
<NONE>
==> Contents of $CHRUBY_VERSION Environment Variable:
<NONE>
==> Contents of $GEM_HOME Environment Variable:
<NONE>
==> Contents of $GEM_PATH Environment Variable:
<NONE>
==> Contents of $BUNDLE_PATH Environment Variable:
<NONE>
==> Contents of $PATH Environment Variable:
PATH="/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/Library/Taps/caskroom/homebrew-cask/cmd:/usr/local/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Library/ENV/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/bin/zsh"
==> Contents of Locale Environment Variables:
LC_CTYPE="UTF-8"
==> Running As Privileged User:
No

https://github.com/caskroom/homebrew-cask/issues/22335#issuecomment-228004961

@vitorgalvao As I mentioned in the bug description, I do have write access /Application and I can create files there. I also managed to install arduino and virtualbox so I think that this problem is specific to the Litecoin formula...

Cask was just updated. brew update and try again, just to make sure it wasn’t a version-specific issue.

Hmm, still not working. I don't understand this, I tried downloading it manually and I can drag and drop it in finder. I cannot however move it using mv (1), but I can create files in the applications folder (2).

➜ mv /Users/linus/Downloads/Litecoin-Qt.app /Applications/
mv: rename /Users/linus/Downloads/Litecoin-Qt.app to /Applications/Litecoin-Qt.app: Permission denied

➜ mkdir /Applications/Litecoin-Qt.app
➜ touch /Applications/Litecoin-Qt.app/test

Easy fix, bitcoin-core had the same problem. See https://github.com/caskroom/homebrew-cask/pull/22462.

Nice, thanks for the quick fix!


fix: Replaced "the the" with "the"

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Replaced what must have been a result of a bad search and replace.

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report
Patch coverage has no change and project coverage change: +31.44 :tada:

Comparison is base (c0520ee) 57.78% compared to head (c3ea46a) 89.23%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@              Coverage Diff               @@
##           release49     #910       +/-   ##
==============================================
+ Coverage      57.78%   89.23%   +31.44%
==============================================
  Files            472       14      -458
  Lines          73009     2628    -70381
  Branches        3684      350     -3334
==============================================
- Hits           42191     2345    -39846
+ Misses         30766      282    -30484
+ Partials          52        1       -51

see 458 files with indirect coverage changes

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


Trying to debug windows latest

add message for debug crash

No tests have run... strange. Will try in fork.


[Release] sdk/resourcemanager/datafactory/armdatafactory/3.0.0

https://github.com/Azure/sdk-release-request/issues/3299

The breaking change is from this PR and has been approved. @JeffreyRichter Could you help to sign off this major version release?

How do I sign this off?

How do I sign this off?

I've added a label of Approved Major Version. Could you help to review and add such label to this PR? We'll finished the release process then.


runtime: handle hitting the top of the address space in the allocator more gracefully

What version of Go are you using (go version)?

$ go version
go version go1.13.4 linux/386

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
go env
GO111MODULE=""
GOARCH="386"
GOBIN=""
GOCACHE="/builddir/.cache/go-build"
GOENV="/builddir/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="386"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/builddir/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_386"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m32 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build011990499=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Run the test suite for github.com/klauspost/compress 1.9.3.
What did you expect to see?
All tests pass.
What did you see instead?
zstd test fails with SIGSEGV.
I reported it upstream and they suggested reporting it here as well as it shouldn't segfault.

Thanks for reporting this. If I've understood the report you linked, the issue is that an OOM caused by a goroutines leak is crashing the runtime with a SIGSEV instead of showing a more graceful failure message.
The crash starts like this:

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x565db1a3]
runtime stack:
runtime.throw(0x5672f88b, 0x2a)
	/usr/lib/golang/src/runtime/panic.go:774 +0x70
runtime.sigpanic()
	/usr/lib/golang/src/runtime/signal_unix.go:378 +0x40a
runtime.(*mheap).setSpans(0x568e89c0, 0xff000000, 0x800, 0xe12c2118)
	/usr/lib/golang/src/runtime/mheap.go:1158 +0x43
runtime.(*mheap).growAddSpan(0x568e89c0, 0xff000000, 0x1000000)
	/usr/lib/golang/src/runtime/mheap.go:1311 +0xcd
runtime.(*mheap).grow(0x568e89c0, 0x800, 0xffffffff)
	/usr/lib/golang/src/runtime/mheap.go:1296 +0x6b
runtime.(*mheap).allocSpanLocked(0x568e89c0, 0x800, 0x568f9368, 0x0)
	/usr/lib/golang/src/runtime/mheap.go:1170 +0x24e
runtime.(*mheap).alloc_m(0x568e89c0, 0x800, 0x568e0101, 0x3bd57)
	/usr/lib/golang/src/runtime/mheap.go:1022 +0xed
runtime.(*mheap).alloc.func1()
	/usr/lib/golang/src/runtime/mheap.go:1093 +0x3f
runtime.(*mheap).alloc(0x568e89c0, 0x800, 0x56010101, 0x61c8e700)
	/usr/lib/golang/src/runtime/mheap.go:1092 +0x72
runtime.largeAlloc(0x1000000, 0x57b00101, 0x5)
	/usr/lib/golang/src/runtime/malloc.go:1138 +0x81
runtime.mallocgc.func1()
	/usr/lib/golang/src/runtime/malloc.go:1033 +0x3a
runtime.systemstack(0x2d673500)
	/usr/lib/golang/src/runtime/asm_386.s:399 +0x62
runtime.mstart()
	/usr/lib/golang/src/runtime/proc.go:1146
goroutine 22760 [running]:
runtime.systemstack_switch()
	/usr/lib/golang/src/runtime/asm_386.s:360 fp=0x59d98e18 sp=0x59d98e14 pc=0x5660fcc0
runtime.mallocgc(0x1000000, 0x567b7e20, 0x1, 0x565f9f25)
	/usr/lib/golang/src/runtime/malloc.go:1032 +0x6ff fp=0x59d98e6c sp=0x59d98e18 pc=0x565c264f
runtime.makeslice(0x567b7e20, 0x0, 0x1000000, 0x565f9ff5)
	/usr/lib/golang/src/runtime/slice.go:49 +0x50 fp=0x59d98e80 sp=0x59d98e6c pc=0x565f9f70
runtime.makeslice64(0x567b7e20, 0x0, 0x0, 0x1000000, 0x0, 0xf7cc036c)
	/usr/lib/golang/src/runtime/slice.go:63 +0x50 fp=0x59d98e94 sp=0x59d98e80 pc=0x565fa040
github.com/klauspost/compress/zstd.(*Decoder).DecodeAll(0x577cc050, 0x6a8043c0, 0x3b, 0x40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/builddir/build/BUILD/compress-1.9.3/_build/src/github.com/klauspost/compress/zstd/decoder.go:318 +0x346 fp=0x59d98f10 sp=0x59d98e94 pc=0x566f1ac6
github.com/klauspost/compress/zstd.TestEncoderRegression.func1.1.1(0x41abc320)
	/builddir/build/BUILD/compress-1.9.3/_build/src/github.com/klauspost/compress/zstd/encoder_test.go:224 +0x46a fp=0x59d98f9c sp=0x59d98f10 pc=0x5671fe2a
testing.tRunner(0x41abc320, 0x60a9a370)
	/usr/lib/golang/src/testing/testing.go:909 +0xae fp=0x59d98fe8 sp=0x59d98f9c pc=0x5667749e
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_386.s:1325 +0x1 fp=0x59d98fec sp=0x59d98fe8 pc=0x56611721
created by testing.(*T).Run
	/usr/lib/golang/src/testing/testing.go:960 +0x2d3
goroutine 1 [chan receive]:
testing.(*T).Run(0x57a3a320, 0x56729ce1, 0x15, 0x567e43b8, 0x301)
	/usr/lib/golang/src/testing/testing.go:961 +0x2f2
testing.runTests.func1(0x56cdc000)
	/usr/lib/golang/src/testing/testing.go:1202 +0x5b
testing.tRunner(0x56cdc000, 0x56c666dc)
	/usr/lib/golang/src/testing/testing.go:909 +0xae
testing.runTests(0x56c0e080, 0x568d0d40, 0x27, 0x27, 0x0)
	/usr/lib/golang/src/testing/testing.go:1200 +0x28b
testing.(*M).Run(0x56c8e180, 0x0)
	/usr/lib/golang/src/testing/testing.go:1117 +0x16e
main.main()
	_testmain.go:152 +0x14f
goroutine 7254 [chan receive]:
testing.(*T).Run(0x57a3a3c0, 0x567268a8, 0x7, 0x579c2700, 0x0)
	/usr/lib/golang/src/testing/testing.go:961 +0x2f2
github.com/klauspost/compress/zstd.TestEncoderRegression(0x57a3a320)
	/builddir/build/BUILD/compress-1.9.3/_build/src/github.com/klauspost/compress/zstd/encoder_test.go:170 +0x23e
testing.tRunner(0x57a3a320, 0x567e43b8)
	/usr/lib/golang/src/testing/testing.go:909 +0xae
created by testing.(*T).Run
	/usr/lib/golang/src/testing/testing.go:960 +0x2d3

and then goes on with a list of the thousands of (leaked) goroutines.
cc @aclements @mknyszek

I can reproduce on 1.13.4, with github.com/klauspost/compress at b87d2c411722993723a9de80b3510411f15ae0a8.
We get a different error with tip:
~/gopath/src/github.com/klauspost/compress$ GOARCH=386 GO111MODULE=off ~/sandbox/readonly/bin/go test -count=10 github.com/klauspost/compress/zstd
fatal error: index out of range

runtime stack:
runtime.throw(0x81eb1de, 0x12)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/panic.go:1106 +0x6a
runtime.panicCheck1(0x806b3e6, 0x81eb1de, 0x12)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/panic.go:34 +0xb9
runtime.goPanicIndexU(0x3fc, 0x3fc)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/panic.go:91 +0x37
runtime.(*pageAlloc).update(0x832b704, 0xff000000, 0x800, 0x1)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mpagealloc.go:409 +0x4b6
runtime.(*pageAlloc).grow(0x832b704, 0xff000000, 0x1000000)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mpagealloc.go:377 +0x16a
runtime.(*mheap).grow(0x832b700, 0x800, 0x0)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mheap.go:1321 +0x7f
runtime.(*mheap).allocSpan(0x832b700, 0x800, 0x100, 0x833c128, 0x8d840e0)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mheap.go:1120 +0x5df
runtime.(*mheap).alloc.func1()
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mheap.go:867 +0x4c
runtime.(*mheap).alloc(0x832b700, 0x800, 0x8c20101, 0x9577500)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/mheap.go:861 +0x63
runtime.largeAlloc(0x1000000, 0x101, 0x974c0e0)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/malloc.go:1150 +0x76
runtime.mallocgc.func1()
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/malloc.go:1045 +0x39
runtime.systemstack(0x8d840e0)
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/asm_386.s:395 +0x53
runtime.mstart()
	/usr/local/google/home/khr/sandbox/readonly/src/runtime/proc.go:1077

Slightly better, but still not great.
I can reproduce with this:
package main

type T struct {
	next *T
	buf  [1<<23 - 4]byte
}

func main() {
	var p *T
	for {
		t := &T{}
		t.next = p
		p = t
	}
}

Run with GOARCH=386 and it fails in the same way as the OP's program.
Replace 1<<23 with 1<22 and it fails correctly, giving an out of memory error.
This seems to be a regression from 1.12 to 1.13.
My gut feeling is we should just fix this at tip.
As it is a regression, backporting to 1.13 is possible, but given it just affects the failure message, it doesn't seem worth it. And the allocator has changed quite a bit, which means a whole different CL, probably.
In the other direction, we could just wait until 1.15. I guess it depends on how safe the fix is.

Tentatively milestoning as 1.14, but not release blocker.

Actually, this is somewhat nondeterministic even with my small repro. Larger sizes tend to make it fail more often, but the demarcation size is not as clear cut as I indicated previously.

From my side, I applied upstream-recommended work-around and I run the test suite with -short on x86 32-bit, which doesn't trigger the out-of-memory condition. Feel free to take your time and implement a proper fix. I wonder why it doesn't happen on ARM 32-bit, though.

@randall77, what commit was that traceback from? (mpagealloc.go:409 is a comment at current tip.)

@aclements, tip was bf3ee57d27f7542808f8a153c7b547efaba355b0

AFAICT this is the result of the runtime not handling allocations at the top of the address space well.
We're running on 32-bit platforms and the arguments to both setSpans (the failing function in the original post) and grow (the failing function at tip that @randall77 produced) are a base address of 0xff000000 and 0x800 pages which translates to 0x1000000 bytes. Adding that to the base address gives us zero with wrap-around, so it's no wonder its failing.
I think we need a bunch of overflow checking in more than one place in the runtime to fix this properly. I'm not sure why setSpans would suddenly start having problems in Go 1.13 or even Go 1.12 as that function hasn't been touched in several releases IIRC. I suspect memory behavior just changed in recent releases which is surfacing this behavior in this instance.

Ping @mknyszek

Ah thanks, nearly forgot about this. Time to play overflow whack-a-mole!

I've confirmed that the latest version of https://golang.org/cl/230719 properly crashes @randall77's program above via an "out of memory" error from the OS allocator, as opposed to a random segfault.


RNN high level API

I extracted high-level API from Chainer. It provides high-level API for cudnn's RNN.

I want to discuss some API design:

Do we need to call ascontiguousarray in APIs? (do we need to support non-contiguous arrays?)
Is it OK to expose enum values such as cudnn.CUDNN_BIDIRECTIONAL?

jenkins, test this please.

Jenkins CI test (for commit c1501c0a8845593b9c8c24c73a6e24e41b9f0962, target branch master) succeeded!

LGTM!


pull request for e2e test at 02/06/2017 05:57:50

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


sink(ticdc): add some integration tests for storage sink

What problem does this PR solve?

Issue Number: ref #8772
What is changed and how it works?
improving tests of storage sink
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/test all

/test all

/test all

/retest

/test all

/test verify

/test all

/test all

/test all

/test all

/retest

/test all

/retest

/test all

/test all

/test cdc-integration-storage-test

/test all

/test cdc-integration-storage-test

/test cdc-integration-storage-test

/test cdc-integration-storage-test

/test all

/merge

/test cdc-integration-storage-test

/merge

/test all

/test verify


Does CTAugment let each augment operation have 17 bins?

Hi,
I am learning about the details of the code, and I appreciate that you could help me with some puzzles.
I noticed that in the ctaugment.py each augment operator is registared to have 17 bins. Does this mean that the magnitude value of each operator will range from 0-17 before mapped to specific range of each augment operator ?
By the way, it seems that there are more augment operators in ctaugment than random augment(including smooth, bluring, cutout, etc), isn't it?

Hi,
Just to make sure I have not understand the code incorrectly, Could you please tell me that: did you train the fixmatch model for 1M(1024x1024) iters in total, and in each iter there are 64 labeled and 448(64x7) unlabeled training samples ?

Yes.


Windows support

Windows compilation was initially attempted in the PR of staged-recipes ( https://github.com/conda-forge/staged-recipes/pull/12863 ) but the Windows CI machine was failing in a way that neither me nor @wolfv were able to reproduce locally. Anyhow, there is currently some work in dependencies (https://github.com/conda-forge/assimp-feedstock/pull/13) and upstream (https://github.com/dartsim/dart/pull/1509, https://github.com/dartsim/dart/pull/1510, https://github.com/dartsim/dart/pull/1513) for Windows support, so it is probably better to wait for these efforts to be successful before trying to attempt to add Windows support here.

There was just a new release. Do you know if it improved things on windows?

No, it was a release out of the 6.9 branch, while all the Windows changes are happening on the master branch.

Related issues:

https://github.com/dartsim/dart/pull/1513
https://github.com/dartsim/dart/issues/1522

We have a Windows build now, thanks to @traversaro.


Dataset split fails

I've already seen this error quite a few times. It happens with moderately large to very large datasets and simply changing the train/valid/test sizes by a tiny bit fixes it
Traceback (most recent call last):
  File "/base/lib/python3.12/site-packages/metatrain/__main__.py", line 100, in main
    train_model(**args.__dict__)
  File "/base/lib/python3.12/site-packages/metatrain/cli/train.py", line 285, in train_model
    train_dataset_new, val_dataset = _train_test_random_split(
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/base/lib/python3.12/site-packages/metatrain/utils/data/dataset.py", line 476, in _train_test_random_split
    raise ValueError(
ValueError: Sum of input lengths does not equal the length of the input dataset!

Hmm might be a rounding error. Do you maybe have a example input file that you can share?

Here is an example: you first have to expand the small ethanol dataset like this:
import ase.io

structures = ase.io.read("ethanol_reduced_100.xyz", ":")
more_structures = structures * 15 + [structures[0]]
ase.io.write("ethanol_1501.xyz", more_structures)

and then run training with this options file:
seed: 42

architecture:
  name: experimental.soap_bpnn
  training:
    batch_size: 2
    num_epochs: 1

training_set:
  systems:
    read_from: ethanol_1501.xyz
    length_unit: angstrom
  targets:
    energy:
      key: energy
      unit: eV

test_set: 0.85
validation_set: 0.01

Thanks I will look into this.


Inline DatePicker?

Hi, is it possible to display the datepicker (the calendar?) inline?
I really like the look of the datepicker but I haven't figured out a way to display it inline...
Thanks!
Alfred

Currently this is not a feature or part of the design spec. It is always assumed to be a popover experience tied to an input. You can see the larger vision for the date picker here #474 and comment if you have additional use cases there to keep track of it.


MySql driver not working on dev version

Bug description
All of the database drivers seem to be missing on dev versions of grabber. At least the program doesn't seem to find them.
Steps to reproduce

install current release version
install current dev version
configure database settings
restart program
do an action that forces a write operation to the database
check either the log tab in grabber or the log file

System information

OS: Windows 7 (x64)
Grabber version: 6.0.4 (f796836)

It would seems like the libmysql.dll provided in nightly does not load properly (version <IP_ADDRESS>) while the one in normal releases loads fine (version <IP_ADDRESS>).
After some investigation, it seems like the nightly DLL is 64-bit while Grabber runs in 32-bit, so it cannot load it. I'll see to have it package the 32-bit DLL instead. :+1:

Nightly DLL:

Release DLL:


Added mower state and mower state detail translations

I have added the translations for the entities "mower state" and "mower state detail" (#228).
The translations are missing in the en.json as the states are already in english.
The translation files for fr, nl, and pl have to be changed, i have already added the lines so only the german text has to be changed.
@zmechu @urbatecte is it possible that you translate the new lines once again ?
@sander1988 not sure but have you done the nl translations in the past ?

@kimzeuner ...

@zmechu @urbatecte is it possible that you translate the new lines once again ?

Is this done / ok. Can we merge?

@sander1988 not sure but have you done the nl translations in the past ?

That's fine. I will do this after merge on the develop branch.

I don't think so as i have not heard anything since i opened the PR 😏

I don't think so as i have not heard anything since i opened the PR 😏

Ok.

@translators ...
I have just updated the text of translation connection_error ; please also update that one your native language. I have done the EN and NL texts.
Please sync with the develop branch before committing the new translations to prevent merge errors.

Hi @sander1988 !
Please find here attached the fr.json translation file.
fr.json
I think some messages may be still missing.
"Stop button have been pushed"
kind of warning message regarding the "blades wear" associated with hours count
kind of "lawn have not been lawed since long time, so it will be done two time"
Thanks for your work @sander1988
Cheers

All possible updates were merged for the PR. I have also included the sk.json from PR #244
@urbatecte Thanks for your work too, As sander1988 just updated the translation for config -> abort -> connection_error could you maybe have a look at this and update the second sentence ?
Regarding the missing messages, i think the messages that you mentioned are alerts, arent they ? Alerts schould be shown in the native language anyway so there is no need to translate them. But let me know when i`m wrong and i will take care of it.

@kimzeuner please find me updated file
fr.json
Cheers

Thanks a lot, i have added your translations ;)
@sander1988 I think i have merged all available translations.


[New] Add elevation source from tile package

Description
This PR implements Add elevation source from tile package in Scenes category.
URL to README: Add elevation source from tile package
Linked Issue(s)

swift/issues/6187

How To Test

Pan and zoom to see the scene's elevation.

Screenshots

Thank you!


exitCode not working with continueOn

Summary
What happened/what you expected to happen?
I see a bug when I use the continueOn function and the exitCode variable. It stays in the form {{tasks.task1.exitCode}} it is never replaced.
Diagnostics
What Kubernetes provider are you using?
AWS/EKS: v1.17.12-eks-7684af
What version of Argo Workflows are you running?
argo-server: v2.12.6
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: workflow-demo-
spec:
  entrypoint: workflow-demo
  arguments:
    parameters:
    - name: jobs_list
      value: '[{"id":"1"}]'

  templates:
  - name: workflow-demo
    dag:
      tasks:
      - name: processing
        template: processing
        arguments:
          parameters:
            - name: p1
              value: "{{workflow.parameters.jobs_list}}"

  - name: processing
    inputs:
      parameters:
      - name: p1
    dag:
      tasks:
      - name: processings
        template: dag-1
        arguments:
          parameters:
            - name: id
              value: "{{item.id}}"
        withParam: "{{inputs.parameters.p1}}"

  - name: dag-1
    inputs:
      parameters:
      - name: id
    dag:
      tasks:
      - name: task1
        template: fail
        continueOn:
          failed: true

      - name: failed-task1
        template: echo-exitCode-exit1
        arguments:
          parameters:
            - name: exitCode
              value: "{{tasks.task1.exitCode}}"
        dependencies: [task1]
        when: "{{tasks.task1.status}} == Failed"

      - name: succeeded-task1
        template: echo-exitCode
        arguments:
          parameters:
            - name: exitCode
              value: "{{tasks.task1.exitCode}}"
        dependencies: [task1]
        when: "{{tasks.task1.status}} == Succeeded"

      - name: end
        dependencies: [succeeded-task1,failed-task1]
        template: ok-bis
        continueOn:
          failed: true
        arguments:
          artifacts:
          - name: a1
            from: "{{tasks.task1.outputs.artifacts.a1}}"

  - name: ok-bis
    container:
      image: alpine:3.7
      command:
        - sh
        - -c
        - exit 0
    inputs:
      artifacts:
      - name: a1
        path: /etc/hostname

  - name: fail
    retryStrategy:
      limit: 1
      retryPolicy: "Always"
    container:
      image: alpine:3.7
      command:
        - sh
        - -c
        - exit 1
    outputs:
      artifacts:
      - name: a1
        path: /etc/hostname_____

  - name: echo-exitCode
    inputs:
      parameters:
      - name: exitCode
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"Exit code was: {{inputs.parameters.exitCode}}\""]

  - name: echo-exitCode-exit1
    inputs:
      parameters:
      - name: exitCode
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"Exit code was: {{inputs.parameters.exitCode}}\"; exit 1"]

I see in my job failed-task1:
Exit code was: {{tasks.task1.exitCode}}
the value is never replaced....
💡 I did two tests, when an artifact exists and when it does not. I think that when it doesn't exist the exit code is not updated?
Thanks,

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Will take a look

@clementlecorre The main issue here is that task1 in {{tasks.task1.exitCode}} is actually a RetryNode (i.e. it has a retryStrategy and can have multiple node children). So it's ambiguous to choose which of the children's exit codes to display.
If each child fails with a different exit code, how do you propose we choose one to display under the parent retry node? What would make sense for your use case? What do you think would make sense for the general use case?

I see the problem ... @simster7
I'm thinking of return the last error code from the last job I retry (by default). To have something precise in the use of argo, I think of a solution :
It would be necessary to add a new variable for example: {[tasks.task1.allExitCode}} which returns a list of int
in my case of 2 retry I would have : [137, -1]


Improve webpack build time

Hello! Can anybody explain some examples nuxt.config.js with webpack dll \ webpack refference dll \ HardSourceWebpackPlugin plugin?
"Build" for my project are boring ( 10+ minutes for admin panel

One of my nuxt website has the same problem (very long build time), so I wouldn't say no to a significative perf improvement, if it can be done someway.

Lots of new perf improvements will come which each release with both our web pack build configs and webpack itself. And will try to make more improvements when possible. BTW experimental dll support is now implemented and HardSourceWebpackPlugin is also a nice idea :)


CTV-128 - Add LOA field

Add radio buttons for user to select LOA1 or LOA2.

Please note; the form hint text is a placeholder and should be approved by a tech writer.

@karlbaker02 thanks for the feedback, all good suggestions. I have made the changes and amended the commit.

Looks good from a tech point-of-view. Will add Tom so he can take a quick look at the content / styling of the LOA, then will approve.


Bug in datetime picker

Storage Explorer Version: 1.12.0
Build Number: 20200116.10
Platform/OS: Windows 10
Architecture: x64
Regression From:  Dont' know
Bug Description
Datetime picker in Manage Access Policies window is not functioning properly. When you increment or decrement value of hour for example (via keyboard), the value of day is also changed. Sometimes, changing the value of hours, AM/PM and/or day are also changed. And finally, if I adjust 11:59 PM, I'm actually getting 10:59, at least that what is seen when I'm getting shared access signature
Steps to Reproduce

On Blob container, right mouse click, Manage Access Policies.
Add new policy
Try to adjust date and time with keyboard (up and down arrows)

Interesting, our datetime picker is the built-in datetime picker of chromium. Let me see if the bug is fixed with a higher chromium version.

Investigate in 1.14 go from there.

Fix merged into master for 1.14


NIFI-6367 - more error handling for FetchS3Object

In some circumstances FetchS3Processor will penalize the flowfile instead of failing it, and can get into a loop where it continually tries to process the flowfile and never succeeds or fails.
This simply adds some error handling checks to avoid that.

+1 merged to master.  thanks


fix using namespace for regex

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

Duplicated. See #30652


Appstudio update test-component-pac-dfaz

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-dfaz-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
29 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
39 seconds
deprecated-base-image-check

✅ Succeeded
35 seconds
sanity-inspect-image

✅ Succeeded
2 minutes
clamav-scan

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
40 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
13 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-dfaz-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
18 seconds
init

✅ Succeeded
40 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
13 seconds
sanity-inspect-image

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
59 seconds
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
17 seconds
sanity-label-check

✅ Succeeded
18 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
show-summary


fixNativeFeedbackRadius fix for  "ActionButton.Item"

Hello !
The problem is fixed for "ActionButton"
but not for "ActionButton.Item" when fixNativeFeedbackRadius={true}
Version 2.8.0
Thanks

Same issue here

Problem still here :( please merge  PR #228

same here


type-explorer is broken in coco pharma notebook environment

A change in 2.4 has broken the configuration of type explorer
... configuring the type-explorer Governance Solution View Service for this server...
...... (POST https://dev:9443/open-metadata/admin-services/users/garygeeke/servers/cocoView1/view-services/type-explorer )
...... Response:  {'class': 'VoidResponse', 'relatedHTTPCode': 400, 'exceptionClassName': 'org.odpi.openmetadata.adminservices.ffdc.exception.OMAGConfigurationErrorException', 'actionDescription': 'configureViewService', 'exceptionErrorMessage': 'OMAG-ADMIN-400-036 Unable to configure server cocoView1 since view service type-explorer is not registered in this OMAG Server Platform', 'exceptionErrorMessageId': 'OMAG-ADMIN-400-036', 'exceptionErrorMessageParameters': ['cocoView1', 'type-explorer'], 'exceptionSystemAction': "The system is unable to add this view service to the server's configuration document.", 'exceptionUserAction': 'Check that the name of the view service is correctly specified in the configuration request.  If you are not sure, issue the call to list the registered view services and verify the values you are using.  If the name is right, but the view service should be registered,then the developer of the view service needs to add this registration to the code of the view service. An view service is registered in the OMAG Server Platform by adding a description of the view service to the view service registration. Once the view service being requested is registered, retry the configuration request.'}
Suspect this is relating to the name change.
cc: @grahamwallis

Caused by #3736 I think
Let me know @grahamwallis if you want to do this or I will -- and if there are any other relevant changes? Would be good to keep this working in master. (and consider automation of the testing)

Hi @planetf1 - Yes please if you wouldn't mind investigating and correcting that would be great. I'm currently doing similar updates to Rex and it will be good to get all the view service changes in and then make sure the admin services and notebooks are all consistent.
Apart from the obvious failure in the configuration attempt above, it's worth mentioning that Tex is not a [Governance] Solution View Service - it's an IntegrationViewService. Not sure if this is just a copy/paste in the notebook, or whether it is a little deeper.

Good to clarify the type -- the current implementation was rather pressed for time to get something out, and the configuration initially was the same as a Governance Solution View service, which is why it got added to that list. I can correct.

If we have related changes to avoid breakage ideally we should include in the same PR so that we keep master good.
When do you think the rex updates will be done? And will both need the same config as dino? Can you provide a sample?

Hi. Agreed and not sure exactly when Rex changes will be good to go - currently having a few problems with node, sass and Spring. But hey! It'd be dull if everything worked first time eh? Agree that we should add notebook changes to the same PR.
All of Dino, Tex and Rex will be able to use the same resource endpoint config. Something along the following lines would be fine, albeit not as interesting as your Coco configuration:
{
"class":"IntegrationViewServiceConfig",
"viewServiceAdminClass":"org.odpi.openmetadata.viewservices.tex.admin.TexViewAdmin",
"viewServiceFullName":"Type Explorer",
"viewServiceOperationalStatus":"ENABLED",
"resourceEndpoints" : [
{
"class"              : "ResourceEndpointConfig",
"resourceCategory"   : "Platform",
"platformName"       : "Platform1",
"platformRootURL"    : "https://localhost:8082",
"description"        : "Egeria deployment on local development server"
            },
            {
                "class"              : "ResourceEndpointConfig",
                "resourceCategory"   : "Platform",
                "platformName"       : "Platform2",
                "platformRootURL"    : "https://localhost:9443",
                "description"        : "Egeria deployment on local test server"
            },
            {
                "class"              : "ResourceEndpointConfig",
                "resourceCategory"   : "Server",
                "serverName"         : "Metadata_Server",
                "serverInstanceName" : "Metadata Server 1",
                "platformName"       : "Platform1",
                "description"        : "Metadata server for development testing"
            },
            {
                "class"              : "ResourceEndpointConfig",
                "resourceCategory"   : "Server",
                "serverName"         : "Metadata_Server2",
                "serverInstanceName" : "Metadata Server 2",
                "platformName"       : "Platform2",
                "description"        : "Metadata server used as home for test artefacts"
            }
        ]
    },

The above cold be used for all 3 integration view services with suitable changes to the name of the VS in viewSewrviceAdminClass and viewServiceFullName.
Will let you know when I have rex resource endpoints working.

I've created a draft PR #3851 with the type explorer changes. So we have the option to merge soon if needed, or - ideally - hold out a day or two for rex - and I'll make those changes too
You can also cherry-pick the commit into your own change if that's easier.

@planetf1 - All of the updates to tex, rec and dino are now merged.

Thanks. I won't be able to do this for a few days - feel free to make the notebook change otherwise I will do likely end of week/monday. until then rex won't work in coco.

@grahamwallis I just checked the notebooks in master, and

rex still has the old style config with just omag server name/ URL
the admin API call passes
the start of cocoView1 fails with

                       error message is: OMAG-ADMIN-400-042 The Repository Explorer Open Metadata View Service (OMVS) has been passed an invalid configuration of ViewServiceConfig{viewServiceId=5001, viewServiceAdminClass='org.odpi.openmetadata.viewservices.rex.admin.RexViewAdmin', viewServiceName='Repository Explorer', viewServiceFullName='Repository Explorer OMVS', viewServiceURLMarker='rex', viewServiceDescription='Explore open metadata instances.', viewServiceWiki='https://egeria.odpi.org/open-metadata-implementation/view-services/rex-view/', viewServiceOperationalStatus=ENABLED, viewServiceOptions=null} in the viewServiceConfig property.

Should the configuration fail?

With a correct config body, both the config and start works correctly.

this should now be complete


Print map does not show buffer info when printed

All graphics were being removed prior to being sent to the print service.  I simply commented this line and it seems to be working now.
//printPara.map.graphics = null;


config file

I can't seem to find any config related docs or if the app even have a config file.
It would be nice to have a config file where one can change:

keybindings
exclude windows from tiling (useful to exclude apps like https://github.com/oliverschwendener/ueli)
gap and margins
bar position
bar color

I listed them from high to low in terms of priority.

Config file can be found at https://github.com/prabirshrestha/dwm-win32/blob/master/config.h.in You need to manually compile it. Instructions can be found at https://github.com/prabirshrestha/dwm-win32#compiling. Ideally we could have a github actions that allows to build and upload the assets so you don't need to setup the environment.
If you provide the alt+i output, I can exclude ueli window and set it to floating or you can add your custom rule and compile.

Config file can be found at master/config.h.in You need to manually compile it.

That's what I was afraid of, so dwm-win32 inherited this from original dwm which is understandable.

Ideally we could have a github actions that allows to build and upload the assets so you don't need to setup the environment.

yeah that can ease the pain a bit.

If you provide the alt+i output, I can exclude ueli window and set it to floating or you can add your custom rule and compile.

It is just another electron app like vscode so the class is Chrome_WidgetWin_1 and title is ueli
Thanks for the quick answer, I will close this since most of the things I mentioned already exits.


Update README.md

Readme typo error
effetcs -> effects

Description

Related issues:

Resolved #XXX

Checklist

[x] I have read CONTRIBUTING.md
[ ] I have linked all related issues above
[ ] I have rebased my branch

For bugfixes:

[ ] I have added at least one unit test to confirm the bug have been fixed
[ ] I have checked and updated TOC and API Docs when necessary

For new features:

[ ] I have added entry in TOC and API Docs
[ ] I have added a short example in API Docs to demonstrate new usage
[ ] I have added type unit tests with dts-jest
[ ] I have added runtime unit tests with dts-jest

Thanks for the fix @merturl! 👍


Why leader is rotating after every block creation in SBFT 2.3.0.

We are using Hyperledger Fabric 2.3.0 and using SBFT Consensus,
and leader is rotating after every block creation.
and we set MaxMessageCount to 10 in configtx.yaml but it is not restricting no of transactions in a block to 10. rather it is accumulating random number of transactions .
How can we configure batch size in SBFT. any suggestions.

You can disable the rotation if you don't want it.

Thanks for your answer.


Is it possible to implement router port forwarding non-80 ports

Due to special reasons, port 80 cannot be used. Can I use other ports for proxy?

You mean port 80 from the internet side ?  Port 80 is mandatory to generate Letsencrypt certificates, unless you use a DNS provider to do so.


Conflicts with lsp-mode diagnostics

Currently, if Apheleia reformats a buffer, then any Flycheck diagnostics provided by lsp-mode disappear until the next edit that causes them to be recomputed. I am not sure which package is at fault for this interaction.

This appears to be an LSP-specific problem which does not reproduce when using another, non-LSP Flycheck checker.

I can reproduce this problem without Apheleia enabled.

Reported upstream at https://github.com/emacs-lsp/lsp-mode/issues/2262.


Tracking Issue for enums

Progress

[x] Implement enum statement parsing.
[ ] Put enum type into the evaluation logic.

p.p


what CallSite ?

static  CallSite< System::Func< CallSite^, CodeContext^, System::Object^, System::Object^ >^ >^ __site_call0_4297_19;
error !!!

note that this repo is dormant.
also, this is not an actionable bug report


Brusher lag when chrome console open

Solved by creating a new option called removeStepsTime. Can only remove lag for keepCleared = true.


fix(RESTPatchAPIGuildJSONBody): system_channel_flags is optional

i swear i literally didn't notice this was also broken with my last pr, please don't hurt me
All jokes aside, totally sorry you put out a version that didn't have this fixed as well, will try to pay more attention from here on out with those PRs, lol

..To spare me time, please run npm version patch -m "chore: releaes 0.11.2", commit the result, and I'll merge 🙏


Delete hideNavBar and replaced hideNavBar with child.hideNavBar

Please refer to #1363
As I know, default value of scene property 'hideNavBar' is false.
So, I fixed two lines in a file 'Defaultrenderer.js'
Added information!

To fix a problem about 'test' and 'jest', I updated  some react packages.

I'm a few versions behind and a bit out of the loop on this project, so I could be wrong here.  But removing deepestExplicitValueForKey seems to me like it would break a lot of functionality that used to be demoed in the Example app: Go to tabbar > push new scene > and then all of the variations of hideTabBar hideNavBar that persisted through additional scenes and correctly recoiled as they were popped off.  I would just urge someone more current on the state of the project to double check this. #1330 #1363

@joenoon
I wanna help something as a person who uses this package.
what can I do for it?

@MechanicKim If I'm guessing, I think what you have is something like this:
- root hideNavBar=false
  - scene1 hideNavBar=false
  - scene2 hideNavBar=true
  - scene3 (unspecified hideNavBar)

And when you go Actions.scene3(), you notice it thinks hideNavBar == true
If that accurately describes the issue, that was how I intended hideNavBar and hideTabBar to work - they are inherited values.  The deepestExplicitValueForKey function walks the scene tree to get the inherited value when it isn't explicitly defined.  Those props are special/different than other props to get the navigation behavior in the "push new scene" demo.  I would compare it to how the ios UINavigationController behaves as you push and pop scenes while setting navigationBarHidden and hidesBottomBarWhenPushed as you go.
So I guess a few things:

Am I describing the issue right?

If so, it would not be a bug, so would better documentation resolve this? (either explicitly set hideNavBar on scenes, or at least set hideNavBar=false on any scene following a hideNavBar=true so it goes back to false).

Or is this not a behavior people want?  For my app this functionality is critical and everywhere, but I can work around it if the core library wants to remove it.

Also, I mentioned before I'm a few versions behind, so I'm kind of jogging my memory on this, and I can't vouch that this functionality hasn't been broken in the latest versions that I haven't seen yet.

First, I'm sorry. I might not know the intention of this react native package well.
To build our application, we are using this package. I just felt strange about using navigation bar.
For example, some html form tags have their default prop values. If we don't change it, they keep the default value. I have been used to this way.

@MechanicKim no need to be sorry!  What do you think about the rest?  Does my explanation solve your issue or is there still something that doesn't work for your app?

Yes! I totally understood your explanation that is so clear. ^^
No problem in our application. I just felt a little strange.
If I can contribute to this project in anyway, I hope to do it.
Thank you so much!
Have a nice day.
2016-11-25 1:28 GMT+09:00 Joe Noon<EMAIL_ADDRESS>
@MechanicKim https://github.com/MechanicKim no need to be sorry! What
do you think about the rest? Does my explanation solve your issue or is
there still something that doesn't work for your app?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aksonov/react-native-router-flux/pull/1406#issuecomment-262812686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALlkF8wg2iFLI3x1gdVPOXJtxm1usEoSks5rBbs8gaJpZM4K5JjC
.

Thank you @MechanicKim, your time is greatly appreciated.
I'll close this PR since it seems resolved, if you think it shouldn't be closed, please let me know.


Make backtest more realistic

Trading the real world comes with certain issues and the backtests should reflect it.
Add these features

Slippage (Maybe we could return the open price, but the actual price for buying is anywhere between the high and the low)
Transactions fees (1$/transaction?)

For slippage, would we set a standard slippage percentage? (for example we avergage the slippage to 25% and apply that on every tarde)
If not, how do we calculate slippage percentage?

Transaction fees : make default transaction fee to 1$ and allow backtesters to set that value to anything over 0 $
Slippage : make default slippage percent to 25% and allow backtesters to set that value to anything between 0 and 100%

slippage works, but only with strategys with DAILY resolutions since we differentiate stocks only from their symbol and not their resolutions, we need to change that before pushing this


fix: hc not work with unhealthyThreshold empty value

Issues associated with this PR
https://github.com/mosn/mosn/issues/1852
Solutions
set default value for healthchecker
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

pls merge master


Reset: draw inspiration from hacknug's

From https://gist.github.com/hacknug/53ff40d9a9c905f98de0f43e53650cb3
input, textarea, button {
    text-align: inherit;
    text-transform: inherit;
    letter-spacing: inherit;
}

small {
  font: inherit;
}

Actually small being font-size: smaller by default makes sense, just like b and strong are set to font-weight: bolder by Normalize.

It actually doesn't according to the spec:

In HTML5, this element is repurposed to represent side-comments and small print, including copyright and legal text, independent of its styled presentation.

small has a pretty specific semantic meaning and it shouldn't be used to make things smaller at all imho.

@hacknug You're right, of course :) Thank you!


https://pub.dev/packages/shadcn_ui ?

Very nice job!
Why this and not collab with that?
https://pub.dev/packages/shadcn_ui

I initially made this for my college projects, it was originally part of a smaller project but I decided to split it and make it its own library. And back then, I don't think that package has been released or maybe I wasn't aware of it, I don't know, but some of my projects already heavily depended on this, and switching to that package would take a lot of time, so I decided to continue this one instead.

This repository behaves better than that one. Keep going, good job!

cool thanks! nice you have a carousel which the other one doesn't.
hmm i'm at a crossroads here. do you plan on completing the full entire implementation?
also, any chance of something like https://www.embla-carousel.com like the js shadcn uses?

cool thanks! nice you have a carousel which the other one doesn't.
hmm i'm at a crossroads here. do you plan on completing the full entire implementation?
also, any chance of something like https://www.embla-carousel.com like the js shadcn uses?

I actually implemented the current carousel based on the embla-carousel (and shadcn UI carousel), unless I miss specific implementation/feature from embla-carousel, just let me know which one

@sunarya-thito that's great. i really like that it's extensible and has a plugin system to expand capabilities
https://www.embla-carousel.com/plugins/

@sunarya-thito that's great. i really like that it's extensible and has a plugin system to expand capabilities https://www.embla-carousel.com/plugins/ can yours use those plugins?

There won't be such thing as plugins, but what I can do is add more params and functionality to the base carousel as a built-in features


[Bug] Repeated enhancement occurs in mysql-5.x-plugin.

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
Both org.apache.skywalking.apm.plugin.jdbc.mysql.v5.define.CacheIpsInstrumentation and org.apache.skywalking.apm.plugin.jdbc.mysql.v5.define.DriverInstrumentation have enhanced the connect method of com.mysql.jdbc.Driver and com.mysql.jdbc.NonRegisteringDriver.
BTW, why do we need to enhance both com.mysql.jdbc.Driver and com.mysql.jdbc.NonRegisteringDriver? This sometimes leads to the method in interceptor being called twice.
What you expected to happen
No response
How to reproduce
No response
Anything else
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We are not sure about that, but be careful when you want to remove something, it could be a bug trigger.


Broken Link

The Device Profile Authentication Mechanism link for Non-interactive client-side example throws a 404 error.
https://azure.microsoft.com/en-us/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a0ab71a0-a2df-fa37-83fa-080dece952f6
Version Independent ID: f74b7d51-aede-ed93-437e-601654d8fa7e
Content: Get started with the REST APIs for Azure DevOps Services and Team Foundation Server - Azure DevOps Services REST API
Content Source: index.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @elbatk
Microsoft Alias: elbatk

The same page is referred to from the sample located at the device profile "sample" link, and is also broken. I raised an issue there as well:
https://github.com/microsoft/azure-devops-auth-samples/issues/71

Duplicate of #466
Thanks for reporting, we will be fixing this.


⚠ ClamAV has degraded performance

In 4ae1a0a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 381b423.


Copying Data to Test3

Anne has suggested that we should make a new copy of the live data on test3.  The existing data has been used for several years and amendments have been made that make a lot of the data rubbish.
Now that a policy has been set on UTF-8 I support Anne in this proposal. It will be very useful to have an up to date copy of the data on test3.
We will need to do a lot of testing of the data to check UTF-8 and even more in the testing of the steps involved in the development of POB searching.
This includes the csv data collection, the vld data collection  and the Gazetteer plus the prevalidation reference  data..
Geoff

Vino to speak to lemon about replacing the data in Test3 with enough, clean data for testing going forward


优化 rax-cli 创建项目选项

Close #561

Codecov Report

Merging #563 (c209aa8) into master (37eb94d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #563   +/-   ##
=======================================
  Coverage   87.80%   87.80%
=======================================
  Files          21       21
  Lines         779      779
  Branches      196      196
=======================================
  Hits          684      684
  Misses         86       86
  Partials        9        9


Use codecov.io for test coverage reports (pipeline might fail)

Hi Anders,
I added a code coverage badge from codecov.io to track test coverage.
At the moment the link in the badge points at my fork. The codecov script i added to the Azure pipeline will probably fail on this pull request, because I cannot add RaaLabs/TSIClient to my codecov account.
You can add it and setup code coverage, by following these steps:

Create an account at https://codecov.io/ (can login with GitHub)
Install the codecov GitHub integration for RaaLabs/TSIClient, https://github.com/settings/installations/7547723
No changes required to the azure-piplines.yml file, since this is generic and codecov does not need a token or secret to interact with the repo
Trigger the build pipeline again to verify it runs successful

Regards,
Rafael

Interesting, it passes :) wondering what the output of the pipeline task "upload to codecov.io" is.

Added some more stuff:

tests for getDataBy...() methods, code coverage now 79%
smarter TSIClient instantiation, constructor arguments take precedence over env variables
some clean up, remove print statements, use of enumerate and reusable function for creating the querystring


Create guide for BigQuery operators

It is not necessary. Let's do it later.

https://issues.apache.org/jira/browse/AIRFLOW-6295?jql=project %3D AIRFLOW AND component %3D documentation


Add glossary

Description

Add glossary page to napari.org > glossary.
Type of change

[v] New feature (non-breaking change which adds functionality)

References

closes #3231.

I don't think the community section of the docs is the right location for this - probably better to have it under "explanations" or "guides" instead (tbh I don't really understand the distinction between those two). Perhaps @melissawm can suggest where it should go.

Any feedback from @haesleinhuepf and @psobolewskiPhD would be appreciated too, thanks!

Gah, sorry to get to this so late! I've been swamped!
I love it! Just reading these helped me understand a lot of things better!
I'm not sure how to properly put comments like everyone else is :sad: so I'll just list a few things below:

Regarding channels: something my colleagues and students struggle with is images ("pictures") vs. data. I think I would prefer to make the connection explicit, for example:
A channel is a way to represent measured signal data as a grayscale image, where the value of each pixel represents the measured signal value. For example, in fluorescence microscopy ... . However, channels can also represent other measurement data, such as concentrations, feature height, temperature, etc. In napari ...
Regarding colormaps: this is another concept I find people struggle with, because they're focused on some perception of reality: that GFP should be in green, Texas Red in Red, etc. Of course we know his is arbitrary and the underlying data need not be color based (e.g. height data? or calcium concentration?) I'd prefer to make this explicit, maybe:
A colormap translates pixel values to a range of color intensities. For example, in fluorescence microscopy, colormaps can be selected to mirror the "color" of the collected emitted light, e.g. green for GFP. In other applications, colormaps provide a visual representation of the intensity of the measured signal.
keybinding : I would add "...that when pressed causes ...". Also, I think functions should be singular function?  Also, maybe worth adding an example? For example, command/control-c triggers "copy" in many operating systems.
labels because napari uses colors for this, I would like this to be made more explicit, for example:
Labels are a means of using unique integer pixel values to represent pixels—or their groups—that belong to unique objects, ROIs, features, classifications, etc. In napari, labels can be visualized in a labels layer: viewable objects that use different colors to represent the different integer values. This way, the different unique objects are assigned a different color.
mousebinding: functions should be singular function?
plugin: I would use that instead of which because I think the second clause ("extends ...") is a defining clause
shapes: I think this is the first time array is mentioned? Perhaps it should be part of the glossary? Either way, to me this is similar to above with labels. I would define a shape then the shapes layer, perhaps:
Shapes are a visual representation of N points in D coordinates, representing NxD arrays. Shapes can be used as a visualization tool to indicate regions of interest (ROI) or for downstream operations. In napari, the "shapes layer" is a viewable object that permits visualization of the following supported shapes: ...
widget: I'd love to extend that first sentence, for example:
... interface component that can extends the ability of the user to interact with the data, layers, or other napari functions.

Furthermore, what do you think about linking other resources from the glossary, such as the napari tutorials and wikipedia?

I am a strong +1 for this!

labels because napari uses colors for this, I would like this to be made more explicit, for example:
Labels are a means of using unique integer pixel values to represent pixels—or their groups—that belong to unique objects, ROIs, features, classifications, etc. In napari, labels can be visualized in a labels layer: viewable objects that use different colors to represent the different integer values. This way, the different unique objects are assigned a different color.

This might be a bit pedantic, but "Assigned a different color" is too strong. More accurately, the labels are assigned an integer (which is mapped to a color, using whatever the current colormap is).

@GenevieveBuckley wrote:

This might be a bit pedantic, but "Assigned a different color" is too strong. More accurately, the labels are assigned an integer (which is mapped to a color, using whatever the current colormap is).

Right, labels are integers mapped to a color. I don't think that mentioning colormaps here is correct though? As far as I can tell the colors are random—just different per label—rather than a colormap as used in the image layer.

@GenevieveBuckley could you help to review the new changes and see if there's still anything that's unclear?
@haesleinhuepf I added a few links to ImageJ reference, please let me know if they make sense.
Thanks!

For labels, I think mentioning that the napari labels layer uses different colors as it's implementation to indicate different labels would still be useful. Sure there maybe some semantics, but I think the distinction is important, because for example in ImageJ/Fiji labels are ROIs and are marked with numeric codes. This way it helps make the shuffle colors button make more sense. I didn't get this until I got what labels were and how they are implemented in napari.

I think all changes have now been made and this is good to go in! I'll merge tomorrow morning unless hearing more. Congrats on getting your first PR to napari in @chili-chiu 🚀

Will merge now! Thanks for the detailed reviews @GenevieveBuckley and making all the changes @chili-chiu 🚀

@melissawm can you make sure this page is given a spot in the new, reorganized documentation structure? Cheers


Native Animated - Add module test on Android

Add tests for the NativeAnimated module on Android. Separated this from #15919 since it caused issues internally.
Test plan
Run android unit tests

Here's the error that happens internally. Looks related to the version of mockito.
ReactAndroid/src/test/java/com/facebook/react/animated/NativeAnimatedModuleTest.java:67: error: cannot find symbol
        mUIBlocks.add(invocation.getArgumentAt(0, UIBlock.class));

@hramos Could you have someone from fb try to fix this?

Warnings

:warning:

:clipboard: Release Notes - This PR appears to be missing Release Notes.

  Generated by :no_entry_sign: dangerJS

@hramos Rebased on master, this PR was really old, might be why it didn't land.

It's failing once the diff goes through Sandcastle:
ReactAndroid/src/test/java/com/facebook/react/animated/NativeAnimatedModuleTest.java:65: error: cannot find symbol
        mUIBlocks.add(invocation.getArgumentAt(0, UIBlock.class));
                                ^
ReactAndroid/src/test/java/com/facebook/react/animated/NativeAnimatedModuleTest.java:72: error: cannot find symbol
        mUIBlocks.add(0, invocation.getArgumentAt(0, UIBlock.class));
                                   ^

@hramos  Looks like fb is using mockito@2+ and OSS was using 1+. It was updated recently in https://github.com/facebook/react-native/commit/3ea803a814f43edb3ec256dd85d778c652ca99d1#diff-5df8978d901ea853da66f065feee64ab. I simply rebased on master and updated to the test to the new api (getArgument instead of getArgumentAt). Lets see if CI passes now.


When AutoSave on, rename could do weird things because of cursor being misplaced

from tweet: https://twitter.com/ajkauffmann/status/1014166157929209856

Weird is when you have autosave on and then you type in the object name, pause for a second to think about it. The autosave will then save the file and if you have rename file on save enabled, then the file will be closed, renamed and reopened with the cursor on a different place

Maybe only rename when the object is valid? E.g. the basic structure is complete with object type, number, name and curly brackets (en optionally extends for table and page extensions)

It can be valid "while" I type as well .. ;-)

That's true... then use your imagination... you have some ;-)


Bug in he GitHub ReadME.md

In the first code snippet,  it states the filename as prettier.config.js instead of tailwindcss.config.js
**// prettier.config.js**
module.exports = {
  plugins: [require('prettier-plugin-tailwindcss')],
}

In the second code snippet, it states the property name as tailwindConfig instead of twConfig
// prettier.config.js
module.exports = {
  **tailwindConfig**: './styles/tailwind.config.js',
}

Hey! There are no mistakes here, both of those things are correct as is.

Sorry, A very rookie mistake 🙏


Write UTs

Description
With the addition of a lot of new code, there seems to be a lack in UTs.
Motivation
Get the coverage up, make code less bug prone
Change
Create a corresponding .test.tsx file, or a .test.ts file and write tests (configured already)

The goal is to have coverage in 1.31.0 > 60%

Completed via #117


Add patch for actions/checkout@v3 update

A patch for enacting the changes requested by https://github.com/adafruit/cookiecutter-adafruit-circuitpython/issues/164 but instead using the now latest v3.  Tested on a local branch in my fork of SI1145, and the build CI behaved properly.
Cookiecutter will be close behind!
Corresponding PR with diff: https://github.com/adafruit/Adafruit_CircuitPython_BME680/pull/52
.... Patch Updates Completed ....
.... Patches Applied: 309
.... Patches Skipped: 5
.... Patches Failed: 4

.... Patch Check Failure Report ....
>> Repo: Adafruit_CircuitPython_PyCamera        Patch: 24AUG2022_checkoutv3.patch
   Error: .github/workflows/release.yml: No such file or directory
>> Repo: Adafruit_CircuitPython_RTD266X_Prog    Patch: 24AUG2022_checkoutv3.patch
   Error: .github/workflows/release.yml: No such file or directory
>> Repo: Adafruit_CircuitPython_JTAG    Patch: 24AUG2022_checkoutv3.patch
   Error: .github/workflows/release.yml: No such file or directory
>> Repo: Adafruit_CircuitPython_MachXO  Patch: 24AUG2022_checkoutv3.patch
   Error: .github/workflows/release.yml: No such file or directory

Closing because this will be updated in the new composite actions instead