Exception Info: System.AggregateException: One or more errors occurred. The semaphore has been disposed.

Not sure if this is the correct place but we have been seeing this more and more since April timeframe. Not sure what other info to provide so let me know if there is anything else we can try to add. Or please point us in the right direction if possible.
Thanks!!

1026
1
0
Keywords

277402015
Application
RD0003FF2BD0FF

Application: w3wp.exe CoreCLR Version: 5.0.421.11614 .NET Version: 5.0.4 Description: The process was terminated due to an unhandled exception. Exception Info: System.AggregateException: One or more errors occurred. (The semaphore has been disposed.) ---> System.ObjectDisposedException: The semaphore has been disposed. at System.Threading.SemaphoreSlim.CheckDispose() at System.Threading.SemaphoreSlim.Release(Int32 releaseCount) at System.Threading.SemaphoreSlim.Release() at Microsoft.ApplicationInsights.SnapshotCollector.Pipeline.ProducerConsumerQueue`1.Produce(T workItem) at Microsoft.ApplicationInsights.SnapshotCollector.Uploader.EnqueueRequest(Request request) at Microsoft.ApplicationInsights.SnapshotCollector.Uploader.Shutdown() at System.Threading.CancellationToken.<>c.<.cctor>b__26_0(Object obj) at System.Threading.CancellationTokenSource.CallbackNode.<>c.b__9_0(Object s) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.CancellationTokenSource.CallbackNode.ExecuteCallback() at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException) --- End of inner exception stack trace --- at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException) at System.Threading.CancellationTokenSource.NotifyCancellation(Boolean throwOnFirstException) at System.Threading.CancellationTokenSource.Cancel() at Microsoft.ApplicationInsights.SnapshotCollector.ApplicationLifetimeManager.Stop() at Microsoft.ApplicationInsights.SnapshotCollector.AssemblyLoadContextLifetimeManager.OnUnloading(Object sender) at System.Runtime.Loader.AssemblyLoadContext.OnProcessExit() at System.AppContext.OnProcessExit()

Yup, this is a known issue that was fixed in <IP_ADDRESS>
If you're adding the SnapshotCollector via a nuget, please upgrade to that version.
If this is a "codeless" scenario in Azure App Service, we have an update in progress to upgrade everyone to <IP_ADDRESS>.

Thank you so very much!

@pharring  Sorry in opening this issue again, but do you have any estimation in when the update is going to be available in codeless scenarios? Or maybe any link to track this situation? Thank you!

It's a bit out of my hands. The bits were delivered to Azure App Service "Rapid Update" on June 14th.
I checked on it yesterday and it hadn't hit canary yet so I have pinged my contacts to ask for a status update.

I got a status update. Unfortunately, we ran into a planned deployment freeze which runs until July 1st. The roll-out is currently scheduled to begin on July 2nd. However, I note that that's a Friday before the US 4th July holiday, so I have a strong suspicion it'll be deferred again by a few days. I'll update this issue as we learn more.

Thank you @pharring for the notice! Just a side comment, It would be great to have a kind of a platform to track the versions in Azure btw 😝

July 2nd roll-out has begun and it includes the updated Snapshot Collector <IP_ADDRESS>. Historically, it has taken about 7 days to finish worldwide deployment, starting in canary regions. The 4th July US holiday may add a day or two to that. Also, there are quite a few other bits riding along with this payload, so the risk of stalls and roll-backs is somewhat higher.

@pharring thanks for your information! We will keep awaiting for the deploy :)
We are still receiving some e-mails about the crash, is there any temporary solution that you know? Thank you and sorry!

The roll-out was paused for a week because of a regression in an unrelated payload. That was patched and restarted last week. We're currently holding waiting for confirmation that the patch is good. Assuming no further hold-ups, I expect the roll-out to complete this week. I know it's frustrating -- it's frustrating for me too.
The only workaround I can think of is to disable Snapshot Debugging altogether, but that's a bit drastic.

We're seeing the exact same problem with the same call stack in a "codeless" Azure App Service scenario. Thanks for confirming it's in the Azure bits and a rollout is pending, and for keeping us updated. I'll subscribe to this issue and continue to watch for further updates on the rollout.

The roll-out has completed (Deployed on 99.55% of all App Services worldwide at time of writing).
To check that you have the latest version, go to the Kudu endpoint "/DiagnosticServices"
e.g. if your site's URL is https://mysite.azurewebsites.net, then go to https://mysite.scm.azurewebsites.net**/DiagnosticServices**
You should see something like this at the top:
Diagnostic Services Status
Site Extension, version 3.11.2106.1101, is up to date.
Application Insights Profiler WebJob, version 2.6.2010.2703, is enabled.
Application Insights Snapshot Collector, version <IP_ADDRESS>, is installed.
Screenshot below:

You may need to restart your site to pick up the latest version -- or just wait, because if you're experiencing this issue then your app has already shut down and it'll pick up the new version next time it starts.

Sadly, this update caused some apps to fail on start up (FileNotFoundException for System.Text.Encodings.Web). As a rapid mitigation, we are rolling out another update (essentially rolling back to the previous DiagnosticServices site extension). Because that version includes SnapshotCollector <IP_ADDRESS>, that means this issue will re-appear.
Obviously, we'll try and get a fix for the FileNotFoundException and SnapshotCollector <IP_ADDRESS> deployed safely as soon as we can.

This should now be fixed (again!) in DiagnosticServices 3.11.2108.201


Add Trusty platform support

This PR adds support for the Trusty secure operating system. This upstreams the patch that we have been using internally, cleaned up to meet the project's style conventions.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon.
Please see the contribution instructions for more information.

For maintenance reasons, I'd like to add target support when it's official (the official targets have target maintainers and we could ensure whether a target is still active or not). At a glance, there's no Trusty-related target on rust-lang/rust repo, could you propose adding it there first?

I've put up a PR to add the trusty compilation targets: https://github.com/rust-lang/rust/pull/103895
Is that enough to move this PR forward? Or did you want to wait until the new targets are approved in the main Rust project before merging here? Because that PR depends on the new APIs added in this PR, which compilates things 😅

I see https://github.com/rust-lang/compiler-team/issues/582 is approved and it's a good time to go ahead.
Could you check my above comment and rebase to re-run CI?

Closing as inactive, feel free to resolve the above comment and re-submit a PR if you're still interested in this change. Thanks for your contribution anyway!


Added build_script file to build images

I added a python script to build images. It takes 5 arguments: link to dockerfile github address, link to the tensorflow optimized binary address, gpu or cpu, framework version and python version. It then builds the final image.
To run this script, it requires that you have nvidia-docker installed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Awesome!
What was your reasoning for a python script instead of a bash script?

I used python because I wanted to make it configurable and was more comfortable using python for string manipulation. I also wanted to use the argparser library for parsing command line arguments and generating help messages.


Some leftover renames after BlobContent

Motivation
We renamed this in a previous PR, but some names were still incorrect
Proposal
Use blob content wherever is appropriate
Test Plan
CI

#2349  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @andresilva91 and the rest of your teammates on  Graphite


[SPARK-47578][R] Migrate RPackageUtils with variables to structured logging framework

What changes were proposed in this pull request?
Migrate logging with variables of the Spark RPackageUtils module to structured logging framework. This transforms the log* entries of APIs like this:
def logWarning(msg: => String): Unit

to
def logWarning(entry: LogEntry): Unit

Why are the changes needed?
To enhance Apache Spark's logging system by implementing structured logging.
Does this PR introduce any user-facing change?
Yes, Spark core logs will contain additional MDC
How was this patch tested?
Compiler and scala style checks, as well as code review.
Was this patch authored or co-authored using generative AI tooling?
Brief but appropriate use of GitHub copilot

cc @gengliangwang

Thanks, merging to master


Remove ic tests from skiplist

Removed ic_geometry, ic_streamlines and ic_integration from skip list.
I ran the tests in all modes on pascal  and Windows and rebaselined accordingly.
I modified the tests to turn off IntegralCurve warnings to reduce verbosity in testing output.

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have added any new baselines to the repo
[X] I have assigned reviewers

@markcmiller86 can you please review?

Apologies....it slipped off my radar. Will do later today.

I saw 58 files and thought it was more work. Most are image rebaselines and so it was pretty quick.


markdown: Fix a bug in query_and_reply.

Fixes: #17466
Testing plan:
Manual testing
GIFs or screenshots:

Thanks for working on this. I fetched the code, and played around a bit. It seems to be working fine. Could you fix the commit messages? Here's Zulip's guide: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages
One more thing - changes to tests should usually be in the same commit as the code changes, so you should probably squash the last commit.
(I don't have much exposure to the markdown processor part of the codebase yet, so I don't have any comments on the code changes right now)

I'm trying to change the commit message, but something wrong with my vim editor. It's showing Waiting for your editor to close the file... error: There was a problem with the editor '/usr/bin/vim'.. I will change the commit message once it got fixed.
I'll squash the test commit. Thanks

There something wrong with my vim. I'm trying to fix it, but it looks like it takes time. Should I create a new PR with the correct commit message?.

@100RABHpy no need to make a new PR -- with git rebase -i and force-pushes you can rewrite this PR to have the revised commits.
Check out our GitHub guide for more details.

@timabbott PR ready for review.

@100RABHpy thanks for working on this!  I posted a couple comments.  The commit message needs work, as it doesn't explain the bug or talk about how to reason about whether the decoding here is correct.
Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages

@timabbott I changed the commit message explaining the error and why decoding logic is not changed.
Also, while looking in the popovers.js file, I saw that we're replacing parenthesis with %28 and %29. But we don't need to do this because the by_conversation_and_time_uri function is calling the encodeHashComponent function, which will take care of the parenthesis.

Merged, thanks @100RABHpy!  Those added explanations were very helpful.


ER DIAGRAMS exported as graphml lose 'key' info

when I try to export an ER diagram to graphml, it works ok, except that critical information is lost.
the diagram in the native .erd format works fine, but graphml loses the primary/relation key data (bolded in the native viewer) and the dividing line between the keys and the rest of the fields.
It would be great if the graphml export reproduced more accurately what the native viewer shows.

Thanks for the idea @jeacott1

Would like to check on the status of this export to GraphML detail or if someone may have crafted a merge between the ERD and GraphML extracts to re-render the GraphML with this detail?


V13 rtl

Merge v13-rtl

Pull Request Test Coverage Report for Build 852387638

0 of 0   changed or added relevant lines in 0 files are covered.
63 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.3%) to 55.281%

Files with Coverage Reduction
New Missed Lines
%

/home/runner/frappe-bench/apps/frappe/frappe/utils/change_log.py
6
21.85%

/home/runner/frappe-bench/apps/frappe/frappe/www/app.py
12
30.77%

/home/runner/frappe-bench/apps/frappe/frappe/utils/jinja.py
14
72.06%

/home/runner/frappe-bench/apps/frappe/frappe/website/doctype/website_settings/website_settings.py
31
61.11%

Totals

Change from base Build 782459719:
0.3%

Covered Lines:
27939

Relevant Lines:
50540

💛  - Coveralls


Data check actions: don't produce duplicate components

Currently, we could add multiple duplicate components from the same actions. We should try to prune duplicate components, if possible:
# current behavior. But this might cause errors, trying to drop 'some col' multiple times
actions = [DataCheckAction(DataCheckActionCode.DROP_COL, {"columns": ['some col']}),
                  DataCheckAction(DataCheckActionCode.DROP_COL, {"columns": ['some col']})]
_make_component_list_from_actions(actions) == [DropColumns(columns=['some col']),
                                                                    DropColumns(columns=['some col'])]

# desired behavior
actions = [DataCheckAction(DataCheckActionCode.DROP_COL, {"columns": ['some col']}),
                  DataCheckAction(DataCheckActionCode.DROP_COL, {"columns": ['some col']})]
_make_component_list_from_actions(actions) == [DropColumns(columns=['some col'])] # only once

There's some support in the DataChecks class to not return duplicate actions, but if a user just used multiple DataCheck objects, we will still end up with duplicates in _make_component_list_from_actions

@angela97lin is this blocked on #1730 ?

@dsherry Nope, not necessarily--just an additional enhancement / cleanup!

This is not blocked on #1929 -- we can lump the dropped cols into one DropColumns component. However, it may make more sense if each action generates its own component, which we'd need to do #1929 for in order to put multiple DropColumns into a pipeline.


Gh/Dyn: null value alignment

Description

Fixes #491 🥳

Null values are now allowed everywhere in GH and Dyn.
Type of change

New feature (non-breaking change which adds functionality)

How has this been tested?

Manual Tests (please write what did you do?)

Tested sending nulls along with other objects to/from Grasshopper/Dynamo in all directions. Null values got properly serialised and deserialised on each program.
Also ensured that receiving in DUI connectors like Rhino/Revit did not break anything.
Docs

No updates needed as there is no reference of this anywhere in the docs.

Not sure if it should be part of this PR or not, but nulls were preventing revit params to go through, so we could do some testing there too :)

Closing! As discussed with Matteo, I'll open a new issue to track the "missing revit params" and fix it in the near future.


Upgrade container disk image

CentOS stream 8 had reached EOL [1] and it breaks our automation for
building the container disk image due to [2].
Our console package does not correctly handle Bracketed-paste [3],
disable it for now.
On CentOS stream 9 it is required to enable the rt repo in order to install a real-time kernel.
The real-time tests package name was changed.
[1] https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/
[2] https://serverfault.com/questions/1161816/mirrorlist-centos-org-no-longer-resolve
[3] https://en.wikipedia.org/wiki/Bracketed-paste

Tested against an OpenShift Virtualization v4.17 cluster.


[gui error report] Error: multiaddr "c2438ffc-3bd8-4d21-b7b6-e2c61193f3df" must start with

👉 Please describe what you were doing when this error happened.
Specifications

OS: win32 10.0.19043
IPFS Desktop Version: 0.24.0
Electron Version: 19.0.9
Chrome Version: 102.0.5005.167

Error
Error: multiaddr "c2438ffc-3bd8-4d21-b7b6-e2c61193f3df" must start with a "/"
    at new Multiaddr (C:\Users\zayan\IPFS Desktop\resources\app.asar\node_modules\multiaddr\src\index.js:54:15)
    at multiaddr (C:\Users\zayan\IPFS Desktop\resources\app.asar\node_modules\multiaddr\src\index.js:621:10)
    at parseMultiaddr (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\config.js:118:7)
    at checkPorts (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\config.js:334:23)
    at getIpfsd (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:71:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async startDaemon (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:210:17)
    at async startIpfs (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\index.js:48:17)
    at async setupDaemon (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\daemon\index.js:116:3)
    at async run (C:\Users\zayan\IPFS Desktop\resources\app.asar\src\index.js:85:5)

Thanks for submitting the issue @RedRaptor22 looks like this error generated from: https://github.com/ipfs/ipfs-desktop/blob/main/src/daemon/config.js#L334 which implies an invalid IP address was saved as config. Can you please confirm what's the IP address in your configuration? Also can you share more logs from your setup? you can find the config and log files here.


Multiple projects management

Currently it is impossible to use wskdeploy to  deploy OW assets (action, package...etc) of the same signature from different manifests having different project names. The problem is that wskdeploy overrides the "managed project" annotation. The workaround could be to use different package names, which results in assets duplication. Duplication is undesirable, because it complicates maintenance.
Introducing a feature allowing to manage OW assets by multiple projects would help to avoid it.
Suggestion:

Use different annotation key instead of "manage" for the sake of backward compatibility. E.g. managedList holding an array of managed project names.
On manifest deployment, if a deployed asset already exists in OW, check whether the manifest asset is identical to the existing one.
If not: override the existing asset with the manifest one (similar to the current functionality)
If yes: add the project specified in the manifest to the managedList.

@kpavel as discussed elsewhere... the plan would be to use URI "tags" where there is no key (each project name would be clearly part of the URI) along with domain/path to indicate that this is a "managed project" tag.

Are your projects statically dependent to each other or not? If yes, then dependencies might solve your problem by putting the common assets into a "library manifest". Otherwise can you deploy each project to their own namespace?

so for now, instead of creating annotation as a JSON value, we can have an array of JSON blob, something similar to:
    "annotations": [
        {
            "key": "managed",
            "value": [
                {
                    "k1": "v1",
                    "k2": "v2"
                },
                {
                    "k1": "v1",
                    "k2": "v2"
                }
            ]
        },

thoughts?

@pritidesai This is exactly what we had in mind. @lionelvillard The functionality we want to achieve is that there will be only one copy of an annotated asset that when updated retains connections to the projects that it is managed by. It's our understanding that creating a library asset is a possible solution, but with the current implementation, if the user updates the library asset, she will need to call wskdeply for each project that has dependency on that asset and the asset will be overwritten N times in the DB, where N is the number of projects. Having an array of annotations, as @pritidesai suggests seems to be a faster and cleaner way of achieving the result. Thoughts?

@pritidesai if we move to a nested map, as we discussed yesterday within the annotations, I would prefer that we attempt to simulate a key-only "tag" which is URI based.  Where the URI includes information regarding the project and project hash.

The idea of the explicit dependencies approach is to have only one project which include all your dependencies. Only one project needs to be deployed (and wskdeploy can compute an optimal deployment plan).
Going back to the multiple projects management issue (in which dependencies are not explicitly specified and instead managed outside of wskdeploy), here I currently think what could go wrong and things to be aware of:

if asset a in Project A and asset b in Project B have the same name but not identical (different code, parameters, etc...) then in general b cannot be deployed, otherwise it would break A.
consequently: if the purpose of B is to extends A (e.g. adding new actions to a package P), then both package descriptions P in A and B must be identical (same parameters, annotations, ...).
comparing feeds for equality required adding additional annotations to store feed parameters.
comparing APIs should probably be done by comparing swagger specifications

Bottom line:

By default, deployment should fail when assets of the same name are different. A flag could be provided to override this behavior
Asset equality must be formally defined to support the default behavior above.

@lionelvillard  I think that --override flag makes perfect sense. Also agreed that assets equality definition is required. Concerning explicit dependencies approach, assume that you have project A -> B and project C -> B, where -> means "depends on". For the sake of discussion, wskdeploy project == OW package. Furthermore, there is a an asset b in B. Now, suppose the user does wsk action update b blah-blah. How would that change propagate to  A and C? The dependencies are reflected only in the manifests of the respective projects, but nowhere in the OW data model, right? So, today the user will have to wskdeploy A and wskdeploy C. With multiple projects annotations on the asset, the user just does  wsk action update b carefree, because the dependencies of other projects on asset b are reflected in the annotations of the asset b.

@mrutkows Can you define the tag for @kpavel  and my education (you probably discussed that within the team, so sorry for asking again). Just want to make sure we're on the same page.

@davidbreitgand in this model, there is only one project:
P --> A --> B
  |-> C -->  B

then it's up to wskdeploy to factor out B. When both A and C instantiates B with the same parameters, then all is fine. Otherwise wskdeploy can reject or decide to deploy B is two different packages (when there is no dynamic bindings) or two different namespaces (wskdeploy automatically handles authentication).
As for wsk action update b, I suppose you also mean the user will then use export. In that case the expected behavior is to update the action in the manifest B. However as you said, the OW data model does not support dependencies so in order to propagate changes to A and C (like for instance if a parameter on b is defined in A) additional annotations must be added to encode such dependencies.
To be clear: I'm not against adding the managedList annotation, I'm just trying to contrast this approach with the dependencies approach. It seems to me that in order to let wskdeploy managing dependencies we will need more than the managedList annotation.

@davidbreitgand Using your example of, A -> B and project C -> B, my initial reaction is that I do not  support making any changes to project B's annotations.  As described, it seems that project B has value (as providing a library/shared asset) and should be marked public/shared by its owner (different owner than project A and project C).   From a security point of view (and existing dependency paradigms) we should never alter another person's assets even if we are only affecting their annotations.


ICU-624 Added markdown tables

A large portion of the changes for this are in the commonmark.js fork. The rest is mostly styling to render them as

... is rendered in the web app.
The only really notable thing that doesn't work quite as expected is that images inside of markdown tables are rendered as links that open the image when you click on them. This is because getting images to work inside a table is incredibly difficult
commonmark changes: https://github.com/hmhealey/commonmark.js/pull/3
commonmark-react-renderer changes: https://github.com/hmhealey/commonmark-react-renderer/commit/86fa63f898802953842526c2030f3b63c5d1ae7a
Ticket Link
https://mattermost.atlassian.net/browse/ICU-624
Checklist

Added or updated unit tests (required for all new features)
Has UI changes
Includes text changes and localization file updates

Device Information
This PR was tested on: iOS Simulator (iPhone 6, iOS 11.2), Nexus 5 (Android 6.0.1)
Screenshots

![screenshot_20180214-025906](https://user-images.githubusercontent.com/3277310/36170832-925c3dd8-10ce-11e8-9ec9-d75e51354dbb.png)

Also requesting a review from @ccbrown since he's more likely to be able to make sense of the changes to commonmark.js

Some things that aren't consistent with GitHub...
GitHub allows leading space and renders this as a table:
 |a|b|
-|-

GitHub renders this as paragraph + list:
a|b
- |-

GitHub permits different whitespace characters in rows. There's a form feed character in the delimiter row here, and GitHub renders this as a table:
a|b
-|-

You're handling pipe escaping differently. GitHub does a naive replacement of "|" with "|", then later unescapes the string a second time. This cell has both backslashes consumed in the double unescaping and renders in GitHub as "a|a":
a|b
-|-
a\\|a|b

Too bad we can't just use GitHub's implementation. (Still hopeful for server-side parsing, which would allow us to use it!)

@ccbrown I'll take a look to see what I can do about those. Unfortunately, those cases aren't covered by either their commonmark spec or their unit tests :/

@ccbrown I added support for the first case since that one seems the most common, but I skipped the others because they're very niche behaviours. We can revisit them if they come up.
@elias I tried out using a LightBox, but I was having a really difficult time getting it to size the table correctly. I also didn't end up doing the zooming since I've spent a ton of time on getting those images to work in the first place, and we don't even know how many people even use them, so there's probably more impactful things that can be improved before we add those. If we end up rewriting the image preview, we can look at having it handle these in a more general way.


Set Window Position test failing on Ubuntu 15.04 / Latest FF 40.0a2

When attempting to set the Y position on a FF window that opens "snapped" to the top menu bar and full length (not full screen) the window will not be moved.

Upon further investigation I found that both Set Window Size and Set Window Position aren't given enough time to properly execute. When adding a delay, Set Window Size fails on  my Ubuntu setup because the window can't be sized above the maximum screen height if the window is snapped. I fixed this by simply reducing the overall resize height.
The issue I reported above is fixed by resizing the window before trying to set the window position.
@emanlove, @pekkaklarck, any ideas on addressing these timing issues? Should I just document that the action may not occur until some point after the keyword executes? I would add a timeout and just watch for the correct changes but Set Window Size lies and says it's the right size until the actual update occurs in which case it gives the correct values.

Is it possible to poll and wait until windows is resized/moved? If not, then documenting this behavior ought to be fine.

It does seem possible for the move, but the resize immediately reports the correct size but gets updated again after the resize occurs. I don't know what's up with the inconsistent behavior, it's just something on the webdiver's side.

I also got tests failing with Firefox (34.5) and Chrome (44.0.2403.155)  in Fedora 19 (but not in Windows 7).
Firefox:
Get and Set Window Size :: Get and Set Window Size                    | FAIL |
846 != 800
Get and Set Window Position :: Get and Set Window Position            | FAIL |
100 != 0
Chrome:
Get and Set Window Position :: Get and Set Window Position            | FAIL |
100 != 102

Here is another example of snapping in Fedora 22.
I noticed no matter what height you choose, the page height can't be more than screen height - bar size - y position - 1. For example, 1080-54-
KEYWORD Selenium2Library . Set Window Size @{WINDOW_SIZE}
Documentation: Sets the `width` and `height` of the current window to the specified values.
Start / End / Elapsed: 	20151118 13:59:38.947 / 20151118 13:59:38.977 / 00:00:00.030
13:59:38.947 	TRACE 	Arguments: [ '860' | '1006' ]
13:59:38.948 	DEBUG 	POST http://<IP_ADDRESS>:56204/hub/session/f6e8321f-371e-4288-9a99-e8ce4334827a/window/current/size {"width": 860, "windowHandle": "current", "sessionId": "f6e8321f-371e-4288-9a99-e8ce4334827a", "height": 1006}
13:59:38.977 	DEBUG 	Finished Request
13:59:38.977 	TRACE 	Return: None

00:00:00.010 KEYWORD ${width}, ${height} = Selenium2Library . Get Window Size
Documentation: 	Returns current window size as `width` then `height`.
Start / End / Elapsed: 	20151118 13:59:38.978 / 20151118 13:59:38.988 / 00:00:00.010
13:59:38.978 	TRACE 	Arguments: [  ]
13:59:38.978 	DEBUG 	GET http://<IP_ADDRESS>:56204/hub/session/f6e8321f-371e-4288-9a99-e8ce4334827a/window/current/size {"windowHandle": "current", "sessionId": "f6e8321f-371e-4288-9a99-e8ce4334827a"}
13:59:38.987 	DEBUG 	Finished Request
13:59:38.988 	TRACE 	Return: (860, 1006)
13:59:38.988 	INFO 	${width} = 860
13:59:38.988 	INFO 	${height} = 1006

00:00:00.008 KEYWORD Selenium2Library . Set Window Position @{POSITION}
Documentation: 	Sets the position `x` and `y` of the current window to the specified values.
Start / End / Elapsed: 	20151118 13:59:38.989 / 20151118 13:59:38.997 / 00:00:00.008
13:59:38.990 	TRACE 	Arguments: [ '1060' | '20' ]
13:59:38.991 	DEBUG 	POST http://<IP_ADDRESS>:56204/hub/session/f6e8321f-371e-4288-9a99-e8ce4334827a/window/current/position {"y": 20, "x": 1060, "windowHandle": "current", "sessionId": "f6e8321f-371e-4288-9a99-e8ce4334827a"}
13:59:38.996 	DEBUG 	Finished Request
13:59:38.996 	TRACE 	Return: None

00:00:00.007 KEYWORD ${x}, ${y} = Selenium2Library . Get Window Position
Documentation: 	Returns current window position as `x` then `y`.
Start / End / Elapsed: 	20151118 13:59:38.997 / 20151118 13:59:39.004 / 00:00:00.007
13:59:38.997 	TRACE 	Arguments: [  ]
13:59:38.998 	DEBUG 	GET http://<IP_ADDRESS>:56204/hub/session/f6e8321f-371e-4288-9a99-e8ce4334827a/window/current/position {"windowHandle": "current", "sessionId": "f6e8321f-371e-4288-9a99-e8ce4334827a"}
13:59:39.003 	DEBUG 	Finished Request
13:59:39.003 	TRACE 	Return: (1060, 20)
13:59:39.004 	INFO 	${x} = 1060
13:59:39.004 	INFO 	${y} = 20

00:00:00.009 KEYWORD ${width}, ${height} = Selenium2Library . Get Window Size
Documentation: 	Returns current window size as `width` then `height`.
Start / End / Elapsed: 	20151118 13:59:39.005 / 20151118 13:59:39.014 / 00:00:00.009
13:59:39.006 	TRACE 	Arguments: [  ]
13:59:39.006 	DEBUG 	GET http://<IP_ADDRESS>:56204/hub/session/f6e8321f-371e-4288-9a99-e8ce4334827a/window/current/size {"windowHandle": "current", "sessionId": "f6e8321f-371e-4288-9a99-e8ce4334827a"}
13:59:39.013 	DEBUG 	Finished Request
13:59:39.013 	TRACE 	Return: (860, 1006)
13:59:39.014 	INFO 	${width} = 860
13:59:39.014 	INFO 	${height} = 1006

There has not been activity for this issue for long time and we are planning to close the old issues if they are not anymore valid ones. If you feel that this is still valid issue, could you send an update. If update is not received in a month, we will assume that this is not anymore an issues and we will close this issue.


VisibleOnScreenNotifier2D screen_entered or screen_exited signal will only emited once.

Godot version
4.0 rc1 official
System information
Windows 11, RTX3070, Vulkan
Issue description
I noticed that the VisibleOnScreenNotifier2D "screen_entered" and "screen_exited" signal will only be emitted once when on or off screen. It will wont be fired or emitted again after that.
Steps to reproduce
1)Create a sprite and add VisibleOnScreenNotifier2D as child
2)Add camera2d and add codes so that the camera can be pan or move (use arrow keys for camera movement)
3)VisibleOnScreenNotifier2D will make the sprite visible when on screen and visible=false when exited the screen.
4)Use arrow keys to move the camera and make the sprite enter or exit the camera view.
Minimal reproduction project
TestVisibilityNotifierBug.zip

If you make your sprite invisible, it makes VisibleOnScreenNotifier2D invisible, which makes it never appear of screen (because it's invisible).
VisibleOnScreenNotifier2D in 4.0 is more performant and accurate, because it uses actual drawing code to determine whether it's visible, but as a result, the node has to be visible.
btw no need to toggle sprite's visibility. It will be culled automatically when off-screen.

@KoBeWi If this is intended by design for v4 , sure fine. But please put into document this new behavior of this node since it does behave differently compared to v3.5.


[bal-navbar] Partner Logo squeezed

Detailed description

the partner logo is squeezed on mobile viewports

@GinaBiondo-aperto is that already fixed by with you last PR's?

Yes, it is! :) Thought I added that to the PR but apparently missed it


Docs: Readme content added

What type of PR is this? (check all applicable)

[ ] Feature
[ ] Bug Fix
[x] Documentation Update
[ ] Refactor
[ ] Optimization

Description

Added how to work with storybook section in readme.

Related Issue #
Closes #75

QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
UI accessibility concerns?
If your PR includes UI changes, please replace this line with details on how
accessibility is impacted and tested. For more info, check out the awesome
Forem Accessibility Docs.
Added/updated tests?

[x] Yes
[ ] No, and this is why: please replace this line with details on why tests
have not been included
[ ] I need help with writing tests

Okay I will work on this changes

@nickytonline in my local I have installed all packages and done with readme part still showing merging block

I'll pull down your pull request and see what's up.

There's still some formatting errors but I can't push changes from my local machine as I do not have access to your branch.
From your local machine, do the following.

Run git pull to pull down the changes I made.
Run npm run format from the root of the project.
Commit the file changes which should be just the ReadME.md file.
Do a git push to push up the changes.

@nickytonline I followed same steps which you told but same merging is still blocked.


unused default_get_install_dependencies and not using the customization get_install_dependencies

I couldn't find any references of default_get_install_dependencies:  https://github.com/search?q=repo%3Apython-wheel-build%2Ffromager default_get_install_dependencies&type=code (apart from the docs)
Similarly for the custom override get_install_dependencies I can't find any reference to it:  https://github.com/search?q=repo%3Apython-wheel-build%2Ffromager+get_install_dependencies&type=code
It seems like we are using get_install_dependencies_of_wheel over these 2 functions: https://github.com/python-wheel-build/fromager/blob/main/src/fromager/sdist.py#L269

Those older functions were the old approach. Standardizing on building the wheel then getting the installation dependencies means we can get the dependencies from pre-built wheels, too. We also found that asking for the installation dependencies from the source tree was doing a large portion of the build work in order to produce the metadata that had the answer, so we might as well just build the wheel.
I think we can delete the old functions and override.


[beta] Basic Node & Express - TypeError: Cannot read property 'stack' of undefined

Challenge Name
https://beta.freecodecamp.org/en/challenges/basic-node-and-express/meet-the-node-console
Issue Description
Using Glitch - below error in console on opening -
cannot read property 'stack' of undefined.
If coding console.log("Hello World");  as per challenge instructions, will print before error but not pass tests.
If attempting to run locally cannot run 'npm start' as Error: Cannot find module 'fcc-express-bground' also present.
Solved this with 'npm install fcc-express-bground' but then receive same cannot read property 'stack' of undefined error (same output as below).
Could not find node 4.4.5, using 6.12.3
2:26 PM
a few seconds ago

TypeError: Cannot read property 'stack' of undefined
2:26 PM
    at Object.setupBackgroundApp (/app/node_modules/fcc-express-bground/index.js:149:31)
2:26 PM
    at Object.<anonymous> (/app/server.js:25:9)
2:26 PM
    at Module._compile (module.js:570:32)
2:26 PM
    at Object.Module._extensions..js (module.js:579:10)
2:26 PM
    at Module.load (module.js:487:32)
2:26 PM
    at tryModuleLoad (module.js:446:12)
2:26 PM
    at Function.Module._load (module.js:438:3)
2:26 PM
    at Module.runMain (module.js:604:10)
2:26 PM
    at run (bootstrap_node.js:383:7)
2:26 PM
    at startup (bootstrap_node.js:149:9)
2:26 PM
Node is listening on port 3000...

Browser Information

Browser Name, Version: Chrome - Version 64.0.3282.140 (Official Build) (64-bit)
Operating System: Windows
Mobile, Desktop, or Tablet:

Screenshot

This is a problem with the [fcc-express-background](https://www.npmjs.com/package/fcc-express-background) module itself, though it's hard to track down the error without the package being open sourced.

The package is at: https://github.com/Em-Ant/fcc-express-bground-pkg
The problem is that the package looks at the routes/middlewares on the challenge but in the first few challenges we don't need to make routes or apply middlewares. So the _routes.stack is undefined and that breaks the application.
This line breaks because router doesn't yet has routes(line 149):
var layers = myApp._router.stack.map(l => l.name)

Notice that there is an other place where similar logic is used for getting the routes(line 160):
var nowRoute = myApp._router.stack.filter(l => {
  if(l.route) {
    return l.route.path === '/now'
   }
  return false;
})

A solution would be to make a variable for the stack and default it to an empty array if there is no router
var stack = myApp._router ? myApp._router.stack : []
var layers = stack.map(l => l.name)
var nowRoute = stack.filter(l => {
  if(l.route) {
    return l.route.path === '/now'
   }
   return false;
})

Sorry guys I saw this only today. I'll have a look during the weekend

@raisedadead I think the problem is the CORS setting. If you try this project https://marked-fowl.glitch.me where I enabled CORS for https://beta.freecodecamp.com the test pass.
We need to check all the boilerplates and add the beta domain to the array.

Ah alright. Thanks for letting me know.

@Em-Ant Can you verify whether this is still an issue now that we've launched our new learning platform? (https://learn.freecodecamp.org)

@QuincyLarson as I commented here probably We have CORS issues in many projects after the domain change. This project is one of them.

@Em-Ant OK - is that something relatively easy to fix?

We should fix them in a common way. They use different approaches.
But the simplest fix will probably require a PR for each project, and fixes in the glitch boilerplates

@Em-Ant so is there a fix for this problem yet? Running to this same issue.

The test would pass because the block is inside a try/catch. By way the error log  is fixed now. @Zacele feel free to submit PRs to https://github.com/Em-Ant/fcc-express-bground-pkg until this packeage is moved under freecodecamp if you find some other problems

@Em-Ant How could I submit my projects into Github?

@Em-Ant you can transfer this repo and any other repos to me, I'll take care of moving them over to the org. Also its preferable that you change the naming schema as per the boilerplates.

@raisedadead, not sure if this was transferred over to you yet.

Not yet, @Em-Ant can you transfer the repo over to me. See https://help.github.com/en/articles/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account for help.

@Em-Ant Did you run into issues trying to transfer the repo?

the repo is transfered to @raisedadead (waiting for him to confirm). Sorry guys I didn't see the last message

The move is now complete. Thanks @Em-Ant for your help and support on this.
Repo is available here: https://github.com/freeCodeCamp/fcc-express-bground-pkg

Hi, it was working a few minutes ago, but it seems to be broken again. I have the correct Repo in package.json but still have the error "cannot find module.."

@raisedadead I notice this issue was closed, but the package.json file for the Basic Express challenges boilerplate still is referencing @Em-Ant's repo.
I will create a PR to switch to the FCC version.


Synology : Server disconnected (code 1006)

Hello,
I'm getting the error : server disconnected (code 1006).
From googling I suppose this is not purely related to docker-firefox but I can't find what is wrong with my configuration.
The docker is installed on my Synology and reached through the embedded nginx of the NAS.
I try to reach it from a subdomain configured to reach the port 5800 of the docker image.
The session starts (I can see the navbar) but after a while I get this error.
Here's some log from the docker image :
10/12/2018 10:12:13 Got connection from client <IP_ADDRESS>
10/12/2018 10:12:13   other clients:
10/12/2018 10:12:13 Got 'ws' WebSockets handshake
10/12/2018 10:12:13 Got protocol: binary
10/12/2018 10:12:13   - webSocketsHandshake: using binary/raw encoding
10/12/2018 10:12:13   - WebSockets client version hybi-13
10/12/2018 10:12:13 Disabled X server key autorepeat.
10/12/2018 10:12:13   to force back on run: 'xset r on' (3 times)
10/12/2018 10:12:13 incr accepted_client=7 for <IP_ADDRESS>:60684  sock=10
10/12/2018 10:12:13 created   xdamage object: 0x600031
10/12/2018 10:13:13 rfbProcessClientProtocolVersion: client gone
10/12/2018 10:13:13 client_count: 0
10/12/2018 10:13:13 Restored X server key autorepeat to: 1
10/12/2018 10:13:13 Client <IP_ADDRESS> gone
10/12/2018 10:13:13 Statistics             events    Transmit/ RawEquiv ( saved)
10/12/2018 10:13:13  TOTALS              :      0 |         0/        0 (  0.0%)
10/12/2018 10:13:13 Statistics             events    Received/ RawEquiv ( saved)
10/12/2018 10:13:13  TOTALS              :      0 |         0/        0 (  0.0%)
10/12/2018 10:13:16 destroyed xdamage object: 0x600031
Regards

Ok, probem solved, WebSocket was not activated on NGINX.
Once configured it works !
Cheers

Hello,
could you explain more how did you fix that problem ?
I'm trying to use it but same error with the same configuration...
Thanks !

You have issue with your reverse proxy?  Did you see https://github.com/jlesage/docker-firefox#reverse-proxy ?

Hello.
I solved the problem with WebSocket activation on the Synology reverse proxy conf.
All is fine, thanks a lot !
But sometime, I have (after navigate) error « server disconnected (code : 1006)... dont known why...

This is often fixed by clearing your browser's cache.

Ok, I tried but always the same error...

Is it working without going through the reverse proxy?  If yes, then it seems that you still have an issue with the WebSocket.
You can also open the browser's developper tools and looks at the console for errors.  You will probably see that the WebSocket connection fails.

actually without going through the reverse proxy, I do not have the error 1006 ...
To give more details, by the reverse proxy, the error arrives after a few minutes without activity....
Here is the console message :
util.js:218  Msg: Password Required
Util.Warn @ util.js:218
Util.Warn @ util.js:218
2util.js:218  Msg: Authentication OK
Util.Warn @ util.js:218
util.js:218  Msg: Connected (encrypted) to: Firefox
Util.Warn @ util.js:218
util.js:218 WebSocket on-close event
Util.Warn @ util.js:218
util.js:220  Msg: Server disconnected (code: 1006)
Util.Error @ util.js:220
Don't known if this could be util ?

More details on error, from console of FireFox.
Test method :

open a FF navigator
go to my personnal link "https://web.mydomain.fr" (where reverse proxy link to "localhost:5800")
waiting 50-60s
then error 1006 appear

https://www.noelshack.com/2019-12-2-1552986895-error-1006.png
Starting UI...  novnc-ui.min.js:1:3611
Msg: noVNC ready: native WebSockets, canvas rendering  novnc-core.min.js:1:2452
novnc-core.min.js:1:2452
GET
https://web.mydomain.fr/websockify [HTTP/1.1 407 Proxy Authentication Required 14 ms]
Msg: Starting VNC handshake  novnc-core.min.js:1:2452
Msg: Sent ProtocolVersion: 003.008  novnc-core.min.js:1:2452
Msg: Authenticating using scheme: 2  novnc-core.min.js:1:2452
Msg: Password Required  novnc-core.min.js:1:2452
novnc-core.min.js:1:2452
Msg: Authentication OK novnc-core.min.js:1:2452
Msg: Connected (encrypted) to: Firefox  novnc-core.min.js:1:2452
WebSocket on-close event  novnc-core.min.js:1:2452
Msg: Server disconnected (code: 1006)  novnc-core.min.js:1:2504
Util.init_logging/Util.Error https://web.mydomain.fr/js/novnc-core.min.js:1:2504
 https://web.mydomain.fr/js/novnc-core.min.js:1:72736
 https://web.mydomain.fr/js/novnc-core.min.js:1:73735
RFB/< https://web.mydomain.fr/js/novnc-core.min.js:1:68502
Websock.prototype.open/this._websocket.onclose< https://web.mydomain.fr/js/novnc-core.min.js:1:21394
Error while connected.  novnc-core.min.js:1:2504
Util.init_logging/Util.Error https://web.mydomain.fr/js/novnc-core.min.js:1:2504
 https://web.mydomain.fr/js/novnc-core.min.js:1:73453
 https://web.mydomain.fr/js/novnc-core.min.js:1:73735
RFB/< https://web.mydomain.fr/js/novnc-core.min.js:1:68502
Websock.prototype.open/this._websocket.onclose< https://web.mydomain.fr/js/novnc-core.min.js:1:21394

OK ! After reading this thread : https://github.com/novnc/noVNC/issues/567
and particulary this post :
karinepires commented Jun 7, 2016
Hello all,
I was having the same issue in my application and decided to follow this issue just in case.
I finally managed to solve it with a different strategy.
So, to complete what @Ziris85 said, if you are using nginx as a proxy to your websocketify connection you may want to complete the configuration with different timeouts.
For example one can add the following code to the nginx configuration on the proxied block to increase the timeout to 1hour:
    proxy_read_timeout 3600s;
    proxy_send_timeout 3600s;

I think my problem was a timer set in reverse proxy, so I looking for in Synology parameters and I found this : (sorry for the UI in french)
[url=https://www.noelshack.com/2019-12-2-1553001309-reverseproxy-syno-param.png][img]https://image.noelshack.com/minis/2019/12/2/1553001309-reverseproxy-syno-param.png[/img][/url]
Initially, params was set to 60s, with new values to 3600s, all is fine !
Thanks a lot for your help !


Add support for django-rest-swagger

There are probably two things to do:

add integration tests to testproject to check if the Swagger doc is generated without any issues
fix the issue with dynamically added fields to serializers - see #41

#41 is no longer an issue from what I can tell. Also I'm not really keen on idea of integration tests for a docs tool.
@haxoza can you elaborate if this issue is still valid?

Looks like it is not valid any more. Especially if you already closed #41.
Let's just close this issue as well.

Great. Thanks for the confirmation!


NaN string displayed when clicking on legend to hide a horizontal bar chart with Y-axis labels as strings

I have a horizontal bar chart. And my X-axis labels are numbers whereas the Y-axis labels are strings. when I click on the legend to hide the bar chart, the chart is hidden, however I see a string NaN on the top left of the Y-axis. Is it a bug? What is the fix for this?

@singhrasster do you have a test case that reproduces this?

Yes, so I have a horizontalBar chart where I have 2 categories of bars ( horizontal). The Y-axis labels are strings whereas the X-axis labels are numbers. Since there are two bars, there are two legends created. I click on each legend to hide the corresponding bar. When both bars are hidden (after clicking on the two legends), I see NaN on the top left of the X-axis.
There can be any number of categories of horiontal bars, say N. Whenever all N bars are hidden by clicking on all the corresponding N legends, the string NaN gets displayed left to the Y-axis.
I don't have anything setup online to show exactly. But, on some google search, I came across someone's fiddle where there is a horizontal bar. In that you can click on the Green legend left to the text "Test" to hide the bar. The bar is hidden but then you will see a text 'NaN' displayed to the left of the Y-axis.
Here is the link of the fiddle I mentioned above (again its not setup by me but it shows the issue I am talking about):
https://jsfiddle.net/4r26box7/

Looks like something goes wrong when there is no data, and the text that shows up should have been on the x axis. Definitely a bug that needs to be fixed

Is this issue fixed now? If yes, how can I use it? Do I need to update my chart.js library to a newer version? Currently I am using "chart.js": "2.5.0", in my package.json

@singhrasster this is not yet fixed


bug: extension fails to load in WSL or a docker container

Check the following:

[X] I have checked the behavior after setting "vscode-neovim.neovimClean" in VSCode settings.
[X] I have read the vscode-neovim docs.
[X] I have searched existing issues.

Neovim version (nvim -v)
NVIM v0.10.1 Build type: Release LuaJIT 2.1.1725453128
Operating system/version

Windows connecting to WSL via the WSL extension
Windows connecting to a remote OpenVSCodeServer container via the SSH and Dev Container extensions

Same issue in both.
Describe the bug
Cannot start neovim.

[Failed to start nvim] Neovim spawn error: spawn

Dev tools gives me:
notificationsAlerts.ts:42 [Failed to start nvim] Neovim spawn error: spawn /home/linuxbrew/.linuxbrew/bin/nvim ENOENT
c @ notificationsAlerts.ts:42
(anonymous) @ notificationsAlerts.ts:28
B @ event.ts:1242
C @ event.ts:1253
fire @ event.ts:1277
addNotification @ notifications.ts:228
notify @ notificationService.ts:253
(anonymous) @ mainThreadMessageService.ts:86
f @ mainThreadMessageService.ts:51
$showMessage @ mainThreadMessageService.ts:45
S @ rpcProtocol.ts:458
Q @ rpcProtocol.ts:443
M @ rpcProtocol.ts:373
L @ rpcProtocol.ts:299
(anonymous) @ rpcProtocol.ts:161
B @ event.ts:1242
fire @ event.ts:1273
fire @ ipc.net.ts:652
K.onmessage @ localProcessExtensionHost.ts:378
log.ts:439   ERR [ExtensionListenerError] Extension 'asvetliakov.vscode-neovim' FAILED to handle event: TypeError: Cannot read properties of undefined (reading 'command'): Error: [ExtensionListenerError] Extension 'asvetliakov.vscode-neovim' FAILED to handle event: TypeError: Cannot read properties of undefined (reading 'command')
	at i.value (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:171:28731)
	at r.B (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
	at r.fire (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:949)
	at I.onDidChangeWindowProperty (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:21118)
	at I.$onDidChangeWindowFocus (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:20929)
	at y.S (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:5968)
	at y.Q (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:5734)
	at y.M (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:4767)
	at y.L (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:3602)
	at i.value (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:2297)
	at r.B (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
	at r.fire (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:949)
	at a.fire (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:14463)
	at i.value (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:184:8635)
	at r.B (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
	at r.fire (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:949)
	at a.fire (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:14463)
	at MessagePortMain.<anonymous> (c:\Users\jmo\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:184:6761)
	at MessagePortMain.emit (node:events:519:28)
	at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2619)

Steps To Reproduce
Run the extension. Set the executable and init paths. Get error.
Set safe mode. Get error.
Install extension on the remote server. Restart. Get error.
Copy the same settings into the User, Remote, and Workspace settings for the extension. Get error.
Try just one of each of them being set. Get error.
Revert to previous verions of the extension (because it did work before!). Get error.
My settings:
{
  "files.autoSave": "afterDelay",
  "vscode-neovim.ctrlKeysForNormalMode": [
    "a",
    "b",
    "c",
    "d",
    "e",
    "f",
    "h",
    "i",
    "j",
    "k",
    "l",
    "m",
    "o",
    "r",
    "t",
    "u",
    "v",
    "w",
    "x",
    "y",
    "z",
    "/",
    "]",
    "right",
    "left",
    "up",
    "down",
    "backspace",
    "delete",
    "n"
  ],
  "vscode-neovim.neovimExecutablePaths.linux": "/home/linuxbrew/.linuxbrew/bin/nvim",
  "vscode-neovim.neovimExecutablePaths.darwin": "/home/linuxbrew/.linuxbrew/bin/nvim",
  "vscode-neovim.neovimExecutablePaths.win32": "/home/linuxbrew/.linuxbrew/bin/nvim",
  "vscode-neovim.neovimClean": true,
  "vscode-neovim.neovimInitVimPaths.linux": "/home/workspace/.config/nvim/init-core.vim",
  "vscode-neovim.neovimInitVimPaths.darwin": "/home/workspace/.config/nvim/init-core.vim",
  "vscode-neovim.neovimInitVimPaths.win32": "/home/workspace/.config/nvim/init-core.vim"
}

nvim exists:
❯ which nvim
/home/linuxbrew/.linuxbrew/bin/nvim

My init file path is correct.
Expected Behavior
It works.

Your settings don't have useWSL. Read https://github.com/vscode-neovim/vscode-neovim?tab=readme-ov-file#-getting-started

Okay, that got rid of the error, though my config is not loading still. Nothing in the dev console.
Also I swear I tried this on the WSL window at one point, to no avail, but who knows what else was different in my setup then.
I am rather confused about why I would have to enable "Use WSL" when remoting from a windows machine into a linux server then connecting to a container running linux. I took the setting to mean "Use the config stored in WSL, at the path of the Linux config option" as a way for Windows users to keep only one copy of the init file to be updated.

I am rather confused about why I would have to enable "Use WSL" when remoting from a windows machine into a linux server then connecting to a container running linux. I took the setting to mean "Use the config stored in WSL, at the path of the Linux config option" as a way for Windows users to keep only one copy of the init file to be updated.

It depends on where the extension is running. You may also want to try setting the extensionKind: https://github.com/vscode-neovim/vscode-neovim?tab=readme-ov-file#remote-development
If the extension is running on your local Windows env (that's the case for "UI" extensions, which is the typical case for this extension), it needs to know that the path you configured is a WSL path.


Function mcrypt_create_iv() is deprecated in PHP 7.1.0

According to https://secure.php.net/mcrypt_create_iv. An appropriate alternative is the PHP function random_bytes()

This function was DEPRECATED in PHP 7.1.0, and REMOVED in PHP 7.2.0.
php documnetation
user random_bytes — which Generates cryptographically secure pseudo-random bytes.
<?php
$bytes = random_bytes(5);
var_dump(bin2hex($bytes));
?>

string(10) "385e33f741"
Taken from php.net

This project seems to be no longer maintained.


Use ::class when importing classes

Instead of components being added by using the full class name as a string, use ::class.

Yep, this would probably be nicer -- PR?


Jira integration with required fields

We have some required fields in our jira.
For example we need always the field "version" and "customfield_xxxx". Without them, we can't create an issue.
It would be nice if we can configure the jira-hook with required fields.
Crashlytics-services doesn't support this at the moment.
It would be great if some one can make this possible :+1: :innocent:

Hey @StefMa,
Thanks for the feedback! This is something that we've talked about adding, but isn't on our immediate roadmap. I'll let you know if that changes and keep the feedback coming :)
-Mike


Improve Error Message

Description
This error message is way too long and confusing and could use some improvement to make it concise and easier for the user for the message to report the issue and help them debug.
  File "C:\...\MIT\Python-SDK\src\cript\nodes\core.py", line 74, in __setattr__
    raise CRIPTAttributeModificationError(self.node_type, key, value)
cript.nodes.exceptions.CRIPTAttributeModificationError: Attempt to modify an attribute of a node (Process) that wasn't intended to be modified.
Here the non-existing attribute properties of Process was attempted to be modified.
Most likely this is due to a typo in the attribute that was intended to be modified i.e. `project.materials` instead of `project.material`.
To ensure compatibility with the underlying CRIPT data model we do not allow custom attributes.
C:\...\MIT\Python-SDK\src\cript\nodes\primary_nodes\process.p

I am OO today and for the next 2 weeks.


improve sun/shadow example to use effect rendering pipeline

For #2993

Change List

new sun/shadow experimental example
create shadow-effect class
refactor example to use effect rendering pipeline
remove dummy shadow map
delete pass and texture

Could you add a screenshot or .gif?

Coverage increased (+0.008%) to 62.021% when pulling c6efcfa53b3d32f90d5308eb9ad4b9ec2d79e36c on x/shadows into 548f139ec58835e109093552c69783ae10b6cbe5 on master.


Git clean changes, cleaned file just shows up blank.

VSCode Version: Code 1.5.3 (5be4091987a98e3870d89d630eb87be6d9bafd27, 2016-09-22T08:40:08.699Z)
OS Version: Linux x64 4.4.0-38-generic

Steps to Reproduce:

Make some changes
From toolbar for git, select to clean the changes.
The file shows up empty in editor.
Close the file form editor and reopen, it's still blank.

Need to restart vscode to correct, so far I've notice this problem 2 times already.

@rajinder-yadav I do this almost daily, and so far I have never seen something like what you describe.
Do you:

create a new file or modify an existing file?
if you modify a file, is the file you modify staged in the git index before you make the modifications?
do you have a diff displaying when you say the file shows up empty in editor?

Can you perhaps capture a screenshot when this happens or perhaps give more detailed steps such that we can reproduce?

I'v done this on an existing project where I've made changes to a file that's already tracked.
I've made some changes and then after saving them I've done a clean (I might have edited other file and or checked in other files? not recall the exact steps.)
It took me a while to repro, something seeing is believing :) ... so here is a screen-cast. In the video each time I delete, I save the file and them edit and save if you see me typing!
https://youtu.be/cCjoifvf4Og
You might have to do it a few times, it took me several tries even with a fresh load of vscode.

Please see if you can find any logged output that could help us find the source of the issue:

run code --verbose from the command line and attach the output
in Code select Help | Toggle Developer Tools and select the Console
attach any output you see in the Console you can find

Thanks!

Attached
git-clean-bug.log.gz

@rajinder-yadav
I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line, execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

Unfortunately it's not, I used "code --disable-extensions --verbose ."
After a few tries, I got into the reported state.
Log below:

//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/FETCH_HEAD
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/FETCH_HEAD
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/FETCH_HEAD
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/FETCH_HEAD
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/templates/source.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/templates/source.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/templates/title.trb
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
//usr/share/code/resources/app/out/vs/workbench/workbench.main.js:36 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
ipc.cp.ts:139 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/templates/source.trb
ipc.cp.ts:139 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
ipc.cp.ts:139 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/templates/source.trb
ipc.cp.ts:139 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
ipc.cp.ts:139 [IPC Library: Watcher] [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
ipc.cp.ts:139 [IPC Library: Watcher] [ADDED] /home/yadav/dev/cpp/rmake/.git/index.lock
ipc.cp.ts:139 [IPC Library: Watcher]  >> normalized [CHANGED] /home/yadav/dev/cpp/rmake/.git/index
ipc.cp.ts:139 [IPC Library: Watcher]  >> normalized [ADDED] /home/yadav/dev/cpp/rmake/.git/index.lock
ipc.cp.ts:139 [IPC Library: Watcher] [DELETED] /home/yadav/dev/cpp/rmake/.git/index.lock
ipc.cp.ts:139 [IPC Library: Watcher]  >> normalized [DELETED] /home/yadav/dev/cpp/rmake/.git/index.lock

@rajinder-yadav do you still see this in 1.6.0?

Thanks for checking back, I went through a few trails and looks like it's been fixed.
Super work guys :D

Marking as verified as the OP has mentioned that this is fixed


Modal backdrop covers modal

Current behavior
I'm in the process of upgrading from ariakit to @ariakit/react, and found that I'm having trouble with my modals.  The backdrop is covering the modal itself, causing the inputs to not be focusable, and the color of the backdrop bleeds over the modal body.  I think this is because I'm not using position: fixed for my modal, since it was not required previously.  Is it a requirement now?
Steps to reproduce the bug

Open sandbox: https://codesandbox.io/s/ariakit-dialog-backdrop-8l5891?file=/src/styles.css
Notice that the backdrop covers the modal, and the input cannot be clicked

Expected behavior
The backdrop should be behind the modal.
Workaround
This only seems to happen when not using position: fixed for the modal.
Possible solutions
No response

It seems like the main change causing me problems is that previously, the modal body was a child of the fixed-position overlay.  Now it's a sibling.  I'm having a bit of difficulty re-creating my previous behavior or being able to add scroll to the overlay, allowing the entire modal to scroll up and down as needed (see https://codesandbox.io/s/ariakit-dialog-backdrop-old-style-bcmiol for an example).  Do you know how to re-create that effect using the current version?

Yeah, the backdrop element is now a sibling of the dialog. This is to allow them to be animated separately. For example, you can fade in the backdrop later than showing the dialog itself. It's not possible if the dialog is wrapped within the backdrop.
I recommend the following base styles for the dialog, which are based on the styles the browser applies to native modal dialogs:
.dialog {
  position: fixed;
  inset: 1rem;
  margin: auto;
  height: fit-content;
  max-height: calc(100vh - 2 * 1rem);
}

If you want to stick with the old style, you can do so by disabling the default backdrop and rendering your own wrapper using the render prop:
https://codesandbox.io/s/ariakit-dialog-backdrop-old-style-o4zle5?file=/src/App.tsx
<Dialog
  store={dialogStore}
  backdrop={false}
  className="modal"
  render={(props) => (

  )}
>

A tall modal, can scroll down to see the entire thing.

</Dialog>

Thanks for the detailed suggestion and workaround.  I think the main downside I can see to the approach you suggest to use the render prop, is that the hideOnInteractOutside won't work, since the entire modal overlay is considered to be part of the contentElement, right?  I'm working on finding a way to make it work, so far getting stymied at the check for whether the element is "marked".  I'll report back if I figure something out, for anyone else hitting this.

Which version are you using? There was a recent update on the marked logic (mostly for popover wrappers, but should also take custom backdrop wrapper elements into account).
In the CodeSandbox I sent above, clicking on the backdrop does hide the dialog.

I've encountered a rather tricky scenario, I want to animate both backdrop and modal and close the modal on outside click. After some tinkering, this is what helped me:

kept backdrop
used render prop and spread props on the nested element
provided pointer-events: none on the outside element passed to render
children is simply modal contents

<AriakitDialog
  store={store}
  backdrop={
}
  render={(dialog) => (

  )}
>
  {children}
</AriakitDialog>

.backdrop {
  /* add backdrop animations here */
}

.modal-container {
  /* note that this element renders no visible UI, but it's not managed by Ariakit,
    meaning it will block user interactions when the modal is hidden */
  pointer-events: none;
  margin: auto;
  position: fixed;
  inset: 0;
  /* adjust spacing here as necessary */
}

.modal {
  pointer-events: auto;
  margin: auto;
  /* add modal animations here */
}

Hope this is useful!

I want to animate both backdrop and modal and close the modal on outside click

@Dremora You should be able to do that without the modal-container element. Do you need this container just to adjust the position of the modal? In this case, I'd try the styles I suggested on https://github.com/ariakit/ariakit/issues/2484#issuecomment-1569114173

@Dremora You should be able to do that without the modal-container element. Do you need this container just to adjust the position of the modal? In this case, I'd try the styles I suggested on #2484 (comment)

You're right, I have revisited your approach and it works after all. I only have to change my approach to specifying padding - calc(100% - 2 * padding) seems to do the job.


Add dynamic dimensions capability to GPT Embeddings models

Apparently this can optimize the cost, performance whilst still out performing ada and small gpt models. Adding this will bake in flexibility for future.
See note below
https://platform.openai.com/docs/guides/embeddings/use-cases

Not all embedding models support dynamic dimensions. I have added it to the OpenAi3LargeEmbeddings model. Simply set the optional parameter dynamicDimension in the constructor. We can also add it to any other embedding model that supports this.
Will be available in the next version published.

Included in version 0.0.73


feature request: timepicker

thank you for adding timepicking to the datepicker. I can now pick dateTimes!
However, just like there are instances when i just need to pick a date, there are other instances when i just need to pick a time.
It would be nice If I could have just the time picker component.

looks like this is resolved with #1281
can we merge?


Disable logging request header by default.

label = Bugfix
RequesterIdentity is assumed to be of type HttpRequesterIdentity in PR https://github.com/apache/pinot/pull/8907 . We also have GrpcRequesterIdentity. So, using GrpcRequesterIdentity will result in error like  cannot be cast to class org.apache.pinot.broker.api.HttpRequesterIdentity
Changing default to false until the bug is fixed properly.
I will create an issue to fix this. We should ideally create a function in RequestIdentity to get client IP and have all child classes implement it.

@GSharayu  and @mcvsubbu  can you please review this?

LGTM, thanks Vivek for the quick fix

Codecov Report

Merging #9192 (b9cba1d) into master (6ed17d2) will decrease coverage by 54.73%.
The diff coverage is n/a.

:exclamation: Current head b9cba1d differs from pull request most recent head 58294df. Consider uploading reports for the commit 58294df to get more accurate results

@@              Coverage Diff              @@
##             master    #9192       +/-   ##
=============================================
- Coverage     70.04%   15.30%   -54.74%
+ Complexity     5003      170     -4833
=============================================
  Files          1852     1802       -50
  Lines         98760    96584     -2176
  Branches      15021    14771      -250
=============================================
- Hits          69175    14783    -54392
- Misses        24709    80736    +56027
+ Partials       4876     1065     -3811

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
15.30% <ø> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Learn more


crashes on android L

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.butterknife/com.example.butterknife.SimpleActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setText(java.lang.CharSequence)' on a null object reference

This is your code crashing, not ButterKnife. You're trying to call setText on a null reference.

ok,I got it.Thanks...

Hi !
When I use normal declaration using findviewbyId working fine after i changed to butterknife bind then i got below exception. Let me know where can i miss any dependencies
In dependencies i have added
compile 'com.jakewharton:butterknife:8.0.1'
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setText(java.lang.CharSequence)' on a null object reference

Did you initialize the butterknife before set text in to textview..

yes
ButterKnife.bind(this, view);

when we added below lines i got gradle exception
apply plugin: 'com.neenbedankt.android-apt'
dependencies {
apt 'com.jakewharton:butterknife-compiler:8.0.1'
}
but itz accepting below dependency
dependencies {
compile 'com.jakewharton:butterknife:8.0.1'
}

Check the textview Id......if not solve ....send the screen shot ...

Hi same issue to me also when we running my app. please can you look at below url once
https://codedump.io/share/5wTxXTI4pLfX/1/null-pointer-exception---issues-with-butterknife---android-application-development

+1 . Facing same using. Not able to solve it


[Dialog, DropdownMenu] Option to disable body margin on Dialog & Dropdown menu.

Feature request
Overview
The CSS selector scrollbar-gutter: stable has landed at 74.09% availability. Using this in conjunction with Dialog or DropdownMenu causes a conflict because it adds additional padding when it's already been added by the browser natively. Currently, this is causing exactly what scrollbar-gutter solves, a layout shift in our apps.
The layout shift is caused when the dialog is open. The body receives this style: margin-right: 17px !important;. I would like a property on the Dialog to disable this margin style as it's impossible to get around. Global CSS rules with !important are overwritten because of CSS' cascading nature.
Something like this should be great
<Dialog.Root nativeScrollbarGutter> // No gutter will be added automatically as it already exists
...
</Dialog.Root>

Examples in other libraries

Who does this impact? Who is this for?
Anyone using scrollbar-gutter: stable to remove layout shifts when navigating pages.
Additional context
Ultimately this is just more control for the library consumer and will future-proof Dialog and DropdownMenu when scrollbar-gutter eventually becomes supported enough.
This also allows for granular control, if native gutters are not supported we can use window.matchMedia to fallback to nativeScrollbarGutter={false}

Managed to get around it with. I'm okay with working on a PR for this if you think this feature would be a good addition.
@supports (scrollbar-gutter: stable) {
  html body {
    margin-left: 0 !important;
  }
}

Hey @sannajammeh, I'd consider this responsibility of the remove-scroll library first and foremost, I know the author has been thinking about this too and shares a similar perspective
With that in mind it's not likely something we'd shim in over the top, rather we'd adopt this downstream or modify / alter our dependency entirely.
So for now your workaround is the best option.

Thanks for the info! Closing this 👍

Could we add this to the docs? It seems like a common problem for users who display the scroll bar on every page to reduce CLS.
For example
html {
	overflow-y: show;
}


add priority and validation

This pull requests adds priority option to the repo i have also added in a few more bits of validation.  The use of validate_integer pushes the stdlib module dependency to 4.6.0.

This looks good.  Would you also mind updating the read me please, with an example and perhaps a brief explanation on how to use?  Is 0 high or low priority?

Ok i have added some documentation

Cheers, thank you.


Elytra helper only seems to affect vanilla elytras

The Ender IO Dark Steel Chest with Elytra upgrade and the Thaumic Augmentations Elytra Harness don't get the special elytra handling when it's turned on.  Since multiple mods have an issue, I'm not sure if they need to implement something in order for them to take advantage of the toggle, or if something has been missed in the code here.

A quick glance at the code suggests the fix is hard coded for vanilla elytras only.  But hand checking armor and baubles for elytra capabilites sounds messy, unless there's some universal sign for elytra wings.

You're correct. I also encountered this bug but it's not easy to fix without modifying the mods themselves.
The issue for Ender IO is that the vanilla check for motionY being less than 0 (which is what Mojang removed in 1.15) is duplicated within their code here. Aqua Acrobatics patches this out of the vanilla elytra logic but cannot do the same for Ender IO automatically.
I haven't checked Thaumic Augmentations' code but it probably has the same issue.
To fix it for a mod, it either needs to add integration (which won't happen for 1.12 at this point), or I need to patch the mod myself using mixins, which is likely the route I'll end up having to take.
Elytras are so infrequently used in modded that I haven't really considered this a high priority, but if you're still being bothered by it, I can take a look.

One bit of good news is that Thaumic Augmentation is still in active development, as there is no Thaumcraft for modern Minecraft yet. If you can explain what Codex needs to do, or offer a pull request, he'll likely accept it.
I can't say the same for Ender IO.

It will be fixed for Ender IO in the next release. Looking at Thaumic Augmentation next.

In 1.10.0 this is fixed for Thaumic Augmentation as well.


dial tcp <IP_ADDRESS>:80: connect: connection refused

I am finding below error  if i try terraform apply
terraform version
Terraform v0.14.3

provider registry.terraform.io/hashicorp/azurerm v2.19.0
provider registry.terraform.io/hashicorp/kubernetes v2.4.1

cloud provider : azure
Error: Post "http://localhost/api/v1/namespaces/kns/services": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 18, in resource "kubernetes_service" "zookeeper_headless":
18: resource "kubernetes_service" "zookeeper_headless" {
Error: Post "http://localhost/api/v1/namespaces/kns/services": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 48, in resource "kubernetes_service" "zookeeper":
48: resource "kubernetes_service" "zookeeper" {
Error: Post "http://localhost/api/v1/namespaces/kns/services": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 66, in resource "kubernetes_service" "kafka":
66: resource "kubernetes_service" "kafka" {
Error: Post "http://localhost/api/v1/namespaces/kns/services": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 82, in resource "kubernetes_service" "kafka_headless":
82: resource "kubernetes_service" "kafka_headless" {
Error: Post "http://localhost/apis/apps/v1/namespaces/kns/statefulsets": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 99, in resource "kubernetes_stateful_set" "zookeeper":
99: resource "kubernetes_stateful_set" "zookeeper" {
Error: Post "http://localhost/apis/apps/v1/namespaces/kns/statefulsets": dial tcp <IP_ADDRESS>:80: connect: connection refused
on main.tf line 260, in resource "kubernetes_stateful_set" "kafka":
260: resource "kubernetes_stateful_set" "kafka" {

can you send your configuration? it seems terraform is trying to reach a local k8s setup instead of a remote one.

Steps
az login
az network vnet create -g 409-375c299f-create-an-aks-cluster-that-uses-azure -n myVnet --address-prefix <IP_ADDRESS>/16 --subnet-name mysubnet --subnet-prefix <IP_ADDRESS>/20 —subnet-name virtualsubnet --subnet-prefix <IP_ADDRESS>/21
az aks get-credentials -g 409-375c299f-create-an-aks-cluster-that-uses-azure  -n cluster1
Screenprint:

added to main.tf


Unable to build Caffe2-GPU with vcpkg toolchain file

Hi,
I'm trying to build Caffe2 from source, while using certain third party libraries(lmdb, leveldb, glog, gflags, etc) provided by vcpkg(specify the vcpkg.cmake toolchain file for cross-compiling). The CPU version of Caffe2 can be built without a problem. But when I build the GPU version, I get lots of compiling errors on the CUDA files:
1>C:/Develop/vcpkg/installed/x64-windows/include\google/protobuf/extension_set.h(640): warning : field of class type without a DLL interface used in a class with a DLL interface
1>
1>C:/Develop/Caffe2/build\caffe2/proto/caffe2.pb.h(227): error : member "caffe2::TensorProto_Segment::kIndexInFileMessages" may not be initialized
1>
1>C:/Develop/Caffe2/build\caffe2/proto/caffe2.pb.h(299): warning : field of class type without a DLL interface used in a class with a DLL interface
1>
1>C:/Develop/Caffe2/build\caffe2/proto/caffe2.pb.h(300): warning : field of class type without a DLL interface used in a class with a DLL interface
1>
1>C:/Develop/Caffe2/build\caffe2/proto/caffe2.pb.h(350): error : member "caffe2::TensorProto::kIndexInFileMessages" may not be initialized
1>
1>C:/Develop/Caffe2/build\caffe2/proto/caffe2.pb.h(598): warning : field of class type without a DLL interface used in a class with a DLL interface

Likely some of the compiler options are not passed to the NVCC compiler.  If I use the normal "Visual Studio 14 2015 win64" generator without specifying the toolchain file, I can compile these CUDA files without errors.

Successfully built Caffe2-GPU as a static library. The problem is unrelated to the vcpkg toolchain file. Closing this issue.

Which version of CUDA and MSVC have you used?

CUDA toolkit version 8.0 with cuDNN v5.1
MSVC 2015 with Update 3

这个问题似乎是 NVCC 不支持 dllexport，使用静态版 protobuf 就不会有此问题。

The problem seems to be that NVCC does not support dllexport, and this problem will not occur with the static version of protobuf.

Hi, I am getting a list of the same error
 error : member "caffe2::TensorProto_Segment::kIndexInFileMessages" may not be initialized
What was the problem here? How did you solve it?

@rakidedigama Just replace all "constexpr" with "const" in caffe2.pb.h will solve the problem. Also you may need to patch Eigen3's Half.h if you are using CUDA 9.x, see http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1526


pt_BR translation

Hello, firstly thank you and congratulations on the widget development, it is very useful :D
This is my way of contributing to the project, i hope it encourages more users to use it.

Thank you!


[Enhancement] Remove persistent index dir when persistent index is disabled

Why I'm doing:
The persistent index dir is not removed when persistent index is disabled. https://github.com/StarRocks/starrocks/pull/32184 can not handled this scenario because the tablet is still in worker.
What I'm doing:
Remove persistent index dir synchronously when persistent index is disabled.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@wyb @meegoo PTAL

https://github.com/Mergifyio backport branch-3.1

https://github.com/Mergifyio backport branch-3.2


[DOC] Versioned Data Prepper documentation

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Data Prepper is a distinct product from OpenSearch. It has its own versions and release schedule. And similar to OpenSearch, there are incompatibilities between major versions.
The OpenSearch documentation currently allows readers to select an OpenSearch version. However, this is not possible with Data Prepper. So readers are unable to know what was valid in Data Prepper 1.5 for example. They only know the latest.
The solution here should be flexible to support any other artifacts with different release cycles. It could be that we want to take a similar approach with the Logstash plugins (maybe, maybe not).
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
N/A

Target Date: Mid-November

This proposal would likely change the overall structure of the documentation page.
Right now, Data Prepper documentation is located at the following: https://opensearch.org/docs/latest/clients/data-prepper. Readers change change the OpenSearch version to other versions, say https://opensearch.org/docs/2.2/clients/data-prepper.
If the documentation resided at the same location, it would result in double versions in the URL and create an explosion of possible paths. For example, OpenSearch 2.2 and Data Prepper 2.0: https://opensearch.org/docs/2.2/clients/data-prepper/2.0/. This would not be a good experience.
Thus, I believe that the Data Prepper documentation should be moved to a top-level page. There are a couple possible options here.
Option 1 - Move Data Prepper only
Move the Data Prepper documentation such that it gets its own page.
https://opensearch.org/docs/data-prepper/latest
https://opensearch.org/docs/data-prepper/2.0

or
https://opensearch.org/data-prepper/docs/latest
https://opensearch.org/data-prepper/docs/2.0

Option 2 - Move OpenSearch documentation as well
The OpenSearch documentation could be given a sub-path as well. This way both products have similar path structures.
https://opensearch.org/docs/data-prepper/latest
https://opensearch.org/docs/data-prepper/2.0
https://opensearch.org/docs/opensearch/latest
https://opensearch.org/docs/opensearch/2.2

Overall, I'd like to suggest that the documentation take the approach of Option 1 since this would not break any existing URLs for OpenSearch. The downside is it may add some development work because the docs page will need to detect if the path is another product (e.g. data-prepper) or an OpenSearch version (e.g. 2.2) in the base URL https://opensearch.org/docs/{subProductOrOpenSearchVersion}.

@kgcreative, would love to hear your thoughts

@AMoo-Miki Lets generalize this to be able to accommodate Data Prepper, OpenSearch and OpenSearch Dashboards

Let's close this once the new repo is created and deployed.

We are going to support versioned Data Prepper documentation with a new documentation repo specifically for Data Prepper documentation. This will decouple the branches and versioning in that repository from those of this project (documentation-website).

Hi David, since we decoupled the Data Prepper content from the OS versioning, do you feel comfortable closing this issue? https://opensearch.org/docs/latest/data-prepper/. We eventually want to create a separate pipeline (and potentially a separate repo) and version the content, but can open new issues for those things, as needed.

@hdhalter , This issue also requests that we have versioning for the Data Prepper documentation. The decoupling helps towards this. But, I think we will still need multiple Data Prepper documentation versions. When Data Prepper 3.0 comes out, it would be good to have the 2.x documentation still available. So I think we should keep this issue open while we work toward that.


Use project ID when querying by repo UUID

The "get by ID" query is used in several places in the code when handling webhooks or other events. When servicing API requests, query by filter to avoid any potential security issues.
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Fixes #(related issue)
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[ ] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 39.295% (-0.002%) from 39.297%
when pulling c0345c53c28e6fe83ae69932f8bb69305d2e5a3e on repo-id-use-project-id
into 9886d13d9a6936c421844896bf6ae99624a0bd41 on main.


Add support for HTTP PATCH requests

Description
Add support for HTTP PATCH requests
Issues Resolved
http_request cannot send PATCH requests - limiting usefulness when working with APIs which require them
Check List

[x] New functionality includes tests (skipped)
[x] All tests pass
[x] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Looks good, thanks @jamesbroadhead . I'm not sure there's any useful unit tests you can add here. @chef/maintainers

removed the "in progress" note from the PR
Added a line to RELEASE_NOTES.md

@thommay what else needs doing to merge? :)

@jamesbroadhead : Per our conversation, you may want to check in on this PR.

Hi @thommay, I've bumped this & CI is now green  (the previous failure was spurious). Anything else needed?
J

This is a great improvement, thanks @jamesbroadhead!


[clangimporter] Fix a StringRef to std::string conversion.

Explictly call StringRef::str, the implicit conversion operator was
removed in an earlier commit:
(See https://github.com/llvm/llvm-project/commit/adcd02683856c)
(Please summon the test bot)

@swift-ci please test

Why not apply this to master?  This seems like it would work on master as well as master-next, but putting it on master means less divergence.

Why not apply this to master? This seems like it would work on master as well as master-next, but putting it on master means less divergence.

Good point, this applies cleanly to master:
https://github.com/apple/swift/pull/32060


Random error > "Failed to look up service"

I'm following on this issue. I'm testing/using this reverse-proxy a lot since 13 days. I have to report that it's not stable. Here are the docker service commands I'm using.
When I check the logs, I see something is wrong. Please watch this video cast.
ctnID=$(docker ps -q --filter label=com.docker.swarm.service.name=router) && \
docker logs --follow $ctnID

In the test you can see, there is only one container for pingme. I have the same issue when I do docker service scale pingme=2.
Hope you this help. BTW, is there any other logs I could check ?
Cheers!

It look like there is something going wrong each time the routes are synced with Redis causing the connections to drop. I'll look into it, thanks for the details.

In terms of extra logs, you can only see the logs coming from the containers. If you want to fork the project you could easily add more debug logs all over the place to try and pinpoint the issue.

Let me know if I can help testing this further more. Per example, would different Redis (using redis:3.2.3-alpine at the moment) version change something?

No I think the issue is in the code when the router picks up the updated services from redis every few seconds. Won't have time to look into it properly until next weekend though I'm afraid.

thx for the follow up!

I've had a go but I was unable to reproduce. Did it run smoothly for several days before showing this behaviour? It could be related to the file handle leak mentioned in #17 if so.

I've made several improvements and upgrades to the project and is packages since you posted this issue - can you please try again using the latest tag and let me know if this is still happening?

Sure! Will do tonight.

Be careful with latest tag! 0.3.0 and latest shall be the same in this case. Personally, I push this way:
docker push $ENV_IMG_NAME_DATE
docker push $ENV_IMG_NAME_LATEST

Not sure what you mean about the tags. The latest tag is always the build using HEAD of the master branch. When I push a tag they are automatically built to the tagged commit using Travis. 0.3.0 is now locked at that tag and will no longer be pushed to unless i manually do so.

I'm still on the case :) As Docker 1.12.2 is out, I want to upgrade my nodes and test hard.

I get your point. The issue is that most folks that tries container will use latest by default. So I don't think it's best practice to have latest=master as master in your case is an active branch dev and not a stable branch. I think it would make more sense to testing something like V0.4.0RC then latest.

If you consider master as stable then life is good. Of course this is only my 5 cents :)

Oh right, I see what you mean. I think that makes sense; when I get time I'll move master to push the dev tag and make latest be the latest numbered stable git tag.

So far, tag latest is stable over Docker 1.12.2
Please push an official tag :)
I'll continue to report while messing nodes and other test stress. Cheers!

Ok 0.3.1 is now released (and the latest tag is now latest stable tag rather than latest commit)

Thanks for everything!


Different request JavaScript objects in loaders/actions and entry.server.ts handlers

What version of Remix are you using?
1.19.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
I want a way to recognize that the handleRequest call (in entery.server.ts) and loader call are related to the same user request. It looks like that remix creates a different request object for handleRequest and handleDataRequest.

attach a dummy id property at the beginning of a loader function.
try to load the page with the loader (SSR)
log the request object in the handleRequest function of the entery.server.ts
there is no id property

Expected Behavior
On each request (SSR, Loader, Action, etc) remix should create a single request object and send it everywhere.
Actual Behavior
Remix creates different request objects for each loader, action, entry.server.ts handler. It looks like it clones the request object before sending it to each handler function.

Hi @sergiodxa
My example was a hypothetical one for demonstration only. Of course, I would not change the request object.
I actually want to request an API in my loaders. I want a way to count the number of API request calls during a single SSR request.
As long as this bug exists, I don't have any proper solution. I don't want to use a custom server and getLoadContext for many reasons.
IMO devs should have a default identifier for the requests so they would be able to find out if a loader is called because of SSR request number 14.


add "type": "module"

Regarding to this issue https://github.com/afitiskin/redux-saga-routines/issues/73

Not sure about that due I have ERR_REQUIRE_ESM error after tests at side of my package.

done in an other way


conn_tracker.exe doesn't load conn_track.sys

after going through https://github.com/microsoft/ebpf-for-windows-demo/blob/main/connection_tracker/README.md#demo-steps on a windows 11 machine with eBFP-for-windows (v0.4.0) installed I get:
PS C:\Users\User\ebpf-for-windows-demo\x64\Release> .\conn_tracker.exe
Press Ctrl-C to shutdown
bpf_object__load for conn_track.sys failed: 9

looks like verification of ELF file passed:
netsh ebpf show verification conn_track.o sockops level=verbose

Verification succeeded
Program terminates within 545 instructions

and sys file has sections:
PS C:\Users\User\ebpf-for-windows-demo\x64\Release> netsh ebpf show sections .\conn_track.sys

                                    Size
             Section       Type  (bytes)
====================  =========  =======
             sockops    sockops     4684

                     Key  Value      Max
          Map Type  Size   Size  Entries  Name
==================  ====  =====  =======  ========
          lru_hash    56      8     1024  connection_map
           ringbuf     0      0   262144  history_map

running the following shows that ebpf isn't running
sc query ebpfcore
sc query netebpfext

Starting them manually with:
net start netebpfext

net start ebpfcore

net start ebpfsvc

and the demo works!