Bug using svelte-check when having tailwind's experimental features turned on

If you write export const experimental = "all" in tailwind.config.js then you get a huge upgrade to the @apply rule. Namely then you can suddenly write @apply hover:bg-red-200, which you couldn't do before.
Unfortunately however, with how this template is currently set up svelte-check will complain that that is not valid syntax. The reason for that is that svelte.config.js doesn't actually use postcss.config.js and therefor it doesn't use tailwind.config.js and therefor svelte-check is not aware that tailwind's experimental feature has been turned on.
I've been able to fix it in my own repo. It wasn't quite as simple as just requiring postcss.config.js, because all those other config files were written in ES6 format, while svelte.config.js was written in Node format and that makes it impossible to use require(). So I had to convert all those config files to Node format.
Right now I'm a bit too lazy to open a PR, but here's the commit in which I fixed the problem for myself. One extra benefit of how I have it now, is that svelte.config.js is the one and only source of truth regarding preprocessing configuration.

If you write export const experimental = "all" in tailwind.config.js then you get a huge upgrade to the @apply rule. Namely then you can suddenly write @apply hover:bg-red-200, which you couldn't do before.

Enabling experimental features will introduce warnings that may confuse people into thinking this project doesn't work.
Thanks for hunting down that this is a problem and fixing it. It's clearly an improvement, but I hate CommonJS a lot and don't know for sure if I'll spend the time refactoring all 3 templates (and my own sites that use them) to use it to fix validation and Tailwind CSS IntelliSense. I'd sooner hope for these tools to support ES imports [does VS Code run extensions as CommonJS or something?] than downgrade.
Hard situation 😦.

I also hate CommonJS, it's ugly. However, these experimental features of tailwind will soon be default features. And especially the upgraded @apply feature is gonna be very popular. So I'm afraid that if you don't switch those config files to CommonJS then soon you won't be able to use the latest version of tailwindcss anymore.
I don't know if the makers of svelte-check can make it work with ES6 modules, but if I were you I wouldn't (want to) count on that.

However, these experimental features of tailwind will soon be default features. And especially the upgraded @apply feature is gonna be very popular.
Not for certain. They're allowed to change, and because they're experimental features, should be opt-in.

So I'm afraid that if you don't switch those config files to CommonJS then soon you won't be able to use the latest version of tailwindcss anymore.
Only for validation (which I assume can be overridden with whatever the svelte-check ignore comment is); the features still work.

Not for certain.

You think there's a chance that the upgraded @apply won't be made default in the next version of tailwindcss? To me it seems basically guaranteed. They themselves said it's the most requested feature ever and they've finally been able to make it work.

and because they're experimental features, should be opt-in

Sure, I'm not asking you to turn on those experimental features in your template. Because I agree, they should be opt-in. I'm just asking you to prepare your template such that when someone does opt in, that everything just works as they expect.

Only for validation (which I assume can be overridden with whatever the svelte-check ignore comment is); the features still work.

True, but looking at the trade-off I'd say that having validation working is much more valuable than having a few config files in ES6 format which we find prettier code to look at.

So I had also reported this bug in the svelte language tools repo:
https://github.com/sveltejs/language-tools/issues/484
And their solution was to add a note to their documentation to make clear that you can only use CommonJS in your config files:
https://github.com/sveltejs/language-tools/commit/50682449663795b3ef9d95adc64d037801368bc8

Note that within your config files you can only use node-syntax, things like import ... or export const ... are not allowed.

In other words, I think this confirms that they have no intention to make svelte check work with a ES6 config file.

This will be solved when https://github.com/babichjacob/sapper-postcss-template/commit/7f4d826cb4c286d3b70c4adb20a8c906b446a00d makes its way downstream here.

In other words, I think this confirms that they have no intention to make svelte check work with a ES6 config file.

It's more like a ESM-CommonJS-thing that's happening. The problem is that our code is CommonJS and is using require to synchronously load the configs. Using the async import is not an option. If you can give me any pointers how I can make this work, I'm happy to take a look.

This will be solved when babichjacob/sapper-postcss-template@7f4d826 makes its way downstream here.

This has been here as https://github.com/babichjacob/sapper-firebase-typescript-graphql-tailwindcss-actions-template/commit/35d43ac3de18395b559722dbd0010fdd46f17854 since yesterday but I forgot to point it out

In other words, I think this confirms that they have no intention to make svelte check work with a ES6 config file.

It's more like a ESM-CommonJS-thing that's happening. The problem is that our code is CommonJS and is using require to synchronously load the configs. Using the async import is not an option. If you can give me any pointers how I can make this work, I'm happy to take a look.

I looked in to how rollup is able to load ES rollup.config.jss, but it's unfortunately await import too.
 [Disclaimer: I won't have the resources to help fix it]

We currently dynamically require for three things:

User's Svelte version/module. That's inside some async context so it would'nt be a problem there
User's Prettier version/module. Also inside async context.
The preprocess config. This one is in a synchronous path, because it's possible to get invoked from the typescript language service which is all synchronous, so no way to getting that asynchronous. The only thing we could do is to change the lookup of a svelte.config.js so that it's only done once on startup, not per file. But this would limit people to only have one svelte.config.js per project, so this would be kind of a breaking change - although I doubt it will break anyone because noone has more than one svelte.config.js in his project.


Stacked net should validate all layer configurations before runtime. Wrong config can produce cryptic exception (bcs) or ignored (wcs)

        .layer(0, new RBM.Builder().nIn(inSz).nOut(1000).build())
        .layer(1, new RBM.Builder().nIn(1000).nOut(500).build())
        .layer(1, new RBM.Builder().nIn(500).nOut(1000).build()) //<- wrong index starting here
        .layer(2, new OutputLayer.Builder().nIn(1000).nOut(numRows*numColumns).build())

This config throws following exception at runtime:
Exception in thread "main" org.nd4j.linalg.exception.ND4JIllegalStateException: Cannot execute matrix multiplication: [10, 1000]x[500, 1000]: Column of left array 1000 != rows of right 500
at org.nd4j.linalg.util.LinAlgExceptions.assertMultiplies(LinAlgExceptions.java:90)
at org.nd4j.linalg.api.ndarray.BaseNDArray.mmuli(BaseNDArray.java:2857)
at org.nd4j.linalg.api.ndarray.BaseNDArray.mmul(BaseNDArray.java:2723)
at org.deeplearning4j.nn.layers.feedforward.rbm.RBM.preOutput(RBM.java:318)
at org.deeplearning4j.nn.layers.feedforward.rbm.RBM.propUp(RBM.java:338)
at org.deeplearning4j.nn.layers.feedforward.rbm.RBM.propUp(RBM.java:328)
at org.deeplearning4j.nn.layers.feedforward.rbm.RBM.sampleHiddenGivenVisible(RBM.java:228)
at org.deeplearning4j.nn.layers.feedforward.rbm.RBM.computeGradientAndScore(RBM.java:119)
at org.deeplearning4j.optimize.solvers.BaseOptimizer.gradientAndScore(BaseOptimizer.java:158)
at org.deeplearning4j.optimize.solvers.StochasticGradientDescent.optimize(StochasticGradientDescent.java:57)
at org.deeplearning4j.optimize.Solver.optimize(Solver.java:51)
at org.deeplearning4j.nn.layers.BaseLayer.fit(BaseLayer.java:574)
at org.deeplearning4j.nn.multilayer.MultiLayerNetwork.pretrain(MultiLayerNetwork.java:274)
at org.deeplearning4j.nn.multilayer.MultiLayerNetwork.fit(MultiLayerNetwork.java:1420)
at org.deeplearning4j.nn.multilayer.MultiLayerNetwork.fit(MultiLayerNetwork.java:1400)
at org.deeplearning4j.nn.multilayer.MultiLayerNetwork.fit(MultiLayerNetwork.java:1477)
Net configuration should be validated before runtime. E.g. all layers are present and there are no duplicates. Tested on a few net types. Some nets don't even hit any runtime problems and therefore can produce unintended results.

@AlexDBlack i think network validation was imporved since this issue was opened, and it's safe to close now?


Makes sure the socket plugin's thread is only started on loading of plugin

Short Description:
Added a guard that prevents the socket plugin from multiple threads (leading to 'address already in use') being started.
Changes:

Makes sure the socket plugin's thread is only started on loading of plugin
@OpenPoGo/maintainers

Without the guard the thread is started for every import of the plugin.

👍

:+1:


Customize the Entity context menu in Catalog

In the Expedia group, we don't use the "unregister entity" or other menu options as we have a different way of deleting entities in our setup. So, for some organizations which don't use the unregister or inspect entity, it must be removable and all other menu items must be customizable for example e.g. badges in the menu item.

Feature Suggestion
To help with the above use case, it's better to not hardcode the menu items like here and give the users option to customize the items in the menu by passing custom values from the entity page, the same way as the extra menu items  options here
Possible Implementation
Add "unregister entity", "inspect entity" via "UNSTABLE_extraContextMenuItems" similar to badges from the entity page instead of hardcoding it here
Do similar checks here  to disable the "Unregister entity" button in the entity page itself, so that users have control over the menu item.
Context
To make the entity context menu customizable.
I would like to work on this if you all think this approach works.

@benjdlambert @emmaindal any thoughts on this issue? :)

Thanks for opening this issue @SuganJoe I think the capability to compose the context menu makes totally sense to me. I see the UNSTABLE_extraContextMenuItems is prefixed with UNSTABLE so not sure if the plan is to deprecate that. In general for how to compose it, I'll leave it up to @backstage/maintainers, as I can imagine there is some patterns (you mentioned one of them) that one can follow for the catalog.

Hi! There's is an option for disabling the unregister button :)
See https://github.com/backstage/backstage/blob/master/plugins/catalog/src/components/EntityLayout/EntityLayout.tsx#L146 which can be passed into as props to EntityLayout.

Wondering if we can make https://github.com/backstage/backstage/blob/master/plugins/catalog/src/components/EntityLayout/EntityLayout.tsx#L147 boolean | VisibleType  and then deprecate the boolean in favour of type VisibleType = 'visible' | 'hidden' | 'disabled' instead? The name of that is probably not great, so feel free to pick something better :)

@benjdlambert tried locally and this works perfectly for all scenarios.
Do you mean to initially keep  disableUnregister  as boolean | VisibleType both and at a later time, deprecate the boolean and just use VisibleType. Is it because the adapters of the code need a change if we directly switch from boolean to VisibleType?

We should support both and do the checking inside the component to see if it's a boolean then use the existing behaviour, but if it's of a string type then check what the string is set to and do the new behaviour. Maybe you could also console.warn if boolean is provided with a deprecation messaetg.

Hi! There's an option for disabling the unregister button :) See https://github.com/backstage/backstage/blob/master/plugins/catalog/src/components/EntityLayout/EntityLayout.tsx#L146 which can be passed into as props to EntityLayout.

I would like to disable "Unregister entity" option. @benjdlambert Can you please provide an example to achieve this? I am not sure how to pass the properties. (new to Backstage IO and React)


Has anybody had success implementing Drag & Drop ordering or Numbered ordering?

Is there a way to implement either of these two things?
Here's an example of  Drag and Drop ordering->
http://jquery-datatables-row-reordering.googlecode.com/svn/trunk/index.html
And this is an example of Numbered ordering

I have not tried either.


NFT #0: get wallet address for payments (artist or MOI?)

Technically, this is a question of who the creator address is set to when we create the first auction.
The contracts expect PA payment to receive the artists' portion, exchange it to USD and settle their LFOs on their behalf. So, technically, the creator address should be set to MOI to receive the 40%. This makes me realise that naming it creator was misleading - my apologies: it should be community or partner or something like that. Naming things huh...
My suggestion here is that we use the FTX account that was set up as the address for MOI, take the 50% that will be sent to payment address, exchange it, pay what we can of Sammie's debts and get the receipts for that ourselves, as it is important that this is handled by PA, both for easier logistics, and for reasons of precedent and clarity for future projects.


create cookbook about VRaptor + ExtJS

same of https://github.com/caelum/vraptor4/issues/761

@Turini, I'm studying AngularJS and 'll try to write a sample in the next days. :)

It sounds great! Thanks @henriqueluz


The password reset link is not working.

The password reset link is not working, is stopping at Token is already use, but it isn't used before,

Problem with resetPassword.php file

I've just ran this now locally and it works perfectly for me, I'll close this as this was some time ago.


Installation Failed

@mianumar5653 commented on Tue Oct 22 2019
Problem encountered on https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/install
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

@mianumar5653 Can you please share your VS Version and provide any error messages you received while installing?

Closing due to lack of activity. If you're still hitting this issue please re-open and provided the requested information.


token-2022: Consider prohibiting creating non-transferable accounts without immutable ownership

Problem
It's possible to create a token account on a mint with the non-transferable extension without immutable ownership enabled. Immutable ownership is enforced during minting, so it's impossible to mint a non-transferable token to an account without immutable ownership.
This can be confusing, because it seems like it might be possible to have non-transferable tokens in an account with transferable ownership.
Solution
Consider throwing an error when trying to initialize a token account on a non-transferable mint without immutable ownership.

So, if I'm understanding this correctly:

In order to mint tokens to a non-transferable account, that destination must have an immutable owner
In order to transfer tokens from a non-transferable account, you can't

What would be the reason to allow creating a non-immutable owner token account on a non-transferable mint? I would say this only makes sense if the non-transferable extension can be removed, which at the moment it does not appear is the case.

What would be the reason to allow creating a non-immutable owner token account on a non-transferable mint?

I can't remember why we did it that way. It looks like it was just done like that in https://github.com/solana-labs/solana-program-library/pull/2912 without any other questions.

In order to transfer tokens from a non-transferable account, you can't

Also, lol

Can I try this issue? I'm going to

Can I have a try on this issue,
I will return the NonTransferableNeedsImmutableOwnership error when trying to initialize an account on a non-transferable mint without immutable ownership.

Yep that's the idea, and no need to ask for permission, go for it! We'll review your PR when it comes in

Fixed in #6206


PR: Modify test_introspection to test numpy issue case

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)
[ ] Included a screenshot (if affecting the UI)

Improve existing introspection test to cover issue case
Issue(s) Resolved

Fixes #8297
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: dalthviz

@dalthviz, this change is causing test_introspection to generate a segfault, and that's why our tests are failing.
So let's use a simpler code to get completions from:
import math
math.ta<Tab>

which should complete tan and tanh.


CAMEL-10517 - Remove Unnecessary suppress warnings

Thanks for the PR it has been merged. Do you mind closing this?

PR merged with https://github.com/apache/camel/commit/39a9f52232fcaa1d82b290622d24aa45523094d0


Fix function comments based on best practices from Effective Go

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared.
From effective go.
I generated this with CodeLingo and I'm keen to get some feedback, but this is automated so feel free to close it and just say "opt out" to opt out of future CodeLingo outreach PRs.

Looks like these changes, few as they are, are reasonably solid. Although, it apparently didn't know how to add the function name again here :laughing: Let me know if you find this useful :smile: and if not, would fixing up that bug make it useful?
Note: I've only updated functions that I know CodeLingo can rewrite nicely, but you can install it from the GitHub marketplace to review your PRs automatically and find all issues.


Swap - Send a message to a Vault (TON) - Sender instance

Docs

Step 4. Send a message to a Vault (TON)
The final step is to send a message with the appropriate amount of TON to Vault (TON).

TypeScript

import { toNano } from '@ton/core';

// ...

const amountIn = toNano('5'); // 5 TON

await tonVault.sendSwap(sender, {
  poolAddress: pool.address,
  amount: amountIn,
  gasAmount: toNano("0.25"),
});

I'm having a difficulty how to to create this sender instance. Can someone please help me?

	import { TonClient4, WalletContractV4 } from "@ton/ton";

	const tonClient = new TonClient4({
		endpoint: "https://mainnet-v4.tonhubapi.com",
	});

	const walletContract = tonClient.open(
		WalletContractV4.create({
			workchain: 0,
			publicKey,
		}),
	)

	const sender = walletContract.sender(privateKey)

Thank you @MurkyMeow


[WIP] Add border styles & triangle primitives

Will fix #119 & #120

To-Do:

[x] Fix child nodes to correctly respond to the translated world when using borders (https://github.com/jordwalke/flex/blob/master/src/lib/LayoutSupport.re#L453-L461) -- in case anyone else has a similar issue, make sure you're using Encoding.cssUndefined as the default value instead of 0.
[x] Optimize the math for triangle texture coordinates (at the very least remove the list/fold operations to find the max & unfold that to pattern matching)
[x] Improve readability/reduce codesize for border rendering function
[x] Make sure that it's okay to multiply to apply the translation
[x] Disable junctions when there aren't borders being connected

Wow, awesome progress @OhadRau ! 💯

Apart from cleaning up the border drawing function, I think I've got all the features/edge cases accounted for here. Let me know if there's anything else I should take a look at or add to this PR.

@OhadRau - looks great to me! I'm ready to bring this in whenever you are. Thanks again for your work on this!
I tested out transparent borders, got some fun results with that:

@OhadRau - looks great to me! I'm ready to bring this in whenever you are. Thanks again for your work on this!

Awesome! As far as I can tell everything is ready unless you think we should add borders to images/text nodes as well.

I tested out transparent borders, got some fun results with that

Huh, didn't really think about that case... I just checked to see what browsers do for that with this JSFiddle and it looks like it's pretty much the same behavior, but it might make more sense to check if both edges are going to be rendered before inserting the corner piece. Don't think that should be a difficult fix if that's the behavior we want to go for.
@bryphe

Huh, didn't really think about that case... I just checked to see what browsers do for that with this JSFiddle and it looks like it's pretty much the same behavior, but it might make more sense to check if both edges are going to be rendered before inserting the corner piece. Don't think that should be a difficult fix if that's the behavior we want to go for.

Actually this is the 'right' behavior from my perspective - it lets you do this CSS trick: https://css-tricks.com/snippets/css/css-triangle 😄 Sorry it wasn't clear from my comment.
So the way we have it is perfect - I take advantage of this behavior sometimes - so I'm glad it works the way it does.

Ah interesting, had no idea about that. Only other behavior that might be weird is that borders inherit the opacity style, but again looks like that's what's done in CSS as well. Assuming that's correct, I guess this PR is good to go.

Assuming that's correct, I guess this PR is good to go.

Perfect - awesome contribution to the project, @OhadRau ! Thank you!


How can I modify hotkeys for human when using pysc2 to play starcraft2

I can't modify hotkeys for human when using pysc2 to play starcraft2.

https://discordapp.com/channels/350289306763657218/369596356953636876/748610536614133801


Grant application - High-availability validator setup

Project Abstract
Validator leader selection via Raft consensus. Based on an already defined grant
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

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

Would be great to see alternative validator setups!
I think that when I wrote the RFP, I wasn't fully aware of how validators determine whether it's their turn.
If I'm not mistaken, right now milestones 1 & 2 are kind of no-op, the validator should know exactly when they are valid block producers.
I would suggest that the application is revised by doing some further research, and that the prospective grantee proposes a concrete revised mechanism for Raft consensus for nodes.
At that point, we should ask some Parity consensus devs about this. It's somewhat analogous to the remote signing keystore, and might need changes to the core protocol (though maybe not, I'm not sure myself).

ping @bufta

Hi @semuelle, sorry, I should have probably written an update here - we've been trying to contact Parity to confirm the ideas behind this proposal with their devs, as suggested by @mmagician. For what I understand, this is necessary for our proposal to be accepted. I will keep you informed how it's going (although no luck with response for now).

I'm coming back with an update - we sent the description of our approach along with some questions to the Parity developers and should receive their answers after 7th November. Hopefully, afterwards we will get back with our revised proposal.

Sounds good @bufta, thanks for the update. I'll put the application on hold until then.

@bufta just checking in here, any updates?

As far as I know, they are still waiting for feedback from parity. So I will close the application for now and we can reopen it later.

@alxs @Noc2 Yes, indeed we are still waiting for the feedback from Parity devs. I will ping them once again. As soon as we get their opinion and adjust the proposal if necessary, we'll go with the PR once again.

@bufta as long as you don't force-push, you can leave a comment here and we'll reopen this PR.

Hi @alxs can I ask you to reopen this PR please? We're ready to follow with the solution that was discussed with Parity developers.

@bufta, I reopened it. Feel free to update it.

Thank you @Noc2! The original proposal has been updated based on the feedback we got in late November 2022 from the Parity developers team.

Ah, yes, sorry @Noc2. I updated the file

The cost stems from the fact that we wanted to include in calculations the period when we were redoing and discussing the solutions in the autumn while checking with Parity. However, taking into account your comment @Noc2 , we will take this part on us. I edited the application accordingly.

Just to check, is there anything else we should improve or add at this stage @Noc2 ? Are our answers sufficient or maybe we should add more information @takahser?


incompatible with latest go/x/exp package

What did you do?
I have integrated the prometheus library into a project as a dependency and it fails to build if using the latest x/exp package. The issue seems to be that the slices package has been updated to use a different call signature.
https://cs.opensource.google/go/x/exp/+/302865e7556b4ae5de27248ce625d443ef4ad3ed
It seems that the stdlib implementation of this uses the int comparable, so prometheus should probably follow that.
What did you see instead? Under which circumstances?
Would expect it to build in supported Go versions.

To be clear this isn't really a bug, but it was surprising to me as a user of the package. I am able to work around it by explicitly depending on an earlier version of the exp package.

Maybe this was fixed by #12650

Hello from the bug scrub!
This indeed appears to be fixed long ago.


Use django-nose

Testing in django is not perfect, For one it is slow and does not allow to run tests individually, making writing tests slower and more annoying then needed.
django-nose purports to solve many of these issues. Nice.

Testing in Django has improved in later versions, so we won't do this.


Opening a new terminal cannot find the previously set node

Operating system and version:
nvm debug output:

nvm --version: v0.39.3
$SHELL: /usr/bin/zsh
$SHLVL: 1
whoami: 'huawei'
${HOME}: /home/huawei
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${HOME}/.g/bin:${HOME}/.g/go/bin:${NVM_DIR}/versions/node/v18.16.0/bin:${HOME}/.sdkman/candidates/maven/current/bin:${HOME}/.sdkman/candidates/java/current/bin:${HOME}/.g/bin:${HOME}/.g/go/bin:${HOME}/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:${HOME}/.local/share/JetBrains/Toolbox/scripts:${HOME}/.cargo/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: 'https://npmmirror.com/mirrors/node/'
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'zsh 5.7.1 (x86_64-debian-linux-gnu)'
uname -a: 'Linux 5.10.0-amd64-desktop #<IP_ADDRESS>-release SMP Wed Jun 8 17:30:51 CST 2022 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
OS version: UnionTech OS GNU/Linux 20
awk: /usr/bin/awk, GNU Awk 4.2.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.1.2)
curl: /usr/bin/curl, curl 7.64.0 (x86_64-pc-linux-gnu) libcurl/7.64.0 OpenSSL/1.1.1d zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
wget: /usr/bin/wget, GNU Wget 1.20.1 built on linux-gnu.
git: /usr/bin/git, git version 2.20.1
ls: cannot access 'grep:': No such file or directory
grep: grep: aliased to grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} (grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox}), grep (GNU grep) 3.3
sed: /usr/bin/sed, sed (GNU sed) 4.7
cut: /usr/bin/cut, cut (GNU coreutils) 8.30
basename: /usr/bin/basename, basename (GNU coreutils) 8.30
rm: /usr/bin/rm, rm (GNU coreutils) 8.30
ls: cannot access 'mkdir:': No such file or directory
mkdir: mkdir: aliased to nocorrect mkdir (nocorrect mkdir), mkdir (GNU coreutils) 8.30
xargs: /usr/bin/xargs, xargs (GNU findutils) <IP_ADDRESS>-235f
nvm current: v18.16.0
which node: ${NVM_DIR}/versions/node/v18.16.0/bin/node
which iojs: iojs not found
which npm: ${NVM_DIR}/versions/node/v18.16.0/bin/npm
npm config get prefix: ${NVM_DIR}/versions/node/v18.16.0
npm root -g: ${NVM_DIR}/versions/node/v18.16.0/lib/node_modules

nvm ls output:

       v16.20.0
->     v18.16.0
default -> v16.18.0 (-> N/A)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v18.16.0) (default)
stable -> 18.16 (-> v18.16.0) (default)
lts/* -> lts/hydrogen (-> v18.16.0)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.0
lts/hydrogen -> v18.16.0

How did you install nvm?

Git Install
What steps did you perform?
What happened?
When I open a terminal and set it up with the command node use --lts and then type node -v, I get the output, but when I open a new terminal and execute node -v it says zsh: command not found: node.
What did you expect to happen?
I should be able to output the version information when I enter the new terminal, because the node version was set before that
Is there anything in any of your profile files that modifies the PATH?

Here's some of the information I've configured myself

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

node use --lts isn't a thing; do you mean nvm use --lts?
If so, use is only ever for the life of the shell session. You want nvm alias default lts/*, for example, if you want the latest LTS version to be the default.


[PE-D][Tester A] Wrong validation prompt for updating client

I tried running this command "uc -e<EMAIL_ADDRESS>-cn " where I want to update a valid client using her email with an empty client name. However, the validation error prompts that the email is in an invalid format which is not true.
I did further testing and this is similar for cases whereby I use -src, -mn, etc instead of -cn and leave that field empty. Could be due to the sequence of validation checks!

Labels: severity.Low type.FunctionalityBug
original: Irminrics/ped#4

Duplicate of #245


Sign In with Apple capability disabled when building

Summary
In version 0.38.2, managed workflow, the "Sign In with Apple" capability gets disabled when building.
Our build command and output sample (STAGE gets passed to app.config.js):
STAGE=development eas build --profile development --platform ios
[...]
✔ Synced capabilities: Disabled: Sign In with Apple
✔ Synced capability identifiers: No updates
[...]

Other capabilities (Associated Domains and Push Notifications) remain enabled as expected.
Downgrading to eas-cli 0.37.0 fixes the issue and re-enables the capability.
I have "expo-apple-authentication": "~4.0.3" installed and no other config related to it (per the docs for managed workflow).
Environment
  EAS CLI 0.38.2 environment info:
    System:
      OS: macOS 12.0.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
      Yarn: 1.22.17 - /opt/homebrew/bin/yarn
      npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
    Utilities:
      Git: 2.33.1 - /opt/homebrew/bin/git
    npmPackages:
      expo: ^43.0.0 => 43.0.1
      expo-dev-client: ~0.6.3 => 0.6.3
      react: ^17.0.2 => 17.0.2
      react-dom: ^17.0.2 => 17.0.2
      react-native: 0.64.3 => 0.64.3
      react-native-web: 0.17.1 => 0.17.1
    npmGlobalPackages:
      eas-cli: 0.38.2
      expo-cli: 4.13.0

Error output
Here's debug output for the capability sync section of the build command (IDs and domains elided):
- Syncing capabilities
Current remote capabilities:
[
  {
    "context": {
      "providerId": 121041716,
      "teamId": "[...]"
    },
    "id": "LRLK3GA2R2_GAME_CENTER",
    "attributes": {
      "ownerType": "BUNDLE",
      "settings": [
        {
          "key": "GAME_CENTER_SETTING",
          "options": [
            {
              "key": "GAME_CENTER_IOS",
              "properties": [
                null
              ]
            }
          ]
        }
      ],
      "editable": true,
      "inputs": null,
      "enabled": true,
      "responseId": "bdee819d-437a-4aea-bb43-497efe3bc199"
    }
  },
  {
    "context": {
      "providerId": 121041716,
      "teamId": "[...]"
    },
    "id": "LRLK3GA2R2_IN_APP_PURCHASE",
    "attributes": {
      "ownerType": "BUNDLE",
      "settings": null,
      "editable": true,
      "inputs": null,
      "enabled": true,
      "responseId": "bdee819d-437a-4aea-bb43-497efe3bc199"
    }
  },
  {
    "context": {
      "providerId": 121041716,
      "teamId": "[...]"
    },
    "id": "LRLK3GA2R2_PUSH_NOTIFICATIONS",
    "attributes": {
      "ownerType": "BUNDLE",
      "settings": null,
      "editable": true,
      "inputs": null,
      "enabled": true,
      "responseId": "bdee819d-437a-4aea-bb43-497efe3bc199"
    }
  },
  {
    "context": {
      "providerId": 121041716,
      "teamId": "[...]"
    },
    "id": "LRLK3GA2R2_APPLE_ID_AUTH",
    "attributes": {
      "ownerType": "BUNDLE",
      "settings": [
        {
          "key": "APPLE_ID_AUTH_APP_CONSENT",
          "options": [
            {
              "key": "PRIMARY_APP_CONSENT",
              "properties": [
                null
              ]
            }
          ]
        }
      ],
      "editable": true,
      "inputs": null,
      "enabled": true,
      "responseId": "bdee819d-437a-4aea-bb43-497efe3bc199"
    }
  },
  {
    "context": {
      "providerId": 121041716,
      "teamId": "[...]"
    },
    "id": "LRLK3GA2R2_ASSOCIATED_DOMAINS",
    "attributes": {
      "ownerType": "BUNDLE",
      "settings": null,
      "editable": true,
      "inputs": null,
      "enabled": true,
      "responseId": "bdee819d-437a-4aea-bb43-497efe3bc199"
    }
  }
]

Current local entitlements:
{
  "com.apple.developer.associated-domains": [
    "applinks:[...]
  ],
  "aps-environment": "development"
}
Skipping existing capability: com.apple.developer.associated-domains (Associated Domains)
Remaining to remove:  [
  'LRLK3GA2R2_GAME_CENTER',
  'LRLK3GA2R2_IN_APP_PURCHASE',
  'LRLK3GA2R2_PUSH_NOTIFICATIONS',
  'LRLK3GA2R2_APPLE_ID_AUTH'
]
Skipping existing capability: aps-environment (Push Notifications)
Remaining to remove:  [
  'LRLK3GA2R2_GAME_CENTER',
  'LRLK3GA2R2_IN_APP_PURCHASE',
  'LRLK3GA2R2_APPLE_ID_AUTH'
]
Existing to disable:  [
  'LRLK3GA2R2_GAME_CENTER',
  'LRLK3GA2R2_IN_APP_PURCHASE',
  'LRLK3GA2R2_APPLE_ID_AUTH'
]
Patch Request: [ { capabilityType: 'APPLE_ID_AUTH', option: 'OFF' } ]
✔ Synced capabilities: Disabled: Sign In with Apple
- Syncing capabilities identifiers
No capability identifiers need to be updated
✔ Synced capability identifiers: No updates

Reproducible demo or steps to reproduce from a blank project
Don't have time now to reproduce from scratch. Let me know if you need more info about our project.

I'm also running into this bug.
Referencing the docs, the capability sync can be disabled, but I haven't been able to figure out where to use "EXPO_NO_CAPABILITY_SYNC=1".

This looks correct to me, based on the introspected entitlements object (no apple sign in entitlement):
{
  "com.apple.developer.associated-domains": [
    "applinks:[...]
  ],
  "aps-environment": "development"
}

Perhaps you have a local entitlements file in your ios folder (?) and this is preventing the introspection.
This can be resolved by either syncing the bare entitlements locally expo prebuild -p ios --no-install or by clearing the ios folder and reverting back to managed workflow.

@EvanBacon Nope, no ios folder -- I'm using managed workflow. Downgrading to eas-cli 0.37.0 and building re-enables the capability again (no other project changes). Upgrading to 0.38.2 and building disables it.
I'm assuming based on the docs, all I need is the expo-apple-authentication dependency, no explicit config plugin?
When I build with 0.37.0 (no other project changes), it picks up the local Apple auth entitlement as expected:
EXPO_DEBUG=1 STAGE=development eas build --profile development --platform ios
...
Current local entitlements:
{
  "com.apple.developer.associated-domains": [
    "applinks:[...]"
  ],
  "aps-environment": "development",
  "com.apple.developer.applesignin": [
    "Default"
  ]
}
...
✔ Synced capabilities: Enabled: Sign In with Apple
- Syncing capabilities identifiers
No capability identifiers need to be updated
✔ Synced capability identifiers: No updates

I also noticed that the initial debug output is different between 0.37.0 and 0.38.2.

This looks correct to me, based on the introspected entitlements object (no apple sign in entitlement):
{
  "com.apple.developer.associated-domains": [
    "applinks:[...]
  ],
  "aps-environment": "development"
}

Perhaps you have a local entitlements file in your ios folder (?) and this is preventing the introspection.
This can be resolved by either syncing the bare entitlements locally expo prebuild -p ios --no-install or by clearing the ios folder and reverting back to managed workflow.

Just ran into this after upgrading to Expo 45 in the bare workflow and running this command fix it for me.

I see, this is possibly related to expo/expo-cli#4031 then, will investigate further.
Edit: this does appear to be a logic bug, as a temporary workaround, you can add:
app.json
{
  "expo": {
    "ios": {
      "entitlements": {
        "com.apple.developer.applesignin": ["Default"]
      }
    }
  }
}

This saved my day.


Prisma2 CLI setup message invisible in light terminal themes

Bug description
Upon running npm i -g prisma2, the user is presented with an instructional message saying "The package prisma2 has been renamed to @prisma/cli" with instructions about what to do to install Prisma 2.0—but the message is not visible to users with light terminal profiles.
For example, Solarized Light, iTerm2 on macOS:

How to reproduce
Change your terminal to a light theme and run npm i -g prisma2. You might get nothing visible, or you might get it in very faint gray. The text shows up ("bolded") when you select over it, like so:

Expected behavior
The message should be readable by users in light theme terminals.
Environment & setup

OS: macOS Catalina (10.15.4), using iTerm2 3.3.9 with Solarized Light theme built-in
Database: n/a
Prisma version: n/a
Node.js version: 13.13.0 (npm 6.14.4)

Thanks for reporting this! I can confirm this issue.

Candidating this as it's been quite a while now and this seems to be an easy fix.

We are not changing the transition package any more.


vue-devtools not recognizing components manually appended to DOM & $mounted

What problem does this feature solve?
Provide ability to debug manually appended & mounted components which is necessary in edge cases.
What does the proposed API look like?
import Mention from "./MentionSpan";

const ComponentClass = Vue.extend(Mention);
const instance = new ComponentClass({
   propsData: { id: result.id, removeFunction: this.
});
instance.$slots.default = [result.name];
instance.$mount();
vue-devtools.register(instance);

Just make sure to define a parent when creating the component instance:
const instance = new ComponentClass({
   propsData: { id: result.id, removeFunction: this.
  parent: this, // assuming you do this in e.g. mounted() or a component method
});

Hum, this doesn't seems to work anymore :(


Add 'kolide' to cf device posture integrations

acceptance tests all passing, thanks!
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareDevicePostureRule_" -timeout 120m -parallel 1
=== RUN   TestAccCloudflareDevicePostureRule_SerialNumber
--- PASS: TestAccCloudflareDevicePostureRule_SerialNumber (23.81s)
=== RUN   TestAccCloudflareDevicePostureRule_OsVersion
--- PASS: TestAccCloudflareDevicePostureRule_OsVersion (18.60s)
=== RUN   TestAccCloudflareDevicePostureRule_LinuxOsDistro
--- PASS: TestAccCloudflareDevicePostureRule_LinuxOsDistro (19.43s)
=== RUN   TestAccCloudflareDevicePostureRule_DomainJoined
--- PASS: TestAccCloudflareDevicePostureRule_DomainJoined (19.97s)
=== RUN   TestAccCloudflareDevicePostureRule_Firewall
--- PASS: TestAccCloudflareDevicePostureRule_Firewall (30.69s)
=== RUN   TestAccCloudflareDevicePostureRule_DiskEncryption_RequireAll
--- PASS: TestAccCloudflareDevicePostureRule_DiskEncryption_RequireAll (19.80s)
=== RUN   TestAccCloudflareDevicePostureRule_DiskEncryption_CheckDisks
--- PASS: TestAccCloudflareDevicePostureRule_DiskEncryption_CheckDisks (20.64s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	154.867s


[NETBEANS-283] private_key in libs.git module should be renamed

Sorry, about all the commits in this PR that don't relate to this PR -- if someone can advise how to get rid of them, that would be great. Only the last commit is applicable here.

Probably, your master branch has merge commits. Merge commits were created when you merged the upstream master branch into your master branch. This is not a fast-forward merge. e.g. This(https://github.com/geertjanw/incubator-netbeans/commit/eb425e4318aa3c391539a0ad5965c002f45dce0a) does not exist in the upstream master branch.
So you should clean up your master branch.
I assume that apache/incubator-netbeans repository is added as upstream.
The simplest way is removing your repository. Then fork apache/incubator-netbeans repository again.
Although I can take no responsibility...

Ah, good idea. I will delete the repo and fork from scratch.


Hosts blocked

During sync monerod on windows, almost at the end(98%), I got the log:

Is this okay? I just don't know it's my ISP has blocked the monerod IPs or the monerod servers blocked my IP. Firewall is off.

This is normal, monerod behavior. It's just blocking on its own misbehaving peers.


Death Script to Main Menu

Update player script line 72 to send you to main menu on death.

Rejected: create a game over scene and jump to that instead


Ruby-LSP and Ruby-LSP-Rails downgrade randomly

Description
Ruby LSP Information
This is a strange bug that I'm not sure how to reproduce, but I've been experiencing it for a while. Sometimes, the Ruby-LSP gem versions will randomly resolve and downgrade to v0.11.2. It seems to happen most often when I restart Ruby-LSP after updating the Gemfile or other gems. I am logging it here in case others are experiencing it also, or if others have figured out what causes and resolves it.
If I then cd into the .ruby-lsp directory and run bundle update, I can reverse the behavior.
I think it is related to the versions of other dependencies, but there's something weird about how they're setup so that they resolve incorrectly.
❯ cd .ruby-lsp
❯ bundle update ruby-lsp
Fetching gem metadata from https://gems.graphql.pro/..
Fetching gem metadata from https://gems.contribsys.com/..
Fetching gem metadata from https://gem.fury.io/angellist/...
Fetching gem metadata from https://rubygems.pkg.github.com/angellist/..
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Resolving dependencies...
Using logger 1.6.2 (was 1.6.1)
Using ruby-lsp 0.11.2 (was 0.22.1)
Using ruby-lsp-rails 0.2.6 (was 0.3.27)
Note: ruby-lsp version regressed from 0.22.1 to 0.11.2
Bundle updated!
2 installed gems you directly depend on are looking for funding.
  Run `bundle fund` for details
❯ bundle update ruby-lsp
Fetching gem metadata from https://gems.graphql.pro/..
Fetching gem metadata from https://gems.contribsys.com/..
Fetching gem metadata from https://gem.fury.io/angellist/...
Fetching gem metadata from https://rubygems.pkg.github.com/angellist/..
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Resolving dependencies...
Using ruby-lsp 0.22.1 (was 0.11.2)
Using ruby-lsp-rails 0.3.27 (was 0.2.6)
Bundle updated!
2 installed gems you directly depend on are looking for funding.
  Run `bundle fund` for details

:wave: Thank you for the report.
Just to rule out anything obvious, can you ensure you're on the latest release of bundler?


Android Icon not working

Hi
My application icon works correctly. However push notifications aren't using it like the default should.
When I set the resource instead it still shows the same, just a blank icon in the notification area.

@quintonv  any solution?

@quintonv any solution?

I ended up using a different plugin after not getting this to work

Which other plugin did you use ?


SaveStateAsync not working with tuples

Expected Behavior
Saving a tuple variable saves the actual value.
Actual Behavior
Saving a tuple variable saves the default value of that tuple type.
Steps to Reproduce the Problem
Assuming 'daprClient' is an instance of 'DaprClient':
(int, decimal) tuple = (1, 2.0m);
await daprClient.SaveStateAsync("statestore", "tuple", tuple);
(int, decimal) tuple2 = await daprClient.GetStateAsync<(int, decimal)>("statestore", "tuple"); // 'tuple2' is (0, 0.0m)

Edit:
This issue was about nullable tuples, but I then found out it also affects regular tuples.

@GianvitoDifilippo - Thanks for opening this issue! This actually has to do with the System.Text.Json serializer that we're using. In order to use tuples, you have to set the option IncludeFields to be true. If you don't, it'll ignore Tuple values.
I made a quick little validation if you would like to see how to set that and that it works with both nullable and non-nullable tuples.
[HttpGet("testTuple")]
public async Task<IActionResult> TestTuple()
{
	var options = new JsonSerializerOptions()
	{
		IncludeFields = true,
	};
	using (var client = new DaprClientBuilder().UseJsonSerializationOptions(options).Build())
	{
		(int, decimal)? nTuple = (1, 2.0m);
		logger.LogInformation($"Nullable - Saving Tuple: {nTuple}");
		await client.SaveStateAsync("statestore", "tuple1", nTuple);

		var stateNTuple = await client.GetStateAsync<(int, decimal)?>("statestore", "tuple1");
		logger.LogInformation($"Nullable - Retreived Tuple {stateNTuple}");

		(int, decimal) tuple = (1, 2.0m);
		logger.LogInformation($"Saving Tuple: {tuple}");
		await client.SaveStateAsync("statestore", "tuple2", tuple);

		var stateTuple = await client.GetStateAsync<(int, decimal)>("statestore", "tuple2");
		logger.LogInformation($"Retreived Tuple {stateTuple}");

		return Ok();
	}
}

And here's the output when I invoke that function:
== APP == info: TestBed.Web.Controllers.StateController[0]
== APP ==       Nullable - Saving Tuple: (1, 2.0)
== APP == info: TestBed.Web.Controllers.StateController[0]
== APP ==       Nullable - Retreived Tuple (1, 2.0)
== APP == info: TestBed.Web.Controllers.StateController[0]
== APP ==       Saving Tuple: (1, 2.0)
== APP == info: TestBed.Web.Controllers.StateController[0]
== APP ==       Retreived Tuple (1, 2.0)

I'm going to close this issue, but feel free to re-open it, or another issue, if you have further questions.

@halspang thank you for your reply. Moral of the story... never use plain tuples when doing anything more than basic stuff :)


Get Scan Result {message: 401 Unauthorized}

Describe the bug
A clear and concise description of what the bug is.
[main] INFO org.jfrog.build.extractor.maven.BuildDeploymentHelper - Artifactory Build Info Recorder: deploy artifacts set to false, artifacts will not be deployed...
[main] INFO org.jfrog.build.extractor.maven.BuildDeploymentHelper - Artifactory Build Info Recorder: publish build info set to false, build info will not be published...
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - BUILD SUCCESS
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - Total time:  3.466 s
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - Finished at: 2022-04-21T07:55:09Z
[main] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
07:55:09 [Info] Scanning module com.example:demo:0.0.1-SNAPSHOT...
07:55:09 [Info] Waiting for scan to complete...
07:55:14 [Info] Auditing frogbot-test master
07:55:15 [Error] GET https://gitlab.com/api/v4/projects/root/frogbot-test/repository/archive.tar.gz: 401 {message: 401 Unauthorized}
To Reproduce
Steps to reproduce the behavior
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions

Frogbot version:
Operating system:
JFrog Artifactory version:
JFrog Xray version:

Additional context
Add any other context about the problem here.

@0c0c0f,
Do you know what archive.tar.gz is? Is it a dependency of the '``frogbot-test``` project Frogbot is attempting to scan?
It looks like Frogbot tries to download this package from this GitLab URL, and fails during authentication -
https://gitlab.com/api/v4/projects/root/frogbot-test/repository/archive.tar.gz
This information will help us figure out the issue.

OK @0c0c0f - archive.tar.gz actually includes the content of the git repository Frogbot is attempting to scan. Are you running Frogbot on GitLab CI?

@0c0c0f,
Assuming you're GitLab CI, my guess is that the GitLab access token configured doesn't have sufficient permissions. Notice the following from the Frogbot documentation:
# [Mandatory]
    # GitLab access token with the following permissions scopes: api, read_api, read_user, read_repository
    JF_GIT_TOKEN: $USER_TOKEN

We would very much appreciate your feedback. We'd like to make sure this works for you.

@0c0c0f, Assuming you're GitLab CI, my guess is that the GitLab access token configured doesn't have sufficient permissions. Notice the following from the Frogbot documentation:
# [Mandatory]
    # GitLab access token with the following permissions scopes: api, read_api, read_user, read_repository
    JF_GIT_TOKEN: $USER_TOKEN

We would very much appreciate your feedback. We'd like to make sure this works for you.

Config JF_GIT_API_ENDPOINT Variable  Fix it


applyImpulse() in local coordinates

Is there a way to use applyForce(...) and applyImpulse(...) in the body's local coordinate system?

I'm super confused about how these work. I'm doing something like this:
playerBody.applyLocalImpulse( new CANNON.Vec3( -200, 0, 0 ), new CANNON.Vec3( 0, 0, 0 ) );
And this only affects my player if the absolute player body position.x is less than zero. I would expect this to affect my player regardless of position?

@DelvarWorld here's how I use it, hope that helps! https://github.com/satellite-game/Satellite-Mobile/blob/88b401047963cf9a1bd0e4fd72af82bea3ca0e95/client/game/classes/s.Controls.js#L85-L103


Added Nodemon

Added nodemon to the project dependencies and changed the start script to run nodemon ./src/index.js instead of node ./src/index.js.

Hey @shadowtime2000 thanks for the PR, However, I'd prefer to keep the bot template rather "dumb" and leave it up for the user to customize. Basically, I would prefer to not add another dependency if I could avoid it. Lmk your thoughts on this.

What if we add it as a setup question when they run npx peterthehan/create-discord-bot.

Hmm, that seems reasonable enough. Before I commit to it, let me do some research into nodemon (I'm not familiar with this package).

Nodemon is usually used as a development dependency so suggest it being installed as a dev dependency with npm install -D nodemon instead of it being installed as a dependency since nodemon is not required for the bot to run.
With this change you could use nodemon if you install the dependencies with npm install but if you don't want to use it you could do npm install --only=production or npm ci --only=production preventing nodemon from being installed.
As for the npm script you could add a "nodemon" script instead of replacing the default start script with nodemon.

So we could add nodemon as a dev dependency and have it run in a script like dev.

I think there are some solid ideas here. To do this justice, I'm going to close this PR and flush out a more comprehensive plan for allowing for some QOL dev dependencies to be selected in the installation process.
Off the top of my head, nodemon and prettier are nice candidates. I'll open up an issue for this and tackle this sometime tomorrow.


currency converter example

added the easiest currency converter with react js

Thanks. This is a good start but we're hesitant to merge more class examples. If you convert this to Hooks, feel free to resubmit.

@gaearon Sure I will convert this to a Hooks example. Thanks


"Dependency Cycle Found" does not give good information on what the loop is

It would be nice if a complete copy of the dependency graph was listed that caused the error (e.g. if a indirectly depends on a then this might be a -> c -> d -> b -> a).

The error message will now include the cycle in it:
    var graph = new DepGraph();

    graph.addNode('a');
    graph.addNode('b');
    graph.addNode('c');
    graph.addNode('d');

    graph.addDependency('a', 'b');
    graph.addDependency('b', 'c');
    graph.addDependency('c', 'a');
    graph.addDependency('d', 'a');

    graph.overallOrder(); // throws Error('Dependency Cycle Found: d -> a -> b -> c -> a')

Released version 0.4.0

Thanks for the fast update!


unignore test/

This is a merge request for 1.0.1. I seem to be unable to make make github see that...
When installing with npat=true the installation fails due to missing
files in test/. Fix is to unignore the test/ directory.
Bumped version in the hope of a minor release.

note that a downside of this is that the released package on npm is 1.1MB in size, 853,6kb is the test folder. I don’t know what npat=true is, is it still in use?


feat: diagnostic with labels

Summary

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

#6001  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @h-a-n-a and the rest of your teammates on  Graphite


ci: implement variable overload for release workflow

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 📝 Documentation Update
[ ] 🔖 Release
[ ] 🚩 Other

Description

This PR finishes the work started in #72
Related Tickets & Documents

Fixes #70 in GitHub actions
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 readme
[ ] 📜 contributing.md
[ ] 📓 docs
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

IMHO let's wait for the deploy preview this time 😂


rework block body vs block header

do an analysis of what is in the header and body and possibly reorganize.

Ed and Karan to review the choices made by the prev. engineers about the new bloc struct and determine if the changes needs to be made.

The state of block header / body at time of writing is, the body contains rewards and transaction hashes and the header contains everything else.
Of the fields in the header, the one that stands out as questionable is
/// The `EraEnd` of a block if it is a switch block.
pub(super) era_end: Option<EraEndV2>,

In my opinion, given the size when populated, this field should be in the body.
However, the current block includes this in the header, and there is a dependency in the era_supervisor create_new_era that expects to get that info from switch block headers. While it could be rewritten to use the body instead, there are a series of ripples that such a refactor would cause.
Given the available resources, including time, and the fact that this is the same as current block, my conclusion is that its not currently worth pursuing moving the era end data off the header.


Add Koan about Dictionnary

Add koan about Dictionnary

@NotMyself , @Benjioe you can assign this issue to me.

@NotMyself , @Benjioe you can assign this issue to me.

@NotMyself  @Benjioe
Please review my PR.


Verifier stack mismatch

During fuzzing an 64-bit binary only application with -V switch enabled I've got this message
[2019-06-25T12:41:52+0200][E][27709] fuzz_runVerifier():281 Verifier stack mismatch: (original) badbad1837b45977 != (new) 1837b45977

It seems nearly indentical except for badbad prefix.

I didn't manage to repro this. Please re-open if this still happens.


Added a file rr_strings.xml with translation into Russian

Added a file rr_strings.xml with translation into Russian

Please fix and reupload.
DO not modify untranslatable strings


feat: adds code blocks

Added support for code blocks in my fork, figured they might be wanted here! Feels like a good improvement, open to suggestions of course.
Here's a quick demo of how it works:
https://user-images.githubusercontent.com/25194960/228704711-12867cec-3b6e-4ba1-932c-37b64419ad9c.mp4
Let me know what you think!

oo @matthuang will be very happy w/ this, he requested this feature a while ago hehe
fantastic job on the first pass, the needed addition of an edit button is a lil annoying but had to be done ig— dont see a way around it
can we maybe make it just a lil icon that only shows up on hover like so:

also i think the copy code button is a little too in the way rn, but not sure the best place to put it, maybe we just ripoff chatgpt here?

Thanks for the suggestions! I'm working on these today. @transmissions11, here's what I'm working with so far for the new copy button - does Paradigm have an opinion on which icon packs to use? I'm currently just keeping the buttons as text for now until I have some direction there.
Stepping away for a few, but when I'm back I'll look into the new edit button and stopping generation.

does Paradigm have an opinion on which icon packs to use?

chakra ui comes bundled w/ some icons and happens to have the same perfect edit button so lets use that if possible! https://chakra-ui.com/docs/components/icon

https://user-images.githubusercontent.com/25194960/228968379-b66ac1ef-399a-41d1-94fa-b92f7fa5cff7.mp4
@transmissions11 addressed your comments and changed the edit button according to your suggestion.
Do we want the edit button on user nodes too? I left it out just because that's probably the most commonly edited area and most people won't be formatting code in their prompts, but maybe it will be good for consistent UX. Quick change if we want to add it.

addressed your comments and changed the edit button according to your suggestion.

looks fantastic!

Do we want the edit button on user nodes too? I left it out just because that's probably the most commonly edited area and most people won't be formatting code in their prompts, but maybe it will be good for consistent UX. Quick change if we want to add it.

yeah i think so now, sets us up nicely for https://github.com/transmissions11/flux/issues/24

seeing this for long lines, looks like we need a break-words or something somewhere?

@transmissions11 seeing this for long lines, looks like we need a break-words or something somewhere?

added break word to the parent column seems to have fixed this, think this was introduced sometime when fixing comments

@transmissions11 small off-topic, what does nit correspond to in conventional commits? I see it for the first time...

LFG tysm again @ghgoodreau and everyone else involved


Ask to skip polymer build at the beginning of a deploy

Unlike the backup name and card rendering, it waits until half way through a deploy to ask if you want to skip polymer building. That means if you walk away and come back it may have paused in the middle. It should ask you at the beginning.
What issue is this related to?

This was broken in dda1a1809f9fd9a961159ccbd5a657e8c30169b1


HomeKit msl100dnot following to "Ignore HomeKit Native Devices" setting

What issue do you have? Please be as thorough and explicit as possible.
I have 4 of these devices, they are HomeKit compatible and I have the  "Ignore HomeKit Native Devices" setting on, but they still show on the Home App
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge

Which version of Homebridge/HOOBS do you have?
1.6.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry

Which version of this plugin (homebridge-meross) do you have? Has the issue started since upgrading from a previous version?
8.5.3, Nope, right after the bulbs were added to the Meross account

Which Meross devices do you have that are causing issues? Please include product models if applicable.
msl100d
FW 4.1.8
HW 4.0.0

Hi @Xanderco
Thanks for reporting this. Please update to the beta version of the plugin. You should find these models are now removed!


Upgrade downloads are unnecessarily bloated with base64 encoding

Encoding binary in base64 in base64 being 133% (8/6) size of binary. If relavent, this occurs in Windows.
grcrestarter2.log in Program Files, renamed to txt to allow upload to GitHub: grcrestarter2.txt
Preview:
2016-07-24 10:37:33, Downloading blob with length 9593 starting with <BLOB>4E/CocPjdcpV8mKdJ3ioKGFN8SZqxlIieQdNturp4sUA9bZOdZcxz7mJleQnqlWE6nMSpGQaHFdbT2LUJobikKu8j0QnyCGbUmVOqgQ9WKnz2deKiUqPRHYGdtKcoIemZF4yFX8yoF60IaFZUCaXHOA8Mw2L4JCvEXLC1ul0Q6zXEnGNbvWHHJZAGuG4/aRgLNlLjAkxYXO7RC/SEw7kbmluRWeDE2sII7w9WotoW1HdNlN6XQxiHB5Nsv+/pAwBJSb1X0PUtpt435wcZd1KANaX5/hzAzrBUhBKYpFhYpr6Ss7Deme0D0XT0y3PuyiXSU3B69krXmwxf3rYsojgC8vA/H5dsIR++yVjui2BezW5IsR2YC8L0aEC0bKhelCs+W9Q7k03x57i1WJO8Yb/uOZGR+zMHqWTg8g0ta3KWmo3M7bp0fLBzEP2ZvOx3IkNYwxXDL1zpmUTmoMCLZ0uCcioX1EHGUKr+OlfmzYXx3Pg5onN1TsCeQzzoh1xxzu/Fx9C+JyhVmCcKMxPQ961KyKAYaMGFyFQzyadWKKopA1cUrVrMQsCAcoSPn67caMXk1WdF+mBpjleFrQB/DALhvkeqOaE9mJoAAlM/3pacC9khuSB4Q6MwHs6XywcnZtQNeiFVKb+EVtQTqBj9tAahZetdBvjLa5dGwfLjZWiSwrTzgqkuy2SdDNhB8Vz23yUF9o9dnLYaLzS4MvG9i/3UB7GInGfYd/isRhOTQw0Hwz5aiF9Qyjs468jf9gtSVuZGE+tOiSmtEw1EZXV4q+/x/rq0pVGQTlzadGRGhk0lJ3p8bOgPCBJBy2BPPLiXrauXVbKz4QzeWndIOsf/bLNZQv6N5y+Srv0tOelT//6tKjELK6SGMB8d2R7W5qbKOFD+THpe86cDH1baP1hilsOLtE9LiPoPNjObRiWDX6Z1322L2TlsamWqA37igtRl/G6tTy+9acnxBgbSSLVF87qOePKVZxv38ie+4
2016-07-24 10:37:33, Converting base64 encoded byte array length 9580 starting with 4E/CocPjdcpV8mKdJ3ioKGFN8SZqxlIieQdNturp4sUA9bZOdZcxz7mJleQnqlWE6nMSpGQaHFdbT2LUJobikKu8j0QnyCGbUmVO
2016-07-24 10:37:33, Decrypted byte array length 7168
2016-07-24 10:37:33, Writing bytes to C:\Program Files (x86)\GridcoinResearch\\gpuenumerator.dll with length 7168
2016-07-24 10:37:33, Closing file.

Binary downloads should be done as is, no base64 conversion.

Looks like this .NET code converts binary to base64 and back for several reasons, none of which have to do with storage space.
The only files downloaded are Changed files, so the process is fairly efficient.


⚠ Bofrost.at has degraded performance

In f86bb76, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1572 ms

Resolved: Bofrost.at performance has improved in f4f66d7 after 26 minutes.


Project Templates should be able to build on demand

Currently we have two templates in sdk branch that are checked in as zip files.
Have a way to build these templates during build or on demand.

Fixed


Replace Left-Hand Chapter Menu with Module Menu

Since we are adding new modules, we need to have a way of displaying them.
Currently the website is configured to display chapters, not modules.
Solving this problem would require refactoring our (on site) database. Please share any ideas or contributions here.

We are currently using this Figma board to explore ideas: https://www.figma.com/file/If6wwgh7KLKNYMOJzPXx31/OceanAcademy.io?node-id=0%3A1

This is part of Project Shrimp now:

Redesign of Left Menu

[ ] Refactor data. This is also part of #43 so see that issue for the reward bounty.
[ ] Create UI with React. Reward: ?
[ ] Hook up to UI to data. Reward: ?

Overall reward allocation: ?
@oceanByte

Merged with https://github.com/learn-ocean/ocean-academy/pull/57


Add oldest_waiting service

Currently, we have no way to determine if some transaction is blocked for a certain period of time.
A service oldest_waiting seems like a good idea.

I also want to monitor this.
The perf data is already available in backends_status - it should be trivial to add threshold levels for the max age of each status here.

using https://github.com/tobixen/check_pgactivity/blob/master/check_pgactivity it's possible to do like this:
check_pgactivity -s backends_status -w active=20s -c active=600s

and it will yield a warning if some query has been running for more than 20s.
not very well tested I must admit.

Hi, thanks for the PR, I'll look through it later, I have no time right now.

Change done in commit 9e10b450bde76a99ad3fd9e9cdb5f321c5a606c0. Thanks to Tobias Brox for his initial patch.


self::creating expects a person entry to already be present

Self-made relation... and this is the result

This is  a bug.

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description
from the 11.12 CHANGELOG:

update user and owner seeders with the ones from laravel-enso/core if they are not customized already (optional)

self::creating in the IsPerson trait seems to do an update; thus expecting an entry to already be there.
If I keep my existing UserSeeder configuration, the following error occurs

Steps to Reproduce

migrate:fresh --seed with a pre-11.12 userseeder (except for modifying owner to group)

Expected behavior

Seeding to happen
Actual behavior

Call to member function update() on null

Note that this will also cause issues if we User::Create(...) from inside the application (as adldap2 does for us if we have a new AD/LDAP user).
I still don't understand how using email as the relationship key makes sense here but that's another issue 😅

self::creating in the IsPerson trait seems to do an update; thus expecting an entry to already be there.
it is indeed

If I keep my existing UserSeeder configuration, the following error occurs
don't use the latest one

Note that this will also cause issues if we User::Create(...) from inside the application (as adldap2 does for us if we have a new AD/LDAP user).

use factory(User::class)->create() instead of User::create, and adapt the factory if you need so

I still don't understand how using email as the relationship key makes sense here but that's another issue 😅
where did you saw that? we have a person_id in the user's table for the relation.

use factory(User::class)->create() instead of User::create, and adapt the factory if you need so

Are we really supposed to use factory() for a user creation? That does not feel like the Laravel way, is it? (outside of a seeder that is).

where did you saw that? we have a person_id in the user's table for the relation.

Ye I noticed meanwhile, I saw that in a previous discussion we had. Sorry.
Seeing the actual implementation would mean I could have multiple users ( authenticatables ) attached to 1 person? 👍

use factory(User::class)->create() instead of User::create, and adapt the factory if you need so

Causes the same issue; as the person still doesn't exist. I'm also pretty sure no library will do a factory(User::class)->create([...]) when trying to implement a new user.
self::creating should just be updated to support provisioning the Person if it doesn't exist yet.

And the factory seems to be having issues even when having the exact same code as the core UserSeeder (apart from an extended User; but it extends EnsoUser so there shouldn't be an issue there...)

was still missing the Person... managed to seed using the new code. However the User::create([...]) related issue is still there (I just have a workaround for seeding now)

@jlsjonas in your issues you always tend to discuss about ~ 5 subjects. And in the following minutes you sort out 2/3 of them. Please be more considerate with my time. I will close this one now and I will kindly ask you to open another one per each subject. Please specify clearly if it's a bug, a question, a request, a discussion etc.
Thank you

@aocneanu the original bug report still exist; the other comments were just related to the debugging process in trying to fix/avoid them.
the exact original bug description still exist

I'm also pretty sure no library will do a factory(User::class)->create([...]) when trying to implement a new user. (and it definitely can't expect a tied-in Person class)

This is exactly the reason why there is a factory. And probably soon all Enso's code regarding to creating models will be moved from Models to Factories.

And probably soon all Enso's code regarding to creating models will be moved from Models to Factories.
From my understanding of Laravel; factories are only made to be used for seeding (usually random) data; not as the main implementation method, no?

Oh wow,
Factories are not invented in Laravel.
start here
then think about situations where you need a more complex logic to create an object (like Enso's user) and where would you write it

A in one place (factory) and use it all over the place where you need it (controllers, tests, database seeders, tinker)
B recreating that logic all over the place
C hiding it in magic methods, just so somebody could use a third party package and use self::create

take in consideration the fact that in time the app will grow to be more complex and probably you will have more people looking at the code, and you want readability, manageability and so on.


UVR-zn.py

Translate the interface language into Chinese。
Co-Authored-By: Anjok07<EMAIL_ADDRESS>

The interface is basically Chineseized, you just need to repackage the program as an installer. Using UVR-ZN.py


gocacheserver doesn't load AutoSaveFile on start

gocacheserver should automatically load the content of the AutoSaveFile in the cache if the AutoSave feature is enabled.

To clarify, the logic for automatically loading the data from the safe file was in gocacheserver/main/server.go, which is used by Dockerfile, so the docker image did support this without a problem.
I just thought that this logic should've been implemented in the server itself rather than in a main specifically used by gocacheserver's docker image.


FRJpvOMb: Replace Carthage with CocoaPods

add bundler
remove Cartfile
add and configure CocoaPods and dependencies
add build scripts
remove R.generated

 Replace Carthage with CocoaPods

 Replace Carthage with CocoaPods

 Replace Carthage with CocoaPods

 Replace Carthage with CocoaPods


Made the Navbar responsive again

Resolved #207
The navbar is responsive again, just changed a few measurements.

Thank you @Lok-ii


nixos/caddy: add support for caddy v2 (take 2)

Motivation for this change
The caddy module allows you to use Caddy 2 but it's broken (https://github.com/NixOS/nixpkgs/issues/92992). This PR is a new take at https://github.com/NixOS/nixpkgs/pull/86686, which has been dormant for a few weeks now. Since I'd really like to get Caddy 2 support in 20.09 I'm opening a new PR with the requested changes.
The tests pass when running the tests interactively (nix-build caddy.nix -A driver and then start_all() followed by test_script()), but they fail when running them non-interactively (nix-build caddy.nix) because the test directory created in the test cannot be found. Since I can't figure out why, any help is appreciated. (fixed!)
I would also like to bump the version to 2.1.1 instead of 2.0, but doing it gives me some go errors I don't know how to fix (eg<EMAIL_ADDRESS>is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt), so if someone knows how to make it work, it would be nice. (fixed!)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks @sephii, I fully support your effort. I'll take a look at the tests.

@ofborg test caddy

From what I can tell, the issue is that Nix doesn't recognize paths in a configuration file as being inputs. caddy-config.json looks like this:
{
    "apps": {
        "http": {
            "servers": {
                "srv0": {
                    "automatic_https": {
                        "skip": [
                            "localhost"
                        ]
                    },
                    "listen": [
                        ":80"
                    ],
                    "routes": [
                        {
                            "handle": [
                                {
                                    "handler": "subroute",
                                    "routes": [
                                        {
                                            "handle": [
                                                {
                                                    "handler": "vars",
                                                    "root": "/nix/store/496k1zx0li2mp94xnydn2smk1gbybw2n-testdir"
                                                },
                                                {
                                                    "encodings": {
                                                        "gzip": {}
                                                    },
                                                    "handler": "encode"
                                                },
                                                {
                                                    "handler": "file_server",
                                                    "hide": [
                                                        "/nix/store/69yh559dagwrhfa8bahpm9v99sd2qkg8-Caddyfile"
                                                    ]
                                                }
                                            ]
                                        }
                                    ]
                                }
                            ],
                            "match": [
                                {
                                    "host": [
                                        "localhost"
                                    ]
                                }
                            ],
                            "terminal": true
                        }
                    ]
                }
            }
        },
        "tls": {
            "automation": {
                "policies": [
                    {
                        "issuer": {
                            "ca": "https://acme-v02.api.letsencrypt.org/directory",
                            "email": "",
                            "module": "acme"
                        }
                    }
                ]
            }
        }
    }
}

Neither /nix/store/496k1zx0li2mp94xnydn2smk1gbybw2n-testdir nor /nix/store/69yh559dagwrhfa8bahpm9v99sd2qkg8-Caddyfile actually exist on a virtual machine.

The tests should now pass, thanks for the help!

@ofborg test caddy

I don't think this is a regression caused by this PR, but for some reason, it's emitting a StartLimitIntervalSec in the wrong section (should be under [Unit] as of some time in 2017 according to the mailing list).
Here's the generated service file:
[Unit]
After=network-online.target
Description=Caddy web server
Wants=network-online.target

[Service]
# ... snip ...
StartLimitIntervalSec=14400
TimeoutStopSec=5s
Type=simple
User=caddy

You're right, it should be moved to the Unit section along with StartLimitBurst. I think you should file an issue, since this problem is present in other services (grepping for StartLimitIntervalSec and StartLimitBurst reveals that other modules are using these options, and that they're also in the Service section).

@sephii I should file a PR and fix all of them as it's relatively trivial. Not sure when I'll have time to do that though.

In terms of actual bugs in this PR though:
@sephii
There's a bug introduced in this PR where we are doing a bit of hamfisted overwriting of the tls key in our generated configs, breaking tls internal settings in the config section. Here's a repro:
{pkgs, ...}: {
    services.caddy.package = pkgs.caddy;
    services.caddy.enable = true;
    services.caddy.agree = true;
    services.caddy.email =<EMAIL_ADDRESS>    services.caddy.ca = "https://acme-staging-v02.api.letsencrypt.org/directory";
    services.caddy.config = ''
      test.catgirl.enterprises:443 {
        encode zstd gzip
        log
        tls internal
        reverse_proxy localhost:3000
      }
    '';
}

is making the following bad config:
{
  "apps": {
    "http": {
      "servers": {
        "srv0": {
          "listen": [
            ":443"
          ],
          "routes": [
            {
              "match": [
                {
                  "host": [
                    "carnap-staging.catgirl.enterprises"
                  ]
                }
              ],
              "handle": [
                {
                  "handler": "subroute",
                  "routes": [
                    {
                      "handle": [
                        {
                          "encodings": {
                            "gzip": {},
                            "zstd": {}
                          },
                          "handler": "encode"
                        },
                        {
                          "handler": "reverse_proxy",
                          "upstreams": [
                            {
                              "dial": "localhost:3000"
                            }
                          ]
                        }
                      ]
                    }
                  ]
                }
              ],
              "terminal": true
            }
          ],
          "logs": {}
        }
      }
    },
    "tls": {
      "automation": {
        "policies": [
          {
            "issuer": {
              "ca": "https://acme-staging-v02.api.letsencrypt.org/directory",
              "email"<EMAIL_ADDRESS>              "module": "acme"
            }
          }
        ]
      }
    }
  }
}

Compare the tls section to what caddy adapt produces for the equivalent caddyfile with the content of config:
{
  "apps": {
    "http": {
      "servers": {
        "srv0": {
          "listen": [
            ":443"
          ],
          "routes": [
            {
              "match": [
                {
                  "host": [
                    "test.catgirl.enterprises"
                  ]
                }
              ],
              "handle": [
                {
                  "handler": "subroute",
                  "routes": [
                    {
                      "handle": [
                        {
                          "encodings": {
                            "gzip": {},
                            "zstd": {}
                          },
                          "handler": "encode"
                        },
                        {
                          "handler": "reverse_proxy",
                          "upstreams": [
                            {
                              "dial": "localhost:3000"
                            }
                          ]
                        }
                      ]
                    }
                  ]
                }
              ],
              "terminal": true
            }
          ],
          "logs": {}
        }
      }
    },
    "tls": {
      "automation": {
        "policies": [
          {
            "subjects": [
              "test.catgirl.enterprises"
            ],
            "issuer": {
              "module": "internal"
            }
          }
        ]
      }
    }
  }
}

Update: it looks like it's that for some reason jq is not merging arrays while doing a * recursive merge. I don't know enough jq to fix it though, sorry. I'll instead go fix the systemd unit option issues :)

I think the following jq should do the trick: jq -s '.[0] * {"apps": {"tls": {"automation": {"policies": (if .[0].apps.tls.automation.policies == .[1]?.apps.tls.automation.policies then .[0].apps.tls.automation.policies else (.[0].apps.tls.automation.policies + .[1]?.apps.tls.automation.policies) end)}}}}'. I don't know jq either so there might be a better way to do it. Can you please try and let me know, so I can submit a patch?


Adding FYST

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: EF6Pjrjf28VKsTiYmmNosbRcH91NyQRnFoBqAaUWqqXq
Token Name: FUNKY SANTAS T
Token Symbol: FYST
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token: /
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I can help refer this zakimzf/profile#1
PS: if you don't need my help.. please ignore this!


Bulletine

Get with Mechell on the Bulletin file format and data.
Find out how she puts that together and if we can transform the data and file formats to automatically put it in the mobile app.
Call her to setup a time to go over there.

AJ and Mechelle added the bulletine to the page in the mobile app. Need to follow up with them to see if any thing needs to change.


⚠ ClamAV has degraded performance

In b2df279, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in deb98ca.


WIP: interpolate: bump nxest, nyest on a failure

Reference issue

closes gh-2167 when complete
What does this implement/fix?

The warning from FITPACK is for s=0 (interpolation) and is literally
The required storage space exceeds the available storage space: nxest  or nyest too small, or s too small.

These nxest, nyest give a maximum number of knots to insert. For the test case from gh-2167 (which is https://github.com/scipy/scipy/blob/main/scipy/interpolate/tests/test_fitpack2.py#L536), FITPACK actually runs into the nxest, nyest limit. The limit comes from the f2py wrapper, nxest = imax(kx+1+sqrt(m/2),2*(kx+1)) where m is the number of data points. This value can be traced to the comment in surfit.f, which literally says
in most practical situation nxest = kx+1+sqrt(m/2), nyest = ky+1+sqrt(m/2) will be sufficient.

So here we have a situation where it is not sufficient. Since the data does not seem special, I suspect it's typical for kx=ky=1, i.e. linear interpolation.
Therefore, in case of a failure, bump the allowed number of knots and rerun. Spot-checking the interpolator shows that (i) in main, lut.fp is non-zero (meaning, the result is not an interpolating spline) and in this PR it is, so that the interpolation conditions are satisfied.
However, the test fails down the line on the value of the integral. This needs to be figured out.
Additional information

[ ] the fix will need to be checked on other test cases from gh-2167, gh-4138 and the SO report linked in that issue.
[ ] need to implement the fix in bisplrep interface, too
[ ] need to think about the API: is it the automatic rerun or we better expose the nxest/nyest parameters to a user so that they are in control

The failing test seems to be bad. Here's why.
What the test does. It checks the value of the integral of the spline against the expected value of an integral of a bilinear function with breakpoints at the (x, y) data points. The spline constructed in the PR, with an increased values of mxest, myest, has the following knots:
In [57]: lut = SmoothBivariateSpline(x, y, z, kx=1, ky=1, s=0)

In [58]: lut.tck[0:2]
Out[58]:
(array([1.        , 1.        , 1.33390249, 4.        , 4.        ]),
 array([1., 1., 2., 3., 3.]))

Note that the internal x knot is at 1.33390249, while the data points are x = [1,1,1,2,2,2,4,4,4].  Checking the expected value of the integral of the function which is piecewise bilinear in the region defined by the knots:
In [60]: ttx
Out[60]: array([1.        , 1.33390249, 4.        ])

In [61]: tty = tck[1][1:-1]

In [62]: ttz = lut(ttx, tty)

In [63]: np.sum((ttz[:-1,:-1]+ttz[1:,:-1]+ttz[:-1,1:]+ttz[1:,1:]) * np.diff(ttx)[:, None
    ...: ] * np.diff(tty)[None, :]) * 0.25
Out[63]: 24.416737810662116

In [64]: lut.integral(1, 4, 1, 3)
Out[64]: 24.416737810662113

Concluding:

SmoothBivariateSpline(..., kx=1, ky=1, s=0).integral(...) method is internally consistent
SmoothBivariateSpline does not guarantee the location of the knots at data.

On main, the spline does not interpolate the data, because
In [18]:         x = [1,1,1,2,2,2,4,4,4]
    ...:         y = [1,2,3,1,2,3,1,2,3]
    ...:         z = np.array([0,7,8,3,4,7,1,3,4])

In [19]: lut = SmoothBivariateSpline(x, y, z, kx=1, ky=1, s=0)
/home/br/repos/scipy/scipy/build-install/lib/python3.8/site-packages/scipy/interpolate/_fitpack2.py:1304: UserWarning:
The required storage space exceeds the available storage space: nxest
or nyest too small, or s too small.
The weighted least-squares spline corresponds to the current set of
knots.
  warnings.warn(message)

In [20]:         tx = [1,2,4]
    ...:         ty = [1,2,3]

In [21]: tz = lut(tx, ty)

In [22]: np.sum((tz - z.reshape((3, 3)))**2)
Out[22]: 8.964285714285715

In [23]: lut.get_residual()
Out[23]: 8.964285714285715

The integral of this spline does agree to the expected value, the area under 2D trapezoids with boundaries at data points, but this I believe is an accident and cannot be guaranteed in general.

This PR is superseded by gh-17178, which will close this one once merged.


Make src/vxworks/mod.rs non-executable

The file should be non-executable, and having executable permissions triggers a lintian check in Debian.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon.
Please see the contribution instructions for more information.

:hourglass: Testing commit 86dd174ae045a3b8401b19d50eca4768ef44c447 with merge 90ee61b489a3456462390cfcf5fe8cb739f4ac42...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing 90ee61b489a3456462390cfcf5fe8cb739f4ac42 to master...


How to use nestjs-paginate with limiting the query fields results?

is there a way to defind /cats?fields=field1,field2 etc?  ats the movement even using some custom solution?
E.g. provide also somehow FindOneOptions options when calling
paginate(query, this.repository, config);

Doesn't currently exist for repositories. You could use QueryBuilder as a workaround.
But..
Allowing query to pass fields onto FindOptions would probably be an easy and straightforward solution.
Helper config:
paginate(query, this.usersRepository, {
    sortableColumns: ['id', 'username', 'email', 'created'],
    select: ['id', 'username', 'email', 'firstName', 'lastName', 'created']
})

Select may acts as a whitelist for the query string here as well.
Query string:
/users?select=email,created

PK might be always selected.
Happy to accept PR :)


Add Search Endpoint

This PR introduces a new structure SearchResult, and functionality to allow for search within Spotify.
The SearchResult structure contains song, album, and artist information.

Thanks for the contribution!


Use current Stellar-Core state when restarting

In the current code, CaptiveStellarCore always clears Stellar-Core state persisted to the database to catchup and start streamed from the last ledger ingested by Horizon. This can be improved if Stellar-Core ledger < Horizon ledger. In such case CaptiveStellarCore can fast-forward to the ledger it needs.
CaptiveStellarCore should also restart the process if forwarding would take too much time. The code similar to this was part of original CaptiveStellarCore but was removed to simplify experimental code. Now that we know the final API we can add it back.

This is blocked while we decide among possible options for online stellar-core.

We decided to always use in-memory version by using https://github.com/stellar/go/issues/2842.


Support for Custom GH Instances + Submodules

Formerly the GithubRepoLoader was hardcoded to support only github.com.
Especially when working with GitHub Enterprise instances, one need to target custom GitHub instances.
This PR provides the support via additional parameters baseUrl and apiUrl.
Furthermore the GithubRepoLoader formerly broke when it was used with a repository using Git submodules.
This PR also provides the support for recursively processing submodules (as long as they stay within the boundaries of the same GitHub instance).

Thank you very much for this!

@jacoblee93 Thank you for the fast reaction. Nice experience for my first PR to langchainjs 😏


Add dir_perms and file_perms to WasiConfig.preopen_dir

The rust preopened_dir method has parameters for setting permissions to allow mapping the directory or its files as read-only. The python preopen_dir doesn't currently expose these parameters, so we can only map directories as read-write.
Is it possible to add the ability to set permissions on mapped directories?

Thanks for the report! While this functionality is present in Rust it's not currently reflected in the C API which this package is built on. That doesn't mean it's not possible, just means that the sequence of steps to fix this would be to (a) update the C APi to enable plumbing these permissions bits and (b) update wasmtime-py to use the new bindings. If you're able to help that'd be much appreciated! If not however that's also ok too.

I'm also interested in this functionality. Looks like the next step is to update the version of wasmtime this package depends on, then update the preopen_dir python wrapper? @alexcrichton or @ajalt, are either of you already working on this first part, or would it be helpful for me to take it on this week?

I'm not working on this myself, and if @ajalt isn't already taking a crack at it please feel free to!
The line to update is this one and set that to "dev" to download the latest build which will have the changes necessary.

Ah the wasmtime-types crate was folded into wasmtime-environ, and for now you can probably add an explicit dependency on wasmparser but otherwise yeah adding it as an export from wasmtime-environ I think would make sense.

For posterity, I am working on this, WIP here which we can land once wasmtime 27 is released.

I just came looking for this feature myself. I want to be able to run the equivalent of this (but in Python):
wget https://github.com/brettcannon/cpython-wasi-build/releases/download/v3.13.0/python-3.13.0-wasi_sdk-24.zip
unzip python-3.13.0-wasi_sdk-24.zip
wasmtime run --dir .::/ python.wasm -c 'print("hello world")'

But I want the directory to be read-only, so that things like this don't break everything:
wasmtime run --dir .::/ python.wasm -c 'open("python.wasm", "wb").write(b"blah")'

@jder thanks for this! If you'd like feel free to go ahead and open a PR and update ci/download-wasmtime.py to using the dev tag. We can land that and then switch to the 27.0.0 release artifacts once they're available.
@simonw I believe that this issue will solve your need for that, and if you're interested in seeing such a readonly flag for Wasmtime mind opening an issue over there for that? I don't think we currently have an issue tracking that.

Thanks! Posted that feature request here:

https://github.com/bytecodealliance/wasmtime/issues/9608


[gui error report] Error: Initializing daemon...

👉 Please describe what you were doing when this error happened.
Specifications

OS: win32 10.0.19045
IPFS Desktop Version: 0.30.2
Electron Version: 19.1.9
Chrome Version: 102.0.5005.167

Error
Error: Initializing daemon...
Kubo version: 0.22.0
Repo version: 14
System version: amd64/windows
Golang version: go1.19.12
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 3 migrations, downloading.
Downloading migration: fs-repo-11-to-12...
Downloading migration: fs-repo-12-to-13...
Downloading migration: fs-repo-13-to-14...
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-13-to-14/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-12-to-13/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-12-to-13/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-13-to-14/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-13-to-14/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmYerugGRCZWA8yQMKDsd9daEVXUR3C5nuw3VXuX1mggHa/fs-repo-12-to-13/versions"

@ll369 it looks like some of the output from the kubo daemon was truncated. Can you attach the error & combined log files? you can find them at https://github.com/ipfs/ipfs-desktop#where-are-my-ipfs-configuration-and-log-files

@ll369 FYI that the repo migration downloads should work properly if given enough time. you shouldn't need to run fs-repo-migrations manually, but you can.
Before trying fs-repo-migrations manually, see if you can update your IPFS config with the following command:
ipfs config --json Migration.DownloadSources '["IPFS", "HTTP"]'
or by changing the json setting in your settings directly via the settings panel in ipfs-desktop:

Please let us know if you're continuing to experience issues.


refactor(cli): replace ethers with viem

closes https://github.com/latticexyz/mud/issues/1006

I just spent a bit trying to remove the chain requirement, because folks will often deploy with just an RPC URL, and they'll have no way to edit the supportedChains of the built CLI package.
While messing around with that, I turned on the --debug flag and discovered that we're getting tons of nonce errors + retries with the approach in this PR. It does eventually seem to deploy properly (see passing tests), but I feel like we should handle nonces better, especially for non-local chains.
I think I'm gonna move on to working on #1611 and overhaul our deployment process. So I'll leave it to you to decide if you want to figure out nonce handling here or if we wanna just wait for handling this better in the declarative deployment approach.

No worries. TBH I'm not sure how its possible to use the manual nonce setting with Viem without this approach as I couldn't find a way to avoid the nonce errors (as far as I could see createContract was essentially doing the same but was just resubmitting with latest nonce instead of the original, which I think ends up causing issues when lots of transactions are being handled). I also tried with a que type setup where it would submit one after the other but this was way slower and AFAIK speed is one of the main priorities here.