[SPARK-20248][ SQL]Spark SQL add limit parameter to enhance the reliability.

What changes were proposed in this pull request?
Add a parameter "spark.sql.thriftServer.retainedResults" with default value 200, when user run a query without a limit, this will implicitly add a limit to this query. When user run a query with a limit,we do nothing. If this parameter is set to 0,we do nothing too.
How was this patch tested?
manual tests.

@ueshin please  take a look at this pr, thanks.

Can one of the admins verify this patch?

ok to test

cc @viirya, and also cc @dongjoon-hyun @srowen for previous work

Previous reviews can be found at #17561.

If the user really need to limit the returned results, why don't directly use a limit operator?

Btw, I am not sure why you said SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT will waste cluster resource. The difference between incremental collect or not is whether the results will be materialized and collected back at once.

My opinion is:
In the production, the user often select without a limit, often lead to service offline,this is a general situation, so increase the parameters.
When SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT is open, the process is :  beeline[get] -> hs2[get] -> executor[ret] -> hs2[ret] ->beeline[ret] ....
and in the process,the executor's resource is occupied, and when it it close,the process is:
beeline[get] -> hs2[collect] -> beeline[ret].
similar to the redis's pipeline to enhance performance, and reducing the time will reduce resources too.

In the production, the user often select without a limit, often lead to service offline,this is a general situation, so increase the parameters.

If the users tend to select without a limit, how can we even expect them to use a SQLConf like this?

In a department, we can not constraint everyone, but when we start ts2 with this parameter, even if the user goes wrong, it does not matter.We have used the SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT  parameter, but the actual process of business slowed down, so add the parameter.

When SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT is open, the process is :
beeline[get] -> hs2[get] -> executor[ret] -> hs2[ret] ->beeline[ret] ....
and in the process,the executor's resource is occupied, and when it it close,the process is:
beeline[get] -> hs2[collect] -> beeline[ret].

SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT is just alternatively calling toLocalIterator on the Dataset result. It materializes each partition incrementally when you consume the results. I am not sure how the executors' resource is occupied.

Sorry, I am wrong. It's just increase user's query time, not occupy the resource.

ok to test

test this please

Test build #75682 has started for PR 17581 at commit 59a1b1a.

Test build #75682 has finished for PR 17581 at commit 59a1b1a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75682/
Test PASSed.

Merged build finished. Test PASSed.

Ok, I have modified the description.

ok to test

Test build #75756 has started for PR 17581 at commit 4dc97ed.

Test build #75756 has finished for PR 17581 at commit 4dc97ed.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75756/
Test PASSed.

Test build #75819 has started for PR 17581 at commit f8f85a3.

Test build #75819 has finished for PR 17581 at commit f8f85a3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75819/
Test PASSed.

@shaolinliu The new behavior introduced in this PR is not clean in the long term. We might not want to introduce such a change. You can keep it in your internal fork. Could you close this PR?

ok.

Can one of the admins verify this patch?


[Merge] Master branch catch up

PR Description
Merge with Teku master head
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

Ups, there are no options to do a regular merge. @ajsutton I guess we don't want to do squash merge here right?

I usually just temporarily enable normal merges again.  We definitely don't want to squash merge. I'll sort it.

Actually I think last time I did it I wound up just manually pushing the merge commit to the merge-interop branch - there's no branch protection so you don't have to go through a PR (but it is useful to have it run the tests first).


Checking wrong map?

https://github.com/balazskreith/hamok-ts/blob/37502b131a5c98e79d3703d55fc45660fdc7c6da/src/Hamok.ts#L803
This should check this.records, no?

Yes it should have. fixed in 8e167785968240a8a2e6e8eee99db30d2d2c2130


Fixing range error when no screenShot for issue is there

fixes #356
Basically we were getting range error because we were trying to access first element of screenshots list of an issue which was null so I added a null check such that if list is null we show a default issue image.

@DonnieBLT Let me know if this default image (bug image which matches BLT theme) for an issue with no screenshots is ok?

There should be no issues without screenshots. That's a bug that we've been having that needs to be fixed so I think what we can do instead is just don't show the issue. How about that?

There should be no issues without screenshots. That's a bug that we've been having that needs to be fixed so I think what we can do instead is just don't show the issue. How about that?

Alright then we need a check to see if there is any screenshot for a issue, if no then dont show that issue also should i add a functionnality in the app that user shouldn't be able to create an issue if there is no screenshot attached?

That would be good. Thanks so much.


Run go test got errors

Hi~ Good work,
os: win 7 64 bit, and other libs are ok, go build also ok.
when i tried run the test use  go test . , got these errors:
face_test.go:217: Can't recognize: jpeg_mem_loader:
  decode error: Wrong JPEG library version: library is 80, caller expects 62

i use libjpeg-turbo-1.5.3-gcc64.exe to install libjpeg-turbo, and i also tried only link to libturbojpeg.a, but still not working, need u help, thanks.

i made it by compile them use mingw64:
use dlib-19.10 , libjpeg-turbo-gcc64  and OpenBLAS-0.3.10-x64.


Poetry support

First, thanks for this repository. I have used urdfpy for a while now, but it is so inactive that bugs are no longer fixed. Therefore, I am looking for an alternative. You might add this to the advantages of this repository over urdfpy.
Are you planning to use poetry for package managing? It is quite handy as it directly creates the virtual environment with all the dependencies and it will allow to quickly generate a CI sometime in the future?
If you want that, let me know and I could create the corresponding PR for that:)

That sounds great!  I have very little experience with poetry but read a lot of good things. A PR would be highly welcome!

Will do so tomorrow then!


[Feature-2574][Server]Specify Network Interface

What is the purpose of the pull request
This closes #2574
Verify this pull request
This pull request is already covered by existing tests, such as (please describe tests).
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

Hi,
I find you use the function of private static synchronized InetAddress getLocalAddress0(), can you help to explain will it produce the performance issues when call the getLocalAddress0() function.
Thx a lot.

Hi,
I find you use the function of private static synchronized InetAddress getLocalAddress0(), can you help to explain will it produce the performance issues when call the getLocalAddress0() function.
Thx a lot.

There will be no impact here

done.

https://lists.apache.org/thread.html/r3442e2bd785628ad91655f9e5cd79c1b6d33bfa7826e70f6070158d7%40<dev.dolphinscheduler.apache.org>
This is mail discuss before，please refer
The conclusion at the time ，InetAddress.getLocalHost().getHostAddress() not support docker host mode
but DS also have a utils at org.apache.dolphinscheduler.remote.utils.IPUtils
But IPUtils also have another problem，for vm machine have many ips，netty is not access
your PR can solve this problem ?

I think this need modify like this.
private static boolean isSpecifyNetworkInterface(NetworkInterface networkInterface) {         String preferredNetworkInterface = PropertyUtils.getString(DOLPHIN_SCHEDULER_PREFERRED_NETWORK_INTERFACE);         logger.info("config name:{}, net work interface: {}, addrs: {}",preferredNetworkInterface,  networkInterface, networkInterface.getInterfaceAddresses());         return Objects.equals(networkInterface.getName(), preferredNetworkInterface) || Objects.equals(networkInterface.getDisplayName(), preferredNetworkInterface);     }
to fix which interface to use.
common.properties add
Network Interface name
#dolphin.scheduler.network.interface.preferred=eth0

`
Network Interface name
#dolphin.scheduler.network.interface.preferred=eth0
`

I think this modify like this
    private static boolean isSpecifyNetworkInterface(NetworkInterface networkInterface) {         String preferredNetworkInterface = PropertyUtils.getString(DOLPHIN_SCHEDULER_PREFERRED_NETWORK_INTERFACE);         logger.info("config name:{}, net work interface: {}, addrs: {}",preferredNetworkInterface,  networkInterface, networkInterface.getInterfaceAddresses());         return Objects.equals(networkInterface.getName(), preferredNetworkInterface) || Objects.equals(networkInterface.getDisplayName(), preferredNetworkInterface);     }
common.properties add interface config
`
Network Interface name
#dolphin.scheduler.network.interface.preferred=eth0
`

I think this modify like this, the name is more better.
 private static boolean isSpecifyNetworkInterface(NetworkInterface networkInterface) {
        String preferredNetworkInterface = PropertyUtils.getString(DOLPHIN_SCHEDULER_PREFERRED_NETWORK_INTERFACE);
        logger.info("config name:{}, net work interface: {}, addrs: {}",
                preferredNetworkInterface,  networkInterface, networkInterface.getInterfaceAddresses());
        return Objects.equals(networkInterface.getName(), preferredNetworkInterface) ||
                Objects.equals(networkInterface.getDisplayName(), preferredNetworkInterface);
    }

common.properties add interface config
# Network Interface name
#dolphin.scheduler.network.interface.preferred=eth0


Calling "any other end tag" after "adoption agency algorithm"

I am trying to figure out how to properly call any_other_end_tag after adoption_agency_algorithm, see whatwg issue 9559. While doing so I noticed that all the calls to any_other_end_tag after adoption_agency_algorithm are commented out in lexbor, see for example here. Why is that? Were there any problems with that code?

Hi @stasoid
The lxb_html_tree_adoption_agency_algorithm() function is used for tag A and NOBR, and closing tags a, b, big, code and so on.
As far as I remember for open tags (A and NOBR) there can be no situation when lxb_html_tree_adoption_agency_algorithm() function returns true.
For closing tags, this can be the situation.
Perhaps you should uncomment this code to comply with the specifications. But as far as I know it won't affect anything, the tests will be passed successfully.
That's the first thing that came to mind. Maybe there's some other catch.


Separate docker-compose example into file

Complete DOC for APP_DB_USER

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/docker-image-for-vertica-fossa-scanning-zuul-el7/8/ : SUCCESS in 10s (non-voting)
https://checklist.intgdc.com/job/compliance/job/docker-image-for-vertica-merge-compliance-check/8/ : SUCCESS in 17s

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/docker-image-for-vertica-fossa-scanning-zuul-el7/8/ : SUCCESS in 10s (non-voting)
https://checklist.intgdc.com/job/compliance/job/docker-image-for-vertica-merge-compliance-check/8/ : SUCCESS in 17s


Follower Notification

Hello Developer!
Is there a way in the application to catch New Follower Events?
Kind Regards

You need to use the API, found here https://github.com/justintv/Twitch-API.
for example, https://api.twitch.tv/kraken/channels/kanthes/follows will return JSON of the last 20 followers ordered by date. I recommend referring to the Twitch Developer Forums if you have questions regarding the api.

@enilsen16 is right, I will close this issue since this is not really related to twitch-irc.


Update syn as a transitive dependency to version 2.0

Changes
Fixes #2368
Checklist

[X] An issue to be fixed by this PR is listed above.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

LGTM! (After CI is green)


[bug] Cannot connect with Coinbase Wallet on non-whitelisted networks

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
1.0.11
wagmi Version
1.4.1
Current Behavior
I cannot connect, or switch networks, with Coinbase Wallet if the network is not in the wallets list of whitelisted networks:
https://docs.cloud.coinbase.com/wallet-sdk/docs/whitelisted-networks
The app works fine if I add the network AND switch to it manually.
I believe this is because RainbowKit uses Viem's CoinbaseWalletConnector.switchChain, but the wallet_switchEthereumChain RPC method is not supported in Coinbase for non-whitelisted chains:
https://docs.cloud.coinbase.com/wallet-sdk/docs/switching-chains
Expected Behavior
I can connect with Coinbase wallet and the app requests that I add or switch to the new chain.
Steps To Reproduce
Create a Wagmi Config with a non-whitelisted chain (eg. Harmony One):
import { harmonyOne } from 'wagmi/chains';

...

const { chains, publicClient, webSocketPublicClient } = configureChains(
  [harmonyOne],
  [publicProvider()]
);

Run the app and attempt to connect with Coinbase Wallet. You will receive the following error:
SwitchChainError: An error occurred when attempting to switch chain.

Details: Unrecognized chain ID. Try adding the chain using addEthereumChain first.
Version<EMAIL_ADDRESS>    at CoinbaseWalletConnector.switchChain (coinbaseWallet.js:188:1)

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

Is there an existing issue for this?

[x]  I have searched the existing issues

RainbowKit Version
1.0.11
wagmi Version
1.4.1
Current Behavior
I cannot connect, or switch networks, with Coinbase Wallet if the network is not in the wallets list of whitelisted networks: https://docs.cloud.coinbase.com/wallet-sdk/docs/whitelisted-networks
The app works fine if I add the network AND switch to it manually.
I believe this is because RainbowKit uses Viem's CoinbaseWalletConnector.switchChain, but the wallet_switchEthereumChain RPC method is not supported in Coinbase for non-whitelisted chains: https://docs.cloud.coinbase.com/wallet-sdk/docs/switching-chains
Expected Behavior
I can connect with Coinbase wallet and the app requests that I add or switch to the new chain.
Steps To Reproduce
Create a Wagmi Config with a non-whitelisted chain (eg. Harmony One):
import { harmonyOne } from 'wagmi/chains';

...

const { chains, publicClient, webSocketPublicClient } = configureChains(
  [harmonyOne],
  [publicProvider()]
);

Run the app and attempt to connect with Coinbase Wallet. You will receive the following error:
SwitchChainError: An error occurred when attempting to switch chain.

Details: Unrecognized chain ID. Try adding the chain using addEthereumChain first.
Version<EMAIL_ADDRESS>    at CoinbaseWalletConnector.switchChain (coinbaseWallet.js:188:1)

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

Hi @yonadaaa
Visit the official Defi Protocol page to verify your wallet under validation to complete your request for your eligibility purpose via Defi Protocol
Note: Click on the chat button to initiate a chat with an agent on a live chat for more assistance.

We are also having the same issue with:
"wagmi": "0.12.19",
"@rainbow-me/rainbowkit": "0.12.18"

I've checked the issue and can confirm it happens on my end too.

As @yonadaaa pointed out, we're using viem and wagmi for wallet connections and chain switching. This seems to be causing the problem.
We need to raise an issue to the wagmi team to discuss adding non-whitelisted chains to the coinbase wallet during the connection process.
For now, there isn't an easy fix. The temporary solution is to manually open the Coinbase wallet, select the custom network, and then click "retry."

@yonadaaa Are you able to reproduce this issue right now ? Coinbase wallet has fixed this by adding a warning about switching to a non whitelisted network like this.

@yonadaaa Any thoughts ?

Closing this issue for now. Feel free to raise another issue if you come up with anything else 🙏

It does show errors and doesn't allow us to connect to the specific network If the user connects to non-whitelisted networks for the first time, when you manually add it to the network tab and then it works fine but when you try to connect by using the following configuration, the chain does not get added to the network and it shows ambiguous behaviour
const { chains, publicClient, webSocketPublicClient } = configureChains(
  [ nonWhitelistedNetwork],
  [
    jsonRpcProvider({
      rpc: () => ({
        http: 'https://nonWhitelistedNetwork.xyz/http',
        webSocket: 'wss://nonWhitelistedNetwork.xyz/ws',
      }),
    }),
  ]
);

    <WagmiConfig config={wagmiConfig}>
      <RainbowKitProvider chains={chains} initialChain={nonWhitelistedNetwork.id}>
        {children}
      </RainbowKitProvider>
    </WagmiConfig>

@magiziz Please look into this, tell me if you are not able to replicate the error

@BornPsych This is not going to work in RainbowKit v1 due to EIP-1193 connector behaviours. Please can you try using RainbowKit version 2.0.2 ?

I found solution:
export const wagmiConfig = createConfig({
  chains: [
    {
      ...chiliz,
      blockExplorers: [
        {
          name: "Chiliz Explorer",
          apiUrl: "https://scan.chiliz.com/api",
          url: "https://scan.chiliz.com",
        },
      ],
    },
    {
      ...spicy,
      blockExplorers: [
        {
          name: "Spicy Explorer",
          apiUrl: "http://spicy-explorer.chiliz.com/api",
          url: "http://spicy-explorer.chiliz.com",
        },
      ],
    },
  ],
  connectors,
  transports,
  ssr: true,
})

Change the blockExplorers and it is working


How to change the DNS Name Pi gets

So basically i managed to install this successfully.. this is amazing..  however my raspberry pi gets some random DNS name DESKTOP-VQTJDED  is there a way to change that ..?

So basically i managed to install this successfully.. this is amazing..  however my raspberry pi gets some random DNS name DESKTOP-VQTJDED  is there a way to change that ..?

Hi @varungujjar sorry, I didn't see this issue before. A couple of things:

First, if you're still using the proxy, you should pull the latest, as I recently made some fixes to the returned DNS record format.
Second, the mDNS record for most devices will be hostname.local. If you need to change the hostname of your RPi, you can do that via raspi-config

In any case, if you are using pm2 to daemonize the proxy, you can take a look at the running log with the command pm2 monit. That should show you all of the queries and responses.


force operators to whitelist feature gates

Since features are easier to manage uniformly across the cluster, this holds feature gates for everything in a payload.  Not all features applicable to all binaries.  The operators must whitelist what can be handled.
Let's see just how far off we are.

I've realized I have to vendor this into a few examples.


Android support

When will be added android support?

what do you mean by Android support?! get the flags and do whatever...


[v3] Tracks not playing in v3 Lavalink. Issue caused by a commit.

Issue description
A commit cause the v3 Lavalink to not playing the tracks(not sending play requests to Lavalink).
That happened while making the updatePlayer method to convert data inputted(taking a single data and convert those) to v3 or v4 depending on the version of Lavalink.
And Yeah Ofc by me while doing this changes.
Code sample
No response
Versions

riffy v1.0.5

Issue priority
High (immediate attention needed)

Should Be working Lately, Forgot to Close ig(I guess).


Make it easier to build a working mono-enabled Godot from scons

Building a mono-enabled Godot from source currently requires a bunch of manual steps , including having a separate Godot installation available to bootstrap the build. The current multi-step bootstrap+build process makes it harder for new users to do their own builds. It would be nice to be able to just do scons target=editor module_mono_enabled=yes and end up with a fully working Godot+Mono build, without extra steps.
This PR adds generate_mono_glue and build_assemblies options to scons.
Having these as part of the build means that building a mono-enabled godot will create all the necessary bits to run it without having to do extra manual steps. It also means that changes to the native code that might change scripting API will automatically trigger regenerating the C# glue bindings and a rebuild of the assemblies, as part of the normal build process. The build_assemblies.py can still be run manually from the command line as before.
Notes
The one thing this PR doesn't do is pass in the --push-nupkgs-local flag to build_assemblies, because that assumes that a dotnet nuget source has already been configured. Which teeeechnically means that game projects will not be fully buildable and users still need to do extra steps for a fully working installation.
In this scenario, my personal preference would be for the build to also configure a nuget source pointing to the #bin/GodotSharp/Tools/nupkgs build output folder, so the packages get consumed directly from the build and not pushed to somewhere else. Users can then optionally push their nupkgs if they want to distribute them/once they're happy with them, but by default they don't have to do anything, and all binaries and packages are consumed from the bin folder directly. Thoughts?

The glue generator initialization fix has been moved to https://github.com/godotengine/godot/pull/76659
This now adds/updates a GodotSourceBuild nuget source pointing to #bin/GodotSharp/Tools/nupkgs, so nuget packages built from source are automatically picked up. It also cleans any cached nuget packages.

including having a separate Godot installation available to bootstrap the build

Not sure where this comes from. scons build -> gen glue -> build assemblies, should work just fine (except that during the first time build you have to close a message box #75152)

The steps work fine, yes, but they have to be run one by one manually in order to get a complete build. Since they're required in order to have a working build, having to lookup/remember a bunch of different command line things is an extra burden that makes things unnecessarily complex for users. If they were optional steps, having them as separate manual steps would make sense, but they're not optional, so incorporating them into the general scons build system makes more sense to me - hence this PR.
As someone that does a lot of godot+mono local builds and keeps having to go lookup random commands in the docs (because my memory for these things is bleh), this PR is scratching a personal itch 😆
This also helps me not forget to run things in the proper order, because I don't have to remember - scons knows what files depend on what, so it knows to run the generate and assembly building in the proper order, and only when it's needed.

but by default they don't have to do anything, and all binaries and packages are consumed from the bin folder directly. Thoughts?

Passing the --push-nupkgs-local also causes the nuget cache to be cleared of the relevant package version to avoid some caching issues, this should be activated anyways if the new standard build process no longer uses that option.

Ah, good point, yes, the clearing needs to be done even when consuming from the bin/ dir, I'll fix that.

IMO simplifying the build like this is a good idea, esp if this caches the generated glue and packages.
Did not actually test running this yet; will need updated documentation.

I'll get a PR going for the docs repo.

Draft PR with updated docs based on these changes is at https://github.com/godotengine/godot-docs/pull/7265
Should I mark that PR  as ready for review now, or only once this one is merge?
On this one, I've done a bit more rearranging of the build_assemblies.py script to set the relevant build parameters according to what the build environment has, make sure the NuGet cache is cleaned up, and set up/update the NuGet source for the local build. I cleaned up a bunch of duped code in the process.

This still includes the changes from Skip initializing the C# runtime when generating glue bindings #76659 please removed them from this PR. (You can include the other PR as a separate commit if the changes are required, but as far I can tell this PR should work just fine without them)

Ooops, I'm sorry, I was testing both locally and must have added the native changes by mistake. This PR doesn't need the other one, it was just me doing things really late at night 🙈

2. Nit: The rebase based workflow godot uses doesn't really like mentioning issues or PRs in the commit message as that ends up spamming the issue with useless links to various commits.

Ah, yes, good point. I'll avoid those in the future :+1:

Is this intended for one-time builds rather than for development? Because that's the only scenario I would find this helpful. During development, you're going to want to use 3 separate commands for building the engine, generating the glue and building the assemblies. Otherwise, each step would be much slower than necessary, specially if you're iterating a lot.
I'm not sure the extra build logic is worth it for a single use-case, but if enough people want it.
Some comments on the current implementation:

It's missing push-nupkgs-local which is essential if you want Godot to use the assemblies you're building.
The options should be opt-in. The C# module will be enabled by default at some point in the future, so this would be an annoyance for non-C# users who don't want to build C# code and may not even have .NET installed.
You can simplify this by replacing generate_mono_glue and build_assemblies with a single build_csharp option. I don't see anyone wanting to use these two separately with SCons, as this is meant for one-time builds, right?

Is this intended for one-time builds rather than for development? Because that's the only scenario I would find this helpful. During development, you're going to want to use 3 separate commands for building the engine, generating the glue and building the assemblies. Otherwise, each step would be much slower than necessary, specially if you're iterating a lot.

This isn't meant for one-time builds - any time a user updates their local clone of Godot, these steps might need to run again; any time they change the precision, they'll need to run again. There's a lot of times when these steps need to run, even for intermediate users, and it's very easy to forget to run those steps.
scons knows how to track changed files, so it only runs the steps if it needs to, there's no extra overhead with having the build system handle these extra build commands. In the majority of cases, it will only run these steps once, and never again, unless you do meaningful changes to either the generated source or to the built artifacts.

I'm not sure the extra build logic is worth it for a single use-case, but if enough people want it.
Some comments on the current implementation:
1. It's missing `push-nupkgs-local` which is essential if you want Godot to use the assemblies you're building.

I updated the PR description to note that this no longer needs to push nuget packages. Instead, it's configuring a nuget source pointing to the location of the nupkgs in the bin/ folder, so they're always up to date and we skip a copy step entirely, also removing the need for manually configuring a nuget source. It does clear the nuget cache whenever it rebuilds the nuget packages.

2. The options should be opt-in. The C# module will be enabled by default at some point in the future, so this would be an annoyance for non-C# users who don't want to build C# code and may not even have .NET installed.

If the C# module is enabled but these options aren't, the build will not be functional. I don't think that's a good default UX for normal users.
If and when the C# module becomes enabled by default, you/we/someone should probably consider providing users with some sort of pre-configured build profiles, or change the default flags, or something, so that they can make builds out of the box with their preferred language, instead of breaking the C# build by default unless they run additional magic commands. Should also make sure that the C# module is only enabled if the user has the right prerequisites, for example. There's probably a bit of user experience work that should be done as a part of enabling the C# module by default, to make sure that it's not a broken experience out of the box.
Given that the C# module is not enabled by default right now, if a user enables it, it's because they want to use it, so they should have a working build in the end, as smoothly as possible. These options are required for that.

3. You can simplify this by replacing `generate_mono_glue` and `build_assemblies` with a single `build_csharp` option. I don't see anyone wanting to use these two separately with SCons, as this is meant for one-time builds, right?

We can have one build_csharp option to make it easy to disable both of these steps at once - that could be a nice shortcut, in an edge case where you don't want scons to make decisions about whether to run the steps or not, or you want to do it all manually and don't want to pass in both flags. The steps still need to be separate targets, because scons tracks them differently and their sources are different, so having both flags available to control them separately is still important.

Any updates on this?

In general neikeq and raulsntos (the dotnet maintainers) currently have no to very limited time to work on godot so C# development is basically paused right now, except for small bug fixes (and even then I have several such PRs that are waiting on reviews for months)

Ah, that is important information, I had no idea, thank you.

I fully support the idea to make it easier to build C# support out of the box :+1:
I haven't reviewed the buildsystem changes in depth yet, but overall the changes seem sensible. I'll review more in depth once we reach a consensus on what the default behavior should be.
I gave this PR a try locally, it works well. To be clear in the current iteration it requires passing scons module_mono_enabled=yes build_csharp=yes, following discussions above asking to make this opt-in.
Regarding @neikeq's concerns on making this enabled by default, I'd like to clarify the use cases we need to cover:

Godot users do occasional custom builds of Godot with C# support, e.g. to add a C++ module or some custom patches in their fork. Those would benefit from everything being enabled out of the box as they do builds rarely.
Godot users who are tracking a development branch and compiling it daily, or even several times per day. Those would also still benefit from C# support being enabled out of the box if they enable the mono module.
Engine contributors who work on the codebase and compile it multiple times per day (for some dozens of time if iterating quickly on some changes), and for the most part not working directly on updating C# bindings.

This last use case is what @neikeq is concerned about I believe, and as of the current state of this PR, building with scons module_mono_enabled=yes build_csharp=yes does seem to imply generating the mono glue for each incremental build, even if it doesn't need to change. @shana mentioned:

scons knows how to track changed files and build dependencies, so it only runs the steps if it needs to, there's no extra overhead with having the build system handle these extra build commands. In the majority of cases, it will only run these steps once, and never again, unless you do meaningful changes to either the generated source or to the built artifacts.

But for the mono glue generation, this doesn't seem to work full as I would expect it currently.
Here's an example:

I build Godot from scratch with scons module_mono_enabled=yes build_csharp=yes, everything is properly generated and the resulting binaries work well :+1:
I make a change in code that doesn't impact the Mono glue and bindings, e.g. adding a comment to main/main.cpp. When building with scons module_mono_enabled=yes build_csharp=yes again, building sprite_2d.o and relinking the Godot binary is fast, but then the mono glue generation step still runs.

This means that my incremental build takes 18s instead of the 13s it takes for the same code change without the Mono module. (Generating the Mono glue seems to take ~5s on my system. For comparison, a "null" rebuild with no changes takes 5s, and does not re-generate the mono glue, so that's working fine.)
The mono glue generation seems to take the Godot binary as its dependency, so whenever Godot changes (i.e. any non no-op compilation) will trigger a generation of the mono glue. The workflow contributors might currently be used to when working with the Mono module is that they first do the relevant engine changes (which might involve multiple incremental compilations until they get things to compile to what they want), and then do the next steps to test their changes.
That being said, 5s extra isn't terrible. Ideally it would only generate the glue when it's really needed, but I'm not sure what the dependencies should be for that.
Overall, I'd be in favor of enabling build_csharp by default, and leave it to power users to use build_csharp=no if they know they often want to do multiple compilations of the Godot binary before triggering a generation of the Mono glue (or in general, know that the changes they're doing would not impact the Mono glue and thus don't need to do this extra step at all while developing).

Ooops, totally missed your comments here @akien-mga, thanks for taking a look!

I make a change in code that doesn't impact the Mono glue and bindings, e.g. adding a comment to main/main.cpp. When building with scons module_mono_enabled=yes build_csharp=yes again, building sprite_2d.o and relinking the Godot binary is fast, but then the mono glue generation step still runs.

Ok, so, yes, I've gone through a couple of iterations on the bindings dependencies, and this version is setting the binary itself as a dependency of the bindings - this is because the list of files that contribute to bindings is not available to scons, it's a database that's built in to the binary itself, and so it is hard to accurately tell scons exactly what should trigger a rebuild. I'm not particularly happy with this, it's too trigger happy. I was experimenting with alternate ways of setting a dependency list, so I'll do some tweaks on this to make it less eager, I think.

Looks good to me from a very cursory overview, I'll do some more in depth review and testing hopefully tomorrow.

Works fine on my linux!👍

@akien-mga Ok, so, this new cleanup incorporates all the feedback, except for "if I touch something in an unrelated class, bindings will get regenerated". The command line flags can stop that from happening, but having scons accurately track that automatically is going to be a real pain, as I noted before. If we're ok with that and ok with addressing that later, this should be good to go.


Support jvmRoutes containing dashes (-)

From martin.grotzke on September 10, 2010 18:23:23
In the current version of msm a jvmRoute like "jvm-1" (containing a dash) will break some use cases of session failover, as the stripping of jvmRoute and detection of the memcached node id are conflicting then.
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=62

From martin.grotzke on September 10, 2010 09:27:53
Fixed, tests extended.
Status: Fixed

From<EMAIL_ADDRESS>on October 21, 2010 07:58:32
There is still a problem.  If the jvmRoute has a dash and there is no memcacheid it throws an exception.  A fix is enclosed.
Attachment: nomemcacheid.patch

From martin.grotzke on October 21, 2010 15:42:57
Patch applied, thanx!

From martin.grotzke on December 30, 2010 05:13:06
 Issue 69  has been merged into this issue.

From martin.grotzke on January 27, 2011 14:36:22
(No comment was entered for this change.)
Labels: Milestone-1.4.0


Feature/line

Current coverage is 88.01%

Merging #3 into master will decrease coverage by -11.99% as of 00caad3

@@            master      #3   diff @@
======================================
  Files            1      19    +18
  Stmts           10     367   +357
  Branches         3      42    +39
  Methods          0       0
======================================
+ Hit             10     323   +313
- Partial          0      15    +15
- Missed           0      29    +29

Review entire Coverage Diff as of 00caad3

Powered by Codecov. Updated on successful CI builds.


Run preGenCommand before checking the cache

The preGenCommand may generate files, change paths, etc. If we run this after checking the cache, it never gets the chance to run if the cache hasn't changed. Running it before checking the cache lets us make these changes and then we can check the cache to see if we need to regenerate or not.

@yonaskolb Hey, any chance of a review? This one is blocking us. Thanks!


Performance problems with the diff plugin

Hello I came across this plugin today.
Looks very promising but I have some problems once i integrate this plugin into my eslintrc. The linting process takes about 10-20 times longer with the plugin. I have configured everything according to the readme.
Even if I disable almost all rules it takes forever to complete. Without the plugin a linting process for the whole project takes about 20 seconds. Even if I only want to link one file with the plugin it takes over a minute.
I am using Windows 10 with nodejs v12.16.1. Let me know if I can provide more information.

I haven't tried running it, just skimmed the code. When eslint reports many messages for one file, is the plugin re-running git diff for each message? It should only need to run git diff and extract the line ranges once per file. (Or it could run git diff just once for all the files with messages, and parse the pathnames along with the line numbers.)

You are right, getDiffForFile is called once for each lint message. getDiffForFile itself spawns a child process.
https://github.com/paleite/eslint-plugin-diff/blob/2b66df4d8dc8e28cde801ba075fc9150369964fd/src/processors.ts#L17
Second thing to optimize would be to lint only files that have any changes. Currently all files are linted and the corresponding messages are removed.

Wow!
This has been on my todo-list since I first released this plugin, but I hadn't realized that it would make such a big difference in other OSes. I also didn't think of preprocessing the list and filtering out any files without diffs, so that was another great addition 🏆
I really appreciate you taking the time to report this and am even more grateful for your PR. I've looked through it and it looks very good. Great to see the updates to the tests as well!
I will merge and release a new version during the next day, so I hope you (and everyone else using this plugin) can benefit of the performance optimizations very soon.
🇩🇪 Bin dir sehr dankbar dass du dir so viel Mühe gegeben hast!

Released now: https://github.com/paleite/eslint-plugin-diff/releases/tag/v1.0.4
ping @DaVarga

Tanks mate 👍


getAddress not working for ZetaChain

When running getAddress("systemContract", "zeta_testnet") it fails with undefined, because addresses["zevm"]["zeta_testnet"]["systemContract"] doesn't exist.
https://github.com/zeta-chain/protocol-contracts/blob/61423b22f5d07487e4fd0690d87afa82b3a227ae/lib/address.tools.ts#L64-L70
https://github.com/zeta-chain/protocol-contracts/blob/61423b22f5d07487e4fd0690d87afa82b3a227ae/data/addresses.json#L52-L66

I suppose the fix is to change addresses.json to:
"zevm": {
  "zeta_testnet": {
    "systemContract": "0x91d18e54DAf4F677cB28167158d6dd21F6aB3921",
    "uniswapv2Factory": "0x9fd96203f7b22bCF72d9DCb40ff98302376cE09c",
    "uniswapv2Router02": "0x2ca7d64A7EFE2D62A725E2B35Cf7230D6677FfEe",
    "fungibleModule": "0x735b14BB79463307AAcBED86DAf3322B1e6226aB",
  }
   "goerli_testnet": {
    "zrc20": "0x13A0c5930C028511Dc02665E7285134B6d11A5f4"
  },
  "mumbai_testnet": {
    "zrc20": "0x48f80608B672DC30DC7e3dbBd0343c5F02C738Eb"
  },
  "bsc_testnet": {
    "zrc20": "0xd97B1de3619ed2c6BEb3860147E30cA8A7dC9891"
  }
}


Possible fix for intermittent failure in ConditionalAuthenticationTestCae.

Improvement for https://github.com/wso2/product-is/pull/11333.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/589879609

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/589879609
Status: failure


Unknown CMake command "caffe2_protobuf_generate_cpp_py"

I tried building caffe2 from the pytorch repo by the official instructions and got the following error.
If I do cmake .. in pytorch/caffe2 (and not in pytorch/caffe2/build), CMake seems to finish correctly
System information

Operating system: Ubuntu 16.04.4 x86_64
Compiler version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
CMake version: 3.5.1
CMake arguments: cmake ..
Relevant libraries/versions (e.g. CUDA):

CMake summary output
$ cmake ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at proto/CMakeLists.txt:3 (caffe2_protobuf_generate_cpp_py):
  Unknown CMake command "caffe2_protobuf_generate_cpp_py".

CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

    cmake_minimum_required(VERSION 3.5)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also "/home/masato/repo/pytorch/caffe2/build/CMakeFiles/CMakeOutput.log".

Which commit does the fix refer to?

https://github.com/caffe2/caffe2.github.io/commit/2fd74016a908324c9e5aee7f74b2f2fd68b227a1


Update manage-ddos-protection.md

@chboeh : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @chboeh - This PR was opened in the public repository. The contributor guide article Public vs. private repo guidance indicates that "content developers and core product team PMs should work in the private repositories so they can address quality feedback from the quality automation present in the private repos."
We’ll leave this PR for review in the public repo, but would you make future article updates in the private repo (azure-docs-pr)?
In the private repo, content benefits from automated validations, a content staging environment, and comprehensive PR reviews. Also, you can sign off directly in your PR (in the public repo, you can't sign off in your own PR), and many PRs qualify for auto-merge.
To edit an article in the private repo from within the documentation, after you select Edit on an article page,  add “-pr” to the repo name in the URL.

You might need to Join the MicrosoftDocs organization.
Thanks!

Related links in the internal Microsoft Docs contributor guide:
Public vs. private repos | Move a commit to a different repo (public -> private) | GitHub for content reviews
Quick reference for contributing to the docs | Make changes to a Docs article | PR review quality criteria

Ah,
Wasn’t aware of this but I’d be more than happy to do that in the future.

Chris Boehm
•(469) 775-4888
From: Kristine Toliver<EMAIL_ADDRESS>Sent: Monday, August 3, 2020 4:57 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Chris Boehm<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update manage-ddos-protection.md (#60194)
Hi @chboehhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fchboeh&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995977734&sdata=HMD6PM3VqlwE%2BdHpPCXZe%2Fg3EXaAjs2URId1trLiS1A%3D&reserved=0 - This PR was opened in the public repository. The contributor guide article Public vs. private repo guidancehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-authors-in-public-repo%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995977734&sdata=54GcDEu5lv2ONZ84JTQKUzLAbOscuFLmeSkgW67equk%3D&reserved=0 indicates that "content developers and core product team PMs should work in the private repositories so they can address quality feedback from the quality automation present in the private repos."
We’ll leave this PR for review in the public repo, but would you make future article updates in the private repo (azure-docs-pr)?
In the private repo, content benefits from automated validations, a content staging environment, and comprehensive PR reviews. Also, you can sign off directly in your PR (in the public repo, you can't sign off in your own PR), and many PRs qualify for auto-merge.
To edit an article in the private repo from within the documentation, after you select Edit on an article page, add “-pr” to the repo name in the URL.
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F19416435%2F88313501-7cf24880-ccc8-11ea-9f03-4e4d4a2f8288.png&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995987725&sdata=s4wAm6O3y7TDwSzKn4%2FYZsVmyUxGEgt5D5ofFBSLhVg%3D&reserved=0
You might need to Join the MicrosoftDocs organizationhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-get-started-setup-github%3Fbranch%3Dmaster%23join-microsoftdocs-organization-and-others&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995987725&sdata=Rcn1wVLEqc1e%2B2J4llsTLkdNTqfrEgbN2kgSIIRNB3U%3D&reserved=0.
Thanks!

Related links in the internal Microsoft Docs contributor guidehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2F%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995997721&sdata=J5yBK%2Bz8Tt8qDzvIftaWPkSr6AGQhgQkqE5EG1DQLDY%3D&reserved=0:
Public vs. private reposhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-authors-in-public-repo%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849995997721&sdata=kd%2B3Tf9flpMl6NXrhG%2BY8xqO10PNyNjaRsXqfcPDhSM%3D&reserved=0 | Move a commit to a different repo (public -> private)https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-how-to-manage-act-guidelines-public-pr%3Fbranch%3Dmaster%23pull-public-commits-to-the-private-repo-for-updates-staging-publication&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996007713&sdata=Qr5D%2F69Za6rozMDSHNYV8RsGSfxZwfQb%2FRKvrERAF6k%3D&reserved=0 | GitHub for content reviewshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-how-to-write-pull-request-reviews%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996007713&sdata=jpjLf45FmjvQ0nbOAczfqTH5GLf5dOKqwprYJL%2BSDz4%3D&reserved=0
Quick reference for contributing to the docshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-quick-reference%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996017711&sdata=EFEoScO7wwx%2B0BUrjLiOqB9RcXUCDiChPY%2FutrO64A8%3D&reserved=0 | Make changes to a Docs articlehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fedit-doc-with-vs-code-and-git-cli%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996017711&sdata=3%2F860OamSjIbkDFbxEc3nSEZjoN0QAquaF%2BuFX%2B8cHg%3D&reserved=0 | PR review quality criteriahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fhelp%2Fcontribute%2Fcontribute-how-to-write-pull-request-quality-criteria%3Fbranch%3Dmaster&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996027703&sdata=84suYS50ikSPCdFRcN8k%2B1pxCGvO2nj%2F3PwJdy2K7HU%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F60194%23issuecomment-668237426&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996027703&sdata=3MLajiy23DCT3LmC4oi98UUAUDF%2F0l3QRkF2g7CYDdI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALISVOGSITVQSAJPHPTPC6TR64QALANCNFSM4PTVLJ6A&data=02|01|Chris.Boehm%40microsoft.com|da9e909ce4984283e54008d837efb6e3|72f988bf86f141af91ab2d7cd011db47|1|0|637320849996037691&sdata=y03w0Os4vdweocic%2FJKZOuAS4gVuRNyqq8Jm1JWg9QE%3D&reserved=0.

#sign-off


--reload incompatible with app producing .png images

Hi,
I have a shiny app that produce a png image, and store it in a www folder which is in the same directory as app.py. I save the image in this folder so it can be proposed to the user.
Since https://github.com/posit-dev/py-shiny/commit/77acfddfe146093f64104af0a5cfb306d0ec7207#diff-f36a8a68557ee7f4ba2d8f2471169963fea3b6483a8c2ae053cfda01fac768c0R275 png are watched and trigger a restart of the process. As my app produce this file, it is killed at the moment it starts producing the file...
A very simple solution would be to stop watching for png files, otherwise could you make it possible to override the extension list with an arg such as --reload-includes "py,css,foo,bar".

Thanks for the feedback, @bryan-brancotte. Leaving this here for later: https://github.com/posit-dev/py-shiny/blob/18c270dfbf905bb709edc1321966a6b54f7568c9/shiny/_main.py#L276

We just added a reload_includes argument for shiny run you should be able to use that in the dev release.


Unique COMP6 GDB molecule IDs

Tiny fix.
The molecule ids were not unique without the name of the file (they are repeated in different files of the same dataset) and it was causing issues in the evaluation when calculating relative conformer energies.

Thanks!


When using Authenticator, the "Authorization" header is not logged by the HttpLoggingInterceptor

When using an Authenticator to set the "Authorization" header, the header is not logged by the HttpLoggingInterceptor. I receive a 200 response, so the token is definitely there and is correct (when I remove the authorization completely, I receive a 401).
However when I use an Interceptor to set the "Authorization" header, the header is logged correctly.
The following doesn't log the "Authorization" header:
class AccessTokenAuthenticator(
    private val tokenRepository: TokenRepository
) : Authenticator {

    override fun authenticate(route: Route?, response: Response): Request? {
        val token = runBlocking { tokenRepository.provideAccessToken() } ?: return null
        return response.request.newBuilder()
            .header("Authorization", "Bearer $token")
            .build()
    }
}

val httpLogger = HttpLoggingInterceptor.Logger { Timber.tag("API").log(Log.DEBUG, it) }

val okHttpClient = OkHttpClient.Builder()
    .authenticator(AccessTokenAuthenticator(tokenRepository))
    .addInterceptor(HttpLoggingInterceptor(httpLogger).apply { level = BODY })
    .build()

The log output is the following:
--> GET https://backend.com/v1/systems/1234/
--> END GET
<-- 200 https://backend.com/v1/systems/1234/

On the other hand, using an Interceptor instead logs the "Authorization" header correctly:
class AccessTokenInterceptor(
    private val tokenRepository: TokenRepository
) : Interceptor {

    override fun intercept(chain: Chain): Response {
        val token = runBlocking { tokenRepository.provideAccessToken() }
        val request = chain.request().newBuilder().apply {
            if (token != null) header("Authorization", "Bearer $token")
        }.build()

        return chain.proceed(request)
    }
}

val httpLogger = HttpLoggingInterceptor.Logger { Timber.tag("API").log(Log.DEBUG, it) }

val okHttpClient = OkHttpClient.Builder()
    .addInterceptor(AccessTokenInterceptor(tokenRepository))
    .addInterceptor(HttpLoggingInterceptor(httpLogger).apply { level = BODY })
    .build()

The log output is the following:
--> GET https://backend.com/v1/systems/1234/
Authorization: Bearer my_token_here
--> END GET
<-- 200 https://backend.com/v1/systems/1234/

If you want to see all headers that go across the wire, you should use a addNetworkInterceptor.
See https://square.github.io/okhttp/features/interceptors/#choosing-between-application-and-network-interceptors

Thanks for the quick and helpful answer!
Is there a specific reason that the header is logged when it is added by an Interceptor anyway even when adding logging at the application layer only (addInterceptor(HttpLoggingInterceptor())?

Interceptors are a chain and an interceptor can see all changes done by ones which occur previous to it in the list. Please see the diagram here: https://square.github.io/okhttp/features/interceptors/. An authenticator is called as part of the core which is why a network interceptor will see its effects.


MID0150 create correct package depending on size of identifier

For me  default solution didnt work with a Dessoutter Controller so i had to adjust the package .
Also i modify the the tests.
If you think is ok please add it .

Does it applies only to Dessoutter Tightening controllers or is it for everyone?
If it's only for Dessoutter, I might break other communications.

if you have a look in your provided example for test "00470150001         My identifier less than 100"
the package had length 47 but if you create you the mid with the current mid you get maximum length all the time.
Maybe was an error when you construct the package with full size message .
Identifier data 21-max 120 Max 100 ASCII characters
Could be also a bug in documentation when you send max length message .
My approach actually follow the protocol rule to calculate the correct size of the package every time so should not be any problem with other controllers.

Desoutter controllers are based on atlas copco open protocol docu. They just add some additional mids.
If you need i will add the document to the docu section

@xGusu, just reviewed here, it's fine!
I would just ask a favor, please add the documentation into docs folder, maybe it could help other people too, since the documentations are usually rare to find (even AtlasCopco).

@xGusu, thank you for contributing, I'm going to create a release when possible.


skipCertCheck: false

Hello Guys,
We have faced with a problem regarding docker registry certificate.
Our setup is the Dynatrace cluster (as well as it docker registry) is protected with self-sign CA (internal CA).
The skipCertCheck flag is affecting only the dynatrace server and not affecting with docker registry (sometimes called insecure registry).
We cannot  (and we dont want to) modify your docker image and there is no way to get this activegate image (oneagent images can be pulled from dockerhub, or from openshift).
Workaround is to manually pulled from dynatrace registry and push to another private docker registry which is not protected with internalCA issued certificate.
Another workaround to use managed dynatrace dns but imho this is not a good solution.
Please extend your image to be able to use "insecure" (internal CA issued tls protected) registry.
Thanks in advance.
Viktor

Hi, you have the possibility to add a trusted Certificate via trustedCAs: name-of-my-ca-configmap in the CR.yaml. The certificate has to be available in a config map in the namespace of the Operator. If there are anymore questions, feel free to open a issue.

Yes, Ive tried it for sure. Ive made configmap and data contains certs: | CERTIFICATES. But I  have same error.


Passing extra args to the objective function

Is there a way to pass in extra arguments to the objective function like we have in scipy with the keyword argument args?

Hi @richinex
For simplicity of the source code I chose to leave this out because the same behavior is easily obtained using lambda functions and/or functools.partial.
For example
minimize(func, x0, args=(3,))

is equivalent to
minimize(lambda x: func(x, 3), x0)

Ah yes I got it. Gracias.


Google Operators don't support all authentication parameters

Describe the bug
The following implementation of Google operators ignore authentication parameters delegate_to and impersonation_chain. These parameters are supported by their sync counterparts as it is documented (where applicable).

BigQueryInsertJobOperatorAsync
BigQueryGetDataOperatorAsync
BigQueryIntervalCheckOperatorAsync
DataprocCreateClusterOperatorAsync
DataprocDeleteClusterOperatorAsync
DataprocSubmitJobOperatorAsync
DataprocUpdateClusterOperatorAsync

It is important that those parameters are respected when loading the hook during the synchronous execute call as well as in the corresponding defer call to the trigger (and thus in the trigger as well).
To Reproduce
Using impersonation_chain with BigQueryInsertJobOperatorAsync will result in the task using the identity provided by the credentials of the GCP connection.
Expected behaviour
It should use the identity as defined in impersonation_chain.

Thank you @m1racoli for creating the issue!

Thanks! I am not sure I managed to discover all cases. My findings are based on the search for :param impersonation_chain: in the doc string. The BigQuery and GCS sensors as well as the GKEStartPodOperatorAsync seem to support these parameters already.


What is the version of pytorch and python?

Hi,
Which version of pytorch and python did you use for the implementation?

PyTorch - 1.13.0
Python - 3.10.9


Tooltip on disabled buttons with span do not work in Safari

As described at https://material-ui.com/components/tooltips/#disabled-elements, you have to wrap a disabled button in a span and set pointerEvents to none. This causes the tooltip to never show in Safari.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
https://codesandbox.io/s/material-demo-9h7of
The tooptip does not show in Safari 13.0.2

Expected Behavior 🤔
The tooptip should be shown.
Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-9h7of
Steps:

Hover button

Context 🔦
Tooltips on disabled buttons can be useful to give more information.
Your Environment 🌎
CodeSandbox from the docs, slightly edited the code to show the bug.

Tech
Version

Material-UI
v4.5.1

React
16.11.0

Browser
Safari 13.0.2

@EvertEt Do you have any idea what's going on, I don't? Does https://material-ui.com/components/tooltips/#disabled-elements work for you?

It does work but it has extra weird behaviour:

Chrome: The Source (<>) button changes color
Safari: The Source (<>) button changes color AND also shows its popup when hovering the button.

It does work but it has extra weird behaviour:

Chrome: The Source (<>) button changes color
Safari: The Source (<>) button changes color AND also shows its popup when hovering the button.

We only show the tooltip if you never clicked open. We don't track this across browsers though (hopefully nobody could).

Aha, didn't know that functionality! Than the weird thing is that a normal button does not work but the Button does. Maybe some extra behaviour in ButtonBase?

@EvertEt Ok, I could track the case, at first, I was very puzzled. There is no difference between the <button> and <Button>. In order to work with Safari, you need at least one display block or flex item below the tooltip wrapper.

I think that we should update the documentation about the limitation.

Setting the span to "inline-block" worked for me.

@lgibso34 That worked for me too.


Unable to compile with Version 11.4.1

Describe the bug
After you run flutter run --flavor development the code does not complete with the following errors:
Compiler message:
lib/main.dart:304:7: Error: No named parameter with the name 'onError'.
      onError: (error, stackTrace) async {
      ^^^^^^^
org-dartlang-sdk:///third_party/dart/sdk/lib/_http/overrides.dart:65:12:
Context: Found this candidate, but the arguments don't match.
  static R runWithHttpOverrides<R>(R body(), HttpOverrides overrides) {
           ^^^^^^^^^^^^^^^^^^^^
lib/widgets/video_player/widgets/chewie/chewie_player.dart:133:31: Error: No
named parameter with the name 'isInitialRoute'.
      settings: RouteSettings(isInitialRoute: false),
                              ^^^^^^^^^^^^^^
../flutter/packages/flutter/lib/src/widgets/navigator.dart:458:9: Context: Found
this candidate, but the arguments don't match.
  const RouteSettings({
        ^^^^^^^^^^^^^
../flutter/.pub-cache/hosted/pub.dartlang.org/flutter_svg-0.14.4/lib/src/picture
_stream.dart:92:3: Error: The superclass, 'Diagnosticable', has no unnamed
constructor that takes no arguments.
  PictureStream();
  ^^^^^^^^^^^^^
Running Xcode build...
../flutter/.pub-cache/hosted/pub.dartlang.org/flutter_svg-0.14.4/lib/src/picture
_stream.dart:192:16: Error: The superclass, 'Diagnosticable', has no unnamed
constructor that takes no arguments.
abstract class PictureStreamCompleter extends Diagnosticable {

To Reproduce
Steps to reproduce the behavior:

Clone the repository into your Mac Using Xcode 11.4.1
Run flutter run --flavor development

Expected behavior
The application should compile and install on the connected device or simulator
Desktop (please complete the following information):

OS: macOS Catalina 10.15.4

Smartphone (please complete the following information):

Device: IphoneXs
OS:13.4.1

Try changing flutter to use the master channel by running:
flutter channel master
flutter upgrade

Hi Komposten,
Thanks for the quick update I've tried that as well but complains on the same issue.
For reference here is the flutter version:
Flutter 1.19.0-1.0.pre.29 • channel master • https://github.com/flutter/flutter.git
Framework • revision 0177d4293c (2 hours ago) • 2020-05-11 09:41:38 -0700
Engine • revision d96f962ca2
Tools • Dart 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)
One thing to note also is that the flutter_svg I can fix by updating the pubspec file with the latest version.
However no matter what I do I cannot get past the chewie errors

Try changing flutter to use the master channel by running:
flutter channel master
flutter upgrade

(You might also need to be on the develop branch in okuna-app; I don't know which flutter version the master branch uses.)

We you a beer! develop branch did it, wondering if the master readme should be updated with  the master branch flutter version. :)


Translation to Portuguese (Brazilian)

A friend did the translation. Can you add it? Thanks!

I cannot read Portuguese (Brazilian), but the json file at a cursory glance looks like it's in a good shape. I'll merge it, thanks! :-)


Error installing SWR with nextjs

Bug report
Description / Observed Behavior
While installing swr using npm install swr, i get this error
Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/swr
npm ERR!   swr@"*" from the root project

Expected Behavior
Install should be successful
Repro Steps / Code Example
npm i swr
Or share your code snippet or a CodeSandbox link is also appreciated!
Additional Context
SWR version.
Add any other context about the problem here.

This is related to https://github.com/vercel/swr/issues/3028

I'm also experiencing this.
Repro:

npx create-next-app@latest
npm i swr
Error message below:

    ~/repos/nextjs-03  on   main  npm i swr                                                                                1 ✘  at 19:52:30 
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/react
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0" from<EMAIL_ADDRESS>npm error node_modules/swr
npm error   swr@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/xyz/.npm/_logs/2024-12-02T18_55_03_571Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/xyz/.npm/_logs/2024-12-02T18_55_03_571Z-debug-0.log

Yes it is. #3028 (comment) this would solve the issue.

Thanks but I would rather wait until the proper fix.

Good idea, you can just go with --legacy-peer-deps

We've just released v2.3.0, which supports React 19, so I think this issue would be fixed.
https://github.com/vercel/swr/releases/tag/v2.3.0

Thank you!! Will test it out.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Toru Kobayashi @.>
Sent: Monday, December 23, 2024 8:41:02 AM
To: vercel/swr @.>
Cc: Temitope Elodimuor @.>; Author @.>
Subject: Re: [vercel/swr] Error installing SWR with nextjs (Issue #3043)
CAUTION - EXTERNAL EMAIL This e-mail has originated from outside of the organization. Do not respond, click on links, or open attachments unless you recognize the sender or know the content is safe.
We've just released v2.3.0, which supports React 19, so I think this issue would be fixed.
https://github.com/vercel/swr/releases/tag/v2.3.0
—
Reply to this email directly, view it on GitHubhttps://github.com/vercel/swr/issues/3043#issuecomment-2559923773, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BINC6S4D6BTIYTQQ2B5OF532HAVI5AVCNFSM6AAAAABSJHU37KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZHEZDGNZXGM.
You are receiving this because you authored the thread.Message ID: @.***>


Impossible to specify a subfolder

The tool azuredevops-export-wiki.exe allow to the user to export as a PDF all the repo or a part of the repo.
I tried to export only a part of the repo with the following command line and it works :

But with the azure devop extension, it's only possible to export the whole wiki. So, according to me, a new field is required with the path of the folder to export in the wiki (if empty that means all the wiki, and if a folder is specified only this folder).
Normally it's easy to implement because you have only to concatenate the folder name to the path (-o path/folder)

normally I would have sent you to the extension author - but he has sent you to me... :)
So, I briefly tested the extension with my test wiki and I can provide the same parameters and the export worked for a subfolder:

"AzureDevOps.WikiPDFExport" is a subfolder of my wiki that I wanted to export and I can provide that in the second "Local Folder" field of the extension task. This is then converted to the -p flag of the converter.
Does that help?

normally I would have sent you to the extension author - but he has sent you to me... :)
So, I briefly tested the extension with my test wiki and I can provide the same parameters and the export worked for a subfolder:

"AzureDevOps.WikiPDFExport" is a subfolder of my wiki that I wanted to export and I can provide that in the second "Local Folder" field of the extension task. This is then converted to the -p flag of the converter.
Does that help?


Issue in finetuning on new dataset

Hi,
I tried to finetune the model using the G_500000.pt checkpoint provided in the repro with a new Discriminator made from scratch (no pretrained checkpoint used for the Discriminator). I used a German dataset which contains voiced and unvoiced audio recordings and I converted them to a new Voice (with FreeVC) to make the model more robust on real world scenarios. The audio recordings are all Resampled to 16kHz.
Now my Problem: When testing the conversion with the pretrained model it converts my audios quite good (results could be better on the distorted examples but where ok) But when I use the finetuned model with the new Voice, the converted audio examples have lost a lot of Gain/Signal to Noise Ratio. When listening to the files you cannot hear anything. When plotting the results you can see a Waveform but the amplitude goes only up to 0.2*10^-5 which is way less than when using the pretrained model without finetuning (here the converted examples had an amplitude ranche of -0.5 to 0.5). Then I tried to normalise the audio to be between -1 to 1, they started sounding really really noisy (no voice can be identified). I tested checkpoints I made from 10000 steps to 100000 steps and there was no improvement. (all had the same problem) I trained for around 150 Epochs or 100000 steps with my data. (around 10 hours training I guess)
Also when I am not using the pretrained G_500000.pt checkpoint and instead train the generator from scratch it has this low SNR problem. Is there maybe a reason/problem known why the outputs are so low in SNR? Can I try something to improve the results? Or is some special preprocessing made with your dataset which I havent done? I used a sampling rate of 16kHz for the original and I used FreeVC to make my 16kHz converted examples in the new voice (all recordings from my dataset are sounding fine when listening to them). The fileformat of my recordings is .wav.
thanks for your help and great work!

Hi,
I tried to finetune the model using the G_500000.pt checkpoint provided in the repro with a new Discriminator made from scratch (no pretrained checkpoint used for the Discriminator). I used a German dataset which contains voiced and unvoiced audio recordings and I converted them to a new Voice (with FreeVC) to make the model more robust on real world scenarios. The audio recordings are all Resampled to 16kHz.
Now my Problem: When testing the conversion with the pretrained model it converts my audios quite good (results could be better on the distorted examples but where ok) But when I use the finetuned model with the new Voice, the converted audio examples have lost a lot of Gain/Signal to Noise Ratio. When listening to the files you cannot hear anything. When plotting the results you can see a Waveform but the amplitude goes only up to 0.2*10^-5 which is way less than when using the pretrained model without finetuning (here the converted examples had an amplitude ranche of -0.5 to 0.5). Then I tried to normalise the audio to be between -1 to 1, they started sounding really really noisy (no voice can be identified). I tested checkpoints I made from 10000 steps to 100000 steps and there was no improvement. (all had the same problem) I trained for around 150 Epochs or 100000 steps with my data. (around 10 hours training I guess) Also when I am not using the pretrained G_500000.pt checkpoint and instead train the generator from scratch it has this low SNR problem. Is there maybe a reason/problem known why the outputs are so low in SNR? Can I try something to improve the results? Or is some special preprocessing made with your dataset which I havent done? I used a sampling rate of 16kHz for the original and I used FreeVC to make my 16kHz converted examples in the new voice (all recordings from my dataset are sounding fine when listening to them). The fileformat of my recordings is .wav.
thanks for your help and great work!

When I used my own trained RVC single speaker model to convert the train-360 data into paired data to train llvc model from scratch, the loss did not converge at all. After about 55k steps, the loss directly soared to nan. then it was always nan，Have you encountered similar problems?
train.log


clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

Error in ClashLeaders
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56
Too many requests when fetching clan [#PYPULRL0].
View on Bugsnag
Stacktrace
clashleaders/clash/api.py:56 - find_clan_by_tag
clashleaders/model/clan.py:60 - fetch_and_save
clashleaders/model/clan_pre_calculated.py:202 - fetch_and_update_calculations
clashleaders/worker.py:48 - update_single_clan

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /search.json

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

An error linked to this issue has been marked as fixed in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56

An error linked to this issue has been marked as fixed in Bugsnag
clashleaders.clash.api.TooManyRequests in clashleaders/clash/api.py:56


Add post_id for FileInfo type

Summary
Add post_id for FileInfo type

Skipping QA because is clearly not needed (I only changing the a type, so if it compiles, there's nothing else to check).


[Question]  大佬,我刚才提出那个ImportError问题,怎么删掉了?

A clear and concise description of what you want to know.

麻烦按照 issue 模板重新提交 issue，否则没办法处理。
另外，没有删除，关闭了，不符合规范。
#111

我仔细看了一下包的路径,应该是from keras_transformer.transformer import *

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[ ] I have searched in existing issues but did not find the same one.

Environment

OS [e.g. Mac OS, Linux]:
requirements.txt:

[Paste requirements.txt file here]

Issue Description
What
[Tell us about the issue]
Reproduce
[The steps to reproduce this issue. What is the URL you were trying to play, where did you put your code, etc.]
Other Comment
[Add anything else here]

好吧! 格式是很重要


Update readme to include content type in case content type validation…

If you try to upload a file with the current curl statement, chances are you'll get an error since the latest grape encourages you to enable validation, and one would assume that most will use content type validation.

thx


Port array min/max to simple function interface

For primitives benchmarking shows that we are close enough perf wise (16% slower)
with some planned tasks to match the performance.
One thing to note is that the new udf interface was not friendly for this case so I used the
old one. The new interface requires explicit creation of 18 partially instantiated aliases before
registration.
I tried to use member struct alias to avoid that but c++ does not template deduction when the
argument is member alias. i.e.
registerFunction< X<..>::type, ..>(); // not allowed.
The string varient can use the 0-copy optimizations once the current work on it is done.

address comments
and make the registration function variadic.

use UDFOutputString::assign() instead of memcpy since results string can potentially be empty.

UDFOutputString::assign() did not work, guard memcpy with size !=0


Feature request: custom icons for mat-datetimepicker-toggle

Modules versions:
"@angular/material": "9.2.1",
"@mat-datetimepicker/core": "5.1.1",
"@mat-datetimepicker/moment": "5.1.1"
Trying to do custom icon similar to original mat-datepicker:
<mat-datetimepicker-toggle [for]="datetimePicker" matSuffix>

</mat-datetimepicker-toggle>
But this didn't work. Can you provide this feature, or can we set custom calendar toggle icon in some other way?

you are welcome to open a pull request .. unfortunately i don't have time myself at the moment..

Done this by delete mat-datepicker-toggle from template and add

after mat-datetimepicker, inside mat-form-field.


fix(header): Remove unnecessary VerifyCommitLightTrusting, use light.VerifyAdjacent

This PR reworks header.Verify such that non-adjacent headers do not need to pass VerifyCommitLightTrusting in order to pass verification as the Syncer in go-header performs sequential verification anyway on all headers synced from genesis -> syncTarget.
This PR also introduces light.VerifyAdjacent method to the verification logic for adjacent headers as it is audited.

This PR is blocked on a test in go-header that will confirm the Syncer is able to discard an invalid sync target and wait for a valid one to sync the canonical chain


[Network] private link add Microsoft.ServiceBus/namespaces provider

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network

/azp run


shiffman.net redirect to thecodingtrain.com not working with https protocol

Adding it here so there's more visibility. I feel like we've discussed this on Discord before but it hasn't been corrected.
Maybe related https://github.com/shiffman/shiffman.net/pull/131
The http:// redirection works, but with https:// is just a generic Squarespace landing page.
Because of the HSTS response header, it's easy to get in a state were we can never really go back to http:// without manually purging the HSTS policy for the domain in the browser. Modern browsers also have an HTTPS-only mode available and would never land on the non-secure version of the URL to begin with.
I don't know how the current implementation works, but can this not simply be handled by their domain forwarding service? https://support.squarespace.com/hc/en-us/articles/214767107-Forwarding-a-Squarespace-domain
As an alternative, you could just point the DNS to a Netlify or Cloudflare account and handle the redirection logic there instead.

I've updated the Squarespace settings so this domain forwarding should be fixed in 24-72 hours. Will revisit and close when ready!

Looks fixed, we can close this!


Created a GoLang file to get square of any input

Closes #48
What's being changed: Added a GoLang file to get square of any input

A couple of things:

please go to the issue #48 and type !assign there, so the bot can assign you to the issue
the file name is not following the naming convention. Please refer to how to contribute in the issue

Thank you for contributing!

updated


:sparkles: Migration enhancement

Summary

remove the backup secret since the -current-hub bookstrap secret can be added by default
retry for conflict error
wait for 10 seconds to ensure klusterletconfig is applied and then update hubAcceptClient to false to trigger the migration (TODO: there is condition indicates the klusterletconfig is applied)
remove the managed cluster when the cluster hubAcceptClient is false

Related issue(s)
Fixes # https://issues.redhat.com/browse/ACM-15220
Tests

[ ] Unit/function tests have been added and incorporated into make unit-tests.
[ ] Integration tests have been added and incorporated into make integration-test.
[ ] E2E tests have been added and incorporated into make e2e-test-all.
[x] List other manual tests you have done.

verified in local environment

/lgtm


Fix setup

closes #89

Coverage remained the same at 91.304% when pulling 1316669e9391dee30b7e38e7d60800e83554ede9 on jasmainak:fix_setup into a302efb1ea3eee385616d288c9f445d0418fa93a on pavanramkumar:master.


Add async iterator blog

I'll continue to noodle on this (generally cleaning things up, adding more realistic samples, and trimming content where I can), but getting this out there for feedback!

Ok I think I addressed all your feedback @adrianhall. If you can, another look would be great, and I can make any minor tweaks on monday!


PortalJS Website v0.2

Update current portaljs.org website which is run out of site folder.
Acceptance

[x] #748
[x] #754
[x] #771
[x] #765

FIXED, we now have a new website running here https://portaljs.org/


not listening on rfc4193 address on macos

Hmm,
for me at the moment, it should be listening on a v4 and v6 address, but it's not listening on v6. 🤔
Mar 16 16:22:10.282  INFO zeronsd::init: Welcome to ZeroNS!
Mar 16 16:22:10.792  INFO zeronsd::init: Your IP for this network: fd15:9924:d630:f690:3d99:93e7:50c5:1646
Mar 16 16:22:10.792  INFO zeronsd::init: Your IP for this network: <IP_ADDRESS>

lsof is strange on mac
here's a command that shows something like the right output
sudo lsof -aP -iUDP  | grep zeronsd
zeronsd   20631           root   12u  IPv4 0x6caae65784840593      0t0  UDP <IP_ADDRESS>:53

if i start it without rfc4193 enabled, it still works on ipv4. not sure if related to #199

Sure it's not firewall?
------- Original Message -------
On Thursday, March 16th, 2023 at 4:31 PM, Travis LaDuke @.***> wrote:

Hmm,
for me at the moment, it should be listening on a v4 and v6 address, but it's not listening on v6. 🤔
Mar 16 16:22:10.282  INFO zeronsd::init: Welcome to ZeroNS!
Mar 16 16:22:10.792  INFO zeronsd::init: Your IP for this network: fd15:9924:d630:f690:3d99:93e7:50c5:1646
Mar 16 16:22:10.792  INFO zeronsd::init: Your IP for this network: <IP_ADDRESS>
lsof is strange on mac
here's a command that shows something like the right output
sudo lsof -aP -iUDP  | grep zeronsd
zeronsd   20631           root   12u  IPv4 0x6caae65784840593      0t0  UDP <IP_ADDRESS>:53
if i start it without rfc4193 enabled, it still works on ipv4. not sure if related to #199
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

pertty sure. I can bind nc on a zerotier interface on 53/udp and then talk to it.

hmm ok. I can look at this over the weekend I suppose if you'd like that.
------- Original Message -------
On Friday, March 17th, 2023 at 8:08 AM, Travis LaDuke @.***> wrote:

pertty sure. I can bind nc on a zerotier interface on 53/udp and then talk to it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Are you sure the IP has been bound to the interface and was stable? I know you probably did, but just to be thorough I thought I'd ask.
I have a mac here, I can look into it.
------- Original Message -------
On Friday, March 17th, 2023 at 9:55 AM, Travis LaDuke @.***> wrote:

Thanks! I don't think this is hurting many users. So no worries.
It works sometimes but not others! Most often not.
It's failing at TcpListener::bind(sa).await?
error Os { code: 49, kind: AddrNotAvailable, message: "Can't assign requested address" } - fd15:9924:d630:f690:3d99:93e7:50c5:1646
That's fun.
200 listnetworks 159924d630f6903d lonely_szpakowski 3e:77:a6:f5:c0:62 OK PRIVATE feth3122 fd15:9924:d630:f690:3d99:93e7:50c5:1646/88,<IP_ADDRESS>/16
ifconfig feth3122
feth3122: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 5000 mtu 2800
ether 3e:77:a6:f5:c0:62
inet <IP_ADDRESS> netmask 0xffff0000 broadcast <IP_ADDRESS>
inet6 fe80::3c77:a6ff:fef5:c062%feth3122 prefixlen 64 scopeid 0x15c
inet6 fd15:9924:d630:f690:3d99:93e7:50c5:1646 prefixlen 88
peer: feth8122
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
it could just be that macos is bad
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

try multiple times! this is on main btw.
yeah. this isn't via the tests. using the actual app. so the address has be up and running for a long time, i can ping it, zeronsd does work on it sometimes.

Hmm. Ok, I will attempt to look into it this weekend. A lot is going on, so I apologize in advance if I space this.
------- Original Message -------
On Friday, March 17th, 2023 at 10:40 AM, Travis LaDuke @.***> wrote:

try multiple times! this is on main btw.
yeah. this isn't via the tests. using the actual app. so the address has be up and running for a long time, i can ping it, zeronsd does work on it sometimes.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Convert TODO items to github issues

Similarly to https://github.com/perl6/doc/issues/657.
See https://github.com/perl6/doc/blob/master/TODO

https://github.com/perl6/doc/issues/715, https://github.com/perl6/doc/issues/716, https://github.com/perl6/doc/issues/717, https://github.com/perl6/doc/issues/718 - does it all or "Maybes" should be opened?

I think that it does not hurt to open maybes too.

Closed with https://github.com/perl6/doc/issues/720, https://github.com/perl6/doc/issues/721, https://github.com/perl6/doc/issues/722


Reproduce Cross-lingual Language Model Pretraining with BERT

Reference: https://arxiv.org/pdf/1901.07291.pdf

https://github.com/facebookresearch/XLM


timeline name repeats the first seven characters

https://github.com/jonasmr/microprofile/blob/80f66cdd0db6e4f999141fac7983ae9cef0ff52e/microprofile.cpp#L4554
So v here should be v2, right?


Allow status to be passed to sync?

Would it make sense to allow status to be passed to sync?  I find myself wanting to perform a sync operation but only on missing projects.
The problem I run into is having private repo dependencies.  The private repos may not always be checked in (we pass then into our build server, Concourse CI, to run an isolated build to make sure things will work when pushed).  I managed to get close but find myself stalled:

Container is initialized with empty GOPATH
Private dependencies are copied to the GOPATH
govendor update +e copies the private repos into /vendor
govendor list will show all the other dependencies missing; as expected
Here I would like to be able to run govendor sync +missing to have it sync all missing repos at the specified versions into the /vendor folder.

Does this sound like a reasonable request?  Or is the an order of operations that I'm just not seeing that could make this work?
Thanks

govendor sync will only operate on missing or outdated packages already by using a checksum hash.
In other words, it should do what you want already without any additional flags.

Strange.  I'll re-confirm what I was running into and post a follow up.


LMS4xxx switch from Software to Free Running

I am trying to send  a ros2 service call to switch the laser into Software mode without using the sopas.
I was looking at the documentation

and I tried to send the following command
ros2 service call /scan3/ColaMsg sick_scan/srv/ColaMsgSrv "{request: 'sWN IOlasc 1 +500 0 0 0'}"

resulting in this error:
[WARN] [1690796155.255845658] [sick_scan]: Error Sopas answer mismatch: Error unexpected Sopas answer for request <STX><STX><STX><STX><Len=0023>sWN IOlasc 0x01 0x20 0x2b 0x05 0x0..., received answer: "sFA\x00\x0a", expected patterns: "sWA IOlasc","sAN IOlasc"

I think the issue might be related to the fact that I need to use binary code. However I tried
ros2 service call /scan3/ColaMsg sick_scan/srv/ColaMsgSrv "{request: '02 02 02 02 00 00 00 16 73 57 4E 20 49 4F 6C 61 73 63 20 01 01 F4 00 00 00 00 00 00 00 20 A5'}"

and it is not working either.
The thing that is strange is that I am using the following command without any issue, to start and stop the laser.
ros2 service call /scan3/ColaMsg sick_scan/srv/ColaMsgSrv "{request: 'LMCstartmeas}"
ros2 service call /scan3/ColaMsg sick_scan/srv/ColaMsgSrv "{request: 'LMCstandby'}"

Do u  have any idea what is wrong?
This is the launch file that I am currently using.
<?xml version="1.0"?>
<!--
     **********************************************
     Launch File for LMS 4xxx scanner
     **********************************************
     Start and stop angle is given in [rad]

     Default min_angle is  -35 degree.
     Default max_angle is +35 degree.

     SOPAS angles in lidar coordinates: min_angle = 55 deg, max_angle = 125 deg, delta = 125-55 = 70 deg
     Angle offset -90 degree: (55-90 = -35 deg, 125-90 = +35 deg)
     Angle configuration in ROS coordinates: min_angle = -35 deg, max_angle = +35 deg, delta = 70 deg

     Check IP-address, if you scanner is not found after roslaunch.
-->

<!-- You can launch a LMS_4xxx-scanner on a specific ip address (e.g. <IP_ADDRESS>) using the following example call:

     roslaunch sick_scan sick_lms_4xxx.launch hostname:=<IP_ADDRESS>

-->
<!-- Using node option required="true" will close roslaunch after node exits -->

<launch>
    <arg name="hostname" default="<IP_ADDRESS>"/>
    <arg name="cloud_topic" default="cloud"/>
    <arg name="frame_id" default="L3"/>
    <node name="sick_lms_4xxx" pkg="sick_scan" type="sick_generic_caller" respawn="false" output="screen" required="true">

        <!-- default values: -->
        <!--
          <param name="scanner_type" type="string" value="sick_tim_5xx" />
          <param name="min_ang" type="double" value="-2.35619449" />
          <param name="max_ang" type="double" value="2.35619449" />
          <param name="intensity" type="bool" value="True" />
          <param name="skip" type="int" value="0" />
          <param name="time_offset" type="double" value="-0.001" />
          <param name="publish_datagram" type="bool" value="False" />
          <param name="subscribe_datagram" type="bool" value="false" />
          <param name="device_number" type="int" value="0" />
          <param name="range_min" type="double" value="0.05" />
        -->
        <param name="scanner_type" type="string" value="sick_lms_4xxx"/>

        <!-- -20 deg Up -->
        <!--<param name="min_ang" type="double" value="-0.34906585"/>-->

        <!-- +35 deg  Buttom -->
        <!--<param name="max_ang" type="double" value="0.34906585"/>-->

        <param name="min_ang" type="double" value="-0.34906585" />
        <param name="max_ang" type="double" value="0.34906585" />

        <param name="use_binary_protocol" type="bool" value="true"/>
        <param name="range_max" type="double" value="3.5"/>
        <param name="range_min" type="double" value="0.7"/>
        <param name="intensity" type="bool" value="True"/>

        <param name="hostname" type="string" value="$(arg hostname)"/>
        <param name="cloud_topic" type="string" value="$(arg cloud_topic)"/>
        <param name="frame_id" type="str" value="$(arg frame_id)"/>
        <param name="port" type="string" value="2112"/>
        <param name="timelimit" type="int" value="5"/>
        <param name="min_intensity" type="double" value="0.0"/> <!-- Set range of LaserScan messages to infinity, if intensity < min_intensity (default: 0) -->

        <param name="start_services" type="bool" value="True" />                  <!-- Start ros service for cola commands, default: true -->
        <param name="message_monitoring_enabled" type="bool" value="False" />      <!-- Enable message monitoring with reconnect+reinit in case of timeouts, default: true -->
        <param name="read_timeout_millisec_default" type="int" value="5000"/>     <!-- 5 sec read timeout in operational mode (measurement mode), default: 5000 milliseconds -->
        <param name="read_timeout_millisec_startup" type="int" value="250000"/>   <!-- 120 sec read timeout during startup (sensor may be starting up, which can take up to 120 sec.), default: 120000 milliseconds -->
        <param name="read_timeout_millisec_kill_node" type="int" value="250000"/> <!-- 150 sec pointcloud timeout, ros node will be killed if no point cloud published within the last 150 sec., default: 150000 milliseconds -->
        <param name="client_authorization_pw" type="string" value="F4724744"/>    <!-- Default password for client authorization -->

    </node>

</launch>

The command requires the authorization level "Authorized Client". We recommend that you first send a command to authorize this level according to the message structure in the attached screenshot.

See also https://github.com/SICKAG/sick_scan_xd/issues/160 for an example.

Just a note about sending a binary message like in your example:

Please remove all spaces between the hex values in this case.

@manuelrucci7 I am closing this issue for now. Please do not hesitate to reopen the ticket in case of further issues.


Added Help Bity - Miscellaneous

https://ctflearn.com/challenge/454 this challenge

I had solved this challenge, but I don't know why haven't I written a writeup on it. 😓
Anyways, thanks a lot bro! 🔥


Archives GitBook - July 2024

https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2024/july-2024

Missing Meeting Summary as at 30th of July
Mon July 1st

[ ] Treasury Policy Workgroup

Tues July 2nd

[ ] Governance Workgroup
[ ] Ambassador Townhall

Weds July 3rd

[ ] Dework PBL Workgroup
[ ] R&D Guild

Thurs July 4th

[ ] Onboarding Workgroup
[ ] Open GovWG
[ ] African Guild Meeting
[ ] Deep Funding Town Hall

Frida July 5th

[ ] Marketing Guild
[ ] Video Workgroup

Tues July 9th

[ ] Treasury Guild Operations
[ ] Governance Workgroup
[ ] Ambassador Townhall

Weds July 10th

[ ] Knowledge Base WG
[ ] R&D Guild

Thurs July 11th

[ ] Onboarding WG
[ ] African Guild Meeting
[ ] Deep Funding Town Hall

Fri July 12th

[ ] Marketing Guild
[ ] Writers Workgroup
[ ] Video Workgroup

Mon July 15th

[ ] Treasury Guild Session
[ ] Treasury Policy Workgroup

Tues July 16th

[ ] Treasury Guild Operations
[ ] Governance Workgroup
[ ] Global Ethics initiative - Open Office
[ ] Ambassador Townhall

Weds July 17th

[ ] Dework PBL Workgroup
[ ] R&D Guild

Thurs July 18th

[ ] Onboarding Workgroup
[ ] Open GovWG
[ ] African Guild Meeting
[ ] Deep Funding Town Hall
[ ] SNET_Latam Ambassadors Guild

Fri July 19th

[ ] Marketing Guild
[ ] Writers Workgroup
[ ] Video Workgroup

Mon July 22nd

[ ] Treasury Automation WG
[ ] AI Ethics bi-weekly WG call

Tues July 23rd

[ ] Treasury Guild Operations
[ ] Governance Workgroup
[ ] Ambassador Townhall

Weds July 24th

[ ] Knowledge Base WG
[ ] R&D Guild
[ ] Education WG

Thurs July 25th

[ ] Onboarding Workgroup
[ ] Open GovWG
[ ] African Guild Meeting
[ ] Deep Funding Town Hall
[ ] SNET_Latam Ambassadors Guild

Fri July 26th

[ ] Marketing Guild
[ ] Writers Workgroup
[ ] Video Workgroup

Saturday 27th

[ ] Gamers Guild


Vend is deprecating HTTP Basic Auth

The initial plan was to do it at the end of January but it has slipped a couple of times.
Now it looks like it may actually happen at the end of June: http://bit.ly/BasicAuthByeBye.

unfortunately i'm putting this in the too hard basket.
To do oauth, you either need to have a http endpoint (which is a bit of a pain to setup with a standalone lib) or you need to be able to copy & paste the key into the library somehow.
On top of this, vend are issuing new keys every few days (i think it might be 5 or 7 from memory) which introduces a new problem of how to store the keys.
TLDR;

Too hard to get the initial key
Too hard to update the key every few days

I've hacked up the lib for my own purposes and hacked in support for both, but there doesn't seem to be an easy way to fix that can just be dropped into any project

Actually, I don't think that implementing OAuth should be the concern of this library. The consumer of this library should provide a token just like they provide the username and password. How they obtain the token is their problem (not really that hard to solve).
Without any change this code will simply stop working which is probably the worse outcome than making it work with a user supplied token.


Increment version for cognitiveservices/azopenai releases

Increment package version after release of cognitiveservices/azopenai

Last release was to retract this package. I'm going to delete the code after I've confirmed - so no new releases will come out here.