Install wget to avoid the busybox wget leaking defunct processes

When running busybox wget v1.31.x to request an SSL page, there is a leak of defunct processes that eventually could hit the limit for fork syscalls, leading to the unavailability of main registry process.
Installing wget from the alpine repository resolves the issue as this only affects the busybox distribution. Moreover, this should transparently resolve the issue for deployments
using wget as healthcheck/readiness/liveness probe.
xref: https://bugs.busybox.net/show_bug.cgi?id=15967
Closes #158

Please sign your commit.

Done!

This wget binary is only used during build of the Dockerfile; as far as I can see, it's not used in the final image, unless someone decides to use it (I see some issues linked that use it in a healthcheck).
All of that is custom, so I don't think we must install wget by default; it's not part of the main requirements of the image to run, and if needed should be installed by the user (extending the image)

Hi @theJeztah

unless someone decides to use it (I see some issues linked that use it in a healthcheck).
All of that is custom, so I don't think we must install wget by default; it's not part of the main requirements of the image to run, and if needed should be installed by the user (extending the image)

Hi @thaJeztah, thanks for the quick reply. I get it, and the best would be to have the wget busybox applet fixed. However, as of today, there's no way for this image to execute a healthcheck of the registry as no tool is available to run HTTP(s) requests, except the bugged wget.
Is there another way users can exploit to execute an in-container healthcheck without extending the image?
The following are leaked zombie processes left by the wget currently available in the image:
└ $ docker exec -it myreg ps aux
PID   USER     TIME  COMMAND
    1 root      0:00 registry serve /etc/docker/registry/config.yml
   40 root      0:00 [ssl_client]
   41 root      0:00 [ssl_client]
   74 root      0:00 [ssl_client]
   75 root      0:00 [ssl_client]
   88 root      0:00 [ssl_client]
   89 root      0:00 [ssl_client]
  102 root      0:00 [ssl_client]
  103 root      0:00 [ssl_client]
  104 root      0:00 ps aux

Is there any reason why you do in-container health checks and not leveraging some "higher leve/external/orchestration" means? I suspect the lure is the HEALTH Dockerfile instruction https://docs.docker.com/reference/dockerfile/#healthcheck?

Is there any reason why you do in-container health checks and not leveraging some "higher leve/external/orchestration" means? I suspect the lure is the HEALTH Dockerfile instruction https://docs.docker.com/reference/dockerfile/#healthcheck?

Docker/Compose health checks are similar to docker exec; the referenced executable needs to be available inside the container.

@schildbach oh, I'm not saying there is anything wrong with the request - in fact I've approved the PR - I'm just curious.
@thaJeztah the current wget binary is clearly DOS-ing the service when used in healthchecks. This needs fixing.

xref: https://bugs.busybox.net/show_bug.cgi?id=15967

Before I forget to mention; I think Alpine ships with its own fork of busybox (I recall that they carry various patches which may not (yet) have been accepted in upstream: https://git.alpinelinux.org/aports/tree/main/busybox?h=master); so it may also be worth opening a ticket in Alpine's issue tracker for this.

Why is busybox binary packed into alpine image kinda breaks my solar system brain -- I guess the galaxy brains that made this decision see something I can't.

I think the busybox binary in alpine is purely as a most-minimal "bootstrap" for the image; provide a minimal userland (a shell, and some common utilities provided by busybox), but adding Alpines package-manager to install the actual tools you may need after that.

Thanks @thaJeztah, in the specific case of the registry, it is the registry itself to be the PID1. Should we consider a fix in the registry also to handle the related signals?

Should we consider a fix in the registry also to handle the related signals?

Heh, just had a lengthy chat in our internal Slack discussing this case because it's really a bit of a grey area, and to some amount a matter of "semantics";

--init should normally be considered an "escape hatch" for a PID1 in a container misbehaving (if process is running as PID1, it should properly handle cleanup)
The grey area here is that registry (as far as I can see) is not "misbehaving"; it does handle what it's expected to do; run a registry, and handle that. It's not expected to do more than that, or not expected to handle processes it didn't create.
The situation happening here is that something went behind its back and shoved some processes underneath it, and those processes (seemingly) expecting something else to handle reaping.

From your earlier descriptions of busybox, I still feel it's a bug in busybox (which, after all, spins up the processes); pending that to be fixed, --init can be a proper workaround (or installing a different tool for the job, such as the apk add wget). From the perspective of the registry's core responsibility, adding that functionality to the registry code would be an "enhancement", not so much a bugfix, and (TBD) could be considered out of scope of its feature-set.
If the busybox maintainer consider it to not be a bug (perhaps it was not designed to be invoked this way?), and IF using the default wget is expected to be the default way to perform health-checks in this image, then an alternative could be to include tini in the container as PID1 to make sure the image has a reaper by default.

From your earlier descriptions of busybox, I still feel it's a bug in busybox

Agreed 100%. All the discussion here is to have a solution until the bug is fixed upstream and downstream by the distros (I'd say it's in the upstream busybox, if not already fixed in the next versions, as the same issue happens on the ubuntu's build).

If the busybox maintainer consider it to not be a bug (perhaps it was not designed to be invoked this way?), and IF using the default wget is expected to be the default way to perform health-checks in this image, then an alternative could be to include tini in the container as PID1 to make sure the image has a reaper by default.

yeah, the point for the registry is that it's actually used as PID1 by this image. Although I agree, it would still be like a 'safety' mechanism when PID1 inherits a defunct child process,  as in this case.
Should I close this PR or would we change it to something that is acceptable? I think some of the thoughts in this discussion should go in the issue at least, to inform other potential users making use of wget in a https-backed registry.

Should I close this PR or would we change it to something that is acceptable? I think some of the thoughts in this discussion should go in the issue at least, to inform other potential users making use of wget for healthchecking an https registry.

I think we should close it as I dont think we'll reach a consensus that will lead to merging this in.
Moving some of the discussed points to the original issue sounds like a good idea but I think it might not be needed as the links to this PR are displayed in the GH UI so I'd just leave it as is.


Clarity on "Forever" and "Time Period with no Deletion"

This Article doesn't provide clarity on difference if option is selected to Retain items Forever Vs. Option to select a time period(e.g. 7 Years) but no deletion after that specific period. Would there be any difference if Unlimited Archive is enabled for the mailbox?

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

ID: 30d08974-4cd1-4fab-7a59-17e5f8517566
Version Independent ID: 93e7f78f-6a94-1b90-1adf-70d2e266ce51
Content: Overview of retention policies - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/retention-policies.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@3novsan   Yes, it's recently come to my notice that this article assumes a policy of retain and then delete, and doesn't explain the other paths of retain-only, and delete-only. I'm working on addressing that gap, with engagement from engineering.

Page now updated for retain-only and delete-only retention policies, for both SharePoint and Exchange.


Update semanticdb-scalac to 4.3.14

Updates org.scalameta:semanticdb-scalac from 4.3.10 to 4.3.14.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "semanticdb-scalac" } ]

labels: library-update, semver-patch

Codecov Report

Merging #374 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #374   +/-   ##
=======================================
  Coverage   86.59%   86.59%
=======================================
  Files         135      135
  Lines        1485     1485
  Branches       36       36
=======================================
  Hits         1286     1286
  Misses        199      199

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a028b2b...44d7e7b. Read the comment docs.


[SourceKit] Introduce "source.lang.swift.expr.closure" in structure (SR-6116)

This PR introduces source.lang.swift.expr.closure in the structure produced by SourceKit. This can be used for tools such as SwiftLint to improve their reliability. One concrete example can be found on this issue.
It'd be also useful to know whether a closure is a trailing closure inside a function call, but I'm not sure if it's semantically correct to add this information on this structure, because it's something available in several declarations such as CallExpr and SubscriptExpr, not ClosureExpr. I'm also not sure how I would implement this: would I have to use hasTrailingClosure from the parent and check if the current closure is the last argument from the parent expression?
Resolves SR-6116.

cc @nkcsgexi


Add Department field to Person class

Add Department field to Person class, and change other relevant classes to match, according to #74

LGTM


Unauthorized issue

When I ran npm run register it said 401
Error: {"message":"401: Unauthorized","code":0}
at DiscordRequest (file:///C:/Users/kbrow/Downloads/discord-example-app/utils.js:36:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async InstallGlobalCommands (file:///C:/Users/kbrow/Downloads/discord-example-app/utils.js:48:5)
when I put everything in correctly in the .env file

Is the bot token or application id correct? Make sure these are correct.


Exporting LOD groups for static (non-skeletal) meshes - possible ?

Until recently Maya was the only app that supported LOD groups export into FBX (afaik):
https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2016/ENU/Maya/files/GUID-90307993-D898-4BFA-9E5E-D7F96EFAFAAD-htm.html
Then eventually someone figured out LOD groups support for Blender FBX exporter (via Empty and parenting/naming):
https://forums.unrealengine.com/community/community-content-tools-and-tutorials/119508-cyaoeu-s-bag-of-blender-tricks?146531-cyaoeu-s-bag-of-Blender-tricks=&viewfull=1
I am wondering if something similar can be added to glTF exporter, assuming glTF format supports such thing as several LODs per object.
Thanks beforehand

Going to close this issue, as we cannot implement here until the extension exists for glTF. Feel free to chime in on https://github.com/KhronosGroup/glTF/issues/1045 to give feedback on this. :)


Update ad-fs-requirements.md

'Sign-in as a Service' needs to be corrected to reflect 'Log on as a Service'

Great spot on the wording here @moondawggy, merging now.


Test CI against PHP 8.1 & fix deprecation

This super cool !
I'm wondering: Do we really need all the combinaisons in the matrix?
IMHO the following matrix is enough:
PHP 7.4 + SF 4.4 + lower deps
PHP 7.4 + SF 5.4
PHP 8.0 + SF 6
PHP 8.1 + SF 6
What do you think ?

Okay, I'm going to adapt it :)

Ready for review 👍

Thanks


Update eventing nightly (#2838)

Signed-off-by: Knative Automation<EMAIL_ADDRESS>Signed-off-by: Knative Automation<EMAIL_ADDRESS>

OCF Webhook is merging this PR


Update tutorial-ingress-controller-add-on-existing.md

It apparently seems like creating a registration with name "microsoft.containerservice" irrespective of making it "Microsoft.ContainerService".  No clue why this is.  But then the document should reflect the lower case of the namespace "microsoft.containerservice" while querying for the status for the registration or else you don't get any status result.
Can this be made better?  Why is the name space "microsoft.containerservice" in lowercase while all others are in pascal casing?

@srikanthnd : Thanks for your contribution! The author(s) have been notified to review your proposed change. @caya

Hi @mscatyao - Would you review the proposed update?
Also, could you change the article's metadata author attribute to your GitHub user name? Automated notification of an update submitted through the public repo is based on this value. Thanks.

@ktoliver LGTM.


Initial commit

See Readme.md for more details.
Signed-off-by: Blake Devcich<EMAIL_ADDRESS>

Add copyright headers


feat: align logging format hooks server and

Pretty

Json

Open question:

zap produces time format with floating point, nevertheless, it should be int64
for zap pretty mode there is no way to format custom props away from JSON at the end of log message

TODO:

WunderNode should favor options.logger.level - zap instance should be shared, abstract logger should be separate for the node and cli

results look nice

You can introduce a custom time encoder https://blog.sandipb.net/2018/05/03/using-zap-creating-custom-encoders/

Pretty logging does not share the same format and style.

In node, we log as a combination of text + JSON
In node, we don't work with colors.

How did you ensure that we use the same log level between both components?
As @jensneuse suggest it would be nice if we have a different log prefix for each component

{ "component": "server" }

INFO: SERVER: ...

Pretty logging does not share the same format and style.

Yeah, with the current customization options of Pino and Zap
It is not possible to fully align this

In node, we log as a combination of text + JSON

that is one of the problems, as zap does not support logging additional keys in a different way at least with a standard console encoder
I believe we could solve it - by writing a custom log encoder - but this was out of the scope of this task

In node, we don't work with colors.

Partially do, the log level is colored
We could colorize output also, but I haven't added that

How did you ensure that we use the same log level between both components?

We don't have to, it is the responsibility of the user to specify log level of WunderNode and WunderGraph Server via the options
But another breaking change - is that loglevel flag of CLI - should be responsible only for CLI log level, neither node nor server, as they use their own config

As @jensneuse suggest it would be nice if we have a different log prefix for each component

{ "component": "server" }

Yeah, agree, this will involve more work, I propose extracting it into a separate issue as well as environment variables refactoring

LGTM

What's the status here? The PR has been open for too long.


Adopt Gatsby

While Next.js can handle static sites, we've had a few issues with it, notably a performance hit at runtime. Gatsby being fully intended for high-performance static sites makes it a great technical fit for the Shields frontend. The createPages() API should be a really nice way to add a page for each service family, for example.
This migrates the frontend from Next.js to Gatsby. Gatsby is a powerful tool, which has a bit of downside as there's a lot to dig through. Overall I found configuration easier than Next.js. There are a lot of plugins and for the most part they worked out of the box. The documentation is good.

Links are cleaner now: there is no #. This will break old links though perhaps we could add some redirection to help with that. The only one I’m really concerned about /#/endpoint. I’m not sure if folks are deep-linking to the category pages.
There are a lot of enhancements we could add, in order to speed up the site even more. In particular we could think about inlining the SVGs rather than making separate requests for each one.
While Gatsby recommends GraphQL, it's not required. To keep things simple and reduce the learning curve, I did not use it here.
Close #1943
Fix #2837

To do before merging:

[ ] Get frontend tests working again
[ ] Fix coverage
[ ] See if there are other dependencies which can be removed
[ ] Test/fix Heroku deploy
[ ] Test/fix Now deploy
[ ] Test/fix self hosting
[ ] Fix or remove former use of NavLink
[ ] Redirect old # links on index page

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against 994dde740bd6bab6095914b5324c2dae57ac5b73

@mbrandau Are you up for giving this a try?

When changing categories, seems to respond faster than the current site:
http://shields-staging-pr-2906.herokuapp.com/
vs.
https://shields-staging.herokuapp.com/

When changing categories, seems to respond faster than the current site:
http://shields-staging-pr-2906.herokuapp.com/
vs.
https://shields-staging.herokuapp.com/

Yeah I think I'm observing the same behavior, although in all honesty both are pretty snappy 😄
Two observations:

The Shields logo in the browser tab is black and white in this PR staging app

In the current site, after quickly hopping around between a few categories, several of the categories started to take a noticeably long time to render the badges, but I've been able to reproduce that in this PR staging app 👍

Could you clarify this?

Sure! I was switching between categories fairly quickly in both apps in an attempt to do an eyeball performance comparison. After some time of doing that in the current site (https://shields-staging.herokuapp.com/) the listings on some of the category pages appeared to not be rendering (they eventually did render, but took 30+ seconds)

This PR has the same problem, or no?

This PR does not have the same problem. Could've just been a fluke, but was only happening on https://shields-staging.herokuapp.com/

Can you give a bit more info on how will the routing work once we're deployed on GH pages? It seems like in order to do away with the client-side # style links, we need to add an extra build step to the deploy process to build static pages for each URL or something?

gatsby build writes out all those files:
public
├── 0-67fa5a5264bb654b8669.js
├── 0-67fa5a5264bb654b8669.js.map
├── 0-ad913e07e45d935c6172.js
├── 0-ad913e07e45d935c6172.js.map
├── 2-660cc00aea5bf7e39cfd.js
├── 2-660cc00aea5bf7e39cfd.js.map
├── 2-cb227f2fc74ce66d55d8.js
├── 2-cb227f2fc74ce66d55d8.js.map
├── app-14d7ce459d4ac392693f.js
├── app-14d7ce459d4ac392693f.js.map
├── app-9e1789bcf880397fdde9.js
├── app-9e1789bcf880397fdde9.js.map
├── category
│   ├── activity
│   │   └── index.html
│   ├── analysis
│   │   └── index.html
│   ├── build
│   │   └── index.html
│   ├── chat
│   │   └── index.html
│   ├── coverage
│   │   └── index.html
│   ├── dependencies
│   │   └── index.html
│   ├── downloads
│   │   └── index.html
│   ├── funding
│   │   └── index.html
│   ├── issue-tracking
│   │   └── index.html
│   ├── license
│   │   └── index.html
│   ├── monitoring
│   │   └── index.html
│   ├── other
│   │   └── index.html
│   ├── platform-support
│   │   └── index.html
│   ├── rating
│   │   └── index.html
│   ├── size
│   │   └── index.html
│   ├── social
│   │   └── index.html
│   └── version
│       └── index.html
├── chunk-map.json
├── component---frontend-components-main-js-438efc3da2edda687363.js
├── component---frontend-components-main-js-438efc3da2edda687363.js.map
├── component---frontend-components-main-js-ea8ec189fb5a125c3404.js
├── component---frontend-components-main-js-ea8ec189fb5a125c3404.js.map
├── component---frontend-pages-endpoint-js-21b461837339c365660b.js
├── component---frontend-pages-endpoint-js-21b461837339c365660b.js.map
├── component---frontend-pages-endpoint-js-7191d3f0fc948a41bbf1.js
├── component---frontend-pages-endpoint-js-7191d3f0fc948a41bbf1.js.map
├── component---frontend-pages-index-js-c3db22348ada5bbbd9da.js
├── component---frontend-pages-index-js-c3db22348ada5bbbd9da.js.map
├── component---frontend-pages-index-js-d5d233367cb92aa4606e.js
├── component---frontend-pages-index-js-d5d233367cb92aa4606e.js.map
├── endpoint
│   └── index.html
├── index.html
├── pages-manifest-3aebc6c37146c164f6ea.js
├── pages-manifest-3aebc6c37146c164f6ea.js.map
├── pages-manifest-d8d2c9f92f905bee0160.js
├── pages-manifest-d8d2c9f92f905bee0160.js.map
├── pages-manifest-efd19252f95bb7a71410.js
├── pages-manifest-efd19252f95bb7a71410.js.map
├── static
│   └── d
│       ├── 117
│       │   └── path---category-rating-046-2e3-KdA7G0YPKQTjYGAyoqXB4cvtk.json
│       ├── 132
│       │   └── path---category-social-06-c-ae9-4VZRdurTidfJEQBJzS8VIf9PQk.json
│       ├── 173
│       │   └── path---index-6a9-NZuapzHg3X9TaN1iIixfv1W23E.json
│       ├── 253
│       │   └── path---category-version-cf-1-a18-gXHyDTzYNgar0wLLw0WZixpAj5c.json
│       ├── 284
│       │   └── path---category-downloads-ac-6-ad2-i1qVAXGTJHbgxNgVU8X7VTyJMg.json
│       ├── 383
│       │   └── path---category-size-7-c-5-f3c-IA7jm7CtmkAoZxX7H1UoYKKqU.json
│       ├── 418
│       │   └── path---category-funding-c-9-c-3d6-fXFX1kL0ODtgGpsFPmDeGpBViw.json
│       ├── 420
│       │   └── path---category-monitoring-1-e-4-713-bEZ1Ow7ciXXVUOK28ye6ImBRmeM.json
│       ├── 428
│       │   ├── path---category-platform-support-54-b-1cb-Z5tIFulGwp1r5jnYKKaRp0ozYg0.json
│       │   └── path---endpoint-a-3-a-f9f-NZuapzHg3X9TaN1iIixfv1W23E.json
│       ├── 485
│       │   └── path---category-issue-tracking-e-8-e-5e4-2rlEZhPS9BHCJs3cEHkP5Hn8WQA.json
│       ├── 600
│       │   └── path---category-dependencies-3-f-4-f6d-Ab6kijLqMLCJfo5PPjulSt60K8.json
│       ├── 678
│       │   └── path---category-other-c-96-41b-RndZH3c3mZfk6hjfU6H8nEoka3I.json
│       ├── 69
│       │   └── path---category-chat-9-aa-fda-Ao51OaMIHXU8mgnpMIOxT7x2kVc.json
│       ├── 792
│       │   └── path---category-activity-571-37c-tsoCfBAcVbrQK2D7rSGCYN11YQ.json
│       ├── 88
│       │   └── path---category-analysis-36-e-d1e-JbegFHdHBYgMoxjX2zbzP05xw.json
│       ├── 955
│       │   └── path---category-license-77-a-1b3-2Fwgu2pA9WVHICxqtSBKuQVYwP8.json
│       ├── 972
│       │   └── path---category-coverage-ffc-771-getZDHJLqCIMepXXS3Ctk7Uqbso.json
│       └── 976
│           └── path---category-build-94-b-71c-AvOamVOIE8vKzzf7fxl1YlaO4.json
├── webpack-runtime-45ab0c5fe180a44c9a6e.js
├── webpack-runtime-45ab0c5fe180a44c9a6e.js.map
├── webpack-runtime-76e0ac706c7f4f18b05a.js
├── webpack-runtime-76e0ac706c7f4f18b05a.js.map
├── webpack-runtime-b3639ec9365f37fed072.js
├── webpack-runtime-b3639ec9365f37fed072.js.map
└── webpack.stats.json

Whichever link you load first, that's the index.html that gets loaded. Then, when you switch routes, the route change gets intercepted on the frontend, some magic happens to load whatever new needs to be loaded, and the page re-renders, without actually loading the other index.html page. It's pretty cool.

I can't make heads or tails of what's going on with the Now deploy. I've experimented with a bunch of different values in .nowignore.
I opened a discussion thread: https://spectrum.chat/zeit/general/troubleshooting-source-file-selection-in-v1~8dc07b08-99ac-4a02-bfc6-6d40d5e44792

Feel like we could review and merge this. I’d like to get the Now build working again quickly, though I don’t think that needs to block. I sometimes get a little weary of Now. It can be a bit unstable, hard to troubleshoot, and is poorly documented.
I feel like the product is improving and changing a lot so I’m not writing it off, and I do use it a lot. Though I find products frustrating when I can’t solve my own problems 🤔

There is a bit of next-specific code left in the dangerfile: _document.js is used by convention by Next

Fixed.

I'm getting TypeError: category is undefined trying to use search or suggest

Thanks for finding that. Should be fixed.

I'm going to be out of my depth on most of the changes in this PR, but going to take a look anyway (if for no reason other than getting myself more familiarized with this part of the codebase)
Semi-related question: Do we have docs anywhere that cover where/how we're using Next.js (and now Gatsby), Now, etc.?

Semi-related question: Do we have docs anywhere that cover where/how we're using Next.js (and now Gatsby), Now, etc.?

No, not really. Two good follow-on tasks would be:

Write a few sentences, probably in the code walkthrough, about how we use Gatsby to build the frontend, and link out to a tutorial and to this PR which includes the basic wiring. We could also mention styled-components and the entirely separate transpilation pipelines for unit tests and linting.
Add a little more context at the top of the self-hosting doc that mentions the three deployment targets we support: Docker, Heroku, and Zeit Now. Probably that should include a short explanation of the build process for each one, and how to validate it.

I've finished going through the files (my inline questions, etc. have already been addressed), and am just poking around in the PR staging app UI now.
I just noticed one minor thing, probably off topic since this occurs in prod too, but when configuring a static badge after I select a color, part of the text of that color gets cut off if I pick a longer color (like bright green):

Yea, that doesn't look great. That whole component could be improved. Maybe it could build off some of the work in the new builders.

Great. Yea, that happened when I fixed the favicon. Will look into it…

Looks like that fix worked.

It's live!


Extract LinkedHashMap from LruCache

LruCache is a thin wrapper around LinkedHashMap now.
LinkedHashMap now has iterator which is double-ended iterator.
fmt is implemented using iterator now.

Just like to say: yesssss
LinkedHashMap is my favourite data structure and now I can say Rust is a real programming language.

Updated PR with:

better example, describing iteration order (is that what you requested?)
removed all deprecated code
removed all unstable markers

Updated with plural "Examples" and minor example and test tweaks.

Unless you have an argument otherwise, I think the interface for interacting with the linked-ness should either be the stack (push/pop/peek) or deque (_front, _back) interface.

Although get_refresh is interesting...

Updated patch with issues fixed.

Updated patch with .keys() and .values() iterators.

Updated the patch with bunch of issues reported by @apasel422.

Is anything else needed to merge this PR?

This LGTM, @apasel422 does this look good to you?

@Gankro: Yup. I suspect changes in Rust master will break some things, but that can be addressed with a subsequent PR.

:boom: :heart:

I'm trying to implement iter_mut, and I have trouble. Have a look at the code:
https://github.com/stepancheg/collect-rs/commit/edf6dae12346221c0c218d148621a43ec165428c#diff-9312c4317d6f1b3401488758a7a7a077R673
It should not work, because iter_mut mutably borrows map, and map.get(..) needs to borrow map again. But test passes.
Moreover siguatures of struct IterMut and fn iter_mut are identical to those in HashMap, however, if I replace LinkedHashMap with HashMap, compilation fails as I expect.
What have I missed?

You probably need to include a ContravariantLifetime for the 'a in the struct.

@Gankro that helps. Should this marker be also added to Iter struct? I see, slice::Iter has it.

Yeah, if a type has a lifetime that isn't used in the struct, you should use a marker so that it is.


Dockerfile for publish-spa

What Happened?
Hello dear friend,  I'm writing a project for my university. I need to publish my website using Gitlab ci. And for this I am writing a dockerfile and my image takes up a lot of space of 5 GB. If I write this command in docker. My image is starting to take up a lot of space. How can I reduce the space occupied?
Reproduce the Bug
FROM ubuntu
RUN mkdir publish-spa
COPY .  /publish-spa
RUN apt-get update && apt-get install curl -y & apt-get install -y -q --allow-unauthenticated git sudo && sudo apt install default-jdk
RUN curl -L -0 https://github.com/clojure/brew-install/releases/latest/download/linux-install.sh && chmod +x linux-install.sh && sudo ./linux-install.sh
RUN curl -sL0 https://raw.githubusercontent.com/babashka/babashka/master/install && chmod +x install &/install
RUN curl -sSL https://deb.nodesource.com/setup_18.x | sudo bash -
RUN sudo apt install -y nodejs && node --version
RUN cd publish-spa && npm i -g
RUN npm install -g -y yarn
RUN git clone https://github.com/logseq/logseq && cd logseq & git checkout 0.10.6
WORKDIR /logseq
RUN yarn install --frozen-lockfile && yarn gulp:build && clojure -M:cljs release publishing
RUN yarn autoclean -i && yarn autoclean -f && yarn cache clean
WORKDIR /
RUN cp -r logseq publish-spa
WORKDIR /publish-spa
RUN npm install @logseq/nbb-logseq
Expected Behavior
No response
Desktop or Mobile Platform Information
No response
### Tasks

Hi. I don't use docker with publish-spa so the best I can offer you are some guesses. After clojure -M:cljs release publishing is called you could try deleting logseq's node_modules to free up some disk space. You could also try the docker config at https://github.com/logseq/publish-spa/pull/29/files but it claims that it's size is ~7G

Hi. Since the publish-spa only use the static output of the logseq-lgoseq, a multi-stage Dockerfile can help reduce the image size. The final image size is at ~700 MB (alpine) and I've published it in ghcr.io. See https://github.com/L-Trump/logseq-publish-docker.

Closing this as this should be solved by logseq-publish-docker


TestStackRemove is flaky

12:42:59 ----------------------------------------------------------------------
12:42:59 FAIL: docker_cli_stack_test.go:103: DockerSwarmSuite.TestStackRemove
12:42:59
12:42:59 [d319f74f7d4ba] waiting for daemon to start
12:42:59 [d319f74f7d4ba] daemon started
12:42:59
12:42:59 docker_cli_stack_test.go:117:
12:42:59     c.Assert(strings.Split(strings.TrimSpace(out), "\n"), checker.HasLen, 2)
12:42:59 ... obtained []string = []string{"Nothing found in stack: testdeploy"}
12:42:59 ... n int = 2
12:42:59
12:42:59 [d319f74f7d4ba] exiting daemon
12:43:01
12:43:01 ----------------------------------------------------------------------

In win2lin there seems to be problem with all TestStack* https://jenkins.dockerproject.org/job/Docker Master (win2lin)/1377/console
@dnephin

Yup, but I've encountered it on experimental.

@tonistiigi Those failures are coming from s.AddDaemon() which is used by every single swarm related test. I think it was just a coincidence that it started to fail when it go to the stack deploy tests. The issue was something with that node, not the test.

@LK4D4 Do you have a link to the build with those failures?
The failure seems to be that the stack never started, which would mean that all the stack tests would be equality as flaky.

@dnephin no, sorry :/ I'll post here if see new.

@dnephin The difference then seems to be that all other tests are behind a build tag.
TestStackRemove is different, I've seen that fail outside win2lin as well.

Ah, thanks, I missed that. I can add !windows.

@dnephin Found https://jenkins.dockerproject.org/job/Docker Master/label=rhel72 && overlay/8306/console for TestStackRemove

Sounds like #30643 fixed this

@dnephin Seems #30643 only fixed the win2lin case. Happened again in #31257
https://jenkins.dockerproject.org/job/Docker-PRs/40617/console
23:11:12
23:11:12 ----------------------------------------------------------------------
23:11:12 FAIL: docker_cli_stack_test.go:105: DockerSwarmSuite.TestStackRemove
23:11:12
23:11:12 [d04ff5cdd87db] waiting for daemon to start
23:11:12 [d04ff5cdd87db] daemon started
23:11:12
23:11:12 docker_cli_stack_test.go:119:
23:11:12     c.Assert(strings.Split(strings.TrimSpace(out), "\n"), checker.HasLen, 2)
23:11:12 ... obtained []string = []string{"Nothing found in stack: testdeploy"}
23:11:12 ... n int = 2
23:11:12
23:11:12 [d04ff5cdd87db] exiting daemon
23:11:14
23:11:14 ----------------------------------------------------------------------
23:11:14 PASS: docker_cli_stack_test.go:17: DockerSwarmSuite.TestStackRemoveUnknow


Remove key-menu.nvim

Repo URL:
https://github.com/linty-org/key-menu.nvim
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR! Fixes #918.


Probability density/mass functions from jax.scipy.stats not supported on Metal

Description
I am attempting to use JAX on Metal (on a M1 Pro chip) to model discrete (count) data. I've installed the latest version jax-metal 0.0.6 using pip as detailed here.
The installation seems to have worked overall as I can perform basic Jax array operations on GPU. However, when I try to compute the (log-)PMFs/PDFs of random variables which are defined in terms of the (log-)Gamma function I get errors like the one below which seems to indicate that the lax.lgamma function is not supported under the hood on M1 metal.
I would categorize this as essential functionality for a wide class of probabilistic machine learning models so I am filing this as a bug. Note that following functions (among others) are broken as a result:

jax.scipy.stats.binom.logpmf
jax.scipy.stats.nbinom.logpmf
jax.scipy.stats.poisson.logpmf
jax.scipy.stats.dirichlet.logpdf
jax.scipy.stats.beta.logpdf
jax.scipy.stats.gamma.logpdf
...

>>> jax.scipy.stats.binom.logpmf(1, n=2, p=0.5)

jax.errors.SimplifiedTraceback: For simplicity, JAX has removed its internal frames from the traceback of the following exception. Set JAX_TRACEBACK_FILTERING=off to include these.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/scipy/stats/binom.py", line 31, in logpmf
    gammaln(n + 1),
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/scipy/special.py", line 44, in gammaln
    return lax.lgamma(x)
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/lax/special.py", line 46, in lgamma
    return lgamma_p.bind(x)
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/core.py", line 422, in bind
    return self.bind_with_trace(find_top_trace(args), args, params)
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/core.py", line 425, in bind_with_trace
    out = trace.process_primitive(self, map(trace.full_raise, args), params)
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/core.py", line 913, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/Users/ljb80/.virtualenvs/jax-metal/lib/python3.10/site-packages/jax/_src/dispatch.py", line 87, in apply_primitive
    outs = fun(*args)
jaxlib.xla_extension.XlaRuntimeError: UNKNOWN: <stdin>:1:0: error: failed to legalize operation 'chlo.lgamma'
<stdin>:1:0: note: see current operation: %0 = "chlo.lgamma"(%arg0) : (tensor<f32>) -> tensor<f32>

System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.26
jaxlib: 0.4.23
numpy:  1.26.4
python: 3.10.6 | packaged by conda-forge | (main, Aug 22 2022, 20:38:29) [Clang 13.0.1 ]
jax.devices (1 total, 1 local): [METAL(id=0)]
process_count: 1
platform: uname_result(system='Darwin', node='PHS027794', release='23.4.0', version='Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000', machine='arm64')

chlo.lgmma is not supported. We will look into add the support.

Conversion pattern for chlo.lgmma  has been added into jax-metal 0.0.7. Reopen the issue if otherwise.


Is there a repo of codes correspond to the tutorials thus I can test directly

Hi, thanks for your great tutorials.
I wonder if there is a repo of the codes used in the tutorials.
Since sometimes I just want to have a quick run/test instead of manually creating the package and coping the code step by step.

Hi @clalancette , Thanks for your clarification. I was not aware of the maintenance efforts before, since I thought we have no problem compiling and testing before updating the tutorial.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2824

Questions ?
Please refer to the Backport tool documentation


typo

Firstly great document.  I have a few other question I will post separately, but there is a typo that is bothering me:-
Under - Failure of a dependent service

Note that high availability decreases throughput and increases latency because write operations must also upedate any secondary copies.

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

ID: cefa78da-afbb-5529-d707-b158d991cb16
Version Independent ID: 64342775-2746-0e51-9aba-253074530f27
Content: Disaster recovery for Azure applications
Content Source: docs/resiliency/disaster-recovery-azure-applications.md
Service: architecture-center
GitHub Login: @adamglick
Microsoft Alias: pnp

Thanks for reporting this!


update for two RD

Docs Build status updates of commit ee36ab7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

rd/media/profiles/gill-cleeren.jpg
:white_check_mark:Succeeded

rd/thomas-martinsen.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Adjust the Title + text of the idpManagement page

Current Behavior

Title and text seems to be temporary and need to be adjusted
Expected Behavior

Title: "Identity Provider configuration"
Text:

This page provides the functionality to manage user authentication for your company.
Upon registration, we have established an Identity Provider (IDP) with a single user entry for the administrator. Many organizations already maintain their own IDP, where users authenticate using their established company user IDs and familiar login interfaces. In such cases, you may prefer to leverage your existing company IDP. You can create and manage the necessary federation on this page.

Steps To Reproduce

Open the page https://portal.int.catena-x.net/idpManagement
read the title + text above the picture.

Hi @MaximilianHauer
I tested this issue it's working fine. Can you close this ticket.
Attached Screenshot for references:


Creating BirdFont 1.0 Cask

Hi!  Thanks!
Travis is failing because it wants the last word of the file to say end (this is missing the "d").

Hi, thanks for info. I got it. It's my first Github commit. I had small problem with environment, but actually I think I'm in!

Welcome!
Can you squash these?

Thanks. Merged as c7d5f0e.


Add a script to clone and build the docs from the monorepo

For #26

@tmeasday Pls take a quick glance at the 302 redirects

Is this deployed somewhere? Seems reasonable on the surface


Add column headers (VB)

Contributes to #25486

Adds column headers
Or converts tables into columns

Preview link for columns
Preview link for data matrix with code fencing

This LGTM @gewarren
One note on the columns: @tdykstra had come up with a neat trick to use one row, and put line breaks between each element in the same column. The presentation was the same as the standard column layout, but it was a lot less verbose. You can see an example here.

That's nifty! The only problem is that you have to read down then across instead of across then down.


Make column names configurable

columns like  speaker, age, gender are used by nkululeko but often present in the data but with different names.
Would be easy to make this confugurable, e.g.
[DATA]
databases = ['my_data']
my_data.colnames = {'speaker':'Participant ID', 'gender':'sex, 'age': 'Age}

Done in 0.68.2


Slow Dispatch Testing for DPRINT

Currently DPRINT tests are fast dispatch only, but DPRINT should be dispatch-agnostic. Enable the tests on slow dispatch and make sure everything passes

PR: https://github.com/tenstorrent-metal/tt-metal/pull/4326 implements this. Tests are passing with slow dispatch as well, with the exception of the hanging test. Decision is to re-enable that after #4363 is completed, so closing this issue


[Feature] Automatic switchover

When using a notebook, and you often have to switch locations (sometimes with available wired networking, sometimes without), networkmgr should automatically switch between wired and WiFi network interfaces, and prioritize a wired interface, if connected. If a network interface is setup with DHCP, this should be handled automatically. Nameserver and default route should also be automatically adjusted to use the desired interface.
Today, you have to manually disable one interface, and sometimes the other interface too and re-enable the desired interface to get it working. In an modern, dynamic working environment this is not very convenient.

Note to myself devd should handle this with
notify 0 {
	match "system"		"IFNET";
	match "type"		"LINK_DONW";
	media-type		"ethernet";
       *
}

and
notify 0 {
	match "system"		"IFNET";
	match "subsystem"	"!(usbus|wlan)[0-9]+";
	match "type"		"LINK_DONW";
	*
};

Completed


Remove redundant code

What does this PR do?
The removed code was removed to export the models when --monolith and use_past=True are both passed. Since their use is removed the code is no longer required.
Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


bug report

if you ever use zipline as a sharex image host and try to upload 2 mp4 files at the same time, it will end up crashing your entire server,

how to reproduce:
Have 2 Mp4 files
Upload both of them at the same time
And watch it crash and burn

Please try to use more descriptive names for bug reports. One example could be: Uploading multiple files at once crashes server.
you could also check if an error is sent in console.

Not able to reproduce with the given details, I need the file size of both videos to look into this issue.

how to reproduce, take 2 mp4 files of 40 to 41 mb size and try to upload both of them at the same time using the upload feature on the website, not sharex the website, and if you try to refresh you will get a 521 on cloudflare If you use cloudflare, which i do

Msg to repopen

Are there any logs in zipline after uploading these files? Also keep this issue open.

Why does this keep closing, Also i need to check the logs, how would i do that

Why does this keep closing
Don't click the not-green button that says "Close with comment", instead click on the green button which just says "Comment".

Also i need to check the logs, how would i do that
If you are using docker/docker-compose head over to the directory where zipline is and run docker-compose logs zipline and copy it over here (preferably the entire thing, unless you know what to send over)

While we are getting more information on this, could you also list your servers specs like its RAM, CPU, Operating System, etc?

The operating system is ubuntu 20.04  it has 1 vcore and has 1gb of ram, it seems to be running very well as its handeling about 5 people every once and awhile

the logs are this right here
https://www.toptal.com/developers/hastebin/unedohabep.properties
it seems to have outputted alot of randomness of which i cant read, it seems to be some errors inside of the logs

I'm not seeing anything where you upload a video, could you upload a video then upload the logs over here? Thanks

Yes. i will. i will comment the new information after i test this

weird. seems to have not happend this time. maybe it was a one off issue?

I will close this issue, but if it happens again feel free to open it and send the logs again.


Docker: build from local code

This PR slightly adjusts the main Dockerfile to match the one in the docker folder to build from local code rather than pulling from git.
Currently if automated builds are configured, the latest tag will always be what's in the repository but if a tag is created on the main repo, when it builds on Docker Hub it will just pull in the latest code in the Dockerfile.
TL;DR This allows automated tagged builds on Docker Hub.

@Roasbeef Could you please merge this and setup automated builds on dockerhub?

@tyzbit still relevant?
cc @guggero

Yes, this PR is still relevant IMO.  When you clone a git repo you expect builds from the repo to use the code in the repo.  That is not the case today without this PR.  Additionally, building images on Docker Hub would make LND more accessible to people, and add signal to the noise that's already on there by having an "official" image.

The "main" docker file (in the root directory) now allows specifying a specific commit or branch, which allows for automated builds on Dockerhub with the checkout build argument.
If you want to build from source, you can use the "dev" docker file that is located in docker/lnd, as @roasbeef pointed out.


Displaying prices and sizes in tools

helix-trace assumes that prices have a scaling factor of 10000 and two decimal digits and that sizes have a scaling factor of 1 and no decimal digits. This works for Nasdaq and Parity until 0.6.0, but Parity 0.7.0 introduces support for configurable number of decimal digits for both prices and sizes.
I'm working on a patch to update the Parity PMD support to Parity 0.7.0. What's your preference for displaying prices and sizes in helix-trace? I can think of two options:

display the values as-they-are without scaling, or

add command line options to specify the number of decimal digits for prices and sizes.

Closing this due to lack of activity.


Misleading sends and sends.typed metrics

Problem
The metrics sends and sends.typed produced by Sorbet with the option --metrics-file can be really misleading as they give a false idea of how much sends are actually typed.
Should we count Sorbet signatures related methods in sends?
Sorbet counts sig, void etc. as sends:
# typed: true

sig {void}
def foo; end

Produces the following metrics:
  {
   "name": "types.input.sends.total",
   "value": 2
  }, {
   "name": "types.input.sends.typed",
   "value": 1
  }

Should we only consider typed >= true files?
The sigil used can also badly impact the metrics collection.
For example, with typed: true:
# typed: true

sig {void}
def foo
end

def bar
end

foo
foo
bar
bar

Sorbet produces:
  {
   "name": "ruby_typer.unknown..types.input.sends.total",
   "value": 6
  }, {
   "name": "ruby_typer.unknown..types.input.sends.typed",
   "value": 3
  }

While with typed: false is does not count any call.
Expected behaviors

I would expect for Sorbet to produce accurate sends and sends.typed metrics whatever the sigil used.

I would also expect Sorbet to not count sig, void etc calls as sends or sends.typed.

I pin-pointed the problem to this if: https://github.com/sorbet/sorbet/blob/master/main/pipeline/pipeline.cc#L50-L52. I wonder if we could extract the metrics computation to be ran even if the file is typed < true?

Given that this is now at least documented, I'm going to close it:
https://sorbet.org/docs/metrics#call-site-level-typedness
I'm down to add a new metric for all calls, even in typed: false files, but i'd prefer to give it a new name so that our graphs don't have a big discontinuity in them.


Set-SFTPFile error message is not helpful at all

Set-SFTPFile command needs only target folder provided with -RemotePath parameter. If you provide target path with target file name (like you do when you're using mv or cp commands in Linux) it gives strange error message:
Set-SFTPFile : /home/azureuser/certificates/cert.p7b does not exist.
At C:\Users\azureuser\Desktop\MomAgent_Certificate_Signer.ps1:64 char:3
+   Set-SFTPFile -SessionId $SFTPSession.SessionID -LocalFile "D:\Certs ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (SSH.SftpSession:SftpSession) [Set-SFTPFile], SftpPathNotFoundException
    + FullyQualifiedErrorId : /home/azureuser/certificates/cert.p7b does not exist.,SSH.SetSftpFile

It pretty obvious that target does not exist because we're going to copy it there.
Example command to reproduce the error:
Set-SFTPFile -SessionId $SFTPSession.SessionID -LocalFile "D:\Certs\cert.p7b" -RemotePath "/home/user/certificates/cert.p7b" -Overwrite
I guess it happens because Powershell command interprets cert.p7b like target folder name that exists but that error message gave me an hour of different thoughts before I took a look at my old script where I was using the right command.

problem is that I test if the target exist, can not validate for user error when he gives a name with a "." since you can have dir names with dot.

I just hit this issue as well. Pull request submitted to update the text to indicate that it was a directory that was not found as that would help tip off the user that the parameter is testing for a directory not a file.


Combine numerical and image data

[x] get output of different layers
[x] find what the model is focusing on
[x] combine brain measurements with images --> use dense layers and logistic regression for numerical data

Multilayer input in a CNN is not really working -> Alternative: try an Ensemble of a numerical model (e.g. ExtraTree which can calculate probabilities as well) and the CNN. Only using brain values will probably not improve the model. Could combine it with a numerical model that contains 1 cognitive test result.


How could I transform the canvas

update:
solution: using css:
#heatmap{  -webkit-transform: skew(-45deg); -moz-transform: skew(-45deg); -o-transform: skew(-45deg); -ms-transform: skew(-45deg); }
Hi ,
I intend to display a heatmap for multiple floors of a building. Therefore I need to transform the rectangular heatmap to a parallelogram. I thought the following code could help, but it didn't work. Any help would be appreciated!
`canvas.className = 'heatmap-canvas';
this._width = canvas.width = shadowCanvas.width = config.width || +(computed.width.replace(/px/,''));
this._height = canvas.height = shadowCanvas.height = config.height || +(computed.height.replace(/px/,''));

this.shadowCtx = shadowCanvas.getContext('2d');
this.ctx = canvas.getContext('2d');
this.ctx.save();
this.ctx.rotate( (Math.PI / 180) * 90);`

have you tried using css and selecting .heatmap-canvas for a CSS transformation?

solution is in the issue content:
#heatmap {
   transform: skew(-45deg);
}


Failed to get current schema version from cassandra when starting cadence

We had a cadence pod in our k8s cluster fail. The pod repeatedly attempts to restart but cadence fails to start.
The error message is
Incompatible versionsunable to read cassandra schema version keyspace: cadence error: Failed to get current schema version from cassandra

The log from the pod is as attached.
logs-from-cadence-in-cadence-6fbbf97d58-6v5m9.txt

Never mind. This is a cassandra issue.

Could you tell how to fix the cassandra issue. Cause I also meet this issue too.

I'm afraid I don't remember how we fixed it. It was likely that we redeployed cassandra.


[BUG] Bloxstrap new icon issue.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?

so i'm in the 2.8.0 developer beta. i know you guys won't provide support for this but i am a developer. So looks like @pizzaboxer forgot to put the new bloxstrap icon in the taskbar. the new icon is everywhere but not in the taskbar icon. Let's hope this doesn't make it into Stable Release!
Bloxstrap Log
N/A

You're NOT a developer.

vro is not a dev

Keep dreaming on being a developer 😃

This is not a developer beta and how did you get access to "2.8.0"?

This is not a developer beta and how did you get access to "2.8.0"?

https://files.pizzaboxer.xyz/bloxstrap-debug/preview/Bloxstrap-v2.8.0-rc1.exe

Ok i realized i was not supposed to share that link.
Pretend like that didn't happen.

the new icon is everywhere but not in the taskbar icon.

This is a Windows cache issue.

Keep dreaming on being a developer 😃

nuh uh i use nobara linux and arch linux daily, contributed to bloxstrap wiki to make it run on linux (2 weeks later roblox removed support for it.) and contributed to jakoolit fedora hyprland dotfiles to make it work with dnf5 for the fedora release 41 and nobara 41. And i make games with unity, godot and currently making a gravity falls type realistic game on roblox studio. yea i may not be a true developer but atleast it's enough for a 13 year old.

yes i know fedora 41 is in beta but i contributed for easy MOR (migration on release)

Keep dreaming on being a developer 😃

Heyy! fellow garuda linux user! or i hope so as that's your pfp. What's your discord man?

Keep dreaming on being a developer 😃

nuh uh i use nobara linux and arch linux daily, contributed to bloxstrap wiki to make it run on linux (2 weeks later roblox removed support for it.) and contributed to jakoolit fedora hyprland dotfiles to make it work with dnf5 for the fedora release 41 and nobara 41. And i make games with unity, godot and currently making a gravity falls type realistic game on roblox studio. yea i may not be a true developer but atleast it's enough for a 13 year old.

alr, when did i ask for a short story about dreaming

Okay, i think  you will lose more in an online battle as more as you try to prove yourself. but this isn't a battle. this a polite discussion. also if you really want i am making my own project called winux. It's like a linux subsystem for linux.

Keep dreaming on being a developer 😃

nuh uh i use nobara linux and arch linux daily, contributed to bloxstrap wiki to make it run on linux

If you contributed to the wiki, why won't you send us the page you contributed to?

okay! the github issue is #1285 also this wiki page was removed 2-3 weeks after adission as roblox discontinued support for it but i hope this is enough.  to be fair i wrote the instructions and @pizzaboxer  put it together in a readable form

im gonna go sudo pacman -Syu

templeos is better than linux

I guess you were right.

But you contributed to a wiki page that then got deleted due to Roblox not supporting Linux, which doesn't make you a developer, nor in the 2.8.0 beta. What you did is basically give a suggestion for a wiki page, pizzaboxer added it, but then Roblox changed some stuff so pizzaboxer removed it.
I'm not saying you're not a developer because the wiki page got deleted, i'm saying you're not a developer because you only gave a suggestion for a wiki page.

wait is nab cooking today

No because i'm a dumbass. I never cook.

templeos is better than linux

best os in existence. no one can be like the creator of temple os

But you contributed to a wiki page that then got deleted due to Roblox not supporting Linux, which doesn't make you a developer, nor in the 2.8.0 beta. What you did is basically give a suggestion for a wiki page, pizzaboxer added it, but then Roblox changed some stuff so pizzaboxer removed it. I'm not saying you're not a developer because the wiki page got deleted, i'm saying you're not a developer because you only gave a suggestion for a wiki page.

i am not a developer, just a dumbass making games with unity, godot and unreal as a hobby. also you do need to be quite techy to give instructions because man that wiki took 3 days to test and debug

and i just called the 2.8.0 beta as developer beta because it is a cool term :P

so i'm in the 2.8.0 developer beta. i know you guys won't provide support for this but i am a developer.

I summon Pandemonium on you.

so i'm in the 2.8.0 developer beta. i know you guys won't provide support for this but i am a developer.

I summon Pandemonium on you.

we dont talk about that. i wrote that at 1 am

also i did contribute to https://github.com/JaKooLit/Fedora-Hyprland via https://github.com/JaKooLit/Fedora-Hyprland/pull/26.
man why cant i code solutions that last. this one was also fixed so it was never added but might be needed again as fedora 41 uses that technology again

Nab you are so cool and epic :3 you aint a dumbass, you a smart fella, not a fart smella

okay then. also wanna be friends please :D @NabHeyka22

No thanks.

:(

(；′⌒`)

ha

ha

hwappy enwing


${config:python.defaultInterpreterPath} in tasks.json does not resolve to full path

Type: Bug

Behaviour
Expected vs. Actual
Using ${config:python.defaultInterpreterPath} in tasks.json does resolve to python.
I expected it to resolve to the full path e.g., C:\venvs\project123\Scripts\python.exe.
Steps to reproduce:

Create a new Python project.
Create a virtual environment somewhere on your computer.
Set the interpreter using the command palette (F1)
Do NOT set python.defaultInterpreterPath in settings.json
Have a tasks.json like the following:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Echo Python Interpreter",
            "type": "shell",
            "command": "Get-Command ${config:python.defaultInterpreterPath}",
        },
        {
            "label": "Run Pip List",
            "type": "process",
            "command": "${command:python.defaultInterpreterPath}",
            "args": ["-V"],
            "dependsOn":"Echo Python Interpreter"

        },
    ]
}

Run the tasks.

Notice that ${config:python.defaultInterpreterPath} resolves simply to python, which calls the default Python installation added to PATH. Instead, it should resolve to C:\Users\niccodan\AppData\Local\Python Environments\atlassian-python-api\Scripts\python.exe, which is the interpreter I configured for the project.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.11
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

Extension version: 2023.14.0
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
47.77GB (27.56GB free)

Process Argv
--crash-reporter-id c8b77264-d6e8-4b5f-95e9-cdecf57cf75e

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
282f8724:30602487
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
962ge761:30823813
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572

Hi @danielniccoli 👋 python.defaultInterpreterPath is actually different from the selected interpreter, hover over the setting description to see how it works:

It points to https://aka.ms/AAfekmf which explains the usage.
What you probably want here is to use ${command:python.interpreterPath} instead. However you may run into https://github.com/microsoft/vscode-python/issues/21687 in that case, which is an open issue on VS Code: https://github.com/microsoft/vscode/issues/160891.

@karrtikr Thank you, it works that way as long as I use shell and not process.

@karrtikr I just noticed that the interpreter path used is from a different workspace in the multi-root workspace, and not from the workspace the tasks.json is placed. Is that normal or a bug?

Is this when using ${command:python.interpreterPath} command?

Hi @karrtikr , yes it was when using ${command:python.interpreterPath}. I can't post my tasks.json, because shortly after I opened this ticket I trashed the entire multi-root project and now work with normal projects with multiple instances of VS Code in parallel. At the moment, multi-root support in VS Code and its extensions is a mess I could just not invest any more time.
However, if you want to reproduce this, just echo the value of the variable into a shell and you will see that all projects in a multi-root project will output the same value, although different interpreters (from different venv's) are used.

Fix should be out in the pre-release version of the extension in a day, use the following to try it out:

@danielniccoli Pinging to see if you can verify the fix works.

I can't post my tasks.json, because shortly after I opened this ticket I trashed the entire multi-root project

I can't verify any longer, sorry.


Can't interact with terminal

All works, but when I get text prompted like Is this ok [y/N]: after sudo dnf autoremove, it automatically aborts.
I think the problem is the while loop in updater.sh

I'm going to check the pull request 👀


Jenkins execution : Getting error WARN: Cannot read lintr_out.json file when trying to execute job using SonarScanner

I have configured R sonar plugin in sonarqube server and installed R in my jenkins nodes.  But when tried to execute job from jenkins,  job got failed with error "WARN: Cannot read lintr_out.json file, skipping
java.nio.file.NoSuchFileException: lintr_out.json"
log :
NFO: Load project repositories (done) | time=420ms
INFO: 1456 files indexed
INFO: 0 files ignored because of inclusion/exclusion patterns
INFO: 0 files ignored because of scm ignore settings
INFO: Quality profile for r: Sonar way
INFO: ------------- Run sensors on module SonarTest
INFO: Load metrics repository
INFO: Load metrics repository (done) | time=29ms
INFO: Sensor JavaXmlSensor [java]
INFO: Sensor JavaXmlSensor [java] (done) | time=5ms
INFO: Sensor HTML [web]
INFO: Sensor HTML [web] (done) | time=21ms
INFO: Sensor JaCoCo XML Report Importer [jacoco]
INFO: Sensor JaCoCo XML Report Importer [jacoco] (done) | time=10ms
INFO: Sensor LintR Sensor for R files [r]
INFO: Running sensor for LintR
WARN: Cannot read lintr_out.json file, skipping
java.nio.file.NoSuchFileException: lintr_out.json
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
at java.nio.file.Files.newByteChannel(Files.java:361)
at java.nio.file.Files.newByteChannel(Files.java:407)
at java.nio.file.Files.readAllBytes(Files.java:3152)
at com.msd.gin.common.sonar.LintRSensor.execute(LintRSensor.java:69)

Please let me know, how to fix this

As described in the documentation, you have to run LintR manually as part of your build process to generate output in JSON format.

Thanks for your reply.
Getting below error.

run_lintr.R is a sample script to demonstrate how you should run LintR for your project (it is just one line of R code to run LintR and put results into JSON file). It can be found here:
https://github.com/Merck/sonar-r-plugin/blob/master/sample-project/run_lintr.R


Reference to task A's output param not resolved if task B does not depend on task A

Checklist:

[x] I've included the version.
[x] I've included reproduction steps.
[x] I've included the workflow YAML.
[ ] I've included the logs.

What happened:
A "{{tasks.X.outputs.parametes....}}" reference was left as a literal during workflow execution because the task including that reference did not list X as a dependency.
What you expected to happen:
This I think violates the 'Principle of Least Surprise'. I think this should be a lint error and a runtime execution error, as the task is attempting to reference an output parameter that may not yet exist.
How to reproduce it (as minimally and precisely as possible):
Run this with the #dependencies ... line left commented out and inspect the logs of the workflow.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: output-parameter-
spec:
  entrypoint: abc
  serviceAccountName: argo
  templates:
  - name: abc
    dag:
      tasks:
        - name: generate-parameter
          template: whalesay
        - name: consume-parameter
          template: print-message
          #dependencies: ["generate-parameter"]
          arguments:
            parameters:
            - name: message
              value: "{{tasks.generate-parameter.outputs.parameters.hello-param}}"
  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [sh, -c]
      args: ["sleep 1; echo -n hello world > /tmp/hello_world.txt"]
    outputs:
      parameters:
      - name: hello-param
        valueFrom:
          path: /tmp/hello_world.txt

  - name: print-message
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["{{inputs.parameters.message}}"]

You see:
consume-parameter:	 _________________________________________
consume-parameter:	/ {{tasks.generate-parameter.outputs.para \
consume-parameter:	\ meters.hello-param}}                    /
consume-parameter:	 -----------------------------------------
consume-parameter:	    \
consume-parameter:	     \
consume-parameter:	      \
consume-parameter:	                    ##        .
consume-parameter:	              ## ## ##       ==
consume-parameter:	           ## ## ## ##      ===
consume-parameter:	       /""""""""""""""""___/ ===
consume-parameter:	  ~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ /  ===- ~~~
consume-parameter:	       \______ o          __/
consume-parameter:	        \    \        __/
consume-parameter:	          \____\______/

Anything else we need to know?:
Environment:

Argo version: We use Nix. Our Nix'd argo version is 2.4.3
Kubernetes version :

clientVersion:
  buildDate: "1970-01-01T00:00:01Z"
  compiler: gc
  gitCommit: e7f962ba86f4ce7033828210ca3556393c377bcc
  gitTreeState: archive
  gitVersion: v1.16.6-beta.0
  goVersion: go1.13.6
  major: "1"
  minor: 16+
  platform: darwin/amd64
serverVersion:
  buildDate: "2019-12-22T23:14:11Z"
  compiler: gc
  gitCommit: c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2
  gitTreeState: clean
  gitVersion: v1.14.9-eks-c0eccc
  goVersion: go1.12.12
  major: "1"
  minor: 14+
  platform: linux/amd64

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Note that this does not appear to be a regression as doing argo lint on v2.2.1 passes.

Coincidentally, I'm looking at the relevant code for another PR. Will take a look at this

Don't close, I think this bug ought to be addressed if it isn't yet fixed. 🙏

Don't close, I've been working on this.

Hi, sorry I was a bit occupied after my last comment. I've confirmed that this issue is still reproducible with the latest commit.
Initially I tried to fix this, but then I started to wonder if we should really fix this. What if a user really wants to print {{tasks.generate-parameter.outputs.parameters.hello-param}}? Are we going to allow users to escape double brackets?

What if a user really wants to print

I'd guess that 99/100 times they wouldn't want to print that, and it'd be a mistake in their task dependency specification.


concurrent, multiuser and custom database

apologies if I am repetitive,
I have a concurrent, multiuser web application that each user connects to this application uses a custom database.
eg User 1 connects to the database 1 and so on (I have almost 100 users and the same number of databases).
several or all users are connected simultaneously.
yank 3 can optimally cover this scenario?
otherwise you could please recommend some strategy or other product (excuse me if the latter is reckless)

I'm thinking about how I can add that functionality back in in an elegant manner. More later...
Sent from my iPhone

On 02 Jan 2016, at 17:23, SOLiNAD21<EMAIL_ADDRESS>wrote:
apologies if I am repetitive,
I have a concurrent, multiuser web application that each user connects to this application uses a custom database
eg User 1 connects to the database 1 and so on (I have almost 100 users and the same number of databases)
several or all users are connected simultaneously
yank 3 can optimally cover this scenario?
otherwise you could please recommend some strategy or other product (excuse me if the latter is reckless)
—
Reply to this email directly or view it on GitHub.

OK, I added functionality for this in the latest snapshot release.


[BUG] Fix CPU fallback for custom timestamp formats in Hive delimited text

The Spark RAPIDS plugin currently supports only the default timestamp format, when reading Hive delimited text files.
i.e. When the user specifies timestamp.formats in their table specification, the reading should fall back to CPU. But this is not the observed behaviour: The code currently does not fall back to CPU.
The problem is that the logic currently checks for the property in Storage Properties instead of TBLPROPERTIES or SERDEPROPERTIES.
This goes uncaught in the test, because the test accidentally tests with Hive delimited text reading disabled.
Both the core logic and the test need to be fixed.

This bug blocks #7296.


bump package.json

Thx. This has been merged with https://github.com/simianhacker/bunyan-elasticsearch/pull/10 already.


wip: initial pose (will update when done)

This PR is a wip for fixing #579 and is opened to have early feedback.

Close this PR as it will be useless (see #579 for more informations).


load_mudatas fix

These small changes make the code work for me
C xx

The only other things I added were 2 line spaces after each function, because it is good practice. But I would be surprised if it made a functional difference to the code 🤷🏻


Adding comentaries on test cases

Remember that you should sync again as pull request #5 has modified README.md in a way that git cannot fix automatically.


Signal handling fixes

First draft. Tested on Linux with glibc only.
See individual commit descriptions for details.
TODOs:

It should not be necessary to recreate the outputs. But the whole thing has so many races and weird things happen if I keep using the existing output list.
Time to dig out my old work on reducing the number of wl_display_roundtrips in the code.
CssReloadHelper does not handle appearance changes and .reset() on reloads can be optimized.

Fixes: #3344

Hi, I'm coming from #3344. Thanks for your work on this!
I see that you are spawning a new thread in the signal handler:
https://github.com/Alexays/Waybar/blob/d8a7f429e756f4dc378ed1cb9824d47ea46edab5/src/util/unix_signal.cpp#L48-L59
Even though that will probably work most of the time, you unfortunately cannot do that, pthread_create is not async-signal-safe. You might end up with users reporting bugs that are extremely complex to diagnose.
You can have a look at man 7 signal-safety for a list of functions you can call in a signal handler.
Some pthread functions are there:
pthread_kill(3)        Added in POSIX.1-2008 TC1
pthread_self(3)        Added in POSIX.1-2008 TC1
pthread_sigmask(3)     Added in POSIX.1-2008 TC1

But not pthread_create. What people usually do in signal handlers is that they set an atomic boolean (let's say sigusr2_needs_to_be_processed) to true, and handle it in a separate thread that is already running. Once the thread is done handling the signal, it would set sigusr2_needs_to_be_processed back to false.

I see that you are spawning a new thread in the signal handler:

That's not what is happening here.
The signal handling thread is started from the main thread in normal context, then we mask all the signals that are interesting for us for all the application threads and listen for signals with sigtimedwait(2). Not a single line of the new code runs in a signal handler context.

Oh my bad, I misunderstood what's going on then, I'm sorry for wasting your time


Do not use pop-ups for emails.

Click on the email in the footer social links to pop up a new window.
I would like not to pop-up the window when clicking on e-mail.

Re: lartpang
The email will pop up the mail client, but it will also pop up a browser window.

Do not look at my home page. I changed the HTML code by myself >o<
Fortunately, there are not many logs.

“ it will also pop up a browser window.”？
Sorry, i didn't meet this problem...
when i click my "mailto", it will call my meil client...
and, i would like to recommend a tool for you, it can encrypt your email address, but it doesn't affect your email.
http://tools.jb51.net/email/emailencode

I think this could be solved by removing target="_blank" for the mail link.

Sorry, i didn't meet this problem...
when i click my "mailto", it will call my mail client...

Re: lartpang
Firefox will not pop up browser windows.
Chromium pops up browser window.
(Linux OS)


option to list custom tasks

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Odd exit in NASTRAN reader

I have a BDF file which read fine with meshio==4.3.1, but does not with 4.3.10. The regression seems to have been introduced with the merge of #988
It seems the BDF file I was using was improperly formatted - it ends with END BULK instead of ENDDATA.
Nevertheless, when using 4.3.10 to read the improperly formatted file, the program would exit(1), which doesn't seem like the right behavior. This should either raise a more informative error message, or just break out of the data reading loop entirely.
https://github.com/nschloe/meshio/blob/cdce0af7cafc9e72365bd4237605b4c58a1c6b0a/meshio/nastran/_nastran.py#L117-L123
test.bdf.zip

the program would exit(1), which doesn't seem like the right behavior.

Absolutely. Looking at it right now.


Confirm Seed word flow:Need to trim the entered words

Trim entered mnemonic words(as they are entered):Need to trim the entered words so that white spaces can be removed.

Verified this issue on dev app v 2.0.75(478)


Smartyads/add_prebid_server_params

🏷 Type of documentation

[ ] new bid adapter
[x] update bid adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[ ] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[ ] For new adapters check submitting your adapter docs

Thanks @rishko00 can you please reference the pull request this documentation change belongs to and fix the markdown linting errors?

Thanks @rishko00 can you please reference the pull request this documentation change belongs to and fix the markdown linting errors?

@muuki88 thanks for feedback, I've just fixed lint error.
We want to separate prebid.js and prebid server params for publishers convenience, there weren't any changes.


get_anndata() / get_seurat() should set uns with census version info

Description
cellxgene_census._get_anndata.get_anndata() and cellxgene.census::get_seurat() should set uns with census version info.
Context
Impact
Helps ensure reproducibility, if only an exported anndata object is available.
Alternatives you've considered
Ideal behavior

This should be cross-language, I edited the top-level comment and title


DCO: Remove unused file

This originally landed in #3 along with a reference from CONTRIBUTING.md.  That CONTRIBUTING.md reference was removed in #255, where it was replaced with references to Linux Foundation CNCF CLAs.  Since we no longer use the DCO, this commit removes the local copy.
This doesn't quite match with the CNCF charter, which has (§11.c):

All new inbound code contributions to the CNCF shall be (i) accompanied by a Developer Certificate of Origin sign-off (http://developercertificate.org) and (ii) made under the Apache License, Version 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0), such license to be in addition to, and shall not supersede, obligations undertaken under the contribution license agreement(s) provided for in (b) above.

But perhaps we want to punt on resolving that until kubernetes-template-project decides how it should be handled.

But perhaps we want to punt on resolving that until kubernetes-template-project decides how it should be handled.

I've filed kubernetes/kubernetes-template-project#16 upstream for this.

Going to wait on the result of kubernetes/kubernetes-template-project#16

It was closed with "I don't think there is any intention to add a DCO requirement to Kubernetes given the CLA requirement...".  I think that's a green light for this PR, although you might want to wait to see if the CNCF charter wording gets updated.


Give data in GeoJSON

Use out body;>;out skel qt;

use out count; to count the nodes and ways - this happens prior to converting to geojson
create lookup for nodes
create way objects with node geometry
convert to geojson

cc @batpad @ramyaragupathy


New items (execept databases) couldn't be created in Simple view

System information:

Operating system (distribution) and version win 10 x64
DBeaver version 7.0.2

Describe the problem you're observing:
When trying to create items in Simple View error appears:
Schema (PostgreSQL):

Table (MySQL):

It is not a bug, see #8381
UI inconsistency fixed


Allow to align text vertically (to the top in the first place)

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
The general problem is the current workflow of adding text. When I start typing text on a shape, I'm expecting to only adjust things manually when the text is too large for the shape. However, currently this is not the case. I'm only reporting one issue at a time (vertical alignment), but in fact there's also a problem with padding, i.e., if I want align the text horizontally to the left in a box, I have in fact to create an additional "text" element inside the box and size it in a way that I get "paddings" around the text.
Now the problem with vertical alignment has to do with both editing process and result: when writing a paragraph of text, I'm not sure about the exact size of the paragraph, so I create just some "text" element and start writing. With each new line, the text (which is vertically aligned to the center of the "text") grows in both directions (up and down) relatively the element, instead of being appended to the bottom. Moreover, even the viewport shifts so that the "vertical center" of the text stays on the same height. Here's an illustration:

Describe the solution you'd like
What a want is basically the vertical alignment buttons near the horizontal alignment buttons on the right panel (even if there is some way to vertically align text to the top, I don't see it). The element shouldn't shift relatively to the viewport; the text should be just appended to the bottom, line by line.
Describe alternatives you've considered
Currently I have to move the text element after I stop writing to align it to the level I want it to start at. This is quite inconvenient.
Additional context
I guess, the icons for the buttons should be similar to, say, those of Google Sheets:

Well, this is still a relevant issue, hope that it will be dealt with


[README] CocoaPods 0.36 is no longer in beta

Just release CocoaPods 0.36 GM, it's no longer in beta. It does require use_frameworks! in the Podfile.

Beautiful. Awesome work, @kylef and the rest of the @CocoaPods team!


[Snyk] Upgrade zone.js from 0.11.8 to 0.14.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade zone.js from 0.11.8 to 0.14.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 8 versions ahead of your current version.
The recommended version was released 22 days ago, on 2023-11-03.

Release notes

Package name: zone.js

0.14.2 - 2023-11-03PR Close #52508

0.14.1 - 2023-10-26

0.14.0 - 2023-09-18

0.13.3 - 2023-09-12

0.13.2 - 2023-09-11

0.13.1 - 2023-06-12

0.13.0 - 2023-03-06

0.12.0 - 2022-11-07

0.11.8 - 2022-08-12

    from zone.js GitHub release notes

Commit messages

Package name: zone.js

1a33a2c release: cut the zone.js-0.14.2 release (#52508)
6033504 docs: update ssr docs to add information about `CommonEngine` (#52506)
3d73b0c fix(core): use TNode instead of LView for mapping injector providers (#52436)
435dd32 fix(zone.js): disable wrapping unhandled promise error by default (#52492)
1da4a24 fix(migrations): handle ngIf else condition with no whitespaces (#52504)
2560037 docs: omit repetitions (#52413)
5ab5be7 build: update dependency multimatch to v7 (#52426)
d4bd3f1 build: configure tslint to ban `performance.mark` usages (#52505)
93d32a9 fix(core): guard usages of `performance.mark` (#52505)
1f528f1 refactor(core): mark `effect` as developer preview again (#52490)
181dc7e docs: release notes for the v17.0.0-rc.2 release
57cad0e docs: release notes for the v16.2.12 release
83a3b85 refactor(core): Do not refresh view if producers did not actually change (#52476)
164cfc0 refactor(core): Update LView consumer to use only 1 consumer for a component (#52476)
58d74a2 refactor(core): Remove warning about signal set during template execution (#52476)
f615f4f docs: additional application builder SSR conversion information (#52485)
9dbc5d7 refactor(core): do not run CDs when setting up image perf warnings (#52482)
51f84d9 refactor(compiler): escape decorators in API JsDoc extraction (#52481)
64db486 build: add rules for generating block/element API data (#52480)
a3abe16 build: add target to generate api manifest (#52472)
91ee269 refactor(core): short-circuits invocations of signals equality (#52465)
184d824 refactor(compiler): Delete some unused imports in template pipeline (#52464)
9564456 refactor(compiler): Rename `slot` -> `handle` in slot consumers (#52464)
6347e0e refactor(compiler): Move an enum to `enums.ts` for Template Pipeline (#52464)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Checkmarx One – Scan Summary & Details – e7bff4c8-fa74-4b48-ad03-9b1b99d8dd06
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-46233
Npm-crypto-js-3.3.0
Vulnerable Package

Passwords And Secrets - Generic Password
/users.yml: 132
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/users.yml: 186
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/users.yml: 195
Query to find passwords and secrets in infrastructure code.

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-2251
Npm-yaml-1.10.2

Cx6b921f00-d395
Npm-vm2-3.9.11


Avoid installing the DOM module when Activity detection is unavailable

The DOM module effectively doesn't work due to our hack that lists all
activities not functioning properly on previous versions of Android.
Without this, we currently cannot provide the DOM feature.
We can fix these issues by providing a manual API that informs us of
activity lifecycle events similar to Romain Guy's ViewServer:
https://github.com/romainguy/ViewServer

Looks good.


Add Spoiler plugin - hideitbot like

HideItBot is (was?) a bot very nicely working but seems to be offline.
It would be great to add a plugin like hideit bot, knowing that that bot is opensource: https://github.com/erpheus/hideit-bot

Right now our bot/framework does not support interfacing with buttons and custom keyboards, first we will need to add support for these backend features.


(feat) Support Github Templates

Added several templates for github issue tracking, contribution, and pull request views.

Implemented


[RFD]: Remove Optional versions of <| operators

The addition of overloads for <| and friends that return optional
values sounded like a great idea but I think they have ended up being
awkward in practice.
The problem that they solve is, frankly, minimal. It helps when decoding
from a root key, but that's about it.
On the other hand, introducing an entirely new set of operators adds
overhead and introduces possible ambiguity for the compiler as well as
introduces cognitive overhead for the user. I'm not convinced that some
of the issues we've seen around expression complexity and poor error
messaging aren't due to the introduction of these (rarely used)
operators.
The real solution would be for Swift to support Monads and then we
could make these completely generic, but I'm not holding my breath
there.
I'm not planning on merging this yet, just want to open a discussion about it.

:+1:

Another datapoint that this is probably the best long-term move, the following code is completely ambiguous:
let foos: [Foo] = (json <|| "foos") ?? []

If we only return Decoded here, this isn't an issue anymore.

I've yet to use the Optional versions and don't anticipate needing them often, so no objections here :+1:

This has been open for a really long time with no objections, so I'm going to move this into master in preparation for 3.0

Too late, but I used it fairly often to manually decode keys from a root JSON when the representation was really bad and I didn't want to deal with handling the Decoded versions:
public static func decode(j: JSON) -> Decoded<NSDate> {
    guard let timeString: String = j <| "time",
        periodString: TimePeriod = j <| "timeSection" else {
        return .customError("Expected time String, got \(j).")
    }

    let timePeriodString = "\(timeString) \(periodString)"

   return .fromOptional(DateFormatter.scheduleTimeFormatter.dateFromString(timePeriodString))
}

In any event I think I'll move the optional operators into my own code.

yep, that's really the only reasonable usecase that we knew of. However, you could replicate the old behavior by adding .value so it seemed like it wasn't adding all that much:
// before
let foo: Foo? = j <| "rootKey"

// after
let foo: Foo? = (j <| "rootKey").value

wasn't adding all that much

^^ not quite right. It's definitely useful, but it had an adverse affect on the complexity for the compiler, as well as caused headaches when the type was fairly ambiguous. Removing <| for Optional simplifies those things at the cost of losing this one feature, which seemed like a reasonable tradeoff.

Yeah, I'll just use .value instead of using the custom operators. Thanks.


Add onboarding checklist

Pull Request: Add onboarding checklist
Related Issue
N/A
Changes Made
Added onboarding checklist that appears for users that haven't created any questions yet (including for users who have forecasted on other questions).
Screenshots

Testing
Tested locally. It's a low risk change wrt breaking anything else, the main risk is changing the layout for non-onboarding users, I've just checked this carefully.

Btw, looks like the <habit x> auto-selection feature isn't working, but it's not working on Predict Your Year either. It should select focus the title and select the substring including the "<" and ">". Could be nice to fix if we're reusing it here, but not important


mac-23 and mac-26 lost external connection from phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-23 and mac-26 lost external connection from phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting both machines above to restore both connections.


Fix priority of not in AST2SQL

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #5026
Problem Summary(Required) ：

CREATE VIEW v1 AS
SELECT t0.c_0_0 FROM t0 WHERE ((NOT false) IS NULL);

When ast is converting to sql, the output content is SELECT t0.c_0_0 FROM t0 WHERE NOT false IS NULL
Given that union operator not's priority < is null operator,  so the order of operators is changed
So we need wrap not operator with "()" when convert ast to sql

[FE PR Coverage check]
:heart_eyes: pass : 8 / 9 (88.89%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/analyzer/AST2SQL.java
8
9
88.89%

please add UT

[FE PR Coverage check]
:heart_eyes: pass : 8 / 9 (88.89%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/analyzer/AST2SQL.java
8
9
88.89%

@Mergifyio backport branch-2.2


lorempixel does not provide CORS headers

CORS headers are needed in image preloading (e.g. Vue components using img tag), thus making default image provider in Faker a no go.
$ curl -I lorempixel.com/640/480/
HTTP/1.1 200 OK
Date: Mon, 11 Nov 2019 07:59:52 GMT
Server: Apache/2.4.10 (Debian)
Expires: Fri, 30 Oct 1998 14:19:41 GMT
Cache-Control: no-cache, no-store
Pragma: no-cache
Connection: close
Content-Type: image/jpeg

For instance, I added bluemmb/faker-picsum-photos-provider as a third party provider and it works fine.
Whether replacing the default provider or trying to get lorempixel to add CORS headers it's for you to decide, I just think it would be nice that the default Faker image provider could have CORS headers too.
Thanks for your amazing work!

This is not directly a bug in Faker itself but in the image provider. I suggest you to use another image provider in this case if it is required since there is nothing we can do on Faker side for this.
In the future the image provider will also be removed meaning it is deprecated at this point for 2.0


SOLR-16392: Refactor and update v2 ADDREPLICAPROP API

Description
The Solr community is engaged in an ongoing effort to make Solr's v2 API more REST-ful and intuitive for users so that it can eventually serve as a viable v1 replacement.  This PR in particular focuses on Solr's "add-replica-prop" API, aligning it with the API design described here and agreed to here and here.
In particular this changes the v2 API from:
    POST /collections/collName {"add-replica-property" : {...}}

to...
PUT /collections/<coll>/shards/<shard>/replicas/<replica>/properties/<prop> {"value": <val>}

This is a breaking change for users of the v2 API, but one that is allowed due to v2's "experimental" designation.
Solution
This PR modifies add-replica-prop in the way described, but it also refactors the API class to use the newly added JAX-RS framework in the process.  This framework-switchover, while conceptually separate from the API realignment in this case, makes sense as both tasks were coming in the short term and touch identical chunks of code.
As a result, this PR not only changes the cosmetics of the add-replica-prop endpoint, it also adds it to Solr's growing OpenAPI spec.
As suggested in the past on similar refactors, I've also moved the logic underlying the add-replica-prop functionality (previously hosted in CollectionsHandler) over to the v2 AddReplicaPropertyAPI class.  The v1 codepath in CollectionsHandler now instantiates an AddReplicaPropertyAPI to do its job.
Tests
New unit tests for AddReplicaPropertyAPI, as well as all the existing v1 and v2 tests for the add-replica-prop functionality continuing to pass.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ ] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[x] I have added tests for my changes.
[x] I have added documentation for the Reference Guide

This PR is blocked on merging apache/solr PR #1035, but is otherwise ready for review!

This PR was originally stacked on top of another PR that has since been merged into upstream's 'main'.  But I can't find a way to convert this PR over to apache/solr's 'main' branch - just the main branch of my own fork.
So rather than fight github on this, I'm going to close out this PR and create another one.  Sorry to all for the loss of history 😬


impl single SG index

This PR allows our plugin to dynamically update a single SG instance:

Uses several tries to write ACL documents based on version
Runs expiration thread on master nodes only
Ignores roles and mappings where expiration value is not defined

I have  a few concerns about race conditions where multiple nodes update the same rolemapping.  Only solution I can conceive is keeping an expiration time associated with users and removing them from the list of users.
cc @portante

@portante @ewolinetz I'm missing something on the expiration thread.  I see it start in the logs, I see the actual thread when I connect via a debugger, I dont ever see it execute.  Are my time values wrong?

Can you explain the strategy to ensure only 1 shared searchguard index per cluster?  How do you ensure that updates to the index are atomic?

Closing for now as unlikely to release for the 2.4.x line


Encrypted transfer can fail if created while another is pending.

Bug Description
If an encrypted transfer is created while another is pending, but sent after the other has been finalized, then it will fail due to invalid proof.
The same is likely the case for "unshield amount" transfers.
Steps to Reproduce

Send an encrypted transfer T1.
(Quickly) Construct another encrypted transfer and enter the submit page and begin signing T2 on ledger.
Wait until T1 has been finalized to complete signing T2 on ledger.

Expected Result
T2 is successful. (Or is not allowed to be sent)
Actual Result
T2 fails due to invalid proof.
Versions

1.1.6
Linux

This should be fixed either by blocking making encrypted (and unshield) transfers when there is another pending, or it should use the updated info from newest pending encrypted (or unshield) transfer.


Updates README usage and description

Coverage remained the same at 94.362% when pulling 85adfc8ba25fd3cd0e2f5209b460fa454bc124bd on jt/update_usage into 4248de253344783571cfd700980d13a2d4bc59c6 on master.


[W4.5c][F09-A4] Ellery Chia

Exception Handling: Updated support for possible read only errors

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.
However, in general, it is not considered "good exception handling" if you only print the error message.
Think about what you could do given the situation at the point where the exception occurs.


Include fmt library for enhanced string formatting

Include the new fmt library to have access to easier string modification. This helps in moving away from hand crafting queries, which can lead to subtle bugs.

This has been addressed already.