text:
[Snyk] Upgrade org.bouncycastle:bcprov-jdk18on from 1.72 to 1.74

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.bouncycastle:bcprov-jdk18on from 1.72 to 1.74.
: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 2 versions ahead of your current version.
The recommended version was released 23 days ago, on 2023-06-15.

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

Fixed in https://github.com/swedenconnect/credentials-support/pull/42

repo: swedenconnect/credentials-support


text:
double click a folder in the tree to open it

double click a folder in the tree to open it

a860dd6af7e18f168329cf198ea5080b18ec41eb

source: gharchive/issue

authors: shengwanhui swharden

repo: swharden/Scan-A-Gator

license: MIT

license_type: permissive

license_source: github-api


text:
Easier function plotting

New contributors should review CONTRIBUTING.md:
https://github.com/swharden/ScottPlot/blob/master/CONTRIBUTING.md
Purpose:
This makes plotting functions with restricted domain easier.
New functionality (code):
Previously, if I wanted to plot the function ln x, I would have to do it like this:
x => x > 0 ? Math.Log(x) : (double?)null
Now I can just do x => Math.Log(x) and it will be taken care of.

Sorry about not including this originally when I was working on the function plotting, the realization didn't hit until I was using the library in my own project this morning and I had to replicate this commit. I figured the change would probably be useful on the upstream library.

looks great @Benny121221, thanks! I'll push this to NuGet tonight

source: gharchive/pull-request

repo: swharden/ScottPlot


text:
Question/Request: Make HTTP requests

Can you make HTTP requests with this? Eg. to respond to a webhook, integrate APIs
I see there's the HTTPClient, which looks like it does HTTP requests, but it's currently internal.

You can use the https://github.com/swift-server/async-http-client library 👍
We're also working towards instrumenting it for tracing (with the swift-tracing instrumentation efforts), so it'd automatically carry XRay tracing headers as well 👍

Thanks a lot @ktoso :)

@cardoso if you are more familiar with URLSession you can also just use it. Just make sure to import FoundationNetworking on Linux to get access to URLSession.

That's even better. Thank you @fabianfett

@cardoso an example for you: https://github.com/swift-server/swift-aws-lambda-runtime/blob/master/Examples/LambdaFunctions/Sources/CurrencyExchange/main.swift

authors: cardoso fabianfett ktoso

repo: swift-server/swift-aws-lambda-runtime


text:
New Version 2.0 API

Motivation
Swift Prometheus has been in development since 2018. The previous maintainer (@MrLotU) stepped down about a year ago. Since then @ktoso and @fabianfett have maintained the existing code base.
In order to improve performance in the Prometheus library, we want to replace the existing implementation with a new one for version 2.0. While we do this we also want to get the general API closer to what the prometheus project recommends in their Writing client libraries guide. This means that we will also start to enforce Prometheus rules. For example having two counter with the same name, but one with labels and one without, is illegal in the Prometheus format. Lastly we want to remove the SwiftNIO dependency that is not needed anymore.
I'm well aware that this is a very large PR that changes lots of moving things.
Changes

Remove SwiftNIO dependency. Vendor in NIOLock from NIOConcurrencyHelpers
Replace PrometheusClient with PrometheusCollectorRegistry
Remove Summary implementation
Replace Counter, Gauge and Histogram implementations
Add Sendability annotations
Require Swift 5.7
Enforces that label names remain constant for a metric name.

Performance difference
In simple testing scenarios:

Exporting values from 1k counters into the prometheus format: ~10x speedup
Exporting values from 1k gauges into the prometheus format: ~10x speedup
Exporting values from 1k histograms into the prometheus format: ~25x speedup

Differences to Writing client libraries guide

There is no explicit Collector protocol, that users could implement to create their own instruments.

Counter, Gauge and Histogram should implement Collector

Currently the PrometheusCollectorRegistry does not offer a register and unregister method for Collectors
There is no API to create a Counter/Gauge/Histogram that is not registered with a PrometheusCollectorRegistry
Collectors can't be registered with multiple different PrometheusCollectorRegistrys
We don't advertise a default collector

Do we want to offer this API? With the current patch we could add this API later.

Looks nice! :shipit:

Feel free to merge at will btw 👍

authors: Andrewangeta fabianfett ktoso

repo: swift-server/swift-prometheus


text:
Test output is not in gnu standard diagnostic format

Description
Example:
✘ Test nfaToDfa() recorded an issue at parsingTests.swift:107:7: Expectation failed: (n.recognizes(input) → false) == (r → true)
✘ Test nfaToDfa() recorded an issue at parsingTests.swift:108:7: Expectation failed: (d.recognizes(input) → false) == (r → true)

Now I have to write a custom parser to recognize these messages, when if they followed the standard, my IDE would "just work".  The standard is here.
The messages also don't output full paths from the directory where swift test was invoked, which means I have to add some really hacky code to crawl through the sources and find the right file…maybe.  I'm not even sure how to do that.
This is a regression from XCTest output and makes me want to go  back!
See also https://github.com/swiftlang/swift-package-manager/issues/6862

Swift Testing is not a GCC-family compiler.
The human-readable (well… hopefully human-readable) output written to stderr is in an arbitrary format and is not meant to be parsed. Take a look at the machine-readable JSON output provided via --event-stream-output-path.

The messages also don't output full paths from the directory where swift test was invoked,

So you're aware, Swift will not report full source file paths in the future. See SE-0285.

I'm aware.  I've requested that there be a flag for debug builds that will provide full paths.  also https://github.com/swiftlang/swift-package-manager/issues/6862.  It's just a matter of how interoperable you want to be with existing tools to integrate and how easy it will be for users to track down problems.

Meanwhile, here is the hack for Emacs.  Unfortunately, every other tool will need its own hack.

I'm not able to see that commit—looks like a permissions issue?
Our human-readable output is never going to be fully machine-readable, but we provide XML and JSON output that is (and the JSON output does contain full paths, although they have underscored keys and so are not officially supported.) So without being able to see your Emacs code, I might suggest teaching it how to read the JSON instead of stderr. :)

Sorry about the perms; code inline below.

I might suggest teaching it how to read the JSON instead of stderr. :)

The problem with that is that a) I have to invoke swift some special way to get the JSON, which is inconvenient, and b) I don't want to look at the JSON output in my compilation buffer.  The barrier to entry for getting a system to actually use JSON output is quite high: you need to parse it, you need to have a system for turning it back into something human-readable, and you need a system for pointing it back at the source.  And if you're invoking swift in a terminal, you're out of luck; you won't get good/complete information.  If you want to solve the terminal problem, I guess you want to build a filter that you can pipe Swift through and turn the JSON into human-readable output. Then you might as well make that output Gnu-compliant, and nobody needs to mess with the JSON.
For years I was able to just M-x compile RET swift test RET in emacs and everything would work.  Then someone decided to remove all the path information from #file and #line and I had to start working around that problem for development purposes.  Now we have tools like swift-testing that don't want to let me work around the problem at all, And I presume JSON isn't going to help with that because swift-testing is just a library that will want to use plain #file and #line itself; the full path information won't be available—am I wrong about that?
  (add-to-list 'compilation-error-regexp-alist-alist
               `(swift-testing
                 ,(rx bol
                      (literal "✘ Test ") (+ (not space)) (literal " recorded an issue at ")
                      (group (+ (not (in "\n:")))) ; 1: file
                      ":"
                      (group (+ digit)) ; 2: line
                      ":"
                      (group (+ digit)) ; 3: column
                      )
                 1 2 3))

  (add-to-list 'compilation-error-regexp-alist 'swift-testing)

;; Enhanced file finding for compilation-mode
(require 'compile)
(require 'cl-lib)

(defvar compilation-smart-find-max-depth 5
  "Maximum depth for recursive file search.")

(defun compilation-smart-find-git-files ()
  "Get list of files tracked by git in current repository."
  (when (executable-find "git")
    (with-temp-buffer
      (when (zerop (call-process "git" nil t nil "ls-files"))
        (split-string (buffer-string) "\n" t)))))

(defun compilation-smart-find-recursive (filename &optional depth)
  "Find file recursively from current directory up to max depth."
  (let ((depth (or depth 0))
        (result nil))
    (when (< depth compilation-smart-find-max-depth)
      (dolist (file (directory-files-recursively
                     default-directory
                     (regexp-quote filename)))
        (when (and (file-exists-p file)
                  (not (file-directory-p file)))
          (push file result))))
    result))

(defun compilation-smart-find-file (filename)
  "Smart file finder for compilation-mode.
First tries git-ls-files, then falls back to recursive search."
  (let ((git-files (compilation-smart-find-git-files))
        matches)
    (cond
     ;; First try exact path
     ((file-exists-p filename)
      (list filename))

     ;; Then try git-ls-files
     (git-files
      (setq matches
            (cl-remove-if-not
             (lambda (f) (string-match-p (regexp-quote filename) f))
             git-files))
      (when matches
        matches))

     ;; Finally try recursive search
     (t
      (compilation-smart-find-recursive filename)))))

(defun compilation-smart-find-file-choose (matches filename)
  "Choose from multiple matching files."
  (cond
   ((null matches) nil)
   ((= (length matches) 1) (car matches))
   (t
    (completing-read
     (format "Multiple matches for '%s', choose one: " filename)
     matches nil t))))

(defun compilation-find-file-smart (orig-fun marker filename directory &rest args)
  "Advice around `compilation-find-file' to enhance file finding."
  (let ((original-result (apply orig-fun marker filename directory args)))
    (if (and (null original-result)
             (not (file-name-absolute-p filename)))
        (let* ((matches (compilation-smart-find-file filename))
               (chosen-file (compilation-smart-find-file-choose matches filename)))
          (if chosen-file
              (find-file-noselect chosen-file)
            original-result))
      original-result)))

;; Install the advice
(advice-add 'compilation-find-file :around #'compilation-find-file-smart)

;; Optional: Add a command to remove the advice if needed
(defun compilation-smart-find-disable ()
  "Remove smart file finding advice from compilation-mode."
  (interactive)
  (advice-remove 'compilation-find-file #'compilation-find-file-smart))

(provide 'compilation-smart-find)

The problem with that is that a) I have to invoke swift some special way to get the JSON, which is inconvenient, and b) I don't want to look at the JSON output in my compilation buffer.

I don't speak Emacs' dialect of Lisp well enough to be sure how you're actually invoking swift test or Swift Testing here, but if you're calling swift test, presumably you can pass a command-line argument? If so, it's then just a matter of passing --event-stream-output-path /tmp/whatever.json and consuming the file afterwards. The JSON won't be written to stdout or stderr, so it presumably won't poison your buffer.

The barrier to entry for getting a system to actually use JSON output is quite high: you need to parse it, you need to have a system for turning it back into something human-readable, and you need a system for pointing it back at the source.

We've managed to make it work quite well with the Swift VS Code plugin, so perhaps the barrier isn't as high as you're guessing? It's worth investigating, I think.

And I presume JSON isn't going to help with that because swift-testing is just a library that will want to use plain #file and #line itself; the full path information won't be available—am I wrong about that?

Swift Testing's JSON output includes the values of #line, #column, #fileID, and (at least currently) #filePath for all relevant records. The schema is laid out here (apologies for the half-baked formatting). Although file paths aren't listed, they are present next to "fileID" under the key "_filePath". The underscore indicates we don't formally support this key, but it's likely to stick around for a while out of sheer usefulness.

I don't speak Emacs' dialect of Lisp well enough to be sure how you're actually invoking swift test or Swift Testing here,

It's not in this code; it's a simple emacs command that I make from inside the editor: cmd-X compile return swift test return (and I have cmd-X compile bound to a key), and I have a key to repeat the last compile command.  Most of my development is editing punctuated by hitting that key.

Swift Testing's JSON output includes the values of #line, #column, #fileID, and (at least currently) #filePath for all relevant records.

In that case, you must be encoding the #filePath in the binary and I really don't see the point in omitting the path from the invocation directory to the file from the human-readable output.

We've managed to make it work quite well with the Swift VS Code plugin, so perhaps the barrier isn't as high as you're guessing? It's worth investigating, I think.

The thing is, VSCode has all the infrastructure for doing that; it has a first-class “problems” pane that you can plug into and whatnot.  Emacs isn't set up that way; I'd have to invent a whole new subsystem just to handle Swift, and then that subsystem wouldn't work with the hundreds of other tools that Emacs already works with OOTB using compilation mode, or with anyone else's 3rd party customization for compilation mode.
Love it or hate it, one good property of Emacs' system is that for the vast majority of tools that report issues, you don't need to know how to write a plugin, or write any code at all.  The tools that use the gnu standard format just work.  The hundreds of others already in emacs' list of output scraping regexes just work.  And if you're not golden at that point, you can usually just write an appropriate regex yourself (that's what the first stanza of my elisp code does)… provided that the tools cooperate and attach at least a relative path to the filename.  Stripping the path is hostile to that system.

The underscore indicates we don't formally support this key, but it's likely to stick around for a while out of sheer usefulness.

Sounds like another reason for me to keep scraping the human-readable output.

It's not in this code; it's a simple emacs command that I make from inside the editor:

Understood.

Love it or hate it, one good property of Emacs' system is that for the vast majority of tools that report issues, you don't need to know how to write a plugin, or write any code at all. The tools that use the gnu standard format just work.

Just to spitball here: if you're not in a position to pass additional arguments to swift test, would environment variables work?
I've also toyed with the idea of having a ~/.swift-testing config file. Hypothetically, if we added something like:
{
}

The hundreds of others already in emacs' list of output scraping regexes just work. And if you're not golden at that point, you can usually just write an appropriate regex yourself (that's what the first stanza of my elisp code does)… provided that the tools cooperate and attach at least a relative path to the filename. Stripping the path is hostile to that system.

The underscore indicates we don't formally support this key, but it's likely to stick around for a while out of sheer usefulness.

Sounds like another reason for me to keep scraping the human-readable output.

It's not in this code; it's a simple emacs command that I make from inside the editor:

Understood.

Love it or hate it, one good property of Emacs' system is that for the vast majority of tools that report issues, you don't need to know how to write a plugin, or write any code at all. The tools that use the gnu standard format just work.

Just to spitball here… I've toyed with the idea of having a ~/.swift-testing config file. Hypothetically, if we added something like "showFullPaths" = true to such a config file (that we would read at the start of a test run), would that be useful to you here?

Sounds like another reason for me to keep scraping the human-readable output.

I can't stop you from doing so, I can only advise against it. 🙂

if we added something like "showFullPaths" = true to such a config file (that we would read at the start of a test run), would that be useful to you here?

Yes please!  showRelativePaths would be even more useful, as it would strip redundant info from the output.

I can only advise against it.

Given what you now know about my environment and the fact that I already have it working, you would really advise that I do something else?  If so, why?

if we added something like "showFullPaths" = true to such a config file (that we would read at the start of a test run), would that be useful to you here?

Yes please! showRelativePaths would be even more useful, as it would strip redundant info from the output.

I'll keep this request in mind for when we stabilize the format of our configuration data.

I can only advise against it.

Given what you now know about my environment and the fact that I already have it working, you would really advise that I do something else? If so, why?

The human-readable output is subject to change over time and we make no guarantees that it will remain compatible with scripting you build around it.

The human-readable output is subject to change over time and we make no guarantees that it will remain compatible with scripting you build around it.

I understand that of course.  Apparently the inclusion of full paths in the JSON is equally subject to change, and I already have this functionality, and the effort to use the other functionality and still produce a good user experience is high.  I just don't see how it makes any sense to change what I'm doing right now.

BTW, what does “recorded an issue” mean?  Does it write some auxiliary file?  Why not a much more straightforward message that a test "failed," which most people would understand right away?  “An issue” doesn't necessarily mean a test failure.

I just don't see how it makes any sense to change what I'm doing right now.

As I wrote, I can't stop you from doing what you're doing, I can only advise against it. 🙂

BTW, speaking of changing the human-readable text, what does “recorded an issue” mean? Does it write some auxiliary file? Why not a much more straightforward message that a test "failed," which most people would understand right away? “An issue” doesn't necessarily mean a test failure.

An issue is an instance of Issue. It is recorded in the test log (which can be any of stderr, Xcode's Test Report, JSON, XUnit/JUnit XML, or whatever VS Code calls their testing UI.)
And, as you note, an issue doesn't necessarily mean a test failure. Right now, issues may be known (not failures) or unknown (failures) but we may introduce the concept of issue severity in the future, in which case an issue may occur and be recorded and only result in a warning or advisory (exact details TBD.)

As I wrote, I can't stop you from doing what you're doing, I can only advise against it. 🙂

Yeah, I heard you. I can't understand why, given everything you know about my circumstances and the systems I have to integrate with, you'd still be advising me against doing it in the short term.  It makes me think maybe I'm missing something.
IMO it's really important to tell users explicitly when something is a failure, that it's a failure—especially if you're going to have non-failure issues.  I strongly recommend making the failure text explicit about that.

authors: dabrahams grynspan

repo: swiftlang/swift-testing


text:
Fix missing whitespace in Swift special comments

Hi!
I'd like to contribute with a simple fix for Swift special comments.
Fix missing whitespace in Swift special comments
Added proper spacing after // in MARK, TODO, and FIXME comments for better readability.
changes
Before
//MARK: Section
//TODO: Need to implement
//FIXME: Bug here

After
// MARK: Section
// TODO: Need to implement
// FIXME: Bug here

@swift-ci please test

repo: swiftlang/swift


text:
[embedded] Don't emit metadata references from C++ interop

This resolves a compiler crash when using C++ interop in Embedded Swift:
Assertion failed: (LazyTypeMetadata.empty()), function emitLazyDefinitions, file GenDecl.cpp, line 1330.
...
8  swift-frontend           0x000000010093cf60 swift::irgen::IRGenerator::emitLazyDefinitions() + 3212
9  swift-frontend           0x0000000100a580f8 swift::IRGenRequest::evaluate(swift::Evaluator&, swift::IRGenDescriptor) const + 2632
10 swift-frontend           0x0000000100aa64a4 swift::GeneratedModule swift::SimpleRequest<swift::IRGenRequest, swift::GeneratedModule (swift::IRGenDescriptor), (swift::RequestFlags)17>::callDerived<0ul>(swift::Evaluator&, std::__1::integer_sequence<unsigned long, 0ul>) const + 200

Added a test that reproduces the compiler crash.

@swift-ci please test

@swift-ci please test


text:
[cxx-interop] Fix assert failure exporting C++ types to Obj-C

This is not supported, of course. But now, instead of an assertion failure we properly mark the declaration as unavailable.
Fixes #78190.
rdar://141492654

@swift-ci please smoke test windows

@swift-ci please smoke test linux

@swift-ci please smoke test linux


text:
Documentation comments

This is mainly to support my WIP Tokamak site TokamakDocs. It will auto generate the site from the doc comments on Views in TokamakCore.
I want to make sure there isn't any "No overview available." before merging.

Oh, I've realised just now that this provides inline previews for example code 🤯
Fantastic work @carson-katri! 👏

Fails

:no_entry_sign:

Sources/TokamakCore/Views/AnyView.swift#L27 - Line should be 100 characters or less: currently 101 characters (line_length)

:no_entry_sign:

Sources/TokamakCore/Views/ForEach.swift#L27 - Line should be 100 characters or less: currently 112 characters (line_length)

:no_entry_sign:

Sources/TokamakCore/Views/ScrollView.swift#L29 - Line should be 100 characters or less: currently 118 characters (line_length)

:no_entry_sign:

Sources/TokamakCore/Views/ScrollView.swift#L43 - Line should be 100 characters or less: currently 112 characters (line_length)

  Generated by :no_entry_sign: Danger Swift against 3893b2a06958f38c9de405bae362c1e00f208e19

Fails

:no_entry_sign:

Sources/TokamakCore/Views/AnyView.swift#L27 - Line should be 100 characters or less: currently 101 characters (line_length)

:no_entry_sign:

Sources/TokamakCore/Views/ScrollView.swift#L29 - Line should be 100 characters or less: currently 118 characters (line_length)

:no_entry_sign:

Sources/TokamakCore/Views/ScrollView.swift#L43 - Line should be 100 characters or less: currently 112 characters (line_length)

  Generated by :no_entry_sign: Danger Swift against 4fd0f63235289d5c24b5de61539d38afca3b6179

authors: MaxDesiatov carson-katri ie-ahm-robox

repo: swiftwasm/Tokamak


text:
modifying [selected] input after using header check broken.

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

Certain table UI actions cause ngxDatatable.selected to be a different array from the original [selected] input. i.e. ngxDatatable.selected !== mySelectedRowsObject
This breaks selection by mutating mySelectedRowsObject (push/splice)
Expected behavior

[selected] should always correspond with what is checked in the table.
Reproduction of the problem

http://swimlane.github.io/ngx-datatable/#chkbox-selection

click header check to select all
click header check again to de-select all
click Add in toolbar, which pushes object into [selected] array

Table does not show checks for selected rows even though listed under Selections.
What is the motivation / use case for changing the behavior?

fix selection bug.
Please tell us about your environment:

Official ngx-datatable demo.

Table version: 9.3.0

Angular version:

Browser: Chrome, Firefox

Probably affects all browsers.

Language: [all | TypeScript X.X | ES6/7 | ES5]
all

FYI, one work around for this bug is just to not use [selected] and modify table.selected directly.
  @ViewChild(DatatableComponent)
  table: DatatableComponent;

This issue occurs only in the demo because it uses array.push to change the select elements instead of assigning a new array. By default Angular will detect changes when the object reference changes .Which means if we mutate/change the array it won't detect the changes.
The demo can be fixed by changing a few things:
onSelect({ selected }) {
  console.log('Select Event', selected, this.selected);

  // this.selected.splice(0, this.selected.length);
  // this.selected.push(...selected);
  this.selected = selected;
}

add() {
  this.selected = [...this.selected, this.rows[1], this.rows[3]];
  // this.selected.push(this.rows[1], this.rows[3]);
}

@yehudag I'm not sure this is a ChangeDetection issue. Mutating the array works at first, but certain selection actions in the table create a new array object, which stops mutation from working. Though in the future, if more ngx-datatable components are changed to OnPush mutation would probably stop working. In any case, if developers are expected to re-assign the selected object from onSelect to their selected input, I think this should be documented in the API reference.
https://swimlane.gitbooks.io/ngx-datatable/content/api/table/inputs.html

I have a similar issue to this... I am using my grid as close to an "excel-like" grid as possible. I have it so that, pressing enter, while focused on an input, will select and enable editing on the next row below it, because I only want 1 row to be selected at a time (for now at least, reqs may change in the future). The issue i'm getting is that, after pressing enter, it does it's thing, everything works fine, but when you go to select another row, it spits out this error:
ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'datatable-body-cell pr-1 sort-active active'. Current value: 'datatable-body-cell pr-1 sort-active'.
    at viewDebugError (core.es5.js:8711)
    at expressionChangedAfterItHasBeenCheckedError (core.es5.js:8689)
    at checkBindingNoChanges (core.es5.js:8853)
    at checkNoChangesNodeInline (core.es5.js:12706)
    at checkNoChangesNode (core.es5.js:12680)
    at debugCheckNoChangesNode (core.es5.js:13455)
    at debugCheckRenderNodeFn (core.es5.js:13395)
    at Object.eval [as updateRenderer] (DataTableBodyRowComponent.html:6)
    at Object.debugUpdateRenderer [as updateRenderer] (core.es5.js:13377)
    at checkNoChangesView (core.es5.js:12502)

Luckily, it seems to just be some kind of warning error, because it doesn't stop anything from happening, I just don't like seeing random errors that I can't find a fix for. None of the above solutions worked for me, because I have to clear the list, currently, I do this by setting: this.selectedRows = [];
Is there another way I should be doing this? I tried the =[...] thing, but it just created MORE errors... maybe it's because my onSelect() method isn't modifying the this.selectedRows array?

+1

authors: Adondriel Arti3DPlayer arlowhite yehudag

repo: swimlane/ngx-datatable

license: mit

license_source: bigquery


text:
Titelgrösse in Brennpunkt-Komponente

In der Brennpunkt-Komponente wird der Titel vordefiniert als H4 angezeigt, wenn er ins Feld "Titel" eingefügt wird. Es sollte aber die Option bestehen, die Titelgrösse selber zu wählen, was momentan nur geht, wenn man den Titel unter "Teaser Text" pflegt. Dies hat aber zur Folge, dass der Abstand zwischen dem oberen Rand und dem Titel grösser wird. Beispiel:

@gs-uvek are you speaking of functionality in your CMS Adobe Experience Manager?

Gemeint ist eigentlich die Teaser-Komponente, die im Brennpunkt eingefügt ist:

Ich habe aber gerade festgestellt, dass laut CD Bund die Titelgrösse im Brennpunkt-Teaser doch nicht definiert ist (https://swiss.github.io/styleguide/de/teaser.html#05-teaser-01-focus), was ich übersehen habe. Ist das definitiv so? Falls ja könnte man den Issue schliessen.

ok, question understood, answer pending.

Bei Elementen auf  Übersicht-Seiten müssen die Titelgrössen (H1..Hn) manuell angepasst werden, damit die Seitestruktur semantisch übereinstimmt gemäss Barrierefreiheit-Vorgabe.

authors: bit-pro-iew-eui gs-uvek

repo: swiss/styleguide


text:
support adding examples of special forms?

Janetdocs is great!
Would it be possible to add the special forms to the list of things you can add examples for?
I can add examples for def- but not for def.

Hmm, what would go in the docstring for special forms?

oh, that's a good question.  Maybe for now just a link to https://janet-lang.org/docs/specials.html ?

authors: cellularmitosis swlkr

repo: swlkr/janetdocs


text:
🛑 BestQA_GO is down

In 6279e96, BestQA_GO (https://www.bestqa.net/go/bestqa_dev/up) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BestQA_GO is back up in 566adb4.

repo: swuecho/upptime


text:
🛑 BestQA_GO is down

In 13ac759, BestQA_GO (https://www.bestqa.net/go/bestqa_dev/up) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BestQA_GO is back up in 76941ff after 8 minutes.


text:
🛑 Random site is down

In 9d62968, Random site (https://www.southernjive.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Random site is back up in c434dac.

repo: sxa/aoupptime


text:
🛑 Random site is down

In 3016326, Random site (https://www.southernjive.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Random site is back up in 28e649e.


text:
🛑 Random site is down

In 4d52dac, Random site (https://www.southernjive.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Random site is back up in 94d77a0.


text:
🛑 雙龍體育社區community is down

In fcd92d2, 雙龍體育社區community (http://community.ssangyongsports.eu.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 雙龍體育社區community is back up in 4bccb5f.

repo: sxadxsx/upptime


text:
客户端停止服务端未清除资源

在客户端强制退出的情况，服务端不会清除已经接收到的 project 文件，这是不符合预期的。

由于一些限制，该问题无法修复。

repo: syfxlin/depker


text:
🛑 Concrete Tree is down

In 1b64439, Concrete Tree (https://concretetree.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Concrete Tree is back up in 2b8b7ed after 1 hour, 43 minutes.

repo: symapex/upsite


text:
🛑 Is Green Scene is down

In 9564e63, Is Green Scene (https://isgreen-scene.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Is Green Scene is back up in 692ddd5 after 1 hour, 15 minutes.


text:
🛑 Landscape Topia is down

In f1de6a6, Landscape Topia (https://landscape-topia.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Landscape Topia is back up in 2fcb8c0 after 28 minutes.


text:
🛑 Concrete Elementz is down

In 59fa53f, Concrete Elementz (https://concreteelementz.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Concrete Elementz is back up in 6b9dc45 after 2 hours, 10 minutes.


text:
🛑 Wall Doctor Denver is down

In 64f83ac, Wall Doctor Denver (https://walldoctordenver.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wall Doctor Denver is back up in e47f19c after 1 hour, 1 minute.


text:
🛑 Jacobs Floors is down

In 2e2219a, Jacobs Floors (https://jacobsfloorstx.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jacobs Floors is back up in 9f1e634 after 1 hour, 24 minutes.


text:
🛑 Sprint Fence is down

In 4cf5e77, Sprint Fence (https://sprintfence.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sprint Fence is back up in 05e7b2f after 10 minutes.


text:
🛑 Tree and Lawn is down

In 98cf079, Tree and Lawn (https://treeandlawnco.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tree and Lawn is back up in 8ad2b97.


text:
🛑 Cleanwagon Ohio is down

In 11e37b9, Cleanwagon Ohio (https://cleanwagonohio.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cleanwagon Ohio is back up in f1ad7c3 after 29 minutes.


text:
🛑 Scrubble Carpet Cleaners is down

In 47a3b02, Scrubble Carpet Cleaners (https://srubblecarpetcleaners.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scrubble Carpet Cleaners is back up in ffc03c1 after 41 minutes.


text:
🛑 Dragues Well Repair is down

In b051505, Dragues Well Repair (https://dragueswellrepair.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dragues Well Repair is back up in fb1d610 after 17 minutes.


text:
🛑 Patio Pros Elpaso is down

In 26778ed, Patio Pros Elpaso (https://patioproselpaso.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Patio Pros Elpaso is back up in 05d82ac after 15 minutes.


text:
🛑 Arborcare Ohio is down

In c7a6171, Arborcare Ohio (https://arborcareohio.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Arborcare Ohio is back up in b0e5460 after 10 minutes.


text:
🛑 Global Translation is down

In 624cb6a, Global Translation (https://globaltranslationsrvs.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Global Translation is back up in 313bc88.


text:
🛑 Sound Phonic is down

In be9e723, Sound Phonic (https://soundphonicca.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sound Phonic is back up in 13f00f3.


text:
🛑 Is Green Scene is down

In 84aeda1, Is Green Scene (https://isgreen-scene.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Is Green Scene is back up in 0337981 after 36 minutes.


text:
🛑 Alpha Landscaping is down

In 3fb1b8f, Alpha Landscaping (https://alpha-landscaping.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Alpha Landscaping is back up in cc1bb1e after 3 hours, 16 minutes.


text:
🛑 Blooming Pots Landscaping is down

In 48f3fee, Blooming Pots Landscaping (https://bloomingpotslandscaping.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blooming Pots Landscaping is back up in f7a712e after 42 minutes.


text:
🛑 Pest Busters is down

In 0c56bc5, Pest Busters (https://pestbustersnc.com/) was down:

HTTP code: 502
Response time: 733 ms

Resolved: Pest Busters is back up in 5072a56.


text:
Remove DoctrineMigrationsBundle

I just updated and got DoctrineMigrationsBundle, along with a lot of things that simply I don't need.
Why bloating this pack? Can't we just leave it with minimal requirements?

see #8

Just saw this issue, I'll re-post my comment here:
You can of course still install doctrine/orm and doctrine/doctrine-bundle independently if you want more control over your deps :). The goal with the packs is to package things together that cover the 90% use-case.

can we close this please? Discussed and decided in #8 already.

authors: afoeder fabpot garak weaverryan

repo: symfony/orm-pack


text:
[Doc] Update the syntax of doc images

This will probably fix the following error reported while building docs:
Errors for ux-twig-component / 2.x

Build errors from "2022-05-02 01:21:40"
Missing image file "https://github.com/symfony/ux-twig-component/blob/2.x/alert-example.png?raw=true" in "index"

Closing in favor of https://github.com/symfony/ux/pull/318

repo: symfony/ux-twig-component


text:
Remove dub.selections.json, relax/upgrade ikod-containers, remove -dip25

See each commit as to the why.

Having dub.selections.json committed makes tests much more deterministic, no random breakage from upstream.

repo: symmetryinvestments/concurrency


text:
[2.7.0RC1] Undefined variable

My debugger throws up because of this new delegate. It says $cis undefined, and I’m not exactly sure what $cshould be or where it comes from.

It's a copy paste from elsewhere. I knew I had some unfinished business in 85f30f3e4caaf2983c770e08b28011e9bdc82319 but could not figure out what it was since it has been coded more than a year an a half ago... But I had confidence in it since it ran in production since the same period of time... Thanks to your debugger than!

authors: jensscherbl nitriques


text:
feat: build the app as a CI artifact, publish it under GH-pages for master

The app will point to the staging server.

PR Storybook available here

PR Storybook available here

PR Storybook available here

PR Storybook available here

PR Storybook available here

PR Storybook available here

Eureka!
@paoloantinori this will build the app, point it to staging and upload it as a CI artifact. In theory after merging this will be built and deployed also for GH pages.
The only drawback is that since the app is meant to be installed in the root page, you'll have to manually click on the dashboard to properly start the app; also refreshes will not work.
WDYT?

Wonder, do those failing requests to /metrics/integrations/ cause problems?  I noticed on Firefox that the app sits loading the integrations for a bit and then goes to a blank gray window, either that or one of the integrations there on staging is junk:

Doesn't happen on Chrome though.  I don't see it as a blocker though, we could merge this and then I can raise an issue for Firefox.

Great, thanks! I don't think the limitations are an issue for us.
In case other team need a more controlled env we will redo it in a more kubernetes native way, but this looks sleek, thanks!

Wonder, do those failing requests to /metrics/integrations/ cause problems? I noticed on Firefox that the app sits loading the integrations for a bit and then goes to a blank gray window, either that or one of the integrations there on staging is junk:

Doesn't happen on Chrome though. I don't see it as a blocker though, we could merge this and then I can raise an issue for Firefox.

Even without understanding the root cause of this issue, can we take advantage of this to make the code more robust and turn this outcome into a checked error so that it the ux can degrade gracefully in a controlled manner?

Yup, I was planning to do exactly that today.

PR Storybook available here

PR Storybook available here

PR Storybook available here

Wonder, do those failing requests to /metrics/integrations/ cause problems? I noticed on Firefox that the app sits loading the integrations for a bit and then goes to a blank gray window, either that or one of the integrations there on staging is junk:

Doesn't happen on Chrome though. I don't see it as a blocker though, we could merge this and then I can raise an issue for Firefox.

I just tried FF Dev Edition, it's complaining about CORS error 😰 I'll dig some more

authors: gashcrumb paoloantinori riccardo-forina

repo: syndesisio/syndesis-react-poc


text:
Fix typo to expose Options type

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
The type of Options was exported as the type of the lib/index.js module itself, not the intended Options type.
This fixes that export.

Thanks!

authors: rwe wooorm

repo: syntax-tree/unist-util-inspect


text:
Remove Mesh::targets, as targets only exists inside Primitive

In a glTF asset, only mesh primitives should have a a "targets" property.
This PR remove the unused data structure and parsing code for this non-existent storage for target metadata.

Awesome! merged.
I think when I implemented it(before the glTF 2.0 spec freeze), it was defined in mesh.

authors: Ybalrid syoyo

repo: syoyo/tinygltf


text:
Create about page

A about page needs to be created that describes our blog.

does current link to https://sysco.no/about-sysco/?lang=en cover this issue?

Closing this. If this is still relevant, please reopen.

authors: jeqo jeroenrinzema


text:
fix(sdf): Graph cycles aren't a 500 when editing attribute bindings

We can hold off on merging this until the other intrinsics work ships
via GIPHY

Cherry-picked into #4636. Needed to fix the lint error too, but it's good to go in that PR.

Closing as Nick pulled this into his PR!

authors: britmyerss nickgerace

repo: systeminit/si


text:
configのポート構成あたりの説明がわかりにくい

Summary
configのポート構成の説明がわかりにくいみたいです https://github.com/syuilo/misskey/issues/2791#issuecomment-425718146
# URL and Port settings overview
# e.g., If you want to realize following structure:
#
#               +--- https://example.com:123 ----------+
# +------+      |+-------------+      +---------------+|
# | User | ---> || Proxy (123) | ---> | Misskey (456) ||
# +------+      |+-------------+      +---------------+|
#               +--------------------------------------+
#
# You need to set 'https://example.com:123' to 'url' prop and
# You need to set 456 to 'port' prop.
#
# In other words, the 'url' prop should be the final accessible URL seen by a user.
# 'port' prop is a port that the Misskey server should actually listen
# on and it is not necessarily the port that a user accesses.

url: http://localhost/

# A port that your Misskey server should listen.
# This value is not a port to use when accessing with a browser.
port: 80

urlにポートが必要と誤解する→実際はhttps && 443なので不要
123という表記で別のポート採番が必要と誤解する→実際は443で公開用ポートと同じなので気にしなくてよい
456が特権ポートなのでサンプルとしてよくない
urlとportの既定値があまり使わなそうな値だったり、上の説明と対応してなかったりする。

また、リバースプロキシを使用する vs Misskeyが443をListenするの2パターンの構成が考えられるので、ややこしくなってそう。

Environment

# URL and Port settings overview
# e.g., If you want to realize following structure:
#
#               +----- https://example.com/ ------------+
# +------+      |+-------------+      +----------------+|
# | User | ---> || Proxy (443) | ---> | Misskey (3000) ||
# +------+      |+-------------+      +----------------+|
#               +---------------------------------------+
#
# You need to set 'https://example.com/' to 'url' prop and
# You need to set 3000 to 'port' prop.
# You need comment out 'https' section.
#
# In other words, the 'url' prop should be the final accessible URL seen by a user.
# 'port' prop is a port that the Misskey server should actually listen
# on and it is not necessarily the port that a user accesses.

url: https://example.com/

# A port that your Misskey server should listen.
# This value is not a port to use when accessing with a browser.
port: 3000

などとすればわかりやすそうなものの、
この場合Reverse Proxy必須となるのでReverse Proxy(Nginx等)の手順についても補足が必要になりそう。

nginxとかのサンプルの設定もあった方がよいのかな

MastodonはガイドにNginxの設定があったり
https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md#nginx-configuration
PleromaはNginxのサンプルが用意してあったり
https://git.pleroma.social/pleroma/pleroma/wikis/Pleromaの入れ方#nginx
するみたいなのであってもよさそう
私はこんな感じだわ
https://github.com/mei23/memo/blob/master/misskey/Setup-Ubuntu1804-Quick.md#管理者ユーザでnginxとssl証明書を設定

ありがとうございます！
私はnginxの知識全くないのでドキュメントは後回しになりそうです

私もこの図見て、 🤔… → 😭なんぞこれ…
って試行錯誤しましたわ…
最終的にurl:をhttps://から初めて、port: 443にして、TLS設定するとうまく行きました。
しゅいろさんはどっちなんだろう…？ 🤔

ドキュメント修正しているのもう大丈夫そう

repo: syuilo/misskey


text:
Misskey => Misskey で renote 出来ない件修正

Resolve #1543
src/remote/activitypub/kernel/announce/note.ts
主にここ
x activity.cc
o note.cc
判定方法もCreate noteと同様に修正
src/remote/activitypub/renderer/announce.ts
idにURLを使用するように、他の項目も送るように修正
Mastodon => Misskey
Misskey => Misskey
Misskey => Mastodon
のパターンで確認済みです

ありがとうございます！！🙏🙏🙏🙏


text:
help setting zsh up

I'm having difficult time setting zsh up. Can you tell me what i have to do in order to get it working
Thanks

Well, you only need to do:
$ cd dotfiles
$ ./install --zsh
$ stow zsh

./install --zsh will install the plugins oh-my-zsh and spaceship.
And i use zsh with keychain too if need install dependencies.

stow zsh did not work. its not linked I believe. downloaded your dotfiles. I just copied the files in zsh folder to $HOME

getting this
compdef: unknown command or service: rails

it come from the .zshrc
plugins=(git git-prompt ruby rails)

You can remove ruby and rails
plugins=(git git-prompt)

The list of plugins can be show here

you don't use ruby and rails? what is it used for.

i use ruby and rails for other projects but not in this repository

What are they used for. Also how would i go about adding more plugins. Like if i wanted them what would i do.

Completion plugins will let zsh know which arguments the package has so it can autocomplete.

So let's say i wanted rails. how would i get it working?

Well if you use ruby or rails, there are probably alrealy installed
# pacman -S ruby rails

Add the completion:
18 plugins=(git git-prompt ruby rails)

Reload zshrc
$ source ~/.zshrc

and it's alll

pacman -S ruby is installed but
rails isn't in the AUR
I checked yay couldn't find it
➜ source ~/.zshrc
compdef: unknown command or service: `rails

I need rails installed i think?

I installed it like this gem install rails
➜ ruby -v
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]

~
➜ rails -v
Rails 5.2.3

I still get
compdef: unknown command or service: rails

I just removed rails like you said at the beginning :) That fixes that

repo: szorfein/dotfiles


text:
When String gets long in TextView, Inserting Predictive text results in scrolling to top.

Hi @szweier, I am still facing this issue in new update.

repo: szweier/SZMentionsSwift


text:
Luasocket dep

This is cool, I love the simplification over gfx.js.
Quick Q: do you need the latest luasocket? Specifying the 3rc version doesn't work for me.

Thanks!
Seems luasocket 2+ is good enough. See f30c20e469e925d0e7fdee3825fba9e832edaf33

great!

authors: clementfarabet szym

repo: szym/display


text:
Error with setting up python subprocess (Macbook)

Hi,
I have the following error when trying to play the "Passing data types 2 demo". I did dowload the pypeline library. Do you have an idea how to solve this?
root.pyCommunicator:
Problem with setting up Python Subprocess:
Caused by: Input returned null; Error stream line reads: Traceback (most recent call last):
File "/var/folders/xt/f4729vqn5zn79c1942d4_tsw0000gn/T/pypeline-server_6617826609874667048.py", line 5, in
from json.decoder import JSONDecodeError
ImportError: cannot import name JSONDecodeError

Hello! AFAIK, that error happens when trying to use Python 2 - what Macs have installed by default. The Pypeline server file (and thus Pypeline more generally) currently only supports Python 3.
The simplest option is to install/use a version of Python 3 and then configure the PyCommunicator to use that version. If you really need to use Python 2 though, you'll need to fork the project and modify the source Pypeline model (which is where the server file is generated from) accordingly.

(I'm closing this but feel free to ask any follow ups!)

authors: IwanHuisman t-wolfeadam

repo: t-wolfeadam/AnyLogic-Pypeline


text:
emacs  path.c assertion "length2 > 0" failed

Warning: no reproduction yet
[ ] - bisect packages to identify package triggering paths.c
[ ] - create minimal repro with emacs -Q
Using my quite large emacs config i get the following error.
./path/path.c:547: Comparison compare_paths2(const char *, size_t, const char *, size_t): assertion "length2 > 0" failed
  proot warning: signal 6 received from process 5597

Putting this here in this pre repro state in case others want to see state of emacs support or someone recognizes that error.
I'll debug this further as time allows.

I encounter the same issue in my fairly vanilla Spacemacs config but only when I try to C-x C-f/SPC f f (handled by HELM in my case).

Could you post your minimal config and exact instructions on how to reproduce this error?

.spacemacs from atemu/dotfiles@ac526f496eccda63ebacacf77fc356651756ed31
.emacs.d is syl20bnr/spacemacs@d95d41f55ba074128b3ed8f0eedcdc3c31b52e42

Run emacs
Let it install all the packages (I needed to set the elpa timeout to something higher than 5s, YMMV)
C-x C-f

I ran into the same issue. Using ivy instead of helm doesn't trigger this bug.
There seems to be a fix in https://github.com/0pq76r/proot/commit/7d7479c490de083729253f120a5e9a9c5bd47d0c but it's not yet upstream.

I am finally able to reproduce it:
emacs -Q --batch --eval '(directory-files-and-attributes "/data/data/com.termux.nix/files/usr/bin" nil "\\`[^.]" t (quote string))'

Nice, i can confirm to get the same error. But could you explain, what this does and what similar commands you tried that worked? I'm asking for so many details because I have neither used emacs nor came in touch with the nix expression of emacs and its dependencies.

I basically opened an eshell within emacs and did an ls in the usr/bin directory and that crashed, other directories work just fine. Afterwards I stepped through the callstack and ended up in the function mentioned above. Said function is implemented in C which makes debugging much harder. Currently, I'm trying to extract a single C function that triggers the bug, based on this source: https://github.com/emacs-mirror/emacs/blob/c70a3a41630a39283f10f183cefb4643a6d424cc/src/dired.c#L166

Just tried again, a simple ls -a in my $HOME from within eshell does also crash. That means, it's not specific to the directory but its contents somehow. Doing the same things using the real ls and not the emacs version, works in all cases.

It seems to be the link to /nix, i.e. the .nix-profile. I tried the following steps:
emacs -Q
M-x eshell
mkdir tmp
cd tmp
ls
# ok
ln -s /nix .
ls
# bam

Does it fail the same with other proot-rerouted locations like /tmp or /usr?
Should we incorporate the fix linked above in advance into our proot build?

Funny, /tmp is ok, /etc /bin are not.

Hi, how can I get a custom version of proot into my nix-on-droid installation? I'm still a noob regarding nix :(
Btw. the issue is reproducible on my laptop as well, but I didn't have time to figure out which syscall fails in proot. My goal is to have a unit test along with a fix for proot.
Is there an irc (or similar) channel for nix-on-droid?

It's not a particularly simple process, as it can't be built on-device (refer to https://gist.github.com/t184256/c79d270498e8441d0f4e3c9be7acad18 if you want an overview of how the building happens and how to start with your own channels and bootstrap zipballs).
Meanwhile, you can try bootstrapping from https://nix-on-droid.unboiled.info/bootstrap-proot-fix (corresponds to proot-fix branch, where I've applied patch mentioned above to proot) and verify whether it fixes the issue.
As for a support chat, we don't have any, though maybe we should have one. Got any specific suggestions?

The fix seems to work. I replaced my proot-static binary with the one from your package and emacs does not crash anymore.

I've merged the fix (9b4fb44) into the master branch then.

authors: Atemu Gerschtli codygman jakalx t184256


text:
htop: 6147 illegal hardware instruction  htop

file $(realpath htop), please.
What's your architecture?

Sorry, file $(realpath $(command -v htop)).

❯ file $(realpath $(command -v htop))
/nix/store/ngkjdhwxdwm39iqm6p4cw0ax5isz23i2-htop-2.2.0/bin/htop: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /nix/store/ikl21vjfq900ccbqg1xasp83kadw6q8y-glibc-2.32-46/lib/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not stripped

❯ uname -a
Linux localhost 4.4.223-g52750b8f2138-ab6846512 #1 SMP PREEMPT Fri Sep 18 09:49:34 UTC 2020 aarch64 GNU/Linux

Pixel 2, android 11

Which versions of nix-channels/flakes you are using? Does it work with the latest 21.05 release of nix-on-droid?

Tried on a clean install of 21.05, couldn't reproduce (/nix/store/5m59dfvmnnk9mrrzpd2ak98v9za4s11y-htop-2.2.0/bin/htop).
Interestingly, it seemed to build it, even though it seems to be in cachix.

I'm following nixos-unstable with flakes. at 1905f5f2e55e0db0bb6244cfe62cb6c0dbda391d.
My config is at https://github.com/bbigras/nix-config . Since today, the github actions are building my nix-on-droid config too (since I saw that this repo does it too).
I'll try to find the time to test with 21.05 soon.

Since today, the github actions are building my nix-on-droid config too

Wait, so that's where this x86 htop comes from?

since I saw that this repo does it too

This one compiles the part that's cross-compiled.

I had the problem with htop before today. I didn't realise it was x86. Maybe the problem is only with the overlays since I have been building and pushing from my computer to my phone for a while now.

authors: Gerschtli bbigras t184256


text:
Failed to turn on BTI protection

I'm unable to get a shell on Samsung galaxy z flip 4
/data/data/com.termux.nix/files/usr/bin/sh: /nix/store/9b6mgv7wzg964rf292s9x49n5g8yfgkp-glibc-2.32-54/lib/ld-linux-aarch64.so.1: failed to turn on BTI protection

[Process completed (code 127) - press Enter]

I encountered this problem as well on my Galaxy S22. The reason is that glibc 2.32 bundled in the Nix bootstrap tarball lacks a recent fix. I'm working on a fix (bump to Nix 2.11.0) and will send a PR soon.

I opened #200 to fix this.

Should be resolved, please clear the app data or reinstall, then bootstrap from https://nix-on-droid.unboiled.info/bootstrap or https://nix-on-droid.unboiled.info/bootstrap-testing.

authors: dlip t184256 zhaofengli


text:
fix: incorrect behavior of SKIP_ENV_VALIDATION

The current logic for checking SKIP_ENV_VALIDATION will pass if SKIP_ENV_VALIDATION is assigned to any value other than an empty string (even false). Ideally, SKIP_ENV_VALIDATION should only pass when its assigned value is true and nothing else.
Closes #
✅ Checklist

[x] I have followed every step in the contributing guide (updated 2022-10-06).
[x] The PR title follows the convention we established conventional-commit
[x] I performed a functional test on my final commit

Changelog
fix the logic for determining whether it should validate environment variables or not

Screenshots
[Screenshots]
💯

I think the best way to do coercion here is to accept

input
resolved

false

""
false

"false"
false

"0"
false

any other values resolves to true

Agreed, the ideal behaviour would be that truthy values evaluate to true

Thank you for your input. Given that type of environment variables string, only process.env.SKIP_ENV_VALIDATION=, process.env.SKIP_ENV_VALIDATION="" or doesn't specify it at all (undefined) will be falsy, any other values will be evaluated to truthy (including "false", and "0").
In response to @c-ehrlich, I disagree that all truthy values should evaluate to true, since "false" or "0" would be evaluated to true if that were the case.
Regarding @juliusmarminge's point, while undefined and "" evaluate to false by default, "false", "0" evaluate to true, we could address this by specifically checking if the value is "false" or "0" and returns false, however, I believe this approach might result in a more verbose implementation.

authors: c-ehrlich juliusmarminge mickyngub


text:
Instagram sharing: How to?

Instagram sharing: How to?

No, it appears it's not supported by Intagram: http://stackoverflow.com/questions/30542054/does-instagram-have-share-button-or-not

authors: biapar tabalinas

repo: tabalinas/jssocials


text:
"(live test)" link should sometimes use https

https://github.com/tabatkins/bikeshed/blob/77332301562e2ce812c013f8fa6debde320dd06e/bikeshed/wpt/wptElement.py#L74
See logic in https://github.com/web-platform-tests/wpt.fyi/blob/master/webapp/components/test-runs.html#L74
Also, could consider using web-platform-tests.live instead of w3c-test.org, I think the former has higher chances of being maintained.

Nice, fixed in df73ddac, both for scheme and new url.

authors: tabatkins zcorpan

repo: tabatkins/bikeshed


text:
[[#li-id]] should generate text of the form "step 7" or "step 6.3"

I'd like a :horse:: I want to refer from one step in an algorithm to another, but if I write "see step 7", that'll get out of date as I change the steps, just like "see section 3" would get out of date. [[#section-id]] works to link to a section resiliently, and the same could work to link to a step in an algorithm. It should fail if the target isn't inside a tag with an algorithm attribute, and if the target is a cross-algorithm reference, the text could be "step N of the <algorithm-name> algorithm".

Sounds great to me. :+1:

Request from @equalsjeffh: Also allow this autolinking to go to figures. While I'm at it, do examples and notes, if numbered.

Note: HTML machinery itsel apparently does not "know" that a particular <ol> step <li> may a part of a multi-layer list, eg "step 6.3" --- thus rendering the latter would have to be done entirely in bikeshed(?)  but then the actual rendered list numbers themselves would still be singletons and might that confuse readers? (it has in my experience when referring to "step 6.3" that's rendered as

 bar

 baz

how do I make it be an entirely-numbered list?

Are there any issues submitted on HTML along the lines of "make rendered list items of multi-layered lists be numbered in a fully-qualified fashion" (this lazy search-challenged person asks)?

I'm not sure what you mean. All I have to do is walk the ancestor chain and count up lists. If you're putting a bunch of separate algorithms into a numbered list that'll fail, but... don't do that, it's weird. (I'm pretty sure no one does in any spec.)
And yeah, the bullet styling might not make for the easiest time converting a number into a particular step, but it's fine.

I'm not sure what you mean.

sorry, no worries, my mis-understanding, thanks for the clarification, ...

the bullet styling might not make for the easiest time converting a number into a particular step
but it's fine.

... tho, I think reasonable people may disagree about the latter claim.

authors: equalsJeffH jyasskin tabatkins


text:
This package should allow specifying the Validator binary path

what happens now
The js-validator package CI tests cannot use this package to determine if a given PR is going to work.
what I would like
This package should be able to be used by the js-validator package to run smoke-screen tests.
additional context
I'd like to be able to pass in a specific path to the validator binary.  So that PRs in the js-validator package can be tested via CI using smoke-screen tests.

fixed by #423

repo: tablelandnetwork/local-tableland


text:
Missing some modules on NPM registry

In order to extend and replace some of Tachyons' modules, I tried importing everything from the main source file. However, my install script failed for tachyons-negative-margins, tachyons-nested, and tachyons-debug-children, saying that none of these modules exist on NPM.
Any chance we could get those these three published like the rest? :)

There is a chance. Not something that is actively supported at this time to be in sync with core.

Not something that is actively supported at this time to be in sync with core.

@mrmrs, I'm a bit confused by this. Are you saying that I shouldn't rely on the individual modules to be kept up-to-date with changes to the monolithic core? Doesn't that kind of break the principle of modularity listed on the main page?

Tachyons isn't just a monolithic framework. It's a collection of small modules that can be mixed and matched or used independently. Use what you need. Leave the rest.

The modules can still be mixed even if they are a bit behind. I don't believe this affects concepts of modularity at all.

On 1 Jun 2017, at 01:57, Austin Wood notifications@github.com wrote:
Not something that is actively supported at this time to be in sync with core.
@mrmrs, I'm a bit confused by this. Are you saying that I shouldn't rely on the individual modules to be kept up-to-date with changes to the monolithic core? Doesn't that kind of break the principle of modularity listed on the main page?
Tachyons isn't just a monolithic framework. It's a collection of small modules that can be mixed and matched or used independently. Use what you need. Leave the rest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah, that's a fair point.
I guess it's just that having the modules behind the monolith—on top of having some of the modules nonexistent on NPM at all—makes the modular nature of Tachyons feel a bit like a second-class citizen, rather than a front-running principle.
I can empathize with the difficulty of keeping the modules in sync with core though, and I believe there is some progress being made on publishing individual modules from the monolith, so I know y'all are working on discovering the best way to make this work.
I appreciate the thoughtful work that has been put into this repo, and look forward to watching it grow and mature 💛

For posterity, it looks like tachyons-negative-margins is now a thing! 🎉

Thanks for creating this issue @indiesquidge. tachyons-debug-children was still missing from the npm registry. I've gone ahead and added it. When we release v5 the updating of all modules will become automated so that users using the individual modules won't have to wait for updates.

authors: indiesquidge johnotander mrmrs

repo: tachyons-css/tachyons


text:
Allow underscores as unused variable identifiers

Closes #319

[x] I have updated CHANGELOG.md
[x] I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
[x] I have run all the tests locally and no test failure was reported
[x] I did not do unrelated and/or undiscussed refactorings

As of now, it only works for foreach and catch, right?

As of now, it only works for foreach and catch, right?

Are there any other cases where we need it?

Are there any other cases where we need it?
I don't think so, at least now. When we'll have #298 in the future, identifiers in let declarations would them though.

When we'll have https://github.com/tact-lang/tact/issues/298 in the future, identifiers in let declarations would need them though.

Actually, let-statements should have underscores even now. This can be used as a clear indication that some functions gets called not for its return value but for its side-effects:
let _ : Foo = effectfulFun(x, y, z);

When we have a bit of type inference, the snippet above will become
let _ = effectfulFun(x, y, z);

In this case a static analyzer won't complain about unused values, whereas it should issue a warning for
effectfulFun(x, y, z);

if effectfulFun is a non-void function.

Added support for let-statements and also resolved all merge conflicts

resolved merge conflicts

@anton-trunov resolved merge conflicts yet again after merge of #198

@anton-trunov resolved everything

authors: Gusarich anton-trunov novusnota

repo: tact-lang/tact


text:
Adjust panel and map animations

Placeholder task to polish the animations around panels + map interaction

Resolved by https://github.com/tahowallet/dapp/pull/783

authors: jagodarybacka xpaczka

repo: tahowallet/dapp


text:
feat: Bridging from L2 to L1 wait time needs to be improved

Describe the feature request
The wait time to bridge from L2 to L1 on taiko is much slower than the bridge from L1 to L2. I love how fast L1 to L2 is. Perhaps you can provide a map of the transaction during bridging so users can see where the transaction is at and have a better idea of how long it'll take.
Describe alternatives you've considered
Look at the map of transactions from L1 to L2 and reverse exactly that during L2 to L1 to mimic the same speed for bridging.
Additional context
transactions performed on wallet: 0x139BD32a991b9D367952677B33FE749d4b660745

Hi @kathy1208tn the L2 to L1 bridging is slower as compared to the other way around, as is also mentioned in the status explainer tooltip. This is because L1 => L2 bridging can happen as soon as the bridge tx is included in L1, but when it comes to L2 => L1, our protocol wont be able to process that L2 => L1 bridging message, unless its corresponding L2 block is verified ( proof submitted then wait an avgProofTime delay ).

repo: taikoxyz/taiko-mono


text:
fix: allow default values for input arguments

Issue Reference(s):
Fixes #1931
/claim 1931

there is an issue with async-graphql as well, I raised a PR https://github.com/async-graphql/async-graphql/pull/1527 there if it gets merged, I'll finish touchups in this PR.

repo: tailcallhq/tailcall


text:
Overriding of environment variables

We should fix how environment variables are overridden.
Currently environ configured in the yaml file has precedence, but it looks like useless. Note, we don't use environment variables from user environment by default.
So the order of precedence from the highest priority to the lowest one should be:

Options -E/--environ in the command-line
Options -e/--use-env in the command-line
VAGGAENV_* variables
Variables set explicitly in settings (TODO in #301)
Variables that are allowed to propagate in settings (TODO in #301)
Variables set in command
Variables set in container: environ dict
Variables set in container: environ-file
Variables that are auto-propagated: *_proxy, TERM

P.S.: another good idea to add the list to the docs
/cc @anti-social

Fixed by #331

repo: tailhook/vagga


text:
Change default purge config value to be a new object instead of array

This pull request just changes the default value when creating the tailwind config file in CLI to be a new object instead of array. I saw myself changing it by default in many projects since I think controlling the purge option from there is a more declarative way when working the tailwind.
It isn't a new feature, just a small modification to the default behaviour.

Going to keep it as an array for now just because that's the way I use it on my own projects. If there is overwhelming demand to default to an object instead of an array we can definitely reconsider. Thanks though!

authors: adamwathan ahmadabuaysheh

repo: tailwindcss/tailwindcss


text:
Specificity of utilities within prose

Hi, this plugin is really awesome! When I want a  within .prose to have .mb-0, it won't be set:

This is my tailwind.css (I use Nuxt):
@import 'tailwindcss/base';

@import 'tailwindcss/components';

@import 'tailwindcss/utilities';

Am I doing something wrong?

Just an unfortunate consequence of CSS specificity I'm afraid. See similar discussion here: https://github.com/tailwindcss/typography/issues/26

Thanks! Keep up the good work! :)

authors: adamwathan gizburdt

repo: tailwindcss/typography


text:
三国志II-霸王的大陆不能运行

大佬，我下载了好多个版本的rom(.nes)，打开时都提示我：读取失败，模拟器不支持该游戏ROM。
有原版的，有汉化的，都是不行，为啥？

模拟器并不能支持所有ROM。

repo: taiyuuki/vscode-nes


text:
バックアップの方法を検討する

github actions で s3 にアップロードする。

デプロイのたびに s3 に以下のように日付のフォルダに分けてバックアップを保存するようにしました。

repo: takamatsu-city/opendata


text:
Add .spec to unittest-switcher.unittest.suffix as default

Angular 2 uses .spec.ts files as convention, it would be great if you could add it as default option

Thank you.
I will consider it positively.

When will this fix be released?

Oops. I Forgot. I will release it.

authors: duydao prashaantt takas-ho

repo: takas-ho/vscode-unittest-switcher


text:
selectig code in commit diff selects linenumbers too

as the issue title says. if you try to select multiple lines on a commit diff, it also selects the linenumbers. that is pretty annoying. :(

@mrkm4ntr Thanks for your work :-)

authors: dodgex takezoe

repo: takezoe/gitbucket


text:
Maybe: split out flit_core?

Flit now looks like a combination of two things: machinery for packaging simple pure-Python packages with no build step, and command line tools for developers to produce, validate and upload such packages. When Flit is automatically installed as a PEP 517 backend to build a package, it's bringing in dependencies which aren't really needed for that purpose.
One approach I'm considering is to split out a flit_core package with minimal dependencies which handles building packages and not much else. This would provide the PEP 517 backend, while flit continued to provide the associated tooling.
From my experience with the 'big split' in Jupyter, I'm wary of over-splitting, where no-one knows what package is responsible for what. So I'd like to stick to two pieces, keeping them in one repository with one set of documentation.
While I'm reluctant to go 'backwards', it may also make sense for flit_core to support Python 2.7 for a while. When I made Flit py3-only, producing Python 2 compatible wheels was enough compatibility. PEP 517 introduces an assumption that packages can be built on the same Python that they are to be installed on. I don't currently have a good answer for how Flit, PEP 517 and Python 2.7 can coexist peacefully. A split would provide an answer for this without having to make all the code support Python 2.
This was prompted by this long discussion about bootstrapping PEP 517 backends on the Python discourse board. Looking back, it's not dissimilar to what was proposed in #101.

Thanks. I haven't totally decided about it yet, and if I go for it I'll probably want to do the initial reorganisation myself (it's kind of my baby ;-)). But if I find grunt work that needs doing, I'll let you know. :smile:

I did go for this plan, and it is out now as Flit 2.

repo: takluyver/flit


text:
Crashes immediately (was working before)

Hey - this app was a godsend until it suddenly stopped working. Now it crashes immediately on launch. Any ideas on how to debug ? Maybe I changed something on my phone.

It's not working for me also, I'm working on a fix

@anirudhgarg Fixed, please update the APK :)

Great, thanks for the quick fix. It works now :) I was also about to tell you that if I tried to share  http://about:blank with the Notion sharing option it says that this is not supported. Looks like just changing that made it work. Thanks again 👍


text:
Request for code release

@taliabensimon
Thank you so much for your wonderful work & paper.
Would you please share the codes to reproduce experiments in your paper?

+1

authors: donggangj pratikrep


text:
feat: allow string sizes (e.g. rem)

this allows me to specify font size for web using rem
I'm not sure if there's a reason tamagui currently prefers everything to be px but I don't see why it should forbid using other units.
Let me know if I should add some docs / tests / whatever
thank you! :)

This would fail on native unfortunately. There are talks to support rem and other sizes in RN.

@natew yes, but I can specify different config for web and for native

Yea Tamagui does need to support web-only use case, that's a big advantage we're working on. Especially with @tamagui/web not finding it's feet.
Still not easy to figure out the best solution here, some people want stricter types and some don't. The changes in fonts to not assume number is great though. Happy to accept a series of PRs here.
React Native has some plans to support relative fonts too at some point.
The ideal maybe that @tamagui/web defaults to allowing string, @tamagui/core is more strict, but then you can override it somehow to enable them. Potentially adding an option in createTamagui({ useStrictFontUnits: false }).

@natew thanks for the comment 🙂
however, I'm slightly confused as to what changes I should make in this PR, if any 😄 . Should I remove changes made in packages/font-inter/src/index.ts and keep the ones in the web package? Or do you prefer doing this yourself and I can close the PR?
Thank you 🙂

@vonovak it gets tricky for inter. I think for web we can have string types, but for core we'd need to limit them to whatever only RN supports. The idea is over time since web only targets web it can be more flexible, but core is the strict RN subset. It's not the easiest making types thread through like that but if you can get them working I'll help out and get this merged.

We can track in issues or discussions

thread

we can get Dimensions for react native and use rem value that has been set in config

authors: natew sinafath vonovak

repo: tamagui/tamagui


text:
Updating to socket 1.0 and Express 4

Took a liberty of copying your code and make it run under socket.io ver 1 and express 4 located here: https://github.com/forddyce/programme-chameleon/tree/master/public/app
Was going to add download feature (I will add a table and when a user clicks on download button the  will export as xlsx and download, table created by room master and downloadable by participants). Also going to add feature on showing what room I'm currently at, and a "logout" button without the need of refreshing the page. Any ideas on the feature I mentioned?

@forddyce as soon as i type a message , I get "Cannot read property 'rooms' of undefined" and the server crashes.

repo: tamaspiros/advanced-chat

license: unlicense


text:
Ensure socket closes properly

The socket is being held open by the writable handle. Close both the handle and the socket.
To do this we need to store the handle as a member variable.

Don't forget to update the README when you make the next release. Only one known issue now :-)

repo: tamentis/rpdb


text:
OutOfMemoryError

I've seen this on two devices at least, occurs at AdbProtocol.java#L323:
java.lang.OutOfMemoryError: Failed to allocate a 1598575456 byte allocation with 7544583 free bytes and 248MB until OOM, target footprint 15089167, growth limit 268435456
	at com.cgutman.adblib.AdbProtocol$AdbMessage.parseAdbMessage (AdbProtocol.java:276)

https://github.com/cgutman/AdbLib/issues/13

The header it read was wrong. By definition, if the header was wrong, it would have to close the connection immediately. The method in question has no sanitisation at all which is causing this problem, I believe.

authors: MuntashirAkon mirfatif

repo: tananaev/adblib


text:
Maven project type

i want to develop it from scratch which of the following maven project need to be select in netbeans for traccar

You need to install the following plugin: Maven Utilities

Also, you have to import project, not create a new one.

authors: Turbovix d33pak-s1ngh tananaev

repo: tananaev/traccar


text:
IOS-6427: Add base blockchain

IOS-6427
Ветка пока сделана от релиза 5.9, как обсуждали на дейлике

так ветка же на develop должна смотреть)

так ветка же на develop должна смотреть)

Ок, поменяю
но добавлять интеграцию в апп становится адово
потому что там это делается с ветки 5.9, в деелопе bsdk уже есть ломающие изменения, а ветка с бейзом еще не влита, чтобы ее можно было черрипикнуть в releases/develop-548

так ветка же на develop должна смотреть)

Ок, поменяю но добавлять интеграцию в апп становится адово с этими правилами
потому что там это делается с ветки 5.9, в девелопе bsdk уже сейчас есть ломающие изменения а ветка с бейзом еще не влита, чтобы ее можно было черрипикнуть в releases/develop-548

Коммит base в develop bsdk
Черрипик в соответствующую releases/develop-XXX
Коммит в релизную ветку приложения с этим тэгом
Синк release в develop с уже нормальным тегом из шага 1.

Получается сложно, но проще непонятно как сделать. Так у нас гарантированное синк безопасный, ничего не потеряем между хотфиксами и релизами. Можно попробовать в приле сделать такой же подход, тогда инков не будет, только черрипики

так ветка же на develop должна смотреть)

Ок, поменяю но добавлять интеграцию в апп становится адово с этими правилами
потому что там это делается с ветки 5.9, в девелопе bsdk уже сейчас есть ломающие изменения а ветка с бейзом еще не влита, чтобы ее можно было черрипикнуть в releases/develop-548

Коммит base в develop bsdk
Черрипик в соответствующую releases/develop-XXX
Коммит в релизную ветку приложения с этим тэгом
Синк release в develop с уже нормальным тегом из шага 1.

Получается сложно, но проще непонятно как сделать. Так у нас гарантированное синк безопасный, ничего не потеряем между хотфиксами и релизами. Можно попробовать в приле сделать такой же подход, тогда синков не будет, только черрипики

Это про финальный уже флоу, тут вопросов нет
Я скорее про флоу интеграции в апп, как сейчас с бейзом выходит - для радианта в аппе в 5.9 надо делать в коде временные заглушки, чтобы проект собрался
Но тоже пока непонятно, как это можно улучшить

repo: tangem/blockchain-sdk-swift


text:
style(heo): 修复在较小屏幕尺寸时，文章宽度样式问题

修复在屏幕宽度变小的时候，heo 主题下文章存在 code 时，文章宽度异常的问题。具体参考下面前后优化。

这个问题是由于 code 标签的存在，而code的父元素没有给指定宽度导致的。没有code的文章详情时没问题的


text:
Add on_source

Closes #103. @hashue Would you mind reviewing this pull request?

@tani
It's worked for me!
Thx for super prompt response  !!!

Great. However the CI is down so I have to fix the bug. Please wait for a
while.
2022年12月23日(金) 7:21 Hasu @.***>:

@tani https://github.com/tani
It's worked for me!
Thx for super prompt response !!!
—
Reply to this email directly, view it on GitHub
https://github.com/tani/vim-jetpack/pull/104#issuecomment-1363400543,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGJR7TN5J7VT2BP3XPV253WOTH73ANCNFSM6AAAAAATGYPDWY
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: hashue tani

repo: tani/vim-jetpack


text:
compile fail, ubuntu 14.04

swift build
Compiling Swift Module 'Vapor' (18 sources)
/home/mac/swiftdev/vapor/Sources/Parser.swift:36:42: error: value of type 'String' has no member 'stringByReplacingOccurrencesOfString'
let key = cookieArray[0].stringByReplacingOccurrencesOfString(" ", withString: "")
~~~~~~~~~^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Can you paste the output of "swift --version" ?

authors: alloyapple tannernelson

repo: tannernelson/vapor


text:
Correct way to recover original Path from Facet?

I am trying to recover a file path from a facet. I noticed in the docs there is encoded_bytes which for some reason is encoded_str on my machine, maybe the docs aren't up to date?
In any case my solution so far has been something like this
let mut location = String::from("/");
location.push_str(my_facet.encoded_str().replace(char::from(0), "/"));

Is this the right way to handle it?
What happens when I insert a windows style path with no leading / eg: C:\path\to\file?

RIght now it seem you can only use the Display implementation.
It will escape / characters that are not meant to be a separator by  a \.
let path = format!("{}", facet)

I leave the bug open to introduce a simpler method than calling Display.
For the second question, your path is required to be  /a/b/c.
Just preprocess your filepath as /c/path/to (i would not include the filepath, and stop at the parent directory.)

Reopening... @fdb-hiroshima Your patch is ok, but I think originally @teovoinea wanted a string representation of the path eg: //papa_branch/kiddie_branch/leaf

authors: fulmicoton teovoinea

repo: tantivy-search/tantivy


text:
Code to remove duplicates from a sorted linkedList

Solved issue number #78

It was my first time contributing to any repo, had learned a lot from it.
Really was a good experience !!

That's great 😊


text:
Create 387 b

https://codeforces.com/contest/387/problem/B
soln to this

Give this repo a star and follow me for follow back 😊


text:
Make server restart on file changes in code

Is it possible to have responder restart on file changes?
Something like --reload flag in gunicorn?

uvicorn is already installed as a dependency. So, taking the basic example from the docs:
import responder

api = responder.API()

@api.route("/{greeting}")
async def greet_world(req, resp, *, greeting):
    resp.text = f"{greeting}, world!"

if __name__ == '__main__':
    api.run()

Let's say this module's name is main.py. You can enable auto-reload by running:
uvicorn main:api --reload

Awesome, thanks for pointing that out!

authors: mpaepper whippiii


text:
Use cksum instead of shasum

cksum is a POSIX standard and therefor on most, if not all, Unix
flavors.
While it has more collisions than sha256, it is faster.  And the
collisions don't matter much for checking if the cache is old or not.
Closes: #72

Thank you.

authors: docwhat tarjoilija

repo: tarjoilija/zgen


text:
Use region predefined by Lambda

Use region predefined by Lambda.

Ref: tarosky/gutenberg-imgconv#3

Ref: tarosky/gutenberg-imgconv#3

repo: tarosky/gutenberg-imgserver


text:
🛑 Immich is down

In d8ea57f, Immich (https://immich.goka.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Immich is back up in 6b02441 after 10 minutes.

repo: tastelessjolt/upptime


text:
内存问题

作者大大您好！我想问下，运行的日志上显示的占用的内存大概为九千多，为什么在服务器上实际占用两万多MB呀？
然后目前跑的最好的结果为：0.410，还未能达到论文里面的精度，是有哪些地方需要改善吗？

这是我的配置：
2024-12-10 23:09:03,773 - mmrotate - INFO - Environment info:
sys.platform: linux
Python: 3.7.16 (default, Jan 17 2023, 22:20:44) [GCC 11.2.0]
CUDA available: True
GPU 0,1: NVIDIA GeForce RTX 3090
CUDA_HOME: /usr/local/cuda-11.4
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.9.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.1.2 (Git Hash 98be7e8afa711dc9b66c8ff3504129cb82013cdb)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 11.6
Built with CUDA Runtime 11.1
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_37,code=compute_37
CuDNN 8.0.5
Magma 2.5.2
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.1, CUDNN_VERSION=8.0.5, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.9.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.10.0
OpenCV: 4.10.0
MMCV: 1.7.0
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 11.1
MMRotate: 0.3.4+HEAD
2024-12-10 23:09:04,784 - mmrotate - INFO - Distributed training: True
2024-12-10 23:09:05,718 - mmrotate - INFO - Config:
dataset_type = 'DOTADataset'
data_root = '/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/'
img_norm_cfg = dict(
mean=[123.675, 116.28, 103.53], std=[58.395, 57.12, 57.375], to_rgb=True)
train_pipeline = [
dict(type='LoadImageFromFile'),
dict(type='LoadAnnotations', with_bbox=True),
dict(type='RResize', img_scale=(1024, 1024)),
dict(
type='RRandomFlip',
flip_ratio=[0.25, 0.25, 0.25],
direction=['horizontal', 'vertical', 'diagonal'],
version='le90'),
dict(
type='Normalize',
mean=[123.675, 116.28, 103.53],
std=[58.395, 57.12, 57.375],
to_rgb=True),
dict(type='Pad', size_divisor=32),
dict(type='DefaultFormatBundle'),
dict(type='Collect', keys=['img', 'gt_bboxes', 'gt_labels'])
]
test_pipeline = [
dict(type='LoadImageFromFile'),
dict(
type='MultiScaleFlipAug',
img_scale=(1024, 1024),
flip=False,
transforms=[
dict(type='RResize'),
dict(
type='Normalize',
mean=[123.675, 116.28, 103.53],
std=[58.395, 57.12, 57.375],
to_rgb=True),
dict(type='Pad', size_divisor=32),
dict(type='DefaultFormatBundle'),
dict(type='Collect', keys=['img'])
])
]
data = dict(
samples_per_gpu=2,
workers_per_gpu=2,
train=dict(
type='DOTADataset',
ann_file='/DATA/zhuzhenghua/PointOBBv2/work_dirs/pseudo_label',
img_prefix=
'/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/trainval/images/',
pipeline=[
dict(type='LoadImageFromFile'),
dict(type='LoadAnnotations', with_bbox=True),
dict(type='RResize', img_scale=(1024, 1024)),
dict(
type='RRandomFlip',
flip_ratio=[0.25, 0.25, 0.25],
direction=['horizontal', 'vertical', 'diagonal'],
version='le90'),
dict(
type='Normalize',
mean=[123.675, 116.28, 103.53],
std=[58.395, 57.12, 57.375],
to_rgb=True),
dict(type='Pad', size_divisor=32),
dict(type='DefaultFormatBundle'),
dict(type='Collect', keys=['img', 'gt_bboxes', 'gt_labels'])
],
version='le90',
classes=('plane', 'baseball-diamond', 'bridge', 'ground-track-field',
'small-vehicle', 'large-vehicle', 'ship', 'tennis-court',
'basketball-court', 'storage-tank', 'soccer-ball-field',
'roundabout', 'harbor', 'swimming-pool', 'helicopter')),
val=dict(
type='DOTADataset',
ann_file=
'/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/trainval/annfiles/',
img_prefix=
'/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/trainval/images/',
pipeline=[
dict(type='LoadImageFromFile'),
dict(
type='MultiScaleFlipAug',
img_scale=(1024, 1024),
flip=False,
transforms=[
dict(type='RResize'),
dict(
type='Normalize',
mean=[123.675, 116.28, 103.53],
std=[58.395, 57.12, 57.375],
to_rgb=True),
dict(type='Pad', size_divisor=32),
dict(type='DefaultFormatBundle'),
dict(type='Collect', keys=['img'])
])
],
version='le90',
classes=('plane', 'baseball-diamond', 'bridge', 'ground-track-field',
'small-vehicle', 'large-vehicle', 'ship', 'tennis-court',
'basketball-court', 'storage-tank', 'soccer-ball-field',
'roundabout', 'harbor', 'swimming-pool', 'helicopter')),
test=dict(
type='DOTADataset',
ann_file=
'/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/test/images/',
img_prefix=
'/DATA/zhuzhenghua/pointobb/PointOBB/Dataset/split_ss_dota/test/images/',
pipeline=[
dict(type='LoadImageFromFile'),
dict(
type='MultiScaleFlipAug',
img_scale=(1024, 1024),
flip=False,
transforms=[
dict(type='RResize'),
dict(
type='Normalize',
mean=[123.675, 116.28, 103.53],
std=[58.395, 57.12, 57.375],
to_rgb=True),
dict(type='Pad', size_divisor=32),
dict(type='DefaultFormatBundle'),
dict(type='Collect', keys=['img'])
])
],
version='le90',
classes=('plane', 'baseball-diamond', 'bridge', 'ground-track-field',
'small-vehicle', 'large-vehicle', 'ship', 'tennis-court',
'basketball-court', 'storage-tank', 'soccer-ball-field',
'roundabout', 'harbor', 'swimming-pool', 'helicopter'),
samples_per_gpu=4))
evaluation = dict(interval=1, metric='mAP')
optimizer = dict(type='SGD', lr=0.01, momentum=0.9, weight_decay=0.0001)
optimizer_config = dict(grad_clip=dict(max_norm=35, norm_type=2))
lr_config = dict(
policy='step',
warmup='linear',
warmup_iters=500,
warmup_ratio=0.3333333333333333,
step=[8, 11])
runner = dict(type='EpochBasedRunner', max_epochs=12)
checkpoint_config = dict(interval=1)
log_config = dict(interval=50, hooks=[dict(type='TextLoggerHook')])
dist_params = dict(backend='nccl')
log_level = 'INFO'
load_from = None
resume_from = None
workflow = [('train', 1)]
opencv_num_threads = 0
mp_start_method = 'fork'
angle_version = 'le90'
classes = ('plane', 'baseball-diamond', 'bridge', 'ground-track-field',
'small-vehicle', 'large-vehicle', 'ship', 'tennis-court',
'basketball-court', 'storage-tank', 'soccer-ball-field',
'roundabout', 'harbor', 'swimming-pool', 'helicopter')
model = dict(
type='ReDet',
backbone=dict(
type='ReResNet',
depth=50,
num_stages=4,
out_indices=(0, 1, 2, 3),
frozen_stages=1,
style='pytorch',
pretrained=
'/DATA/zhuzhenghua/PointOBBv2/model/re_resnet50_c8_batch256-25b16846.pth'
),
neck=dict(
type='ReFPN',
in_channels=[256, 512, 1024, 2048],
out_channels=256,
num_outs=5),
rpn_head=dict(
type='RotatedRPNHead',
in_channels=256,
feat_channels=256,
version='le90',
anchor_generator=dict(
type='AnchorGenerator',
scales=[8],
ratios=[0.5, 1.0, 2.0],
strides=[4, 8, 16, 32, 64]),
bbox_coder=dict(
type='DeltaXYWHBBoxCoder',
target_means=[0.0, 0.0, 0.0, 0.0],
target_stds=[1.0, 1.0, 1.0, 1.0]),
loss_cls=dict(
type='CrossEntropyLoss', use_sigmoid=True, loss_weight=1.0),
loss_bbox=dict(
type='SmoothL1Loss', beta=0.1111111111111111, loss_weight=1.0)),
roi_head=dict(
type='RoITransRoIHead',
version='le90',
num_stages=2,
stage_loss_weights=[1, 1],
bbox_roi_extractor=[
dict(
type='SingleRoIExtractor',
roi_layer=dict(
type='RoIAlign', output_size=7, sampling_ratio=0),
out_channels=256,
featmap_strides=[4, 8, 16, 32]),
dict(
type='RotatedSingleRoIExtractor',
roi_layer=dict(
type='RiRoIAlignRotated',
out_size=7,
num_samples=2,
num_orientations=8,
clockwise=True),
out_channels=256,
featmap_strides=[4, 8, 16, 32])
],
bbox_head=[
dict(
type='RotatedShared2FCBBoxHead',
in_channels=256,
fc_out_channels=1024,
roi_feat_size=7,
num_classes=15,
bbox_coder=dict(
type='DeltaXYWHAHBBoxCoder',
angle_range='le90',
norm_factor=2,
edge_swap=True,
target_means=[0.0, 0.0, 0.0, 0.0, 0.0],
target_stds=[0.1, 0.1, 0.2, 0.2, 1]),
reg_class_agnostic=True,
loss_cls=dict(
type='CrossEntropyLoss',
use_sigmoid=False,
loss_weight=1.0),
loss_bbox=dict(type='SmoothL1Loss', beta=1.0,
loss_weight=1.0)),
dict(
type='RotatedShared2FCBBoxHead',
in_channels=256,
fc_out_channels=1024,
roi_feat_size=7,
num_classes=15,
bbox_coder=dict(
type='DeltaXYWHAOBBoxCoder',
angle_range='le90',
norm_factor=None,
edge_swap=True,
proj_xy=True,
target_means=[0.0, 0.0, 0.0, 0.0, 0.0],
target_stds=[0.05, 0.05, 0.1, 0.1, 0.5]),
reg_class_agnostic=False,
loss_cls=dict(
type='CrossEntropyLoss',
use_sigmoid=False,
loss_weight=1.0),
loss_bbox=dict(type='SmoothL1Loss', beta=1.0, loss_weight=1.0))
]),
train_cfg=dict(
rpn=dict(
assigner=dict(
type='MaxIoUAssigner',
pos_iou_thr=0.7,
neg_iou_thr=0.3,
min_pos_iou=0.3,
match_low_quality=True,
ignore_iof_thr=-1),
sampler=dict(
type='RandomSampler',
num=256,
pos_fraction=0.5,
neg_pos_ub=-1,
add_gt_as_proposals=False),
allowed_border=0,
pos_weight=-1,
debug=False),
rpn_proposal=dict(
nms_pre=2000,
max_per_img=2000,
nms=dict(type='nms', iou_threshold=0.7),
min_bbox_size=0),
rcnn=[
dict(
assigner=dict(
type='MaxIoUAssigner',
pos_iou_thr=0.5,
neg_iou_thr=0.5,
min_pos_iou=0.5,
match_low_quality=False,
ignore_iof_thr=-1,
iou_calculator=dict(type='BboxOverlaps2D')),
sampler=dict(
type='RandomSampler',
num=512,
pos_fraction=0.25,
neg_pos_ub=-1,
add_gt_as_proposals=True),
pos_weight=-1,
debug=False),
dict(
assigner=dict(
type='MaxIoUAssigner',
pos_iou_thr=0.5,
neg_iou_thr=0.5,
min_pos_iou=0.5,
match_low_quality=False,
ignore_iof_thr=-1,
iou_calculator=dict(type='RBboxOverlaps2D')),
sampler=dict(
type='RRandomSampler',
num=512,
pos_fraction=0.25,
neg_pos_ub=-1,
add_gt_as_proposals=True),
pos_weight=-1,
debug=False)
]),
test_cfg=dict(
rpn=dict(
nms_pre=2000,
max_per_img=2000,
nms=dict(type='nms', iou_threshold=0.7),
min_bbox_size=0),
rcnn=dict(
nms_pre=2000,
min_bbox_size=0,
score_thr=0.05,
nms=dict(iou_thr=0.1),
max_per_img=2000)))
work_dir = './work_dirs/redet_dotav10'
auto_resume = False
gpu_ids = range(0, 2)
2024-12-10 23:09:05,718 - mmrotate - INFO - Set random seed to 0, deterministic: False
2024-12-10 23:09:28,736 - mmrotate - INFO - initialize ReResNet with init_cfg {'type': 'Pretrained', 'checkpoint': '/DATA/zhuzhenghua/PointOBBv2/model/re_resnet50_c8_batch256-25b16846.pth'}
2024-12-10 23:09:28,944 - mmrotate - INFO - initialize RotatedRPNHead with init_cfg {'type': 'Normal', 'layer': 'Conv2d', 'std': 0.01}
2024-12-10 23:09:28,949 - mmrotate - INFO - initialize RotatedShared2FCBBoxHead with init_cfg [{'type': 'Normal', 'std': 0.01, 'override': {'name': 'fc_cls'}}, {'type': 'Normal', 'std': 0.001, 'override': {'name': 'fc_reg'}}, {'type': 'Xavier', 'layer': 'Linear', 'override': [{'name': 'shared_fcs'}, {'name': 'cls_fcs'}, {'name': 'reg_fcs'}]}]
2024-12-10 23:09:29,151 - mmrotate - INFO - initialize RotatedShared2FCBBoxHead with init_cfg [{'type': 'Normal', 'std': 0.01, 'override': {'name': 'fc_cls'}}, {'type': 'Normal', 'std': 0.001, 'override': {'name': 'fc_reg'}}, {'type': 'Xavier', 'layer': 'Linear', 'override': [{'name': 'shared_fcs'}, {'name': 'cls_fcs'}, {'name': 'reg_fcs'}]}]
Name of parameter - Initialization information
祝好！

您好，感谢你对我们论文的关注。对于运行内存，mmrotate里面报告的内存，是 PyTorch 统计的张量显存占用量，实际显存占用更高。对于性能，需要提交到DOTA官网上测试，看到你的log中几种field不太理想，可以改一下阈值，然后把pca_length设置为28或36（实际对应于feature_map中的7和9）。


text:
[bug] v2 Event system: AnyLabel isn't handled correct

Describe the bug
The new event system, which primarily relies on targets to work, has some major flaws when it comes to handling these targets. Specifically targets of the kind AnyLabel, which is the default when just adding a string as target in both emitTo and listen.
For example, if a listener is set with the target "main", and emitTo("main", "eventName", "payload") is run, the listener will not be triggered.
I have tried to trace this behavior back to the source, and have stumbled upon this snippet from the implementation of the emit_to function in Rust.
// https://github.com/tauri-apps/tauri/blob/12ffc19ce08eeafdedc65207f312432aa2cf9c84/crates/tauri/src/manager/mod.rs#L590-L606
match target {
  // if targeting all, emit to all using emit without filter
  EventTarget::Any => self.emit(event, payload),

  // if targeting any label, emit using emit_filter and filter labels
  EventTarget::AnyLabel {
    label: target_label,
  } => self.emit_filter(event, payload, |t| match t {
    EventTarget::Window { label }
    | EventTarget::Webview { label }
    | EventTarget::WebviewWindow { label } => label == &target_label,
    _ => false,
  }),

  // otherwise match same target
  _ => self.emit_filter(event, payload, |t| t == &target),
}

Here, target is the target set in emit_to. When this is of the kind AnyLabel, the code will enter the second match, where it checks for t which is the listener target. It checks if t is of kind Window, Webview or WebviewWindow, none of which apply to AnyLabel by which it will return false when the listener is initialized without a specific kind.
If a kind has been specified for emit_to, it will go to the bottom line, and only match the same targets. Again, if the listener is initialized without a specific kind, and therefore gets the kind AnyLabel, it will not trigger the listener.
Reproduction
No response
Expected behavior
As far as I understand it, the expected behaviour would be to let AnyLabel serve as a "wildcard" for both emitTo and listen. So if any of the two are of the kind AnyLabel, any event with a label would be served between the two.
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 x86_64 (X64)
    ✔ WebView2: 130.0.2849.56
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.15.1
    - yarn: 4.5.1
    - npm: 10.7.0
    - deno: deno 2.0.4

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.5
    - @tauri-apps/api : 2.0.3
    - @tauri-apps/cli : 2.0.5

[-] Plugins
    - tauri-plugin-dialog 🦀: 2.0.3
    - @tauri-apps/plugin-dialog : 2.0.1
    - tauri-plugin-fs 🦀: 2.0.3
    - @tauri-apps/plugin-fs : 2.0.1
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-http 🦀: 2.0.3
    - @tauri-apps/plugin-http : 2.0.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:4321/
    - framework: Svelte
    - bundler: Rollup

Stack trace
No response
Additional context
I would be willing to work on a PR fixing this issue, but I would like to discuss the exact issue and expected behavior in depth before starting to change things in the event API.

@Mikkel-T thank you for the detailed bug and tracing, please feel free to open a PR.

I will definitely be doing so! But before I start, I would like to ensure that my implementation is going to align with the intended behaviour.
From my understanding, there are two main scenarios to consider:

Emitter emitting an event to an AnyLabel target
Listener listening to an AnyLabel target

There are currently four target kinds that support a label: Window, Webview, WebviewWindow and AnyLabel.
Expected behavior
For the first scenario, I expect that an event emitted to a target of kind AnyLabel should invoke listeners associated with any of the specified kinds. For example:
emitTo({kind: "AnyLabel", label: "main"}, "event", "payload");

// The following listeners should be invoked by this event:
listen("event", () => {}, {target: {kind: "Window", label: "main"}});
listen("event", () => {}, {target: {kind: "Webview", label: "main"}});
listen("event", () => {}, {target: {kind: "WebviewWindow", label: "main"}});
listen("event", () => {}, {target: {kind: "AnyLabel", label: "main"}});
listen("event", () => {}, {target: "main"}); // Default is AnyLabel

For the second scenario, I believe that a listener initialized with a target of kind AnyLabel should be invoked when receiving an event from any of the specified kinds:
listen("event", () => {}, {target: {kind: "AnyLabel", label: "main"}});

// The following events should invoke this listener:
emitTo({kind: "Window", label: "main"}, "event", "payload");
emitTo({kind: "Webview", label: "main"}, "event", "payload");
emitTo({kind: "WebviewWindow", label: "main"}, "event", "payload");
emitTo({kind: "AnyLabel", label: "main"}, "event", "payload");
emitTo("main", "event", "payload"); // Default is AnyLabel

Could you please confirm if my understanding is correct? I want to ensure that I’m on the right track before proceeding with a PR.

authors: Mikkel-T amrbashir

repo: tauri-apps/tauri