text:
Transactions don't propagate when low peer count / not 100% synced

Discovered if the node is connected with a low peer count and majority of the peers aren't 100% synced the Transactions don't propagate
Node:::ffff:100.19.40.254:50290,         connected (inbound),       agent StratisBitcoin:1.0.7,  height=5000
Node:::ffff:13.64.76.48:26178,           connected (outbound),      agent /Stratis:2.0.0.3/,  height=154000
Peer:::ffff:88.253.146.132:62256,        connected (inbound),       agent Breeze:1.0.5,   height=226432
Peer:::ffff:176.24.25.143:47818,         connected (inbound),       agent StratisBitcoin:1.0.7,  height=231432
Peer:::ffff:62.194.112.119:56404,        connected (inbound),       agent StratisBitcoin:1.0.7,  height=96172
Peer:::ffff:212.92.108.174:54167,        connected (inbound),       agent StratisBitcoin:1.0.7,  height=44173```

Possibly due to the peers being in IBD?

The propagation algorithm works like this:

select half of the peers and send them the transaction
wait other half to propagate it back. if they did or we received a block with out tx- consider it propagated.

So mist likely that the half that was selected for sending the tx to was in IBD.
Overall this bug could be solved by not including IBD peers in this algorithm.
And right now we don't have a way for knowing if peer is in IBD. But this will be fixed after part 2 of this PR series is done.

Regarding the propagation algorithm. Would this work?:

Send transaction to two random peers giving preference to high quality score peers that are not in IBD.

Repeat (with some interval) until half of the peers are propagating the transaction back.

Based on that algo that the FN is using, I'm not sure the logic/reasoning/security/benefit to having only 50% of peers getting broadcasted of a transaction? I observed how the Stratis-qt (and others) do this, and they are broadcasting to 100% of connected peers.
@fassadlr could you possibly elaborate on this?

@D3m0nKingx without the propagation to the half of the peers we son't have a way to know if tx was propagated or not until the block with this tx is mined.
So it's a trade off- if the tx wasn't propagated we at least know for sure that we can respend the coins used in that tx.
Also it is planned to add this feature in the full node UI- the user will be able to see al txes and manually remove\resend transactions that were not propagated.

@noescape00 agreeable, furthermore, if 100% of the connected peers are broadcasted to, it's more likely for a transaction to get propagated I believe than just using half of them.
In addition, from a security point of view, if we're only broadcasting to half of the connections, then an attacker could effectively bring down the network by 50% persay, which then reduces the number of usable peers by 50% as well (albeit those peers aren't dirty, etc).

At some point a Network Stress Test should be performed to give some more clear picture of this.

In addition, from a security point of view, if we're only broadcasting to half of the connections, then an attacker could effectively bring down the network by 50% persay, which then reduces the number of usable peers by 50% as well (albeit those peers aren't dirty, etc).

If 50% of the network goes down we will loose 4\8 max peers. So we will just connect to 4 more peers in a minute and the propagation chances are the same as before.

If 50% of the network goes down we will loose 4\8 max peers. So we will just connect to 4 more peers in a minute and the propagation chances are the same as before.

Assuming there's no issues with the "4 more peers" ...
Although theoretical there'd be such situation to cripple the network to that degree, without actually seeing an event as this.
Either way, putting any ratio for propagation seems more of a performance degradation imho.

@D3m0nKingx I dont think I can comment here? What algo are you referring to?

Assuming there's no issues with the "4 more peers" ...

Current peer selection algho would try connecting mostly to known before peers so we should gain those +4 just in a few minutes if this scenario happens.

@fassadlr

The propagation algorithm works like this:
select half of the peers and send them the transaction
wait other half to propagate it back. if they did or we received a block with out tx- consider it propagated.

As stated by @noescape00

Ahhhh I see! I havent really been involved in that selection algo, so cant really comment at this point :) I'll need to go and investigate first.

Either way, putting any ratio for propagation seems more of a performance degradation imho.

Agreed. But this trade off is needed for the full node UI and the breeze wallet. Removing this trade off will make us remove a  potentially useful feature from the wallets.
Though if you still think that propagating to 100% makes more sense- start a separate issue discussing the propagation algho and request a change- let's discuss this separately since it involves changing some very important logic.

@fassadlr to investigate this take a look at wallet manager : SendTransactionAsync and at light wallet and full node's broadcaster managers.

Also @Aprogiena is familiar with the propagation algorithm so you'd probably want him to comment on this as well.

I started an issue specific to for the Algo discussion, lets continue the discussion there #973

@noescape00 unfortunately not, i'm familiar with block propagation, not transaction propagation

@Aprogiena ok, then it was Dan who explained the current algho to me, I forgot (tried to check in slack but it removed all the conversations).

We can close this can't we @dangershony @fassadlr ?

authors: Aprogiena D3m0nKingx bokobza fassadlr noescape00 quantumagi

repo: stratisproject/StratisBitcoinFullNode


text:
[FS] Sidechains move

Sorry it's so big...

Shouldn't touch FN / SC code except for solution.
Adds .Sidechains.Networks project
Adds .Features.FederatedPeg project
Adds .Features.FederatedPeg.Tests project
All tests pass

Is there any way to disable the CI just for Stratis.Features.FederatedPeg.Tests? Don't want to block others while we're still making these tests stable.
Will also slowly start moving over and improving the integration tests too.
In case you're wondering why do this:

Sidechains moves faster. No package redeployment, no time lost amending code to keep up with breaking API changes between packages, easier debugging.
Hopefully helps us think about how to best build the core FN components to let others (and ourselves) build on top of them.
The long-term plan remains the same: to move smart contracts and sidechains out to their own repos when the API is a bit more locked-down

NOTE: This code is more or less identical to what was in the sidechains repo, I don't expect it to be reviewed, more just check with everyone that this is okay to do. If you do come across style issues, just note 1 of them and I'll try and fix all of the same issue in the rest of the files.

@bokobza I did as suggested, but when viewing commits here I'm getting this...

source: gharchive/pull-request

license: mit

license_type: permissive

license_source: bigquery


text:
Update README.md change versions 0.8.1

SDS

The Stratos Decentralized Storage (SDS) network is a scalable, reliable, self-balancing elastic acceleration network driven by data traffic. It accesses data efficiently and safely. The user has the full flexibility to store any data regardless of the size and type.
SDS is composed of many resource nodes (also called PP nodes) that store data, and a few meta nodes (also called indexing or SP nodes) that coordinate everything.
The current repository contains the code for resource nodes only. For more information about meta nodes, we will open source it once it's ready.
Here, we provide a concise quickstart guide to help set up and run a SDS resource node. For more details of SDS as well as the Tropos-Incentive-Testnet rewards distribution, please refer to Tropos Incentive Testnet.
Building a Resource Node From Source
git clone https://github.com/stratosnet/sds.git
cd sds
git checkout v0.8.1
make build

Then you will find the executable binary ppd under ./target
Installing the Binary
The binary can be installed to the default $GOPATH/bin folder by running:
make install

The binary should then be runnable from any folder if you have set up go env properly
Creating a SDS Resource Node
Creating a Root Directory for Your Resource Node
To start a resource node, you need to be in a directory dedicated to your resource node. Create a new directory, or go to the root directory of your existing node.
# create a new folder
mkdir rsnode
cd rsnode

Configuring Your Resource Node
Next, you need to configure your resource node. The binary will help you create a configuration file at configs/config.toml.
ppd config -w -p
# following the instructions to generate a new wallet account or recovery an existing wallet account

You will need to edit a few lines in the configs/config.toml file to configure your resource node.
First, make sure or change the SDS version section in the configs/config.toml file as the following.
[version]
app_ver = 8
min_app_ver = 8
show = 'v0.8.1'

To connect to the Stratos-chain Tropos testnet, make the following changes:
stratos_chain_url = 'https://rest-tropos.thestratos.org:443'

and then the indexing node list:
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '18.223.175.117:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '52.13.28.64:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '46.51.251.196:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '35.73.160.68:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '35.74.33.155:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '18.130.202.53:8888'
[[sp_list]]
p2p_address = ''
p2p_public_key = ''
network_address = '3.9.152.251:8888'

You also need to change the chain_id to the value visible Stratos Explorer right next to the search bar at the top of the page. Currently, it is tropos-4.
chain_id = 'tropos-4'

Finally, make sure to set the network_address to your public IP address and port.
Please note, it is not the meta node network_address in [[sp_list]] section
# if your node is behind a router, you probably need to configure port forwarding on the router
port = '18081'
network_address = 'your node external ip'

Acquiring STOS Tokens
Before you can do anything with your resource node, you will need to acquire some STOS tokens.
You can get some by using the faucet API:
  curl --header "Content-Type: application/json" --request POST --data '{"denom":"ustos","address":"put_your_wallet_address_here"} ' https://faucet-tropos.thestratos.org/credit

Just put your wallet address in the command above, and you should be good to go.
Starting Your Resource Node
Once your configuration file is set up properly, and you own tokens in your wallet account, you can start your resource node.
to start the node as a daemon in background without interactivity:
# Make sure we are inside the root directory of the resource node
cd rsnode
# start the resource node
ppd start

Starting Mining
In order to interact with the resource node, you need to open a new COMMAND-LINE TERMINAL, and enter the root directory of the same resource node.
Then, use ppd terminal command to start the interaction.
# Open a new command-line terminal
# Make sure we are inside the root directory of the resource node
cd rsnode
# Interact with resource node through a set of "ppd terminal" subcommands
ppd terminal

Registering to a Meta Node
Your resource node needs to register to a meta node before doing anything else.
In the ppd terminal command-line terminal, input one of the two following identical commands:
rp
# or
registerpeer

Activating the Resource Node by Staking
Now you need to activate your node within the blockchain.
Use this command in the ppd terminal command-line terminal:
activate stakingAmount feeAmount gasAmount

stakingAmount is the amount of uSTOS you want to stake. A basic amount would be 1000000000.
feeAmount is the amount of uSTOS to pay as a fee for the activation transaction. 10000 would work. it will use default number if not provide
gasAmount is the amount of gas to use for the transaction. 1000000 would be a safe number. it will use default number if not provide

Resource node will start to receive tasks from meta nodes and thus gain mining rewards automatically after it has been activated successfully.
What to Do With a Running Resource Node?
Here are a set of ppd terminal subcommands you can try in the ppd terminal command-line terminal.
You can find more details about these subcommands at ppd terminal subcommands
Check the current status of a resource node
status

Update stake of an active resource node
updateStake stakeDelta fee gas isIncrStake

stakeDelta is the absolute amount of difference between the original and the updated stake. It should be a positive integer, in the unit of ustos.
isIncrStake is a flag with 0 for decreasing the original stake and 1 for increasing the original stake.
When a resource node is suspended, use this command to update its state and re-start mining by increasing its stake.

Purchase Ozone
Ozone is the unit of traffic used by SDS. Operations involving network traffic require ozone to be executed.
You can purchase ozone with the following command:
prepay purchaseAmount feeAmount gasAmount

purchaseAmount is the amount of uSTOS you want to spend to purchase ozone.
The other two parameters are the same as above.

Query Ozone Balance of Resource Node's Wallet
getoz WALLET_ADDRESS

Upload a File
put FILE_PATH

FILE_PATH is the location of the file to upload, starting from your resource node folder. It is better to be an absolute path.

Upload a media file for streaming
Streaming is the continuous transmission of audio or video files(media files) from a server to a client.
In order to upload a streaming file, first you need to install a tool ffmpeg for transcoding multimedia files.
putstream FILE_PATH

List Your Uploaded Files
list
# or
ls

Download a File
get sdm://WALLET_ADDRESS/FILE_HASH SAVE_AS

Every file uploaded to SDS is attributed a unique file hash. You can view the file hash for each of your files when your list your uploaded files.
You can use an optional parameter SAVE_AS to rename the file after downloading
Delete a File
delete FILE_HASH

Share a File
sharefile FILE_HASH DURATION IS_PRIVATE

DURATION is the time period(in seconds) when the file share expires. Put 0 for unlimited time.
IS_PRIVATE is whether the file shared should be protected by a password. Put 0 for no password, and 1 for a password.
After this command has been executed successfully, SDS will provide a password to this shared file, like  SharePassword 3gxw. Please keep this password for future use.

List All Shared Files
allshare

Download a Shared File
getsharefile SHARE_LINK PASSWORD

Leave the PASSWORD blank if it's a public shared file.

Cancel File Share
cancelshare SHARE_ID

View Resource Utilization
Type monitor to show the resource utilization monitor, and stopmonitorto hide it.
# show the resource utilization monitor
monitor

# hide the resource utilization monitor
stopmonitor

You can exit the ppd terminal command-line terminal by typing exit and leave the ppd start terminal to run the resource node in background.
Contribution
Thank you for considering to help out with the source code! We welcome contributions
from anyone on the internet, and are grateful for even the smallest of fixes!
If you'd like to contribute to SDS(Stratos Decentralized Storage), please fork, fix, commit and send a pull request
for the maintainers to review and merge into the main code base.
Please make sure your contributions adhere to our coding guidelines:

Code must adhere to the official Go formatting
guidelines (i.e. uses gofmt).
Code must be documented adhering to the official Go commentary
guidelines.
Pull requests need to be based on and opened against the dev branch, PR name should follow conventional commits.
Commit messages should be prefixed with the package(s) they modify.

E.g. "pp: make trace configs optional"

License
Copyright 2021 Stratos
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

And Turkish setup content about sds
https://github.com/mmc6185/node-testnets/tree/main/stratos/stratos-sds
And validator tests
https://github.com/mmc6185/node-testnets/tree/main/stratos

repo: stratosnet/sds

license_source: github-api


text:
Updated documentation for types/Union

Description
It looks like a copy / paste error, but I think the type of latest_media should be MediaItem, not AudioVideoImage from the previous example.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR
No issue opened
Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥

authors: botberry byarmis

repo: strawberry-graphql/strawberry

license: MIT


text:
Add support for returning interfaces directly in resolvers

...

/pre-release

Pre-release
:wave:
Releasing commit [04b1bb46ee660270e142b719c49e9b481bc84759] to PyPi as pre-release! :package:

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds support for returning interfaces directly in resolvers:
@strawberry.interface
class Node:
    id: strawberry.ID

    @classmethod
    def resolve_type(cls, obj: Any, *args: Any, **kwargs: Any) -> str:
        return "Video" if obj.id == "1" else "Image"

@strawberry.type
class Video(Node):
    ...

@strawberry.type
class Image(Node):
    ...

@strawberry.type
class Query:
    @strawberry.field
    def node(self, id: strawberry.ID) -> Node:
        return Node(id=id)

schema = strawberry.Schema(query=Query, types=[Video, Image])

Here's the preview release card for twitter:

Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Works well for me, thanks!

authors: botberry iamkhav patrick91


text:
OR / AND operator hooks!

Hello, I need a hook that has a boolean value with OR / AND operator.
Like below
useOR
const [a, setA] = useState(false)
const [b, setB] = useState(false)
return { value: a || b, setA, setB }

useAND
const [a, setA] = useState(false)
const [b, setB] = useState(false)
return { value: a && b, setA, setB }

I think these are good micro utility hook for solving diverse state problem.
But I cannot name it, I wanna name it with good metaphor like useToggle.
Is anybody has a idea or know already existing solution, please let me know.
Thanks !

Can you give an example of usage of the api you want?

@childrentime
Thanks for the interest.
I have some business logics the use or state like below.
const useIsUserActive = () => {
  const { value, setA, setB } = useOR();

  // when user is in page
  setA(isUserInPage);
  // when user mouse moved in 30 seconds.
  setB(hasUserMoved);

  // isUserActive
  return value;
}

source: gharchive/issue

authors: childrentime codemilli

repo: streamich/react-use

license: Unlicense


text:
🛑 Meet Jitsi Streamlined is down

In c3147f4, Meet Jitsi Streamlined (https://jitsi.streamlined-scs.cl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Meet Jitsi Streamlined is back up in 976d64e.

repo: streamlined-scs/upptime


text:
Use LZ4 as external dependency

PR Details
This PR removes LZ4 compression algorithm from Stride repo and uses as a external package.
Related Issue
#1394
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Looks good. Have you tested if it's actually compatible or breaking on compiled assets (build game before the change, copy generated assets from output, rebuild after the change, use copied assets and run game)?

After longer testing I've found that Stride.Assets.Compiler throws error that 'Could not load file or assembly 'K4os.Compression.LZ4.Legacy' which is weird.
logs here : error.txt

@manio143 I've tested the changes on a couple of projects and I didn't notice any regression. However, our LZ4Stream implementation must stay, because as it turned out K4os version is not quite complete :/ (e.g doesn't have an implementation of the Seek method or doesn't remember current position value). Otherwise I guess is fine

Thank you for checking! Merging this PR is a great step towards removing native compilation in Stride.

~After longer testing I've found that Stride.Assets.Compiler throws error that 'Could not load file or assembly 'K4os.Compression.LZ4.Legacy' which is weird. logs here : error.txt~
I don't know why this happened, but now is working perfectly fine.

After sync'ing I've ran into this. I'm still investigating it but it looks like something to do with the nuget source "MSBuildSdkExtras CI Builds".

Well, I did these steps:

deleted all the obj and bins folders of my projects
cleared out all my nuget caches
reverted my stride repo to prior to the sync
cleaned up it's non repo files
built and ran the game
brought master back to head
rebuilt stride
built and ran the game again

I still can't seem to reproduce the error.
I suspect it's not package source but like manio143 asked about above regarding cached asset compilations. If someone else runs into this you can probably get around it by deleting your game obj and bins and rebuilding but that's just a guess.

If the assembly load error occured at game run it suggests at the time the dll wasn't copied over and rebuilding should have fixed it. I'm not sure why but I have a hunch that it's a caching issue around NuGet - not having a repro we can't pin it down, but it shouldn't occur for users once the new packages are released as they will be downloading fresh packages with an increased version, this skipping the cache.

2>EXEC : error 4.907s: [AssetCompiler] Unhandled exception. Exception: FileNotFoundException: Could not load file or assembly 'K4os.Compression.LZ4, Version=1.2.16.0, Culture=neutral, PublicKeyToken=2186fa9121ef231d'. The system cannot find the file specified.
2>   at Stride.Core.LZ4.LZ4Stream.FlushCurrentChunk()
2>   at Stride.Core.LZ4.LZ4Stream.Flush() in C:\Users\x\Documents\Repos\Stride\stride\sources\core\Stride.Core.Serialization\Serialization\LZ4\LZ4Stream.cs:line 334
2>   at Stride.Core.Storage.BundleOdbBackend.CreateBundle(String bundleUrl, IOdbBackend backend, ObjectId[] objectIds, ISet`1 disableCompressionIds, Dictionary`2 indexMap, IList`1 dependencies, Boolean useIncrementalBundle) in C:\Users\x\Documents\Repos\Stride\stride\sources\core\Stride.Core.Serialization\Storage\BundleOdbBackend.cs:line 675
2>   at Stride.Core.Storage.ObjectDatabase.CreateBundle(ObjectId[] objectIds, String bundleName, BundleOdbBackend bundleBackend, ISet`1 disableCompressionIds, Dictionary`2 indexMap, IList`1 dependencies, Boolean useIncrementalBundle) in C:\Users\x\Documents\Repos\Stride\stride\sources\core\Stride.Core.Serialization\Storage\ObjectDatabase.cs:line 112
2>   at Stride.Core.Assets.CompilerApp.BundlePacker.Build(Logger logger, PackageSession packageSession, Package rootPackage, String indexName, String outputDirectory, ISet`1 disableCompressionIds, Boolean useIncrementalBundles, List`1 bundleFiles) in C:\Users\x\Documents\Repos\Stride\stride\sources\assets\Stride.Core.Assets.CompilerApp\BundlePacker.cs:line 241
2>   at Stride.Core.Assets.CompilerApp.PackageBuilder.BuildMaster() in C:\Users\x\Documents\Repos\Stride\stride\sources\assets\Stride.Core.Assets.CompilerApp\PackageBuilder.cs:line 169
2>   at Stride.Core.Assets.CompilerApp.PackageBuilder.Build() in C:\Users\x\Documents\Repos\Stride\stride\sources\assets\Stride.Core.Assets.CompilerApp\PackageBuilder.cs:line 57
2>   at Stride.Core.Assets.CompilerApp.PackageBuilderApp.Run(String[] args) in C:\Users\x\Documents\Repos\Stride\stride\sources\assets\Stride.Core.Assets.CompilerApp\PackageBuilderApp.cs:line 304

I fixed the issue by copying: 'C:\Users\x.nuget\packages\k4os.compression.lz4\1.2.16\lib\net5.0\K4os.Compression.LZ4.dll' into 'C:\Users\x.nuget\packages\stride.core.serialization\4.1.0.1\lib\net6.0'.
Steps to reproduce:

git clone https://github.com/stride3d/stride.git
Open Stride.sln
Build Stride.GameStudio
Create template: top-down RPG
Open the .sln file from Visual Studio 2022
Debug -> Start Debugging

At this point, the build error should occur.
The main issue is the K4os.Compression.LZ4.dll isn't being packed with Stride.Core.Serialization.

I see that missing DLL is a dependency of the Legacy package being referenced - could it be there's something blocking transitive dependency inclusion? But why would the issue get fixed some of the time 🤔


text:
Question: react native "confirmSepaDebitPayment" equivalent

Hi,
We are using sepa_debit payments; after paying, the answer from stripe is:
requiresConfirmation: true,
paymentIntentStatus: 'requires_payment_method',
...

On the website, we call the confirmSepaDebitPayment to handle this situation: https://stripe.com/docs/js/payment_intents/confirm_sepa_debit_payment.
I couldn't find the equivalent function for react-native. I've tried the basic confirmPayment but I got  a payment_intent_unexpected_state error.

Hi! This is working in our example app here. It seems like maybe the payment method is not attached properly. Can you share some sample code to reproduce this?

Hi. The problem was analyzed further on your Slack channel. Basically, it's not possible to confirm the sepa payment on react native without using the PaymentSheet. The confirmSepaDebitPayment used on the website was indicated as "deprecated" (not in documentation, but by someone on slack) and not implemented in the react-native library.

Ah i see, well you could attach the payment method to the customer, then use confirmPayment with just the client secret, and it will automatically use the customer's default payment method (as of v0.18.0, see changelog- https://github.com/stripe/stripe-react-native/blob/master/CHANGELOG.md#0180---2022-08-17)

authors: angelica-snowit charliecruzan-stripe

repo: stripe/stripe-react-native


text:
[Android] Payment sheet have infinite loading when call presentPaymentSheet function

Describe the bug
Android bottom sheet have infinite loading when call presentPaymentSheet function
To Reproduce
Steps to reproduce the behavior:

Fetch payment params from server
Init payment sheet with initPaymentSheet function
call presentPaymentSheet function
See error

Expected behavior
Payment sheet should have finite loading and present the card form
Screenshots

Desktop (please complete the following information):

OS: MacOs Catalina
Version 10.15.7

Smartphone (please complete the following information):

Device: Simulator (Pixel 3 XL)
OS: Android
Version API 27

Additional context

@KalumDog can you please provide your code? And does your cord work on iOS?

@thorsten-stripe
I follow instruction from this https://stripe.com/docs/payments/accept-a-payment?platform=react-native&lang=node&ui=payment-sheet
Btw, It works on iOS

@KalumDog we'll need some more information to dig into this. Are you using Stripe Connect? If so, maybe it's the same as https://github.com/stripe/stripe-react-native/issues/267 ?
If not, please provide your server-side and client-side code.

Server Side
`
let customer = await this.customerRepository.findOne({
userId: user.id,
})
if (!customer.stripeCustomerId) {
const { id } = await this.stripeClient.customers.create()
customer.setStripeCustomerId(id)
customer = await this.customerRepository.save(customer)
}
const ephemeralKey = await this.stripeClient.ephemeralKeys.create(
  { customer: customer.stripeCustomerId },
  { apiVersion: '2020-08-27' },
)

const paymentIntent = await this.stripeClient.paymentIntents.create(
  {
    amount: totalAmount * 100,
    currency: 'eur',
    customer: customer.stripeCustomerId,
    metadata: {
      bookingId: booking.id,
    },
  },
)

return {
  paymentIntent: paymentIntent.client_secret,
  ephemeralKey: ephemeralKey.secret,
  customer: customer.stripeCustomerId,
  bookingId: booking.id,
}`

Client Side
`
const initPayment = async (
params,
merchantDisplayName?: string
) => {
try {
setIsLoading(true)
const resp = await checkoutApi(params)
  if (resp) {
    setpaymentParams(resp)
    const { error } = await initPaymentSheet({
      customerId: resp.customer,
      customerEphemeralKeySecret: resp.ephemeralKey,
      paymentIntentClientSecret: resp.paymentIntent,
      merchantDisplayName,
      customFlow: false,
    })

  }
} catch (error) {
  console.log(`_fetchMyOrder error`, error.response)
} finally {
  setIsLoading(false)
}

}
const fillCardAndPay = async (onSuccess: () => void, onError: () => void) => {
try {
const { error } = await presentPaymentSheet({
clientSecret: Config.STRIPE_SECRET_API_KEY,
})
  if (error) {
    onError()
  } else {
    onSuccess()
  }
} catch (error) {}

}`
PS. try to add stipe account id on both server-side and client-side not working as well

I think the issue is with
const { error } = await presentPaymentSheet({
clientSecret: Config.STRIPE_SECRET_API_KEY,
})

Here clientSecret needs to be the PaymentIntent's client secret, in your case resp.paymentIntent.
But I now realise that our parameter naming is not consistent across these methods, and the docs also don't help in making this clear. Thank you for flagging and providing your code!

@thorsten-stripe
Thanks for your help.

authors: KalumDog thorsten-stripe


text:
Load history from JHist files, not the history server

Timberlake currently eagerly loads data for past jobs from the history
server, the load from which can cause it to be sad sometimes. This bypasses
the historyserver to load job details, prefering to load them directly from
the .jhist files in HDFS.
It also contains a bunch of opportunistic cleanup and restructuring.

There's too many lines of code here to give a review past LGTM. However, it's an enthusiastic LGTM since I'm excited about these changes and the opportunistic cleanup. Thanks a bunch!

authors: colinmarc jbalogh

repo: stripe/timberlake


text:
Issue 1176: Implement a PypiWheelDependencyFormatter

Implemented PypiWheelDependencyFormatter.java

Implemented PypiWheelDependencyFormatterTest.java

Fixes #1176

Thanks, David!
I will merge this to our pypi-layout-provider branch, while we're still actively developing the PyPi layout support.

authors: carlspring whalenda

repo: strongbox/strongbox


text:
Upgrade maven-assembly plugin from 3.1.1 to 3.3.0

Pull Request Description
This pull request closes #1877
Acceptance Test

[ ] Building the code with mvn clean install -Dintegration.tests still works.
[ ] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[ ] No

Does this pull request require other pull requests to be merged first?

[ ] Yes, please see strongbox/strongbox-parent#81
[ ] No

Does this require an update of the documentation?

[ ] Yes, please see strongbox/strongbox-docs#{PR_NUMBER}
[ ] No

Update: This is now being build in Jenkins with our complete build pipeline here.

Hi @hirva10  ,
Thank you, the tests have passed and I will be closing this pull request as it proves it works!


text:
Docs say apiVersion is optional, but it is required  to connect

When you leave out the api-version, you get a type-error
TypeError: Cannot create data source "elasticsearch": Cannot initialize connector "es": Cannot read property 'indexOf' of undefined
at ESConnector.connect (/diekeure/platformso/API/node_modules/loopback-connector-es/lib/esConnector.js:105:37)
at Object.module.exports.initialize (/diekeure/platformso/API/node_modules/loopback-connector-es/lib/esConnector.js:30:30)
at DataSource.setup (/diekeure/platformso/API/node_modules/loopback-datasource-juggler/lib/datasource.js:339:19)
at new DataSource (/diekeure/platformso/API/node_modules/loopback-datasource-juggler/lib/datasource.js:117:8)
at Registry.createDataSource (/diekeure/platformso/API/node_modules/loopback/lib/registry.js:355:12)
at dataSourcesFromConfig (/diekeure/platformso/API/node_modules/loopback/lib/application.js:440:19)
at EventEmitter.app.dataSource (/diekeure/platformso/API/node_modules/loopback/lib/application.js:235:14)
at /diekeure/platformso/API/node_modules/loopback-boot/lib/executor.js:190:9
at /diekeure/platformso/API/node_modules/loopback-boot/lib/executor.js:281:5
at Array.forEach (native)
at forEachKeyedObject (/diekeure/platformso/API/node_modules/loopback-boot/lib/executor.js:280:20)
at setupDataSources (/diekeure/platformso/API/node_modules/loopback-boot/lib/executor.js:180:3)
at execute (/diekeure/platformso/API/node_modules/loopback-boot/lib/executor.js:38:3)
at bootLoopBackApp (/diekeure/platformso/API/node_modules/loopback-boot/index.js:154:3)
at Object. (/diekeure/platformso/API/server/server.js:28:1)
at Module._compile (module.js:556:32)

Tested with version 1.0.7

Yes correct, we added some code to decide how to operate for v1 vs v2 and that looks at the apiVersion, will think about it more and either fix the docs or the code.

Overtime the default_api_branch": "2.3" and apiVersion will continue to be a moving target.
Since we don't have quick access to that property in the code when we need to make decisions based on version, for example: if (self.settings.apiVersion.indexOf('2') === 0) { ... lets just make apiVersion required in the docs.

v1.0.8 has been released with a documentation update. Thank you for reporting the problem @diekeure

authors: diekeure pulkitsinghal


text:
.pik ピックアップファイル　エンコード（Shift_JIS）の場合でも正常に読み込めるようにする

エンコード は UTF-8 を前提にしているが、レガシーアプリから生成される .pik ファイルが Shift_JIS のため
可能ならば両方読めるようにする
不可能ならば
.pik は、 Shift_JIS とする

Shift_JISのpikファイルとUFT-8のpikファイルがあるので、どちらも読めるように修正をお願いします。
現在は、UFT-8で読み込むようにしています。
サンプルデータ
・Shift＿JIS
▲サンプル(函体)インド.zip
・UFT-8
サンプルファイル作成用UFT-8.zip

authors: sasaco yuluji

repo: structuralengine/WebDanforJS


text:
Support Cylinder and Pipe component shapes in C4PlantUMLExporter

Overview
This change updates the C4-PlantUML exporter to use C4-PlantUML's ComponentDb and ComponentQueue for Structurizr's Cylinder and Pipe shapes respectively (#59).  The exporter already does this for containers, this change simply replicates that for components too.
Testing
I've added appropriate test for the new logic. I'm not entirely sure that the tests use best-practices (I'm no Java developer), but as much as possible I've tried to follow the patterns and conventions of the existing tests 😇
I also added a test for the existing container shapes support. The Cylinder support was being testing implicitly (by the "Big Bank plc" example), but the Pipe support was not being testing at all.
PUML Diff
Here's a simple diff showing the change in generated PUML:
--- before.puml 2023-06-03 11:42:29.657670020 +1000
+++ after.puml  2023-06-03 11:42:11.969731326 +1000
@@ -10,8 +10,8 @@

 Container_Boundary("SoftwareSystem.Container_boundary", "Container", $tags="") {
   Component(SoftwareSystem.Container.DefaultComponent, "Default Component", "", $tags="")
-  Component(SoftwareSystem.Container.CylinderComponent, "Cylinder Component", "", $tags="")
-  Component(SoftwareSystem.Container.PipeComponent, "Pipe Component", "", $tags="")
+  ComponentDb(SoftwareSystem.Container.CylinderComponent, "Cylinder Component", "", $tags="")
+  ComponentQueue(SoftwareSystem.Container.PipeComponent, "Pipe Component", "", $tags="")
   Component(SoftwareSystem.Container.RobotComponent, "Robot Component", "", $tags="")
 }

Renders
Here's how the embedded test example renders before and after the change.
Before:

After:

Cheers.

Thanks!

authors: pcolby simonbrowndotje

repo: structurizr/export


text:
raise error in read result if there is no .strFEM

note:
Quantities can be read without running the analysis ( .strFEM file )
research:
what about Finite Elements?
It seems possible to display them but there is no output if the analysis is not runned

Check if .strFEM is generated when analysis is runned with Pipe

@andosca
Looks like that .strFEM file is generated when the user run an analysis AND save the file.
Raising an error in ReadResult can be done only if we save the file after running the analysis (cmdsave).
I would suggest to do not implement the feature as it means to write the results on disk. Writing on disk can be slow and we can avoid it. I think at Big Model where FEM-Design needs to write down hundreds of MB.
What do you think?
I am happy either way.

I would suspect that the main idea was that when reading models from file (.str) using:

It is useful information for the user that the (.strFEM) is missing and no results could be extracted. I think we could at least add error handling to this component.
For pipe components maybe we could forward any log message if there is a "no result found" type of message This could be a separate case.

👌
Let's do it in this way than.

authors: Marco-Pellegrino andosca

repo: strusoft/femdesign-api


text:
Meta line issue in 962-gørrel.txt

Page 962-gørrel.txt has combination of previous meta line issues. It won't drop singular "4", as there is expected amount of meta parts. This is due to two words appearing as combination word, as OCR read them together.
There is handling for separating those lines, but it is guarded by clause of having too few parts. Should be adjusted so it drops this extra "4"

& this is a page-split page, so test case should be written accordingly


text:
WIP Enforce foreign key contraints

Who is this PR for?
Add foreign key constraints for all models
What problem does this PR fix?
Issues around data integrity with DiscontinuedServices being connected to deleted ServiceUploads
What does this PR do?
Add the immigrant gem and add the migration it creates that will add foreign keys
Screenshot (if adding a client-side feature)
Checklist

[x] Tested latest version in an Internet Explorer virtual machine? (If the PR adds Javascript.)

Questions/Concerns

[x] it appears I've committed a different version of bundle, should I reverse that?
[x] Immigrant recommends adding a rake task to our CI to ensure we continue adding keys (rake immigrant:check_keys). Is that something we want to do?

I've downloaded VirtualBox and the two Windows images and if I am correct, it is currently installing on my machine. If however it is not, can someone help me kick off the installation process or point me to some good installation instructions? Google is not being helpful.

Hey @gabivoicu!
Bundler

Well, you're on 1.16.0 and the rest of us are on 1.15.4. Since you're using the most recent version I support you checking in your version and having the rest of us catch up to you! 👍

Rake task

I say yes! Adding foreign keys is easy to forget so this seems like helpful CI to me.

VirtualBox

Happy to schedule some time next week to meet with you on this! That said since this PR doesn't touch the UI at all I don't think this should be a blocker.

QA

Using a demo data setup, did running the add_keys.rb migration affect the demo data at all? Are all the foreign key relationships working nicely in the app after running the migration?

@alexsoble
Bundler

sounds good, I will leave it as it is now

Rake task

great, I will add that task

VirtualBox

I'll email you to schedule a time. Yup, it's not needed for this PR, I wanted to make sure I have it set up for the future.

QA

when you say using a demo data setup are you referring to the local dev setup? I ran the migration locally and from what I can tell, everything looks fine, but I am thinking it would be good for someone with more domain knowledge to test it as well.

@gabivoicu — FYI, I want to finish up #1251 (investigating and closing the lid on the mystery of some missing Service IDs) before we merge this and deploy it. I'm using the current database state to investigate and I want to avoid changing the state of the database until the investigation is over.

@alexsoble Sounds good, I'll leave this as WIP until then, just let me know, thanks!

@gabivoicu Cool! #1251 is all verified, so that's a step forward. I read through immigrant's README this morning and saw this in the Considerations section:
If the data in your tables is bad, then the migration will fail to run (obviously).
IOW, ensure you don't have orphaned records before you try to add foreign keys.

We currently have some known orphan records in the discontinued services table. #1267 will remove those orphans and put us in a better state when it comes to that particular table.
But there could be orphan records in other tables of course. I wonder if there's a good way for us to scan all our tables for orphan records before we merge this in and try to run the migration?

@gabivoicu — We could run a "scan for orphaned records" rake task first that iterates over each pair of tables in the immigrant rake task and checks through them to see if there are any orphans:
["courses", "schools"]
["educators", "schools"]
["event_note_attachments", "event_notes"]
["event_note_revisions", "event_notes"]
["event_notes", "educators"]
["event_notes", "event_note_types"]
["event_notes", "students"]
["homerooms", "educators"]
["homerooms", "schools"]
["iep_documents", "students"]
["interventions", "educators"]
["interventions", "intervention_types"]
["interventions", "students"]
["sections", "courses"]
["service_uploads", "educators", column: "uploaded_by_educator_id"]
["services", "educators", column: "recorded_by_educator_id"]
["services", "service_types"]
["services", "service_uploads"]
["services", "students"]
["student_assessments", "assessments"]
["student_assessments", "students"]
["student_risk_levels", "students"]
["students", "homerooms"]
["students", "schools"]

@gabivoicu Can you rebase this on top of master? Just merged and deployed #1267 so the immigrant-generated migration will look a little different now.

Hey @gabivoicu, let me know what your timeline and availability looks like for finishing up this thread of work. The two immediate tasks on our plate here are rebasing and writing a task for scanning for orphan records. If you have less availability this week I'll jump on the scanning task, if you have more I'll let you tackle both. I'd like to have the scan done before the Thanksgiving holiday. If that doesn't turn up any orphan records then we can merge and enforce referential integrity!

Hey @alexsoble. I am going to work on this tonight, not sure if I will be able to get both done- depends on how much work the rake task is. Once I have an idea of how much work the rake task is, I will update you.
If I can't get to it tonight, then I'll let you do it, because after tonight I won't have availability until Friday/Saturday.

Just got off a video call with @gabivoicu! We went over the rake task and a few other topics! Since we're getting awfully close to the Thanksgiving holiday we'll plan on finishing up this thread of work next week. 👍

Readout from Friday meeting discussion: we determined via #1275 that this should should be good to merge. @gabivoicu is going to do a little more QA to double-confirm. Planning to merge/deploy on Tuesday Dec 5. later in the afternoon/evening when no educators are likely to be using it.

@alexsoble Coming back to report that it has been impossible for me to test this feature as we discussed.
First, I ran bundle exec rake immigrant:check_keys on a "clean" database: on this branch, with the migration ran and the only foreign keys missing being nil. That succeeds quietly:
Gabrielas-MacBook-Pro:studentinsights gabrielavoicu$ bundle exec rake immigrant:check_keys
Gabrielas-MacBook-Pro:studentinsights gabrielavoicu$

Then, I tried deleting a School or Educator ID. And that fails because we now have foreign key constraints.
2.3.0 :001 > School.find(9).delete
  School Load (0.6ms)  SELECT  "schools".* FROM "schools" WHERE "schools"."id" = $1 LIMIT $2  [["id", 9], ["LIMIT", 1]]
  SQL (2.3ms)  DELETE FROM "schools" WHERE "schools"."id" = $1  [["id", 9]]
ActiveRecord::InvalidForeignKey: PG::ForeignKeyViolation: ERROR:  update or delete on table "schools" violates foreign key constraint "courses_school_id_fk" on table "courses"
DETAIL:  Key (id)=(9) is still referenced from table "courses".
: DELETE FROM "schools" WHERE "schools"."id" = $1
	from (irb):1
2.3.0 :002 >

I then tried some complicated moving between branches, to try to delete an object from a branch where that foreign key migration doesn't exist (after resetting the db, of course), but that refused to work also because running bundle exec rake immigrant:check_keys suggests I create a migration to add foreign keys and I try running that migration, that blows up because School 9 is missing.
Takeaways:

to test this, we should run the migration and the bundle exec rake immigrant:check_keys on a copy of production data. If we have any missing foreign keys that are not nil, the migration will fail.
🚨we need to be aware that we cannot simply .delete or .destroy on objects of rows that have foreign key connections anymore. This seems like a big issue that might have bigger implications than I had originally anticipated.

What are your thoughts?

@gabivoicu I think those results are good and what I would have expected!
The overall goal of this PR is to make it harder for developers to create orphan records.
The error warning you got once foreign keys were enforced by the database is saying exactly that:
ActiveRecord::InvalidForeignKey: PG::ForeignKeyViolation: ERROR:  update or delete on table "schools" violates foreign key constraint "courses_school_id_fk" on table "courses"
DETAIL:  Key (id)=(9) is still referenced from table "courses".

Overall what I read from your comment is that it's impossible to find out how immigrant "handles" orphan records, because (A) it won't run if orphan records exist, and (B) it won't allow new orphan records to get created once it's set up.
That sounds really really 👍  to me! And thanks to your earlier scanning we know we don't have any orphan records in our database! So I think we're in good shape to merge and deploy according to plan on Tuesday afternoon.

@alexsoble Yup, pretty much impossible to test that scenario.
Glad to hear this is good, and we can go ahead with the deploy! 👍

@gabivoicu Woohoo! Merge and deploy time! It's after 5PM East Coast time, which should be a good low-traffic time to make a database change.
We've done lots of local testing and production scanning. I did some triple checking locally as well just now. But we've never run this against production data, so I took a database backup before we deploy.
Plan:

If we merge and all is good, we're great and we're defended against orphan records in the future!
If we merge and we're not able to run the migration successfully, I'll revert the PR, and then we can improve/fix the PR.
If we merge and deploy and the db is in a bad state, I'll restore the backup and then revert.

🚢 🚢

@gabivoicu Deploy and migration went smoothly, app's in a good state. Let's be sure to use appear.in for this week's team meeting so we can use those party hat stickers!! 🎉

@alexsoble 🎉🎉🎉 yay, so awesome. definitely need to party on Friday :D

authors: alexsoble gabivoicu

repo: studentinsights/studentinsights


text:
Fix bug in internal tools routing in JS

Refactoring bug, fixed and added tests.

selfie


text:
[Feature] Add a ScrollReveal atom

Changelog
Added

Add a ScrollReveal atom
Add a ScrollRevealRepeat atom

To-do

[ ] Update doc with JS API
[ ] Should the ScrollRevealRepeat component be transformed into an option of the ScrollReveal one?

Leaning towards an option instead of a separate component for the repeat behavior

authors: perruche titouanmathis

repo: studiometa/ui


text:
20180306 Go Experience Report: Generics for Functional Patterns

标题：Go Experience Report: Generics for Functional Patterns
原文链接：https://medium.com/go-in-5-minutes/go-experience-report-generics-for-functional-patterns-eb6ce737bc1
译者自己根据原文翻译，译文保存为 markdown 格式，并附上尾部的签名。
----------------

via: https://medium.com/go-in-5-minutes/go-experience-report-generics-for-functional-patterns-eb6ce737bc1

作者：[Aaron Schlesinger](https://medium.com/@arschles)
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)

本文由 [GCTT](https://github.com/studygolang/GCTT) 原创编译，[Go 中文网](https://studygolang.com/) 荣誉推出

认领

repo: studygolang/GCTT


text:
AS A payroll manager I WANT AN employee payroll tracker SO THAT I can see my employees' payroll data and properly budget for the company

Acceptance Criteria
GIVEN an employee payroll tracker
WHEN I click the "Add employee" button
THEN I am presented with a series of prompts asking for first name, last name, and salary
WHEN I finish adding an employee
THEN I am prompted to continue or cancel
WHEN I choose to continue
THEN I am prompted to add a new employee
WHEN I choose to cancel
THEN my employee data is displayed on the page sorted alphabetically by last name, and the console shows computed and aggregated data

This is complete.


text:
🛑 Main Website is down

In 99d77af, Main Website (https://xoro-hosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Status is back up in 5b1ff12 after 7 minutes.

repo: stxrlite/xoro-updates


text:
Specific attrs cannot be merged inside component that is wrapped with styled()

Environment

System:

OS: macOS High Sierra 10.13.5
CPU: x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 135.84 MB / 16.00 GB
Shell: 5.3 - /bin/zsh

Binaries:

Node: 10.6.0 - /usr/local/bin/node
Yarn: 1.7.0 - /usr/local/bin/yarn
npm: 6.1.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

npmPackages:

styled-components: ^3.3.0 => 3.3.3

Reproduction
https://codesandbox.io/s/885yo82z19
Steps to reproduce
Please see the codesandbox. Note that this is a highly contrived example - the inline styles in a real project are ones that change frequently, hence the reason for putting them in the style attribute in the first place (as per #134).
Essentially:

set up a component which uses a styled-component that defines a style key as one of its attrs
set up another component which wraps this first component with styled and attempts to set different inline styles

Expected Behavior

The ...props.style spread inside the Paragraph component should merge the styles from the BlueText component

Actual Behavior

Inline styles are not merged.

I believe this is related to #1343, however in that example extend is used directly on the styled-component, in this example we are wrapping the styled-component in a regular component, and using the styled() wrapper instead.

<Paragraph style={this.props.style}> overwrites the style from attrs
const Paragraph = styled.p.attrs({
  style: props => ({
    ...props.styleParent,
    fontSize: `${props.fontScale}em`
  })
})``;
<Paragraph styleParent={this.props.style}>

Doing it like this will make it work as expected.

@wzchua correct. I'm making a change to handle the "style" prop though specifically since that's likely a common use case.

@probablyup thanks for implementing this!

authors: fiznool probablyup wzchua

repo: styled-components/styled-components


text:
not found props accent-color

not found props accent-color

Hey @njavilas2015,
I think that issue, is not related to styled-components but to vscode-styled-components.
We already have that issue tracked there: https://github.com/styled-components/vscode-styled-components/issues/335 - however, we can't resolve it directly because it is due to yet another library (more details are provided in the issue).


text:
babel-plugin-flow-react-proptypes still cause React 15.5 PropTypes deprecated warning

babel-plugin-flow-react-proptypes still cause React 15.5 PropTypes deprecated warning.
import type { Interpolation } from '../types'
transpiled to
var babelPluginFlowReactPropTypes_proptype_Interpolation = require('../types').babelPluginFlowReactPropTypes_proptype_Interpolation || require('react').PropTypes.any;

I'm also still encountering prop-types warnings after adding styled-components. The babel-plugin-flow-react-proptypes package has fixed their prop-types usage in the 1.0.0 release:
https://github.com/brigand/babel-plugin-flow-react-proptypes/commit/192e12895759917898179ad7520157021d5e91fe

Submitted a pr. Not sure whether this'll break things, but this way we can get the process started.

Just upgrade to styled-components v1.4.5
But, the devtools console still gives me warning

For me 1.4.5 fixes the devtools console warning, but still logs warnings when running my jest tests on the command line:

PR #683 fixes those warnings.

hey @mxstbr @geelen,
this is still an issue
I just tried to do a fresh install of create-react-app
then install and import styled-components (v1.4.5) in App.js
the devtools console still logs the proptypes warning
the terminal also still logs the warning everytime I run a test

It's been fixed:
v1: https://github.com/styled-components/styled-components/commit/769be58e8558dd8d1bbbf3e4c5d3d93e802ebff0
v2: https://github.com/styled-components/styled-components/commit/9e7ce0e9881a144466a8cac85c5447973e81fe17
Just needs to be released on npm


text:
fixed withTheme

Updated withTheme to take default props from WrappedComponent. Fixes issues when ThemeProvider is not used but theme is defined in defaultProps.

Can we add a test case to this scenario? @theboyWhoCriedWoolf

Tests added, I also changed the determineTheme method to prevent it from throwing an error and stay consistent with previous functionality of just throwing a warning if no theme is there.
Happy to make further changes if required.
Thanks

Thank you so much for helping us improve styled-components! Based on our Community Guidelines every person that has a PR of any kind merged is offered an invitation to the styled-components organization—that is you right now!
Should you accept, you'll get write access to the main repository. (and a fancy styled-components logo on your GitHub profile!) You'll be able to label and close issues, merge pull requests, create new branches, etc. We want you to help us out with those things, so don't be scared to do them! Make sure to read our contribution and community guidelines, which explains all of this in more detail. Of course, if you have any questions just let me know!

authors: imbhargav5 mxstbr theboyWhoCriedWoolf


text:
Portuguese Brazil locale has wrong phone number

The pt-BR locale returns (XX) XXXXX-XXXX for Faker::PhoneNumber.phone_number when it should return (XX) XXXX-XXXX and it returns XXX.XXX.XXXX for Faker::PhoneNumber.phone_number when it should return (XX) 9XXXX-XXXX.

PR merged successfully. Thanks for contributing 💯

authors: lucasqueiroz vbrazo

repo: stympy/faker


text:
Feat: Add Getting Started Page

Describe the feature
The "Getting Started" page for Blox AI serves as an introductory guide designed to help new users quickly familiarize themselves with the platform. Blox AI is a powerful tool for crafting flowcharts and diagrams effortlessly. It enables users to seamlessly create visuals and rich documentation, collaborate with their teams, and enjoy secure sharing.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@subhadeeproy3902 Can i work on this issue

we can add information about Introduction to Blox AI, Creating Your First Diagram, Collaborative Features, Secure Sharing etc

usure go ahead @Asymtode712

@subhadeeproy3902 Assign me this task i can work on this


text:
🛑 Cubari (NHentai) is down

In ee05b26, Cubari (NHentai) (https://cubari.moe/read/nhentai/381867/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 8066 ms

Resolved: Cubari (NHentai) is back up in 7c69bdf after 34 minutes.

repo: subject-f/cubari-status-page


text:
Remove our stringset implementation

We can use k8s.io generic sets instead for unsynchronized use cases. Synchronized uses typically benefit from locks covering the full operation involving sets, rather than locks covering individual set operations, so k8s.io generic sets can also be used there with additional locking.
Depends on https://github.com/submariner-io/cloud-prepare/pull/627
Depends on https://github.com/submariner-io/submariner/pull/2324
Depends on https://github.com/submariner-io/subctl/pull/587

Thanks @tpantelis, can you open another PR with your synchronized set wrapper? That way we can change the users of synchronized sets to use that where appropriate, and then once that’s done delete stringset.

Or we can do something like https://github.com/submariner-io/lighthouse/pull/1124.

repo: submariner-io/admiral


text:
Lodash version

Hello!
We are using subschema in a project. The version of lodash library is ˆ3.0.1. Is there a reason to use this version of that library? The last version is 4.15.0. npm are showing us several problems of UNMET PEER DEPENDENCY.
I was preparing a pull request to update it but I saw that related projects like subschema-expressions have that dependency too. So before start to fork several project, I prefer to ask you.
Thanks!

Have no real reason for not going to lodash 4, except it was a bunch of work.   Be more than happy to merge PRs.   subschema-expression, subschema-injection, subschema-demo, subschema-test-support, subschema-project will need to be updated.   You can get them all from a recursive checkout of subschema-devel.

Thanks you @jspears for your response. Yes, I'm going to check lodash 4 changelog because it includes a lot breaking changes.

authors: Angelmmiguel jspears

repo: subschema/subschema


text:
Update & fix some stations

Add: 2f30, anon, rfb
Fix: kexp, gd, phish

Thanks!

authors: clehner damassi

repo: substack/tuner


text:
QuickFix: Allow empty fn-group

Currently this errors.

Related: Create converter that ensures one (empty) footnote group is always present.

Done by @Integral !

repo: substance/texture


text:
[Win] Testing installation on machines with minimal resources

RAM - 2GB (1.74 available), 2 cores. Installation successful (1GB on VM), but host machine works very slow, unacceptable.

Tested with RAM usage of 1024 - 1GB:

Cannot create environments , fail results all the time :

ERROR. Building containers. java.lang.NullPointerException
ERROR. Wrong peer state: ERROR
ERROR. Building containers. java.lang.NullPointerExceptio

Also cannot ez-ssh to the existing environments with Healthy statuses :
ssh_exchange_identification: read: Connection reset by peer
Getting this ^^ error all the time.

And exactly the same picture with RAM usage of 1536.

1 core + 2048GB RAM works, with one apache env

authors: akylbekesenaliev btemir

repo: subutai-io/installers


text:
Track and Playlist Embedded Player

We need an HTML player for

Twitter player cards (See https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/player-card.html)
Artist embedding on their websites

Bandcamp probably implements this best currently:
https://daily.bandcamp.com/2013/06/12/all-new-players-up-twitter-too/
I'd be happy with just having a single track player and a playlist player to start. The question is if we should use an off the shelf solution or write something from scratch.

Closing this for now, going to sleep on it.

repo: sudara/alonetone


text:
Add messageburst and messagelimit configuration

This PR

introduces messagelimit and messageburst as config parameters
fixes shellcheck  issues in the entrypoint
sorts the config values in the README

Sadly the messageburst and messagelimit are not well documented in mumble. it wasn't even mentioned in the 1.3.0 release. So a link to the corresponding PR was added.

Thank you for your suggestions. I'm happy to do what I can.

* Separate out the configuration property sorting into its own commit

done ✅

* Separate out each shellcheck violation, grouped by the notice number, into its own commit

done ✅

* Add some validation around `messagelimit` and `messageburst` to ensure the values are always >= 1

I'm conflicted on this. I understand your concern. But there is currently no parameter validation in the entrypoint. This is solely left to mumble itself to confirm them. Which is a very sensible approach, as the validation logic doesn't have to be implemented twice. In fact mumble already takes care of validating negative values and corrects them:
messageburst: murmur/Server.cpp#L493
messagelimit: murmur/Server.cpp#L489

repo: sudoforge/docker-images


text:
Friendship between two models

Hi,
Is it possible to create friendship between two models, I am not sure if its right but the idea is more like this:
User1 with Manager role will add a POST1
User2 with Coworker role can send a request to join POST1 to be a Team member of POST1.
User1 can send request to let user2 be part of Teams
User1/User2 can approve or reject if they got request.
If anyone removes the relation so it's removed from both.
Any idea or way to do that.
Thanks

This is currently out of scope for this gem. The main purpose is to add a polymorphic join between records of one data type.
I will be attempting to clean up the current code to support the basic associations that should exist. However, that can be fairly easily accomplished by a polymorphic group. 😄


text:
杂乱需求

表达式new datetime()

Mapper Cachekey

获取列的精度

MYSQL特殊类型转INT

repo: sunkaixuan/SqlSugar


text:
There's a problem.

After connecting my laptop to an external monitor, I can access the client but cannot enter the game. It gets stuck in the process of entering the game, but the mouse cursor changes to the in-game style. The surrounding area is black. However, when I remove that file, it runs normally. What should I do

This version is no longer available for nvidia driver 555.85 version

thanks

此版本不再适用于 nvidia 驱动程序 555.85 版本

thanks

repo: sunmanbitch/SunSkin


text:
linux-aarch64 build for gemma

Describe your pull request here

Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions

If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:
build:
  run_exports:
    - ...

with ... being one of:

Case
run_exports statement

semantic versioning
{{ pin_subpackage("myrecipe", max_pin="x") }}

semantic versioning (0.x.x)
{{ pin_subpackage("myrecipe", max_pin="x.x") }}

known breakage in minor versions
{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)

known breakage in patch versions
{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)

calendar versioning
{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.
Bot commands for PR management

Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update
Merge the master branch into a PR.

@BiocondaBot please add label
Add the please review & merge label.

@BiocondaBot please fetch artifacts
Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.
Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.


text:
Fix SunSpecClientBlockBase.setitem() parameter name mismatch

Also updated a few similar Comments.  If they don't get deleted they
ought to be maintained.
#31

LGTM +1 to merge

repo: sunspec/pysunspec


text:
Cannot install @supabase/auth-helpers-nextjs error not in the npm registry

When I try to install @supabase/auth-helpers-nextjs  I get the following error message.
npm install @supabase/auth-helpers-nextjs
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@supabase%2fauth-helpers-nextjs - Not found
npm ERR! 404
npm ERR! 404  '@supabase/auth-helpers-nextjs@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/dipeshwagle/.npm/_logs/2022-04-22T12_19_44_665Z-debug.log

You'll want to install @supabase/supabase-auth-helpers.  The nextjs utils can then be imported like this:
import { withAuthRequired } from '@supabase/supabase-auth-helpers/nextjs';

I created a PR to update this in the README at #87.

I've changed back to default to the main branch to make sure you see what's currently released.

authors: Dipeshwagle bill-offertrackr okezieuc thorwebdev


text:
Feat: Side panel

For the form actions - I think the side over (side panel..?) component should have the actions at the bottom.
we could add these actually into the side over panel itself, just like the Modal.
We can open an issue to make this component in ui lib.
see tailwind ui example for actions at the bottom -

Originally posted by @MildTomato in https://github.com/supabase/infrastructure/issues/716#issuecomment-765888967
example of side panel in GTM.
https://user-images.githubusercontent.com/8291514/105700872-762ce280-5f44-11eb-9ecb-0feb5913ce40.mov

@MildTomato Tailwind example is looking great 👍 I can play around with it to make it work if that's not assigned to anyone.
I guess it should be quite generic component, but I'm wondering if we should create top and bottom parts (kinda header and footer with actions) in this component. What do you think about it?

@MildTomato Tailwind example is looking great 👍 I can play around with it to make it work if that's not assigned to anyone.
I guess it should be quite generic component, but I'm wondering if we should create top and bottom parts (kinda header and footer with actions) in this component. What do you think about it?

@mrkldshv it's not assigned to anyone so feel free to have a crack at it.
I've already made a bit of a start on this component, it's in src/components/SideOver
You can see the demo/docs of it here
It could do with some tidying up, and also needs migrating to typescript 😄

I guess it should be quite generic component, but I'm wondering if we should create top and bottom parts (kinda header and footer with actions) in this component. What do you think about it?

Absolutely, I've already tried to split it up into 'header', 'content' and 'footer'.
For the footer - I think ideally it would be good to do the same as the Modal component, which has the option for a custom footer, where you can just use your own ReactNode in a prop rather than use the generic 'submit' and 'cancel' buttons.
Take a look and see what you think.
If you have any ideas on how to handle the nesting of panels (like in the video above) that would be superb! 💯

@mrkldshv it's not assigned to anyone so feel free to have a crack at it.
I've already made a bit of a start on this component, it's in src/components/SideOver
You can see the demo/docs of it here
It could do with some tidying up, and also needs migrating to typescript 😄

I guess it should be quite generic component, but I'm wondering if we should create top and bottom parts (kinda header and footer with actions) in this component. What do you think about it?

Absolutely, I've already tried to split it up into 'header', 'content' and 'footer'.
For the footer - I think ideally it would be good to do the same as the Modal component, which has the option for a custom footer, where you can just use your own ReactNode in a prop rather than use the generic 'submit' and 'cancel' buttons.
Take a look and see what you think.
If you have any ideas on how to handle the nesting of panels (like in the video above) that would be superb! 💯

Not sure if you've seen these - Supabase uses the side panel quite a lot in the table view in the dashboard, so we'd be quite keen to get those replaced with this new side panel if we can get it tidied up and support nesting.

Not sure if you've seen these - Supabase uses the side panel quite a lot in the table view in the dashboard, so we'd be quite keen to get those replaced with this new side panel if we can get it tidied up and support nesting.

@MildTomato Thanks for details! I'll try to make simple side over component and then we can think of handling nesting. Sounds good to you?

@MildTomato Thanks for details! I'll try to make simple side over component and then we can think of handling nesting. Sounds good to you?

@mrkldshv awesome! ping me in here if you have any trouble.

@mrkldshv awesome! ping me in here if you have any trouble.

@MildTomato finishing it up 🚀 Got couple questions regarding colors for light and dark variants though, and I think we can discuss it in MR. Also, the only problem I have is adding top border (any border) to footer, it just does not apply for some reason. Did you had similar issue? I've tried to reproduce it on playground, but wasn't able to.

@MildTomato finishing it up 🚀 Got couple questions regarding colors for light and dark variants though, and I think we can discuss it in MR. Also, the only problem I have is adding top border (any border) to footer, it just does not apply for some reason. Did you had similar issue? I've tried to reproduce it on playground, but wasn't able to.

@mrkldshv yea i've had problems using borders,  especially tailwind classes like border-t, i wasn't actually able to reproduce it in tailwind playground though, it seemed like a problem with tailwind setup on this repo.
ah way round it could be (if you want to keep using tailwind classes) is to do something like this.
/* Sidepanel.css */

.top-border-example {
  @apply border-gray-200 dark:border-dark-500;
  border-top-style: solid;
  border-top-width: 1px;
}

@mrkldshv yea i've had problems using borders,  especially tailwind classes like border-t, i wasn't actually able to reproduce it in tailwind playground though, it seemed like a problem with tailwind setup on this repo.
ah way round it could be (if you want to keep using tailwind classes) is to do something like this.
/* Sidepanel.css */

.top-border-example {
  @apply border-gray-200 dark:border-dark-500;
  border-top-style: solid;
  border-top-width: 1px;
}

@mrkldshv also had problems using tailwind divide 😒    it's probably a related problem

@mrkldshv also had problems using tailwind divide 😒    it's probably a related problem

Closing this 🚀  - thanks to @mrkldshv for this one 🔥
nesting feature moved to #104

Closing this 🚀  - thanks to @mrkldshv for this one 🔥
nesting feature moved to #104

authors: MildTomato mrkldshv

repo: supabase/ui


text:
JAVASCRIPT_ES: Invalid option '--eslintrc' - perhaps you meant '--ignore'?

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[X] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
When running super-linter through Github Actions or locally using the super-linter container image I receive always the same error for JAVASCRIPT_ES and JSON linter:
Invalid option '--eslintrc' - perhaps you meant '--ignore'?   You're using eslint.config.js, some command line flags are no longer available. Please see https://eslint.org/docs/latest/use/command-line-interface for details.
Expected Behavior
super-linter lints the codebase successfully and returns with exit code 0.
Super-Linter version
v6 / v6.6.0

Relevant log output
I prepared a Github Action run with v6 here - link points to the error:
https://github.com/patricklubach/approver-action/actions/runs/9742603873/job/26884239041#step:8:5498

And one for v6.6.0 here - link points to the error:
https://github.com/patricklubach/approver-action/actions/runs/9742742949/job/26884666606#step:8:5498

Steps To Reproduce
The same error appears locally when running super-linter using docker:

Clone repository: https://github.com/patricklubach/approver-action
Switch into cloned repository.
Run docker command:

docker run \
  -e LOG_LEVEL=DEBUG \
  -e DEFAULT_BRANCH=main \
  -e JAVASCRIPT_DEFAULT_STYLE=prettier \
  -e VALIDATE_ALL_CODEBASE=true \
  -e VALIDATE_JSCPD=false \
  -e CREATE_LOG_FILE=true \
  --rm \
  -e RUN_LOCAL=true \
  -v $PWD:/tmp/lint \
  ghcr.io/super-linter/super-linter:v6.6.0

Optional: May you need to change permissions on the super-linter.log file: sudo chmod o+r super-linter.log

Anything else?
Context:
Currently I am learning JavaScript and try to create my first Github Action and used the template here: https://github.com/actions/javascript-action/tree/main
Link to my repository: https://github.com/patricklubach/approver-action
If you need something, let me know.

Hi @patricklubach ! I think this is a duplicate of #5688.

@ferrarimarco thank you for replying. As it was pointed out in the issue you referenced it is more a feature request than a bug so maybe I didn't see it but anyway I will test the fix later today and if it works I will close this one and follow up on the other one. Thank you very much!

authors: ferrarimarco patricklubach

repo: super-linter/super-linter


text:
feat: Setup All Contributors

Description

https://github.com/superfaceai/one-sdk-js/tree/feat/all-contributors#contributors-
I picked the emojis mostly randomly so feel free to disagree with your assignment.
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have updated the documentation accordingly. If you are changing code related to user secrets you need to really make sure that security documentation is correct.
[ ] I have read the CONTRIBUTING document.
[ ] I haven't repeated the code. (DRY)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@jnv Is this good to go? 🤔

@jnv Is this good to go? 🤔

Well, I wasn't quite happy about the roles distinction. Also I think the roster was in a wrong place. I will reopen it today.

authors: Jakub-Vacek jnv

repo: superfaceai/one-sdk-js


text:
[CONSOLE] Assorted Visual Bug Fixes

Task List

[ ] Vertical centring of Superfluid logo in top left of Console
[ ] Change interactable icons in page headers to buttons or green links

Show token symbol before balance.
Almost every page has a grid at the start of the page that is broken.

btw @vmichalik, don't you like the icons? Imo it looks nice and clean like this. If you have interacted with the icon once then you will remember what it does.

design best practices are to have a different colour for interactable elements

authors: Mikkoun vmichalik

repo: superfluid-finance/superfluid-console


text:
UI should should supergiant version

When debugging issues, one of the first questions is "what version are you running?". This information is not available from the dashboard UI.

@FestivalBobcats Wondering about the approach found here to help us generate version numbers?

authors: devrsw mrichmon

repo: supergiant/supergiant


text:
Spike: copy and paste plain text.

Spike: copy and paste plain text.

Since reviews are not being done, and we're currently only dealing with spikes, I've temporarily turned off require approvals and I'm merging in this spike.


text:
🛑 Node - us-5cdf1ea7.yalaso.top is down

In 0c09a7d, Node - us-5cdf1ea7.yalaso.top (http://us-5cdf1ea7.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - us-5cdf1ea7.yalaso.top is back up in 16c41a6 after 3 hours, 25 minutes.

repo: superrr-vpn/status


text:
🛑 Rufus Jackson Landing Page is down

In b3d6197, Rufus Jackson Landing Page (https://insurancesavingsmichigan.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rufus Jackson Landing Page is back up in 8528de3 after 9 minutes.

repo: superwebpros/uptime


text:
Prompted to provide --cluster-name

Sometimes when I'm running the plugin it errors and tells me to provide the cluster name. I haven't figured out why (yet). Usually I have an exported KUBECONFIG file with a single cluster but providing the --cluster-name doesn't resolve the issue.
Here's an example. You can see that k get nodes works fine but k eks nodes doesn't know what cluster to use. My KUBECONFIG var is set to /home/ANT.AMAZON.COM/rothgar/.kube/spot
☸ spot in .dotfiles on  main [$] on ☁  demo (us-east-1)
❯ k config get-clusters
NAME
arn:aws:eks:us-east-1:323238900174:cluster/spot

☸ spot in .dotfiles on  main [$] on ☁  demo (us-east-1)
❯ k get no | head -3
NAME                              STATUS   ROLES    AGE   VERSION
ip-192-168-100-26.ec2.internal    Ready    <none>   19h   v1.27.1-eks-2f008fe
ip-192-168-101-104.ec2.internal   Ready    <none>   18h   v1.27.1-eks-2f008fe

☸ spot in .dotfiles on  main [$] on ☁  demo (us-east-1)
❯ k eks nodes
2023/06/08 11:12:56 please pass cluster name with --cluster-name or with AWS_EKS_CLUSTER environment variable

☸ spot in .dotfiles on  main [$] on ☁  demo (us-east-1)
❯ k eks nodes --cluster-name spot
Error: unknown flag: --cluster-name
Usage:
  kubectl-eks nodes [flags]

Flags:
  -h, --help   help for nodes

Global Flags:
      --as string                      Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
...

ah I think I know why this is happening, there's no --cluster-name flag defined  for nodes command like how it is for other commands https://github.com/surajincloud/kubectl-eks/blob/main/cmd/nodegroups.go#L86
will get it fixed quickly

I think, #46 just fixes the flag problem, but I will check other issues as well.

I just built main 4b87943 and still get prompted for cluster name

@rothgar this should fix the issue: https://github.com/surajincloud/kubectl-eks/pull/47 try the main now.
This line was the culprit: https://github.com/surajincloud/kubectl-eks/pull/47/files#diff-b1ddc12073437afb094f910de081ff3d1fa4a61572ddb44409a9e82b0e975b19L39 which was asking for `--cluster-name``
should be fixed now

Yep, that works.
There is a semi-related issue I have where the plugin explicitly requires AWS_REGION to be set in the environment instead of using my default configured in the AWS profile. You can see here in the command output. Notice my terminal prompt (using starship.rs) picks up my default region configured from the profile
☸ production in demos/clearwater on  main [$✘!?] on ☁  demo (us-west-2)
❯ /home/ANT.AMAZON.COM/rothgar/src/kubectl-eks/kubectl-eks nodes
2023/06/09 09:58:15 please pass region name with --region or with AWS_REGION environment variable

☸ production in demos/clearwater on  main [$✘!?] on ☁  demo (us-west-2)
❯ env | grep AWS_
AWS_PROFILE=demo
AWS_DEFAULT_PROFILE=demo

☸ production in demos/clearwater on  main [$✘!?] on ☁  demo (us-west-2)
❯ export AWS_REGION=us-west-2

☸ production in demos/clearwater on  main [$✘!?] on ☁  demo (us-west-2)
❯ /home/ANT.AMAZON.COM/rothgar/src/kubectl-eks/kubectl-eks nodes
NAME                                              INSTANCE-TYPE

@rothgar that's great point, I kind of know why that's happening, fix is coming in #48 Happy Friyay :tada:

@rothgar try the main now? should work as intended. I changed the issue name for tracking both the flags :)

This worked for me. :+1:

closing this as it is fixed in: https://github.com/surajincloud/kubectl-eks/releases/tag/v0.3.0

authors: rothgar surajnarwade

repo: surajincloud/kubectl-eks


text:
Good first issue label

What about to add "Good first issue" label to some issues?
I see a lot of new issues, I think we could delegate some of them to somebody who wanna be in our contributor's list.
What do you think @LastSprint ?

Delegated issueses marked "Help wanted", couse these not depend from library designing.
You should keep in mind that CoreNetKit is at redesign stage.

@LastSprint Oh, ok, thanks

authors: LastSprint ismetanin

repo: surfstudio/CoreNetKit


text:
[Docs] Update README.md to be more accurate

Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
I needed to quickly start using the Python driver. This documentation is flawed, and I realized I could very quickly fix it. This will save time for other developers like me.
Type of Change

[X] Replaced all references to SurrealDB and AsyncSurrealDB with Surreal
[X] Added the use function for connecting to namespaces and databases
[X] Fixed connection strings to properly reference the /rpc route rather than /database/namespace

What does this change do?
These changes make it easier for people to quickly start writing code with the Surreal Python driver.

[X] I have read the Contributing Guidelines

Closing this pull-request as the latest codebase has now been significantly updated, now making use of a native Python with binary communication with remote databases, and support for embedded database usage. The native Python library now has support for custom types, including datetimes, durations, decimals, geojson types, Record IDs, ranges, and tables 🎉.

authors: nottisa tobiemh


text:
syntax highlight

hi there ,many thanx for this series ,one question though
the below img is from the Tabs Inside Out

could u plz tell me which editor/IDE u were using ?

I was using Sublime Text 2. Hope that helps.

can u tell me which scheme u were using ? ,am trying to implement the same thing but i cant find any scheme/syntax lang that have this scopes.

I am not sure what you mean by scheme/syntax lang. Can you please elaborate?
Sorry for the delay though.

the scheme is the color scheme file u use to get the highlight i.e monokai the syntax language is the actual language u use in ST like html,js,css,etc.. so i was asking were u using a custom package other than the default that came with ST ?

Nothing really fancy and I don't think I had anything apart from the popular Angular plugins like AngularJS/ AngularJS Snippets.
Hope that helps.

unfortunately i cant get the same highlighting as in the screenshot because anything within the double quotes are treated the same so all get the same color which is driving me nuts ,still thanx for ur help :+1: .


text:
📦 upgrade:  Update Flutter SDK 3.0.2

Issue #172

Codecov Report

Merging #173 (00f0fb0) into develop (0bf69dd) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop      #173   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           52        52
  Lines         1254      1254
=========================================
  Hits          1254      1254

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0bf69dd...00f0fb0. Read the comment docs.

authors: codecov-commenter susatthi

repo: susatthi/github-search


text:
Unable to build EIB Image on macOS - 'hauler' not found in package names'

I am unable to build the EIB Image on macOS and get the following error message.
Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache [....done]
Retrieving repository 'Update Repository (Non-Oss)' metadata [........done]
Building repository 'Update Repository (Non-Oss)' cache [...done]
Loading repository data...
Reading installed packages...
No provider of 'hauler' found.
'hauler' not found in package names. Trying capabilities.
Error: building at STEP "RUN zypper install -y     xorriso squashfs      libguestfs kernel-default e2fsprogs parted gptfdisk btrfsprogs gues
tfs-tools lvm2     podman     createrepo_c     helm hauler     nm-configurator &&     zypper clean -a": while running runtime: exit status 1
04

Running on:

OS: macOS 13.6 22G120 arm64
Podman: 4.9.3

Previous versions of the EIB image worked perfectly!
I followed the instructions in the README but not clear why I should need all the different libraries installed as they are pulled-in via the Dockerfile.

Hey, @mpas. Please delete the Podman image caches and rebuild.
For reference: https://github.com/suse-edge/edge-image-builder/pull/248

@atanasdinov Life saver! Works!! Thanks!!!

authors: atanasdinov mpas

repo: suse-edge/edge-image-builder


text:
feat: improve uninstall script to find the installed version

This commit improves the experience of using the uninstall script by
automatically finding the version of kepler-operator installed. So, user
need not explicitly specify the version to installed (but they can
should they choose to) to uninstall.
It also adds a --help option to the script to print the usage

cc: @vimalk78 @vprashar2929

can we add an option to find resources even if find_installed_version fails? for those clusters where operator installation fails halfway.


text:
affilateEmail

hjuik

This PR was automatically closed and added to a release PR: https://github.com/suvikram/apex-recipes/pull/41

repo: suvikram/apex-recipes