text:
--include-builtins fails

There is a typo in pyjs.py file:
                builtins = open(os.path.join(os.path.dirname(__file__)), "py-builtins.js").read()

should be
                builtins = open(os.path.join(os.path.dirname(__file__), "py-builtins.js")).read()

Thank you very much for reporting this! As it happens, I am no longer associated with qsnake/py2js since we had a difference of opinion in which way to take the project. Therefore I maintain a fresh branch over at https://github.com/chrivers/pyjaco, where many new features are implemented and this bug is fixed.
However, I would like to point out that I am NOT the primary author of qsnake/py2js, but I am one of the lead devs on pyjaco. I wish py2js all the best. I merely want you to know that alternatives exist :-)

Thanks for the information !
I experienced many problems with py2js (I was wondering if I would switch
all my js code for some project) and I'm glad to see there is maintainers ;)
I watch your project now, I'll take a look from time to time, now I have to
dig my plain javascript ;)
Cheers,
Fabien Devaux.
2011/12/4 Christian Iversen <
reply@reply.github.com

Thank you very much for reporting this! As it happens, I am no longer
associated with qsnake/py2js since we had a difference of opinion in which
way to take the project. Therefore I maintain a fresh branch over at
https://github.com/chrivers/pyjaco, where many new features are
implemented and this bug is fixed.
However, I would like to point out that I am NOT the primary author of
qsnake/py2js, but I am one of the lead devs on pyjaco. I wish py2js all the
best. I merely want you to know that alternatives exist :-)

Reply to this email directly or view it on GitHub:
https://github.com/qsnake/py2js/issues/20#issuecomment-3007040

Could you give some examples of the problems you have had? I'd like to make sure they are fixed :)
Also, keep in mind that by now, py2js and pyjaco are totally different projects. Things might work better in one or the other, as they have different goals.

Hi @fdev31, thanks a lot for reporting the bug! I've just fixed it. Let us know if you find more bugs, feel free to also send us pull requests.
@chrivers, good luck with your new project. I would suggest you to delete and repush your repository, so that github doesn't show that it is forked from py2js, so that people are not confused which project is which.

Thanks for the reactivity!
If I want to understand the main differences between py2js & pyjaco, where should I look ?

Thanks for your words about pyjaco. Let my clarify the goals of py2js (you were not exactly precise above).
The goal of py2js is to provide a Python like experience in JavaScript by emulating Python types in a javascript library and translating the Python code using AST. The goal is that it should feel like Python. In addition to that, we want to allow fine granularity to be able to call raw JS libraries from within in.
I don't want to interpret the goals of pyjaco, but from what you wrote I think your goals are the same as ours. So I would say that the main difference is that pyjaco is developed mainly by @chrivers, while py2js by @certik. We were not able to work together on one project, so that's why there are two projects with almost the same goals.

Hey guys, sorry for not having answered to the question about the problems I encountered, in fact I only played a full afternoon but then I switched to "do nothing" (keep play javascript) for now and I can't remember precisely enough.
I can tell it was about "str" type, passed as argument to some jQuery functions required a String() cast :(
Some syntax is now allowed like the "$" sugar, but I suppose it's not an important issue.
try/except not being support sounded rude to me also :P
For lambdas & co, I think that was acceptable, but with some possible improvements I can't remember anyway.
About the fight of egos, that's so "classic" , I just can tell trying to work together is always more difficult.
At the end, people trying to conciliate may achieve a wonderful project, but those fighting alone rarely survive to the lack of energy and just do toys.
It's quite known that having divergent opinions it pretty god for the target : the final quality raises automatically
Sorry if I sound direct since we don't known each-other but try once more to work on a "merged" project if you think that is possible. If it's just marketing or implementation issues, then it's easy to make things better instead of different.

And be positive: you have a change to get a real contributor to your project !

fdev31, thankk you for your comment.
In fact, I'm using pyjaco for a jQuery project right now, so it is possible :)
Of course, $ is not valid in python, so I've simply injected the raw javascript string "var Q = $" into the beginning of the translated code.
So instead of using
$(foo)
I can just use
Q(foo)
which is valid python. When you pass a pythonic value to javascript, you have to convert it to a native javascript type with js(). So it would be something like this:
Q(js("#foo div.bar:first-child")).....
This works, I use it myself. Oh, and try-except is most definitely supported, in both projects I believe :)
I think we would both love the idea of having you contribute to "a / the / our" project, and I certainly would never exclude anyone. Because github as a standard course of action asks people to fork projects, it just sort of happened. I started contributing to py2js, but we wanted our forks to go in different directions.
Ondrej, what do you think?

Heh, I was talking as both of you as "contributors" of each-other ;)
I understood about the "$" limitation, that sounded "obvious" but still a theoretic bug since it can mask some js behavior.
Btw, from what I remember, I didn't try the js() function, that may explain some of my difficulties ;)
Forking of course is an option, with regular merge, but since, the differences only sounded "technical" but I suppose big part of the code base could be at least shared.
Having a library ? A tool set ? But definitely, having something in common sounds "simple".
If you both have strong vision on a project, trying to collaborate can give birth to something even stronger, don't you think ?
About the current goals, sorry If I understand badly, can I summarize to:

pyjaco tries to put the power on the python side, with generated "self-contained" javascript
py2js offers some kind of "python emulation layer" on the javascript side, some like of "python wrapper for javascript"
but today both projects are hybrid...
can you fix my vision ?

authors: certik chrivers fdev31


text:
Create tests folder with demo projects

Able to test each class, function, etc

Have two subfolders, one for GLEW builds and one for GLAD builds.
See Issue https://github.com/qtf0x/csci441/issues/6

In reference to https://github.com/jpaoneMines/csci441/issues/14

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Fixes to unit tests (@qualweb/qw-page, @qualweb/evaluation, @qualweb/wcag-techniques)

This PR contains a bunch of fixes to the unit tests of @qualweb/qw-page, @qualweb/evaluation, and @qualweb/wcag-techniques.
For the first two, it's basically just reducing their verbosity (run puppeteer in headless mode, reduce console output) so the output is cleaner.
For @qualweb/wcag-techniques, I've cleanup up their setup/teardown to happen in actual setup/teardown functions, and refactored the code to be more DRY.

Forgot to mention, the PR addresses the following issues: #15, #13, and #11

source: gharchive/pull-request

repo: qualweb/qualweb

license: ISC


text:
🛑 otakusan is down

In 0c60336, otakusan (https://otakusan.net/LightNovel) was down:

HTTP code: 0
Response time: 0 ms

Resolved: otakusan is back up in c6d693c.


text:
🛑 kokocon is down

In b959dd9, kokocon (http://kokocon.net/) was down:

HTTP code: 500
Response time: 123 ms

Resolved: kokocon is back up in 2866474 after 7 minutes.


text:
🛑 kokocon is down

In 552454d, kokocon (http://kokocon.net/) was down:

HTTP code: 500
Response time: 112 ms

Resolved: kokocon is back up in 79dd769 after 7 minutes.


text:
🛑 kokocon is down

In 3c8232f, kokocon (https://tracker.kokocon.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kokocon is back up in 34b093b after .


text:
🛑 hako.re is down

In adda6b2, hako.re (https://mangochan.site/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hako.re is back up in b808916 after 6 minutes.


text:
Docstring cleanup for cum_returns

In response to Issue #73 the docstring for the cum_returns() function is cleaned up.

Note completely removed.

Thanks @rsheftel!

authors: rsheftel twiecki

repo: quantopian/empyrical


text:
cirq.Simulator.compute_amplitudes not well documented

We should add some documentation on how to use cirq.Simulator.compute_amplitudes . There is no documentation in https://cirq.readthedocs.io/en/stable/generated/cirq.Simulator.html , or in the simulator tutorial https://cirq.readthedocs.io/en/stable/simulation.html

The method is documented at https://cirq.readthedocs.io/en/stable/generated/cirq.Simulator.html: it's listed under "Methods", and clicking on it links to the full method documentation. Though it does look like that documentation could be expanded a bit.
As for adding it to the tutorial, I think it would make a much more compelling example once Cirq has a tensor network simulator that does not explicitly store the entire wavefunction.

We've moved to new docs infra and this appears to have more complete docs now.

authors: MichaelBroughton karlunho kevinsung

repo: quantumlib/Cirq

license_source: bigquery


text:
cg.get_engine_sampler gate_set_name should be made optional

As far as I can tell, Engine.get_sampler's gate_set argument is now optional. As such, cg.get_engine_sampler should not require a gate_set_name.
Also: we don't have a CZ gate in gatesets.NAMED_GATESETS or GOOGLE_GATESETS

We could deprecate cg.get_engine_sampler entirely, since this is equivalent to cg.get_engine(...).get_processor(...).get_sampler(). But I agree if we keep it around we should make the gate set arg optional, as it is on EngineProcessor.get_sampler.

This has been done

authors: maffoo mpharrigan


text:
Hubbard model Trotter steps

Eventually it would be great to implement the sqrt(N) depth Trotter steps described in arXiv:1711.05395 - perhaps @john6060 would be interested in working on this?
But more immediately I think it would be really helpful for people to see some examples of using OpenFermion-Cirq for Hubbard Trotter steps. Because the algorithm of arXiv:1711.04789 is much closer to the linear swap networks we've already implemented, I think we should try to add that in the next couple weeks, perhaps with a small tutorial. @kevinsung would you want to do this? How much would it require beyond what we already have?

I'd say that we're probably at about 60% of the tutorials I'd like to have once we add some rather basic functionality over the next few months.

@Strilanc most of the extra build time from the tutorials is from the simulator, so the first thing is to upgrade the simulator.

That's true, the coming simulator improvements will help a lot.

authors: Strilanc babbush kevinsung

repo: quantumlib/OpenFermion-Cirq


text:
Add SignExtend for two's complement sign extension

Useful for a lot of arithmetic ops which allow different bitsizes. wiki

I think this belongs in bookkeeping not arithmetic + this bloq needs to implement classical action

My understanding is that bookkeeping bloqs are only for building the correct bloq graph, but do not actually perform any quantum action. But this bloq actually performs a non-trivial action, so it makes more sense to keep it in arithmetic.

My understanding is that bookkeeping bloqs are only for building the correct bloq graph, but do not actually perform any quantum action. But this bloq actually performs a non-trivial action, so it makes more sense to keep it in arithmetic.

This is a reasonable set of logic to apply to the organization, thanks

authors: anurudhp mpharrigan

repo: quantumlib/Qualtran


text:
Global features

AFAICS, you cannot register a "global" feature for all clients via e.g.:
quarkus.cxf.client.features=org.apache.cxf.feature.LoggingFeature

(or quarkus.cxf.endpoint.features for that matter)
For a DRY and KISS config approach, registering global features should be supported (and probably also for interceptors etc.).
One question to answer would be whether client/endpoint specific settings are adding to the global ones or are replacing them instead (for the respective client/endpoint).

Workaround:

quarkus.cxf.client.foo.features=${myproject.cxf.client.global-features}
quarkus.cxf.client.bar.features=${myproject.cxf.client.global-features}
set myproject.cxf.client.global-features=org.apache.cxf.feature.LoggingFeature (or even multiple features, separated with ,)

You can also use something like: quarkus.cxf.client.foo.features=MySpecificFeature,${myproject.cxf.client.global-features}
And the property doesn't event need to exists at all.

One question to answer would be whether client/endpoint specific settings are adding to the global ones or are replacing them instead (for the respective client/endpoint).

I'm all for adding.

Do you have an opinion on this @ppalaga?

Sounds good

@famod, it sounds like (and I'd think the same from my own experience) the main motivation for this request is logging.
I wonder whether it would be much more user-friendly to do the following two changes:

Move the code of quarkus-cxf-rt-features-logging extension to quarkus-cxf (and keep quarkus-cxf-rt-features-logging empty for backwards compatibility), so that users can enable logging without having to bother with adding the extension.
Add some new global logging config, like:

quarkus.cxf.logging.enabled-for = clients|services|both|none
quarkus.cxf.logging.pretty = true
...

WDYT?

@ppalaga sorry for the late reply:
That change LGTM as far as logging is concerned!
But what about other features, maybe even user-supplied ones? I think it would come in handy if you could register any kind of extension globally, no?

This would make sense for the quarkus-cxf-rt-features-metrics module as well.

@manubell thanks for the suggestion! Would you mind filing a separate issue?

authors: famod ppalaga

repo: quarkiverse/quarkus-cxf


text:
Check IDEs Quarkus tooling support for this

Make sure the Quarkus tooling support this and the tooling team is aware of this.

or at least check that there aren't parts of it that is inherently difficult to tool :)

Having the node_modules dir as part of the root of the project allow to have IDE support:
https://docs.quarkiverse.io/quarkus-web-bundler/dev/advanced-guides.html#node_modules

repo: quarkiverse/quarkus-web-assets


text:
Add automatic browser reload in dev-mode

See https://esbuild.github.io/api/#hot-reloading-css
We should create a new SSE endpoint containing the list of changes, and inject something similar to the esbuild example, directly in the code in dev mode (with a config to disable it)

We could create a specific extension for this with a SPI to allow pushing added, udpated and removed resources to the list.
With the Web-Bundler we also control the js part so we can add the EventSource automatically in dev mode.

This is done in 1.5.1

repo: quarkiverse/quarkus-web-bundler


text:
Upload files with utf-8 encoded name

Hi,
It would be nice to be able to upload files with a name encoded in utf-8 rather than ascii (for example containing accents). One possible way to do that would be to escape(urldecode(upfile.raw_filename)) (at scans.py:146) rather than using the bottle escaping as is (which is what upfile.filename is, according to the Bottle doc.
I think it would be very valuable to users to be able to keep the file name they uploaded (and globally). What do you think?

solved by commit 01361543ebab6ff237e261d26e0cf00cca3279ca

repo: quarkslab/irma-frontend


text:
Add some indexes to extension_release* tables

@gastaldi could we try to deploy that and see how it goes? It might be a good first step towards trying to improve the situation.
What would help further would be to get a dump of the production database and set a log_min_duration_statement to 1s there to get some input.

In the end, it didn't help.


text:
Chunk options on first-line not recognized as executable code chunk

Hi, May I suggest some improvements.
I've found that R code chunk that has options defined on the first line or has space after r can't be recognized as executable code chunk, and the code can't be run (by cmd-enter).

(This works fine in RStudio, however.)
I've notice that you recommend using the comment-based syntax, however, may be someone (including me) might use in-line option in some chunk, also.
I guess, the problem might located in the regular expression somewhere that matching code chunk.
However, This is a Great extension thus far, Good job 👍
Thankyou

Thanks for pointing this out! I made the change to do more liberal parsing here: https://github.com/quarto-dev/quarto-vscode/commit/169c5cda0fb146ae1410b5d64e9bb439052245ce
This will be in the next release which should be in ~ 1 week or so.

Thank you !

authors: Lightbridge-KS jjallaire

repo: quarto-dev/quarto-vscode


text:
Java 8 not supported?

It looks like 2.5.0 has been published and requires Java 11 to run.
I am not sure if this is intended.
If it is, I suggest to amend the release notes for 2.5.0 to call it out: https://github.com/quartz-scheduler/quartz/releases/tag/v2.5.0

Migration from javax to jakarta is a migration to JDK 17. Breaking everything. No surprises on my side. Maybe emphasize the "consequences".

this is intended; if you need to stick to old java versions use 2.4.x, see https://github.com/quartz-scheduler/quartz/discussions/1195

Thanks. All clear. I think the "Jakarta" mention does not clearly convey the Java 11 thing. IMHO it's worth pointing out Java 11 dependency in 2.5.0 release notes.

authors: jonnybecker mccartney mprins

repo: quartz-scheduler/quartz


text:
Quasar Repository Re-organization.

Currently Quasar is considered to be too monolithic. This results in long build times (e.g. 100 minutes build time , 600 minutes total time). This ticket is the EPIC which will in turn point to multiple smaller tickets.
The hope is to break out Connectors and other "logical" pieces into their own repositories and then building inter-repository dependencies, so as to achieve the desired level of modularity. This is delicate surgery and will likely entail a "binary-switch" release - i.e. will be too hard to maintain 2 code bases concurrently, so we will just switch from the current monolithic
Quasar repository to a modular organization of repositories on a certain date/time and then go from there.

Coverage has only been running on master since the introduction of PR caching due to how that is achieved. This means that passing PRs can be merged and subsequently cause master to start failing due to a coverage threshold not being met. Currently we're wading the waters and making adjustments as necessary. We should shore this up and start running coverage against PRs again once a poly repo is in place. PR caching shouldn't be necessary afterwards due to smaller and hence faster builds.

Polyrepoing out the connectors should be relatively straightforward once we fully invert the dependency between it and the connectors.  That task requires some restructuring effort, but not too much since most of that work is already done (the current state of things is a very hacky shim, since the connector architecture is now very clearly biased towards an inversion).
Once the dependency is inverted, polyrepo for the connectors becomes a relatively trivial application of git witchcraft (to avoid losing commit history) and infrastructure setup (to ensure we still have Travis stuff).  It also requires moving to a four-component version for Quasar itself, which is a relatively small change, though one which touches some other stuff (including SDBE).

authors: djspiewak drostron zeeiyerWork

repo: quasar-analytics/quasar


text:
Endpoint to interrogate RW permissions of a given target-mount (db+user combination).

From @zeeiyerWork on September 23, 2017 22:28
In support of https://github.com/slamdata/slamdata/issues/2011:

We need to add an API that can return to the front-end, whether the target store specified in a mount supports READ or READ/WRITE operations for the user/pwd combination.

cc: @kRITZCREEK
Copied from original issue: slamdata/slamdata-backend#244

From @kRITZCREEK on September 25, 2017 11:18
I think @djspiewak suggested to put this into Quasar, since it needs to be implemented in the connectors (Can't just be a slamdata-backend thing).


text:
Plan LeftShifts with IncludeId using $unwind's includeArrayIndex

Relevant documentation: https://docs.mongodb.com/manual/reference/operator/aggregation/unwind/#pipe._S_unwind
When planning LeftShifts, the Id flag is simply passed through inside the newly created FlatenningBuilder. The choice of whether to plan the FlatteningBuilder with $unwind (agg) or $simpleMap (mapReduce) is made in the toWorkflow function.

In talking with @jsantos17 - several queries do need it (of the type -> select a[*] + b[*] from foo) and @rintcius is taking a look - hence the December/5.0.0 labels. Thanks.


text:
[service] .env parser

Will this be resolved by quasar-cli, or do we roll our own?

Good question!
I think both would be fine dotenv is pretty friendly.
Current

Medium Post using the current method of ENV vars for the cli.
dotenv Can be the bridge to future cli env options.

quasar-env RFC

quasar-cli. Writes current CLI state to .env file, loads existing ENV variables, accepts ENV variables as parameters and reads from .env file via  dotenv

authors: PhearZero nothingismagick


text:
make it possible to run go-consistent as a library

This is handy when integrating linters into an already existing system.

@quasilyte Do you mind if I try on this issue? It seems that some refactoring has to be done though

@jlwt90 go ahead, it's all yours. :)

@quasilyte I finally got some time to go into the source code 🙇
In order to let go-consistent scan all source code and detect the majority of the variants, we probably need to run with all the target packages, instead of a single run per package. What do you think about the entry point of the library?
I am about to write an entry point with function function Run(...) []Issue but kinda struggling with the input of this entry point. Taking golangci-lint as an example, we probably need to pass a *loader.Program into the Run() function(?) with goanalysis.LoadModeWholeProgram so that that tool can pass everything to go-consistent in one shot?
Here is the example that I referred to:
https://github.com/golangci/golangci-lint/blob/master/pkg/golinters/deadcode.go#L24-L25
https://github.com/golangci/go-misc/blob/master/deadcode/deadcode.go#L27
Sorry for the question... I am still a golang / analysis tool newbie ><
Thanks!

The problem with traditional "load the whole program" approach is it.. requires a lot of memory. Some projects can take so much that analysis can't be run on local machines anymore.
go-consistent does do a whole-program analysis, but it does not keep all AST and types in memory the entire time. Once a package is processed, we update the facts set (counters) and continue with another package. It allows us to process almost arbitrary sized project with constant memory usage (it's less CPU efficient, but "a little slower" is faster than "never" in cases of the big projects).
go/analysis permits to consume one package at the time I believe. If that's the case, we can the same trick there. Although it might load all packages into the memory behind the scenes. We want to avoid reporting issues while "indexing" pass, we'll only collect "facts" (in analysis terminology). Then users can use that pass to do whatever they want. One example is to write another pass that uses these facts to report more/less used variants.
Maybe we can move all the state in a separate package, use that inside the current main and add third package that provides go/analysis compatible analyzer that can be used as a library (it will use that second package to do its work).

It's also stated in the project traits (readme):
Can handle projects of any size. This means that there should be no significant memory consumption growth with an increased number of packages being checked. There can be "fast, but memory-hungry" option that can work best for small-average projects, but it should be always possible to check huge projects on the developer machine.

I feel a little guilty for the time you could invest in this.
The initial idea of this project was "zero-configuration". It sounds nice, but in reality, there are at least two drawbacks:

You need to analyze the entire scope (package/module/project) to infer appropriate suggestions.
Sometimes inferred suggestions are not what you want.

Maybe it would be better to split this into two almost independent parts. One would run a consistency check over a project using the given config that describes what should be used and what shouldn't. The second part would allow you to run analysis over the code base and generate the config that the user may edit later.
With this new architecture, checking consistency does not require a full scan/indexing as we know all the right answers from the beginning.

Any updates on this?
It would be really great if this is implemented because then we can start to integrate this awesome longer into golangci-lint

repo: quasilyte/go-consistent


text:
Adding check on organization name

Adding validation that org name must be valid before submitting form. Adds alert icon to invalid orgname. Does not display message since format requirements are already present under input.

@bcaton85 Can you also add a check for the max length? Should flag on >255 characters.

Good catch!

repo: quay/quay-ui


text:
Unable to get good results with categorical_crossentropy on a Multi-Class Object Segmentation Model

My goal is to train a Multi-Class FPN based Object segmentation network consisting of 8 or more classes. As I understand it the categorical_crossentropy model compile option should be used for that, but I can't seem to get it to work on a 2-class test case.
I can get good results with a 2-class FPN Object Segmentation network when I use
binary_crossentropy, and binary accuracy for the Model Compile.
It seems like I'm missing something obvious.
Here is my code
Code.zip
Here is a Results comparison between binary_crossentropy and categorical_crossentropy.
Result_Comparison.zip

same

What is your activation function? for categorical it should be softmax and for binary sigmoid

For the categorical_crossentropy option I use softmax.
For the binary_crossentropy I use sigmoid.
Is it possible that I don't have my dataset correctly configured for categorical_crossentropy?
Here is my dataset for the two-classes.
https://drive.google.com/open?id=1cuiXlbmRQ-iyfD8lzfnMgrG4M4LwJSCW
Now I did test out more classes, and binary_crossentropy worked fine even when I reached all 8-classes that my original dataset has.

I updated my code to switch from floating point for the mask to uint8 with values of {0, 1}.
It still doesn't work using categorical_crossentropy. So I still either have the dataset wrongly configured or my understanding of how it's supposed to work is wrong. Maybe I need to add a background layer. Something that doesn't seem to be required for binary_crossentropy.
The_Two.zip

Background is necessary for categorical_crossentropy
Make sure if your sum onehot encoded mask across last dim you will have np.ones() array.

Adding the background fixed it so now I'm getting the expected results.
Thanks for your help.
Here is the code in case anyone else is playing around with Object Segmentation on a dataset that consist of only a single object class per image. So all I did to add the background mask was to simply invert the object mask for each image, and assign it to background mask.
Code.zip

My goal is to train a Multi-Class FPN based Object segmentation network consisting of 8 or more classes. As I understand it the categorical_crossentropy model compile option should be used for that, but I can't seem to get it to work on a 2-class test case.
I can get good results with a 2-class FPN Object Segmentation network when I use
binary_crossentropy, and binary accuracy for the Model Compile.
It seems like I'm missing something obvious.
Here is my code
Code.zip
Here is a Results comparison between binary_crossentropy and categorical_crossentropy.
Result_Comparison.zip

hi
@S4WRXTTCS, can you provide codes for multi-class object segmentation you designed for your 8 classes.
Also suggest way to generate custom dataset mask generation, that looks similar to camvid dataset.
it will  be thankful to you.


text:
.NET SDK Requirement

This is really neat, thanks.
Is there any way to host the SDK along with the application? Can a portion be shipped so as not to be so huge?
My goal is to allow for creating dynamic content in PowerShell for F# in the same way that can be done with C# with Add-Type, and for C# at least, the SDK doesn't have to be present. Ideally it all ships as a self-contained powershell module, or otherwise doesn't need to bootstrap the SDK (which is a lot when you just want some ad-hoc F# types)
https://github.com/justingrote/fsharp
This used to work but broke with the latest compiler changes disallowing dynamic compilation.
C# example I'm trying to adapt to work for F# as well:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/add-type?view=powershell-7.3#example-1-add-a-net-type-to-a-session

Hi Justin,
I don't think hacking with shipping parts of the SDK with the fsc-host package promises a lot of stability or is a good practice. Although, I think it may be possible to compile without fsc.exe (and hence without depending on .NET SDK). The docs state:

NOTE: There are several options for hosting the F# compiler. The easiest one is to use the fsc.exe process and pass arguments.

I am wondering what the other several options are. I may give it a bit of research (any ideas welcome). However, the current version of fsc-host just assumes the SDK is there (hence my recommendation to package apps with Docker).
Side note: I guess for your use case it would be great if Powershell team could take a contrib to Add-Type providing some guidance from the F# compiler team. From the code it looks like Add-Type is meant to support multiple langs in the future...

Also I think this discussion indicates the tight coupling of F# tooling with the SDK.
I'll close the issue for now.

authors: JustinGrote queil

repo: queil/fsc-host

license: Unlicense


text:
Doc update: Remove querydsl-apt from regular classpath

When a dependency is set to 'provided' the classes are available on classpath during development. Even worse: The compiler is compiling the code with success and the implementation will fail due runtime.
The solution for that issue is (I think): Add the dependency to the maven plugin itself. So it's only available due runtime of the plugin and won't be added to the classpath of the programm itself.

Thanks for the contribution. The APT processor uses the project compile classpath for compilation. Plugin dependencies won't be part of that classpath. Did you try that configuration?
I agree that there is the risk that APT dependencies might be referenced also elsewhere. Did that happen in your case?

For sure: I've tried it in an example project and it works very well. The Q-Files are generated and they work in all my test cases.
As far as I know the dependency added by a plugin is only on the classpath when the lifecycle runs the plugin goal. See Sonatype documentation 7.1.2: http://books.sonatype.com/mvnref-book/reference/_configuring_maven_plugins.html
I removed slf4j-log4j as well because it clashes with my logback on the CP:
SLF4J: Found binding in [jar:file:/<private>/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/<private>/.m2/repository/org/slf4j/slf4j-log4j12/1.7.11/slf4j-log4j12-1.7.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]

Are you sure this dependency is really needed? I'm new to QueryDSL but if it uses slf4j for all logstatements, it is ok without slf4j-log4j. If you use log4j as well, you should replace the entry with log4j-over-slf4j (http://www.slf4j.org/legacy.html).

I've been using this configuration without issues: https://github.com/johnktims/spring-boot-querydsl-liquibase-starter/blob/master/pom.xml#L81

@johnktims @Shredder121 Is this good to merge?

:+1:

Yes, it's good, @johnktims do you want to merge?

authors: Shredder121 SvenBunge johnktims timowest

repo: querydsl/querydsl


text:
Normalization and quoted things

It's not getting any prettier.
One thing we could maybe do is split on quotes, and only process all odd numbered indexes. (string mode off)

Repushing, one commit isn't being built.

Forgot my progress label.
There are still some cases that fail.

I don't think we intend maintaining QueryDSL 3 anymore and as far as I am aware,  normalisation and quotation in queries was actually improved in QueryDSL by a fair bit. Please reopen if I am mistaken.


text:
Incorrect namespace in C++ to/from json (nlohmann)

The to_json/from_json functions should be in the same namespace as the structure. I'm using Visual Studio 2017 (VC++)
Additional information: https://github.com/nlohmann/json/issues/780#issuecomment-376696058
QuickType Code Gen
#pragma once

#include "json.hpp"

namespace quicktype {
    using nlohmann::json;

    inline json get_untyped(const json & j, const char * property) {
        if (j.find(property) != j.end()) {
            return j.at(property).get<json>();
        }
        return json();
    }

    inline json get_untyped(const json & j, std::string property) {
        return get_untyped(j, property.data());
    }

    struct Welcome {
        int64_t response_code;
        std::string response_message;
    };
}

namespace nlohmann {
    void from_json(const json & j, quicktype::Welcome & x);
    void to_json(json & j, const quicktype::Welcome & x);

    inline void from_json(const json & j, quicktype::Welcome& x) {
        x.response_code = j.at("response_code").get<int64_t>();
        x.response_message = j.at("response_message").get<std::string>();
    }

    inline void to_json(json & j, const quicktype::Welcome & x) {
        j = json::object();
        j["response_code"] = x.response_code;
        j["response_message"] = x.response_message;
    }
}

Working Code
#pragma once
namespace quicktype {
	using nlohmann::json;

	inline json get_untyped(const json & j, const char * property) {
		if (j.find(property) != j.end()) {
			return j.at(property).get<json>();
		}
		return json();
	}

	inline json get_untyped(const json & j, std::string property) {
		return get_untyped(j, property.data());
	}

	struct Welcome {
		int64_t response_code;
		std::string response_message;
	};

	void from_json(const json & j, quicktype::Welcome & x);
	void to_json(json & j, const quicktype::Welcome & x);

	inline void from_json(const json & j, quicktype::Welcome& x) {
		x.response_code = j.at("response_code").get<int64_t>();
		x.response_message = j.at("response_message").get<std::string>();
	}

	inline void to_json(json & j, const quicktype::Welcome & x) {
		j = json::object();
		j["response_code"] = x.response_code;
		j["response_message"] = x.response_message;
	}
}

I am facing a similar issue with Visual Studio 2017. What I have done is to add an additional useTopLevelNamespace option for C++. This basically reuses the top level namespace provided for wrapping to_json and from_json functions.
--[no-]useTopLevelNamespace                       Moves to_json and from_json functions under the top level namespace (off by default)

I can create a PR for this, but haven't had time to run tests.

Confirmed in Visual Studio 2019.

@schani As to the linked issue (https://github.com/nlohmann/json/issues/780#issuecomment-376696058) the fix described by @smalhotra-spirent correctly solves the problem and better complies with the C++ standard.
His fix only adds a new option, thus it can't even break backwards compatibility and is the only chance to get it to compile with the latest Microsoft compiler (I think after a short test phase, it should get the default though).
If it helps to speed things up, I could also create a pull request with @smalhotra-spirent's fix.

Using MSVC-2022 with c++-20 enabled resolves the problem.

While the solution is very simple, the issue cause recurring support in the popular Nlohmann repo
https://github.com/nlohmann/json/discussions/3280
Indeed the generated code need to be corrected so that the to and from are not in the lib namespace, or at least in the generated header comments, please mention the possibility that the compilation error "no matching overloaded function found when implementing from_json function" relate to the choice of namespace where "to" and "from" are implemented in the autogenerated code.
The combination of the quicktype tool and the Nlohmann is a very powerfull tool that should gain in popularity but we can't evaluate how many users could be discouraged at the first occurence of the issue !

authors: Jusonex LeStahL SylvainFogale hemantvallabh llilakoblock smalhotra-spirent

repo: quicktype/quicktype


text:
Adding the capacity for an actor to spawn another actor.

Removed the supervising code in the actor handle.
Renames spawn_async_actor.

@fulmicoton
I left a comment, though it was a minor one.

@mosuka, oops. I added a commit that was not meant for this PR. I removed it. (And apply your comment to the other commit)

@fulmicoton oh. ok, thanks!

authors: fulmicoton mosuka

repo: quickwit-inc/quickwit


text:
Too many gRPC gossip rounds

Seen on the Cicada CP:
2024-04-08T18:10:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:10:41.769Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-286599efe1d068", "indexer-2875172c04e558", "indexer-28756d5c093408"]
2024-04-08T18:10:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:10:41.843Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 73ms
2024-04-08T18:11:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:11:41.773Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-286599efe1d068", "metastore-48ed0d2a796358"]
2024-04-08T18:11:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:11:41.837Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 64ms
2024-04-08T18:12:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:12:41.770Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-287422ec6352e8", "indexer-28756d5c093408"]
2024-04-08T18:12:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:12:41.851Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 80ms
2024-04-08T18:13:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:13:41.773Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "indexer-2875172c04e558", "janitor-78423eec261148"]
2024-04-08T18:13:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:13:41.827Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 53ms
2024-04-08T18:14:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:14:41.769Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-287422ec6352e8", "janitor-78423eec261148"]
2024-04-08T18:14:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:14:41.829Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 59ms
2024-04-08T18:15:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:15:41.773Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "indexer-2875172c04e558", "metastore-48ed0d2a796358"]
2024-04-08T18:15:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:15:41.831Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 57ms
2024-04-08T18:17:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:17:41.778Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "searcher-286599efe1d068", "indexer-28756d5c093408"]
2024-04-08T18:17:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:17:41.869Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 91ms
2024-04-08T18:17:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:17:41.869Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling up number of shards to 3 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:17:48Z app[e82d41ec03e498] iad [info]2024-04-08T18:17:48.158Z  INFO quickwit_ingest::ingest_v2::routing_table: inserted 1 shards into routing table index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:18:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:18:41.775Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "indexer-2875172c04e558", "indexer-28756d5c093408"]
2024-04-08T18:18:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:18:41.833Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 57ms
2024-04-08T18:19:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:19:41.776Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "indexer-2875172c04e558", "janitor-78423eec261148"]
2024-04-08T18:19:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:19:41.855Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 79ms
2024-04-08T18:20:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:20:41.777Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "indexer-2875172c04e558", "searcher-0806603b656998"]
2024-04-08T18:20:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:20:41.838Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 61ms
2024-04-08T18:21:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:21:41.775Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-0806603b656998", "searcher-286599efe1d068", "janitor-78423eec261148"]
2024-04-08T18:21:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:21:41.840Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 64ms
2024-04-08T18:22:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:22:41.778Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "searcher-287422ec6352e8", "indexer-28756d5c093408"]
2024-04-08T18:22:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:22:41.836Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 58ms
2024-04-08T18:23:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:23:41.783Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "janitor-78423eec261148", "searcher-0806603b656998"]
2024-04-08T18:23:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:23:41.850Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 66ms
2024-04-08T18:24:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:24:41.779Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "indexer-2875172c04e558", "janitor-78423eec261148"]
2024-04-08T18:24:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:24:41.849Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 69ms
2024-04-08T18:24:48Z app[e82d41ec03e498] iad [info]2024-04-08T18:24:48.075Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling down number of shards to 2 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:25:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:25:41.779Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-0806603b656998", "metastore-784ee79fe23e58"]
2024-04-08T18:25:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:25:41.835Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 55ms
2024-04-08T18:25:52Z app[e82d41ec03e498] iad [info]2024-04-08T18:25:52.595Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling down number of shards to 1 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:26:00Z app[e82d41ec03e498] iad [info]2024-04-08T18:26:00.160Z  INFO quickwit_control_plane::indexing_scheduler: running tasks and last applied tasks differ: reapply last plan plans_diff=IndexingPlanDiff(missing_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2"), ShardId("01HTZEW97E5EVCE3GDT76VBFFG")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []}, , unplanned_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZ8DC1RCWFR6Y89F8EZ88BN"), ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2"), ShardId("01HTZEW97E5EVCE3GDT76VBFFG")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []})
2024-04-08T18:26:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:26:41.781Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["janitor-78423eec261148", "metastore-784ee79fe23e58", "indexer-28756d5c093408"]
2024-04-08T18:26:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:26:41.842Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 60ms
2024-04-08T18:26:55Z app[e82d41ec03e498] iad [info]2024-04-08T18:26:55.179Z  INFO quickwit_control_plane::indexing_scheduler: running tasks and last applied tasks differ: reapply last plan plans_diff=IndexingPlanDiff(missing_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []}, , unplanned_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2"), ShardId("01HTZEW97E5EVCE3GDT76VBFFG")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []})
2024-04-08T18:27:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:27:41.780Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "metastore-48ed0d2a796358", "searcher-286599efe1d068"]
2024-04-08T18:27:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:27:41.838Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 58ms
2024-04-08T18:27:57Z app[e82d41ec03e498] iad [info]2024-04-08T18:27:57.839Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling up number of shards to 2 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:27:59Z app[e82d41ec03e498] iad [info]2024-04-08T18:27:59.171Z  INFO quickwit_ingest::ingest_v2::routing_table: inserted 1 shards into routing table index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:28:34Z app[e82d41ec03e498] iad [info]2024-04-08T18:28:34.813Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling down number of shards to 1 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:28:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:28:41.781Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "searcher-287422ec6352e8", "metastore-784ee79fe23e58"]
2024-04-08T18:28:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:28:41.856Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 74ms
2024-04-08T18:29:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:29:41.781Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "searcher-0806603b656998", "indexer-28756d5c093408"]
2024-04-08T18:29:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:29:41.868Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 87ms
2024-04-08T18:29:55Z app[e82d41ec03e498] iad [info]2024-04-08T18:29:55.282Z  INFO quickwit_control_plane::indexing_scheduler: running tasks and last applied tasks differ: reapply last plan plans_diff=IndexingPlanDiff(missing_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []}, , unplanned_tasks_by_node_id={"indexer-28756d5c093408": [IndexingTask { index_uid: Some(IndexUid { index_id: "app-logs-164", incarnation_id: Ulid(2064201451011466848739298672857251088) }), source_id: "_ingest-source", pipeline_uid: Some(Pipeline(01HTYQCYYEGM9RYBB6E8H5MSDH)), shard_ids: [ShardId("01HTZDAAA2EJ06GWBFBGMFJVV2"), ShardId("01HTZFF2RG9X8JCWF3E1XJ7QHR")] }], "indexer-0806246b6e5258": [], "indexer-2875172c04e558": []})
2024-04-08T18:30:34Z app[e82d41ec03e498] iad [info]2024-04-08T18:30:34.081Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling up number of shards to 2 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:30:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:30:41.782Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["janitor-78423eec261148", "indexer-2875172c04e558", "searcher-0806603b656998"]
2024-04-08T18:30:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:30:41.841Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 58ms
2024-04-08T18:30:58Z app[e82d41ec03e498] iad [info]2024-04-08T18:30:58.750Z  INFO quickwit_ingest::ingest_v2::routing_table: inserted 1 shards into routing table index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:31:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:31:41.782Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-287422ec6352e8", "metastore-784ee79fe23e58"]
2024-04-08T18:31:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:31:41.839Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 57ms
2024-04-08T18:32:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:32:41.868Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 82ms
2024-04-08T18:33:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:33:41.784Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-286599efe1d068", "searcher-287422ec6352e8"]
2024-04-08T18:33:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:33:41.866Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 82ms
2024-04-08T18:34:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:34:41.785Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "janitor-78423eec261148", "metastore-784ee79fe23e58"]
2024-04-08T18:34:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:34:41.869Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 83ms
2024-04-08T18:35:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:35:41.786Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "searcher-286599efe1d068", "searcher-0806603b656998"]
2024-04-08T18:35:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:35:41.881Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 94ms
2024-04-08T18:36:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:36:41.786Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["janitor-78423eec261148", "searcher-0806603b656998", "metastore-48ed0d2a796358"]
2024-04-08T18:36:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:36:41.865Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 78ms
2024-04-08T18:37:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:37:41.788Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "metastore-48ed0d2a796358", "searcher-287422ec6352e8"]
2024-04-08T18:37:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:37:41.852Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 63ms
2024-04-08T18:38:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:38:41.786Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "indexer-2875172c04e558", "searcher-0806603b656998"]
2024-04-08T18:38:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:38:41.846Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 59ms
2024-04-08T18:38:58Z app[e82d41ec03e498] iad [info]2024-04-08T18:38:58.798Z  INFO quickwit_control_plane::ingest::ingest_controller: scaling down number of shards to 2 index_id=app-logs-164 source_id=_ingest-source
2024-04-08T18:39:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:39:41.786Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "searcher-287422ec6352e8", "janitor-78423eec261148"]
2024-04-08T18:39:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:39:41.847Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 60ms
2024-04-08T18:40:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:40:41.787Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "searcher-0806603b656998", "indexer-28756d5c093408"]
2024-04-08T18:40:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:40:41.862Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 74ms
2024-04-08T18:41:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:41:41.791Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-0806603b656998", "searcher-286599efe1d068"]
2024-04-08T18:41:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:41:41.860Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 68ms
2024-04-08T18:42:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:42:41.788Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "indexer-2875172c04e558", "searcher-0806603b656998"]
2024-04-08T18:42:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:42:41.849Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 61ms
2024-04-08T18:43:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:43:41.790Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "indexer-2875172c04e558", "indexer-28756d5c093408"]
2024-04-08T18:43:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:43:41.881Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 91ms
2024-04-08T18:44:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:44:41.790Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "metastore-784ee79fe23e58", "janitor-78423eec261148"]
2024-04-08T18:44:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:44:41.846Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 55ms
2024-04-08T18:45:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:45:41.791Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-784ee79fe23e58", "indexer-2875172c04e558", "indexer-28756d5c093408"]
2024-04-08T18:45:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:45:41.852Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 61ms
2024-04-08T18:46:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:46:41.792Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-0806603b656998", "indexer-28756d5c093408"]
2024-04-08T18:46:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:46:41.880Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 87ms
2024-04-08T18:47:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:47:41.794Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-286599efe1d068", "janitor-78423eec261148"]
2024-04-08T18:47:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:47:41.864Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 70ms
2024-04-08T18:48:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:48:41.791Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-0806603b656998", "searcher-287422ec6352e8", "indexer-28756d5c093408"]
2024-04-08T18:48:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:48:41.879Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 87ms
2024-04-08T18:49:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:49:41.793Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "searcher-286599efe1d068", "metastore-48ed0d2a796358"]
2024-04-08T18:49:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:49:41.853Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 59ms
2024-04-08T18:50:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:50:41.795Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["metastore-48ed0d2a796358", "searcher-287422ec6352e8", "indexer-28756d5c093408"]
2024-04-08T18:50:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:50:41.858Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 63ms
2024-04-08T18:51:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:51:41.796Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-0806603b656998", "janitor-78423eec261148"]
2024-04-08T18:51:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:51:41.859Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 63ms
2024-04-08T18:52:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:52:41.794Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["indexer-0806246b6e5258", "searcher-286599efe1d068", "metastore-48ed0d2a796358"]
2024-04-08T18:52:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:52:41.853Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 58ms
2024-04-08T18:53:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:53:41.796Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-0806603b656998", "metastore-48ed0d2a796358", "indexer-28756d5c093408"]
2024-04-08T18:53:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:53:41.856Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 60ms
2024-04-08T18:54:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:54:41.798Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-0806603b656998", "searcher-287422ec6352e8", "metastore-784ee79fe23e58"]
2024-04-08T18:54:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:54:41.851Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 53ms
2024-04-08T18:56:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:56:41.801Z  INFO quickwit_cluster::grpc_gossip: pulling cluster state from node(s): ["searcher-287422ec6352e8", "metastore-48ed0d2a796358", "indexer-28756d5c093408"]
2024-04-08T18:56:41Z app[e82d41ec03e498] iad [info]2024-04-08T18:56:41.857Z  INFO quickwit_cluster::grpc_gossip: pulled cluster state in 56ms

The bug was fixed in Chitchat but has not been deployed yet. I redeployed.

repo: quickwit-oss/quickwit


text:
Detach topology from LES

The current LES's are dependable on the topologies table. We need to merge them together in order for the LES to become independent of a topology.

When that's all done we need to move the old topologies to the template topologies. Can we than remove all the clones and variations or should we keep everything? @ChaelKruip do you have some insight into this.

Can we than remove all the clones and variations or should we keep everything?

I think we should remove everything unless it breaks/changes existing LESses. Also, please, please, keep a back-up of the databases.

Also, please, please, keep a back-up of the databases.

Yes 👍

authors: ChaelKruip grdw

repo: quintel/etmoses

license: mit


text:
Raidboss: Eden's verse consistency

I have modified names on replaceSync  fr and ja for more consistency with replaceSync de, text file and networks logs.
I know it is not particularly useful, it seems to me. But I find it more consistent that the names are the same and with their punctuation everywhere. Sorry again.

Sorry, I do not think this is worth doing.  I think there is inconsistency between the way the game displays things and the way network logs display things (and these also change over time).  As replaceSync is case insensitive, it is not worth changing these.
I do not mean to be rude here, but I think this is just not worth the time to change.

authors: VanSlanzar quisquous

repo: quisquous/cactbot


text:
Fix tests & replace System.out.println()

added additional constructor to fix tests
replaced System.out.println() with LOGGER.info() statements

Thank you to ChaosMarc for the improvements. --QC

authors: ChaosMarc quixotic-cynic

repo: quixotic-cynic/open-diablo-editor


text:
Add SocksSharp

Http/SocksSharp - https://github.com/extremecodetv/SocksSharp
SocksSharp provides support for Socks4/4a/5 proxy servers to HttpClient

Since initial review there was a little progress in regards with tests and core functionality so I'm closing the PR. We'd love to add it to the list when it'll become more mature project.

authors: extremecodetv zihotki

repo: quozd/awesome-dotnet


text:
Facebook/Twiter share

Ramadam to-do list #312
Some possible designs:
Ayah Share:

Surah share:

Or we can use the popover for the surah share, similar to the font size popover.

Thoughts?

[ ] Twitter/Facebook icons
[x] Twitter card and Facebook opengraph

@sabeurthabti looks awesome mashallah! :)

authors: mmahalwy sabeurthabti


text:
🛑 Adguard Home DoT is down

In f5bd743, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in bc9b8b3 after 1 hour, 9 minutes.

repo: quyleanh/upptime


text:
🛑 Adguard Home DoT is down

In 65f945c, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in 4b3de90 after 20 minutes.


text:
🛑 Adguard Home DoT is down

In 38e77ff, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in 7d2173d after 15 minutes.


text:
🛑 Adguard Home DoT is down

In e69513c, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in 2f8ec4b after 16 minutes.


text:
Fix macOS PKG architecture

Add hostArchitectures="x86_64,arm64" to the distribution.xml file.
References:

https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html#:~:text=list of supported architecture codes

Fixed by a766de5

repo: qwerty-fr/qwerty-fr


text:
History/Favourites/Blacklist empty

The program works okay, but the History/Favourites/Blacklist lists stay empty. Tried running it as Administrator as suggested in a previous issue, but it made no difference.

I'm having the same issue (ran as administrator or not)

@kroese @Vorenu5 Can you please upload a copy of the logs? Restart the program, then upload via About -> Log File -> Upload Log, then paste the link. Or upload the file manually, it should be located in C:\Users<Your User Name>\AppData\Roaming\Reddit Wallpaper Changer\Logs\RWC.log

RWC.log

Update: Uninstalling, then deleting everything in "C:\Users\AppData\Roaming\Reddit Wallpaper Changer", then reinstalling and running first time as administrator fixed this issue for me. SQL database has valid tables and are updating now.

Fixed in #6

authors: Vorenu5 kroese qwertydog

repo: qwertydog/Reddit-Wallpaper-Changer


text:
🛑 Home Assistant is down

In 47b71a5, Home Assistant ($SECRET_SITE_HA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Home Assistant is back up in 19fe095.


text:
Provide examples for common cases of permission configurations

E.g. limiting a connection to only publishing to a set of existing exchanges.

Mostly addressed in the revisited Access Control guide.

repo: rabbitmq/rabbitmq-website


text:
Make the Atom feed valid

This PR does a few things to ensure that the currently invalid Atom feed is made valid. The feed started out with the following list of warnings:
$ python src/demo.py http://localhost:8191/news.atom
Validating http://localhost:8191/news.atom
line 2, column 0: Use of unknown namespace: http://www.rabbitmq.com/namespaces/ad-hoc/doc
line 2, column 0: Avoid Namespace Prefix: atom
line 2, column 0: Avoid Namespace Prefix: xhtml
line 2, column 168: updated must be an RFC-3339 date-time
line 2, column 0: Missing feed element: title
line 2, column 0: Missing feed element: id
line 2, column 0: Missing atom:link with rel="self"
line 2, column 342: updated must be an RFC-3339 date-time (57 occurrences)
line 29, column 33: Missing entry element: author (100 occurrences)
line 1993, column 13: p contains bad characters (2 occurrences)

Which should all be gone after merging this and doing xsltproc site/feed-atom.xsl site/news.xml > site/news.atom to generate a new news.atom feed.

Thank you!

authors: asbjornu michaelklishin


text:
update elixir client 1.0 -> 3.3

Using the 1.0 client in the example leads to connection errors.

@mkumm Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@mkumm Thank you for signing the Contributor License Agreement!

authors: mkumm pivotal-cla


text:
Allow no dedicated master in ES domain

You can create ES with no dedicated masters. Current module does not allow for this by saying that if master_node_count is not > 0 then the provided answer to the ES call is an empty string which does not satisfy the constraint of the service.
Change here makes the default behaviour to be no dedicated master.

Fixed definition of variable snapshot_start_hour which was not surrounded in quotation marks


text:
Tweak the API to handle initial state correctly

I know this is going to be controversial..
I think it’s wrong that the middleware dispatches during its creation. We probably won't allow it in next versions of Redux anyway.
The fact that this dispatch happens too early also caused https://github.com/rackt/react-router-redux/issues/252. When the initial state is specified to the store and we “listen to replays”, we want the state to be the source of truth in the absence of user action. So if we load a location from localStorage and pass it into the initial state, whether with devtools or not, we want the URL to be set from it.
Since we need to extract a method to cause the initial dispatch anyway, I thought I might as well unite these two methods and turn them into options:
middleware.syncWith(store, {
  urlToState: true, // reflect URL changes in the state (useful in app)
  stateToUrl: false // reflect state changes in the URL (useful for replays, DevTools, etc)
})

I know not everybody is a fan of named arguments so I’m very open to suggestions here. My reasoning for uniting these two methods was the fact that:

You have to call them in the right order (or we need to implement safeguards)
You never need to call them twice

Therefore having to call one or two methods just to get the thing working seems like overkill. Additionally, named arguments explain what actually happens in very straightforward two-way binding terms, which is what this library actually is: two-way bindings from URL to a state field.
If you think this API sucks I’ll be happy to rewrite this to your API of choice. The primary purpose of this PR is still to fix #252, and I added a couple of new tests verifying that it is indeed now fixed.
This PR updates tests, example, and first part of the README. I am happy to update the API usage part when/if we agree on the API.

No idea why some tests fail on Firefox with store is undefined :-(. Tests pass locally.

Note: most changes in src diff are just reindent.

Why have the middleware at all? Structurally, this seems sound. Why not make it a store enhancer?
Also, should the syncing default to opt in? If this works well, I'd want everyone to use it by default and have an option to disable for edge cases.

Looks like a magic :+1:

Yeah store enhancer might be a nicer fit. I’ll give it a go.

I'm in the middle of a big project at work, so I don't have a lot of time to think about this right now, but this looks like an interesting approach. Why have the named parameters at all though? Is there are reason we can just enable both by default and not make it configurable? The only reason for listenForReplays to exist is to get the store->router sync working, but if that call is going to initialize everything I don't see why we can do the bidirectional sync all the time.
My only concern is API churn. I know that we want to find the right API and it's probably worth it, but I hate having to ask users to change again. There's already a feeling of too many moving parts with the various libraries, and I wish we could make it smoother somehow. This change only affects where you init everything, but you mentioned a bigger change in https://github.com/rackt/react-router-redux/issues/248#issuecomment-179265532 that would affect everyone who reads from the state. I like the idea, but a lot of people probably aren't going to be happy about hiding the routing state (they've been pushing for route params to be in there, so this is going to opposite direction, but I actually agree with it).

I don't mean this as a final API (especially regarding the named arguments etc). I also don't mind creating another library to handle that if you feel it's out of scope.
It's just I feel that asking user not to subscribe to a part of their store is sketchy. Using middleware for stateful things is also sketchy (e.g. I think current version might be broken if you create two separate stores because it keeps shared state). The persistence support is one of the goals of this library, so I think #252 needs to be fixed, even if without revamping the API.

Superseded by https://github.com/rackt/redux/pull/1362.

authors: awinogradov gaearon jlongster timdorr

repo: rackt/react-router-redux


text:
Bug: ractive.set() breaks data-binding

Hi,
here is the fiddle:
http://jsfiddle.net/xc2o8y08/6/
...it's rather strange and depends on a lot of conditions.
Works with latest, broken on edge.

Updated the fiddle, it had nothing to do with the partial but with a simple set:
http://jsfiddle.net/xc2o8y08/8/

Here's a few interesting cases:
It works when you reverse the order of the select and the component.
Ractive.components['comp'] = Ractive.extend({
  template: "
{{yield}}
"
})

var ractive = new Ractive({
  el: 'body',
  template: `
  	{{#with foo}}
      Outside:
      <select value="{{.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
      </select>
      <comp>
        In a component:
        <select value="{{.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
        </select>
      </comp>
    {{/with}}
  `
})

ractive.set('foo', {})
ractive.set('foo', {})

It works when something else is bound in the tempate. In this case, the JSON.stringify(.bar). Even JSON.stringify(.) works.
Ractive.components['comp'] = Ractive.extend({
  template: "
{{yield}}
"
})

var ractive = new Ractive({
  el: 'body',
  template: `
  	{{#with foo}}
      <comp>
        In a component: {{ JSON.stringify(.bar) }}
        <select value="{{.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
        </select>
      </comp>
      Outside: {{ JSON.stringify(.bar) }}
      <select value="{{.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
      </select>
    {{/with}}
  `
})

ractive.set('foo', {})
ractive.set('foo', {})

Direct foo.bar doesn't work, but again, anything else bound in the template will make it work.
Ractive.components['comp'] = Ractive.extend({
  template: "
{{yield}}
"
})

var ractive = new Ractive({
  el: 'body',
  template: `
      <comp>
        In a component:
        <select value="{{foo.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
        </select>
      </comp>
      Outside:
      <select value="{{foo.bar}}">
          <option></option>
          <option>A</option>
          <option>B</option>
          <option>C</option>
      </select>
  `
})

ractive.set('foo', {})
ractive.set('foo', {})

Another more impressive example:
http://jsfiddle.net/xc2o8y08/24/
...this is seriously broken guys!

Looks like this is fixed too :smile:

authors: dagnelies evs-chris fskreuz

repo: ractivejs/ractive


text:
Computed array's dependent fragments not updating (edge, ractive-datatable)

Description of the bug:
Ractive is not updating a computed array's dependent DOM fragments even though the computed is getting updated in the viewmodel. Check out the edge demo of ractive-datatable here. Generate some data, then change pages. Nothing happens except for when reaching the last page. You can verify that the rows computation is getting recalculated correctly by placing a breakpoint or running main.findAllComponents()[0].get('rows'). However, the DOM is not being updated to reflect the new values of the rows computation.
Versions affected:
0.8-edge
Platforms affected:
Chrome 50
Reproduction:
http://jondum.github.io/ractive-datatable/demo/edge.html
Code:
<datatable data='{{data}}'></datatable>

{{#rows:r}}
    <tr {{#if selectionMode == 'row' && _selection.indexOf(index) !== -1 }}class='selected'{{/if}} on-
        ...
    </tr>
{{/}}

rows: function() {
    var self = this;

    var page = self.get('page') - 1;
    var _data = self.get('_data');
    var perpage = self.get('perpage');
    var total = self.get('total');

    // the original data, unfiltered
    var data = self.get('data');

    return _data.slice(page * perpage, Math.min(page * perpage + perpage, total));
},

Interestingly, if you go to a page that changes the length of the displayed result set, then it rerenders as expected.

Maybe something to do with equality checking the objects? Since it has the same length it goes to check each item in the array but it's not passing the equality check? The rows array looks like this:
[ {
    item: {
        ...
    },
    index: 30
}, ...]

I verified that after changing a page rows[0] !== rows[0] though. Hmm.

I've tracked this down to an issue with the content of the column partial not being flagged as dirty because it doesn't exactly depend on any of the values that are changing. I'm thinking it's a bug with how the expression proxies notify and/or are notified about changes.

Just wanted to note that the events aren't working because the pre-compiled template is not compatible with expression events.

Tested it out on edge and works with raw template string 👍 .
So I guess this should only be a problem now until 0.8 drops to NPM (if you use the prebuilt version).
If you use the version in src it should work fine as long as you have ractive-loader set up to use 0.8-edge.

authors: JonDum evs-chris


text:
8 failing tests

Just tried to use the gem but there are 8 failing tests for me (ruby 2.1.1):
Just putting these here, I will try to investigate more when I have more time.
  1) A better distance_of_time_in_words distance of time 14515200 == 5 months and 15 days
     Failure/Error: expect(distance_of_time(number)).to eq(result)

       expected: "5 months and 15 days"
            got: "5 months and 14 days"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:30:in `block (4 levels) in <top (required)>'

  2) A better distance_of_time_in_words real version should be 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true)).to eq(output)

       expected: "1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds"
            got: "1 year, 2 months, 3 days, 3 hours, 5 minutes, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:101:in `block (4 levels) in <top (required)>'

  3) A better distance_of_time_in_words real version without finish time should be 5 months and 15 days
     Failure/Error: expect(distance_of_time_in_words(start)).to eq(output)

       expected: "5 months and 15 days"
            got: "5 months and 14 days"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:148:in `block (5 levels) in <top (required)>'

  4) A better distance_of_time_in_words with output options should be 1 year - 2 months - 3 days - 4 hours - 5 minutes, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true, options)).to eq(output)

       expected: "1 year - 2 months - 3 days - 4 hours - 5 minutes, and 6 seconds"
            got: "1 year - 2 months - 3 days - 3 hours - 5 minutes, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:232:in `block (4 levels) in <top (required)>'

  5) A better distance_of_time_in_words with output options should be 1 year, 2 months, 3 days, 4 hours, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true, options)).to eq(output)

       expected: "1 year, 2 months, 3 days, 4 hours, and 6 seconds"
            got: "1 year, 2 months, 3 days, 3 hours, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:232:in `block (4 levels) in <top (required)>'

  6) A better distance_of_time_in_words with output options should be 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true, options)).to eq(output)

       expected: "1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds"
            got: "1 year, 2 months, 3 days, 3 hours, 5 minutes, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:232:in `block (4 levels) in <top (required)>'

  7) A better distance_of_time_in_words with output options should be 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true, options)).to eq(output)

       expected: "1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds"
            got: "1 year, 2 months, 3 days, 3 hours, 5 minutes, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:232:in `block (4 levels) in <top (required)>'

  8) A better distance_of_time_in_words with output options should be 1 year, 2 months, 3 days, 4 hours, and 6 seconds
     Failure/Error: expect(distance_of_time_in_words(start, finish, true, options)).to eq(output)

       expected: "1 year, 2 months, 3 days, 4 hours, and 6 seconds"
            got: "1 year, 2 months, 3 days, 3 hours, and 6 seconds"

       (compared using ==)
     # ./spec/lib/dotiw_spec.rb:232:in `block (4 levels) in <top (required)>'

Take a look at #41 and comment if you have time!

repo: radar/dotiw


text:
Emacs daemon created by systemd dosen't work

What's wrong
If i try to create the daemon with systemctl --user start emacs (or enable it with  systemctl --user enable emacs  and restart the session), the process is created but systemctl remain blocked for a while and gives a timeout error. The emacsclient doesn't find the daemon.
This happends only with straight.el bootstrap code
Directions to reproduce

use any .emacs.d folder that has the  straight.el bootstrap code in the init.el file
try to start the emacs daemon with systemctl --user start emacs

Version information

Emacs version: 28.2 (i tried even with emacs 27 an there is the same problem)
Operating system: Arch linux

I get this:
% journalctl --user -efu emacs
Feb 25 10:32:04 wit systemd[5009]: Starting Emacs text editor...
Feb 25 10:32:04 wit emacs[645356]: Warning: due to a long standing Gtk+ bug
Feb 25 10:32:04 wit emacs[645356]: https://gitlab.gnome.org/GNOME/gtk/issues/221
Feb 25 10:32:04 wit emacs[645356]: Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
Feb 25 10:32:04 wit emacs[645356]: Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.
Feb 25 10:32:04 wit emacs[645356]: Rebuilding all packages due to change in Emacs version
Feb 25 10:32:04 wit emacs[645356]: Building straight...
Feb 25 10:32:04 wit systemd[5009]: emacs.service: Got notification message from PID 645358, but reception only permitted for main PID 645356
Feb 25 10:32:04 wit emacs[645356]: Building straight...done
Feb 25 10:32:04 wit emacs[645356]: Building use-package...
Feb 25 10:32:04 wit emacs[645356]: Building use-package → Building bind-key...
Feb 25 10:32:04 wit systemd[5009]: emacs.service: Got notification message from PID 645375, but reception only permitted for main PID 645356
Feb 25 10:32:04 wit emacs[645356]: Building use-package → Building bind-key...done
Feb 25 10:32:04 wit emacs[645356]: Building use-package...

Emacsclient is able to start and connect to the server successfully.
This is Emacs 28.1 on Pop!_OS 22.04.

I retried to test my config file and understood that straight.el has nothing to do with the problem, sorry for the mistaken bug report

Not  a problem. Thank you for letting us know.

authors: SimoriccITA progfolio raxod502


text:
🛑 GPS Receiver API is down

In 75d658f, GPS Receiver API (http://tracker.ace-energy.co.th/receiver/api/v1/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GPS Receiver API is back up in b6d6eff.

repo: radiuszon/upptime


text:
Primitive initial dom render loading issues

Bug report
Current Behavior
Radix Navigation Menu and Popover are behaving weird on the initial dom load. The navigation menu renders vertically for a split second and then correctly goes horizontal. However this looks weird and ugly as none of the css has been applied. I've tried the exact same example in the docs, and it gives me the exact same behaviour.
Popovers are also moving weirdly on the initial load.

Expected behavior

I expect the navigation menu to render horizontally on the initial dom load, and not vertically for a split second.
Reproducible example
Suggested solution

The menu would need to load correctly on the initial render.
Your environment

Software
Name(s)
Version

Radix Package(s)
Navigation Menu, Popover
1.1.1 , 1.0.2

React
n/a
18.2

Browser
All browsers
Newest versions

Assistive tech

Node
n/a
16.18.0

npm/yarn
8.19.2
1.22.19

Operating System
Windows
11

@Mbensler Seems like an issue with SSR rendering and your styling configuration rather than Radix specifically, what’s your stack?

Could you provide a sandbox code sample matching your configuration or an example github repro? I'm not familiar with styling custom components with chakra but it seems like the SSG step is not pre-rendering your styles, rather they are being hydrated by the bundle only.

I got it working by following the stitches SSR documentation: https://stitches.dev/docs/server-side-rendering
Even though I use SSG the SSR method works, and it seems it's necessary to have for Radix primitives to be pre-rendered.

Ah I didn't realise you were also using stitches here. Generally the pre-rendering of markup / styles will be similar whether it's static generation (SSG) or a server side response (SSR). To be clear though, stitches isn't required for Radix, you could use any css-in-js, tailwind or plain css solution.
But as you say, regardless of the library, most css-in-js will provide a method to make sure styles are applied prior to hydration, i'm happy you resolved it for Stitches in this case 👍

Hello again, I'm experiencing a related issue with the navigation menu.
Liked mentioned before I am using Stitches and this time with the provided example at: https://www.radix-ui.com/docs/primitives/components/navigation-menu
I have copy pasted the code from the navigation menu demo from the link above.
My stitches SSR config looks like this:
import { createStitches, keyframes } from '@stitches/react';
import * as PopoverPrimitive from '@radix-ui/react-popover';
export const { styled, getCssText } = createStitches({
  theme: {
    colors: {},
    space: {},
    fontSizes: {},
    fonts: {},
    fontWeights: {},
    lineHeights: {},
    letterSpacings: {},
    sizes: {},
    borderWidths: {},
    borderStyles: {},
    radii: {},
    shadows: {},
    zIndices: {},
    transitions: {},
  },
});

That SSR code is what solved my previous problem. However it seems there is something wrong with the SSR/SSG rendering.
I have attached a video showing my problem.
https://user-images.githubusercontent.com/3165204/197991814-78695196-24c7-4e37-aa27-d187489f8406.mp4
I have no idea how to solve this. I feel like I've tried everything.

@Mbensler Can you provide a minimal github repo with a matching configuration that demonstrates this problem?

Hello sorry for the late response. I've made a quick and dirty demo displaying the error.
Github repo can be found here: https://github.com/Mbensler/primitiveSSRdemoError
Demo can be found here: https://testdemo-ten.vercel.app//
Let me know if you need any additional details. Thanks in advance.

@Mbensler Your components should be consuming methods from the instance returned by createStitches. In your case you need to update the destructure to include keyframes from createStitches rather than @stitches/react.
You also have a mixture of responsibilities here, I recommend moving all components out of stitches.config and making it only responsible for setting up the stitches configuration and exposing the methods which the components should be consuming.
Here is a simplified example repo showing the menu functioning correctly after a build and serve.
https://github.com/andy-hook/primitiveSSRdemoError
I recommend joining the Stitches channel on our discord if you haven't already, the community are very good at providing guidance on best practice and styling architecture.
I'm going to close this issue now but I hope this helps 🙏 .

authors: Mbensler andy-hook

repo: radix-ui/primitives


text:
feat: add new-york style components

Describe the feature
I just added most of the components in the new-york style, I hope it helps. I think the remaining components have no difference between the default and new-york styles.
Additional information

[x] I made a PR for this feature.
[x] I have already implemented and/or tested this feature.

Hello! @zernonia, I just completed all the components in the new york style, you can merge it with the rest of the work 😃

repo: radix-vue/shadcn-vue


text:
Memory leak in JLI_StringDup

zcash4mac 1.0.4-208
Steps:
Launch zcash4mac.
What happened:
Memory leak in JLI_StringDup
https://www.dropbox.com/s/pf54fy2ge7yx5o9/zcash4mac.trace.zip?dl=0
Expected result:
No leaks.
Notes:
Unzip and open file with Apple Instruments (part of Xcode tools).

This project is dead so retracting.


text:
ML node

Thank you for this excellent example, I have successfully used it to set up similarity search.
I am wondering how the pre-trained model in elasticsearch is utilized. I have an ML node in elastic cloud and I have imported the pre-trained model but I am unclear on if those things are necessary. I am already using sentence-transformers to extract image embeddings in my application - how is the model loaded into elasticsearch used?
If I can get rid of the ML node in elastic cloud, I can substantially reduce cost.

Hello @threewordphrase !
Thanks for your feedback. I am glad to see that you were able to successfully deploy the example.

how is the model loaded into elasticsearch used?

When you create a vector (image embedding) from your image, store it in Elasticsearch in an index; then you have your vector database of image embeddings.
When searching your images based on the generated vectors, you need a vector to search against them. In the case of this application, the "searching" vector is generated from the text query from the search bar. The vectorization of the text utilizes the NLP model loaded in Elasticsearch. This model can convert the search text to a vector and then use that vector as a "query term" for the vector database.
So, the model in Elasticsearch is used to convert the text to a vector for your search against images.
Having the model in Elasticsearch is very convenient because you do not need to utilize other infrastructure, and it uses Elasticsearch API for the _inference.
Note that the model to create image embeddings (from binary data to vector) and the model to generate vectors from your search text must be compatible (dimensions, type, learning content)
I hope this helps and if you want, you can read more on the topic in a miniseries I wrote. There are 3 parts.
1, 2 and 3
Feel free to let me know if you have more questions.

I am closing this one for now. If you have more questions, feel free to reopen.
Thanks

authors: radoondas threewordphrase

repo: radoondas/flask-elastic-image-search


text:
Move DOAP file to correct location

The filename had a trailing space at the beginning; fix it by renaming the file.

Thanks!

authors: knuxify rafaelmardojai

repo: rafaelmardojai/forge-sparks


text:
V3/attrs expansion

Feature or improvement description
This pull request further expands the usage of attrs and numpy workflows. A docstrings linter has also been added with some changes in annotations types.
This is marked as a draft because there are a couple of spots where I have questions regarding a change in typing methods and numpy methods that I'd like your feedback on @rafmudaf. If we go with the NumExpr speedup methods, then the numpy typing won't be available to us because numba is a dependency and has the version of numpy prior to the testing subpackage as a requirement.

@rafmudaf, this should be ready to be merged and incorporated in your branch now. I didn't touch every possible instance, but instead focused on the primary src/ level modules (except utilities) so nothing gets changed too much all at once.

@RHammond2 do you know what's going on with the failing tests here? I haven't looked into it, but I can take that on if you haven't.

@rafmudaf I took care of it, it was a pretty simple fix.

@rafmudaf everything should be all set now!

repo: rafmudaf/floris


text:
Different precompiled files with same code

When I precompile the same css in two servers I get differents css minimized. I don't know the reason of this issue,I have the same config (config.assets.css_compressor = :sass)
For example one part of the unpacked minimized css in server 1 is like this (the same that the real file) :

.c3-tooltip
{
    border-collapse:collapse;
    border-spacing:0;
    background-color:#fff;
    empty-cells:show;
    -webkit-box-shadow:7px 7px 12px -9px #777;
    -moz-box-shadow:7px 7px 12px -9px #777;
    box-shadow:7px 7px 12px -9px #777;
    opacity:0.9
}

Then in server 2 I get this (webkit-box-shadow and -moz-box-shadow were removed):

.c3-tooltip
{
    border-collapse:collapse;
    border-spacing:0;
    background-color:#fff;
    empty-cells:show;
    box-shadow:7px 7px 12px -9px #777;
    opacity:0.9
}

how are you getting that info?
Are you doing curl calls to 2 different servers and seeing different results?
Not sure how to simulate this issue, if you could provide a sample app would help out.
thanks

I have a loadbalancer with different servers and sometimes the stylesheets are were not loaded. I checked the names of the css compressed files and in one server I have a different fingerprint. Next uncompressing the files with (http://cssunpacker.com/) I realize that one of the servers when compress the css is removing some -webkit, -moz  and other syntaxis.

one server I have a different fingerprint

This means that the file content is not the same. Something is generating different files in your server.
If the code is the same and the version of the gems are the same I don't see why sprockets would generate different results. Make sure that your assets folders and dependencies are the same.

Yes, the compressed file in one server remove some lines as shown in the first comment. I just realize that most of the files that have this problem have ".css.scss" extension and files with .sass extension don't have this problem. Could be something related with this? I know that in the latest version of sass-rails the .css.scss extension is deprecated.

Don't think so. Given the same environment and the same code, I don't see how the files would be different. I'd make sure that the environment is the same in both servers first (gem versions, dependencies versions, assets code)

It's the same code and gem versions. The deploy in both servers use the same branch. In the server with the problem if I check the non precompiled assets It's exactly the same of the other server, but when I compress it, some attributes as shown in the first comment were removed.

Does that code being generated by some gem like compass or bourbon? Seems only the prefix styles are missing, but the box-shadow is there.

No, the only difference are that in the server of the problem I'm using AWS opsworks with some chef recipes and I don't have rbenv configured, It's possible that some of this is cousing this issue? (I use the default recipes of opsworks rails layer). The box-shadow is there in both servers, the compression remove the whole line "-webkit-box-shadow" and "-moz-box-shadow".Thanks, I would really appreciate any help or comments about this issue.

"-webkit-box-shadow" and "-moz-box-shadow"

In our sass code are these properties generated by some kind of mixin?
Like:
@include box-shadow(7px 7px 12px -9px #777);

Not having rbenv configured can be a reason for this yeah, if that means that global gems installed on the machine are affecting your application, but I'd guess bundler would protect you.

not, It's not generated by some kind of mixin, they are in some imports of scss from the application.sass with normal css syntax.

:confounded: so this is now even more weird. If it is just normal css syntax I can't see how this same file can be different in different servers.

yes is very weird. Finally I give up with this issue and decided to use the gem 'asset_sync' to upload the assets on s3.

RAILS_ENV=production rake assets:precompile on server dropped
  font-family: "ヒラギノ丸ゴ ProN W4", "Hiragino Maru Gothic Pro", "メイリオ", Meiryo, Helvetica, sans-serif
  -webkit-tap-highlight-color: rgba(0, 0, 0, 0)
  -ms-text-size-adjust: 100%
  -webkit-text-size-adjust: 100%

from html section
on local machine not

The same is happening to me  my css vendor prefixes are removing in production enviroment but not in my local machine. Here you can get more info http://stackoverflow.com/questions/32179803/rails-removing-css-vendor-prefixes-in-production-enviroment

authors: Fudoshiki agrass arthurnn ekaitzht rafaelfranca

repo: rails/sass-rails


text:
Setup development to work with solid_queue out of the box

When starting a new 8.0 rails project it doesn't fully setup solid_queue as I might expect.
It doesn't configure the following in development:

active_job.queue_adapter
solid_queue.connects_to
config/database.yml

It'd be nice if I could just start solid queue right away in development with a new Rails 8.0 project.

Related: https://github.com/rails/solid_queue/pull/390

Ahh, didn't see that one! Cheers.
Duplicate of https://github.com/rails/solid_queue/pull/390

authors: joelzwarrington rosa


text:
How to use with ActsAsTenant?

Describe the bug
Install rails_admin into a Rails 7 app (that uses bootstrap so it is not using imagemap) and attempt to hit the base admin URL (eg /admin).
Get a stack trace:
ActsAsTenant::Errors::NoTenantSet in RailsAdmin::MainController#dashboard

[acts_as_tenant (0.5.1) lib/acts_as_tenant/model_extensions.rb:20:in `block in acts_as_tenant'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:157:in `instance_exec'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:157:in `block (2 levels) in build_default_scope'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:153:in `each'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:153:in `inject'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:153:in `block in build_default_scope'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:189:in `evaluate_default_scope'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/default.rb:152:in `build_default_scope'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/named.rb:46:in `default_scoped'](https://postwrangler.ngrok.io/pwadmin#)
[activerecord (7.0.2.3) lib/active_record/scoping/named.rb:32:in `all'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/adapters/active_record.rb:23:in `scoped'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/adapters/active_record.rb:31:in `all'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/adapters/active_record.rb:43:in `count'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/config/actions/dashboard.rb:31:in `block (3 levels) in <class:Dashboard>'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/config/actions/dashboard.rb:29:in `each'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) lib/rails_admin/config/actions/dashboard.rb:29:in `block (2 levels) in <class:Dashboard>'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) app/controllers/rails_admin/main_controller.rb:36:in `instance_eval'](https://postwrangler.ngrok.io/pwadmin#)
[rails_admin (3.0.0) app/controllers/rails_admin/main_controller.rb:36:in `action_missing'](https://postwrangler.ngrok.io/pwadmin#)

Additional context

rails version: 7.0.3
rails_admin version: 3.0.0

Seems this is not a RailsAdmin issue, but an ActsAsTenant one.