text:
issue label "good first issue"

It would be helpful for people looking to contribute if there was a label for issues suitable for a first-time contributor to okhttp.
I'd recommend "good first issue" as that's a common label name in other projects.

Tracking with https://github.com/square/okhttp/issues/5049

authors: sjconnor swankjesse


text:
Additions to Weather Underground client to support weather alerts

Updates to the Weather Underground client to support weather alerts, PoP (probability of precipitation), and initialization function to allow setting metric flag other than at instantiation.

@fowlerk -- Your commits have included getForecastText, but I'm having trouble with it.  Is it operable (or is it something on my side)?  I'm trying to use  wunderground.getForecastText() to get the WU text such as: this: Thursday: Steady light rain this morning. Showers continuing this afternoon. High near 60F. Winds light and variable. Chance of rain 60%.

@aliceand -- Yes, it is operational, this was one of the recent additions I added to the Weather Underground library.  You need to pass an integer period to indicate which forecast text you want to request from the function, like wunderground.getForecastText(0) to request the forecast for the current forecast period.  (You may already be aware, but for others, the 10-day forecast API returns (20) forecast periods (numbered 0-19), which include forecast info for each of the 12-hr periods of the 10-days (including the current period)).  Have a look at the code on my distro here https://github.com/fowlerk/ESP8266-Color-Weather-Station-v8, particularly the drawForecastText function as an example.  I call this (3) times passing 0,1,2 to get the next 36-hours of forecast text to display on the bottom panel.
If you're getting an error indicating the function isn't implemented, you likely need to update your library components with the latest from here (or my distro which includes some new features not yet merged into the master for weather alerts also).

@fowlerk --Thank You!  I appreciate your detailed response.  I should be able to make it work now.

source: gharchive/pull-request

authors: aliceand fowlerk

license: mit

license_type: permissive

license_source: bigquery


text:
this mirror is out of date

Please keep it up to date with hg tip.

+1

source: gharchive/issue

authors: frazr sunaku

repo: sr/dwm

license: MIT

license_source: github-api


text:
Is there a way to checkout a new branch, aka git co -b dev

Unfortunately I was not able to work out this bit myself nor could I find an example in the code. Is there a way to checkout a new local branch (and also how do I push this new branch)?
worktree.Checkout takes git.CheckoutOptions but if the reference does not exist there seems to be no way to create it first. Alternatively, what would be the way to create a new reference and then checkout normally?

Ok, got it sorted. If you are interested in examples to include I could submit one.

@osklyar How did you get this working? I am having the same problem. I would love to see an example.

@devonmoss See https://github.com/silvertern/xgit/blob/master/client/gitclient.go#L131 followed by https://github.com/silvertern/xgit/blob/master/client/gitclient.go#L195 -- essentially you first check if the branch is available in refs/heads, if yes, use it, if no, check if it exists in refs/remotes, if yes, link it to local one, if no create a new ref.

Thank you. This is excellent.

@devonmoss See https://github.com/silvertern/xgit/blob/master/client/gitclient.go#L131 followed by https://github.com/silvertern/xgit/blob/master/client/gitclient.go#L195 -- essentially you first check if the branch is available in refs/heads, if yes, use it, if no, check if it exists in refs/remotes, if yes, link it to local one, if no create a new ref. The code is currently WIP so I cannot guarantee line numbers remain unchanged :)

These links are now dead.

authors: devonmoss kiefersmith osklyar

repo: src-d/go-git


text:
Export urlEndpoint

Can urlEndpoint be exported? Right now I have to String() and re-parse the endpoint in order to get the URL object out for my custom transport. :-(

All Endpoint implementations could be exported. Could you make a PR for this?

authors: smola taralx


text:
Limit or offset number of results returned by With{Type}

It is stated in the documentation that filters (kallax.Condition) can be applied to  With{Type}() methods.
However, is it possible to apply offsets or filters to the rows joined by these functions? If so, what is the correct way of doing it?
Regards,
R

Nope, there's no way to apply offsets and limits to the Withs. That's by design. If you need to limit the results, it's not a relationship.
The ideal solution would be something like this:
type A struct {
    ID int64
    B []*B
}

type B struct {
    ID int64
    A *A
}

records, err := bStore.FindAll(NewBQuery().FindByA(a.ID).Limit(10))

Nice, I'll go for that aproach then.
Thanks!
PD: ... which forces me to change from Bs []B to Bs []*B, if I want to keep marshalling simple. Not taking advantage of CPU cache makes me cry at night.

No need, works with both []*B and []B. I put the * just because.

If I want to keep marshalling simple, this is, embedding the result of the "dependant" FindAll into a, I'd have to change it.
But anyway, as you said, when I have so many Bs, modeling the relation as A has many Bs feels unnatural. I'd rather model it as "B belongs to A", and query As separately.
Thanks for the advice!

authors: erizocosmico roobre

repo: src-d/go-kallax


text:
new Init method on entities

Every time that a entity with the method Init() error is recovered from the db, the method Init is called
type ResultSetInitFixture struct {
	storable.Document `bson:",inline" collection:"resultset"`
	Foo               string
}

func (r *ResultSetInitFixture) Init() error {
	r.Foo = "foo"
	return nil
}

Current coverage is 42.67%

Merging #25 into master will increase coverage by +0.41% as of debe215

@@            master     #25   diff @@
======================================
  Files           16      16
  Stmts         1138    1120    -18
  Branches        67      66     -1
  Methods          0       0
======================================
- Hit            481     478     -3
+ Partial         41      40     -1
+ Missed         616     602    -14

Review entire Coverage Diff as of debe215

Powered by Codecov. Updated on successful CI builds.

LGTM

LGTM

LGTM

authors: codecov-io dripolles klaidliadon mcuadros mvader

repo: src-d/storable


text:
Cannot download files

Since a couple or three versions ago I'm not able to download any files with FF-stable or FF-esr appimages.
I have no problems with LibreWolf appimage (another appimage derivative of FF-stable).
I'm running Debian-stable with Xfce.

It seems nobody cares. Mmmm....

Weird, is probably out of the scope for this repository. You might want to raise a support ticket with GitHub instead

These FF-appimages are unable to save files or to open a bookmark's backup file. It seems that they are unable to reach a directory, unable to interact with the file system. It doesn't happen with regular FF o with LibreFox.

Sorry I cannot reproduce this issue any more, can you please try the latest versions of firefox AppImages to see if this issue still exists?

Can't you reproduce this issue? Why? None of you have a computer?
Well, don't worry, I've got one. And you know what? Surprise!! Your Firefox-ESR appimages are unable to download anything. Who could imagine it?
But I'm sure that in a couple or three months someone with no manners will come, he won't be polite, he won't be cool, he will be insulted, but in the end you will address the problem. It's just a matter of time...

Since you are able to reproduce the issue, can you run the AppImage from the terminal to see if Firefox is generating any errors? If yes, I can investigate on them

Done. There are no error messages.
It seems that the FF-esr appimage is unable to reach the file system. It's unable to download anything, but is unable to open anything from the file system as well: You select "open" and absolutely nothing happens.

Thanks for testing, may I know which desktop environment you are using? Not sure if it is related. Also, do you have something like firejail installed?
To check if its related to some existing config, I tried this:
./firefox-esr.....AppImage --appimage-portable-home
./firefox-esr.....AppImage --appimage-portable-config
./firefox-esr.....AppImage # which now uses the portable config folder and home

but still the download works, the Downloads are now stored in ~/firefox-esr..../Downloads. Let me know if this approach works, if yes, we can narrow down the scope of the problem.

By a regular installation, do you mean, those which are installed from the package manager for your distribution? Can you also test using the binary provided by firefox here: https://www.mozilla.org/en-US/firefox/all/#product-desktop-esr to see if the issue does not exist with this one?
I am wondering if the issue is related to the rewrite of many firefox features (esr-next to esr), which possibly broke some config.

Done.
Debian's default FF is the ESR version. I installed it, it worked properly when clean and with my complete configuration.
As you suggested, I downloaded the binary provided by Mozilla of FF-ESR as well. It worked properly clean and with my complete configuration.

Ok, but the issue on latest Firefox ESR 102.5 AppImage still exists? Also do you use any appimage utilities like AppImageLauncher

Yes, your last ESR appimage can't open or save anything with my configuration (it can do it when it is clean). But Mozilla's FF-ESR binary works properly with my configuration.
To open appimages I just use a launcher from my desktop panel (on the other hand, double click on the FF-esr appimage doesn't change its weird behaviour).

Hi. I've tried with the latest version of the appimage (v111), with my current and a fresh profile, as well as starting firefox in safe mode (all extensions disabled etc). The issue persists.
When running from the terminal the following warning appeared when I tried to use File->Open:
(firefox:22209): Gtk-WARNING **: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files

googled that error,  seems it's a common thing with flatpaks/snaps/appimages. various suggestions:

installed xdg-desktop-portal and xdg-desktop-portal-gtk
neither of these alone or both fixed it, so not sure if they're needed. But what did fix it was:
set widget.use-xdg-desktop-portal.file-picker to 0 in the about:config in Firefox.

File dialogs now work as expected! Hurrah! :tada:

authors: IdolIcon marc1uk srevinsaju suotroel

repo: srevinsaju/Firefox-Appimage


text:
Make Journals property names configurable

Currently, the plugin defaults to using the following properties:
journal: journal
journal-end-date: 2024-12-24
journal-section: day
journal-start-date: 2024-12-24

It would be good if the names of the properties could be customized so that they can be tailored to your users' frontmatter schemes. E.g. I have properties in my notes like date-start that would already satisfy the journal-start-date property as it has the same value.

good point
will add this as further enhancement after v2 release

repo: srg-kostyrko/obsidian-journal


text:
Consider using GitHub Actions to always keep events updated

Today GitHub released Actions. It might be useful to set them up to automatically trigger the codegen when there is a commit to the Go repo and create a PR with the corresponding changes here.

The events crate has now moved to https://github.com/LegNeato/aws-lambda-events. Because of GitHub limitations (https://help.github.com/articles/transferring-an-issue-to-another-repository/) this issue is being closed rather than transferred.
If it is still relevant, please open an issue in the new repo.
Sorry for the churn!

repo: srijs/rust-aws-lambda


text:
Could we only allow enabled user login through Oauth?

Add user from github is awesome, but for security concerns, Oauth login should not open to everyone...How you deal with this problem?

you can choose to allow only known users to login - http://www.go.cd/documentation/user/current/configuration/configuration_reference.html#security

thanks again, really help a lot, btw I got some trouble when I use user api to delete user,
when the user name is a email address, I will get this :
curl -k 'https://.com/go/api/users/@gmail.com'       -u ':**'       -H 'Accept: application/vnd.go.cd.v1+json'       -X DELETE
{
"message": "Either the resource you requested was not found, or you are not authorized to perform this action."
}
the user is not admin and disabled...why we just have a delete user button?

welcome!
the delete user api issue is Go's issue. can you raise an issue for that in https://github.com/gocd/gocd?
thanks.

Can you try:
curl -k 'https://******.com/go/api/users/********%40gmail%2Ecom' -u '******:******' -H 'Accept: application/vnd.go.cd.v1+json' -X DELETE

Hi Srinivas
I have successfully installed and configured the plug-in, however, it still allows anonymous logins, even with the config set as you suggested:
  <server ...

    <security allowOnlyKnownUsersToLogin="true">
      <admins>
        <user>pejvan</user>
      </admins>
    </security>
  </server>

Any suggestions?

yes. thats a limitation currently. to enable authentication you will need to add a dummy (with no valid users) LDAP / password file authentication. this is just to enable authentication in Go. once its enabled GitHub authentication will kickin.

authors: Ehekatl pejvan srinivasupadhya

repo: srinivasupadhya/gocd-oauth-login


text:
astwifid: Add configuration option for bridge device

Closes #74

Good choice of emoji as it's San Francisco.

repo: srobo/astoria


text:
Deprecate download flag (useGlobalNode)

Deprecate download flag and introduce useGlobalNode instead. If this is true, then it will use global installed node (that is in path) instead of downloading node.

I like this plugin because it means that my project only depends on Java being installed; with the Gradle wrapper, Gradle will download and update itself, while this plugin handles downloading/updating NodeJS.
If you work with a team of developers, then these features are handy because it means that the whole team is always using the same version the toolchain, which makes it easier to reproduce problems. Using system-installed software increases the likelihood of "Works on my machine" which can be difficult to track down.
Deprecations should generally only be done when you have a suitable replacement - in this case download and useGlobalNode do different things, and therefore the latter is not a replacement for the former. It would perhaps be better to recommend useGlobalNode (if that is your preference), without deprecating download.

Sorry, did not see this comment before now. Yes, I know, 8 months later :-) You are absolutely right. Will not deprecate download, but will default set this to true in the 1.0 release. Starting to write a migration guide of breaking changes here: https://github.com/srs/gradle-node-plugin/wiki/Migration-Guide

authors: jawnsy srs

repo: srs/gradle-node-plugin


text:
tile Vector feature style based on job status, final result availability

job submitted/on going = grey line fill
job finished successfully/ final result available = green line fill
job failure = red line fill
should have a toggle to show "advanced" tile states on map or not.

Relates #10 #12


text:
Github Issue

We are facing problems while installing the packages.

You can use npm install @sse-auth/github --force to install the packages. We will fix this issue in the newer version.
Thankyou for informing it.

repo: sseworld/sse-auth


text:
get output files from PCE to web interface

Need to figure out how to get the files from the PCE to the web server, and from the web server to the web interface.

The PCE is currently serving this information, but the PCEAccess class in the server implementation needs to be updated to fetch it.

Closed with commit: 797d3777c0485cdcf07949faa218f10a3beac1e2.
A few other refactoring items included:

changed users.js to start.js to match start.html
changed some manual path construction to use os.path.join instead.  much more portable and less error-prone.

authors: koepked ssfoley

repo: ssfoley/onramp


text:
Cannot select/handle "non-standard" font size

The dialog allows to select a font size from a list box, which limits possibility to use an arbitrary size.
And when an unexpected font size is fed into the dialog, it displays it incorrectly (f.i., 55 will be shown as 10, and if OK is pressed 10 is passed further).

Though p.1 is rather hard to fix without redesigning the dialog, I propose to handle this problem at least partially and fix p.2: when an unexpected font size is encountered, the dialog shouldn't touch it unless the user explicitly selects a new size.

Hello, and thanks for the feedback! I have modified the dialog so you optionally can input arbitrary font sizes, as well as input your own custom font size range if you want to use a still limited (but different) allowed size range. It should be on Nuget as of now.

hello, can we hide some content? like hide color selector?

It was a pretty quick feature to implement, so i made the changes for you. Just input the bool in constructor whether to show or hide color selector from the lastest version.
Also don't forget if you want to customize or change more stuff around for you own needs, you can always just fork!

authors: Anton-V-K dabnoj sskodje

repo: sskodje/WpfColorFont


text:
Update atlassian-trello.yaml

Added a link to Atlassian Access's pricing which adds $4 to each Trello plan (Free, Standard and Premium) but Enterprise.

Thank you @kalinres . I made an adjustment as the USD 4 need to be added to the base pricing: 4 -> 14.

authors: MMore kalinres

repo: ssotax/ssotax


text:
Nextjs doesn't have "copyFiles" property

Pre ion, NextjsSite construct had a cdk prop and from there, via server.copyFiles you could have added an array of files.
In ion, only Function has copyFiles prop. I guess Nextjs is missing it, since Dax told me to open this issue.

Hmm is this the correct repository? NextjsSite is related to https://github.com/sst/sst

Hmm is this the correct repository? NextjsSite is related to https://github.com/sst/sst

You are absolutely correct. I've been thinking about open-next too much lately. Because of the streaming, I've opened this issue instinctively.
I'm taking it to sst repo.
Thanks

authors: aquarazorda khuezy

repo: sst/open-next


text:
Example: Debugging in Webstorm

Requested by gio in Slack

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble

authors: fwang thdxr

repo: sst/sst


text:
tests: fix path_without to handle /bin properly

I was seeing /bin being left.  This patch fixes it by anchoring the search
pattern with ':' on both sides.
Also affects pyenv.

Thanks!

authors: blueyed mislav

repo: sstephenson/rbenv


text:
support mysql read concurrency with NOWAIT and SKIP LOCKED

see https://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html#innodb-locking-reads-nowait-skip-locked
closes https://github.com/staabm/phpstan-dba/issues/340

Cool thanks!

authors: Seldaek staabm

repo: staabm/phpstan-dba


text:
RangeError: Invalid value: Not in range 0..1114111, inclusive: -1

Hi. I'm experiment with PersistentStore and executeQuery method.
Just try a simple query:
final pStore = PostgreSQLPersistentStore('postgres', 'xxxxxx', 'localhost', 5432, 'MyTest);
const query = 'SELECT id, testo, attivo FROM lux_appo';
final rsets = await pStore.executeQuery(query, {}, const Duration(seconds: 30).inSeconds);

And I received Exception "RangeError: Invalid value: Not in range 0..1114111, inclusive: -1".
I'm running: psql (PostgreSQL) 12.3 and Dart VM version: 2.8.4 (stable).
This is the entire log:
[SEVERE] aqueduct: GET /appo 53ms 500 {user-agent : Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0\nconnection : keep-alive\ncache-control : max-age=0\naccept : text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8\naccept-language : it\naccept-encoding : gzip, deflate\ndnt : 1\nhost : localhost:8888\nupgrade-insecure-requests : 1\n}  RangeError: Invalid value: Not in range 0..1114111, inclusive: -1 #0      StringBuffer.writeCharCode (dart:core-patch/string_buffer_patch.dart:76:9)
#1      PostgreSQLFormat.substitute (package:postgres/src/substituter.dart:83:29)
#2      Query.sendExtended (package:postgres/src/query.dart:61:38)
#3      _PostgreSQLConnectionStateIdle.processQuery (package:postgres/src/connection_fsm.dart:182:9)
#4      _PostgreSQLConnectionStateIdle.awake (package:postgres/src/connection_fsm.dart:168:14)
#5      _PostgreSQLExecutionContextMixin._enqueue (package:postgres/src/connection.dart:399:67)
#6      _PostgreSQLExecutionContextMixin.query (package:postgres/src/connection.dart:318:12)
#7      PostgreSQLPersistentStore.executeQuery (package:aqueduct/src/db/postgresql/postgresql_persistent_store.dart:297:38)
<asynchronous suspension>
#8      AppoController.getAppo (package:lux_aqueduct_server/controllers/appo_controller.dart:16:32)
#9      _InstanceMirror._invoke (dart:mirrors-patch/mirrors_impl.dart:339:37)
#10     _InstanceMirror.invoke (dart:mirrors-patch/mirrors_impl.dart:335:25)
#11     BoundOperation.invoke (package:aqueduct/src/http/resource_controller_internal/controller.dart:24:10)
#12     ResourceController._process (package:aqueduct/src/http/resource_controller.dart:371:36)
<asynchronous suspension>
#13     ResourceController.handle (package:aqueduct/src/http/resource_controller.dart:138:14)
<asynchronous suspension>
#14     Controller.receive (package:aqueduct/src/http/controller.dart:174:30)
#15     _ControllerRecycler.receive (package:aqueduct/src/http/controller.dart:402:17)
#16     Controller.receive (package:aqueduct/src/http/controller.dart:206:28)
<asynchronous suspension>
#17     Router.receive (package:aqueduct/src/http/router.dart:139:18)
#18     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#19     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#20     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:266:7)
#21     _ForwardingStreamSubscription._add (dart:async/stream_pipe.dart:134:11)
#22     _MapStream._handleData (dart:async/stream_pipe.dart:234:10)
#23     _ForwardingStreamSubscription._handleData (dart:async/stream_pipe.dart:166:13)
#24     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#25     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#26     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:266:7)
#27     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:779:19)
#28     _StreamController._add (dart:async/stream_controller.dart:655:7)
#29     _StreamController.add (dart:async/stream_controller.dart:597:5)
#30     _HttpServer._handleRequest (dart:_http/http_impl.dart:2837:19)
#31     new _HttpConnection.<anonymous closure> (dart:_http/http_impl.dart:2596:19)
#32     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#33     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#34     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:266:7)
#35     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:779:19)
#36     _StreamController._add (dart:async/stream_controller.dart:655:7)
#37     _StreamController.add (dart:async/stream_controller.dart:597:5)
#38     _HttpParser._headersEnd (dart:_http/http_parser.dart:399:19)
#39     _HttpParser._doParse (dart:_http/http_parser.dart:739:15)
#40     _HttpParser._parse (dart:_http/http_parser.dart:328:7)
#41     _HttpParser._onData (dart:_http/http_parser.dart:850:5)
#42     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#43     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#44     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:266:7)
#45     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:779:19)
#46     _StreamController._add (dart:async/stream_controller.dart:655:7)
#47     _StreamController.add (dart:async/stream_controller.dart:597:5)
#48     _Socket._onData (dart:io-patch/socket_patch.dart:1982:41)
#49     _RootZone.runUnaryGuarded (dart:async/zone.dart:1374:10)
#50     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#51     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:266:7)
#52     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:779:19)
#53     _StreamController._add (dart:async/stream_controller.dart:655:7)
#54     _StreamController.add (dart:async/stream_controller.dart:597:5)
#55     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1527:33)
#56     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1019:14)
#57     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#58     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#59     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#60     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

Ok. I used a dependency_overrides in pubspec.yaml to forcing use postgres: 2.1.1 as a temporary workaround, and it works.
Any news on a final fix?
Many thanks.
Luca

I'm following the aqueduct tutorial and I get the same error after running the aqueduct db upgrade. I changed to postgres to 2.1.1 and I get the same error.

Yes, in db migration appears the same error and override postgres to 2.1.1 in pubspec.yaml does not solve it.

Yes, in db migration appears the same error and override postgres to 2.1.1 in pubspec.yaml does not solve it.
EDIT: Solved. Run pub run aqueduct db upgrade in application folder.

Thank you, that solved my problem.

➜  server git:(master) ✗ aqueduct db upgrade
-- Aqueduct CLI Version: 3.3.0+1
-- Aqueduct project version: 3.3.0+1
*** Uncaught error
RangeError: Invalid value: Not in inclusive range 0..1114111: -1
**** Stacktrace

#0      StringBuffer.writeCharCode (dart:core-patch/string_buffer_patch.dart:74:9)
#1      PostgreSQLFormat.substitute (package:postgres/src/substituter.dart:83:29)
#2      Query.sendExtended (package:postgres/src/query.dart:61:38)
#3      _PostgreSQLConnectionStateIdle.processQuery (package:postgres/src/connection_fsm.dart:182:9)
#4      _PostgreSQLConnectionStateIdle.awake (package:postgres/src/connection_fsm.dart:168:14)
#5      _PostgreSQLExecutionContextMixin._enqueue (package:postgres/src/connection.dart:399:67)
#6      _PostgreSQLExecutionContextMixin.query (package:postgres/src/connection.dart:318:12)
#7      PostgreSQLPersistentStore.execute (package:aqueduct/src/db/postgresql/postgresql_persistent_store.dart:153:37)

#8      PostgreSQLPersistentStore.schemaVersion (package:aqueduct/src/db/postgresql/postgresql_persistent_store.dart:216:26)
#9      CLIDatabaseUpgrade.handle (package:aqueduct/src/cli/commands/db_upgrade.dart:28:52)
#10     CLICommand.process (package:aqueduct/src/cli/command.dart:159:20)

#11     CLICommand.process (package:aqueduct/src/cli/command.dart:135:12)
#12     CLICommand.process (package:aqueduct/src/cli/command.dart:135:12)
#13     main (file:///Users/roott/.pub-cache/hosted/pub.flutter-io.cn/aqueduct-3.3.0+1/bin/aqueduct.dart:9:27)
#14     _startIsolate. (dart:isolate-patch/isolate_patch.dart:299:32)
#15     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

The problem is  that + postgres 1.0.2 (2.2.0 available) is not the latest one, when i run   pub global activate aqueduct.
~  pub global activate aqueduct
Package aqueduct is currently active at version 3.3.0+1.
Resolving dependencies... (1.5s)

analyzer 0.35.4 (0.40.2 available)
aqueduct 3.3.0+1
args 1.6.0
async 2.4.2
charcode 1.1.3
codable 1.0.0
collection 1.14.13
convert 2.1.1
crypto 2.1.5
front_end 0.1.14 (0.1.29 available)
glob 1.2.0
isolate_executor 2.0.2+3
js 0.6.2
kernel 0.3.14 (0.3.29 available)
logging 0.11.4
meta 1.2.3
node_interop 1.1.1
node_io 1.1.1
open_api 2.0.1
package_config 1.9.3
password_hash 2.0.0
path 1.7.0
pedantic 1.9.2
postgres 1.0.2 (2.2.0 available)
pub_cache 0.2.3
pub_semver 1.4.4
safe_config 2.0.2
source_span 1.7.0
string_scanner 1.0.5
term_glyph 1.1.0
typed_data 1.2.0
watcher 0.9.7+15
yaml 2.2.1
Precompiling executables... (14.6s)
Precompiled aqueduct:aqueduct.
Installed executable aqueduct.
Activated aqueduct 3.3.0+1.

we can clone aqueduct to local and activate it from local.
pub global activate --source path ./
and add dependencies from local.
dependencies:
aqueduct:
path: /Users/xxxx/xxxx/xxxx/aqueduct/aqueduct

It was getting this error by running $ aqueduct db upgrade (dart from flutter).
How I fixed it
override dependency to postgre
pubspec.yaml
dependency_overrides:
postgres: 2.1.1
then run this using pub
$ flutter pub run aqueduct db upgrade

authors: RGkevin luX0r-reload mejiad zmtzawqlp

repo: stablekernel/aqueduct


text:
clarify that field names can be prefixed with properties or not

Related Issue(s):

#1

Proposed Changes:

Clarify that implementers decide if field names need to be prefixed with properties or not

PR Checklist:

[X] This PR has no breaking changes.
[X] I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

Should we say that a /queryables implementation would be helpful nevertheless? Otherwise, LGTM.

Should we say that a /queryables implementation would be helpful nevertheless? Otherwise, LGTM.

I was thinking we would define a /fieldable (includable? something like that) endpoint that is optional to implement, but not for rc.2. maybe for 1.1

authors: m-mohr philvarner

repo: stac-api-extensions/fields


text:
Add static typing to CI

Add configuration for mypy (disallow untyped defs in this repo) and get this running in CI.

There's already a mypy hook in pre-commit-config:
https://github.com/stac-utils/stac-geoparquet/blob/50f2886b7d8acfe5053c936f42c6240c0aecb3d7/.pre-commit-config.yaml#L21-L37
I generally dislike putting the mypy check in pre-commit because it doesn't have access to any dependencies, or, in this case, you have to re-define dependencies (and I assume that anything listed in additional_dependencies is not constrained to the same versions in any other lockfile)

Ah right, forgot about that.
I agree with moving it out of pre-commit now that this is growing a bit.

Closed by #44

authors: TomAugspurger kylebarron

repo: stac-utils/stac-geoparquet


text:
[CMake] set INSTALL_RPATH for python on linux

To avoid the need for python users to set LD_LIBRARY_PATH when the CMAKE_INSTALL_PREFIX is not a standard one.
ref. https://github.com/stack-of-tasks/eigenpy/pull/241

Thanks @nim65s !

repo: stack-of-tasks/tsid


text:
Bolt is now not working (An unknown error occurred while processing the server's response.)

Describe the bug
I have been getting this error "An unknown error occurred while processing the server's response." and the only resolve it gives it to retry and nothing happens. i have refreshed the web page and now it won't load my project. I have already poured $50 worth of tokens into this project and I was at least 90% done and now I'm stuck.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-11fied
Steps to reproduce
I just asked it to edit a function in the UI interface.
Expected behavior
to update the request
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = 130.0.0.0
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 158423693,
  "usedJSHeapSize": 140946969,
  "jsHeapSizeLimit": 4294705152
}
Username = Azraelblame
Chat ID = d0bb293fbac7

Additional context
Error:
An unknown error occured while running an action.

The same thing is happening to me. Did you ever get it resolved?

authors: Azraelblame MASDDB


text:
Missing Tokens

Describe the bug
When I subscribed I subscribed for pro version but it said i had 30 M tokens, but now it just says I have 1 M left and have used around 8M+ tokens out of 10M token, theres a major discrepancy and please resolve this
Link to the Bolt URL that caused the error
https://bolt.new/
Steps to reproduce
Go to Settings> Tokens
Expected behavior
It should have had 30 M tokens but it only has 1M + tokens left.
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Everytime I try to update one component it removes something else. I have wasted $90 so far an have not completed one thing. Please resolve the issues. It keeps happening over and over again. I am also sure I have not gone through all the tokens. Also the price keeps changing. First it was $9.00 then jumped to $20 per 10M tokens. This is frustrating.

@gitboikills the pro plan includes 10m tokens so everything seems in order here.
@ginuineca please reference issue #678 for tips around increasing token usage efficiency

authors: ginuineca gitboikills kc0tlh


text:
bolt repeatedly breaks things and costs me millions of tokens in fixing stuff that it did not do properly

Describe the bug
It has burned through over one million tokens just today, fixing things which should not have needed fixing. When I complained that it had fixed the Preview screen when I did not ask it to do that, it totally redeployed my app. I cannot afford to use this product given that you charged me $30 for 10 mill and they are almost half gone and all on fixing mistakes Bolt created.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-gz7tdz
Steps to reproduce
I can't describe them because Bolt deleted all of our chats.
Expected behavior
I expect Bolt to update things properly, instead of having to do things over and over and over again until it gets it right. Then things work great for a while, and I will ask it to make some TRIVIAL change, because we are basically DONE, but it then BREAKS something, and ends up using hundreds of thousands of tokens trying to fix each simple detail.
Screen Recording / Screenshot
https://somup.com/cZ6TYtHd8i
Platform
Browser name = Chrome
Full version = 130.0.0.0
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 93229128,
  "usedJSHeapSize": 89673912,
  "jsHeapSizeLimit": 4294705152
}
Username = horserankerco
Chat ID = a8221410e4ad

Additional context
I have seen many other people utter similar complaints, that it does well for a while but then it starts deleting or breaking processes while it is supposedly performing simple updates.

I wonder if they are reading this and the large pile of similar complaints here. Something is seriously wrong and must be addressed urgently. I know they are working on it, but meanwhile I believe they should at least explain what's happening. Shouldn't they also proactively refund the millions of tokens spent trying to fix errors that should't have occurred in the first place?

I'm estimating a loss of around 30 million tokens due to these persistent errors. It's extremely concerning to encounter repeated >199k prompt limit messages for simple, one-line queries.
Quickly addressing and resolving these issues is an immediate and non-negotiable requirement. Many of us here are deeply concerned and need the team to fully understand the severity of this situation. We're not just unhappy—significant financial losses are at stake, compounded by lingering frustration from the recent unexpected and substantial token cost increase.
This situation feels like early supporters are bearing the brunt of these problems while the system is being fixed. Moments like this define reputations, and we are watching closely to see how the team responds. We want to succeed together, but right now, the system is not functioning as it should.
Every hour of downtime further devalues each token.

@jaywakeford @leosdad @horserankerco, apologies for the frustrating experience during the beta!
We are working aggressively to address these issues (and sharing progress publicly in #678) but we are a small team and ensuring everyone sees the updates has been a challenge!

Thank you,  I appreciate the response and continue cheering you on as a team!   It is a fantastic product.   That said I have lost upwards of 30m tokens without clear understanding or resolution during the iterations.   Great news is I just tried running a command and it seems to be live again.     Was a painful last 5 days but happy to be live again.  Have a great week!  Warm regards,  Jay WakefordOn 29 Oct 2024, at 2:11 PM, Alexander Berger @.***> wrote:
@jaywakeford @leosdad @horserankerco, apologies for the frustrating experience during the beta!
We are working aggressively to address these issues (and sharing progress publicly in #678) but we are a small team and ensuring everyone sees the updates has been a challenge!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I spoke a little too soon.  Hit a brick wall again with relatively simple requests.   Hopefully the issues are resolved to satisfaction.  Warm regards, Jay WakefordOn 29 Oct 2024, at 3:13 PM, Jay Wakeford @.> wrote:Thank you,  I appreciate the response and continue cheering you on as a team!   It is a fantastic product.   That said I have lost upwards of 30m tokens without clear understanding or resolution during the iterations.   Great news is I just tried running a command and it seems to be live again.     Was a painful last 5 days but happy to be live again.  Have a great week!  Warm regards,  Jay WakefordOn 29 Oct 2024, at 2:11 PM, Alexander Berger @.> wrote:
@jaywakeford @leosdad @horserankerco, apologies for the frustrating experience during the beta!
We are working aggressively to address these issues (and sharing progress publicly in #678) but we are a small team and ensuring everyone sees the updates has been a challenge!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi Alex,
To be absolutely clear, if there’s any perception that I haven’t exercised patience and accepting this being in beta, just review my 900 open issues. I’ve been trying to resolve these for over a week BEFORE escalating, potentially adding to the backlog. My costs are your margins—let that be understood. However, after upgrading to the $100 monthly tier, my patience has turned into a strong sense of being overcharged. When paying such fees, I expect a product that doesn’t fail on this scale.
In today’s chat, I was the one reluctantly asking for resolution steps for issues like these.
Issues #900 and #907 on GitHub.
Honestly, your team should consider addressing and resolving the existing issues before pushing forward with a product launch on platforms like Product Hunt. Development improvements may address future problems, but there should be a concerted effort to properly manage and resolve the current backlog, especially for your early supporters like myself. The team’s inexperience is becoming increasingly evident.
Kind regards,Jay WakefordOn 29 Oct 2024, at 3:13 PM, Jay Wakeford @.> wrote:Thank you,  I appreciate the response and continue cheering you on as a team!   It is a fantastic product.   That said I have lost upwards of 30m tokens without clear understanding or resolution during the iterations.   Great news is I just tried running a command and it seems to be live again.     Was a painful last 5 days but happy to be live again.  Have a great week!  Warm regards,  Jay WakefordOn 29 Oct 2024, at 2:11 PM, Alexander Berger @.> wrote:
@jaywakeford @leosdad @horserankerco, apologies for the frustrating experience during the beta!
We are working aggressively to address these issues (and sharing progress publicly in #678) but we are a small team and ensuring everyone sees the updates has been a challenge!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi Alex, To be absolutely clear,,,

Let me add that the team answered here and they are quite active in Discord. At least they seem to be listening. This is the beginning and they have lots pf constructive feedback already so they can steer towards the right direction very quickly. The overwhelming response should tell them that the dev community was eager to put their hands on a product like this, and at least in the surface it appears to deliver what is promises. Nevertheless, what must be stressed is that the product is obviously not ready for prime time! I didn't find the word "beta" anywhere in the UI, and I believe they should come clean about it. It's clearly a beta or even a pre-beta (does aanyone still call anything "pre-beta" these days?), it has lots of bugs, don't use it for production, use at your own risk. Also addressing the many refund requests and complaints about lost tokens would be very welcome.

@leosdad @jaywakeford we absolutely are listening and moving as fast as we can to improve the product! We had no idea it would be this successful right at launch, and our very small team is hustling to try and keep up with the feedback, but obviously have fallen a bit behind given the torrent of feedback across Github, email, twitter, live chat, reddit and discord.
We are committed to addressing each issue, with a priority on refund requests which are handled via hello@stackblitz.com, and have begun onboarding people to help with support.
Thanks again for the patience and feedback.
P.S. @jaywakeford I responded to those other 2 tickets you mentioned just now as well.

authors: horserankerco jaywakeford kc0tlh leosdad


text:
Issue with swapped dependency

Describe the bug
Running npm i @swc/core causes the following error:
❯ npm i @swc/core
npm ERR! Failed to fetch dependencies:
npm ERR! - @swc/wasm@1.3.93

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/.npm/_logs/2023-10-20T23_44_48_973Z-debug-0.log

My assumption is that "@swc/core" is being swapped for "@swc/wasm", with the matching version. The reason I am assuming that is because if I install one of the projects, that gives me the issue, locally then I get @swc/core@1.3.93. The issue is that the only 1.3.93 versions of @swc/wasm are nightlys, so @swc/wasm@1.3.93 does not exist.
I noticed the issue, because I have been unable to load any Storybook sandboxes from "https://storybook.new/". I did end up finding a workaround, once I realized what was happening, which is to add "@swc/core": "1.3.92" to my dependencies, so my child dependencies don't install @swc/core@1.3.93.
Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-webcontainer-api-starter-pprezj
Steps to reproduce

Run npm i @swc/core in a web-container.

Expected behavior
Since my child dependency has "@swc/core": "^1.3.82" in it's dependencies, I would expect a valid version of the replacement, which in this case would be "@swc/wasm@1.3.92.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform

OS: [Windows]
Browser: [Chrome, Edge, Firefox]
Version: [118.0.5993.89, 119.0.2151.2, 119.0b8]

Additional context
No response

:wave: Thanks for the report, this looks like an error on our side, we assumed that @swc/core and @swc/wasm would be released in lockstep.
Your particular issue might solve itself on its own if they happen to bump the Wasm version, but at any rate, we probably need to look into handling this more graciously.

authors: Marklb jrvidal

repo: stackblitz/webcontainer-core


text:
Bug: WASM-based npm package works only when stepping through in debugger

Describe the bug
Using a library that loads and runs WASM does not seem to run (a terminating log statement is not hit or error logged) unless the dev tools are open and you explicitly step through execution to the end.
Link to the blitz that caused the error
https://stackblitz.com/edit/node-vireo-hello-world
To Reproduce
Steps to reproduce the behavior:

Open the blitz and run node index.js with devtools closed

Note that the output shows Hello Node.js v14.16.0! but does not show an ascii art mandelbrot or the output done :D

Open the blitz and run node index.js with devtools open. Meticulously step through the code stepping into functions and stepping into async tasks (not running to a breakpoint).

Note that everything seems to work correctly and print the above mentioned output 🤯

Expected behavior
Expect the mandelbrot ascii art and completion message to print without meticulously stepping through the code in the chrome debugger.
Screenshots
See above
Desktop (please complete the following information):

OS: Win 10 20H2 (OS Build 19042.985)
Browser Chrome
Version 90.0.4430.212 (Official Build) (64-bit)

Additional context
If I had to guess maybe there is an issue with async and waiting for tasks in the event queue to complete? How the heck would that even work without plugs into V8 itself or something funny like shimming zone.js into everything? (goes to mess with the example) I actually think this might be the issue, if I add a setInterval to keep the event queue alive it seems to print everything reliably: https://stackblitz.com/edit/node-vireo-hello-world-event-queue-keepalive
Edit: This is really freakin cool ♥

That definitely seems like a bug in our event loop being closed to soon.
Thanks for reporting 🙏

@rajsite I looked at this and I cannot seem to reproduce this on my end. I forked your project and tested it again and it works for me https://stackblitz.com/edit/node-vireo-hello-world-tqhdjy. Can you try it again?

Hmm I still see the same issue, my current machine configuration is different:
macOS Big Sur 11.5.1
Chrome Version 92.0.4515.107 (Official Build) (x86_64)
Both my example and the fork show the behavior of the first screenshot (only "Hello Node" is printed and not the Mandelbrot ascii art). I tried in incognito mode. Also tried with clean profile and all extensions disabled:
open /Applications/Google\ Chrome.app --args --disable-default-apps --disable-extensions --user-data-dir=/tmp/testprofile2 --no-first-run

@rajsite We were able to reproduce the issue, and are currently looking into a fix.

@rajsite This now works :tada:

@jrvidal I  confirmed on my machine too, ty!

authors: KwintenP d3lm jrvidal rajsite


text:
Sharp library failure in Gatsby project

Describe the bug
A Gatsby project that uses the gatsby-plugin-sharp plugin doesn't run with gatsby dev:
 ERROR

Error in "/home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/gatsby-node.js":
Something went wrong installing the "sharp" module

Cannot find module '../build/Release/sharp.node'
Require stack:
- /home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/node_modules/sharp/lib/const
ructor.js
- /home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/node_modules/sharp/lib/index
.js
- /home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/safe-sharp.js
- /home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/index.js
- /home/projects/my-docs-site/node_modules/gatsby-plugin-sharp/gatsby-node.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/bootstrap/resolve-module-exports.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/bootstrap/load-plugins/validate.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/bootstrap/load-plugins/load.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/bootstrap/load-plugins/index.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/bootstrap/load-config-and-plugins.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/services/initialize.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/services/index.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/state-machines/develop/services.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/state-machines/develop/index.js
- /home/projects/my-docs-site/node_modules/gatsby/dist/commands/develop-process.js
- /home/projects/my-docs-site/.cache/tmp-83-Spj6KQC39tw4

- Remove the "node_modules/sharp" directory then run
  "npm install --ignore-scripts=false --verbose sharp" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/install
- Search for this error at https://github.com/lovell/sharp/issues

Link to the blitz that caused the error
https://stackblitz.com/edit/my-docs-site?file=package.json
Steps to reproduce
Run npm run dev
Expected behavior
Build should succeed without errors
Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 91.0.4472.114
Major version = 91
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 64918242,
  "usedJSHeapSize": 57704938,
  "jsHeapSizeLimit": 4294705152
}
Hash = 84452ea99b8c6a79e19cae2129beaf85d5da007c

Additional context
No response

I think there is still some work needed to support Sharp on Stackblitz, per comments I saw over in #241

@thescientist13 thanks for heads up ! Sorry I didn't search for similar issues.
It looks like it's WIP https://github.com/stackblitz/webcontainer-core/issues/147#issuecomment-855642099
Do you have a timeline to share for the sharp polyfill already ?

Hey @icaraps. I'm just a stackblitz user / fan so unfortunately I can't help you there.

Hey @icaraps. So the problem with sharp is that it's a native binary. We're actively working on converting Sharp to WASM and bringing support for it to StackBlitz. We'll keep you posted.

This probably can be closed now :) https://blog.stackblitz.com/posts/bringing-sharp-to-wasm-and-webcontainers/

Yes, we now support sharp but you have to use >=0.31.3 for this to work. I am going to close this issue but if encounter any issues with it please file a new ticket.


text:
Deal with comment "spam"

We need to prevent the same user from over-commenting on posts. Users have been complaining about this because they see what looks like a discussion only to realize it's the same user repeatedly commenting. We can use a combination of rate-limits and sat barriers. Behavior we want to prevent:

the same user commenting multiple times at the same level
the same user replying to themselves repeatedly?

(1) is more important than (2). The hope is preventing these will force these users to say everything they want to say in a single comment and be concise and more thoughtful.
We can make the second comment at the same level either not possible (by not allowing it), or simply make it prohibitively expensive (1000 sats).

The easiest solution to this is preventing multiple comments from the same user on one parent. We'll see how well this goes and do more if necessary.


text:
Sats forwarded to anon don't go to rewards

Description
If sats are forwarded to @anon, the sats don't go to rewards like anon zaps but increase the balance of anon.
Steps to Reproduce

Create item and forward 100% sats to anon
Zap item with 100 sats item (can be anon)
Check /rewards
Rewards increased by 5 sats via fees and rewards via anon's stack didn't change at all[^1]
Running SELECT id, msats, "stackedMsats" FROM users WHERE id = 27 reveals that 90 sats went to anon's balance

[^1]: 5 sats go to territory founder as revenue since all subs in seed.sql have "rewardsPct" set to 50
Expected behavior
Rewards increased by 5 sats via fees and by 90 sats via anon's stack
Additional context
Reported by @0xbitcoiner here.

Blocked because we wait for #1195


text:
autogenerate rule_type references

Describe the bug
Just before the releases we've written the rule type references manually, but that doesn't scale. We need to autogenerate them.

We should automate the generation of rule_type documentation for the stacklok managed rules -- Luke had a start somewhere.

@ethomson -- this might be a fit for our beta quality bar

authors: evankanderson jhrozek

repo: stacklok/minder


text:
Deleted blog posts appear at the bottom of other posts

Even after deleting the demo blogs posts they do appear at the bottom of other blog posts.
I tried to clear the cache and deployed again but still no change. any solution for this ?

Can you share a link to your website and GitHub repo

Can you share a link to your website and GitHub repo

https://ruchir-blog.netlify.app/what-is-net-neutrality

authors: TheRuchirShah munawar-js

repo: stackrole/gatsby-starter-foundation


text:
Allow specifying instruction set

Description
Kernel supports few instruction sets [1], and the default one (which is
apparently being used at the moment in falco) is going to be the
generic or v1, which has certain limitations and requires
workarounds. It's possible to instruct llc to search the latest
supported instruction set via -mcpu parameter, which generally
speaking should result in more compact and potentially more performant
generated instructions for the same code. For the support table see
great blog post [2] about the topic. The gist for the support is:
v2: Linux v4.14 [3], LLVM v6.0 [4]
v3: Linux v5.1 [5], LLVM [6]
Probing is working via performing bpf syscall with various instruction
sets and figuring out maximum supported version based on the results.
Which means it would work only for the build host, so we need to allow
pinning it precisely if needed.
Checklist

[ ] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Testing Performed
Local testing with instruction set v2.

@erthalion Is this still relevant?

@robbycochran it is, in the sense that it still could be applied, but has to be evaluated again.

authors: erthalion robbycochran

repo: stackrox/collector


text:
ROX-22718: Sort Roles in Tokens

Sorting of roles
Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/ok-to-test

Hi @aaa5kameric,
thanks for your contribution, this issue has been bugging me for some time :). Could you please add a test for the service implementation that asserts the sorting in the list response? You can take inspiration from https://github.com/stackrox/stackrox/blob/a7ee107776bf374940c9dd7c1b691095caaa2b68/central/administration/events/service/service_impl_postgres_test.go to set up the test code.

/ok-to-test

pinging @stehessel

Once the checks are passing, you'll be able to hit that green "squash and merge" button 🥳

/retest

@stehessel do you know if it is expected that tests fails on external contributor forks? Looks like images are not pushed

/retest

@stehessel do you know if it is expected that tests fails on external contributor forks? Looks like images are not pushed

Yes believe that is intentional, see https://github.com/stackrox/stackrox/blob/master/.github/workflows/build.yaml#L388-L390.

Closing in favor of: https://github.com/stackrox/stackrox/pull/11614 because of CI failures

authors: GrimmiMeloni aaa5kameric ludydoo stehessel

repo: stackrox/stackrox


text:
ROX-17762: Delete non-postgres code in Reports UI

Description

deprecating our Postgres feature flag

Divide and conquer the residue of conditional code for Vulnerability Management.
I missed that this conditional code is related to collections in #6454
Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn lint in ui
yarn build in ui
yarn start in ui

Integration testing

yarn cypress-open in ui/apps/platform

vulnmanagement/reporting/reportingForm.test.js

/test ocp-4-12-ui-e2e-tests


text:
ROX-12982,ROX-21061,ROX-21062: Switch to stock SCCs

Description
This is part 1 of a stack of multiple PRs. This PR is only concerned with the initial SCCs in Helm templates.
Therefore, Operator-related tests are failing because of these changes. They are fixed in the next layered PR.
Switch from our custom SCCs to stock SCCs OpenShift ships with.
The table below lists all components and the planned changes for them.

Component
Custom SCC before
OpenShift 4 SCC
Reasoning

Sensor
stackrox-sensor
restricted-v2
Great!

Admission Controller
stackrox-admission-control
restricted-v2
Great!

Central
stackrox-central
restricted-v2
Great!

Central-db
stackrox-central-db
nonroot-v2
Image running as fixed uid:gid

Scanner
stackrox-scanner
nonroot-v2
Image running as fixed uid:gid

Scanner-db
stackrox-scanner
nonroot-v2
Image running as fixed uid:gid

Collector
stackrox-collector
privileged
Needs full access to Node

monitoring
stackrox-monitoring
nonroot-v2
Image running as fixed uid:gid

To Dos to get this PR ready to merge

[x] Helm deployable on OpenShift 4
[x] Update unit tests
[x] Update E2E tests

Follow-up PRs:

[ ] Implement changes in Operator
[ ] Update Operator upgrade tests
[ ] Add upgrade instructions for Manifest-based installations
[ ] Update teardown script in stackrox/workflows to clean up the new/changed resources

Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
I deployed on an OpenShift 4 cluster and ensured that all containers are running and StackRox is working as intended.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

@Maddosaurus regarding the table in the PR description - It looks good, but I would love to see a reason (if possible) for picking nonroot-v2 instead of restricted-v2.

/retest

/test ci/prow/gke-nongroovy-e2e-tests

I added the ci-all-qa-tests label

Current dependencies on/for this PR:

master

PR #8663   👈

PR #8766

This stack of pull requests is managed by Graphite.

@vikin91

Are all tests functional when we merge this?
AFAIK, the Operator ships embedded Helm charts, so that shouldn't break. That said, I don't know about newly compiled/dev versions of the Operator.

Would some installation method or CI be broken?
Likely the Operator E2E tests will stay broken until we update either the tests or better, the Operator.

That said, we could merge this PR as-is, as it results in a running Helm deployment, but I'd prefer to merge it together with the follow-up.
On the other hand, it's a run against time, as multiple people are currently working on the Helm charts.

@vikin91

Are all tests functional when we merge this?
AFAIK, the Operator ships embedded Helm charts, so that shouldn't break. That said, I don't know about newly compiled/dev versions of the Operator.

Would some installation method or CI be broken?
Likely the Operator E2E tests will stay broken until we update either the tests or better, the Operator.

That said, we could merge this PR as-is, as it results in a running Helm deployment, but I'd prefer to merge it together with the follow-up. On the other hand, it's a run against time, as multiple people are currently working on the Helm charts.

If it breaks CI for master (more than it is broken now), then I would say: wait. If not, then you can merge it.


text:
🛑 STAKR.space site is down

In bd146d6, STAKR.space site (https://stakr.space) was down:

HTTP code: 0
Response time: 0 ms

Resolved: STAKR.space site is back up in 46e5063 after 11 minutes.

repo: stakrspace/upptime


text:
🛑 Proxima/DNS Server is down

In 1543e3f, Proxima/DNS Server (http://proxima01.its-telekom.eu/livewatch.php) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Proxima/DNS Server is back up in 6d96042.

repo: stamateas/upptime


text:
⚠ GitLab Server has degraded performance

In c677b8d, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11536 ms

Resolved: GitLab Server performance has improved in 182e29a.


text:
Update README.md

Submisison Checklist

[ ] Run tests: ./runCmdStanTests.py src/test
[ ] Declare copyright holder and open-source license: see below

Summary:
Intended Effect:
How to Verify:
Side Effects:
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

the README.md file lists the interfaces in the stan-dev repo.
the page: https://mc-stan.org/users/interfaces/
lists the julia interface, among others.

authors: mitzimorris odechant

repo: stan-dev/cmdstan


text:
Added initial variadic ODE design doc draft (design-doc #19)

Rendered version here
There's a bit of code here that has implemented most of this design: https://github.com/stan-dev/math/pull/1641

@wds15, @yizhang-yiz, @charlesm93, @bob-carpenter -- whoever wants to comment or review, have at it. I'd like to get something like this through in the release 3 months from now.

Really cool to see that much action from you on this! I will take a deep dive on this soon.

@wds15 I'm bored and haven't coded stuff in a long time. Gimme something to do.

Sorry for the long delay...
Do we have benchmarks new vs old stuff?

Do we have benchmarks new vs old stuff?

I do not. I'm just assuming this interface can be fast enough, and then we can check it before it merges that it indeed is.

Eek, was there something that you wanted me to write up here (said something about it in the meeting)?
I just started writing code. I guess things I've done are:

Converted to doing state as an Eigen::VectorXd
Written a bunch of docs and added more tests
Fixed the t0 issue again (hopefully for good this time)
And now I've started adding in the adjoint stuff in, which isn't really part of this design doc, but I'm doing it in the ODE thread. We might break that up into separate things -- I kinda just saw the opportunity and started.

I was expecting to hear back so that we start exploring those additional tolerance control things for example. We still need to decide on what options to control in addition of any.
Btw, as we seem to switch to general template arguments you can do that here now as well which will probably make the code more memory efficient since some copies can be avoided, I think.

I was expecting to hear back so that we start exploring those additional tolerance control things for example

Oh yeah, working through the interface now. We'll go back and forth on that once I get a baseline up.

Just as a note: The just released sundial 5.3 includes in the release notes: "Our latest release, v5.3.0, adds support to CVODE for integrating IVPs with contstraints and projecting the solution onto the constraint manifold"
Sounds cool.
https://computing.llnl.gov/projects/sundials/sundials-software
totally not for this design per se, but could be a consideration should we want to move into this direction in the future.

Oh interesting. That could be an easier way to handle positivity constraints.
But then we couldn't easily expose that functionality to the other solvers.

I think the basic code and such is in place to evaluate this and start wrapping everything up.
There are three outstanding questions I know of (it's possible more get added in the course of review), but let me tag some people and see if we can get these out of the way.
The writeup is here.

We should decide on default tolerances. The docs are inconsistent now anyway. Currently CVODES solvers run at rtol = 1e-10, atol = 1e-10 and the RK45 solver runs at rtol = 1e-6, atol = 1e-6.

We need to decide on the error control for CVODES (whether or not to include sensitivity variables in error control, see here)

Naming. I originally did short names like ode_bdf for convenience. @wds15 likes integrate_ode_bdf_2 (details). Either one will do. What seems better from a user perspective?

@wds15 @charlesm93 @yizhang-yiz @bob-carpenter

Is it an option to drop for the new interfaces the functions which set default tolerances? I do think that people should by all means set the tolerances.

I hope my benchmarks will be done next week and give some help to decide.

I am fine with short names. So ode_bdf is great for me...just like matlab

@wds15 let's keep default tolerances so-as to not rock the boat. I'll copy them over and fix the doc to reflect the difference if nobody has any other suggestions.
I also like the different names since the interface is changing slightly (vector initial conditions + tolerances in different places). The new solvers aren't just a drop in substitute for the old solvers (though that is handled via the backwards compatibility integrate_ode_bdf etc. interfaces here).

I've done BDF/Adams defaults as rtol = 1e-10, atol = 1e-10 and RK45 solver defaults at rtol = 1e-6, atol = 1e-6.

I've configured CVODES (BDF/Adams) to adjust timestep based on tolerance requirements of the sensitivity equations.

Short names are good.

@wds15 did everything but the promotion. We have answers for all the unanswered questions, so I just cleaned those up.

Should we now approve/merge this? Everything proposed here now lives in Stan, as of 2.24

I would suggest to merge, yes.

@wds15 want to approve? You have done most of the reviewing.

I just approved once more. Not sure why this is still roadblocked.

You seem to not have approving rights (gray tick on approval), let me try.

Someone with proper permissions will have to do it.

maintainers only have read access.  people with write access are BB, Carp, Steve Bronder, and D Lee.  an odd set of folks.  Steve might have been given write access in order to manage the CoC issue which isn't really a design doc.
choices:  grant write access to all maintainers; get approval from BB, Steve, Daniel, or Bob.

repo: stan-dev/design-docs


text:
If i want use eslint-plugin-react-hooks, is it necessary to use standardx？

I want to config  standard  for eslint-plugin-react-hooks, but it doesn't work. So, i replace standard with standardx,like...
 "standardx": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ]
  },
  "eslintConfig": {
    "rules": {
      "react-hooks/rules-of-hooks": "error",
      "react-hooks/exhaustive-deps": "warn"
    }
  },

But, is it the only way?
And, vscode-standardjs can't give the warning about react hook, what should i do ?

I think i find the reason.
It' seem like StandardJS (the vscode plugin) can't read the standardx in package.json.
Will this problem be fixed?

Hello Junting
you were able to configure it ?

Hello Junting
you were able to configure it ?

maybe, you  need to see this issue at first. It seems like a bug of vscode-standardjs and  It seems can't be solved quickly。
There is my final config。 I have to use both vscode-standardjs and eslint extension in vscode，It means the real tips about hooks come from eslint。I think my config is not good，but i don't have any other better solutions right now.
  "standardx": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ]
  },
  "eslintConfig": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ],
    "rules": {
      "react-hooks/rules-of-hooks": "error",
      "react-hooks/exhaustive-deps": "warn"
    }
  },
  "standard": {
    "parser": "babel-eslint"
  },

@Junting-Liu This will be fixed once we release a new version of vscode-standardjs. Sorry that this hack is required in the meantime.

what about for Webstorm, how do I configure standardjs to use eslint-plugin-react-hooks?
Do I need to install eslint or have an .eslintrc file?
currently I just added react-hooks to my standard config in package.json with nothing happening:
  "standard": {
    "parser": "babel-eslint",
    "env": [
      "jest"
    ],
   // here/how do I specify rules for plugins in this config?
    "plugins": [
      "react-hooks"
    ]
  }

@orpheus, adding a plugin usually does not add the rules provided by that plugin to your list of rules that participate in linting.
Currently, customizing or adding rules in Standard is not supported. Please see #1356 and my proposal #703.
If these rules are important to you, you could quite easily replace standard with eslint and the eslint-config-standard package.
https://www.npmjs.com/package/eslint-config-standard
But then you need to know a little bit about how to use ESLint and configure rules and plugins and use the command line and you'd use an ESLint extension for you editor instead of a Standard extension.
ESLint's documentation is quite alright. Good luck.

authors: Junting-Liu feross jousmo mightyiam orpheus

repo: standard/standard


text:
Lint all JavaScript in markdown files by default

ESLint supports the notion of "processors" which allows us to extract JS from markdown files and lint it to ensure it is in standard style. https://eslint.org/docs/user-guide/configuring#specifying-processor
That would let us eliminate this whole section of the readme which describes how to install eslint-plugin-markdown, run standard with the --plugin flag. In the end you need to actually run standard twice if you do this: standard && standard --plugin markdown '**/*.md'
I think we can do better. Let's just do the right thing out of the box.
We should probably do the same for

Brilliant. I'd love that. Would probably break some projects.
Would that be supported merely by extending from eslint-config-standard or would it require the executable? I would prefer the former, if possible.

We'd put it directly in eslint-config-standard.

We should probably do the same for

I've seen and written code examples in READMEs that are not 100% correct, for example to quickly demonstrate two ways to achieve the same thing:
const x = doItOneWay()

// Alternatively:
const x = doItAnotherWay()

I guess standard would implicitly impose a rule to split such snippets? In this case, to not reassign x.

@vweevers Yeah, we'd certainly need to disable some of the rules for examples, like unused variables for example. I think we can look at what standard-markdown disables as a starting point: https://github.com/zeke/standard-markdown/blob/2f044f48eed5f7162147e7927b65a61387200341/lib/linter.js#L8-L15

I attempted to get this working for standard 16 but ran into issues. Help would be appreciated to figure it out!
Here's what I tried:
eslint-config-standard

Install eslint-plugin-markdown as a peer dep of eslint-config-standard (2.0.0-rc.0 was latest at the time)
Add "extends": ["plugin:markdown/recommended"] to the eslint.json file.

standard

Install eslint-plugin-markdown as a dep of eslint-config-standard
Add extensions: ['.md'] to eslintConfig in options.js:

observed behavior
  /Users/feross/code/standard/CHANGELOG.md:654:10: 'foo' is defined but never used. (no-unused-vars)

Rules like no-unused-vars are being enforced, which should be ignored for markdown files. From the docs for eslint-plugin-markdown:

Some rules that catch mistakes in regular code are less helpful in documentation. For example, no-undef would flag variables that are declared outside of a code snippet because they aren't relevant to the example. The plugin:markdown/recommended config disables these rules in Markdown files:

https://github.com/eslint/eslint-plugin-markdown#frequently-disabled-rules
Help appreciated!

bump. would like to see this land

authors: feross jimmywarting mightyiam vweevers


text:
Templates from Python string

Make loading a jinja2 template from a python string possible.

A simpler version would be something like this (doesn't need jinja2):
magic_number = 42

sys_prompt_str = "You are a helpful assistant"

prompt_str = f"""You are going to do the following:
- Say hi to the user first.
- then use the {magic_number}
"""

llm_generation_chain(system_prompt_text=sys_prompt_str, user_prompt_text=prompt_str)

Done in v0.2.0

authors: duskybomb s-jse

repo: stanford-oval/chainlite


text:
SchemaRetriever: another attempt at retrieving the right entity record

entities.json cannot be trusted for entities that are defined in
classes, if classes are overridden locally.

Pull Request Test Coverage Report for Build 1241

16 of 16 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 77.762%

Totals

Change from base Build 1240:
0.02%

Covered Lines:
10004

Relevant Lines:
12353

💛  - Coveralls

authors: coveralls gcampax

repo: stanford-oval/thingtalk


text:
utf-8 bug

in common.c file:
if (i == MAX_STRING_LENGTH - 1 && (word[i-1] & 0x80) == 0x80) {
if ((word[i-1] & 0xC0) == 0xC0) {
word[i-1] = '\0';
} else if (i > 2 && (word[i-2] & 0xE0) == 0xE0) {
word[i-2] = '\0';
} else if (i > 3 && (word[i-3] & 0xF8) == 0xF0) {
word[i-3] = '\0';
}
}
the modification as follows:
if (i == MAX_STRING_LENGTH - 1 && (word[i-1] & 0xC0) == 0x80) {  # test 10xx xxxx
if ((word[i-1] & 0xE0) == 0xC0) {   #test 110x xxxx
word[i-1] = '\0';
} else if (i > 2 && (word[i-2] & 0xF0) == 0xE0) {   # test 1110 xxxx
word[i-2] = '\0';
} else if (i > 3 && (word[i-3] & 0xF8) == 0xF0) {  # test 1111 0xxx
word[i-3] = '\0';
}
}

Want to make it a PR?
also, honestly, if you could explain where you found the bug, that would be great.  not many people here are that familiar with the codebase

Figured that out based on the bit masks.  Is the update better in terms of handling utf-8, though?

my modification has bugs.  let 's see your code :
if ((word[i-1] & 0xC0) == 0xC0) {
if word[i-1] startswith 110, 1110, 11110 and your code works well。 but in my code:
if ((word[i-1] & 0xE0) == 0xC0) {
it only matchs words which starts with 110, and will miss  1110, 11110.
thanks!!!

authors: AngledLuffa cicido

repo: stanfordnlp/GloVe


text:
Automate pypi deployment

WIP for automatically publishing package to pypi and creating github release. Testpypi automation in place for package at: https://test.pypi.org/project/dspy-ai-test/

Great job! Thank you for your time and contribution! Overall, this looks good to me, but here are a few suggestions:

It would be helpful to have a document explaining how we are building this. Including this document in the PR should be sufficient. While I have a general understanding of how it works currently, a short document connecting the dots would make it much easier to understand.

-> Shall I expand to what I've got here or is that enough detail? I also included a release-checklist.md  file which contains instructions for use and prereqs.

I've added a few comments which may help in cleaning up, but they aren't necessary.
Instead of copying the intro.py into the file, it might be better to move it to pytest and run it from there.

Great job! Thank you for your time and contribution! Overall, this looks good to me, but here are a few suggestions:

It would be helpful to have a document explaining how we are building this. Including this document in the PR should be sufficient. While I have a general understanding of how it works currently, a short document connecting the dots would make it much easier to understand.

-> Shall I expand what I've mentioned here or is that enough detail? I also included a release-checklist.md  file which contains instructions for use and prereqs.

I've added a few comments which may help in cleaning up, but they aren't necessary.
Instead of copying the intro.py into the file, it might be better to move it to pytest and run it from there.

@hmoazam I think that's a good draft but i would say

let's keep it somewhere in our repo as a document not a comment
let's add a little bit more detail like which part of the CI is doing what

All in all, great job!
Let's tweak it a little bit and merge it as soon as we can.

This PR depends on #1192 and #1048.
Once #1048 is merged in we need to:

Update the test-intro-script task to point to the pytest at tests_integration/test_intro.py instead of build_utils/tests/intro.py
Delete build_utils/tests/intro.py

authors: ammirsm hmoazam

repo: stanfordnlp/dspy


text:
panic: runtime error: invalid memory address or nil pointer dereference

me@host:~$ '/home/me/Downloads/go/bin/go' get  github.com/stapelberg/airscan/cmd/airscan1

me@host:~$ '/home/me/Downloads/go/bin/go' install github.com/stapelberg/airscan/cmd/airscan1

me@host:~$ ./go/bin/airscan1
2020/08/16 14:35:07 finding device for 5s (use -timeout=0 for unlimited)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x7111fa]

goroutine 1 [running]:
github.com/stapelberg/airscan.NewClientForService(0x0, 0x0)
	/home/me/go/src/github.com/stapelberg/airscan/airscan.go:333 +0x3a
main.(*airscanner).scan1(0xc0000de580, 0x0, 0x0)
	/home/me/go/src/github.com/stapelberg/airscan/cmd/airscan1/airscan1.go:173 +0x52
main.airscan1(0x0, 0x0)
	/home/me/go/src/github.com/stapelberg/airscan/cmd/airscan1/airscan1.go:155 +0x6e9
main.main()
	/home/me/go/src/github.com/stapelberg/airscan/cmd/airscan1/airscan1.go:238 +0x25

This is my printer (I do not know whether it should be supported): HP LaserJet 200 colorMFP M276n. It is being advertised with Zeroconf as  _scanner._tcp.

Is there an easy way to find out, from looking at the output of avahi-browse -ar, whether a scanner should be supported?

Found it:
https://github.com/stapelberg/airscan/blob/15a04490cd177b5b9b76c884b04b0b56b9201bee/airscan.go#L36
Unfortunately my printer does not publish that service.

repo: stapelberg/airscan


text:
Fix rust audit report error

https://circleci.com/gh/starcoinorg/stargate/51
ID:       RUSTSEC-2019-0004
Crate:    libp2p-core
Version:  0.7.0
Date:     2019-05-15
URL:      https://rustsec.org/advisories/RUSTSEC-2019-0004
Title:    Failure to properly verify ed25519 signatures makes any signature valid
Solution:  upgrade to ^0.7.1 OR >= 0.8.1
Dependency tree:
libp2p-core 0.7.0

Already fixed. close it.

authors: fikgol jolestar

repo: starcoinorg/stargate


text:
Some DX and testing quick fixes

What this PR does:

Made StargateServerError message include the command that failed, and store the command document that was sent
Fixed insertMany()
Implemented dropCollection()
Used dropCollection() to clean data in between tests. I was getting a lot of strange test failures locally because data wasn't being cleared.

Also @kathirsvn , what do you think about making deleteMany() throw an unimplemented error for now, until the server side implements it? It is a little error prone that deleteMany() is a no-op right now, leads to hard-to-debug test failures.
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

Thanks @vkarpov15 for the fixes/improvement with StargateServerError and insertMany. I updated the postman collection as well for insertMany now which I used for testing.
dropCollection - Thanks for that. I was about to implement that after testing sample netlify app yesterday.
deleteMany - Sure, we can make it throw 'unimplemented' error for now.
Also, I just started a discussion about my observations and fixes that I had to do, while testing and making the netlify sample app work. Could you please comment on the observations (especially points 3 & 4 about upsertOne and the projection field?)

@kathirsvn I didn't see your comments until just now. Looks like you ran into some of the same issues I did in #18. I'll leave some comments on #18, but please take a look at c84d2b6 and 1d08b1a.
The major difference is that I made find() and findOne() not take a projection param, rather relying on options.projection. That's the function signature that Mongoose expects from drivers, see find() and findOne()

Thanks @vkarpov15 for the details on find and findOne projection option. I proposed the same change in the src/driver/collection.ts as well. Apart from that this PR looks good. Can we merge this?

@kathirsvn yep this works. Want to merge this or should I?

I'm merging this now, thanks @vkarpov15

repo: stargate/stargate-mongoose


text:
updateColumn should allow altering type

In updateColumn for both v1 and v2 we are only renaming the column and ignoring the typeDefinition provided. Instead you should be able to rename or change the type of the column
Reference:

https://docs.datastax.com/en/cql-oss/3.3/cql/cql_using/useAlterColType.html

Changing types is dangerous and has been removed https://cassandra.apache.org/doc/latest/cql/changes.html#id2

@tjake so is the doc I linked to outdated?

Yeah

authors: dougwettlaufer tjake

repo: stargate/stargate


text:
Bind DSE JMX server to listen address

When specified, it binds JMX server to the listen address.
It looks like in C* it's not possible:

https://github.com/apache/cassandra/blob/9802a70f68cdcd239a9128f90f5d8f9a941168de/src/java/org/apache/cassandra/utils/JMXServerUtils.java#L82-L86
https://github.com/apache/cassandra/blob/9802a70f68cdcd239a9128f90f5d8f9a941168de/src/java/org/apache/cassandra/utils/JMXServerUtils.java#L261

Do we create JMX servers with C* persistence? I've never seen any JMX port conflicts with C* :thinking:

Do we create JMX servers with C* persistence?

Yeah, its in there :)
INFO  [main] 2020-10-01 15:04:52,818 CassandraPersistenceActivator.java:134 - Starting persistence-cassandra-3.11...
INFO  [main] 2020-10-01 15:04:52,952 AbstractCassandraPersistence.java:97 - Initializing Apache Cassandra
INFO  [main] 2020-10-01 15:04:52,965 DatabaseDescriptor.java:381 - DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
INFO  [main] 2020-10-01 15:04:52,966 DatabaseDescriptor.java:439 - Global memtable on-heap threshold is enabled at 14563MB
INFO  [main] 2020-10-01 15:04:52,966 DatabaseDescriptor.java:443 - Global memtable off-heap threshold is enabled at 14563MB
INFO  [main] 2020-10-01 15:04:53,059 RateBasedBackPressure.java:123 - Initialized back-pressure with high ratio: 0.9, factor: 5, flow: FAST, window size: 2000.
INFO  [main] 2020-10-01 15:04:53,059 DatabaseDescriptor.java:773 - Back-pressure is disabled with strategy null.
INFO  [main] 2020-10-01 15:04:53,097 JMXServerUtils.java:246 - Configured JMX server at: service:jmx:rmi://0.0.0.0/jndi/rmi://0.0.0.0:7199/jmxrmi

authors: dimas-b jorgebay


text:
增加多账户支持时更新出现问题

#8 重新推了版本，现在应该可以了

authors: Brianwind startkkkkkk


text:
Feedback: it didn't find my root INSTALL.md but subfolders' xyz.md ?!

Runme (or runme tui) was suggesting a myriad of commands from xyz_blabla.md (ie. not only README.md) in typescript/node apps down various folders, but not the top level INSTALL.MD

Thanks for the feedback @kopeboy.
We have the concept of named cells, and assume that if those are what exist that they are what folks are actually looking for. Any chance you could try: runme ls --allow-unnamed and let us know if you see what you're looking for there? Similarly runme --allow-unnamed should show all the commands in the TUI.
Also if you are willing to share the contents of INSTALL.md that would help.
We're on Discord if you have any interest in real-time convo! https://discord.gg/runme

Hi @kopeboy! Checking in. Did @admc's comments help you? And if not, would you be willing to share your INSTALL.md with us? We can do it via email or discord private message if you'd rather not share it on a public channel.

Hey @kopeboy,
As we haven't heard from you in a bit, we'll go ahead and close this issue. However, if you continue to have issues, please provide the details requested above and reopen this issue.
Thanks!

authors: admc joseeantonior kopeboy sourishkrout

repo: stateful/runme


text:
After "state" deprecation in ActorRefFrom, there is no easy way to get the type of an ActorRef

Description
Previously, when I needed a way to extract the context from an ActorRef of a generic machine, I could do something like this:
interface MyMachineActor<T> extends ActorRefFrom<MyMachine<T>> {}

// but now I get
// 'state' is depricated
const myMachineSelector<T, R>(selector: (state MyMachineActor<T>['state']) => R) { ... }

Expected Result
We probably can provide a utility type like:
type EmittedFrom<T> = T extends ActorRef<any, infer TEmitted>
  ? TEmitted
  : T extends Behavior<any, infer TEmitted>
  ? TEmitted
  : never

Used like this:
const myMachineSelector<T, R>(selector: (state EmittedFrom<MyMachineActor<T>>) => R) { ... }

Let me know what you think and if I should open a PR.
Thanks!

Let me know what you think and if I should open a PR.

Yes please! This would be a good addition (cc. @Andarist)

authors: VanTanev davidkpiano

repo: statelyai/xstate


text:
Review terminology

After reading the documentation, I realized that the "voting room" terminology was confusing so I moved away from it in favour of "proposal".
Also review some of the documentation

@Szymx95 What do you think? Does it make sense? Was there a strong reason for using a "voting room" name? (or is it something I asked?)

We decided to differentiate between polling and voting so 'voting room' kind of made sense if you like proposal more you can change it, I don't strong feelings about it

repo: status-im/wakuconnect-vote-poll-sdk


text:
[RFC]: refactor blas/ext/base/dsumpw to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/dsumpw to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter  I would Like to work upon this issue. Please assign it to me.

@Planeshifter @kgryte @Pranavchiku assign me this issue

authors: Planeshifter ShivamAhir rajutkarsh07

repo: stdlib-js/stdlib


text:
the window can't be moved if call this->winId() in the widget

If I add this line here the window can't be moved by dragging the title bar:

Window can't be moved if I drag the title bar:

Built by qt 5.15.10_msvc2019_64, this bug maybe happen in the Qt source code, who can help with this bug? Thanks.

This is a big problem, a frameless window will not receive WM_HITTEST if it has a native child window, I have been researching for a long time but now can't find a solution. If you really need to move an outside widget into the frameless window, you could wrap the widget with another frameless container.

Maybe the issue is fixed, I'll push very soon.

authors: SineStriker tinybug

repo: stdware/qwindowkit


text:
add prepare script to allow yarn/npm load from git

By adding a prepare stanza to the package.json scripts, this allows a consumer to specify the upstream by git URL and have it transpile properly.
{
  "name": "steem-program",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "@steemit/steem-js": "https://github.com/steemit/steem-js"
  }
}

More info available at https://github.com/npm/npm/issues/3055

lol CI fails because the test is using the network and the test account is bandwidth limited:

  1) steem.broadcast: comment with options works:
     RPCError: plugin exception:Account: guest123 has 966821953 RC, needs 1443846168 RC. Please wait to transact, or power up STEEM.rethrow
      at RPCError.Error (native)
      at new RPCError (src/api/transports/http.js:8:25)
      at src/api/transports/http.js:36:13
      at process._tickCallback (internal/process/next_tick.js:109:7)

repo: steemit/steem-js


text:
Error Creating default object from empty value

Hi Pak Steevenz,
Saya coba menggunakan package ini tp ketika saya test muncul error Creating default object from empty value. Adakah yang salah pak? Terimakasih.

Saya juga punya case yang sama

Hi Pak Steevenz,
Saya coba menggunakan package ini tp ketika saya test muncul error Creating default object from empty value. Adakah yang salah pak? Terimakasih.

authors: vinjerid yalinmuslem

repo: steevenz/id-payroll-calculator


text:
Server side rendering tutorial

how to accomplish what next.js accomplishes?
if website is requested first time - THEN send html with prerendered content
ELSE (if just going to other page using browser) THEN request server /api for more data and render new page on browser side

Sorrry, I don't understand the question. What is next.js?

framework that adds SSR to react https://github.com/vercel/next.js/
usually one writes
function MyPage() {
   const data = requestDataFromServerHook()
   return
....

}

but with this framework can write
function MyPage(dataFetchedFromApiOnServerSite) {
   return
....

}

MyPage.specialFunctionToFetchOnServerSide = ...

can try to make such framework if there is a HTML -> Text printer

There is an HTML to String rendering function, but I suggest you have a look at idris2-dom-mvc, which comes without the FRP complexity of idris2-rhone-js.

authors: srghma stefan-hoeck


text:
🛑 Teamkalender API is down

In 70380a2, Teamkalender API (https://niko.neuenhauser.de/api/tk/q/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Teamkalender API is back up in 6c07410 after 5 hours, 29 minutes.

repo: stefan-hoeltker-nextn/niko-uptime


text:
Still immutable error when using --force

As I understood #155 bumped github.com/fluxcd/pkg/ssa version which should have resolved resources not recreated when using --force arg. However I'm still facing the issue with some resources:
11:20AM ERR IAMServiceAccount/banst/opkg-registry dry-run failed: admission webhook "deny-immutable-field-updates.cnrm.cloud.google.com" denied the request: cannot make changes to immutable field(s): [spec.resourceID]; please refer to our troubleshooting doc: https://cloud.google.com/config-connector/docs/troubleshooting

Is there something we can do to catch that and recreate the resource when using --force or "action.timoni.sh/force": "enabled" annotation?
timoni version
api: timoni.sh/v1alpha1
client: 0.14.0
cue: 0.6.0

Yeah that error does not come from Kubernetes CEL but some GKE webhook and the error doesn't match the regex we use for CEL. https://github.com/fluxcd/pkg/blob/6dc2f174f41fb859afafc0d6f28d58d6a610e606/ssa/utils.go#L288C26-L288C26

Any chance we could check custom webhooks too or would that be too much work? I'm asking that totally out of context since I did not check the code. Sorry if that sounds dumb

Doing string matching on error messages is really bad, especially for something like force apply which has the potential to wipe your cluster clean if it matches something wrong. I could maybe expose this somehow in the SSA package and allow Timoni users to go YOLO with regexes while risking major incidents. How ofter do you run into this, is this an exception or your are changing immutable fields in GPC objects all the time?

Sooo, that's the thing with config connector. A ton of stuff is immutable and needs recreation of the resource (because the Google resource itself needs to be recreated). So to answer your question, yes this is something I run into way more often that I would like 😅. They even have immutable fields that should not be immutable (see https://github.com/GoogleCloudPlatform/k8s-config-connector/issues/670#issuecomment-1179301208 for example).

repo: stefanprodan/timoni


text:
Move of froide GitHub repo to facilitate further development

There is discussion to slightly repurpose Froide for different goals.
One goal could be a Personal Data request service (suggested by me), and another could be an IsItOpenData reboot (suggested by @rgrp).
The dynamics required have lots of commonality, putting the interaction with the entity holding data itself in the commons (after stripping some information due to privacy concerns). In the personal data case, the substance of the response should be treated with special care (and most likely not shown publicly), as it really is private data.
Codewise, it would make sense to implement some more modular system in Froide dictating the interaction. To support collaborative development towards this, I suggest the following moves:

https://github.com/stefanw/froide -> https://github.com/okfn/froide
https://github.com/okfde/froide-theme -> https://github.com/okfn/froide-theme

(this would help for access control, fundraising, visibility, code development, discussions around code development, etc)

Hi @pdehaye,
I'm all for making froide more modular and encourage more use. Moving this repo to a GitHub organisation is a good first step. However, I don't see any advantage moving repos to the okfn organisation over the okfde organisation, so I'm going to move them to the okfde organisation (simply because I'm an admin there).
I will add you as a collaborator on this repository. Let's discuss how to make froide more modular in there.

Great, thanks!

On 30 Nov 2016, at 19:43, Stefan Wehrmeyer notifications@github.com wrote:
Hi @pdehaye,
I'm all for making froide more modular and encourage more use. Moving this repo to a GitHub organisation is a good first step. However, I don't see any advantage moving repos to the okfn organisation over the okfde organisation, so I'm going to move them to the okfde organisation (simply because I'm an admin there).
I will add you as a collaborator on this repository. Let's discuss how to make froide more modular in there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Repository is moved, you have write access. Please contribute through PRs with a plan.
We don't necessarily need backward compatibility but we do need migration plans for existing instances running froide. So for any changes we should start a CHANGELOG etc.

😄  👏

authors: pdehaye rgrp stefanw

repo: stefanw/froide


text:
🛑 Teamkalender API is down

In 55e0929, Teamkalender API (https://niko.neuenhauser.de/api/tk/q/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Teamkalender API is back up in 9f74a4c after 10 hours, 22 minutes.

repo: stefanwendelmann/niko-uptime


text:
Add explanation to PureComponent Link context issue.

this.pureComponentLastPath can't be undefined even after previous set without explicit unmounting, because shouldComponentUpdate does not work correctly with this.context. It's React isssue. Nothing several, just some components are updated more often than needed.

https://github.com/gaearon/react-pure-render can be used where react-router context workaround isn't needed, aka for components without router Link.
import PureComponent from 'react-pure-render/component'

repo: steida/este


text:
SEP-9: Add cbu_alias and cbu_number fields to core and platform

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Adds cbu_number and cbu_alias to the SEP-9 fields supported by the core and platform packages.
Why
These fields were added to SEP-9

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Reference Server Preview is available here:https://anchor-ref-pr727.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr727.previews.kube001.services.stellar-ops.com/

authors: JakeUrban stellar-jenkins

repo: stellar/java-stellar-anchor-sdk


text:
Renamed Explore Endpoints to Endpoints

Renamed Explore Endpoints to Endpoints
Added yarn test to pre-push hook
Renamed View XDR to XDR in the main nav

Preview is available here:http://laboratory-pr813.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr813.previews.kube001.services.stellar-ops.com/

authors: quietbits stellar-jenkins

repo: stellar/laboratory