text:
Issue in get_attributes module in agouti_shred.py

Hi AGOUTI team,
let me start off by stating what an awesome program AGOUTI is, which exactly caters to my needs of recovering a fragmented genome assembly in my MSc-thesis. I'd be a little bit lost without it. A very minor issue i was encountering when shredding an assembly. As you may know annotators dump pretty much anything in the comment section, which is a problem for agouti.  It throws an error and exits, when its not in the =<attribute_name> format, which is not always the case (and was not in my case). In my case i fixed it by changing the get_attirbutes function to:
def get_attributes(attribute):
	dAttributes = {}
	tmp_attributes = attribute.split(';')
	for i in range(len(tmp_attributes)):
		tmp_attribute = tmp_attributes[i].split('=')
		if len( tmp_attribute) > 1:
			attributeName = tmp_attribute[0]
			attributeValue = tmp_attribute[1]
			if attributeName not in dAttributes:
				dAttributes[attributeName] = attributeValue

which is a very minor correction and simply gets rid of comments not in the desired format. It's not the best solution, but worked for me. Anyway, I just wanted to point out this very minor issue and thanks again for writing such an elegant program!
Best,
Nico

Hello Nico,
Thanks very much for using AGOUTI, and pointing out this potential problem!
Could you please give me a bit more info about your case, if you don't mind? For example, what annotator you were using? What does your "comment" section look like? I'd like to try to come up with a general solution so that everyone else won't have it.
Thanks again,
Simo

Hello Simo,
the problem arose using a gff pulled from the German cockroach genome project's ftp page:
ftp://ftp.hgsc.bcm.edu/I5K-pilot/German_cockroach/maker_annotation/version_0.5.3/
It was built using MAKER. I Don't know what the exact line is which is giving teh problem but if i do  		```
try:
attributeName = tmp_attribute[0]
attributeValue = tmp_attribute[1]
except:
print tmp_attribute
it prints
> ['']
so i guess somewhere there is an empty attibute passed to the get_attributes function, but i don't know where. Maybe there are empty lines. Sorry, I couldn't be of any more help, but maybe you can recreate the problem

Best,
Nico

Hi Nico,
These info are great. Let me play with it. I'll leave this issue open and get back to you.
Simo

Hi Nico,
I just made a patch. The error you saw was due to the semicolon at the end of attribute field in the GFF file. The fix can also bypass cases in which there were attributes with no {}={} type of format.
Thanks for bringing this up.
I close this for now. Let me know if you get further problems.
Simo

authors: bananenbongo svm-zhang

repo: svm-zhang/AGOUTI


text:
#branding

Love your blog!

lol nice gif

source: gharchive/pull-request

authors: sw-yx theianjones

repo: sw-yx/swyxdotio

license: MIT

license_type: permissive

license_source: github-api


text:
Add support for JAX-RS @BeanParam

Would it be possible to add support for the @BeanParam (https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/BeanParam.html) from JAX-RS? Same question as answered at http://stackoverflow.com/questions/19913046/does-swagger-support-the-jax-rs-beanparam-annotation, but didn't find an issue for it here.

Has anyone tried using Swagger Core 1.5.x and Swagger UI 2.0 using Jersey2 with no web.xml
It doesn't seem to recognize API annotations within BeanParam object and also the path param pattern doesn't get replaced such as /v1/report/{report_type:[aA-zZ]+} ..when executed on UI it uses the pattern as is

Hi @swarupe04 It is definitely supported.  Please take a look at this sample:
https://github.com/swagger-api/swagger-core/tree/develop_2.0/samples/java-jaxrs-no-webxml
It is a jaxrs 1.x sample but the spirit is the same.  All configuration for swagger is done in the Bootstrap.java.

Hi Tony,
It seems to be the UI side, that doesn't seem to support it. Since I can
see api documentation in the swagger.json.
Since, by using swagger 2.0 forma, we're forced to move to the new UI.
Also,  I noticed that new UI 2.0 doesn't have the "raw" link anymore.
Is master the latest for UI work, or do u think I should instead using
develop_2.0 for swagger ui too, to get the latest UI modules.
Thanks
On Wed, Mar 18, 2015 at 6:15 PM, Tony Tam notifications@github.com wrote:

Hi @swarupe04 https://github.com/swarupe04 It is definitely supported.
Please take a look at this sample:
https://github.com/swagger-api/swagger-core/tree/develop_2.0/samples/java-jaxrs-no-webxml
It is a jaxrs 1.x sample but the spirit is the same. All configuration for
swagger is done in the Bootstrap.java.
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/446#issuecomment-83205159
.

Master should be fine. Can you share the bean property?  Email is fine if its private

Please can you provide the email id to send to.
Thanks,
Swarup
On Wed, Mar 18, 2015 at 9:05 PM, Tony Tam notifications@github.com wrote:

Master should be fine. Can you share the bean property? Email is fine if
its private
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/446#issuecomment-83242191
.

Tony@swagger.io

sent to your gmail..please let me know if you need more info..
also wanted to mention about the swagger.json out too
base class to support all types of Report Requests:
{

required:
[

"active_campaigns",
"date_range",
"report_type",
"time_unit",
"view_level"
],

for bean class
@ApiModel(value = "base class to support all types of Report Requests")
public class ReportRequest {
shouldn't it using the class name instead?
On Wed, Mar 18, 2015 at 9:30 PM, Swarup Eda swarup.eda@teamaol.com wrote:

Please can you provide the email id to send to.
Thanks,
Swarup
On Wed, Mar 18, 2015 at 9:05 PM, Tony Tam notifications@github.com
wrote:

Master should be fine. Can you share the bean property? Email is fine if
its private
—
Reply to this email directly or view it on GitHub
https://github.com/swagger-api/swagger-core/issues/446#issuecomment-83242191
.

source: gharchive/issue

authors: fehguy joscarsson swarupe04

repo: swagger-api/swagger-core


text:
Parameters in DefaultReaderConfig

Hi,
We should do improvements:
ignore.routes should not depend on scan.all.resources parameter
We want to use this parameter to ignore some routes. However, it depends on scan.all.resources. We should not have this dependency.
Support new param path.from.declaration
We wouldn't like to use value in @Path - javax.ws.rs.Path because we have nice URLs with rewrite engine. So we want to use value from @Api - io.swagger.annotations.Api. For flexibility, we should support new parameter to indicate this.

@kiennguyen - thank you, but that changes the meaning of @Api#value() which was changed in 1.5 (check the javadocs). I don't think it's wise to give the value a double meaning for the same framework (i.e., JAX-RS).

Per @webron 's comments, we cannot change the meaning for @Api#value()

authors: fehguy kiennguyen webron


text:
Please add documentation outlining the steps required to add Swagger to an existing project

Looks like Swagger at the moment supports the following frameworks:

connect
express
hapi
restify
sails

It would be great if there was documentation showing how we can add swagger to existing projects.

I agree. I'm having serious issues trying to do it.

+1

Is this even pissible with this npm module?

It is possible, certainly: Swagger-Node just relies on the standard frameworks (eg. connect). But moving any particular project to swagger-node would depend on the specific framework being used and what your expectations are for the resulting application. I don't know that this can be answered well in the abstract.

I just "swaggerized"  my existing express app; it was a bit frustrating, especially given that I had not previously used Swagger.  It came down to a few "simple" steps:

install swagger (obviously) via npm install -g swagger
create a swagger app via swagger project create hello-world.  Bear with me here - you'll just use some of the files from hello-world to bootstrap your node project
manually create /api/swagger and api/controller paths in your existing node app
copy config/default.yaml from hello-world to the /config path in your node project
copy api/swagger/swagger.yaml from hello-world to the /api/swagger path.
At this point, you should be able to use 'swagger project edit' to start defining your node endpoints in Swagger.  Unfortunately, I haven't found anything out there that turns a response from a node endpoint into a swagger definition, but that's not to say it doesn't exist.  On the upside, there are quite a few examples out there.
Tip: I wasted a LOT of time trying to externalize the definitions: in swagger.yaml.  It is possible, but it ain't easy, and it ain't pretty.  Until there is better support for this (or you have a dedicated dev team), I highly recommend just keeping it all in swagger.yaml and focus on turning your node route logic into controller snippets.
create your controller code and place the files in api/controller.  You can look in the hello-world api/controllers/ path for examples.
That will get you to the point where you can use swagger project run

Hey! I agree that this is a problem. @JacquesPerrault 's description is the best thing I've found so far. Is there not a way to automatically generate definitions given a pre-existing API? Should I be annotating my code? I can't seem to find any useful annotations for Javascript. Any help is much appreciated!

@brunerson These definitions might provide you with a good starting point.
A few notes:

I take advantage of the x-swagger-router-controller: parameter to give my controller filenames more intuitive naming
It took me a little while for figure it out, but getreposResponse: is a good example of how to include an array of objects in a response
getreposResponse: is just one example of where I needed to define the response as 'type: string', even though it is really an object, in order to support a JSONP response.

+1
Having an official manual on adding Swagger support to an existing node.js RESTful service with arbitrary layout would be very helpful.

+1

+1
Just some instructions that detail how to set the paths to your own controllers would be nice.

@codercurtis does this help?

There is also a very interesting way of modularizing it documented here
I found the article was just slightly out of date, but if you look at his repo (referenced in the blog) it is current.  I have a working version that I can post to a git repo if you need an example.

+1

authors: JacquesPerrault behrangsa brunerson chainlink codercurtis harindaka hpsharon mariofts theganyo timur-perelmutov zphingphong

repo: swagger-api/swagger-node


text:
cannot find type definition: sql.NullInt64

Describe the bug
We wrap the sql.Null* types from Go standard library in our own null types so we can override JSON marsha/unmarshal.
Example:
// NullString is a wrapper around sql.NullString that provides proper json.Marshal
type NullString sql.NullString

// NullInt64 is a wrapper around sql.NullInt64 that provides proper json.Marshal
type NullInt64 sql.NullInt64

// NullInt32 is a wrapper around sql.NullInt32 that provides proper json.Marshal
type NullInt32 sql.NullInt32

When I upgraded from swag v1.6.7 to v1.7.0 this started happening when generating docs:
2021/02/08 11:04:31 Generating types.NullInt64
2021/02/08 11:04:31 ParseComment error in file internal/api/v1/routers/foobar/tx.go :cannot find type definition: sql.NullInt64
make: *** [swagger] Error 1

With version v1.6.7 the CLI would not error out but occasionally I would get an error in the web site complaining about not have a definition for those types.  Now the tool is broken it seems.
To Reproduce
Steps to reproduce the behavior:

Define types like above.
Define a struct that uses it like this:

type Foo struct {
   ID NullInt64 `json:'id"
}

Create a quick route that uses the type Foo
Generate docs and see error

Expected behavior
I expect it to understand the type sql.NullInt64 since it is defined in the standard library.
Screenshots
Your swag version
1.7.0
Your go version
1.15.7
Desktop (please complete the following information):

OS: [e.g. iOS] Mac OS
Browser: [e.g. chrome, safari] Brave
Version: [e.g. 22]

Additional context
Add any other context about the problem here.

swag --parseDependency [your other params if any] should do the trick. This super-secret param is actually documented here.

Thanks for the tip.  Unfortunately, this is not resolving the issue for me.  If I don't add --parseDepth 5 it chews up my CPU and eventually fails with it complaining it can't find an internal type (which has not failed before).  If I do add --parseDepth it again fails to resolve the go standard library sql.NullString type.

Resolved with https://github.com/swaggo/swag/issues/817#issuecomment-730962356

I had same issue with v1.7.1. None of the flags worked, maybe because we use vendor, not sure. I found a workaround by annotating structh wtih swaggertype:"string" which worked fine.

swag init --parseDependency github.com/volatiletech/null/v8

This worked for me. for null string

authors: davisford roppa smitpatelx ubogdan

repo: swaggo/swag


text:
Update quote.py

Modify sentence
Short description of what this resolves:
Changes proposed in this pull request:
-Modify sentence

Fixes: #

Thank you for taking the time to contribute! This is sincerely appreciated. 😇
(Powered by GitMate.io)

authors: limmiok swapagarwal

repo: swapagarwal/JARVIS-on-Messenger

license: mit

license_source: bigquery


text:
Buttons of Drum Kit are not visible on small screens.

Which pre-existing JavaScript project will you be working on?
I'll be working on Drum Kit project under GSSoC'24
Describe your enhancement/improvement
On minimizing the screen size the width of the buttons is not decreasing in equal manner and the corner buttons are getting hidden.
Like here 'A' is hidden even though the scroll bar is at leftmost side.
Current page

This could be corrected by wrapping the buttons and fixing the width in this way
Enhanced Page

Anything you need to say to the Reviewers
Please assign this issue to me under GSSoC'24.

@bhumii-ka All the best 👍🏻

authors: bhumii-ka swapnilsparsh


text:
username v-alignment

the username seems to be too high

Is it better now or still an issue?

authors: michelleplur vojtechsimetka

repo: swarmcity/boardwalk-ts


text:
Rendering broken on X11 since recent changes

Hi,
I'm trying to run the latest git master + Wayfire git master and getting the following errors:
EE 17-12-20 12:57:25.913 - [backend/x11/backend.c:602] X11 error: op 149:7, code 11, sequence 32, value 109051908
EE 17-12-20 12:57:25.964 - [render/swapchain.c:97] No free output buffer slot

Everything works when reverting to 16a51bbab27ba5fa9348f21cfabff3085e25fc99
Notes: I'm on Ubuntu 18.04 and have to revert commits dd69c5871cbfd00b88309fcff8a159f9bb515510 and 1100c509c253bab72a0b51879d23558305e8723a to build; I understand if this might be an issue, but opening this since the problem does not seem directly related.
I'm attaching the full log (note: the error about no matching mode in line 56 appears in a working build as well)
swapchain_error.log

Can you try building with xcb-errors? This would make it easier to debug these X11 errors.
What X11 driver are you using? I've tested with the modesetting driver on amdgpu.

Hi,
with xcb-errors, I get the following errors:
EE 17-12-20 21:17:57.746 - [backend/x11/backend.c:592] X11 error: op DRI3 (PixmapFromBuffers), code Alloc (no extension), sequence 62, value 52428804
EE 17-12-20 21:17:57.746 - [backend/x11/backend.c:592] X11 error: op Present (Pixmap), code Pixmap (no extension), sequence 64, value 52428805
EE 17-12-20 21:17:57.746 - [backend/x11/backend.c:592] X11 error: op DRI3 (PixmapFromBuffers), code Alloc (no extension), sequence 65, value 52428804
EE 17-12-20 21:17:57.746 - [backend/x11/backend.c:592] X11 error: op Present (Pixmap), code Pixmap (no extension), sequence 67, value 52428807
EE 17-12-20 21:17:57.764 - [backend/x11/backend.c:592] X11 error: op DRI3 (PixmapFromBuffers), code Alloc (no extension), sequence 72, value 52428804
EE 17-12-20 21:17:57.764 - [backend/x11/backend.c:592] X11 error: op Present (Pixmap), code Pixmap (no extension), sequence 74, value 52428809
EE 17-12-20 21:17:57.783 - [backend/x11/backend.c:592] X11 error: op DRI3 (PixmapFromBuffers), code Alloc (no extension), sequence 75, value 52428804
EE 17-12-20 21:17:57.783 - [backend/x11/backend.c:592] X11 error: op Present (Pixmap), code Pixmap (no extension), sequence 77, value 52428811

After this, the No free output buffer slot keeps repeating until I kill the process, and there is no output.
As far as I can, the X11 driver is modesetting, with the i965 DRI2 driver. DRI3 is loaded, but I see no messages related to it in my Xorg.log -- I'm attaching it here, in case there's something useful in it.
Xorg.0.log

Can you try https://github.com/swaywm/wlroots/pull/2553?

Just tried and it's working with #2553 . Thanks!

authors: dkondor emersion

repo: swaywm/wlroots


text:
xdg-shell: introduce wlr_xdg_surface_state

This is preliminary work for properly handling cached state in
xdg-shell.
cc @vyivel

Ah, I added it myself already :D
Also, the state should probably have configure serial as well.

I've updated this PR to just cherry-pick @vyivel's commit from https://github.com/swaywm/wlroots/pull/3107. Also added a small description of the change in the commit message.

Could you please update this to have wlr_xdg_surface.current as well? surface_commit_state() can be inlined.

Done!

authors: emersion vyivel


text:
Better format to select tags

Can we have a better format to select tags?  The current scrolling list makes it difficult to see which tags are selected when in 'edit' mode.

This could be fixed by just making the box resizable.  Then the user can make it bigger if they wanted to see the whole list at once.

@maneesha we can perhaps make all widgets for multiselection (such as tags) as long as the list of items so that all items are visible at once (ie. no resizing then), would that work?

Yes.

This probably requires some JS magic to automatically set options.size to the number of items it contains.

User resizable or auto size -- what ever is easier.
Auto size might get unwieldy if we end up with fields that have many options - the widget could get really big.

I suggest we use buttons as checkboxes to select multiple tags. It is also responsive and works great with touch devices.
Demo

@narayanaditya95 this might be silly, but if I didn't know AMY internals and how to roll back from a backup, I'd be very afraid to click anything that resembles a button that I didn't click before ;)
From dev point of view, neither of demo'd widgets shows its function (radio or multiselection) clearly.

Yes, it may be tough to distinguish between the selected and the non-selected checkboxes.
What are your views regarding bootstrap-switch? They convey the purpose.

Any progress on this?  I think just having the box be resizable would meet my needs.

@maneesha, it's planned for v1.10 and we'll take care of that after releasing v1.9.
This can be easily solved by adding size="20" to the <select> widget. However, for some reason, this doesn't work:
    tag = django_filters.MultipleChoiceFilter(
        choices=TAG_CHOICES, name='tags', action=filter_tag_by_name,
        widget=SelectMultiple,
        attrs={'size': 10},
        # widget=SelectMultiple(attrs={'size': 10})  # does not work too
    )

authors: chrismedrela maneesha narayanaditya95 pbanaszkiewicz

repo: swcarpentry/amy


text:
Add back --readable-names flag

By default hygiene gives all bindings a new name with _<number> appended to it. In most cases you can just drop the unique suffix; it is only needed in cases where multiple bindings with the same name mix. In pre 1.0 the --readable-names flag did this.
Adding it back now is probably much easier with the Shift scope analyser.

This discussion has probably happened elsewhere but any reason not to make the --readable-names behavior the default instead and provide a flag to uniquify everything if they want that?

Ah good call. That's probably a better default.

+1

Doesn't seem to have been addressed. A "fix" which probably breaks things but works for me is in my branch https://github.com/gkovacs/sweet.js at https://github.com/gkovacs/sweet.js/commit/94f637476f0d8a74f37a5047491a3e55a9b4aec6

@gkovacs indeed that will avoid the renaming but hygiene is obviously broken now.

yes I mean obviously the system should optimally check to see if a rename is required and only rename if necessary. none of my macros declare new variables so it seems to work for my purposes.

authors: bearnshaw disnet gkovacs jayphelps


text:
[PubGrub] Narrow down cases when pre-release decisions are marked invalid

Pre-release decisions are valid if the derived range they were inferred from supports pre-release versions.
Motivation:
Currently, after deriving a pre-release assignment, the solver would assert
in some circumstances depending on order in which the dependencies are
specified in the manifest.
This change makes it possible to infer pre-release verison of a package
even when intermediate derivations did not support pre-release versions.
For example one package could declare swift-syntax dependency as
508.0.1 ..< 601.0.0 and another could narrow it to 600.0.0-latest ..< 601.0.0.
Since the most constrained range in such case supports pre-releases a decision
to use the lastest pre-release version of 600.0.0 should be valid if there
is no 600.0.0 release yet.
It's important to note that on each path a decision for a package is always
made based on the last undecided term's requirements which means -
based on the current semantics - if such derivation doesn't support pre-release,
even though intermediate ones did, the solver would select a released version.
This PR is not aim to change that.
There is a caveat which we cannot narrowly fix - if package depends on an exact
pre-release version the inference is going to fail when there is another dependency
to the same package that doesn't support pre-releases. For example:
Package A depends on packages B and C as follows:
A depends on B = 0.0.1-alpha and C = 1.0.0
B version 0.0.1-alpha has no dependencies
C version 1.0.0 depends on B - 0.0.1 ..< 0.0.2
In this situation the solver would fail because 0.0.1-alpha does not satisfy range - 0.0.1 ..< 0.0.2 inferred from C.
Modifications:

Delays version decisions for packages with pre-release ranges until there are no more packages without pre-release versions. This also means that if a previous decision narrows down the range to releases-only the package would be made a contender on the next step of the solver.

Relaxes the isValidDecision check for pre-release decisions but makes sure that the last derivation supports pre-release versions.

Result:
In situations like https://github.com/swiftlang/swift-package-manager/issues/7658 and https://github.com/swiftlang/swift-package-manager/issues/7643 the solver would no longer assert and would produce a solution with a pre-release version for swift-syntax.

@swift-ci test

@swift-ci please test

@swift-ci please test Windows platform

authors: MaxDesiatov xedin

repo: swiftlang/swift-package-manager


text:
[SR-1358] Improved FindICU.cmake for more systems and static linking

Previous ID
SR-1358

Radar
None

Original Reporter
ewmailing (JIRA User)

Type
Improvement

Additional Detail from JIRA

Votes
0

Component/s

Labels
Improvement, Android, CMake, ICU, Linux

Assignee
None

Priority
Medium

md5: 57487fce257e295f9be5f65704802b72

Issue Description:
This patch modifies FindICU.cmake and a few other files to support more systems and more configurations.
The existing ICU infrastructure was insufficient for multiple things.

It relied on pkg-config, which is problematic on systems that don't
ship pkg-config (e.g. Ubuntu 12.04, Windows?)

It didn't allow an easy way for specifying alternative locations for ICU
which is needed if you need to supply a non-system installed version.
This form is also useful when you want to supply a static library
version. (I will be submitting related issues about Android and SteamOS.)

It didn't handle linking when ICU was a static library. (libicudata is
needed)

pkg-config also doesn't handle libicudata

pkg-config also can present problems for cross-compiling. (Android was
also taken into account for this patch.)

This change fixes all these problems so Swift can be built on systems
like SteamOS/Steam-Runtime which don't supply libICU (and is based on
Ubuntu 12.04 which lacks a pkg-config). This allows you to supply
some other libICU which is a static library, and the Swift build system
will do the right thing. (It does not force static linking. So if you want static linking, only provide the static library.)
An explicit setting of ICU_ROOT (cmake -DICU_ROOT=/path/to/icu_root) or
setting an environmental variable called ICU_ROOT will allow alternative
paths to be searched.
I do want to point out that there is a popular FindICU.cmake floating out there that already handles this stuff and is pretty mature. I’m wondering a bit why you rewrote this from scratch considering ICU is a non-trivial library to deal with.
My patch is here:
https://github.com/ewmailing/swift/commit/f9cbb94148ae9d5d34e2313e129491d79ea8eb29

The toolchain now ships with swiftlang/swift-foundation-icu, so unless you're still seeing any issues with that, closing this.

authors: finagolfin swift-ci

repo: swiftlang/swift


text:
IRGen: Omit property descriptors from #_hasSymbol checks for static properties

Property descriptors for static properties were only recently introduced with SE-438. Since these symbols are not present in Swift libraries that were compiled with earlier versions of the compiler, it is not safe for #_hasSymbol to check for the property descriptor symbols, since they can be absent at either link time or runtime.
Resolves rdar://139749275.

@swift-ci please smoke test


text:
Create separate Build All Release task

We were naively transforming the arguments of the returned Build All task to create one that would run a release version of Build All. Unfortunately the task.execution remained the same and so while upon inspection the task looked like it would run a release build it was not.
Create two separate versions of the Build All task, one for Debug and one for Release builds, and use the release version when building tests in release mode.

Are you saying even though it is printing -c release to the terminal it isn't running a release build

@adam-fowler correct, we print the task’s description which isn’t necessarily what is executed. What runs, in this case, is determined by the tasks execution which is a SwiftExecution with its own set of args. If you check the terminal panel after running a test in release mode you see a build all has run, but without -c release.

Verified

I'm not a great fan of this. It creates a release build all task which virtually nobody needs and is only needed for running tests in release. Do we need to include the release task in the list of tasks returned by the task provider?

@adam-fowler https://github.com/swiftlang/vscode-swift/pull/1005 should address that

authors: adam-fowler award999 plemarquand

repo: swiftlang/vscode-swift


text:
The site documentation is unavailable

Both the link in the repository readme and the «documentation» link on the site point to a 404 error page.

https://swiftmailer.symfony.com/ works for me

@Rotzbua Yes, the site works but there is a 404 error instead of the documentation on the site.

valkeru@valkeru-supcomp:~ [0 ✓] $ curl -IL https://swiftmailer.symfony.com/docs/introduction.html
HTTP/1.1 404 Not Found
Cache-Control: no-cache
Content-Type: text/html; charset=UTF-8
Date: Sun, 08 Oct 2017 05:09:41 GMT
X-Correlation-Id: hbyuyvx3djoiqv4zh6o3znlb
X-Sensiocloud-Cache: MISS
X-Sensiocloud-Cluster: ism4mega7wpx6-master-7rqtwti
X-Sensiocloud-Processor: ji7dtgjzh7xkw425ntkt5sr6me
X-Sensiocloud-Router: oaeikbbkwwyxwl3vacgi6sviqy

As alternative:
Use the source of the website: https://github.com/swiftmailer/swiftmailer/tree/master/doc
Or for older versions the waybackmachine: https://archive.org/web/

fixed now

authors: FinesseRus Rotzbua Valkeru fabpot

repo: swiftmailer/swiftmailer


text:
yii\base\UnknownPropertyException

Exception (Unknown Property) 'yii\base\UnknownPropertyException' with message 'Setting unknown property: yii\swiftmailer\Mailer::0'
in D:\USR\www\basic\vendor\yiisoft\yii2\base\Component.php:197
Stack trace:
#0 D:\USR\www\basic\vendor\yiisoft\yii2\BaseYii.php(518): yii\base\Component->__set('0', Array)
#1 D:\USR\www\basic\vendor\yiisoft\yii2\base\Object.php(105): yii\BaseYii::configure(Object(yii\swiftmailer\Mailer), Array)
#2 [internal function]: yii\base\Object->__construct(Array)
#3 D:\USR\www\basic\vendor\yiisoft\yii2\di\Container.php(372): ReflectionClass->newInstanceArgs(Array)
#4 D:\USR\www\basic\vendor\yiisoft\yii2\di\Container.php(151): yii\di\Container->build('yii\swiftmailer...', Array, Array)
#5 D:\USR\www\basic\vendor\yiisoft\yii2\BaseYii.php(344): yii\di\Container->get('yii\swiftmailer...', Array, Array)
#6 D:\USR\www\basic\vendor\yiisoft\yii2\di\ServiceLocator.php(133): yii\BaseYii::createObject(Array)
#7 D:\USR\www\basic\vendor\yiisoft\yii2\di\ServiceLocator.php(71): yii\di\ServiceLocator->get('mailer')
#8 D:\USR\www\basic\controllers\TestController.php(11): yii\di\ServiceLocator->__get('mailer')
#9 [internal function]: app\controllers\TestController->actionLala()
#10 D:\USR\www\basic\vendor\yiisoft\yii2\base\InlineAction.php(55): call_user_func_array(Array, Array)
#11 D:\USR\www\basic\vendor\yiisoft\yii2\base\Controller.php(151): yii\base\InlineAction->runWithParams(Array)
#12 D:\USR\www\basic\vendor\yiisoft\yii2\base\Module.php(455): yii\base\Controller->runAction('lala', Array)
#13 D:\USR\www\basic\vendor\yiisoft\yii2\web\Application.php(84): yii\base\Module->runAction('test/lala', Array)
#14 D:\USR\www\basic\vendor\yiisoft\yii2\base\Application.php(375): yii\web\Application->handleRequest(Object(yii\web\Request))
#15 D:\USR\www\basic\web\index.php(12): yii\base\Application->run()
#16 {main}
web.php:inside components:
'mailer' => [
[
'class' => 'yii\swiftmailer\Mailer',
'viewPath' => '@app/mail',
'useFileTransport' => false, //I tried true too
'transport' => [
'class' => 'Swift_SmtpTransport',
'host' => 'smtp.gmail.com',
'username' => 'ibondariev@gmail.com',
'password' => '***',
'port' => '587',
'encryption' => 'tls',
],
],
],
and in controller:
\Yii::$app->mailer->compose()
->setFrom('ibondariev@gmail.com')
->setTo('bondsasha@ua.fm')
->setSubject('This is a test mail')
->send();
any ideas.what is wrong?

This is totally unrelated to swiftmailer.


text:
🛑 BestQA_GO is down

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

HTTP code: 500
Response time: 1208 ms

Resolved: BestQA_GO is back up in 5013e47.

repo: swuecho/upptime


text:
🛑 BestQA_GO is down

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

HTTP code: 0
Response time: 0 ms

Resolved: BestQA_GO is back up in ed03388.


text:
🛑 BestQA_GO is down

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

HTTP code: 0
Response time: 0 ms

Resolved: BestQA_GO is back up in f84760a after 10 minutes.


text:
🛑 BestQA is down

In 6b2bdf5, BestQA ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BestQA is back up in 0050c74.


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

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

HTTP code: 0
Response time: 0 ms

Resolved: 雙龍體育社區community is back up in 086be97.

repo: sxadxsx/upptime


text:
[Bug] Initialize Importer Emulator Selection

Igic02 — Today at 4:08 PM
Looks like a prior bug has been re-introduced.  When I go to import my tables, I have to select VPX, even though it's the only emulator listed in the software.

Fixed with 3.7.2.


text:
Add an Interval timer mode

The workout plan is really useful but I also see another usage: an interval timer. In this mode, you have must configure an exercise duration and a rest duration and that's it. When you start the timer it countdown the exercise duration then the rest duration and start again like this video: https://www.youtube.com/watch?v=w_5VVI8esPU&t=1883s but in a configurable way.
Thanks for your app by the way. I did something a bit similar: https://work-move.netlify.app/ I haven't publish the code source yet but may be one day.

I agree, I found it painful sometimes to set a lot of exercises/break sequences. It could definitely be useful, but I won't have the time in the near future to implement that.
Congrats for your Pomodoro btw. 👍

authors: jrmi sylvaindubus

repo: sylvaindubus/workout-chrono


text:
🛑 Alpha Landscaping is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Alpha Landscaping is back up in 8fb33ae after 40 minutes.

repo: symapex/upsite


text:
🛑 Superior Surface is down

In 7c856ae, Superior Surface (https://superior-surface.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Superior Surface is back up in 4d56968 after 53 minutes.


text:
🛑 Earth Works Lawn Cares is down

In a7e43db, Earth Works Lawn Cares (https://earthworkslawncares.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Earth Works Lawn Cares is back up in afce89e after 12 minutes.


text:
🛑 Everlast Deck is down

In c6df269, Everlast Deck (https://everlastdeck.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Everlast Deck is back up in 04991ed after 34 minutes.


text:
🛑 Get Fence Lab is down

In 6a7dfa7, Get Fence Lab (https://getfencelab.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Get Fence Lab is back up in a733924 after 45 minutes.


text:
🛑 Rigid Ground Work is down

In b435787, Rigid Ground Work (https://rigidgroundwork.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rigid Ground Work is back up in eca065b after 43 minutes.


text:
🛑 Real Time Digital Kansas is down

In bd15a14, Real Time Digital Kansas (https://realtimedigitalkansas.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Real Time Digital Kansas is back up in a00b78f.


text:
🛑 Pestero Bug Fortworth is down

In e7a9016, Pestero Bug Fortworth (https://pesterobugfortworth.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pestero Bug Fortworth is back up in c95a63a after 1 hour, 11 minutes.


text:
🛑 Clean Wise is down

In 1076749, Clean Wise (https://cleanwisenv.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Clean Wise is back up in 28d5f7b after 10 minutes.


text:
🛑 Scrub Clean Seattle is down

In e328560, Scrub Clean Seattle (https://scrubcleanseattle.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scrub Clean Seattle is back up in cffd089 after 16 minutes.


text:
🛑 Scrub Clean Seattle is down

In ae07820, Scrub Clean Seattle (https://scrubcleanseattle.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scrub Clean Seattle is back up in 973ca7d after 59 minutes.


text:
🛑 Sprint Fence is down

In 96011c1, Sprint Fence (https://sprintfence.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sprint Fence is back up in 2dd0d5c after 10 minutes.


text:
🛑 Brickyard Fence is down

In 53599c7, Brickyard Fence (https://brickyardfence.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Brickyard Fence is back up in fc9175a after 37 minutes.


text:
🛑 Dragues Well Repair is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Dragues Well Repair is back up in f4f7954 after 25 minutes.


text:
🛑 Boon Wood Flooring is down

In 1f21c6a, Boon Wood Flooring (https://boonwoodflooring.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Boon Wood Flooring is back up in de95e1e after 39 minutes.


text:
🛑 Get Fence Lab is down

In 4437b46, Get Fence Lab (https://getfencelab.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Get Fence Lab is back up in e93f16f after 10 minutes.


text:
🛑 Fresh Auto is down

In f68bf48, Fresh Auto (https://fresh-auto.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fresh Auto is back up in 6404662 after 11 minutes.


text:
🛑 Bitztream is down

In f819343, Bitztream (https://bitztreamnc.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bitztream is back up in 33a0cc4.


text:
fix #133 XSS injection (with Htmlpurifier)

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets
#133

License
MIT

Doc
PR

@stof , thanks for fast response. your comments applied ;)

@stof , sorry for disturbing. pull request is updated due to all your notes :)

Thanks for working on this feature @e-moe

Given you don't use the bundle anymore, you should configure HtmlPurifier to write its cache inside the Symfony cache (where we are sure we can write)

ok, I'll try to create one more pull request to fix HtmlPurifier  cache

authors: e-moe javiereguiluz stof

repo: symfony/symfony-demo


text:
Ensure default Post sort order shows newer Posts first

In at least #223 the topic of sorting on the admin backend was mentioned. This is the first time I've loaded the demo app in quite awhile and wasn't sure it was working because I didn't realize the new post I had added was going to show up at the bottom of the list. It may not be a problem for everyone but the bottom of the list on my laptop was well past the fold.
I appreciate that we do not need to make this admin backend fully completed with pagination and column-by-column sorting and what-not. However, I think it would make sense to have newer posts showing up at the top.

I think that's the simplest solution 👍

@simensen thanks! I like this feature and the solution was very simlpe at the end.

authors: bocharsky-bw javiereguiluz simensen


text:
Console should not accept an empty --env option

Now, if you try to run bin/console --env, it throws an exception:
[InvalidArgumentException]
The file "/path/to/app/app/config/config_.yml" does not exist.

Also I think it would be great to add a checking to the Kernel constructor. Now the Kernel accepts '' as a value for the environment. See https://github.com/symfony/http-kernel/blob/master/Kernel.php#L78

Passing an empty env option should probably fail instead of silently defaulting to dev.

I'm :-1: for this change, this should be resolved in the kernel itself, but I think it can introduce BC breaks...

authors: Pierstoval jvasseur voronkovich

repo: symfony/symfony-standard


text:
[Live Component] The User cannot be retrieved from a component extending AbstractController

I encountered this bug because I needed to retrieve the currently authenticated User from within a Live Component extending AbstractController. The first time, it works like a charm, but the second time, it doesn't. Here's my code and a detailed explanation:
<?php

namespace App\Twig\Components;

use App\Entity\Post;
use App\Entity\User;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
use Symfony\UX\LiveComponent\Attribute\AsLiveComponent;
use Symfony\UX\LiveComponent\Attribute\LiveAction;
use Symfony\UX\LiveComponent\Attribute\LiveArg;
use Symfony\UX\LiveComponent\Attribute\LiveProp;
use Symfony\UX\LiveComponent\DefaultActionTrait;

#[AsLiveComponent]
class Posts extends AbstractController
{
    use DefaultActionTrait;

    private ?User $user = null;

    #[LiveProp]
    public Posts_DisplayTab_Enum $displayTab = Posts_DisplayTab_Enum::POSTS_LATEST;

    public function __construct(
        private readonly PostRepository $postRepository,
    ) {}

    #[LiveAction]
    public function setDisplayTab(#[LiveArg] Posts_DisplayTab_Enum $tabName): void
    {
        $this->displayTab = $tabName;
    }

    public function getData(): array
    {
        // This works the first time. When setDisplayTab() is called from within the component, inside the
        // function getUser() the line $this->container->get('security.token_storage')->getToken() returns null.
        $this->user = $this->getUser();

        $data = match ($this->displayTab) {
            Posts_DisplayTab_Enum::RECORDS_PENDING => $this->getTabPending(),
            default => $this->getTabLatest(),
        };

        return $data;
    }

    private function getTabLatest(): array
    {
        return $this->postRepository->getLatestPosts($this->user);
    }

    private function getTabPending(): array
    {
        return $this->postRepository->getPendingPosts($this->user);
    }
}

            <button
                    class="nav-link {{ displayTab.value is same as 'latest' ? 'active' : '' }}"
                    type="button"
                    role="tab"
                    data-action="live#action"
                    data-action-name="setDisplayTab(tabName=latest)"
            >
                Latest
            </button>
            <button
                    class="nav-link {{ displayTab.value is same as 'pending' ? 'active' : '' }}"
                    type="button"
                    role="tab"
                    data-action="live#action"
                    data-action-name="setDisplayTab(tabName=pending)"
            >
                Pending
            </button>

Liste of the {{ this.data|length }} latest posts

                    {% for post in this.data %}

Post n°{{ post.id }} - {{ post.title }}

                    {% endfor %}

I also tried to not extend AbstractController but rather inject the service Symfony\Bundle\SecurityBundle\Security in the constructor, but I encountered the same error. The second time the component loads, when setDisplayTab() is called from within the component, inside the function getUser() the line $this->container->get('security.token_storage')->getToken() returns null.
It does not see; to be linked to my configuration or my firewall.

Maybe you need to customize the live component URL to have it covered with the same firewall you use for the initial rendering https://symfony.com/bundles/ux-live-component/current/index.html#define-another-route-for-your-component

@1ed Yea, that's an excellent idea & thing to check.
Unrelated, I'd recommend removing the user property and calling $this->getUser() each time you need the user: there's no real overhead to calling that method multiple times and would make the component a bit less fragile.

Made a small test and could not figure the problem.
The best way i think for you would be to inject the User in the LiveAction  (just tested, it works)
#[AsLiveComponent]
class FooBar
{
    use DefaultActionTrait;

    #[LiveProp]
    public string $message = 'Hello who ?';

    #[LiveAction]
    public function foo()
    {
        $this->message = 'Hello Foo!';
    }

    #[LiveAction]
    public function bar(#[CurrentUser] ?UserInterface $user = null)
    {
        $this->message = sprintf('Hello %s', $user?->getUserIdentifier() ?? 'XXX');
    }
}

Thanks @1ed, it worked!
Thanks for the recommendation @weaverryan, I will apply it.
I tried @smnandre solution, and it did not work for me. Maybe this attribute (that I did not know about, thank you for that!) is not available to me because of my firewall configuration. I'm using multiple firewalls, as you can see:
#config/packages/security.yaml

security:
    password_hashers:
        Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface: 'auto'
    providers:
        back_user_provider:
            entity:
                class: App\Entity\Security\Back\BackUser
                property: email
        app_user_provider:
            entity:
                class: App\Entity\Security\App\AppUser
                property: email
        all_users:
            chain:
                providers: ['back_user_provider', 'app_user_provider']

    firewalls:
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false
        back:
            pattern: ^/back
            provider: back_user_provider
            form_login:
                login_path: back_login
                check_path: back_login
                default_target_path: back_index
            logout:
                path: back_logout
                target: back_login
        app:
            pattern: ^/app
            provider: app_user_provider
            form_login:
                login_path: app_login
                check_path: app_login
                default_target_path: app_index
            logout:
                path: app_logout
                target: app_login

And so it's easier using them, I'm using the following config and file structure:
#config/routes.yaml
anonymous:
    resource: ../src/Controller/Anonymous/
    type: attribute
    prefix: '/'
    name_prefix: 'anonymous_'
app:
    resource: ../src/Controller/App/
    type: attribute
    prefix: '/app'
    name_prefix: 'app_'
back:
    resource: ../src/Controller/Back/
    type: attribute
    prefix: '/back'
    name_prefix: 'back_'
api:
    resource: ../src/Controller/Api/
    type: attribute
    prefix: '/api'
    name_prefix: 'api_'
#And so on

src
├──Controller
│   ├── Anonymous
│   │   ├── ...
│   ├── App
│   │   ├── ...
│   ├── Back
│   │   ├── ...

I wanted to follow the same directory structure with my components:
src
├──Twig
│   ├── Controllers
│   │   ├── Anonymous
│   │   │   ├── ...
│   │   ├── App
│   │   │   ├── ...
│   │   ├── Back
│   │   │   ├── ...

Do you think this is achievable, so I wouldn't rely on specifying the route property of AsLiveComponent each time?

If getUser() gives back a correct user then #[CurrentUser] should too, but if you have FrameworkExtraBundle then #[CurrentUser] will not work.
https://github.com/symfony/symfony/issues/40333

The CurrentUser attribute currently does not work if your user is also a Doctrine entity and you have FrameworkExtraBundle's param converters enabled.

Do you think this is achievable, so I wouldn't rely on specifying the route property of AsLiveComponent each time?

The default route used by live components is something you import in your app - https://github.com/symfony/recipes/blob/main/symfony/ux-live-component/2.6/config/routes/ux_live_component.yaml - you could change that prefix to something like /back/_components assuming that you only use live components on the backend. If you also use on the frontend, then have 2 routes: one that starts with /back and the other for /app. But since only one of these routes can be called the default ux_live_component route, you will need to specify the route to point to the other for all components being used in that context.
Cheers!

authors: 1ed Narthall smnandre weaverryan

repo: symfony/ux


text:
Electron-325 (Removed restriction from opening a popup from another popup window)

Description
Removed restriction from opening a popup from another popup window ELECTRON-325
Approach
How does this change address the problem?
Problem with the code:

The previous implementation was restricted to popup a window only from the main window.

Fix:

Removed the restriction which validates and creates the pop-out window

Before

After

Spectron test results
Test Results — Spectron.pdf
Unit test results
Test Results — Unit Tests.pdf
Learning

N/A

Blog Posts

N/A

Open Questions if any and Todos

[X] Unit-Tests (N/A)
[x] Documentation
[X] Automation-Tests
When solved, check the box and explain the answer.

@VikasShashidhar & @VishwasShashidhar Please review. Thanks 😄

@KiranNiranjan Have you made the changes that @VikasShashidhar has requested? If so, please let me know and I'll merge this PR.

@VishwasShashidhar & @VikasShashidhar I've made all the required changes. Please review. Thanks 😄

@VikasShashidhar Please approve so I can merge the changes.

authors: KiranNiranjan VishwasShashidhar

repo: symphonyoss/SymphonyElectron


text:
Allow adding more matrix properties

Currently I run this hack to build a matrix of all my packages with php-versions 7.4 and 8.0.
Would be cool if this was supported by the monorepo-builder?
   -   id: set-matrix
                run: echo "::set-output name=matrix::$(vendor/bin/monorepo-builder packages-json | sed 's/.$/,"php_version":["7.4", "8.0"]}/')"
        outputs:
            matrix: ${{ steps.set-matrix.outputs.matrix }}

@TomasVotruba  Great that https://github.com/symplify/symplify/pull/2592 is merged. It returns an array with versions ['7.4', '8.0'] that can be added to a matrix like this:
matrix
  php: ${{ steps.php-output }}

Now the only thing left, is to change the packages-json command also return an array with packages, instead of returning {"package_path": ['one', 'two']}
Because then, I can combine the two:
matrix
  php: ${{ steps.php-output }}
  package: ${{ steps.package-output }}

I've just read your comment... pushed this 2 hours ago https://github.com/symplify/symplify/pull/2594
We're synced :)

authors: TomasVotruba ruudk

repo: symplify/symplify


text:
[EasyCodingStandardTester] Add missing dependency

Error : Class 'Symplify\PhpConfigPrinter\HttpKernel\PhpConfigPrinterKernel' not found
 /app/vendor/symplify/package-builder/src/Testing/AbstractKernelTestCase.php:104

Maybe the Kernel class is wrong

Then what's the correct one? :sweat_smile:

I see, it's a nested kernel to dump the config, all right then :)

Thanks :+1:

What you're testing?

A custom (app-specific) fixer. ^^

:+1:  What does it do?

I use value objects with public properties and @psalm-immutable annotation. The fixer generates __construct using the typehints and annotations of the properties.

That's nice one :+1:
I think AST would be maintainable technology here, but if you know tokens better, that's ok.

Yeah it was admittedly a pain to do with tokens. AST-based tech would be much better for it.

I took some time to create a demo in Rector. This is how it might look like:
https://github.com/rectorphp/rector/pull/6167/files#diff-648598e9be2f7e0b87e64718a9e3acd79dca67f6ebe7ae327dd924689dc33023

That's pretty neat! Maybe I should give Rector another chance and see where it explodes this time. :-D

authors: TomasVotruba enumag


text:
[ECS] Remove dependency on symfony/http-kernel

The symfony/http-kernel is a useful package to quickly bootstrap project using Symfony DI.
The disadvantage is that it will many heavy Symfony framework components

http-foundation
error-handler
var-dumper
cache
event-dispatcher

etc.
We only need to build Dependency Injection container. But unfortunately, there is no component that would only create container from configs. The Dependency Injection component is just a simple package for handling mostly service value object. The container itself is built unfortunately in http-kernel component.
Ideally the container-builder should be separated from http-kernel, that would be light and only build the container. Due to this heavy Symfony pull, all Symplify CLI packages are almost as heavey as any MVC framework application. Imagine PHPUnit using full symfony/symfony, that's not good.
As negative consequence, the downgrade process is slow, heavy and the download of simple ECS results in download of dozens unused Symfony components, just to make http-kernel happy.
To avoid this, this is an attempt to build the missing container-builder package, that only accepts:

extensions
compiler passes
configs paths

And returns compiled Container in the end. Will it work? :)

cc @matthiasnoback Hi Matthias, I had a struggle with too heavy Symfony, so I've decided to drop anything we don't need from Symfony to build the container. I think you might like this one.
Any feedback appreciated!
Also, if this work, it might get to Rector itself :)

It took a while to clean whole symplify dependency tree from symfony/http-kernel, but the results are here :) - 390 files
https://twitter.com/VotrubaT/status/1455104311478951936

How much ECS vendor lose weight?
phploc vendor before
Directories                                        504
Files                                             2326

Size
  Lines of Code (LOC)                           263771
  Comment Lines of Code (CLOC)                   91989 (34.87%)
  Non-Comment Lines of Code (NCLOC)             171782 (65.13%)
  Logical Lines of Code (LLOC)                   61606 (23.36%)

Classes                                         2056

phploc vendor after
Directories                                        436
Files                                             1974

Size
  Lines of Code (LOC)                           225756
  Comment Lines of Code (CLOC)                   78870 (34.94%)
  Non-Comment Lines of Code (NCLOC)             146886 (65.06%)
  Logical Lines of Code (LLOC)                   52923 (23.44%)

Classes                                         1768


text:
New discovery protocol over HTTPS

Maybe have a look-see here as well

Does this work?

Yeah :)

authors: AudriusButkevicius calmh

repo: syncthing/discosrv


text:
Bitkit accounting Ledger

A library for keeping track of all transactions, balances within Bitkit.
The aim is to have clarity on the current state of the users funds within Bitkit, and have a good idea where the funds are at all times.
Integrate a database

In my opinion key/value db is better.

Track all incoming and outgoings transactions

All transactions should have a unique identifier
Routing fees
On chain fees

Consolidation system (calculate current final balance)

Throw errors if numbers don't match up

Exportable for debugging

Logging. Passing a logger function as a constructor so it works with Bitkit's logger.

Lightning transactions

Sweeping
Channel opening/closing
Track user's node id

Transaction state tracking

Which block on chain tx is included in.

Multi currency support

We should expect to not only be used with bitcoin, but also tokens in the future too.

Multi account support

Assume that we will have many accounts.

Documented API and testable

We should be able to test the logic of this lib independently of bitkit
Bitkit various components need to pass data to this component.

[ ] Define API
[ ] Implement it
[ ] Design test
[ ] Integrate it into Bitkit

Happy enough with how this behaves. Closing.

repo: synonymdev/bitkit


text:
stripe-background and custom options

Hi,
I tried this highlighter before and can't attain full options and line stripes..Many many websites have all that in it.
See "syntax1.png" photo for what I'm mentioning:
https://drive.google.com/folderview?id=0B4ruhRenMo6kV0VqenphTE41R1k&usp=sharing
Any idea on how to implement/configure syntaxhighlighter for that?
Thanks & regards,
Zenith

The screenshot is from a different script. I think it might be a fork.

authors: alexgorbatchev zenithtekla

repo: syntaxhighlighter/syntaxhighlighter


text:
Add godef

This cribs a lot from the godocget, I'd like to get it cleaned up before merging but this works right now.

Great work, I appreciate you contributing to this bundle.
I went ahead and merged this because it's functional and I'm not too concerned about the minor repetition. Sometimes tools change so it's not always worth factoring out minor stuff. This should also get our git histories in order and make merges more straightforward.

Awesome! Appreciate the expedient merge.

The Go → Def action is bound to ⌘D and lack a scope selector of source.go.
This means using ⌘D to duplicate a file in the file browser now trigger this command.
/cc @Infininight

Changed. That's a nifty shortcut I didn't know about. Thanks!

@syscrusher That shortcut conflicts as well (Find Again), there aren't any free shortcuts using ⌘ actually. A shortcut that is in use for this sort of command is ⇧⌘D.

It's my opinion that godef is used quite a bit and should have a 2-key activation. Is there a Ctrl-{key} that could work?
Sent from my iPhone

On Sep 19, 2016, at 00:58, Michael Sheets notifications@github.com wrote:
@syscrusher That shortcut conflicts as well (Find Again), there aren't any free shortcuts using ⌘ actually. A shortcut that is in use for this sort of command is ⇧⌘D.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Also, would I be misunderstanding if it seems that just adding the scope selector should be enough to fix the duplicate file bug, allowing us to continue using ⌘D?
Sent from my iPhone

On Sep 19, 2016, at 07:48, shankga@gmail.com wrote:
It's my opinion that godef is used quite a bit and should have a 2-key activation. Is there a Ctrl-{key} that could work?
Sent from my iPhone

On Sep 19, 2016, at 00:58, Michael Sheets notifications@github.com wrote:
@syscrusher That shortcut conflicts as well (Find Again), there aren't any free shortcuts using ⌘ actually. A shortcut that is in use for this sort of command is ⇧⌘D.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Surprisingly no, every single command plus a letter shortcut is already taken. Adding the scope greatly reduces the issue, because it will only be active when a Go document is frontmost. But overriding the key isn't really desirable in this case because it breaks a basic function in the app with a completely different one. Overriding a built-in function can be good in some cases when you provide a better more custom version of a built-in command but this isn't the case here.

@taterbase Any preference for the final shortcut?

It sounds like  ⇧⌘D is available? That would be a good alternative.

What about Ctrl-] like in Vim?

⇧⌘D is available and already has a somewhat assigned meaning as “go to something” (in C and Ruby we use it to go to the file included/required, alternatively opening a dialog when not on such line).
The ⌃] will be very hard to reach on most European keyboard layouts.
@infininight Might be worth making some standard proxy items in the Source bundle so bundle items can use semantic classes and leave the key equivalent empty.

⇧⌘D is currently used by our "Open Package" command. It fits the common usage, but its package resolution abilities are limited and it has been on my radar to rewrite it.
Def fits most of the common usage, except opening a dialog if no identifier is selected. I will add that, remove Open Package, then use ⇧⌘D for this command.

authors: infininight msoap sorbits syscrusher taterbase


text:
fix: vector needs to mount the journal in order to ship systemd logs

Vector needs to mount the journal on the host so it can ship systemd logs.

bors r+

repo: systeminit/si


text:
cli: add popper pipeline to test the badge server

Popper pipeline to test that restful endpoints work as intended

@ivotron Can this be closed now??

repo: systemslab/popper


text:
ネームスペース付き変数への代入ができない問題を修正

Resolve #101

👍

authors: marihachi syuilo

repo: syuilo/aiscript


text:
Fix overlap of birthday label on datepicker

Summary

Fix #3696
Adds a new "title" slot that works like the expanded label.
This means birthday will always be expanded out with no animation, so it cannot overlap the date picker

Great! Thank you 🙏🙏🙏

authors: ibrokemypie syuilo

repo: syuilo/misskey


text:
The url property on share component doesn't seems to work

i put the url property and the components still goes for the window.location.href

This bug is confirmed and was fixed with an update to v0.3.0. Thanks.

authors: LorisTujiba szchenghuang

repo: szchenghuang/react-line-social


text:
Alignment Offset (Portal={true})

React/React-dom version: v18.2.0
React-Menu version: v4.0.0
Describe the bug
When setting Portal={true} and align='end' (could occur with the other values as well), the first time a menu is dropped down, there is a slight offset to the position of the menu; the position is accurate in subsequent attempts to drop down the menu. Happens with every menu in my app if those settings are set.
To Reproduce

Created a basic menu
Set align = 'end'
Set portal = {true}
Dropdown the menu once (offset), dropdown again (fixed)

Expected behavior
Code snippets/CodeSandbox examples/Screenshots
https://ibb.co/nDyp07X

Hello @danglez83 , your screen recording did demonstrate menu failed to align properly on the first drop down. However, I was not able to reproduce it on my end, neither in a sandbox example nor a nextJS project.
I'd appreciate it if you could provide a sandbox environment that can showcase the issue and help us investigate it.

Here you go @szhsin, hopefully this helps. I tried to pare my exterior code down as best I could. The issue appears to be when the height is set to 100% on a parent.
https://codesandbox.io/s/react-menu-starter-forked-lm2wp7?file=/src/App.js

Sorry @szhsin, accidentally closed the issue. Hopefully my sandbox helps!

Thanks @danglez83, your sandbox really helps! Will be looking into the issue.

Hi @danglez83,
I solved this issue by adding unmountOnClose prop to the Menu component. Let me know if it works for you. Zheng, I would like to understand why this worked and is it a hacky way?
Side note: Thanks for building this awesome lib <3 All Hail Open Source

Hi @danglez83, I solved this issue by adding unmountOnClose prop to the Menu component. Let me know if it works for you. Zheng, I would like to understand why this worked and is it a hacky way?
Side note: Thanks for building this awesome lib <3 All Hail Open Source

Just an FYI @sohamsshah, adding that prop to my app did not fix the issue, which kind of makes sense since this issue only happens on initial menu dropdown.

Hey folks, it turns out the issue was caused by a vertical scrollbar.
When a menu is to be positioned, we use two render passes. In the first pass menu is placed at a default position which in some cases might cause browser to display a scrollbar, for example, page has 100% height. Menu position is then calculated and repositioned in the second pass, taking into account the scrollbar width (15px on macOS). Now menu is positioned close to anchor and scrollbar is no longer needed for the page. This results in a 15px horizontal misalignment. All these steps are finished before browser repaints the screen so that we don't see the scrollbar in the end.
On the second dropdown, menu is already positioned close to anchor, thus browser doesn't create scrollbars as in the first dropdown.
I fixed the bug by giving menu a large negative position by default, which ensures a scrollbar is not created by the browser.
Again, thanks @danglez83 for bringing this issue to our attention.
To @sohamsshah

I solved this issue by adding unmountOnClose prop to the Menu component. Let me know if it works for you. Zheng, I would like to understand why this worked and is it a hacky way?

It didn't solve the issue but make the misalignment appear on every dropdown instead of only in the first one. When unmountOnClose prop is set, menu position is reset to the default position every time before being opened.

Fixed by v4.0.2

authors: danglez83 sohamsshah szhsin

repo: szhsin/react-menu


text:
Erase?

Is there any way to erase part of a line?  I'm trying to make it into a simple drawing program.

It depends on what you mean by "erase". You can paint over it, which would effectively erase it. Though, if you're talking about "undo" feature, then it's not possible at the moment. It only keeps the last few points in the memory and uses them to draw the next line.

OK thanks for the help

I'm closing it, but if you got any more questions or issues, feel free to reopen it.

Hi, I'd like to erase some previously painted lines, the lines are placed over a transparent background.. how to do that?
Cheers

(I have tried to change signaturePad.penColor = "transparent" at runtime, but it doesn't erase)

@giuliogatto Again, it depends on what you mean by "erase". It's possible now to do "undo" feature, by using #toData and #fromData methods. Let me know, if that's what you want.

Hi Szimek, thank you for the quick reply!!
Well what I'd like to implement is an 'eraser' feature: something that you can use to partially delete lines that are already been painted.. I hope I am explaining myself clearly.
For example: first the user would trace an 'X' on the screen, the he'd decide that he wants to delete/erase one of the 2 lines of the 'X'. To do so, he'd click onto an 'eraser' button. When the button is clicked the pen doesn't draw lines anymore, but remove the lines/pixels that that clicked.

I'm not sure if it's possible if you have a transparent background, though I'm not saying it's not. If the background was opaque, then it should be rather simple - just set pen color to be the same as background color and use it to draw over previously drawn lines.

Thank you, 'source-out' seems to be what I am looking for.. is there a way to implement it with your library?
Cheers

OK, done it by adding a public method like this:
// Public methods SignaturePad.prototype.eraser = function () {   var ctx = this._ctx;   ctx.globalCompositeOperation = 'destination-out'   console.log('eraser'); }

@giuliogatto Thanks! I've added links to 2 demos to README for future reference, one based on your code:

erase feature: https://jsfiddle.net/szimek/jq9cyzuc/
undo feature: https://jsfiddle.net/szimek/osenxvjc/

authors: alexiskattan giuliogatto szimek


text:
Feature/signature from text

Feature added to signature from a text string
Developer can now provide a text either may be from a text input or any other source to signature along with font style.

I don't think this should be part of signature_pad. We want to keep this library focused on drawing the signature.

authors: UziTech arunredhu


text:
added toBlob method

added toBlob method

You pass the canvas into signature_pad. Why not just call toBlob on that instead of having to do so through the signature_pad object?
This seems like unnecessary maintenance required by signature_pad if the API ever changes.

Ok good point, That‘s how i do it now.
I was seeing, that there is a toDataURL method and was thinking, no toBlob has been forgotten.

authors: UziTech qxsch


text:
Add configuration file

Configuration handling needs some love. We should standardize it so it can be easily editable and extensible. One of the propositions we discussed was to use a YAML file.
version: 1
selectedAccount: default
accounts:
  default:
    jiraName: somename
    accountId: 123
    token: 345
    config:
      settings:
        someFlag: true
        defaultRemainingEstimate: 1h
      aliases:
        sm: abc-123
        daily: abc-123
        lunch: abc-321
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
  jake:
    jiraName: somename
    accountId: 123
    token: 345
    config:
      settings:
        defaultRemainingEstimate: 1h
      aliases: []
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
config:
  settings:
    defaultRemainingEstimate: 0h
  aliases:
    sm: abc-123
    daily: abc-123
    lunch: abc-321
  attributes:
    _EXTERNALREF_: foo
    _COLOR_: green

While it would serve its purpose I'm not the biggest fan of the YAML format. I'd like us to consider TOML or HOCON which in my opinion have better syntaxes.

I modified some keys and my proposition is something like that:
version: 2
selectedAccount: default
accounts:
  default:
    jiraName: somename
    accountId: 123
    token: 345
    accountConfig:
      settings:
        someFlag: true
        defaultRemainingEstimate: 1h
      aliases:
        sm: abc-123
        daily: abc-123
        lunch: abc-321
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
  jake:
    jiraName: somename
    accountId: 123
    token: 345
    accountConfig:
      settings:
        defaultRemainingEstimate: 1h
      aliases: []
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
globalConfig:
  settings:
    defaultRemainingEstimate: 0h
  aliases:
    sm: abc-123
    daily: abc-123
    lunch: abc-321
  attributes:
    _EXTERNALREF_: foo
    _COLOR_: green

Also I started writing migration from old config file but for now I have some problems with parsing maps (for example aliases) to YAML.

authors: MiSikora szymonkozak

repo: szymonkozak/tempomat


text:
Multi select expanding while page loads

Hi,
We are having an issue where multi select is expanding on page load, until (and I'm guessing here) js finishes loading and being processed, then it it's displayed as expected.
Here is a screenshot of the example page doing this:

This was on Chrome for Windows, version 43.0
As I'm pretty sure I'm not the first person to run into this, is there a way to prevent this from happening that you know of?
Thanks!

You're guessing right. ;-)
The original select2-bootstrap-css (for Bootstrap 2) seemed to handle that issue with a class .select2 that you would apply to the original <select> element that Select2 would be instantiated on:
/**
 * This stops the quick flash when a native selectbox is shown and
 * then replaced by a select2 input when javascript kicks in. This can be
 * removed if javascript is not present
 */

select.select2 {
  height: 28px;
  visibility: hidden;
}

https://github.com/t0m/select2-bootstrap-css/blob/master/lib/select2-bootstrap.scss#L94-L103

Thanks!

authors: fk pedroreys


text:
Use python3.8 and add logging

Fixed comment from previous PR #1

Looks good, will verify tomorrow that it works and if so will approve

@bityob sorry, but can you fixe the Merge conflict (our fault not yours)

@AdamRussak  resolved conflicts

Verified.
Updated Dockerfile too with the renamed file name.
PR #3 didn't update the docker file
RUN echo 'export PATH="/opt/chromedriver-85.0.4183.87":$PATH' >> /root/.bashrc && chmod 777 /etc/Health_Statements.py

authors: AdamRussak bityob


text:
docs: Links to TRPC documentation in the TRPC section of create t3 docs are broken.

Provide environment information
N/A
Describe the bug
In the TRPC Section of the  Create T3 docs, all links to trpc.io are broken, and lead to a "not found page".
Reproduction repo
NA
To reproduce
N/A - issue is with live docs page.
Additional information
No response

Some are still not working. I make a PR here - https://github.com/t3-oss/create-t3-app/pull/1946
@literallyJoel  @juliusmarminge


text:
bug: Errors with clean T3 install

Provide environment information
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Memory: 5.50 GB / 15.89 GB
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
bun: 1.1.22 - ~.bun\bin\bun.EXE
"ct3aMetadata": {
"initVersion": "7.36.2"
}
Describe the bug

Create a completely fresh T3 app.
Fix invalid environment variables:

NEXTAUTH_SECRET="sample"
NEXTAUTH_URL="http://localhost:3000"

# Next Auth Discord Provider
DISCORD_CLIENT_ID="placeholder"
DISCORD_CLIENT_SECRET="placeholder"

Literally just open or refresh the localhost site in browser:

[TRPC] post.getLatest took 153ms to execute
A query that was dehydrated as pending ended up rejecting. [[["post","getLatest"],{"type":"query"}]]: TRPCError: UNAUTHORIZED; The error will be redacted in production builds
Error: redacted
at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) {
digest: '1184500366'
}
GET / 200 in 8406ms
⨯ Internal error: Error: redacted
at eval (./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31)
digest: "1184500366"
⨯ unhandledRejection: Error: redacted
at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) {
digest: '1184500366'
}
⨯ unhandledRejection: Error: redacted
at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) {
digest: '1184500366'
}
Reproduction repo
It's a fresh create t3-app@latest, with only the .env changed as described
To reproduce
◇  Will you be using TypeScript or JavaScript?
│  TypeScript
│
◇  Will you be using Tailwind CSS for styling?
│  Yes
│
◇  Would you like to use tRPC?
│  Yes
│
◇  What authentication provider would you like to use?
│  NextAuth.js
│
◇  What database ORM would you like to use?
│  None (I also tried with Prisma)
│
◇  Would you like to use Next.js App Router?
│  Yes
Additional information
I tried GPTing my way to a solution, but it was not helpful.

Provide environment information
System: OS: Windows 10 10.0.19045 CPU: (8) x64 Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Memory: 5.50 GB / 15.89 GB Binaries: Node: 20.10.0 - C:\Program Files\nodejs\node.EXE bun: 1.1.22 - ~.bun\bin\bun.EXE
"ct3aMetadata": { "initVersion": "7.36.2" }
Describe the bug
1. Create a completely fresh T3 app.

2. Fix invalid environment variables:

NEXTAUTH_SECRET="sample"
NEXTAUTH_URL="http://localhost:3000"

# Next Auth Discord Provider
DISCORD_CLIENT_ID="placeholder"
DISCORD_CLIENT_SECRET="placeholder"

3. Literally just open or refresh the localhost site in browser:

[TRPC] post.getLatest took 153ms to execute A query that was dehydrated as pending ended up rejecting. [[["post","getLatest"],{"type":"query"}]]: TRPCError: UNAUTHORIZED; The error will be redacted in production builds Error: redacted at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) { digest: '1184500366' } GET / 200 in 8406ms ⨯ Internal error: Error: redacted at eval (./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) digest: "1184500366" ⨯ unhandledRejection: Error: redacted at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) { digest: '1184500366' } ⨯ unhandledRejection: Error: redacted at eval (webpack-internal:///(rsc)/./node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) { digest: '1184500366' }
Reproduction repo
It's a fresh create t3-app@latest, with only the .env changed as described
To reproduce
◇ Will you be using TypeScript or JavaScript? │ TypeScript │ ◇ Will you be using Tailwind CSS for styling? │ Yes │ ◇ Would you like to use tRPC? │ Yes │ ◇ What authentication provider would you like to use? │ NextAuth.js │ ◇ What database ORM would you like to use? │ None (I also tried with Prisma) │ ◇ Would you like to use Next.js App Router? │ Yes
Additional information
I tried GPTing my way to a solution, but it was not helpful.

i have the same errors

I'm getting something very similar (fresh setup with tRPC, NextAuth, Drizzle)
[TRPC] post.hello took 373ms to execute
[TRPC] post.getLatest took 120ms to execute
A query that was dehydrated as pending ended up rejecting. [[["post","getLatest"],{"type":"query"}]]: TRPCError: RequestInit: duplex option is required when sending a body.; The error will be redacted in production builds
 ⨯ Internal error: Error: redacted
    at eval (./node_modules/.pnpm/@tanstack+query-core@5.51.21/node_modules/@tanstack/query-core/build/modern/hydration.js:37:31)
digest: "2433427594"
Error: redacted
    at eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@tanstack+query-core@5.51.21/node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) {
  digest: '2433427594'
}

I'm getting something very similar (fresh setup with tRPC, NextAuth, Drizzle)
[TRPC] post.hello took 373ms to execute
[TRPC] post.getLatest took 120ms to execute
A query that was dehydrated as pending ended up rejecting. [[["post","getLatest"],{"type":"query"}]]: TRPCError: RequestInit: duplex option is required when sending a body.; The error will be redacted in production builds
 ⨯ Internal error: Error: redacted
    at eval (./node_modules/.pnpm/@tanstack+query-core@5.51.21/node_modules/@tanstack/query-core/build/modern/hydration.js:37:31)
digest: "2433427594"
Error: redacted
    at eval (webpack-internal:///(rsc)/./node_modules/.pnpm/@tanstack+query-core@5.51.21/node_modules/@tanstack/query-core/build/modern/hydration.js:37:31) {
  digest: '2433427594'
}

I could fix my issue by re-creating the project via an older version of t3-app, in particular the 7.34.0.
I think that the issue is related to the changes introduced in the PR https://github.com/t3-oss/create-t3-app/pull/1932

Newly created 7.36.2
>> query  #1 post.getLatest  { input: undefined }
[TRPC] post.getLatest took 355ms to execute
❌ tRPC failed on post.getLatest: UNAUTHORIZED
 GET /api/trpc/post.getLatest?batch=1&input=%7B%220%22%3A%7B%22json%22%3Anull%2C%22meta%22%3A%7B%22values%22%3A%5B%22undefined%22%5D%7D%7D%7D 200 in 372ms
 << query  #1 post.getLatest  {
  input: undefined,
  result: TRPCClientError: UNAUTHORIZED
      at TRPCClientError.from (webpack-internal:///(ssr)/./node_modules/@trpc/client/dist/TRPCClientError.mjs:40:20)
      at eval (webpack-internal:///(ssr)/./node_modules/@trpc/client/dist/links/httpBatchStreamLink.mjs:125:106)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    meta: {
      response: Response {
        status: 200,
        statusText: 'OK',
        headers: Headers {
          vary: 'RSC, Next-Router-State-Tree, Next-Router-Prefetch, trpc-accept',
          'content-type': 'application/json',
          'transfer-encoding': 'chunked',
          date: 'Tue, 13 Aug 2024 18:40:43 GMT',
          connection: 'keep-alive',
          'keep-alive': 'timeout=5'
        },
        body: ReadableStream { locked: true, state: 'readable', supportsBYOB: true },
        bodyUsed: true,
        ok: true,
        redirected: false,
        type: 'basic',
        url: 'http://localhost:3000/api/trpc/post.getLatest?batch=1&input=%7B%220%22%3A%7B%22json%22%3Anull%2C%22meta%22%3A%7B%22values%22%3A%5B%22undefined%22%5D%7D%7D%7D'
      }
    },
    shape: { message: 'UNAUTHORIZED', code: -32001, data: [Object] },
    data: {
      code: 'UNAUTHORIZED',
      httpStatus: 401,
      stack: 'TRPCError: UNAUTHORIZED\n' +
        '    at eval (webpack-internal:///(rsc)/./src/server/api/trpc.ts:111:15)\n' +
        '    at callRecursive (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/procedureBuilder.mjs:160:38)\n' +
        '    at next (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/procedureBuilder.mjs:169:32)\n' +
        '    at eval (webpack-internal:///(rsc)/./src/server/api/trpc.ts:90:26)\n' +
        '    at async callRecursive (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/procedureBuilder.mjs:160:32)\n' +
        '    at async procedure (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/procedureBuilder.mjs:190:24)\n' +
        '    at async eval (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/http/resolveResponse.mjs:207:30)\n' +
        '    at async eval (webpack-internal:///(rsc)/./node_modules/@trpc/server/dist/unstable-core-do-not-import/http/resolveResponse.mjs:359:45)',
      path: 'post.getLatest',
      zodError: null
    },
    [cause]: undefined
  },
  elapsedMs: 388
}
 ⨯ Internal error: TRPCClientError: UNAUTHORIZED
    at TRPCClientError.from (./node_modules/@trpc/client/dist/TRPCClientError.mjs:40:20)
    at eval (./node_modules/@trpc/client/dist/links/httpBatchStreamLink.mjs:125:106)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
digest: "4169396856"
 GET / 500 in 1242ms

that worked for me too @Guria

can confirm adding await to line #11 of page.tsx inside the app folder; also worked for me to eliminate this error message. Will check back to see if there is any new information..

@eltonstewart @ryanhell Please don't treat it as long term fix.
Adding await here changes expected behaviour. General idea is just trigger getting result at early stage, but don't block page loading and return Suspense fallback.
This issue still requires investigation and proper long term fix. Personally I decided to bootstrap with 7.34 version.

Just had this exact same error and @Guria's temporary fix works for me.

@eltonstewart @ryanhell @NightClover-code @ScottyMaher @lorenzocorallo
can you share which DB adapter have you used? Drizzle or Prisma?

I'm using Drizzle with a Turso database

Hmm. With latest 7.37 I have this issue with Postgres + Prisma, and no issue with Postgres + Drizzle.

Ok, I've found the descrepancy.
One template use getLatest: protectedProcedure.query and another one getLatest: publicProcedure.query.
So proper solution is just either use publicProcedure for getLatest or do not await protectedVersion in signed out state.
I will prepare a fix for affected templates.

I have the same issue !

@electroheadfx just make prefetch conditional based on session. See #1969

Closed by https://github.com/t3-oss/create-t3-app/pull/1969

authors: Guria NightClover-code ScottyMaher electroheadfx eltonstewart juliusmarminge lorenzobandini lorenzocorallo ryanhell


text:
データベースを読むときにバグがある(パス周り)

>ap アリシア -n ch1
Traceback (most recent call last):
File "prompt.py", line 613, in
File "cmd.py", line 138, in cmdloop
File "cmd.py", line 217, in onecmd
File "prompt.py", line 51, in do_append
sqlite3.OperationalError: unable to open database file
[10124] Failed to execute script prompt
自分の環境ではでなかった。めうすさんの環境で発生した

パスが上手く取れてないから、exeの場所まで移動してから起動しないと、dbを見つけられない

パスをいい感じに取得したい

やった 毎度のことながらながたさんありがとう

直ってなかった。修正法はわかったのでやる

e28c8df6d016044f8854e16510e0f1f8f81799ba


text:
コマンドの省略について

【change】【append】などの長めのコマンドを，【ch】【ap】など2文字程度に省略して使用したい。

done


text:
Indicator and Strategy

Indicator: McGinley dynamic moving average (smoothing fuction)
Strategy: Directional probablity index (DPI)

@ta-oliver @Optimus-Q
We can possibly set the buy signal to be generated if the DPI Index is less than 20% instead of 10%, what are your thoughts about this?

@ta-oliver @Optimus-Q We can possibly set the buy signal to be generated if the DPI Index is less than 20% instead of 10%, what are your thoughts about this?

Sure we can do that, however, we can add max and minimum level as per user requirement like:
buy_level = 20, sell_level= 80 and user can change these settings according to their need.

repo: ta-oliver/infertrade


text:
Issues vom Treffen am Donnerstag 17.11.2016

[x] Fehler melden Seite: umbauen Links deutlicher, als Button / Github Issue als Button
[x] Fehler melden Seite:Fenster Read Only
[x] Fehler Bei Suche, wenn Straße nicht gefunden
[x] Schritt 3: Eigene anschrift ergänzen
[x] Schritt 4: "(hilfreich" weg
[x] Schritt 4: 2. Hacken setzen
[x] Schritt 4: Rückmeldung wenn keine E-Mail angegeben oder 2. Hacken entfernt: Das wir dann nicht in Kontakt treten können.
[x] Schritt 4: letzer Punkt mit Namen und Anschrift raus
[x] Schritt 5: uns als E-Mail anklickbar zur laeuft adresse
[x] Umlaute aus E-mail
[x] Schritt 5: E-Mail bestätigen erwähnen

sollte alles drinn sein


text:
Override edit button function

how to override default edit function in jsgrid?

Description lacks any details. What do you mean by "edit function"?  How would you like to override it?

i have button out of jsgrid with name Edit

when i checked checkbox on grid i want to get data of row for edit

how to do this?

Checkout Data Manipulation demo on the demo page.

repo: tabalinas/jsgrid


text:
LogShark command failing to publish workbook to tableau server

Hi All,
I am using LogShark to analyse the server logs generated. Installed it and configured it on windows.
Aware that Tableau does not provide any official support regarding LogShark
I am Using tableau server 2020.2.1 version and came to know from one of the tableau official article that REST API version supported by that version is 3.8
Trying to publish the workbooks (to the tableau server) which are generated as the outputs after running the LogShark on the ziplogs file, however got the error saying http error and found that the error is due to incompatible REST API version 2.8.
It is taking 2.8 version.. How to make it take the API version 3.8.
Have tried putting 3.8 version in the tableau server URL in the config json file of LogShark but no use, and noticed that 2.8 is getting appended as the suffix to 3.8 in the same URL when the command is run. Found that observation in the log file of the LogShark run. Please suggest the way forward
Thanks in advance
Surya

Hi,
Tableau Server 2020.2.1 supports REST API version 2.8 just fine, so the problem should be somewhere else. The first thing to check is usually the config: make sure that Url parameter only contains url of the server, without site or any other info (i.e. https://tableau.company.com/). Site parameter should not be empty (when using default site, default should be used as a value).
If this doesn't help - try to do at least these two steps through REST API manually and see if there are any issues:

Authenticate to a site
Create a project

Also, what error message do you see?

repo: tableau/Logshark


text:
TypeError thrown when running excel_ui.py

Conda3.7 version:  4.7.10
Matplotlib version: 3.1.0
Error report:

Last login: Fri Aug  2 12:55:26 on ttys001
/Applications/Flowcal_my_develop/FlowCal/Run\ FlowCal\ (OSX) ; exit;
felixs-mbp:~ felixekness$ /Applications/Flowcal_my_develop/FlowCal/Run\ FlowCal\ (OSX) ; exit;
//anaconda3/lib/python3.7/runpy.py:125: RuntimeWarning: 'FlowCal.excel_ui' found in sys.modules after import of package 'FlowCal', but prior to execution of 'FlowCal.excel_ui'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
objc[9329]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9fc6d3d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1c1dcbdf50). One of the two will be used. Which one is undefined.
Reading experiment.xlsx...
Processing Beads table (1 entries)
Beads ID B0001...
Loading file "FCFiles/Beads006.fcs"...
Performing data transformation...
Performing gating...
Plotting density plot and histogram...
Traceback (most recent call last):
File "//anaconda3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "//anaconda3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/excel_ui.py", line 1671, in
run_command_line()
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/excel_ui.py", line 1668, in run_command_line
hist_sheet=args.histogram_sheet)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/excel_ui.py", line 1550, in run
full_output=True)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/excel_ui.py", line 487, in process_beads_table
savefig=figname)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/plot.py", line 1716, in density_and_hist
density2d(data, channels=density_channels, **density_params)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/plot.py", line 1211, in density2d
plt.gca().set_xscale(xscale, data=data_plot, channel=0)
File "//anaconda3/lib/python3.7/site-packages/matplotlib/axes/_base.py", line 3322, in set_xscale
ax.xaxis._set_scale(value, **kwargs)
File "//anaconda3/lib/python3.7/site-packages/matplotlib/axis.py", line 799, in _set_scale
self._scale = mscale.scale_factory(value, self, **kwargs)
File "//anaconda3/lib/python3.7/site-packages/matplotlib/scale.py", line 743, in scale_factory
return _scale_mapping[scale](axis, **kwargs)
File "/Applications/Flowcal_my_develop/FlowCal/FlowCal/plot.py", line 677, in init
matplotlib.scale.ScaleBase.init(self)
TypeError: init() missing 1 required positional argument: 'axis'
Press [Enter] to finish...

Identified reason for error:
In plot.py, the _LogicleScale() class fails at __init__(self, axis, **kwargs). As of Matplotlib 3.1.0, matplotlib.scale.ScaleBase__init__(self) requires a matplotlib.axis.Axis object as a second argument.

The obvious solution would be to modify this line, which has the following contents:
    def __init__(self, axis, **kwargs):
        # Run parent's constructor
        matplotlib.scale.ScaleBase.__init__(self)

to the following:
    def __init__(self, axis, **kwargs):
        # Run parent's constructor
        matplotlib.scale.ScaleBase.__init__(self, axis)

While this seems to work with matplotlib 3.1.0 and greater, it breaks compatibility with any previous version, including 3.0.x. Therefore, the recommended solution to preserve some level of compatibility is the following:
    def __init__(self, axis, **kwargs):
        # Run parent's constructor
        if packaging.version.parse(matplotlib.__version__) \
                >= packaging.version.parse('3.1.0'):
            matplotlib.scale.ScaleBase.__init__(self, axis)
        else:
            matplotlib.scale.ScaleBase.__init__(self)

I'll submit a PR with this code.

authors: castillohair felixekn

repo: taborlab/FlowCal


text:
Tabula doesn't recognize PDF

Issue: Tabula can't open PDF. PDF opens in Chrome and Preview. Mac OS bash shell utility 'file' reports
2014_SHS_Table_A-1.pdf: PDF document, version 1.6
Err Msg: Sorry, your file upload could not be processed. Please double-check that the file you uploaded is a valid PDF file and try again.
Tabula Version: 1.0.1 (1)
URL: http://ftp.cdc.gov/pub/Health_Statistics/NCHS/NHIS/SHS/2014_SHS_Table_A-1.pdf
OS: Mac OS X 10.11.3 / Mac OS X 10.9.5
FireFox: 44.0.2
Chrome: 48.0.2564
If you open the PDF with "PDF Split and Merge" <pdfsam.org> to save each page separately as version 1.7, you can open and extract data from these PDF files with Tabula using OS X 10.11.3 and Chrome.

	at java.util.concurrent.FutureTask.report(java/util/concurrent/FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(java/util/concurrent/FutureTask.java:192)
	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:497)
	at RUBY.afterExecute(/Users/204434/code/tabula/lib/tabula_job_executor/executor.rb:42)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1150)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(java/lang/Thread.java:745)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 4
	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:497)
	at RUBY.initialize(/Users/204434/code/tabula/lib/thumbnail_generator.rb:56)
	at RUBY.perform(/Users/204434/code/tabula/lib/tabula_job_executor/jobs/generate_thumbnails.rb:15)
	at RUBY.call(/Users/204434/code/tabula/lib/tabula_job_executor/executor.rb:104)
	at GenerateThumbnailJob_1233439963.call(GenerateThumbnailJob_1233439963.gen:13)
	at java.util.concurrent.FutureTask.run(java/util/concurrent/FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1142)
	... 2 more
java.util.concurrent.ExecutionException: java.lang.ArrayIndexOutOfBoundsException: 4
	at java.util.concurrent.FutureTask.report(java/util/concurrent/FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(java/util/concurrent/FutureTask.java:192)
	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:497)
	at RUBY.afterExecute(/Users/204434/code/tabula/lib/tabula_job_executor/executor.rb:42)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1150)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(java/lang/Thread.java:745)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 4
	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:497)
	at RUBY.initialize(/Users/204434/code/tabula/lib/thumbnail_generator.rb:56)
	at RUBY.perform(/Users/204434/code/tabula/lib/tabula_job_executor/jobs/generate_thumbnails.rb:15)
	at RUBY.call(/Users/204434/code/tabula/lib/tabula_job_executor/executor.rb:104)
	at GenerateThumbnailJob_1233439963.call(GenerateThumbnailJob_1233439963.gen:13)
	at java.util.concurrent.FutureTask.run(java/util/concurrent/FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1142)
	... 2 more

traceback ^^
looks like it's in JPedal?

I should note: I've reproduced in master Tabula.

authors: bllkng jeremybmerrill

repo: tabulapdf/tabula


text:
Improve documentation

Closes #8

bors r+

repo: taiki-e/easy-ext


text:
feat(taiko-client): change guardian provers  to directly submit proofs instead of contests

Description

Clarify responsibilities between components.
1.1. Event-handler just handles behavior when receiving various events, including submitting proof, submitting a contest, or doing nothing.
1.2. Proof-submitter chooses how to submit proof and whether to use delay.

Guardian prover workflow

Gavin, I think there should be a minimum delay before guardian prover submits a proof, to give regular prover a chance to submit valid proofs.

Gavin, I think when we have zk proofs, there should be a minimum delay before guardian prover submits a proof, to give regular prover a chance to submit valid proofs.

Yes, we did. Either sgx or zk proofs,  guardian prover will not submit proof until the current time is greater than expiredAt + at least 1 hour and there was no proof at that time.
In the above guardian prover workflow, I focused on the guardian prover's behavior when receiving events and put the logic about delaying into packages/taiko-client/prover/proof_submitter/proof_submitter.go.

repo: taikoxyz/taiko-mono


text:
Added support for Human-Readable Flattened GraphQL Queries

Summary:
Added Support for Human-Readable Flattened GraphQL Queries.
Sample Usage: curl "http://localhost:8000/api?posts&\$s=id,user.name"
Demo:
https://github.com/tailcallhq/tailcall/assets/62684960/6c642403-4f89-4ae4-8df7-7ea551584f3e
Issue Reference(s):
Fixes #560
/claim #560
Build & Testing:

[x] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly (if applicable).
[ ] I have performed a self-review of my own code.

@ssddOnTop the url should look like —
Expected
curl "https://example.com/api/user?id=123&$=name,age,address.city,address.state"

Actual
curl "https://example.com/api?user&id=123&$=name,age,address.city,address.state"

ie. the operation name should be part of the route and not the query params.

the operation name should be part of the route and not the query params.

yes I will fix that
But apart from that I think keeping we should give key to the query part i.e. $s and $r part
I think I can remove that part but having some key will be much better to recognize

@tusharmath can you assign someone to drop a review

/tip 50

authors: ssddOnTop tusharmath

repo: tailcallhq/tailcall


text:
Work on an interactive example editor

Work in progress...
This adds an optional interactive example editor to Tailwind :)

Hey, this is pretty cool! So you want to add interactive editor to all of the examples in the docs? I think that'd be rad.
In case this helps, I created Tailwind Filddle for fun a while ago (it's open source). FWIW I used Ace editor (by Cloud9) instead of codemirror. I invite you to a look 🙂. It's not super clean, but if you're not embarrassed with an early version - you released to late haha. Cheers.

Try: https://gustscss.com

The idea for this was that it's baked into the examples itself so that you can see what it's doing in realtime :)

That is awesome, @jbrooksuk

I'd still love to incorporate something like this into the docs at some point but since we've moved the docs to their own repo I'm going to close this WIP PR. Thanks @jbrooksuk!

authors: ZiFFeL1992 adamwathan jbrooksuk mkarnicki

repo: tailwindcss/tailwindcss


text:
Freebsd: Deamon don't work

Hello,
I'm testing takama/daemon and it don't work when I started my computer with the example.
[root@compile ~]# service -e
/usr/local/etc/rc.d/myservice
/etc/rc.d/hostid
....
[root@compile ~]# netstat -na |grep 99
[root@compile ~]#
When I start the service manually, it is works.
[root@compile ~]# service myservice start
[root@compile ~]# netstat -na |grep 99
tcp46      0      0 *.9977                 .                    LISTEN
I make many tests and I don't undertand :x:
One  Idea ?

Could you explain your example with code which used daemon service?
Did you use install the service before?

The code is the real example in https://github.com/takama/daemon.
Actually, I install daemon example in /bin/daemon.
Then I install daemon by "/bin/daemon install" and start service "service myservice start "
The program start correctly, I see the port 9977 open in netstat.
I have enabled debug mode in RC.
[root@compile ~]# service myservice start
/usr/local/etc/rc.d/myservice: DEBUG: pid file (/var/run/myservice.pid): not readable.
/usr/local/etc/rc.d/myservice: DEBUG: checkyesno: myservice_enable is set to YES.
/usr/local/etc/rc.d/myservice: DEBUG: run_rc_command: doit: myservice_start
Then I active myservice in reboot in the /etc/rc file.
myservice_enable="YES"
When it restarts, I see the service git but not myservice in /var/log/messages
I change permission on my service for 555 like git_daemon.
[root@compile ~]# ls -lrt /usr/local/etc/rc.d/
total 8
-r-xr-xr-x  1 root  wheel  413 Nov 18 19:46 myservice
-r-xr-xr-x  1 root  wheel  678 Dec 24 02:29 git_daemon
The most bizarre trick is when I rename the /bin/myservice program to /bin/myservice.app and I create "sh" script for starting myservice.app. The programme starting Oo.
I used
[root@compile ~]# uname -a
FreeBSD compile 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

The last changes corrected the worry.
I reopen a ticket to you on another issue.

repo: takama/daemon


text:
Support for functioning in reverse (time since)

Instead of only until it would be very useful to also support since so the timer could count up from a specified time.
Use cases: After an event occurs, you want the context to change from "days until X" to "days since X"

This would be great.

authors: Nepherius fjarrett