text:
Feed cannot be added in iOS app

Hello,
First of all thanks for the great work on the iOS app!
I am not able to add the feed https://ledrenche.ouest-france.fr/feed/ in the iOS app (version 6.0.2 Build 610 - iOS 15.0.2) whereas the feed is displayed correctly in my browser (Firefox with Want my RSS extension).
The error message is: The feed couldn't be found and can't be added..
Is it a known bug?
Thank you in advance!

What kind of account are you using to sync with?

None. I try to add the feed in a folder which is in the category "On my iPhone".

It will add the feed if you remove the trailing slash.

I'm sorry but it didn't work even without the trailing slash. (You meant ˋhttps://ledrenche.ouest-france.fr/feed` right?)

Yeah, but without the trailing space.

Very strange that it worked for you whereas it didn't for me.
The value I tried:

https://ledrenche.ouest-france.fr/feed (without trailing space)
https://ledrenche.ouest-france.fr/feed/

The same error is reported for each of them.

@vincode-io any idea what I could try to solve my problem?
Would reinstalling the app help?
Thanks in advance!

The only thing I can think of is that the server is redirecting you based on your locale or language settings. If you set your locale and language on your iPhone to US English are you able to add it then?
This is a real long shot, but I'm grasping at straws here. I've been able to add that feed multiple times without problem on the exact same version of NNW that you are using.

Thanks for the new suggestion but it didn't help to set region and language to US English...
Is there a way to turn on debug logs or something similar to get more information about the error?

Have you tried the new 6.1 Beta yet? Maybe it will help. Again, I am just grasping at straws here.
We don't have any way to capture that kind of info via logs at this time.

Thanks again to keep on trying to fix my problem!
I installed 6.1 beta but I was still not able to add the feed.
Then I deleted the app completely (with all its data), reinstalled the 6.1 beta but still no luck 🙁
I will try on other devices and I will post back here.
(By the way it was not easy to find the Test Flight link to install the beta: I used a link in an old blog post (from September). Maybe you should add the Test Flight link to subscribe to beta versions in the Readme of this repository as people checking the source code are usually also interested in installing beta versions 😉)

I tested on another iPhone running on iOS 15.0.1 with NetNewsWire 6.0.2 and I got the same error as on my phone. This iPhone is configured with French as language and France as region so maybe it is related to locale as you guessed since it works on your phone.
But it is very strange that it doesn't work with French locale as it is a French-only feed.

Language and region don't seem to be the problem. I changed them to French/France and was able to still subscribe to the feed.
You mentioned that you might be browsing the code. Are you a developer? If so, can you snoop the http requests using Proxyman, Charles, or some other kind of http monitor? That could tell us what we are getting back from the server. It might be blocking you based on IP or something.

@thombet Did you ever get a solution to your problem?

Nope. Just tried again with 6.1 build 6104 and there is still the problem on my phone.
I didn't take the time to try what you suggested in your last comment.

Are you still seeing this bug?

Yes.
I tried again with version 6.1.1 (build 6114) and iOS 15.4.1 and the same error appears.

Would you go into Terminal, copy-and-paste the following, then hit return…
curl -I https://ledrenche.ouest-france.fr/feed/
…then reply here with what it says?
(The above command gets the HTTP response header from the server for that feed.)

This is the response:
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 09 Mar 2023 23:18:45 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://ledrenche.fr/feed/

But how does it relate to the iOS app?

The redirect response is not surprising (and is fine). Let’s try it again with the new URL:
curl -I https://ledrenche.fr/feed/

It returns:
HTTP/1.1 403 Forbidden
Date: Fri, 10 Mar 2023 08:04:31 GMT
Content-Type: text/html; charset=iso-8859-1
X-Request-ID: 575963303
Cache-Control: no-cache
Vary: Accept-Encoding
X-CDN-Pop: rbx1
X-CDN-Pop-IP: 51.254.41.128/25
X-Cacheable: Cacheable
Connection: keep-alive

May I ask how the response on my machine may be different than the response on your machine?

When I try that on my Mac, I get:
date: Sat, 11 Mar 2023 04:30:49 GMT
content-type: text/html; charset=iso-8859-1
server: Apache

…but I can also add the feed to NetNewsWire on my Mac! And I can add it to NetNewsWire on iOS.
Here’s my theory: their server is looking at some combination of things — user agent, IP address (maybe determining location), and who knows what else — and is returning a 403 in some cases.
There’s nothing we can do about it — it’s a bug on their end, unfortunately. I wish I could help more!

authors: brentsimmons thombet vincode-io

repo: Ranchero-Software/NetNewsWire


text:
Add Mark Above as Read and Mark Below as Read to the Mac toolbar

These should be optional toolbar items.
This was suggested here: https://github.com/Ranchero-Software/NetNewsWire/issues/662#issuecomment-1257019298

Reopening because this needs additional verification.

source: gharchive/issue

authors: brentsimmons vincode-io

license: MIT

license_type: permissive

license_source: github-api


text:
Add Dock menu of unread items (like NNW had)

I love the hierarchical dock menu in NetNewsWire (so much so that I'm still using v3.x)
Please implement this in Evergreen.
Thanks.

Should selecting an article in the Dock menu open the article's URL (like NNW 3.x), or select the article in NNW?

My personal preference is URL - but perhaps left as an option (as in NNW 3.x)

"Open links in: NetNewsWire" still opens the URL (in-app insted of in-browser) vs. selecting the feed in the app, as far as I can tell. Since NNW 5 doesn't have an in-app browser yet, I'll just have it open in the default browser (which is easier than selecting the articles in the timeline, anyway).

I've got this mostly working, but popping the menu is kind of slow since it has to build the entire menu when it's popped up. I may look at building the menu before it's popped, asynchronously.
Using NSMenuDelegate + menuNeedsUpdate() was fruitless, as it seems that for the Dock menu, menuNeedsUpdate() is called for the submenus right away instead of just before they're opened.

We’re unlikely to do this — it’s a big performance hit when there are lots of unread items, which is a pretty typical thing for a lot of people.
We were able to do it in NetNewsWire of Yore because we kept all unread articles in memory all the time. We use memory better these days! But at the cost of making this feature do-able.

authors: Diggory Wevah brentsimmons


text:
Publish to npm

Hey, this looks interesting, do you plan to publish it to npmjs?

yes! It's been published. 😅 https://www.npmjs.com/package/hyper-gateway

authors: RangerMauve alessiostalla

repo: RangerMauve/hyper-gateway


text:
FPS on cpu i5 is not high

Hi @RangiLyu, thank you for your work.
I trained NanoDet-m on my own dataset with head and face labels, and exported to onnx successfully. But when I did benchmark onnx model on my computer Mac pro cpu core i5, the model got only 32 fps. I used code in demo_ncnn/python/demo_ncnn.py
I wondered it was not high and it will got higher if I convert onnx to mnn model, right?
Because your model had small enough size, so I thought that your model could get higher fps than 32.

To get better performance on Intel CPU, please use openvino.

@RangiLyu How many fps you could get when running MNN on arm chipset of NanoDet-m model?

Hi @RangiLyu, I ran MNN model on my arm device having 6 threads and got only 9 fps instead of 97 in your README.md. I used your demo_mnn code to compute fps. Had I was wrong in which step?

兄弟,请将语言由python改为c++,在测试推理速度

@superbayes Thanks for your suggestion.
Which device did you test speed using cpp script? And how many fps did you get? Thank you.

@superbayes Thanks for your suggestion. Which device did you test speed using cpp script on? And how many fps did you get? Thank you.

97fps is benchmarked on Arm A76 4 threads with ncnn fp16 inference.

authors: RangiLyu awl-anht-nguyen superbayes

repo: RangiLyu/nanodet


text:
Why the example looping is not incrementing values in background

Hi I set up the app as instructed and the background service seems working when opening the app

const veryIntensiveTask = async (taskDataArguments) => {
console.log(taskDataArguments)
const { delay } = taskDataArguments
await new Promise(async (resolve) => {
for (let i = 0; BackgroundService.isRunning(); i++) {
console.log(i)
await BackgroundService.updateNotification({
taskDesc: Adding steps... + i,
})
await sleep(delay)
}
})
}

but when i closed the app the console update just stop so as the BackgroundService.updateNotification
shouldn't this defeats the whole purpose of background action?
it should be looping infinitely but the notification stops refreshing after the app went background.
what is happening?

I am running the app on Android 12. Is this the cause for the inactivity?

Oh I found out that the MIUI will kill the background task aggressively.
I tried using the solution here but to no avail: https://dontkillmyapp.com/xiaomi
If someone uses Xiaomi phone with MIUI, please tell me if you have solve the problem.


text:
Update nlu.md

Added a few variations for all intents.

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

Thanks for submitting a pull request 🚀 @TyDunn will take a look at it as soon as possible ✨

source: gharchive/pull-request

authors: CLAassistant sara-tagger vish0701

repo: RasaHQ/NLU-training-data


text:
WIP - 3.0 remove user warnings

Proposed changes:
Closes #9777
Removes and/or updates UserWarnings pertaining to 3.0 changes.
Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

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

Thanks @alwx I saw the comment but was waiting for @samsucik to advise.

authors: CLAassistant carlad

repo: RasaHQ/rasa


text:
Does rasa use any word embeddings internally ?

Does rasa use any word embeddings internally ( like word2vec or glove ) ?

Rasa uses either spaCy or MITIE as a backend for much of the NLP tasks. Both of which use word embeddings. You'll find better answer to how each of those two tools work in their own documentation.

authors: vivekaditya wrathagom


text:
Overlay shows games played from other users

For multiple users on the same computer, the overlay shows games played by other accounts for common decks.
For example, one account shows 0 | 41 for a deck that is invalid on that account.  Seemingly because 44 games were played with that deck on another account.

41 is global % winrate of the deck taken from out database.

authors: Razviar jimthev

repo: Razviar/mtga-pro-tracker


text:
Running binwalk with Cygwin

Could you improve the README to properly run binwalk with Cygwin, which pacakges are required and such?

Seconded

Would also appreciate this

repo: ReFirmLabs/binwalk


text:
Feature request: native guard

It's been enough time for work arounds. We need react router to add natively guards (auth support). It can be a simple boolean check.
How it would work
The router could support a prop of type boolean that shows if the user is logged:
<Router logged={true}>

Now the only thing we need to do, is to inside of a route, check for it:
<Route guard="guest">

Having to default types: guest and logged. If the user is logged and the route requires guest, it won't pass, and vice-versa for logged. Of course there should be the check inside of the Switch component.
Conclusion
This is really simple and has space for expansion. I'm tired of writing custom Switchs and Routes to make this work, when it should be native from the start. And by the way, I still think that routes should support a when parameter to make a simple boolean check (that would be run in switch components also).

There are ideas to add a validate prop to the <Route /> component. This would go well with your proposal, but is more general in its use cases.

@MeiKatz, I really wouldn't like to mix those, because auth is such a common feature, and seeing they are giving what we brazilians call "gambiarra" (let's say it's a horrible way of fixing things) in their documentation for it, gives me an horrible feeling.

@darklight9811 I don't think that this kind of feature is in the scope of RR. But you could implement it on your own if there were something like the validate prop, that enables you to use conditional skipping of routes.

I came up with an idea that scalates better. It's a kind of a middleware.
How it would work
First you place the guard available to the router:
<Router guards={{guest, logged, validateSomething}}>
    {...}
</Router>

Those variables would be functions that would run some logic when required, let's show for example the validateSomething:
function validateSomething (data, _arguments) {
    return data.path == _arguments[0];
}

The first argument is data, that would be entire router encapsulated into an object, so you would be able to access current path, type, location stuff. The second is a set of arguments that you can set when calling it, now let's see how you can do so:
<Route {...} guards={"validateSomething:home"} />

This is pretty much like laravel, the guards prop could accept an array of strings or a simple string. We could encapsulate the router components inside guards, to enable a full customization on it's behaviour.

We're not going to do this. Mainly because while it makes sense for the simple case (I do or do not have access to this individual Route), it breaks down as an abstraction over many routes or many levels of auth (or both!).
You would have to add the validation prop to each route individually. This is both cumbersome and error prone. It creates a ton of boilerplate for any decently-sized application.
The easier thing is to just move the check up above your Switch and provide two sets of routes for authed or unauthed users. Something like !!user ? <SwitchWithAuthRoutes> : <SwitchWithPublicRoutes>. If you need to reuse routes, just use common arrays and combine them together in whatever structure you need.
Again, this is attacking the problem from the wrong angle. It's more scalable to not build this into React Router as an API, but to structure your app agnostically to the routing layer.

authors: MeiKatz darklight9811 timdorr

repo: ReactTraining/react-router

license: mit

license_source: bigquery


text:
Best practices in dealing with EventEmitters that have many events

Is the right/standard thing to do to create many Observables?
How about for emitting - a series of Subscribers?

Is the decision between a single event bus observable for all types vs an
observable for each event type?

Is the decision between a single event bus observable for all types vs an observable for each event type?

How would you structure the single event bus observable? Top level object with the event name?

This may be more a question for stack overflow but I'll give my opinion.
Keeping in mind I am not a contribute.
Having worked with signals for many years, and implementing reactivity with
them, I can say you don't want a unified bus.
Object orientate each event type with its own observable. With an object
for each event type you can see at a glance what code depends on what
events.
But i guess this assumes dependency injection such as in angular (or
robotlegs back in the day).
If you have crosscutting concerns you will want these observables to be
part of a multiton, or otherwise factoried from some common point, so that
you are aware of all instances. In short crosscutting is still not an
argument for an event bus as such.

Closing this issue as stale.

authors: bholloway blesh rgbkrk

repo: ReactiveX/rxjs


text:
ConnectableObservable & publish typings are wrong

Bug Report
Current Behavior
Typings for connectableObservable when using publish are wrong
Reproduction

REPL or Repo link:
https://stackblitz.com/edit/rxjs-nsj1hs?file=index.ts

import { of, ConnectableObservable,timer } from 'rxjs';
import { map, publish } from 'rxjs/operators';

const stall$: ConnectableObservable<number> = timer(100).pipe(publish());
stall$.connect();

There is a TS error on declaration of stall$
Expected behavior
Should infer the type w/o annotating. If I do chose to annotate, no type error should occur.

I think it's a duplicate of #2972

Closing as dupe as commented.

Closing as dupe as commented.

authors: joshribakoff kwonoj voliva


text:
update Observable.md

subscriber -> observer

There are no subscribers in Glossary.


text:
add unit tests for models/featureFlag

New Test Coverage

We are using fetching and storing by username and not by userId, which will cause problem in future if username changes.

This endpoint is getting deprecated. New endpoint :

https://github.com/Real-Dev-Squad/website-backend/issues/563

repo: Real-Dev-Squad/website-backend


text:
ReDoc broken with the latest release 1.18.0

Our doc was broken when the latest release was tagged. Here are the 2 errors we had:

Error: Uncaught (in promise): TypeError: invalid 'in' operand
11:58:49,339 ERROR Error: Uncaught (in promise): TypeError: invalid 'in' operand this.componentSchema.info.contact
i</t.prototype.init@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:371290
o</e.prototype.preinit@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:219624
i</t.prototype.ngOnInit@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:371499
xn@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:28269
pr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:43066
ur@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42599
Lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:48730
i/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:1011482
updateDirectives@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:46663
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42282
wr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:45122
_r@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:44785
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42307
Hs</e.prototype.detectChanges@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:117565
c</t.prototype.load/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:399047
u</t.prototype.__tryOrUnsub@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301987
u</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301262
l</t.prototype._next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:300304
l</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:299987
p</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:303156
a</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:315648
f</e.prototype.load/</<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:211323
c</e.prototype.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549712
onInvoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10507
c</e.prototype.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549639
l</r.prototype.run@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:544864
c/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:554636
c</e.prototype.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550387
onInvokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10419
c</e.prototype.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550300
l</r.prototype.runTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:545555
o@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:542627
p</t.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551561
t/this.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551407
n@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:535386

Trace de la pile :
l@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:554097
c/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:554669
c</e.prototype.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550387
onInvokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10419
c</e.prototype.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550300
l</r.prototype.runTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:545555
o@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:542627
p</t.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551561
t/this.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551407
n@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:535386
 1 redoc.min.js:7:5735
	_ https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:5735
	wi</e.prototype.handleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:64234
	i</t.prototype.handleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:498094
	next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:83803
	fa</t.prototype.subscribe/o< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78325
	u</t.prototype.__tryOrUnsub https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301987
	u</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301262
	l</t.prototype._next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:300304
	l</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:299987
	p</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:303156
	fa</t.prototype.emit https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78084
	onHandleError/< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10817
	c</e.prototype.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549712
	l</r.prototype.run https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:544864
	ha</e.prototype.runOutsideAngular https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:79949
	onHandleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10779
	c</e.prototype.handleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549792
	l</r.prototype.runGuarded https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:545119
	n.microtaskDrainDone/< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:555402
	n.microtaskDrainDone https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:555371
	o https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:542728
	p</t.invokeTask https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551561
	t/this.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551407
	n https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:535386

TypeError: n.componentSchema is null
c/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:1055376
updateDirectives@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:46663
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42282
wr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:45122
br@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:44520
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42417
wr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:45122
_r@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:44785
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42307
wr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:45122
br@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:44520
lr@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:42417
Hs</e.prototype.detectChanges@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:117565
Pa</t.prototype.tick/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:87719
Pa</t.prototype.tick@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:87680
next/<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:85580
c</e.prototype.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549712
onInvoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10507
c</e.prototype.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549639
l</r.prototype.run@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:544864
ha</e.prototype.run@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:79811
next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:85557
fa</t.prototype.subscribe/o<@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78325
u</t.prototype.__tryOrUnsub@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301987
u</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301262
l</t.prototype._next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:300304
l</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:299987
p</t.prototype.next@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:303156
fa</t.prototype.emit@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78084
oe@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10115
onHasTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10652
c</e.prototype.hasTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550706
c</e.prototype._updateTaskCount@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551065
l</r.prototype._updateTaskCount@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:547147
l</r.prototype.runTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:545767
o@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:542627
p</t.invokeTask@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551561
t/this.invoke@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551407
n@https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:535386
 1 redoc.min.js:7:5735
	_ https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:5735
	wi</e.prototype.handleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:64234
	i</t.prototype.handleError https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:498094
	Pa</t.prototype.tick/< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:87882
	c</e.prototype.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549712
	l</r.prototype.run https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:544864
	ha</e.prototype.runOutsideAngular https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:79949
	Pa</t.prototype.tick https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:87835
	next/< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:85580
	c</e.prototype.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549712
	onInvoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10507
	c</e.prototype.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:549639
	l</r.prototype.run https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:544864
	ha</e.prototype.run https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:79811
	next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:85557
	fa</t.prototype.subscribe/o< https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78325
	u</t.prototype.__tryOrUnsub https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301987
	u</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:301262
	l</t.prototype._next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:300304
	l</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:299987
	p</t.prototype.next https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:303156
	fa</t.prototype.emit https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:78084
	oe https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10115
	onHasTask https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:10652
	c</e.prototype.hasTask https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:550706
	c</e.prototype._updateTaskCount https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551065
	l</r.prototype._updateTaskCount https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:547147
	l</r.prototype.runTask https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:545767
	o https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:542627
	p</t.invokeTask https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551561
	t/this.invoke https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:551407
	n https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js:7:535386

We reverted back to 1.17.0 and ReDoc works again.

Could you link to your swagger?

We are experiencing the same issue - https://trackmatic.github.io/trackmatic-documentation/rest/loads/drivers/open-api

Fixed, new version 1.18.1 will be available on CDN in 20-30 min
I will notify you

Thanks!

@mnapoli @RossJayJones @luxifer
new version 1.18.1 (latest) is available on CDN.
Sorry for the inconvenience and thank you for the prompt bug report!

authors: RomanGotsiy RossJayJones mnapoli

repo: Rebilly/ReDoc


text:
Update volunteer URL on homepage and about page

This updates the "Submit Information" Link on the bottom of the homepage and in the bottom card on the about page. The link is set to http://join.rebuildblackbusiness.com/ which currently redirects to discord but will soon be pointed to a new form.
Pages/Interfaces that will change

Home page
About page

 Volunteer "Submit Information" link is not working

repo: Rebuild-Black-Business/RBB-Website


text:
Updates to Design/code status page

Updates to Design/code status page to reflect current state of design system and PFE

Tugboat has finished building the preview for this pull request!
Link:

https://pr157-np6xsq4zfuxvoz9pjavqcgk0imw7wpbm.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60d9ed3b57072d302de576d0

authors: coreyvickery wesruv

repo: RedHat-UX/red-hat-design-system-site


text:
docs: alert page cleanup

What I did
Updated Alert docs
Testing Instructions
View Alert page in deploy preview
Notes to Reviewers
Closes #903

@coreyvickery, there are still some things that need to be updated site-wide (like fixing the alert styling and changing the "Foundations" to "Related elements or patterns"), but I wanted to get your feedback on the other docs updates.

Things that need to be completed in Spinner docs:

[ ] Replace Foundations section with Related Components section
[ ] Add accessibility info

repo: RedHat-UX/red-hat-design-system


text:
add swaggo and prereqs for generating openapi spec file

Description
Adds the swaggo package and updates the Makefile and Dockerfile with new commands.
Includes /api/README.md for overview information.
Adds an api model file with description
FIXES: THEEDGE-3343
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[x] Refactor

/retest

/retest

Repository migration is failing, but not necessary a every start.

authors: acosferreira loadtheaccumulator

repo: RedHatInsights/edge-api


text:
Update wait_for_dv_success to work without DV Garbage Collection enabled

Short description:
DataVolume Garbage Collection featureGate is no longer a default, so we can update the function to work without the DV Garbage Collection.
Which issue(s) this PR fixes:
If DV got created after the check if sample is None - we are not waiting for DV success, and only waiting for PVC to be Bound, but this is not correct behavior.

Report bugs in Issues
The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR. (Closed when PR is merged/closed)
Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
verified label removed on each new commit push.
To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.

Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
Cherry-pick will be started when PR is merged

To build and push container image command /build-and-push-container in the PR (tag will be the PR number).
To add a label by comment use /<label name>, to remove, use /<label name> cancel
To assign reviewers based on OWNERS file use /assign-reviewers
To check if PR can be merged use /check-can-merge

Supported /retest check runs

/retest tox: Retest tox
/retest python-module-install: Retest python-module-install

Supported labels

hold
verified
wip
lgtm

/verified

/hold
/cancel verified

Label cancel is not a predefined one, will not be added / removed.
Available labels:

hold
verified
wip
lgtm

/verified

is this still on hold?

/hold cancel

/cherry-pick v4.15

Cherry-picked PR Update wait_for_dv_success to work without DV Garbage Collection enabled into v4.15

repo: RedHatQE/openshift-python-wrapper


text:
Better error messages

I've been having some fun playing with cooltt. An annoyance I had is the opaque error message on parse error. So I added the next token to the LexingUtil. Because the span is used in the Grammar I needed to change the call to pp_span to take in a product type.
More controversially, if the output of cooltt is going to be used by another program, the INFO line numbers are a bit of a problem so I suppressed them in pp_message.
My OCaml is meh so happy to adjust this pull request to however you'd prefer it.

More controversially, if the output of cooltt is going to be used by another program, the INFO line numbers are a bit of a problem so I suppressed them in pp_message.

I want to learn more about the use cases. It is indeed in the plan to have (separate) scriptable interactive interfaces. Could you elaborate the usage in your mind? Thanks! (And thanks for your contribution.)

More controversially, if the output of cooltt is going to be used by another program, the INFO line numbers are a bit of a problem so I suppressed them in pp_message.

I want to learn more about the use cases. It is in the plan to have (separate) scriptable interactive interfaces. Could you elaborate the usage in your mind? Thanks! (And thanks for your contribution.)

Eventually, if this gets beyond the airy lands of research, someone will want to take values it outputs and use them in the real world. It kind of reminds me of the early days of Haskell before Monads where all you could do is output a string to do IO. =)
Another way of doing this that doesn't alter your current toolset is to provide a command line argument that changes how the pretty printer works if you want "cpu consumable output".

Eventually, if this gets beyond the airy lands of research, someone will want to take values it outputs and use them in the real world. It kind of reminds me of the early days of Haskell before Monads where all you could do is output a string to do IO. =)
Another way of doing this that doesn't alter your current toolset is to provide a command line argument that changes how the pretty printer works if you want "cpu consumable output".

Yes, this is exactly what I had in my mind. I haven't thought through it very carefully, though. Apparently, we need to write some code to un-elaborate core terms back to surface syntax. Assuming there's no problem there, I wonder if you have a design you like in your mind? (e.g., a tool that outputs exactly what you want.) I believe it's not difficult to add a new output mode.

I will re-review this hopefully today, thank you again for your contribution! We are very excited to see some outside interest, and would be happy to discuss ways to further involve you in the project if you have interest.

Give me a second. I better understand the difference between load_file and the REPL now and I'll have a patch shortly that makes this better.

I like this better as it starts to abstract the difference between the an error and output. However don't review just yet as I found an edge case...

I like this better as it starts the process of abstracting Error Messaging from Eval messaging. The test suite runs and my testing of various errors works.
The errors currently look like...
my-test/errortest.cooltt:37.4-37.5 [Error]:
  [Error near normalize] Parse error

@favonia I haven't thought super deeply about it either. But my intuition says that if we provide a system for taking in strings and outputting strings made for machine use, we'll get the benefits of Unix style integrations out of the gate and that could lead to some surprising things.
For me, I just want a language where a + b can be known to equal b + a but in a "turtles all the way down" way. I see the same world where someone comes up with a cool proof of some property of a structure that my program is using, I add it and my program is "magically" more expressive as you all see so I'm happy to chip in some to push that along. =)

Agree with your comments... this latest is further along the way by maintaining one DriverMessage class, splitting the load errors from runtime errors, and taking Driver Messaging in pp_message out of the Driver file and putting it into the DriverMessaging module.
There is always more to do but this seems a lot further towards "better". Happy for feedback!

So, this is looking a lot better! There are still some aspects that I am finding confusing at the moment; the part I'm still getting stuck on is there is a type called error that contains non-error things (by virtue of containing DriverMessage.message), and consequently, the function pp_error_message is therefore also seeming to be printing non-error things. Maybe the right question for me to ask is: perhaps the errors (like ParseError etc.) should not be part of DriverMessage.message and some types should be peeled apart?
I am also finding the distribution of the spans and the last-tokens to be a little confusing; there is some semi-subtle layering going on in the architecture and I could use a high-level gloss of the motivations.
Thanks again!

I definitely see where you are going with your comment and I agree. I'll move around some things and try to get closer to cleanly separating messaging from error reporting.
I've taken a look at how Haskell does it and instead of having a LexingUtil class, they have an Outputable class that is used by an Error and the main GHC class. That is obviously better but I won't get to that level of sophistication in this PR. Let me propose something incrementally better as I walk towards that goal.

authors: EntropyFails favonia jonsterling

repo: RedPRL/cooltt


text:
Scan for android

Java.Lang.IllegalStateException: 'Unexpected rotation value -1'
Quits unexpectedly as soon as it runs, but I don't do anything
Can it select a photo and Automatic Identification?

any idea here? I hot the same issue.

authors: TingtingAn xlawswants


text:
Fix bug in Omics Integrator 1 TMPDIR

Closes #60
This bug was introduced in #49.  Previously volumes were mapped such that /OmicsIntegrator1 inside the container corresponded to the root of the spras repository on the local filesystem, which made it a suitable temporary directory for Omics Integrator 1.  That is no longer the case.
Now the temporary directory is set to the output directory for this Omics Integrator 1 run.  I was able to reproduce #60, and this change fixed it for me.

Confirming that this fixes https://github.com/Reed-CompBio/spras/issues/60

Thanks for the bug report and testing @sverchkov

authors: agitter sverchkov

repo: Reed-CompBio/spras


text:
Add NuGet README.md

https://docs.microsoft.com/en-us/nuget/reference/msbuild-targets#packagereadmefile

Correct yes, I should have linked that issue.

FYI, it looks like .NET 6 RC2 will have the fix for the blocking issue: https://github.com/NuGet/Home/issues/10791#issuecomment-926218883

authors: RehanSaeed Turnerj


text:
Update README.md

Made the readme's instructions more concise, and improved its wording and grammar. :sparkles: :cat2:

Thank you!

authors: IslaTheCutie Reimnop

repo: Reimnop/Catalyst


text:
Crash with Fasterrandom and AntiqueAtlas (Mixin conflict?)

Describe the bug
A startup crash happens when VMP, Fasterrandom (version >=2.0.0) and Antique atlas 4 (any version) are installed.
To Reproduce
This also happens when Sounds is installed. I'll report it to them as well.
It doesn't happen when VMP/Sounds isn't installed. By themselves, Fasterrandom and antiqueatlas work fine.
Steps to reproduce the behavior:

Have the three mods installed (Fasterrandom, Antiqueatlas, and VMP/Sounds)
Crash

Expected behavior
No crash.
Screenshots
I don't have any to show.
Runtime info (please complete the following information):

OS: Windows 11
Minecraft version: 1.20.1
Mod version: 0.2.0+beta.7.102

Crash reports / logs
https://pastebin.pl/view/c67be32e
Other mods
Checklist

[x] I am using the official version of the mod.
[x] I tried the latest development version but the issue persists.
[x] I searched for similar open issues and could not find an existing bug report on this.

Additional context
This issue is weird. Also I'm not a dev, I have no idea what I'm talking about. I just know there's a mixin conflict lol

Closed as it's not actually a VMP problem, just a my-machine problem.

repo: RelativityMC/VMP-fabric


text:
Rename IOPort to IoPort

To match the standards we are currently following (and the Rust standards). VgaWriter is an example of where we are already doing this.

Irrelevant now that the new Port io was merged.

repo: Restioson/flower


text:
feat: refactor to use Guzzle

Obviously this doesn't have to be used, but I thought I'd create a quick example of what this package could look like using Guzzle. 👍🏻
And here's a test script you can use:
<?php

declare(strict_types=1);

use RetroAchievements\Api\RetroAchievements;

require __DIR__ . '/vendor/autoload.php';

$username = getenv('RA_API_USERNAME');
$token = getenv('RA_API_TOKEN');

$client = new RetroAchievements($username, $token);

dump($client->getGameInfo(23796));

I'd also be happy to implement PHPStan and Pint for static analysis and code style formatting (or some tests). 👍🏻

Another possibility would be to create classes representing each resource, and then we would be able to map the values into these.
This would be similar to how the JS package uses it's model interfaces.

Hi @owenvoke!
I believe @luchaos may be otherwise engaged at the moment.
My perception is all of our API packages are intended to be reference wrappers around RAWeb's endpoints, similar to api-js. I'm sure you've already looked through api-js's source code, but if not it can be found here: https://github.com/RetroAchievements/api-js

Hi @wescopeland, thanks for the details. I modelled this off of the API (and looked into the JS package previously). The changes in this PR should cover the expectations. 👍🏻
I've got no issues with waiting for feedback, I was more adding that comment as a note for myself. 👍🏻

authors: owenvoke wescopeland

repo: RetroAchievements/api-php


text:
Using SimulateLatency/SimulatePacketLoss

This is a help/support question.
Hi there! I'm having a great time learning about networking with this library. Thank you!
I'm trying to use SimulateLatency and SimulatePacketLoss but I'm not noticing any change in behaviour when those are turned on. The docs say they only work in DEBUG mode, but I'm not sure what that means. Adding #define DEBUG to my own project doesn't seem to help. Is DEBUG mode a LiteNetLib compile-time flag? Do I need to compile the dll myself instead of using the nuget version?
Sorry if this is a basic C# question; I'm still learning. :)
Library version: 1.2.0 via nuget
Framework: MonoGame
OS: Windows

Yeah it does seem like these only features only work when compiling LiteNetLib itself as Debug. This seems unnecessary IMO and I personally think this functionality has no reason not to work in Release mode as well.

@JamDoggie it slowdowns library much, because there additional checks and lists that contains delayed packets. Use Clumsy to test release https://jagt.github.io/clumsy/

Fixed by https://github.com/RevenantX/LiteNetLib/pull/557

authors: JamDoggie RevenantX shouldice

repo: RevenantX/LiteNetLib


text:
feat: add support to missed dotnet versions (.net9, .net8, .net7)

Added support to missed dotnet versions (.net9, .net8, .net7)

.net9 is unsupported currently in AppVeyor.

Added manualy


text:
Rebase crash_dumper onto current Godot 4.3 master

This PR rebases the crash_dumper branch onto Godot's current master branch.
Note that I removed the mono re-hook as it seems to no longer be necessary.
I've only tested this on Windows, as that's the only platform I have available.

The merge conflicts appear to be expected as I chose to rebase rather than merging master.

I'm not sure how merging this should be done...
What did you need to do to rebase this work? I'm kind of guessing that it might be just more effective to redo this crash dumper feature on a clean branch from Godot master and just re-add fresh crash dumper library files and redo the hooking into the engine.

I remade the branch here. https://github.com/V-Sekai/godot/tree/vsk-crash-dumper-4.3-beta1

That remade branch looks fine to me based on a quick look. If there is a chance that this feature would finally make it into Godot soon I can probably make some time next week to do some stuff like:

determining if the signal handler overrides hack is still needed with the dotnet runtime
updating the breakpad version to latest commit as the previously extracted code is from 2021
testing that the crash dump generation (and decoding) still works

Here's my understanding.

Godot 4.3 is in beta and in feature freeze
I don't know when 4.4 merges, it could be 6 months 4.2 took or it could be the year that 4.3 took.

Since I want to have crash dumps today. I'll probably revive https://github.com/V-Sekai/godot-sentry-native and use sentry.io (a commercial service)

I don't mind redoing the work, or simply updating the breakpad integration - it looks relatively simple to do. Primarily, I wanted to update your PR into the Godot engine itself, instead of creating a new PR. It seems that redoing the branch would require me to do so. I'm a new contributor, so it's hard for me to gauge which is the best solution here.

A couple more notes:

testing that the crash dump generation (and decoding) still works

I tested this on windows and it works. I built Godot with debugging symbols and used OS.crash to force a crash, which generated a dump file in %appdata%. I was able to successfully extract a stack trace from the minidump using Visual Studio.

determining if the signal handler overrides hack is still needed with the dotnet runtime

The above was done with the dotnet module enabled, and I removed your re-init code in this branch, so I think it is no longer needed.

updating the breakpad version to latest commit as the previously extracted code is from 2021

I will try to get this done today.

If there is a chance that this feature would finally make it into Godot soon

To be honest, I have no idea what the chances of this are. I also find it quite demoralizing that critical features necessary for shipping a game like this are missing from the core engine. But I figured if I could add weight to and help out with the issue, perhaps there's a better chance.

I think what might work is that once you have your branch ready in your fork, I'll pull that to my local git repo and then force reset this repo's crash_dumper branch to match your branch, and then push that to github. I have a feeling that that would probably do the correct thing.

I've now updated the branch in my fork and tested that it's still functional at least on Windows: https://github.com/Chaosed0/godot-crash-dumper/tree/crash_dumper
Breakpad has been updated from Google's main branch. I removed all the test and HTTP upload files I could find. Here is a list of the new files, in case there are any that I missed that ought to still be removed:
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-amd.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-intel.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_file.cc
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_file.h
 create mode 100644 thirdparty/breakpad/src/client/linux/minidump_writer/pe_structs.h
 create mode 100644 thirdparty/breakpad/src/client/mac/UnitTests-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_test.xcodeproj/project.pbxproj
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests32-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests64-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/obj-cTestCases-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/solaris/handler/exception_handler_test.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/dwarf2reader_test_common.h
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.h
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_pipe.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_pipe.h
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_tmpfile.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/scoped_tmpfile.h
 create mode 100644 thirdparty/breakpad/src/common/linux/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/symbol_collector_client.h
 create mode 100644 thirdparty/breakpad/src/common/linux/synth_elf.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/synth_elf.h
 create mode 100644 thirdparty/breakpad/src/common/mac/SymbolCollectorClient.h
 create mode 100644 thirdparty/breakpad/src/common/mac/SymbolCollectorClient.m
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.cc
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.h
 create mode 100644 thirdparty/breakpad/src/common/safe_math.h
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.cc
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.h
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.h
 create mode 100644 thirdparty/breakpad/src/google_breakpad/common/minidump_cpu_riscv.h

I have a feeling that at least the following are data files that should not be included:
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-amd.sym
 create mode 100644 thirdparty/breakpad/src/client/linux/data/linux-gate-intel.sym

Also these might be data generation only files that may not be needed for a stripped down client library compilation:
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_test.xcodeproj/project.pbxproj
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests32-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/minidump_tests64-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/mac/handler/obj-cTestCases-Info.plist
 create mode 100644 thirdparty/breakpad/src/client/solaris/handler/exception_handler_test.cc
create mode 100644 thirdparty/breakpad/src/common/dwarf/dwarf2reader_test_common.h
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.cc
 create mode 100644 thirdparty/breakpad/src/common/dwarf/elf_reader.h
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/linux/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.cc
 create mode 100644 thirdparty/breakpad/src/common/mac/dump_syms.h
 create mode 100644 thirdparty/breakpad/src/common/safe_math.h
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.cc
 create mode 100644 thirdparty/breakpad/src/common/solaris/dump_symbols.h
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.cc
 create mode 100644 thirdparty/breakpad/src/common/test_assembler.h
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.cc
 create mode 100644 thirdparty/breakpad/src/common/windows/symbol_collector_client.h

Some of those might be necessary, but I think at least some of those source files are purely for the dumping side of things or just tests, meaning that they are unnecessary to include with the godot engine. Though to be sure each platform's files should be inspected to see if some other headers include those files to be removed to do a sanity check on not removing important files. I should be able to also pretty easily test on Linux to make sure there aren't missing files that prevent compilation.

Removed those files and re-tested, and things appear to still work.

I found a few problems compiling on Linux, but I fixed those. The PR to Godot should now be updated.

authors: Chaosed0 fire hhyyrylainen

repo: Revolutionary-Games/godot


text:
Comma in album name during import generates SyntaxError: None:1:15: Expected '{' or EOF

osxphotos version 0.68.1
When importing photos using osxphotos import having a comma in the name of the album into which to import will cause an error as shown in the command line/output below:
osxphotos import images/2014\ Vancouver,\ Summer/P1020237.JPG --album "2014 Vancouver, Summer" --check

Usage: osxphotos import [OPTIONS] [FILES_OR_DIRS]...
Try 'osxphotos import -h' for help.
Error: Invalid value for '--album' / '-a': SyntaxError: None:1:15: Expected '{' or EOF => ' Vancouver*, Summer'

If I remove the comma from the album name, then this command executes correctly as expected.

The album name is an OSXPhotos template and in the OSXPhotos template language, comma is a reserved symbol. To include a comma in the album name (or any other template), use {comma}.  For example, Vancouver{comma} Summer.

Thanks for the feedback. My bad for filing a bug - I did try looking through the docs before doing so... ;-)

No worries. The error message isn't very helpful. Unfortunately it is generated by the parser I use for the template system and I don't have much control over it. I'll look into adding a more descriptive suggestion when the parsing error is generated.

repo: RhetTbull/osxphotos


text:
How to keep the program running?

How do I keep the program running?
I am new to Golang especially Concurrency.
I use the code from one of the example. If I remove <-time.After(5 * time.Minute) the program does not even run.
Many thanks for your kind help.
`func main() {
//create new WhatsApp connection
wac, err := whatsapp.NewConn(5 * time.Second)
if err != nil {
fmt.Fprintf(os.Stderr, "error creating connection: %v\n", err)
return
}
//Add handler
wac.AddHandler(&waHandler{})

err = login(wac)
if err != nil {
	fmt.Fprintf(os.Stderr, "error logging in: %v\n", err)
	return
}

<-time.After(5 * time.Minute)

}`

// Your initializations like connections nad stuffs

forever := make(chan bool)
wac.AddHandler(&waHandler{})
<-forever

in go you can create a forever channel and if you wanted to close it you can use close(forever) inside the two tags ofcouse.

Thanks so much.
It works.

@SchulteMK isn't that a resource heavy since he's always adding a handler for a for loop if that's the case or worse always executing codes inside for loop while he only need is to block the program from exiting? since the package already have a loop function to receive messages in conn.go respectively keepAlive, writePump, readPump functions

repo: Rhymen/go-whatsapp


text:
Polygons displaying incorrectly on globe horison.

The problem is in geom.Dist3s.scala, def earthZPositive: GlobedArea. ". 3rd  case temporarily removed.

I commit to closing this by the end of 2019.

Closing this into #155.


text:
Prepare 0.4.0 release

Fixes #10

bors r+

repo: Richard-W/libfuse-sys


text:
Add a simple collector to generate flame graph data

The pull request adds a generic class to aggregate the data (under core.collector) and trivial wrapper that can be used from the command line (under ports, I'm not sure it's the best place).

Thanks for this pull request. In general looks great, but there's a couple of issues to fix. The help won't block a merge, but the missing licensing headers probably should do.

Added the licensing headers and the help message (sorry for forgetting that, it should have been obvious...)

Thanks - that's great.

authors: RichardWarburton mbarbon

repo: RichardWarburton/honest-profiler


text:
Resizable stops working if you load Jquery-UI 1.11.4

colResizable-1.6.min.js works fine until I load the jquery-ui 1.11.4
Should it be compatible?

Agreed - ran into this as well - even with the latest 1.12.1

Thanks David, that fix worked a treat. Hopefully Rick will consider making the change in the next version release.

I experienced this namespace collision problem as well. Would be good to permanently rename the 'resizable' function call, especially since some web apps load jQuery UI by default and it's not always easy to turn it off.

authors: brapion davidmcglynn gquach

repo: RickStrahl/jquery-resizable


text:
TypeScript generation with EnumStyle StringLiteral and defaults

I am generating TypeScript code for an API with a MyClass schema defined like this:
myProperty:
  type: "string"
  enum:
  - "ABC"
  - "DEF"
  - "GHI"
  default: "ABC"

I am generating with /enumStyle:StringLiteral.  This will correctly generate the type for myProperty which looks like this:
export type MyClassMyProperty = "ABC" | "DEF" | "GHI";

However, when the default is used within the init method of MyClass, it still tries to use enum syntax which gives an error:
this.myProperty= _data["myProperty"] !== undefined ? _data["myProperty"] : MyClassMyProperty.ABC;

I think this was just an oversight during the implementation of #1137 .  I am going to attempt to address this.

I am preparing a fix that overrides GetEnumDefaultValue in TypeScriptValueGenerator and changed the behavior if this is true:
typeResolver is TypeScriptTypeResolver tsr && tsr.Settings.EnumStyle == TypeScriptEnumStyle.StringLiteral

Hooray!  I can confirm that upgrading NSwag.MSBuild to the latest preview (14.0.0-preview008) fixes our TypeScript generation issue!

repo: RicoSuter/NJsonSchema


text:
nswag not generating proxy service in asp.net zero

I'm facing a problem wher i'm trying to create a proxyservice in asp.net zero. I'm running the refresh.bat file which starts nswag and in order should create a proxyservice.
The bat-file gets executed without any errors, but still won't generate the necessary proxyservice.
I don't understand why it wont generate anything and that there's no way for me to see whats happening.

I solved the issue, forgot to put class public

I am facing same issue..please let me know what you did

repo: RicoSuter/NSwag


text:
Align with new Microsoft.Extensions.ApiDescription.Client package

aspnet/AspNetCore#8487
NSwag.ApiDescription.Design -> NSwag.ApiDescription.Client

match newer Microsoft package and clear way for an NSwag.ApiDescription.Server package

@(CurrentServiceFileReference) -> @(CurrentOpenApiReference)
remove @(ServiceProjectReference) support; coming in NSwag.ApiDescription.Server package
use %(Options) metadata instead of %(GenerateNSwagCSharpOptions) and %(GenerateNSwagTypeScriptOptions)
use %(FirstForGenerator) metadata to avoid (some) compilation errors due to duplicate class definitions
use supported (LTS) runtime when executing dotnet-nswag.dll

@RicoSuter as discussed a few weeks ago…
I'll update this PR once the new package is available on NuGet. But, let's resolve any questions / issues up front.

@dougbu Looks good to me.

@RicoSuter this is ready to go. Preview 5 bits are now available on NuGet.org and I used the public version of the Microsoft.Extensions.ApiDescription.Client package while rebasing on your 'master' branch

v12.3.0

authors: RicoSuter dougbu


text:
RFC: Replace SoapClient with ext-soap-engine

Hello There,
Would you consider merging a PR which includes https://github.com/php-soap/ext-soap-engine as a replacement for using PHP's SoapClient directly?
Some context:
I am the author of phpro/soap-client.
We recently created the php-soap organisation, which contains an extraction of the low-level structure of our own soap-client package.
The packages inside the php-soap organisation can be used completely stand-alone and provide well-proven structures around PHP's SoapClient in order to make it as flexible as possible.
What's in it for this package:

It makes it possible to use laravel's HTTP client to deal with the SOAP requests. PHP's soap-client has many known issues around HTTP requests: broken on chuncked encoding, not possible to load wsdl's behind authentication, advanced authentication like NTLM and Bearer tokens ...

#38
#39
#34

By allowing an alternative HTTP layer, you can make it possible to deal with extensions like WSSE (which many soap services require).

#40

It provides validation for the SoapClient $options: If you mistype, you'll get sensible feedback
It provides abstractions for type converters and classmaps, so that you can change how soap encodes and decodes internally
It parses the __getFunctions() and __getTypes(), so that you can actually do something with that information.
It contains a SOAP abstraction (engine) so that in the long run, you might be possible to not depend on PHP's ext-soap implementation in the future. Benifits for that could be that the wsdl does not need to be loaded every time you want to do something with soap. (-> faster reponse times)
... much much more ...

I'm not a laravel expert, but looking at the code - it should not be to hard to include the basics.
At first sight, including the package would  especially affect these lines:
https://github.com/Ricorocks-Digital-Agency/Soap/blob/b0e5ef25515a36661d59e4df7c2cffd23edd6782/src/Request/SoapClientRequest.php#L80-L88
If you are willing to accept a PR, I am willing to try introducing the basics into this package.

Hi @veewee
That sounds really cool! Is it possible to conform to the request interface? If so, we could ship both and allow users to choose 👀

How would you make the request interface conform? Maybe I don't fully understand your question :)
My first idea was to keep this library completely like it is and use the ext-soap-engine to do the hard work internally instead of the SoapClient.
Meaning that the way that your users configure soap remains exactly like it is.
Since the options array is available during constructClient, we have all the information we'dd need to do this.

Hi @veewee
First of all, thank you for offering advice and help in this project across issues 💪
It's, let's say, been a while since this was first discussed.
Where do we stand right now for bringing in the engine as you said?
We aim to bring up to a new v2 soon, (dropping old dependencies, new tooling etc) and we could aim to go into v2, or v3.
Do you have the capacity to bring #36 up to date once these updates go into the main branch?

Hi @nedwors,
No problem 😄

Where do we stand right now for bringing in the engine as you said?

That's up to you. This issue and the demo provided in #36 is still very relevant.
I didn't go further than delivering the demo PR because there are many implementation details to be made in this package, as you can read in the comments inside that PR.

Do you have the capacity to bring https://github.com/Ricorocks-Digital-Agency/Soap/pull/36 up to date once these updates go into the main branch?

Currently a bit limited in time here. Getting the PR up to date might not be a problem.
But since it's a demo of what the possibilities are, it won't be fully mergeable afterwards either.
It might make more sense from the people maintaining this repository to figure out what the possibilities are and to decide how it will be implemented here. The PR contains a lot of comments with detailed information. I can imagine some of them are confusing or unkown - but I can always try to explain the things that are not clear to you or to point you in the right direction.
Would this be something that could work for you?

authors: lukeraymonddowning nedwors veewee

repo: Ricorocks-Digital-Agency/Soap


text:
[Feature Request] - Fast Channel opening with a new peer

The current flow of opening a channel with a new peer is:

Connect with a peer.
Open channel with the peer.

This flow can be shortened for better UX, by handling peer connection in the background.

Addressed in commit: https://github.com/Ride-The-Lightning/RTL-Design/commit/adc8f82c1073e99e18b175a7bb4e8bd0a6e5c1a5 with the following changes:
Open Channel:
Removed ability to add peer within the open channel flow to keep funcitionality segmented.
Add Peer:
Updated flow to a stepper. 1st Step: Add Peer / 2nd Step: Open Channel (Optional).

authors: diogorsergio saubyk

repo: Ride-The-Lightning/RTL-Design


text:
rg-map example showing how to use markers

The google maps object, rg.map.obj, is only available after initialize. Shouldn't there be another event that lets the parent tag know when they can use the rg.map.obj, because there is currently no way to add markers since the map object is not available after mounting. It still needs to wait for an initialize event

v3.1.0 should address your needs ;-)

authors: gregorypratt osiloke

repo: RiotGear/rg


text:
Feature request: Instagram "tagged" page support

When visiting https://www.instagram.com/username/tagged/, Instagram displays images that have that username tagged in them.
I'd like to request support for those pages in RipMe. At the moment, the "tagged" URL doesn't seem to be recognized as an "unable to find user" error is displayed when attempting to start a rip. #

Request for IGTV as well
https://github.com/RipMeApp/ripme/issues/38#issuecomment-453629195

This can be closed since it's already done.
https://www.instagram.com//tagged for user tags
https://www.instagram.com//channel for IGTV

authors: Isaaku domonic46 pinnie

repo: RipMeApp/ripme


text:
Update getting-started.md

Added a section into to docs to warn users about the Run In Background option in the Unity project settings that allows testing Riptide networking using the Unity Editor.
This is necessary because, UnityEditor will stop calling the FixedUpdate, if the Editor window is running in the background, when Run In Background option is disabled, and that stops the server and the client from communicating with each other.
In the previous versions of Unity Editor, this setting was enabled by default. But in the newer versions its disabled so its better to add it to the docs.

I decided to add this manually as I felt it made more sense to place it a little further down in the article, and your commit also adds a newline in one of the other tips which shouldn't be there.

authors: bkcetinkaya tom-weiland

repo: RiptideNetworking/Riptide


text:
[FEATURE REQ] Clear Options

i.e. everything or only irrelevant data

Implemented in 1.5 release.

repo: Rllyyy/Internet-Check


text:
Unserialising empty ImmutableRoaringBitmaps results in a RuntimeException

After adapting the example code for loading a ImmutableRoaringBitmap from a ByteBuffer to load two consecutive empty bitmaps results in the following exception:
Exception in thread "main" java.lang.RuntimeException: I failed to find one of the right cookies. 0
	at org.roaringbitmap.buffer.ImmutableRoaringArray.<init>(ImmutableRoaringArray.java:102)
	at org.roaringbitmap.buffer.ImmutableRoaringBitmap.<init>(ImmutableRoaringBitmap.java:406)
…

Code (in Scala):
object EmptyBitmapLoadingBug extends App {
  val rr1 = MutableRoaringBitmap.bitmapOf()
  val rr2 = MutableRoaringBitmap.bitmapOf()
  val bos = new ByteArrayOutputStream()
  val dos = new DataOutputStream(bos)
  rr1.serialize(dos)
  rr2.serialize(dos)
  dos.close()
  val bb = ByteBuffer.wrap(bos.toByteArray)
  val rrback1 = new ImmutableRoaringBitmap(bb)
  bb.position(bb.position() + rrback1.serializedSizeInBytes())
  val rrback2 = new ImmutableRoaringBitmap(bb)
}

The exception is thrown on loading the second bitmap.
I'm using RoaringBitmaps 0.5.9 on Java 1.8.0_65.

Verified.

Thanks for the bug report. Fixed in release 0.5.17. Please upgrade and verify.

Verified as fixed. Thank you, @lemire!

@maciej  Please keep the bug reports coming! ;-)

:+1: whenever I find any – I definitely will! However due to the quality of the project – I doubt there will be many coming. :-)

authors: lemire maciej

repo: RoaringBitmap/RoaringBitmap


text:
Redirect on connected instead of this.state.connected

This lets react router do the job of display once a connection is established.
ServerSelection is the IndexRoute and is intended to display a server selection screen. As is the case right now, this just shows boilerplate connecting text.
The next Route should be a React component that has the sidebar as well as the children routes. I'm imagining this one would pass the color on down (or make it part of the redux store).

I'll start this branch anew this evening.

repo: RobCoIndustries/pipboy


text:
Found another Python client/server.

https://github.com/Gavitron/pipulator/
@Gavitron

Sweet!

authors: luckydonald rgbkrk

repo: RobCoIndustries/pipboylib


text:
Test sketch

Do you happen to have a test sketch to try? Arduino Esp32

All examples should work on ESP32.
You just need to change the datapin in the examples.

Thanks, not going to lie I didn't look in there properly. I assume the dhtnew_test would be the best one to try?

What is the best is subjective.
If you take 20 minutes you can quickly go through all examples. Just read them and try to understand what happens.  You will note the similarities between the code. It might even be that one of the examples is very close to your needs/ideas.

If the issue is solved you may close it

repo: RobTillaart/DHTNew


text:
TypeError: type NoneType doesn't define round method

Hi,
I have the following issue with my flair integration for HASS. Can you please help?
Logger: homeassistant.components.automation.hvac_vent_control
Source: helpers/script.py:526
integration: Automation ([documentation](https://www.home-assistant.io/integrations/automation), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+automation%22))
First occurred: November 12, 2024 at 7:00:04 PM (1016 occurrences)
Last logged: 9:50:05 AM

HVAC Vent Control: Play Room: Error executing script. Unexpected error for call_service at pos 1: type NoneType doesn't define __round__ method
HVAC Vent Control: Error executing script. Unexpected error for if at pos 1: type NoneType doesn't define __round__ method
HVAC Vent Control: Play Bath Room: Error executing script. Unexpected error for call_service at pos 1: type NoneType doesn't define __round__ method
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 764, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
    return await long_task
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1032, in entity_service_call
    raise result from None
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1612, in async_request_call
    return await coro
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/flair/cover.py", line 175, in async_close_cover_tilt
    await self.coordinator.async_request_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 273, in async_request_refresh
    await self._debounced_refresh.async_call()
  File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 114, in async_call
    await task
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 358, in async_refresh
    await self._async_refresh(log_failures=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 481, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 176, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 561, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1007, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1132, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1069, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1013, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 544, in state
    value = self.native_value
            ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/flair/sensor.py", line 789, in native_value
    return round(self.vent_data.current_reading['duct-pressure'], 2)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: type NoneType doesn't define __round__ method

Please share your automation (the YAML) to determine if there is something in it that is causing it.

alias: HVAC Vent Control
description: ""
triggers:
  - entity_id:
      - input_boolean.hvac_elsa_room_cool_demand
      - input_boolean.hvac_playroom_cool_demand
      - input_boolean.hvac_living_room_cool_demand
      - input_boolean.hvac_martin_office_cool_demand
      - input_boolean.hvac_playroom_bath_cool_demand
      - input_boolean.hvac_elsa_bath_room_cool_demand
      - input_boolean.hvac_playroom_heat_demand
      - input_boolean.hvac_elsa_room_heat_demand
      - input_boolean.hvac_living_room_heat_demand
      - input_boolean.hvac_martin_office_heat_demand
      - input_boolean.hvac_playroom_bath_heat_demand
      - input_boolean.hvac_elsa_bath_room_heat_demand
    trigger: state
  - minutes: /5
    trigger: time_pattern
conditions: []
actions:
  - alias: Play Bath Room
    if:
      - condition: or
        conditions:
          - condition: state
            entity_id: input_boolean.hvac_playroom_bath_cool_demand
            state: "on"
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_playroom_bath_heat_demand
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id: cover.play_room_bath_aef0_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id: cover.play_room_bath_aef0_vent
  - alias: Play Room
    if:
      - condition: or
        conditions:
          - condition: state
            entity_id: input_boolean.hvac_playroom_cool_demand
            state: "on"
          - condition: state
            entity_id: input_boolean.hvac_playroom_heat_demand
            state: "on"
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id:
            - cover.play_room_cb44_vent
            - cover.play_room_080d_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id:
            - cover.play_room_cb44_vent
            - cover.play_room_080d_vent
  - alias: Elsa Room
    if:
      - condition: or
        conditions:
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_elsa_room_cool_demand
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_elsa_room_heat_demand
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id: cover.elsa_s_room_7515_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id:
            - cover.elsa_s_room_7515_vent
  - alias: Elsa Bath Room
    if:
      - condition: or
        conditions:
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_elsa_bath_room_cool_demand
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_elsa_bath_room_heat_demand
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id: cover.elsa_s_room_33b9_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id: cover.elsa_s_room_33b9_vent
    enabled: true
  - alias: Martin Office
    if:
      - condition: or
        conditions:
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_martin_office_cool_demand
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_martin_office_heat_demand
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id: cover.martin_s_office_380d_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id: cover.martin_s_office_380d_vent
  - alias: Living Room
    if:
      - condition: or
        conditions:
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_living_room_cool_demand
          - condition: state
            state: "on"
            entity_id: input_boolean.hvac_living_room_heat_demand
    then:
      - action: cover.open_cover_tilt
        data: {}
        target:
          entity_id:
            - cover.living_room_1c09_vent
            - cover.living_room_2811_vent
            - cover.living_room_3062_vent
            - cover.living_room_e27b_vent
    else:
      - action: cover.close_cover_tilt
        data: {}
        target:
          entity_id:
            - cover.living_room_e27b_vent
            - cover.living_room_3062_vent
            - cover.living_room_2811_vent
            - cover.living_room_1c09_vent
mode: queued

Go to the Flair integration (in the Home Assistant integrations page)

Click on "Enable debug logging"
Restart Home Assistant
Give it a minute once Home Assistant is back up and running and then navigate back to the Flair integration and disable debug logging.

A Log file should get downloaded - share that file here.

The vents causing the issue are offline and as a result the current-reading endpoint returns empty. For vents that are offline, you should see that I log a warning in the Home Assistant logs and the cover entity for vents that are offline will be unavailable in Home Assistant.
For example: Play Room Back shows
"inactive": true

What's happening is that your automation runs and when it calls for a vent to open or to close, if the vent is unavailable, the vent won't have been controlled and, when that service call is made, the API is polled and the current-reading endpoint is empty for offline vents.
The best way to handle this is to add a check in your automation to make sure, for the vent that is having a action executed on it, the cover entity is available - if it isn't available then you can have it do something else like sending yourself a notification.

Thank you. That makes sense. Do you know how exactly I can check if an entity is available? Or is there way to let the automation continue even if a servie call failes. Kind of like a IFERROR function?

I believe you can nest in another condition where you check the state of the vent that passed the initial condition. If the state is not unavailable then call the cover service. If it is unavailable then send yourself a notification. I use node red mainly, but I'm sure someone on the home assistant forums could assist you some more.


text:
Incompatible with 1.20.6

Hey, this doesn't really seem like the best place to put this since your code repo and CurseForge posting don't indicate 1.20.6 support, but I couldn't find a better way to contact you so I suppose an issue will do.
On Modrinth, it is listed as having support for 1.20.4, .5, and .6, however on 1.20.6, the following mixin fails:
mixins.reach-entity-attributes.json:InventoryValidationMixin -> net.minecraft.class_1263

Full crash report when running just this mod w/dependencies
This is from the reach-entity-attributes dependency that your mod uses, which has not yet been updated to 1.20.6
I'll also open an issue on their project and see if I have the time/patience to set up my modding workspace to submit a PR to port it to 1.20.6, but in the meantime, if you could remove the 1.20.6 support indicator on Modrinth, that'd be cool, thanks!

The mod isn't updated yet for those versions. I'm working on a 1.20.5 update at the moment. I incorrectly labeled it on Modrinth as compatible with those other versions, thank you for letting me know

repo: RobertHoueland/enchantments-plus


text:
Add Web REPL using Emscripten

As for code tester - we'd love to get this! I think the easiest path is to build Luau REPL using Emscripten to WASM and create an HTML wrapper around it. Pull requests with that functionality are welcome, feel free to create a separate feature request for that.

Originally posted by @zeux in https://github.com/Roblox/luau/issues/120#issuecomment-961045046
Create a demo page similar to Lua's on the doc site.
PR #138 closes this.

Oops this wasn't supposed to close. We now have a change that allows us to build Repl with Emscripten. I'm going to take a look at integrating this change into the build process, and figure out how to best integrate it with the web site.
The current top two contenders are:

Maybe it's feasible to fetch the GH release artifact, directly or using something like jsdelivr
Maybe we should make an npm package and just publish new versions of that package; unpkg can be used after that to source the file.

Sounds good! Let me know what the end decision is.

We've tested this lightly and it seems like it should be possible to just load the script from releases, e.g.
<script src="https://github.com/Roblox/luau/releases/download/<TAG>/luau.js"></script>

We could hardcode the tag to latest and make sure we move the tag with each release. Then we can simply upload build artifact with each release as we do with .zip archives for other artifacts.
This leaves the build setup. The only issue with the action that was in the earlier PR was the reliance on a third-party emsdk setup action. Is it possible to simply clone emsdk and run install & activate manually? (and maybe use GHA cache to speed this up, although maybe it's already pretty fast?)

Oh, I should say that I don't know OTOH if the setup above works with .wasm but Emscripten has an option to embed ,wasm into .js so I'm assuming we could use that, which would also make it easier for us as it's just a single file we need to upload with releases.

authors: MathematicalDessert zeux

repo: Roblox/luau


text:
setmetatable() doesn't accept typeof(setmetatable()) types, type error when setting a metatable to a new value

typeof(setmetatable()) doesn't work with setmetatable, with type error setmetatable should take a table
When creating a type with typeof(setmetatable()), using setmetatable on said type, seems to raise a type error: "setmetatable should take a table".
I've provided the source below.

--!strict

local App = {}
App.__index = App

type self = {
    test: string
}

export type App = typeof(setmetatable({} :: self, App))

function App.new(): App
    local self = setmetatable({} :: self, App)

    self.test = 'Hello, world!'

    return self
end

function App.Destroy(self: App): ()
    setmetatable(self, nil) -- TypeError: setmetatable should take a table
end

return App

I'd like to mention you can fix this with the following, however this causes other issues:
function App.Destroy(self: App & {}): ()
    setmetatable(self, nil)
end

Causing this type error:
TypeError: Type '{ @metatable App, self }' could not be converted into '{ @metatable App, self } & {|  |}'
caused by:
  Not all intersection parts are compatible. Type '{ @metatable App, self }' could not be converted into '{|  |}'

when running the following code:
local Interface = require(path.to.app.module).new()

Interface:Destroy()

typeof(setmetatable()) doesn't work with setmetatable, with type error setmetatable should take a table

When using setmetatable to extend a object's type, you'll have to use a table in both sides, while including their types.
Eg:
type ObjectAExtendsObjectB= setmetatable({}  :: typeof(ObjectA), {}  :: typeof(ObjectB)

authors: Nicklaus-s gitdesk-richard


text:
Question of why you did this feature | Optimization changes.

If you dont shut your no jawline having ass up i will come to your door and fuck your mom with davids cock

:joy: :trollface:

authors: latte-to zuwastaken


text:
Accessing push.Service concurrently?

The docs aren't entirely clear about the lifespan of a push.Service.  Is a new Service supposed to be created for each individual push notification (or batch of notifications), or is it intended to be long-lived and reused?  If the latter is true, is it safe to use across different threads?
Here's what I've got working right now:
package main

import "github.com/RobotsAndPencils/buford/push"
...

var service push.Service

// InitAPNS initializes the APNS service for global access.
func InitAPNS() {
    filename := "/path/to/certificate.p12"
    password := "certificate_password"
    cert, key, err := certificate.Load(filename, password)
    if err != nil {
        log.Fatal(err.Error())
    }
    client, err := push.NewClient(certificate.TLS(cert, key))
    if err != nil {
        log.Fatal(err.Error())
    }
    service = push.Service{
        Client: client,
        Host: push.Development}
}

func SendPushNotification(deviceTokens []string, notificationDetails...) {
    ...
    service.PushBytes(token, nil, bytes)
    ...
}

I initialize my global Service once from main(), and then reuse it each time I call SendPushNotification() - usually from different threads.  After 48 hours of running and maybe 50 total notifications, everything seems to be working ok.  But, I haven't been able to test it under a real load yet.
Am I going about this the right way?  Supposing that Service is meant to be long-lived, how can we catch connection errors?  And if it's instead meant to created and destroyed with each notification, what suggestions do you have to avoid reading the certificate from disk each time?  Thanks for the help.

Service is meant to be long lived. It should be safe to use across different goroutines. If there is an error, service.PushBytes will return the error.
Service is just a wrapper around an HTTP/2 Client using the Go standard library. The standard library provides a connection pool that will reuse a connection for multiple requests, but can also create new connections if there is an error. The standard library takes care of all the hard parts, so the service code is actually very simple.

Ok, that's the impression that I had while digging through the code but I wanted to be sure. If you have any suggested improvements to the code I've shown, please let me know. Thanks!

I think your code is fine. There should probably be some concurrent tests and documentation in Buford to address this concern.

@collinhundley I've written a concurrent example #54. Right now I'm considering changing Push to do things concurrently for you.

#54 documents concurrent use.

authors: collinhundley nathany

repo: RobotsAndPencils/buford


text:
document (common) errors and what to do

BadCertificateEnvironment #33 #76
unknown certificate #80

Thanks for the note. You can use certificate.TopicFromCert to extract the bundle identifier from the certificate itself.


text:
Could you provide your model weights？

Very nice project. Thank you! Could you provide your model weights? ^-^

Thank you! Good catch, I will upload my LoRA and decoder weights in the next commit. Also, I noticed a small mistake in the IoU computation if you're testing the code,
f_iou = IoU(
        task="multiclass",
        num_classes=config.n_classes,
        ignore_index=255,
        average="micro",
    ).cuda()

I forgot to specify average="micro" in the current commit. I will also fix this in the next commit.

I uploaded the weights and added a short explanation to the README.md :)

I uploaded the weights and added a short explanation to the README.md :)

Thanks! Look forward to your better output!

I added more pre-trained weights and corrected the IoU computation, how I used torchmetrics was incorrect. If you're ok with it, I will close this issue.

authors: RobvanGastel ztrong-forever


text:
关于工具的使用问题

您好，我在使用最后一个命令的时候出现如下提示，不知道怎么回事
cp: 无法获取'SimpleSources/sources.list' 的文件状态(stat): 没有那个文件或目录

@nishenge
你好，现在 v0.5 版本中的 sources.list 文件是和 Ubuntu 版本有关的，应该不会报你说的这种错误，你是直接 clone 下来然后运行的吗？方便地话可进一步提供更详细的信息（如 log 文件、报错截图等）我看下。

@nishenge
你好，现在 v0.5 版本中的 sources.list 文件是和 Ubuntu 版本有关的，应该不会报你说的这种错误，你是直接 clone 下来然后运行的吗？方便地话可进一步提供更详细的信息（如 log 文件、报错截图等）我看下。

您好  我做了一个演示视频  您可以看一下 https://smartshen.lanzoui.com/iEjwbuseyab  解压后就能看
因为没办法在线clone 所以我是下载下来放在那个目录下的

@nishenge
hello，要进到 rostaller 仓库里面为 run.sh 添加可执行权限，然后运行 run.sh，你的操作方式因为相对路径不对所以会导致找不到文件。README 里没有写进入仓库这一步。

@nishenge
hello，要进到 rostaller 仓库里面为 run.sh 添加可执行权限，然后运行 run.sh，你的操作方式因为相对路径不对所以会导致找不到文件。README 里没有写进入仓库这一步。

Hello，我对Linux不是很熟悉，麻烦您看一下是不是这样操作的。   结果依旧是没通过。   如果方便的话，麻烦您告诉我具体的操作步骤。   谢谢
这是我的操作视频  https://smartshen.lanzoui.com/iQZsnuswt1a

@nishenge
hello，你的操作没有问题，视频二中的错误是出在了 curl 向 http://keyserver.ubuntu.com 发起请求时连接失败，应该是网络问题（比如防火墙配置），你可以看下浏览器中是否可以直接打开 http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654 ，也可以试下直接在终端中执行下面语句看是否有效：
curl -sSL 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654' | sudo apt-key add -

如果没有问题得话，重新运行 run.sh。

@nishenge hello，你的操作没有问题，视频二中的错误是出在了 curl 向 http://keyserver.ubuntu.com 发起请求时连接失败，应该是网络问题（比如防火墙配置），你可以看下浏览器中是否可以直接打开 http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654 ，也可以试下直接在终端中执行下面语句看是否有效：
curl -sSL 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654' | sudo apt-key add -

如果没有问题得话，重新运行 run.sh。

hello，非常感谢您的耐心解答，已成功解决问题。    谢谢您

如果可以的话  希望您更新了Ubuntu14安装ros

@nishenge hello，你的操作没有问题，视频二中的错误是出在了 curl 向 http://keyserver.ubuntu.com 发起请求时连接失败，应该是网络问题（比如防火墙配置），你可以看下浏览器中是否可以直接打开 http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654 ，也可以试下直接在终端中执行下面语句看是否有效：
curl -sSL 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xC1CF6E31E6BADE8868B172B4F42ED6FBAB17C654' | sudo apt-key add -

如果没有问题得话，重新运行 run.sh。

hello，非常感谢您的耐心解答，已成功解决问题。 谢谢您 （我的解决办法是使用了科学上网）

应该不需要科学上网的，保证正常的网络连接即可，如果要求科学上网，那么这个工具就没有意义了。

如果可以的话 希望您更新了Ubuntu14安装ros

请单独再开一个 issue 吧，这个 issue 我先关闭掉了 🙂

@nishenge
hello，已添加对 Ubuntu 14.04 自动安装 ROS 1 Indigo 的特性，已通过测试，欢迎试用 🙂

authors: RocShi nishenge

repo: RocShi/rostaller


text:
文章重复

运行一段时间就会出现问题，发布时间稍微早点的文章会重复。

采用 Leancloud 部署。
博客链接：https://www.casecori.top/circle/
仓库链接：https://github.com/Cystee/hexo-circle-of-friends
API：https://circori.vercel.app/all

切换数据库之后还有问题吗

还有问题：

而且点这篇文章的卡片会提示无法获取，只有点最新的那一个才能看到，卡片里只有一篇文章：

这不是文章重复的问题
文章卡片获取不到说明数据库friend未查询到该作者，按照提示检查数据库，后续会考虑对无法获取的情况进行优化
如无其他问题，此issue将被关闭

okok

authors: Cystee hiltay

repo: Rock-Candy-Tea/hexo-circle-of-friends


text:
Why not Node 5??

Why not use Node 5 vs 0.10.x?

Code is based on Meteor platform 1.2.x.    Meteor 1.2.x is tested against 0.10.x

Ah okay -- was just curious -- always worth asking!

authors: Sing-Li robbyoconnor


text:
Cannot install latest version

App repeatedly tells me that there is an update available, and when I click install, it tells me that it will do so when ready, but never does. I typically just go to the web and download the new version, but now the website is two versions behind what the app says is "ready". This is what happened with 2.17.10, and now with 2.17.11.
My Setup

Operating System: Windows 10 1903
App Version:2.17.9
Installation type: downloaded windows install from rocket.chat.

[ ] I have tested with the latest version - I cannot test with latest version, as it is not available for me to install.
[x] I can simulate the issue easily - by just starting Rocket Chat

Description
Described above
Current Behavior
Described above
Expected Behavior
It should install the new version. Or failing that, I should be able to download the new version so that I can force the install.

Same for me, I have 2.7.10 and auto update to 2.7.11 fails on Windows 10.
A file c:\Users\...\AppData\Local\rocketchat-updater\pending\temp-rocketchat-setup-2.17.11.exe is being downloaded, but after a moment it's removed and nothing happens.

Same as https://github.com/RocketChat/Rocket.Chat.Electron/issues/1670

authors: Rich-Hopkins ankar84 xmedeko


text:
Multi-select dropdown i.e. tag selector

E.g.

this is in! Simply use multiSelect={true}

authors: adamiprinciples simon-rocketmaker

repo: Rocketmakers/armstrong-react