text:
add the function of check site symmetry

Ideally, we need to check the site symmetry after we do each wyckoff merge.
No check is needed if there is no merge.

@scottfredericks , I think you can enable the function of check_wyckoff_position() in the merge_coordinate function.
something like the followings,
                merged = np.array(merged)
                if check_wyckoff_position(merged, sg, wyckoffs) is not False:
                    coor = merged
                else:
                    return coor, False

@scottfredericks  please fix the following bug shown in bug.py

in check_wyckoff_position()
    for i, wp in enumerate(wyckoffs):
        w_symm = w_symm_all[i]
        if len(p_symm) == len(w_symm):
            temp = w_symm
            for p in p_symm:
                for w in temp:
                    if p == w:
                        temp.remove(w)

p/w contains the information for both rotation (rot) and translation (tau) operation.
sometimes, tau of p might return an array of [1.5, 1.5, 1.5]
while tau of w might be [0.5, 0.5, 0.5]
This should be equivalent.
@scottfredericks please enable the periodic boundary condition check for this case.

@scottfredericks
Problem:
We generate site_symmetry from general wyckoff position, while we compare it with the data from a database in csv file.
However, they might differ in the translation vector.
This happens not only in A/B/C/F/I cells, also in P cells. Below is case for P4mm (99)
------ site symmetry from our code------------
['x, y, z', '-y+1, -x+1, z']
['x, y, z', '-y+1, -x+1, z']
['x, y, z', 'y, x, z']
['x, y, z', 'y, x, z']
------ site symmetry from database------------
['x, y, z', 'y, x, z']
['x, y, z', 'y, x, z']
['x, y, z', '-y, -x, z']
['x, y, z', '-y, -x, z']

Solution:
generate a new list of wyckoff database to make it is consistent with the way generated from general wyckoff position.

It seems site_symm() is automatically converting negative coordinate values
into positive ones (due to SymmOp.from_xyz_string()). For example, [
0.23631801, -0.23631801, -0.06786002] is encoded as [ 0.23631801
0.76368199  0.93213998] within the function. As a result, the coordinates
are interpreted as 'x, -x+1, z' instead of 'x, -x, z'. I will see if there
is a way to prevent this automatic filtering.

an attempt to fix the issue a99a03157e976840506335e1c41ae2821e272439

The problem was actually in my code, not the SymmOp class. I removed a line
which filtered out negative values. The code now works for coordinates
generated directly from the Wyckoff position (using negative values for -x,
etc.) However, if we input only positive values, the code still produces
the same error. For now, we can avoid this by keeping negative values
during merge_coordinates. In the future, we need a way to recognize
already-filtered values; this will depend on the other coordinates being
checked, and will likely require trying a mapping for x, y, and z, and
making sure all other coordinates in the set work with the same mapping.

I have updated wyckoff_list.csv to include values such as "x+1", and I've updated wyckoff_symmetry.csv based on this new wyckoff position databaes. As long as negative values are carried over from the general position, check_wyckoff_position now works. However, I am not sure if merge_coordinates uses this method, because check_wyckoff_position(merged, sg) still fails very often during crystal generation (note that the text output for the failure is currently commented out).

@scottfredericks, I suggest add an option of considering periodic boundary condition here. When we check the site symmetry for the merged coordinate, we don't really need to know the exact wyckoff letters. So the ambiguity of two wyckoff sites with same rotational matrices and different translation vector is not an issue in this case.
def check_wyckoff_position(points, sg, wyckoffs=None, pbc=False):
      """
      pbc: if we check the translation vector by periodic boundary condition. Default: False
      """

@scottfredericks  A recent test:
-----------------Species:[3], NumIons:[8]----------------------
Space group  requested:  2 generated 2
Space group  requested:  3 generated 3
Space group  requested:  4 generated 4
Space group  requested:  5 generated 5
something is wrong
[[ 0.85097362  0.43820877  0.86841429]
[ 0.85097362 -0.43820877  0.86841429]]
[[-0.14902638 -0.5        -0.13158571]]
6
[x, 0, z] should be a valid wyckoff position for space group Pm

@scottfredericks
For space group 210, below is another set of data from my test,
[[-0.25 -0.25 -0.25]
[ 0.25 -0.25  0.25]
[ 0.25  0.25 -0.25]
[-0.25  0.25  0.25]
[-0.5   0.    0.  ]
[ 0.5  -0.5   0.5 ]
[ 0.    0.5   0.  ]
[ 0.    0.   -0.5 ]]
This should be wyckoff 8b. But it was missed by your code.

I have added another fix. The temporary arrays used within check_wyckoff_position were being generated using = instead of deepcopy. As a result, they were not being copied correctly. I have added a test script, test_wyckoff_check.py. This script generates points from Wyckoff positions using random (possibly negative) xyz coordinates, then randomly adds a value of (-1,0, or +1) to each point. Then, it runs check_wyckoff_position on these points. I have ran it twice, and it passed both times. It might be good to run it a few more times to make sure we aren't just lucky.

looks like this issue has been resolved


text:
Update tox to python 3.7

It's been a few months since Python received a minor version upgrade (3.7). As it is (of course) downwards compatible and it should be encouraged to use up to date software, I would suggest to use python 3.7 as default interpreter in tox.

@moritzschaefer Are you working on this issue?  Would you be okay if I jumped in?

@moritzschaefer Hey!  Thanks for letting me know.  Want to jump back into the project after making a small change.  I will let you continue.

There are backwards incompatible features in 3.7. to ensure we remain Py3.6+ you'll actually have to run testing under both Python interpreter versions.
TravisCI can be configured with Tox to also run a matrix of interpreters.
My bid: do not drop Py3.6 testing.

I agree with clintval - lets not force this move just yet.

source: gharchive/issue

authors: apfejes clintval moritzschaefer vghorakavi

repo: r-bioinformatics/edgePy

license: MIT

license_type: permissive

license_source: github-api


text:
Move to a named logger.

Move to a logger named git_theta so that we don't edit the default logger which causes other libraries we use to output all of there logs too.
Now only git-theta logs get output unless other loggers are configured.

One clear advantage is that this suppressed the GitPython log message about not being in a CYGWIN environment which multiple people have though was an error in their git-theta install

Closes https://github.com/r-three/git-theta/issues/93

source: gharchive/pull-request

repo: r-three/git-theta


text:
🛑 Sistarbanc is down

In 4f18ef0, Sistarbanc ($SISTARBANC_URL) was down:

HTTP code: 503
Response time: 2429 ms

Resolved: Sistarbanc is back up in 343b901.


text:
Remove invalid Windows characters

Hello,
I found another issue with this program. On Ubuntu, it downloads folder names and file names as they are and doesn't check if there are any invalid Windows characters. For an example of characters I am talking about, check this link: https://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names
Basically, I feel that this program should replace the invalid Windows characters with a different character, or with nothing else.
Thank you.

@ipkpjersi it already cleans up that for windows have a look at this issue #29.

It did not work for me, at least for folder names: https://i.imgur.com/WhTjK6U.png
As you can see, it has : in the folder name which as far as I know, is one of the invalid Windows characters.

@ipkpjersi can you please clone the latest repo available here on github and try once?
a POC code which checks for windows

.

I have just spotted the issue. You only remove the special Windows characters if the OS is windows, but I want it removed regardless that way if you download videos on Mac or on Linux, you can still use them all just fine on Windows too. I think this would be a great enhancement for this program.

@ipkpjersi this is not the issue for the 1st because i am skipping this part for Mac and Linux intentionally  as both of these Operating Systems  don't have a problem with naming convention.  Thanks for suggestion i am taking this suggestion as future enhancement.  for now i think this is not the problem for many users.


text:
fix(ksp): Add more meaningful error message when KSP cannot detect default value

Some time ago we fixed error which prevent using navArgsDelegate from different module (#261).
Today I tried to use data class with default parameter value, but I've got an error:
[ksp] java.lang.ClassCastException: class com.google.devtools.ksp.symbol.NonExistLocation cannot be cast to class com.google.devtools.ksp.symbol.FileLocation (com.google.devtools.ksp.symbol.NonExistLocation and com.google.devtools.ksp.symbol.FileLocation are in unnamed module of loader java.net.URLClassLoader @713ec06c)
	at com.ramcosta.composedestinations.ksp.commons.DefaultParameterValueReaderKt.getDefaultValue(DefaultParameterValueReader.kt:180)
	at com.ramcosta.composedestinations.ksp.processors.KspToCodeGenDestinationsMapper$toParameter$2.invoke(KspToCodeGenDestinationsMapper.kt:270)
	at com.ramcosta.composedestinations.ksp.processors.KspToCodeGenDestinationsMapper$toParameter$2.invoke(KspToCodeGenDestinationsMapper.kt:270)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
	at com.ramcosta.composedestinations.codegen.model.Parameter.getDefaultValue(Parameter.kt:10)
	at com.ramcosta.composedestinations.codegen.writers.SingleDestinationWriter.navArgDefaultCode(SingleDestinationWriter.kt:529)
	at com.ramcosta.composedestinations.codegen.writers.SingleDestinationWriter.navArgumentsDeclarationCode(SingleDestinationWriter.kt:384)
	at com.ramcosta.composedestinations.codegen.writers.SingleDestinationWriter.write(SingleDestinationWriter.kt:54)
	at com.ramcosta.composedestinations.codegen.writers.DestinationsWriter.write(DestinationsWriter.kt:30)
	at com.ramcosta.composedestinations.codegen.CodeGenerator.generate(CodeGenerator.kt:41)
	at com.ramcosta.composedestinations.ksp.processors.Processor.process(Processor.kt:49)
	at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension$doAnalysis$4$1.invoke(KotlinSymbolProcessingExtension.kt:237)
	at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension$doAnalysis$4$1.invoke(KotlinSymbolProcessingExtension.kt:235)
	at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension.handleException(KotlinSymbolProcessingExtension.kt:330)
	at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension.doAnalysis(KotlinSymbolProcessingExtension.kt:235)
	at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:123)
	at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:99)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:264)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:55)
	at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:115)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:255)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:101)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli$default(KotlinToJVMBytecodeCompiler.kt:60)
	at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:157)
	at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:52)
	at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:94)
	at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:43)
	at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:101)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:1642)
	at jdk.internal.reflect.GeneratedMethodAccessor110.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
	at java.rmi/sun.rmi.transport.Transport$1.run(Unknown Source)
	at java.rmi/sun.rmi.transport.Transport$1.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.rmi/sun.rmi.transport.Transport.serviceCall(Unknown Source)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

This PR should add more meaningful error message - maybe different wording?. I also added two more tests.
Reason: We are building KMM application and we want to have more code shared between iOS and Android.

Thank you for this! :)

authors: Mordred raamcosta

repo: raamcosta/compose-destinations


text:
All uris must be reachable in case of environment creation

Describe the bug
Not sure if that is an expected behavior but it makes the usage of the client very hard. In case you are using multiple uris by SetUris(uris ...string) method all the hosts must be available at the point in time you create the environment with NewEnvironment.
Reproduction steps
env, err = stream.NewEnvironment(
		stream.NewEnvironmentOptions().
			SetUris([]string{"rabbitmq-streams://localhost:5552", "rabbitmq-streams://localhost:5553"}))

will return an error in case one of the uris is not accessable at point in time
Expected behavior
From the documentation I would expect to silently accept one of the hosts/uris to be not available at any point in time and automatically use randomly another one. Otherwise it is really hard in context of kubernetes/docker when I can never guarantee that all nodes are available when my service tries to start.
Additional context
No response

Thank you @Egyptmaster
yes,  his part can be improved:
https://github.com/rabbitmq/rabbitmq-stream-go-client/blob/202c881a329b793d5999fe7dcebffd1cd90b1c97/pkg/stream/environment.go#L51-L76
The client should try to connect with each URI

@Egyptmaster can you please try https://github.com/rabbitmq/rabbitmq-stream-go-client/pull/310 ? thank you

Sure, but can do on Monday earliest

@Egyptmaster, please let me know if you have a chance to test it so I can release the new version. Thank you

@Gsantomaggio sorry for late response. I recently tried the feature brach and the issue seems to be fixed 👍
thanks for the quick fix

FYI: https://github.com/rabbitmq/rabbitmq-stream-go-client/releases/tag/v1.4.5

authors: Egyptmaster Gsantomaggio

repo: rabbitmq/rabbitmq-stream-go-client


text:
🛑 Pet Project is down

In 3c5f4e2, Pet Project ($RINFO_SITE) was down:

HTTP code: 500
Response time: 20916 ms

Resolved: Pet Project is back up in 5bc35ab.


text:
Removal of overly complicated AsyncChain code, in order to facilitate future maintenance

Removed AsyncChain class and associated tests.
Replaced AsyncFunctionWithThreadPool class with FunctionWithThreadPool.
Converted AsyncFunctionWithThreadPool's subclasses to use FunctionWithThreadPool instead
Converted the users of AsyncChain to invoke each step of the chain individually.
Added/fixed unit tests for the individual functions in the chain, (which didn't exist.)
Added integration test for preaggregated metrics.
Increased the http request timeout from 5 seconds to 1 minute, and changed the status
returned on timeout from 202 to 504, (GATEWAY_TIMEOUT).
My understanding is the Udp ingestor code is basically deprecated.  Since it uses
AsyncChain as well, I had to update it, just to keep it compiling.  It didn't have
any tests, and I didn't add any.

@GeorgeJahad Is it a proper analysis of the code that the async nature of the processor chain has been reduced to just the BatchWriter? I still see that we are going to wait for the ListenableFuture returned by the BatchWriter.

Is it a proper analysis of the code that the async nature of the
processor chain has been reduced to just the BatchWriter?

In reality, the asyncNature of the processing stream hasn't changed at all.
The TypeAndUnitProcessor, RollupTypeCacher, and DiscoveryWriter processing always ran in a threadpool and still do.  They were always asynchronous WRT the batchWriter and they still are.  In the past, to satisfy each step of the chain, the prior step would return a copy of the input in a NoOp future so that the next step could proceed immediately.  Now instead of manipulating the input through the NoOp futures, I pass the input in to each step directly.  Does that make sense?

Changes Unknown when pulling cbe3f5740524a80ce33349942878578407f837c5 on GeorgeJahad:george/remove_async_chain_rebase into ** on rackerlabs:master**.

Changes Unknown when pulling cbe3f5740524a80ce33349942878578407f837c5 on GeorgeJahad:george/remove_async_chain_rebase into ** on rackerlabs:master**.

Ran some perf tests to confirm that ingest rate/cpu usage remains the same before and after these changes:
Here are the before graphs:

Here are the after graphs:

Coverage increased (+4.28%) to 33.67% when pulling 55dece716741a4ba2759dcdbbb51215f6eb5eae9 on GeorgeJahad:george/remove_async_chain_rebase into dc787ea0e899f7016ab1cafff360bdd6ab969924 on rackerlabs:master.

@GeorgeJahad Now that we have removed AsyncChain, is there a reason to keep NoOpFuture around? I see it getting used only in tests and udp modules...

Fixed indentation and removed no longer used NoOpFuture class.  Thanks Chinmay!

Coverage increased (+4.26%) to 33.65% when pulling 0bdeaa4049cca5628bf7ee3605bb13cb2ea9fd84 on GeorgeJahad:george/remove_async_chain_rebase into dc787ea0e899f7016ab1cafff360bdd6ab969924 on rackerlabs:master.

+1. Please squash the commits before merging.

Coverage increased (+1.81%) to 53.01% when pulling 8514bae4149d6efd94e210a7d0ece477854750c6 on GeorgeJahad:george/remove_async_chain_rebase into 6c95f5f01f2680a277bc5332cc4d53e00676789e on rackerlabs:master.

authors: GeorgeJahad chinmay-gupte coveralls

repo: rackerlabs/blueflood

license_source: bigquery


text:
🛑 barbican-api is down

In e413b4d, barbican-api (https://barbican.api.sjc3.rackspacecloud.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: barbican-api is back up in a63c626 after 2 minutes.

repo: rackerlabs/rs-flex-uptime


text:
loadAsyncProps never fires callback

When the flattened components that are passed in is an empty array maybeFinish is never called which means the callback is never fired.

fixed in #2

authors: AlastairTaft ryanflorence

repo: rackt/async-props

license: mit


text:
Cannot read property ownerDocument of null

Inside the custom menu demo, I got this error http://rackt.github.io/react-autocomplete/custom-menu/
Uncaught TypeError: Cannot read property 'ownerDocument' of nullgetClientPosition @ shared.js:20971
getOffset @ shared.js:21034
module.exports.offset @ shared.js:21336
scrollIntoView @ shared.js:20856
maybeScrollItemIntoView @ shared.js:20561
componentDidUpdate @ shared.js:20554
assign.notifyAll @ shared.js:3435O
N_DOM_READY_QUEUEING.close @ shared.js:17673
Mixin.closeAll @ shared.js:4738
Mixin.perform @ shared.js:4679
Mixin.perform @ shared.js:4665
assign.perform @ shared.js:3177
flushBatchedUpdates @ shared.js:3257
ReactPerf.measure.wrapper @ shared.js:3540
NESTED_UPDATES.close @ shared.js:3133
Mixin.closeAll @ shared.js:4738
Mixin.perform @ shared.js:4679
assign.perform @ shared.js:3177
flushBatchedUpdates @ shared.js:3257
ReactPerf.measure.wrapper @ shared.js:3540
Mixin.closeAll @ shared.js:4738
Mixin.perform @ shared.js:4679
ReactDefaultBatchingStrategy.batchedUpdates @ shared.js:15795
batchedUpdates @ shared.js:3192
ReactEventListener.dispatchEvent @ shared.js:17396

I have the same issue in my project. It happens when I clear the 'items' while they are still being displayed:

I found another case where this happens:
When you type some text in the input and already press the "arrow down" key on the keyboard, before the suggestions have been displayed.

+1

+1

Is it solved? i have same issue (react-autocomplete version 0.2.1)

+1

authors: barinbritva changhwa hugotox loopmode tleunen ventrill

repo: rackt/react-autocomplete


text:
Add support for supplying a path to DefaultRoute

It would be nice, as mentioned in #883, to be able to give a default route a path so that, for example, when someone hits a top level path /settings/ they would be redirected to /settings/general/ or similar. Just a piece of the code I'm working on for an example:
<Route name="settings" handler={SettingsBase}>
  <DefaultRoute name="settings_general" path="general" handler={SettingsGeneral}/>
  <Route name="settings_team" path="team" handler={SettingsTeam}/>
</Route>

Default routes match when their parent matches, they don't have a path. Maybe you're after a defaultRedirect? in which case you redirect in the default route's transitionTo.

hm, I'm not sure what you mean by the default route's transitionTo. I just want /settings/ to redirect to /settings/general/ but don't see an easy way to make this happen. I tried the above first and next tried:
<Route name="settings" handler={SettingsBase}>
  <Redirect from="/" to="general"/>
  <Route name="settings_general" path="general" handler={SettingsGeneral}/>
  <Route name="settings_team" path="team" handler={SettingsTeam}/>
</Route>

but that also does not work.

that being said, the following does work, but I'd rather the above.
<Redirect from="settings" to="settings_general"/>
<Route name="settings" handler={SettingsBase}>
  <Route name="settings_general" path="general" handler={SettingsGeneral}/>
  <Route name="settings_team" path="team" handler={SettingsTeam}/>
</Route>

+1 — would much prefer the former, as it keeps all related items encapsulated in the parent <Route />.

authors: Wildhoney chrisdrackett ryanflorence

repo: rackt/react-router


text:
Breadcrumbs example

@knowbody a couple of concerns:

not super happy with the static properties, although I needed to set up path as well to make links from breadcrumbs working.
it won't work with any HOC's, so use case is pretty limited. In my custom project, I was using a HOC called @RouterPage(title) that was the top-most HOC assigning these static properties for use with router and with DocumentTitle. Quite verbose, but it was working efficiently.

And generally it feels like styling and breadcrumbs component can be (and should) be extracted to a separate component, but just wanted to check if we are heading in the same direction first ;)
Commits to be squashed into one later.

I really like this)

@grabbou I think we can go forward with this example. I like it! Clean it up and maybe add the README file with the concerns, so it's clear for others.

Hey @grabbou! Thanks for the PR! Would you mind rebasing on current master? The tests should pass now.

@grabbou can you rebase this? If you don't have time I'm happy to help with that, it would be great to have it in our examples.

Yeah i do have time! Sorry, been on Twitter only holidays :) will rebase this evening!

thanks!

Rebased :)

squash commits please @grabbou

Yeah, sorry! Squashed and reworded

omg, you're going to be annoyed with me lol, a few more changes and we can merge. I'll comment on the code

that's all, sorry, should've mention that earlier

Hah, no worries :) This is acceptable as I need to get familiar with your coding style :+1: Will commit & squash in a bit!

thanks, just trying to have each example written in the similar way. and as we did the React 0.14 changes to all of them it will be great to have it everywhere.

@grabbou thanks again for this PR, I merged it and added the changes (https://github.com/rackt/react-router/commit/c7bafe5bb67c8405d8c8401ce498e90c15707702)
P.S. I really like the use of statics for the paths

Ha, thanks! Sorry for the details but I'm still quite sick ;< A
The statics are quite helpful although the only problem is when you have HOCs. Then, preferably, you should have HOC called router to apply these static properties on top of your component hierarchy.

authors: grabbou iNikNik knowbody mjackson


text:
Forem Should Include Default Formatter

I think this is something that ought to be discussed. If there's consensus, I'm happy to provide a patch.
It doesn't make sense that Forem comes without a formatter. New users expect that there will be rich text editing—a standard for pretty much any online forum. Providing the option to customize is powerful, but the goal ought to be zero-config: the most standard use case should require absolutely zero admin work. To me, that means including a default {insert-templating-language-here} formatter that can be overridden.

I can agree with this. Personally I like Markdown, but some other people may prefer something like BBCode, which is something Forem doesn't support at the moment. I wonder if @parndt or @knewter have any thoughts on this one?

BBCode and 'the best forum system out there' are anathematic statements. :P

I like it.  I think you'd want to just provide a block that is passed the content of the forum post, and by default that would be Forem.default_formatter = lambda{ |content| Redcloth.new(content).to_html }
Something like that?  That seems the most flexible and simple

lol entirely missed that you'd already added the formatter bits in there :)  At any rate, I prefer markdown which is what you'd asked I think :)

Hi friends,
I've thought about how we could do this. We could have the default formatter be a strict dependency of Forem, meaning that it would be installed when the Forem gem is used. When the application starts, it will load the Formatter along with Forem and have it basically seamless.
If you want to override the formatter, you just need to specify another formatter gem in your Gemfile which should be enough to override the Forem.formatter setting and alter it.
Good?

sounds good to me

Makes sense.

authors: knewter radar robyurkowski

repo: radar/forem


text:
Version bump

Apparently, the tvos changes wouldn't propagate to cocoa pods if version remains the same in podspec. So just a version bump to fix that :)

@staticdreams Apologies for not doing it months ago. I've just released v2.1.0

authors: radex staticdreams

repo: radex/SwiftyUserDefaults


text:
Update Unclassified Test Site to latest Accumulo

Update the mar.ossim site to the latest accumulo.  This will require us to replicate our test VM to the omar.ossim.

0d (covered in #212)

I have updated to the latest accumulo 1.7.0

authors: gpotts mpgerlek

repo: radiantbluetechnologies/ossim-geotools


text:
Human-readable "Region name" for bbox/geometry?

What do others think about a free-form text field that encodes a "region" name for the given bbox or geometry?
For example if you cover the island of Hawaii, you could include the human-readable name "Hawaii" in addition to the bbox/geometry.
We've seen this in some extensions like https://github.com/stac-extensions/osc and https://github.com/stac-extensions/noaa-mrms-qpe where the extensions define a specific set of region names for the given location.
Does this make sense?

Duplicate of #1225

repo: radiantearth/stac-spec


text:
foreign language get started not working.

Noticed a bunch requests from Sweden were not working correctly.

Patched


text:
How about a date picker component?

It would be nice to have such component that complements with the theme.

I think these 2 are duplicates https://github.com/radix-ui/themes/issues/69. Perhaps you can join forces?

Closing as a duplicate of #69

authors: IgnusG caburj vladmoroz

repo: radix-ui/themes


text:
First record does not look like a TLS handshake

با سلام. من تانل رو با استفاده از روش سرویس فعال کردم.
تانل وصل هست ولی تست توی برنامه v2rayN و v2rayNG گاهی ارور میده:
Fail to detect internet connection: tls: first record does not look like a TLS handshake
در لاگ برنامه v2rayNG آمده:
measureV2rayDelay: go.Unvierse$proxyerror: Get "https://www.google.com/generate_204": tls: first record does not look like a TLS handshake
تقریبا از هر 6 بار تست، 3 بار این خطا میاد و انگار که یه چیزی این وسط بطور لحظه ای قطع و دوباره وصل میشه. 3 بار دیگه ولی پیام موفقیت آمیز میاد.
ممنون میشم این مشکل رو بررسی کنید.
تشکر از توسعه دهندگان این پروژه.

مرسی از کامنتتون، تغییر sni رو در ادامه انجام میدم و نتیجه رو میگم.
این کد سرویس هام هست. این رو هم بگم که چند تا سرور ایران و خارج رو با این کد و چند تا سرویس دیگه شبیه همین، بصورت چند به چند به هم وصل کردم.
این سرور خارج
[Unit]
Description=Reverse TLS Tunnel

[Service]
Type=idle
User=root
WorkingDirectory=/root
ExecStart=/root/RTT --kharej --iran-ip:$(hidden) --iran-port:44986 --toip:127.0.0.1 --toport:44986 --password:$(hidden) --sni:splus.ir --terminate:24
Restart=always

[Install]
WantedBy=multi-user.target

این سرور ایران:
[Unit]
Description=Reverse TLS Tunnel

[Service]
Type=idle
User=root
WorkingDirectory=/root
ExecStart=/root/RTT --iran  --lport:443 --add-port:48021 --add-port:58098 --add-port:32204 --add-port:56281 --add-port:44986 --add-port:42403 --sni:splus.ir --password:$(hidden) --terminate:24
Restart=always

[Install]
WantedBy=multi-user.target

با این sni ها هم تست کنید ببینید نتیجه چطوره

server.ir

parsannet.ir

magnet.ir

server.ir

parsannet.ir

magnet.ir

سلام وقت بخیر
خسته نباشید یه سوال داشتم
راهی یا اسکریپتی هست بشه همچین sni  هایی خودمان پیدا کنیم؟
با تشکر

repo: radkesvat/ReverseTlsTunnel


text:
RadzenDataGrid Settings: SettingsChanged gets an incorrect CurrentPage value

Describe the bug
The SettingsChanged event handler receives an incorrect CurrentPage value after a page change:
To Reproduce
Add code to Edit Source on DataGrid Pager API ad display the @current_page value it on the page. We will see different values of the current page in the variable and the current pagers page number on the screen.
 int? current_page;
protected override void OnAfterRender(bool firstRender)
{
    if (firstRender)
    {
        dataGrid.SettingsChanged = new EventCallback<DataGridSettings>(this, async (DataGridSettings settings) =>
	{
            current_page = settings.CurrentPage;
	});
    }
    base.OnAfterRender(firstRender);
}

Expected behavior
The values must be the same.

I don't see any difference:

At now I can't reproduce the issue

At now I can’t reproduce the issue, apparently the reason was in my code and was fixed, but the demo example works correctly, I was just inattentive. Guilty. Sorry.

authors: aplib enchev

repo: radzenhq/radzen-blazor


text:
Mobile App [Radzima UIKit, iOS, Dark mode] Bookmark cover image has a low contrast with the background.

When enabling dark mode on iOS, the bookmark cover image (in "Закладки" tab) has a low contrast with the background of the application.
On the RN, the bookmark cover image has a white border, so the cover has a high contrast with the background.
Precondition:

Run Radzima app in dark mode;
There are some objects on bookmarks page.

Steps:

Tap on "Закладки" tab;
Check the figure on the cover of category.

Expected results:

"Закладки" tab opens;
Bookmark cover image  has a high contrast with the background.

Actual result:

"Закладки" tab opens;
Bookmark cover image  has a low contrast with the background.

UIKIt:

RN:

Verified successfully on Test Flight as a part of Mobile Release 2 Build 17 UiKit v.1.1.1

authors: AndreyKramskoy ArtsemHarustovich


text:
how to disable banner notification on ios?

Do we have possibility to disable banner notification on ios for notification?

What is banner notification? Try to decrease the notification's priority.

generally if you google this phrase you will see. because its strangely named :)
on android the notifications coming is visible by icon appearing on topbar, but in ios there is banner on top of everything.
user can deactivate it or influence in settings, but i am asking if there is some way to setup notification settings for android/ios in this library or not?

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!

authors: Miedziaq rafaelsetragni


text:
jpg read

I have on question,how can i read file as image from mongo

This Endpoint is created to stream files back from mongodb.
https://github.com/rahil471/fileupload-nodejs-gridfs-angular2/blob/master/app.js#L53

thanks on response,..im interested in how to get image.jpg as a picture,not name or size...Is there some rules for that kind of type jpg png

Buddy That API, is to fetch your uploaded Image as a picture. Hit that in the browser and your image/video will be loaded.

Here you can see the content-type being set.
https://github.com/rahil471/fileupload-nodejs-gridfs-angular2/blob/master/app.js#L70

buddy i download your app from github,and also getting responseCode: 1,
responseMessage: "error"  ....maybe i missed something :/


text:
I want to know how much blocks are left until I can withdraw my RDN / SVT from the main account

User Story
As Chris I want to know how much blocks are left until I can withdraw my RDN / SVT from the main account so that I can get them.
Acceptance criteria

It is shown on the UDC screen
I want to see the number of remaining blocks until the planned withdraw is complete
I want to see the amount of RDN / SVT on the planned withdrawal
We use our existing colors
There is another issue for the rest of the screen https://github.com/raiden-network/light-client/issues/2220
A refactoring to split the stores is done

Design
The click-dummy

Click on the Withdraw button to see the complete design

One part:

Remark

Are several planned withdrawals possible at a time? -> No it is not.

Tasks

[x] Design @sashseurat (can be done together with #2220)
[ ] Write down the software design @weilbith

This requires a small new function in the interface of the SDK. This should work pretty much similar to how we get token balances. This means it does not use the state machine and doesn't dispatch any action or event. It simply provides an easy method to query the user deposit contract for planned withdraws for the SDK user. This then simply gets queried on the account UDC screen of the dApp. Similar to the account withdrawal screen this will require to show a loading state while the SDK reads data from the blockchain. This will be just a mounted hook of the Vue component as use already there.
After all this is a pretty simple solution with a high impact. It should be very simple to add.

@christianbrb do you want any end-to-end tests for this feature?

@weilbith No, I don't think so.

authors: christianbrb weilbith

repo: raiden-network/light-client


text:
How to get rid of scss via sprockets when using webpacker

Describe the bug
I upgraded rails_admin from 2.x to 3.x and switched to webpacker and it's working fine without sprockets. However, I also use https://github.com/ankane/blazer which still uses sprockets-rails (but not sassc-rails).
However, when I add sprockets-rails back to my application (to make blazer work again), I also need to manually add sassc-rails because even though rails_admin is configured to use webpacker, sprockets-rails tries to compile rails_admin's scss files and fails without it.
Reproduction steps
RailsAdmin.config do |config|
  config.asset_source = :webpacker
...

Gemfile:
gem "sprockets-rails"
# gem "sassc-rails"

(note that sassc-rails is commented out here. When removing # , it will work.)
Expected behavior
rails_admin's files should be ignored by sprockets-rails if rails_admin is configured for webpacker
Additional context

rails version: 7.0.2.3
rails_admin version: 3.0.0
rails_admin npm package version: 3.0.0
full stack trace (if there's an exception)

rake aborted!
LoadError: cannot load such file -- sassc
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.11.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:27:in `require'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/autoload/sassc.rb:2:in `<main>'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.11.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bootsnap-1.11.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/sassc_processor.rb:42:in `initialize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/sassc_processor.rb:27:in `new'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/sassc_processor.rb:27:in `instance'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/sassc_processor.rb:31:in `call'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:22:in `block in <class:CompositeProcessor>'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:33:in `call'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:182:in `load_from_unloaded'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:59:in `block in load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:337:in `fetch_asset_from_dependency_cache'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:43:in `load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/cached_environment.rb:44:in `load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/bundle.rb:27:in `call'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:182:in `load_from_unloaded'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:59:in `block in load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:337:in `fetch_asset_from_dependency_cache'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/loader.rb:43:in `load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/cached_environment.rb:44:in `load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/base.rb:81:in `find_asset'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/base.rb:88:in `find_all_linked_assets'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `each'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `to_a'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `block (2 levels) in find'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:24:in `block in execute'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `block in synchronize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `synchronize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `synchronize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:22:in `execute'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:564:in `block in realize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/immediate_executor.rb:29:in `post'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:563:in `realize'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:250:in `execute'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:297:in `execute'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:124:in `block in find'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:123:in `map'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:123:in `find'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:170:in `compile'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-rails-3.4.2/lib/sprockets/rails/task.rb:67:in `block (3 levels) in define'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.3/lib/rake/sprocketstask.rb:148:in `with_logger'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/sprockets-rails-3.4.2/lib/sprockets/rails/task.rb:66:in `block (2 levels) in define'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/airbrake-13.0.0/lib/airbrake/rake.rb:17:in `execute'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli/exec.rb:58:in `load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli/exec.rb:58:in `kernel_load'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli/exec.rb:23:in `run'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli.rb:484:in `exec'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli.rb:31:in `dispatch'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/cli.rb:25:in `start'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/exe/bundle:48:in `block in <top (required)>'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
/home/app/webapp/vendor/bundle/ruby/3.0.0/gems/bundler-2.3.4/exe/bundle:36:in `<top (required)>'
/usr/local/rvm/rubies/ruby-3.0.3/bin/bundle:25:in `load'
/usr/local/rvm/rubies/ruby-3.0.3/bin/bundle:25:in `<main>'
/usr/local/rvm/gems/ruby-3.0.3/bin/ruby_executable_hooks:22:in `eval'
/usr/local/rvm/gems/ruby-3.0.3/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => assets:precompile

Add any other context about the problem here.

Would mind trying this suggestion?
https://github.com/railsadminteam/rails_admin/issues/3536#issuecomment-1179498926

Stale.

authors: bb mshibuya


text:
No implicit conversion of Nil into String when running fontello convert

Error message reads:
/home/visa/.rvm/gems/ruby-2.2.1/gems/fontello_rails_converter-0.4.0/lib/fontello_rails_converter/cli.rb:77:in read': no implicit conversion of nil into String (TypeError) 	from /home/visa/.rvm/gems/ruby-2.2.1/gems/fontello_rails_converter-0.4.0/lib/fontello_rails_converter/cli.rb:77:in convert_main_stylesheet'
from /home/visa/.rvm/gems/ruby-2.2.1/gems/fontello_rails_converter-0.4.0/lib/fontello_rails_converter/cli.rb:62:in convert' 	from /home/visa/.rvm/gems/ruby-2.2.1/gems/fontello_rails_converter-0.4.0/bin/fontello:134:in <top (required)>'
from /home/visa/.rvm/gems/ruby-2.2.1/bin/fontello:23:in load' 	from /home/visa/.rvm/gems/ruby-2.2.1/bin/fontello:23:in '
from /home/visa/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in eval' 	from /home/visa/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in '
For some reason the various fontello_name variables seem to be passed in as empty.
Env: RVM, Rails 4.1.6
Edit: Installed via Bundler + Gemfile

Thanks for the bug report @wizzor
Could you provide some more information in what context the bug appeared?

Was it initial usage of the gem or were you updateing an existing fontello font?
What is the exact command in which folder that is failing?
Where is you config.json located and what is it's content?  Especially asking for the "name" property in there.

The best thing for me to fix the bug would be some concrete steps to reproduce the issue.
I hope you can help me out with fixing this.

Of course,
This was initial usage, I downloaded a Fontello zip, renamed it to fontello.zip, placed in app's /tmp directory
Command used was
fontello convert --no-download
The config.json is inside the fontello-generated zip file, and gets correctly copied over to ./vendor/assets/fonts/config.json
The name value is empty, as I didn't specify a name for Fontello. I will retry with a named fontello font and report back.

Hi,
The process completed successfully after I gave a name to the font package.
As an improvement suggestion, I propose one of the following:

Set a default name to be used eg. fontello-rc
Raise an error with instructions to re-generate the font package with a name specified, if none is found

@wizzor , how did you give the font package name? If manually change the config.json it will be deleted after running the fontello convert command.

I renamed the package in fontello UI, saved and redownloaded the package,
and then ran fontello convert --no-download again, everything works well
now.
On 26 Jun 2015 21:27, "Andrey Koleshko" notifications@github.com wrote:

@wizzor https://github.com/wizzor , how did you give the font package
name? If manually change the config.json it will be deleted after running
the fontello convert command.
—
Reply to this email directly or view it on GitHub
https://github.com/railslove/fontello_rails_converter/issues/29#issuecomment-115824740
.

authors: jhilden ka8725 wizzor


text:
[bug] throw error r.removeListener is not a function when trustwallet disconnect

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
1.0.1
wagmi Version
1.1.1
Current Behavior
trustwallet disconnect throw error r.removeListener
Expected Behavior
disconnect wallet successfully.
Steps To Reproduce

click disconnect

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
The website can also be reproduced:

@ybgbob Thanks for reporting. Have communicated this to the Trust Wallet team as this behavior only recently began appearing and likely resulted from a change to the Trust provider, but haven't had much luck working out a solution with that team yet. Marking as duplicate in favor of the previous #1259 report.

@ybgbob 1.0.5 is now available with a fix for this issue.

authors: DanielSinclair ybgbob

repo: rainbow-me/rainbowkit


text:
[bug] No QueryClient set, use QueryClientProvider to set one

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
2.0.2
wagmi Version
2.5.12
Current Behavior
An error is thrown immediatly when starting my app. I've made extensive searches throught the web to figure out what is going on, with no luck.
Expected Behavior
To work.
Steps To Reproduce
Unable to figure out why this error keeps being thrown as i've checked for hours almost everything. I've done extensive searches accross the web to try to find a workaround, with no luck

{ "name": "my-app", "version": "2.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "export": "next export", "lint": "eslint --fix \"src/**/*.{js,jsx,ts,tsx}\"", "format": "prettier --write \"src/**/*.{js,jsx,ts,tsx}\"", "build:icons": "tsc -b src/iconify-bundle && node src/iconify-bundle/bundle-icons-react.js" }, "dependencies": { "@casl/ability": "6.3.3", "@casl/react": "3.1.0", "@emotion/cache": "11.10.5", "@emotion/react": "11.10.6", "@emotion/server": "11.10.0", "@emotion/styled": "11.10.6", "@faker-js/faker": "^8.0.2", "@iconify/react": "4.1.0", "@moralisweb3/next": "^2.23.2", "@mui/lab": "^5.0.0-alpha.169", "@mui/material": "^5.15.14", "@mui/system": "^5.15.14", "@mui/x-data-grid": "^7.0.0", "@mui/x-date-pickers": "^7.0.0", "@popperjs/core": "2.11.6", "@rainbow-me/rainbowkit": "^2.0.2", "@tanstack/query-core": "^5.28.6", "@tanstack/react-query": "^5.28.6", "@tanstack/react-query-devtools": "^5.28.6", "@types/dompurify": "^3.0.2", "@types/draft-convert": "^2.1.4", "@types/draftjs-to-html": "^0.8.1", "@types/jsonwebtoken": "^9.0.1", "@types/lodash": "^4.14.194", "@types/numeral": "^2.0.5", "@types/react-dom": "^18.2.8", "@types/react-lines-ellipsis": "^0.15.2", "@types/uuid": "^9.0.2", "@types/webextension-polyfill": "^0.10.7", "@uploadthing/react": "^6.0.2", "@upstash/ratelimit": "^0.4.4", "@vercel/analytics": "^1.0.2", "apexcharts": "^3.42.0", "apexcharts-clevision": "^3.28.5", "axios": "^1.6.2", "bootstrap-icons": "1.10.3", "chart.js": "^4.4.0", "cleave.js": "1.6.0", "clipboard-copy": "4.0.1", "clsx": "1.2.1", "date-fns": "2.29.3", "dompurify": "^3.0.3", "draft-js": "^0.11.7", "draftjs-to-html": "^0.9.1", "embla-carousel-react": "^8.0.0-rc15", "embla-carousel-wheel-gestures": "^8.0.0-rc05", "emoji-picker-react": "^4.4.9", "ethers": "^6.11.1", "jose": "^4.14.0", "jsonwebtoken": "^9.0.0", "lodash": "^4.17.21", "mongoose": "^8.0.3", "moralis": "^2.23.2", "nanoid": "^4.0.2", "next": "^14.1.4", "next-auth": "^4.24.5", "nprogress": "0.2.0", "numeral": "^2.0.6", "react": "^18.2.0", "react-apexcharts": "^1.4.1", "react-chrono": "^2.2.0", "react-countdown": "^2.3.5", "react-datepicker": "4.10.0", "react-dom": "18.2.0", "react-draft-wysiwyg": "^1.15.0", "react-dropzone": "^14.2.3", "react-error-boundary": "^4.0.8", "react-hook-form": "^7.43.9", "react-hot-toast": "^2.4.1", "react-lines-ellipsis": "^0.15.3", "react-multi-carousel": "^2.8.4", "react-perfect-scrollbar": "1.5.8", "react-popper": "^2.3.0", "react-swipeable-views": "^0.14.0", "react-transition-group": "^4.4.5", "recharts": "^2.12.3", "stylis": "4.1.3", "stylis-plugin-rtl": "2.1.1", "swr": "^2.2.5", "uploadthing": "^6.0.4", "uuid": "^9.0.0", "viem": "^2.8.16", "wagmi": "^2.5.12", "yup": "^1.3.2", "zod": "^3.22.2" }, "devDependencies": { "@iconify/iconify": "^3.1.1", "@iconify/json": "^2.2.195", "@iconify/tools": "^4.0.2", "@iconify/types": "^2.0.0", "@iconify/utils": "^2.1.22", "@tanstack/eslint-plugin-query": "^5.28.6", "@types/cleave.js": "1.4.7", "@types/d3-color": "^3.1.0", "@types/draft-js": "0.11.10", "@types/node": "18.15.3", "@types/nprogress": "0.2.0", "@types/payment": "2.1.4", "@types/prismjs": "1.26.0", "@types/react": "^18.2.24", "@types/react-datepicker": "^4.15.1", "@types/react-draft-wysiwyg": "1.13.4", "@types/react-swipeable-views": "^0.13.1", "@typescript-eslint/eslint-plugin": "^7.3.1", "@typescript-eslint/parser": "^7.3.1", "eslint": "^8.57.0", "eslint-config-next": "^14.1.4", "eslint-config-prettier": "^9.1.0", "eslint-import-resolver-alias": "^1.1.2", "eslint-import-resolver-typescript": "^3.6.1", "eslint-plugin-import": "^2.29.1", "prettier": "^3.2.5", "typescript": "^5.4.3" } }
App.ts:
import { ReactNode } from 'react'
import { HydrationBoundary, QueryClient, QueryClientProvider } from '@tanstack/react-query'
import type { NextPage } from 'next'
import type { AppProps } from 'next/app'
import Head from 'next/head'
import { Router } from 'next/router'
import NProgress from 'nprogress'
import type { EmotionCache } from '@emotion/cache'
import { CacheProvider } from '@emotion/react'
import themeConfig from 'src/configs/themeConfig'
import { Toaster } from 'react-hot-toast'
import ThemeComponent from 'src/@core/theme/ThemeComponent'
import UserLayout from 'src/layouts/UserLayout'
import AuthGuard from 'src/layouts/components/auth/UserAuthGuard'
import Spinner from 'src/layouts/components/spinner'
import { SessionProvider } from 'next-auth/react'
import { SettingsConsumer, SettingsProvider } from 'src/@core/context/settingsContext'
import ReactHotToast from 'src/@core/styles/libs/react-hot-toast'
import { createEmotionCache } from 'src/@core/utils/create-emotion-cache'
import 'react-perfect-scrollbar/dist/css/styles.css'
import { RainbowKitProvider, darkTheme, getDefaultConfig } from '@rainbow-me/rainbowkit'
import '@rainbow-me/rainbowkit/styles.css'
import { WagmiProvider, http } from 'wagmi'
import { arbitrum, bsc } from 'wagmi/chains'
import { ReactQueryDevtools } from '@tanstack/react-query-devtools'
import 'src/iconify-bundle/icons-bundle-react'
import '../../styles/globals.css'
import { UsernameProvider } from '../contexts/UsernameContext'
import { Analytics } from '@vercel/analytics/react'

type ExtendedAppProps = AppProps & {
Component: NextPage
emotionCache: EmotionCache
}

type GuardProps = {
authGuard: boolean
children: ReactNode
}

const clientSideEmotionCache = createEmotionCache()

const wagmiConf = getDefaultConfig({
appName: MyProject',
projectId: 'xxx',
chains: [arbitrum, bsc],
transports: {
[arbitrum.id]: http(),
[bsc.id]: http()
},
ssr: true
})

if (themeConfig.routingLoader) {
Router.events.on('routeChangeStart', () => {
NProgress.start()
})
Router.events.on('routeChangeError', () => {
NProgress.done()
})
Router.events.on('routeChangeComplete', () => {
NProgress.done()
})
}

const queryClient = new QueryClient()

const Guard = ({ children, authGuard }: GuardProps) => {
if (!authGuard) {
return <>{children}</>
} else {
return <AuthGuard fallback={}>{children}
}
}

const App = (props: ExtendedAppProps) => {
const { Component, emotionCache = clientSideEmotionCache, pageProps } = props

const contentHeightFixed = Component.contentHeightFixed ?? false
const getLayout =
Component.getLayout ?? (page => {page})

const setConfig = Component.setConfig ?? undefined
const authGuard = Component.authGuard ?? true

return (

 <CacheProvider value={emotionCache}>
      <Head>
        <title>Title</title>
        <meta
          name='description'
          content='Content'
        />
        <meta
          name='keywords'
          content='keyword'
        />
        <meta name='viewport' content='initial-scale=1, width=device-width' />
      </Head>

  <WagmiProvider config={wagmiConf}>
    <SessionProvider session={pageProps.session}>
      <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
        <QueryClientProvider client={queryClient}>
          <HydrationBoundary state={pageProps.dehydratedState}>
            <UsernameProvider>
              <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                <SettingsConsumer>
                  {({ settings }) => {
                    return (
                      <ThemeComponent settings={settings}>
                        <Guard authGuard={authGuard}>{getLayout(<Component {...pageProps} />)}</Guard>
                        <ReactHotToast>
                          <Toaster
                            position={settings.toastPosition}
                            toastOptions={{ className: 'react-hot-toast' }}
                          />
                        </ReactHotToast>
                      </ThemeComponent>
                    )
                  }}
                </SettingsConsumer>
              </SettingsProvider>
            </UsernameProvider>
            <Analytics />
            <ReactQueryDevtools />
          </HydrationBoundary>
        </QueryClientProvider>
      </RainbowKitProvider>
    </SessionProvider>
  </WagmiProvider>
</CacheProvider>
)
}

export default App

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@Kaldrogh Thanks for raising this issue. I see you use a lot of custom logic outside of your <App /> component like Component.getLayout and others. This error happens if you're using any of the wagmi hooks outside of the <QueryClientProvider /> component.
Is this the case on your end ? Also if you try to remove <RainbowKitProvider /> will the issue persist ? Cleaning your browser cache may i also help.

@Kaldrogh Thanks for raising this issue. I see you use a lot of custom logic outside of your <App /> component like Component.getLayout and others. This error happens if you're using any of the wagmi hooks outside of the <QueryClientProvider /> component.
Is this the case on your end ? Also if you try to remove <RainbowKitProvider /> will the issue persist ? Cleaning your browser cache may i also help.

Thanks a lot for your help!
If i remove the <RainbowKitProvider, it starts to work normally as before.
I also try to enclose my variables initialization within the WagmiProvider scope, with no luck. I even try to enclose them within the  one and clear the cache, but it doesn't change anything.
Working version:
  <WagmiProvider config={wagmiConf}>
        {(() => {
          const contentHeightFixed = Component.contentHeightFixed ?? false
          const getLayout =
            Component.getLayout ?? (page => <UserLayout contentHeightFixed={contentHeightFixed}>{page}</UserLayout>)

          const setConfig = Component.setConfig ?? undefined
          const authGuard = Component.authGuard ?? true

          return (
            <QueryClientProvider client={queryClient}>
              <HydrationBoundary state={pageProps.dehydratedState}>
                <SessionProvider session={pageProps.session}>
                  <UsernameProvider>
                    <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                      <SettingsConsumer>
                        {({ settings }) => (
                          <ThemeComponent settings={settings}>
                            <Guard authGuard={authGuard}>{getLayout(<Component {...pageProps} />)}</Guard>
                            <ReactHotToast>
                              <Toaster
                                position={settings.toastPosition}
                                toastOptions={{ className: 'react-hot-toast' }}
                              />
                            </ReactHotToast>
                          </ThemeComponent>
                        )}
                      </SettingsConsumer>
                    </SettingsProvider>
                  </UsernameProvider>
                  <Analytics />
                  <ReactQueryDevtools />
                </SessionProvider>
              </HydrationBoundary>
            </QueryClientProvider>
          )
        })()}
      </WagmiProvider>

Non working version:
      <WagmiProvider config={wagmiConf}>
        {(() => {
          const contentHeightFixed = Component.contentHeightFixed ?? false
          const getLayout =
            Component.getLayout ?? (page => <UserLayout contentHeightFixed={contentHeightFixed}>{page}</UserLayout>)

          const setConfig = Component.setConfig ?? undefined
          const authGuard = Component.authGuard ?? true

          return (
            <QueryClientProvider client={queryClient}>
              <HydrationBoundary state={pageProps.dehydratedState}>
                <SessionProvider session={pageProps.session}>
                  <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
                    <UsernameProvider>
                      <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                        <SettingsConsumer>
                          {({ settings }) => (
                            <ThemeComponent settings={settings}>
                              <Guard authGuard={authGuard}>{getLayout(<Component {...pageProps} />)}</Guard>
                              <ReactHotToast>
                                <Toaster
                                  position={settings.toastPosition}
                                  toastOptions={{ className: 'react-hot-toast' }}
                                />
                              </ReactHotToast>
                            </ThemeComponent>
                          )}
                        </SettingsConsumer>
                      </SettingsProvider>
                    </UsernameProvider>
                    <Analytics />
                    <ReactQueryDevtools />
                  </RainbowKitProvider>
                </SessionProvider>
              </HydrationBoundary>
            </QueryClientProvider>
          )
        })()}
      </WagmiProvider>

Also non working version:
 <WagmiProvider config={wagmiConf}>
        <QueryClientProvider client={queryClient}>
          <HydrationBoundary state={pageProps.dehydratedState}>
            <SessionProvider session={pageProps.session}>
              <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
                {(() => {
                  const contentHeightFixed = Component.contentHeightFixed ?? false
                  const getLayout =
                    Component.getLayout ??
                    (page => <UserLayout contentHeightFixed={contentHeightFixed}>{page}</UserLayout>)

                  const setConfig = Component.setConfig ?? undefined
                  const authGuard = Component.authGuard ?? true

                  return (
                    <UsernameProvider>
                      <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                        <SettingsConsumer>
                          {({ settings }) => (
                            <ThemeComponent settings={settings}>
                              <Guard authGuard={authGuard}>{getLayout(<Component {...pageProps} />)}</Guard>
                              <ReactHotToast>
                                <Toaster
                                  position={settings.toastPosition}
                                  toastOptions={{ className: 'react-hot-toast' }}
                                />
                              </ReactHotToast>
                            </ThemeComponent>
                          )}
                        </SettingsConsumer>
                      </SettingsProvider>
                    </UsernameProvider>
                  )
                })()}
                <Analytics />
                <ReactQueryDevtools />
              </RainbowKitProvider>
            </SessionProvider>
          </HydrationBoundary>
        </QueryClientProvider>
      </WagmiProvider>

@Kaldrogh This works for me:
import "@/styles/globals.css";
import { RainbowKitProvider, darkTheme } from "@rainbow-me/rainbowkit";
import { HydrationBoundary, QueryClientProvider } from "@tanstack/react-query";
import type { AppProps } from "next/app";
import "@rainbow-me/rainbowkit/styles.css";
import { getDefaultConfig } from "@rainbow-me/rainbowkit";
import { WagmiProvider } from "wagmi";
import { mainnet, polygon, optimism, arbitrum, base } from "wagmi/chains";
import { QueryClient } from "@tanstack/react-query";
import { SessionProvider } from "next-auth/react";

const queryClient = new QueryClient();

const config = getDefaultConfig({
  appName: "My RainbowKit App",
  projectId: "YOUR_PROJECT_ID",
  chains: [mainnet, polygon, optimism, arbitrum, base],
  ssr: true, // If your dApp uses server side rendering (SSR)
});

export default function App({ Component, pageProps }: AppProps) {
  return (
    <WagmiProvider config={config}>
      {(() => {
        return (
          <QueryClientProvider client={queryClient}>
            <HydrationBoundary state={pageProps.dehydratedState}>
              <SessionProvider session={pageProps.session}>
                <RainbowKitProvider modalSize="wide" theme={darkTheme()}>
                  <Component {...pageProps} />
                </RainbowKitProvider>
              </SessionProvider>
            </HydrationBoundary>
          </QueryClientProvider>
        );
      })()}
    </WagmiProvider>
  );
}

Of course i don't have access to all of your other providers, but can you share a small reproducible example via CodeSandbox or Github repo ?

@Kaldrogh This works for me:
import "@/styles/globals.css";
import { RainbowKitProvider, darkTheme } from "@rainbow-me/rainbowkit";
import { HydrationBoundary, QueryClientProvider } from "@tanstack/react-query";
import type { AppProps } from "next/app";
import "@rainbow-me/rainbowkit/styles.css";
import { getDefaultConfig } from "@rainbow-me/rainbowkit";
import { WagmiProvider } from "wagmi";
import { mainnet, polygon, optimism, arbitrum, base } from "wagmi/chains";
import { QueryClient } from "@tanstack/react-query";
import { SessionProvider } from "next-auth/react";

const queryClient = new QueryClient();

const config = getDefaultConfig({
  appName: "My RainbowKit App",
  projectId: "YOUR_PROJECT_ID",
  chains: [mainnet, polygon, optimism, arbitrum, base],
  ssr: true, // If your dApp uses server side rendering (SSR)
});

export default function App({ Component, pageProps }: AppProps) {
  return (
    <WagmiProvider config={config}>
      {(() => {
        return (
          <QueryClientProvider client={queryClient}>
            <HydrationBoundary state={pageProps.dehydratedState}>
              <SessionProvider session={pageProps.session}>
                <RainbowKitProvider modalSize="wide" theme={darkTheme()}>
                  <Component {...pageProps} />
                </RainbowKitProvider>
              </SessionProvider>
            </HydrationBoundary>
          </QueryClientProvider>
        );
      })()}
    </WagmiProvider>
  );
}

Of course i don't have access to all of your other providers, but can you share a small reproducible example via CodeSandbox or Github repo ?

Thanks again for helping me, i've tried to remove almost everything, enclose all my variables initialization within wagmi scope, but it doesn't change anything.
The only way to get an other error message (but not a working app unfortunately :( ) is being enclosing wagmi inside rainbowKit:
const App = (props: ExtendedAppProps) => {
  const { emotionCache = clientSideEmotionCache, pageProps } = props

  return (
    <CacheProvider value={emotionCache}>
      <Head>
      </Head>
      <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
        <WagmiProvider config={config}>
          <QueryClientProvider client={queryClient}>
            <HydrationBoundary state={pageProps.dehydratedState}>
              <SessionProvider session={pageProps.session}>
                <UsernameProvider>
                  {(() => {
                    const contentHeightFixed = props.Component.contentHeightFixed ?? false
                    const getLayout =
                      props.Component.getLayout ??
                      (page => <UserLayout contentHeightFixed={contentHeightFixed}>{page}</UserLayout>)

                    const setConfig = props.Component.setConfig ?? undefined
                    const authGuard = props.Component.authGuard ?? true

                    return (
                      <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                        <SettingsConsumer>
                          {({ settings }) => (
                            <ThemeComponent settings={settings}>
                              <Guard authGuard={authGuard}>{getLayout(<props.Component {...pageProps} />)}</Guard>
                              <ReactHotToast>
                                <Toaster
                                  position={settings.toastPosition}
                                  toastOptions={{ className: 'react-hot-toast' }}
                                />
                              </ReactHotToast>
                            </ThemeComponent>
                          )}
                        </SettingsConsumer>
                      </SettingsProvider>
                    )
                  })()}
                </UsernameProvider>

                <Analytics />
                <ReactQueryDevtools />
              </SessionProvider>
            </HydrationBoundary>
          </QueryClientProvider>
        </WagmiProvider>
      </RainbowKitProvider>
    </CacheProvider>
  )
}

Which throws this error:

Otherwise, with this enclosure hierarchy, i get the same error message as before:
const App = (props: ExtendedAppProps) => {
  const { emotionCache = clientSideEmotionCache, pageProps } = props

  return (
    <CacheProvider value={emotionCache}>
      <Head>
      </Head>
      <WagmiProvider config={config}>
        <QueryClientProvider client={queryClient}>
          <HydrationBoundary state={pageProps.dehydratedState}>
            <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
              <SessionProvider session={pageProps.session}>
                <UsernameProvider>
                  {(() => {
                    const contentHeightFixed = props.Component.contentHeightFixed ?? false
                    const getLayout =
                      props.Component.getLayout ??
                      (page => <UserLayout contentHeightFixed={contentHeightFixed}>{page}</UserLayout>)

                    const setConfig = props.Component.setConfig ?? undefined
                    const authGuard = props.Component.authGuard ?? true

                    return (
                      <SettingsProvider {...(setConfig ? { pageSettings: setConfig() } : {})}>
                        <SettingsConsumer>
                          {({ settings }) => (
                            <ThemeComponent settings={settings}>
                              <Guard authGuard={authGuard}>{getLayout(<props.Component {...pageProps} />)}</Guard>
                              <ReactHotToast>
                                <Toaster
                                  position={settings.toastPosition}
                                  toastOptions={{ className: 'react-hot-toast' }}
                                />
                              </ReactHotToast>
                            </ThemeComponent>
                          )}
                        </SettingsConsumer>
                      </SettingsProvider>
                    )
                  })()}
                </UsernameProvider>

                <Analytics />
                <ReactQueryDevtools />
              </SessionProvider>
            </RainbowKitProvider>
          </HydrationBoundary>
        </QueryClientProvider>
      </WagmiProvider>
    </CacheProvider>
  )
}

It's pretty hard to give a minimal reproduction example as i have a quite complex app...
And my wagmi.config.ts use for the WagmiProvider config prop:
import { getDefaultConfig } from '@rainbow-me/rainbowkit'
import { arbitrum, bsc } from 'wagmi/chains'

export const projectId = process.env.NEXT_PUBLIC_PROJECT_ID

if (!projectId) throw new Error('Project ID is not defined')

const metadata = {
  name: 'My Project',
  description: 'This is my project',
  url: process.env.NEXTAUTH_URL,
  icons: ['/public/images/logo/project.svg']
}

const chains = [arbitrum, bsc] as const
export const config = getDefaultConfig({
  chains,
  projectId,
  appName: metadata.name,
  appDescription: metadata.description,
  appIcon: metadata.icons[0],
  appUrl: metadata.url,
  ssr: true
})

If i remove RainbowKitProvider, it works right out of the box.
Anyway, i'm having a hard time figuring out with an other React Query context would be created as everything is enclosed inside the Wagmi and React Query scope, i was using react query before without having any issues.

Even when removing everything, clearing the cache, i'm getting the same error:
const App = props => {
  return (
    <WagmiProvider config={config}>
      <QueryClientProvider client={queryClient}>
        <HydrationBoundary state={props.pageProps.dehydratedState}>
          <RainbowKitProvider modalSize='wide' theme={darkTheme()}>
            <props.Component {...props.pageProps} />
          </RainbowKitProvider>
        </HydrationBoundary>
      </QueryClientProvider>
    </WagmiProvider>
  )
}

@Kaldrogh Can you please share a small reproducible example ? I can't see your code right now and how you compute your layouts / components. If you could share a CodeSandbox link or a GitHub code repo that'd be awesome, since we have with-next and with-next-app project examples and they work completely fine.

@Kaldrogh Can you please share a small reproducible example ? I can't see your code right now and how you compute your layouts / components. If you could share a CodeSandbox link or a GitHub code repo that'd be awesome, since we have with-next and with-next-app project examples and they work completely fine.

Thanks! I can give you access to a private repo so you can try it out on your side, i just need an e-mail address to invite you.
Otherwise, it's near impossible to build a repoducible example given the complexity of the app...

@Kaldrogh I would love to do that, but i would like to keep this as simple as possible. Your project might be big and for us to debug this we would love to just have a simple reproducible example. We don't know if your project might include libraries that blocks TanStack react query from being used or cached.
Would you be able to do that for now ?

@Kaldrogh I would love to do that, but i would like to keep this as simple as possible. Your project might be big and for us to debug this we would love to just have a simple reproducible example. We don't know if your project might include libraries that blocks TanStack react query from being used or cached.
Would you be able to do that for now ?

I'll try to simplify as much as possible the github repo i wanted to invite you on.
But i don't tking that it is related to a library blocking react-query as i'm using react query everywhere inside my app for caching purpose for a very long time, and i never had any issue at all, i can see my cached queries inside the react query tool, as well as the cached entries for wagmi.
As soon as i try to enclose my app with the rainbowkit, it stops working immediatly and throws the no QueryClient error. If i remove it, wagmi and react-query work perfectly fine again.

@Kaldrogh Got it. Yeah this could be maybe conflicting peer dependencies with wagmi and viem probably, but can you just provide a small reproducible example instead of inviting me to a whole github repo project ?
Like i know you're facing this issue, but giving a small reproducible example would be the best since we don't want to go over the whole codebase project.

@Kaldrogh Got it. Yeah this could be maybe conflicting peer dependencies with wagmi and viem probably, but can you just provide a small reproducible example instead of inviting me to a whole github repo project ?
Like i know you're facing this issue, but giving a small reproducible example would be the best since we don't want to go over the whole codebase project.

Here you go, i've reproduced the error in a fresh and new repo:
https://github.com/Kaldrogh/RainbowKit-Test

The problem seems to be directly correlated to the next.config.js file which have been copied and pasted from my main app.

The problem comes from this experimental parameter:
experimental: {
esmExternals: false,
},
Once removed, it starts working normally, with a "ReferenceError: localStorage is not defined" thrown tho.

@Kaldrogh Yeah i can see the error now 🙏
When doing esmExternals: false next.js won't recognise RainbowKitProvider as esm module and we're also using peer dependencies such as wagmi and viem+ on top of wagmi we're using @tanstack/react-query which is why the webpack / builds might throw an error here.
If you have conflicts between different esm modules in your project you can also try doing esmExternals: 'loose' which may correct some errors when building your app. Here is the docs for reference.
If you're getting localStorage error you need to add ssr: true to your getDefaultConfig function i see you have it specified as false at the moment.

@Kaldrogh Any updates ?

@Kaldrogh Any updates ?

Sorry for replying late, i was busy.
After setting esmExternal to 'loose', it seems to work like a charm again! But i'll have to check everything more thoroughtly as i'm also using a library called uploadthing which required to set esmExternals to 'false'.
Anyway, thank you very much for your help!

All good. Feel free to raise another issue if you encounter any other bugs 🙏

authors: Kaldrogh magiziz


text:
Add a button to cancel the bookmark

Since the extension repository has been archived, thus I'm commenting here.
When adding a bookmark via the extension for chrome, there is no "cancel" button.
A "cancel" button would be nice to have, in cases where you might have accidently pressed the extension and/or you may change your mind.
Moreover, if you think that this is "nice to have" feature but not something you would want to work on right now, I can help you in developing it, if you can assign it to me.

Cancel == Delete

authors: coastaldemigod exentrich

repo: raindropio/app


text:
fix setup

#107

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.36%. Comparing base (dcb17be) to head (51da9b3).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #108   +/-   ##
=======================================
  Coverage   90.36%   90.36%
=======================================
  Files          35       35
  Lines        5322     5322
=======================================
  Hits         4809     4809
  Misses        513      513

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter rainyl


text:
feat : reduce pdf size to parse and adds integrationtest

Summary by CodeRabbit

New Features

Updated the AI chat service to focus on cricket-related questions, enhancing the user experience for cricket enthusiasts.

Bug Fixes

Changed the file path in the application configuration to ensure the correct document is loaded to the database.
Modified the method parameter in the AI controller for improved clarity and consistency in user interactions.

Tests

Enhanced testing capabilities with new imports and annotations.
Introduced a setup method for API testing and renamed a test for better clarity.

@coderabbitai , please fix the integration test failures

repo: rajadilipkolli/ai-playground


text:
'translate' support in ionic toast

Ionic toast is the best tool in ionic to display all types of messages.
i am working on application that has multiple countries,currencies supported.
Now i want to display translated Messages, i am using angular-translate for all messages,forms and text in HTML. now coming to JS file. i want to translate messages that are in ionic-toast.

ionicToast.show($filter('translate')("Hi ionic"), 'middle', false, 5000);
This is the solution of this issue. you need to inspect $filter in controller

Thanks for the answer.

authors: chiragandroid rajeshwarpatlolla

repo: rajeshwarpatlolla/ionic-toast


text:
Log file location should be configurable

On a production system the log files should be in /var/log, so the log file location needs to be configurable.

The PR associated with this issue has been reviewed and merged, but because it hasn't been merged into master, it hasn't been closed automatically, but the work for this issue has been completed.

repo: ral-facilities/datagateway-api


text:
Adds code coverage workflow and badge.

@ralexstokes to finish this PR the ssz-rs repo would need the CodeCov app to be added.

I've added the code cov app for this repo. And generally thumbs up on this approach
it looks like this PR uses tarpaulin, which I haven't used before but don't see any issues yet -- ill go do some more research but if you want to send over any resources that would be appreciated!

@ralexstokes thanks for reviewing! I applied the changes. 😄

authors: claravanstaden ralexstokes

repo: ralexstokes/ssz-rs


text:
Aligment justified

Is there any way to set paragraph aligment justified? I only see these choices: center, left, right.

Currently not, since I did not need that so far. But give some days to give it a try.

Would you expect justification to be done by word- or character-spacing?

I expect justification to be done by word, like is done by itext library.

Fixed in 1.0.0

authors: ralfstuckert victommasi

repo: ralfstuckert/pdfbox-layout


text:
Defaulting code examples to gpu if available

Feature suggestion from Christian :)

LGTM. We also need to update the Jupyter notebooks in examples. They are linked to the colab

authors: KPHippe braceal

repo: ramanathanlab/genslm


text:
cropped text not readable

On the Miniconda-README.md file located at https://github.com/rambasnet/DevEnvSetup/blob/master/Linux/Miniconda-README.md, the file Miniconda-Install.png shows the commands being used.
the red border overlay covers an underscore character and makes it appear to really be a space
https://github.com/rambasnet/DevEnvSetup/raw/master/Linux/Miniconda-Install.png

Fixed it. Thanks for the feedback!

repo: rambasnet/DevEnvSetup


text:
Create new launch screens

We should prepare new launch screens.

@etolstoy лончскрин, состояние загрузки, ошибка загрузки

error1.mp4.zip

Can you send me the gif of the error state?

@etolstoy try this one. If it's too big, I'll try to reduce the size

Great, thanks

authors: etolstoy ykamendrovskiy

repo: rambler-ios/RamblerConferences


text:
More than 10 arguments in R.lift?

I'm making an app to convert sets of array from user input into a cartesian product. Example on http://typography.philipyoungg.com
Based on schema below...
title: {
      type: 'text',
      properties: {
        fontFamily: ['Lato', 'Playfair Display', 'Open Sans'],
        fontSize: ['3rem'],
        fontWeight: [500, 'bold'],
        fontStyle: ['normal'],
        textTransform: ['none', 'uppercase'],
        color: ['#333', 'mediumblue'],
        lineHeight: ['1.2'],
        marginBottom: ['8px'],
        letterSpacing: ['-0.025em'],
        text: ['Guns, Germs, and Steel'],
      },
    },

R.compose(R.apply(R.liftN(10, R.unapply(R.identity))), R.values, R.prop('properties'))(title)  // <— works well

I tried to add more than 10 array and got an error.
First argument to _arity must be a non-negative integer no greater than ten
I've tried to read the source code and it seems LiftN limit this to 10.
So I tried this.
const arg12 = (a, b, c, d, e, f, g, h, i, j, k, l) => [a, b, c, d, e, f, g, h, i, j, k, l];
R.lift(arg12))(title)

and the same error still produced.
How do I solve this?

Back in #372 and #373, Ramda made the decision not to support functions of more than ten parameters.  We thought that overgenerous, thinking that more than three or four was already on pretty shaky grounds.
Although we'd certainly never thought about a case like yours, I also don't see an easy way to relax the constraints to allow it.
Any suggestions are welcome.

@CrossEye Just looked at the source code. Now understand that it'll change Ramda's arity function. Guess it's easier to use another library to create the cartesian product.
Appreciate your help! Ramda is a fantastic library. 💪

@philipyoungg:
I'm glad you found something that works.  That looks like a nice implementation.  Ramda's xprod is meant only for two lists.  But you can fold over it with something like
const xproduct = lift(reduce(pipe(xprod, map(flatten))))(head, tail)

(That would take a list of lists.  To get the same variadic API, just wrap it in an unapply.)
Or you could create a version much like the one shown using Ramda functions with something like
const xproduct = unapply(reduce(
  (acc, set) => unnest(map(x => map(y => [ ...x, y ], set), acc)),
  [[]]
));

I'm not suggesting either.  The function you found looks nice.  I just wanted to point out some of the Ramda options.

@CrossEye that's cool! Gonna change it to yours.
Could you help me understand the first xproduct?
const xproduct = lift(reduce(pipe(xprod, map(flatten))))(head, tail)

Been stuck for hours trying to understand it...

I would, except that it's the horrible result of sleepiness.  I solved the same problem twice in two different ways in that solution.  A much, much better version is the simpler:
const xproduct = reduce(pipe(xprod, map(unnest)), [[]])

Again, this could be wrapped in unapply if you don't like making a list out of your inputs.

If you really want to understand what was going on in that solution, a naive version would be to wrap up the results of xprod in some sort of fold.  Since this is xprod:
xprod(['small', 'medium', 'large'], ['red', 'green']);
//=> [["small", "red"], ["small", "green"], ["medium", "red"] /*,  ... */]

would this be enough?:
const xproduct = reduce(xprod, [[]])

No, because with this version,
xproduct([['small', 'medium', 'large']])
//=> [[[], "small"], [[], "medium"], [[], "large"]]

And here I went down the wrong path.  Ramda has not had foldl1 since way back in #20.  But it's a clear thing to want, a fold that takes its initial accumulator from the head of the list.  I wrote a quick wrapper to allow this function to grab the initial accumulator from the head, rather than supplied as [[]] separately.
const xproduct = lift(reduce(xprod))(head, tail)

I do this with lift, with the interpretation that I lift a function (reduce(xprod)) that operates on two values into one which operates on functions which return those values.  So I will pass one list into the result, which will be passed to both head and tail and then lift will pass the two resulting values into reduce(xprod).  I could have done something very similar with converge, which is slightly more powerful.  But converge is very much Ramda-specific, whereas lift is well known in the FP world.  If I don't need converge's additional power, I will stick with lift.
This now works as expected for that first case:
xproduct([['small', 'medium', 'large']]);
//=> ["small", "medium", "large"]

And it works for the next case:
xproduct([['small', 'medium', 'large'], ['red', 'green']);
//=> [["small", "red"], ["small", "green"], ["medium", "red"] /*,  ... */]

So I could hope I was done....  However, there was a problem:
xproduct([
  ['small', 'medium', 'large'],
  ['red', 'green'], //, 'blue']
  ['shirt', 'jeans', 'shoes']
]);
//=> [[["small", "red"], "shirt"], [["small", "red"], "jeans"], [["small", "red"], "shoes"],
//    [["small", "green"], "shirt"] /*, ... */]

I could see a fix for this problem.  I had to do one level of flattening as I went.  Ramda has flatten and unnest for this.  I'll blame sleepiness for my not realizing that I could have just chosen the simpler unnest. So I had to change my simple xprod step in the fold to pipe(xprod, map(flatten)).
const xproduct = lift(reduce(pipe(xprod, map(flatten))))(head, tail)

And this works for all our cases.  I sent my note (forgetting to note that this wouldn't work properly for the empty case because of the head call), responded to a few more issues and went to bed.
But what I didn't think about was that this second fix, adding the flatten, also fixed the initial problem I had as well.  I didn't need the whole lift/converge solution at all!
So this is a much better solution:
 const xproduct = reduce(pipe(xprod, map(unnest)), [[]])

(unnest doesn't try to delve deeper to flatten nested lists, so it's probably better than flatten here, although I haven't looked back at the implementation in a while.)
So the moral of the story is not, "Don't code when you're sleepy."  It's just "Don't publish your code when you're sleepy!"  :smile:

@CrossEye fantastic. Thank you for dissecting the function step by step. Read it several times, and now starting getting hang of it. Really appreciate your help for this!
By the way, wouldn't change xprod to
const xproduct = unapply(reduce(
  (acc, set) => unnest(map(x => map(y => [ ...x, y ], set), acc)),
  [[]]
));

...makes more sense ? It accept n number of arguments and return the cartesian product, while xprod limit it to two. ☺

@philipyoungg:
It might make sense to have such a function in place of or alongside our simple xprod.  We would definitely not want exactly that version (with the unapply) as Ramda avoids variadic functions.  But one that took a list of lists might be a good idea.
I don't get the sense, though, that this is one used much in Ramda.  It's there because in the early days there was no one to stop me putting in functions I personally found useful even if they weren't generally applicable.  :smile:
So perhaps the best bet would be to get this on in the Cookbook and then think about moving it to the main library if there are further requests for it.

@CrossEye
Agree with your view. The unapply isn't really needed. 😊
Yes, I believe xprod is a very specific case and not very general function (unlike map, reduce, etc). But I think it'll helps a lot of people using this in the future.
My reasoning:

There's already xprod in Ramda.
xprod only take 2 arguments, meanwhile eddmann's implementation took n number of list. Hence: more flexible.

…therefore, there's actually no loss at all implementing this one.
By the way, I'm really intrigued by your xproduct function before and explore it more deeply—especially the lift function. So I took my time to learn it and try to help the community back by answering this http://stackoverflow.com/questions/39545916/how-come-i-can-pass-functions-to-a-lifted-r-divide/41411109#41411109.
All credits to you, @CrossEye! 🤘
p.s. Happy New Year!

My application is built in react redux which has more than 10 properties in the state. When I tried to bind the redux state with ramda, I see the above error.
I have looked on the source code, changing the default switch in _arity.js and nAry.js seems fixed the issue.
default:
        return function (...args) {
          return fn.call(this, ...args);
        };

@venba: We will switch to something like that after v1.0.  Current versions of Ramda still support ES3/ES5.

I had trouble trying to type this function in TypeScript. Here's my best attempt that actually works:
const nxprod = <T>(list: T[][]) =>
  list.reduce(
    (newlist, domain) => R.xprod(newlist, domain).map(([xs, y]) => [...xs, y]),
    [[]] as T[][]
  );

It's not point-free, and I had to replace unnest with an explicit append function. (Which should be equivalent to flip(append)), but somehow isn't)

authors: CrossEye Kinrany philipyoungg venba

repo: ramda/ramda


text:
feature : findOr lastOr nthOr

Have a good time. Thank you for the beautiful library!) I noticed a strange feature. Why will the call of head([]) return undefined, and the call of tail([]) return an empty array? Can it fix the behavior of R.head and also return an empty array? It will allow you to use Ramda more safely and avoid using Maybe monad. The same applies to the functions find, last nth . Or you can add findOr, lastOr nthOr, headOr functions like propOr?
I've seen such offers in Issue before. I propose to think again about this trick. Thank you again for your great tool.
I'm not arguing with you. There is a great helper defaultTo, but in my opinion the introduction of the proposed features will avoid unnecessary movements.
const safeHead = R.compose(R.defaultTo([]), R.head);
const safeFind = R.compose(R.defaultTo({}), R.find);

safeHead([]);
safeFind([{}]);

@CrossEye @saurabh-ku There's good sense in what you're saying. Would that mean undefined is a good value for tail to return?
While [] as a default is problematic for the reasons above, the inconsistency is confusing at the moment and a change in one direction or the other seems better than none at all.

For consistency I‘d recommend R.splitAt(1) which returns the „head“ and the „tail“ as arrays. R.splitAt(1)([]) = [[], []].
While I agree that in principle  head as nth(0) too should return a Maybe, returning undefined from R.tail instead of an empty array is dangerous because it breaks sequential iteration over the rest of the array. Which [] does not.

authors: mg901 semmel zacnomore