No traces in Zipkin when running the example weather and Example.WeatherService

Hi,
I have installed Zipkin which is running fine on http://localhost:9411/ :
docker run -d -p 9411:9411 openzipkin/zipkin
I started the example :

https://github.com/serilog-tracing/serilog-tracing/tree/dev/example/weather
https://github.com/serilog-tracing/serilog-tracing/tree/dev/example/Example.WeatherService

I can see the trace in Seq :

But nothing in Zipkin.
I put a breakpoint in ZipkinSink :
public async Task EmitBatchAsync(IEnumerable<LogEvent> batch)
    {
        var content = FormatRequestContent(batch);
        if (content == null)
            return;

        var request = new HttpRequestMessage(HttpMethod.Post, "api/v2/spans")
        {
            Content = new StringContent(content, _encoding, "application/json")
        };

        var response = await _client.SendAsync(request);
        response.EnsureSuccessStatusCode();
    }

And saw that I had an error in the response 400 BadRequest :
Expected a long but was<PHONE_NUMBER>558327.4 at line 1 column 176 path $[0].timestamp reading List<Span> from json
I find out the problem was here TracingFunctions and commented (decimal)ts.Ticks / 10 :
public static LogEventPropertyValue? Microseconds(LogEventPropertyValue? timeSpan)
{
// Casts (truncates) rather than rounding.
// if (timeSpan is ScalarValue { Value: TimeSpan ts })
//     return new ScalarValue((decimal)ts.Ticks / 10);
  if (timeSpan is ScalarValue { Value: TimeSpan ts })
      return new ScalarValue((decimal)ts.Ticks);

  return null;

}
Now I'm getting a 202 but there is nothing in Zipkin :

I'm new to OpenTelemetry and don't why I can't see the traces in Zipkin?
 All MeterFilters should be configured before any Meters are registered. If that is not possible or you have a use case where it should be allowed, let the Micrometer maintainers know at https://github.com/micrometer-metrics/micrometer/issues/4920. Enable DEBUG level logging on this logger to see a stack trace of the call configuring this MeterFilter.
2024-11-01T10:26:03.345Z  INFO [/] 1 --- [oss-http-*:9411] c.l.a.s.Server                           : Serving HTTP at /[0:0:0:0:0:0:0:0]:9411 - http://<IP_ADDRESS>:9411/

Thanks for the report @rachkoud! It looks like Zipkin's API expects the timestamp as an integer value of microseconds since the Unix epoch.
The behavior of that Microseconds expression doesn't appear to actually truncate to a whole integer value so I think this is a bug.


Tuning the Erlang VM

Simple standard tunings of the Erlang VM cuts processing time in half here on my Linux Core i7 machine:
erl +P 2000000 +sbt db +sbwt very_long +swt very_low +sub true +Mulmbcs 32767 +Mumbcgs 1 +Musmbcs 2047
This makes the system lock the schedulers to physical cores so your kernel threads are not jumping around like mad. It also tells the VM to allocate carriers for memory in blocks of 32 megabytes and to use 2048 kilobyte blocks inside there. This means you get superpages in the TLB and you have way fewer TLB hits in the long run :)

I am using Erlang v19.0 in Windows 7, i7-5600U, there is no significant difference between your turning parameters and the original one 'erl +P 2000000', original one costs around 1763ms, while your turning one costs around 1700ms.

Two immediate comments:

The above won't work in a VM. It requires you have precise control over the "raw steel".
I'm quite sure many of those parameters are no-ops on Windows, so you will probably need some Unix-derivative to get these to work.


"this.$waveui.notify" not compatible with vite and vue3

Can not use "this.$waveui.notify" not compatible with Vite and Vue3 is there any ways to use notification function with Vite and Vue3 instead of using <w-notification>
Thank for reviewing my issue!

Hi @fxxhhhhhhh,
Thanks for reporting. It's weird that the documentation itself is built with Vue 3 and Vite and the notify method works fine.
I also tried to use Wave UI from npm import on another Vue 3 + Vite project and the notify works fine as well.
Only the example on Stackblitz reproduces the issue that you are seeing.
So I'll keep searching and will let you know when I have a fix.

@antoniandre,
Thanks for answer me. Notify method works fine on option API but my project use composition API, so it can not call this.$waveui.notify method and I also tried to use global properties as well but it's not working either.
const globals = getCurrentInstance().appContext.config.globalProperties.$waveui;
globals.notify({ message: "test noti", color: "error", timeout: 0});
It has no error message but notification tab not appear on my screen
I'm not sure if I correctly call the instance of waveui by using globalProperties

Hi @fxxhhhhhhh, could you try the latest version 2.42.0 and let me know if it works for you?
Here is how you should be able to use the notify method for composition API:
<script setup>
import { useWaveUI } from 'wave-ui'

const waveui = useWaveUI()

const notify = () => {
  waveui.notify('test!')
}
</script>

from the template: @click="notify".
Let me know if that works

I have reverted the change for now in version<EMAIL_ADDRESS>because it would be a major breaking change.
So to try it, please specifically install npm i<EMAIL_ADDRESS>Here is also a Codepen example: https://codepen.io/antoniandre/pen/gOzbVPz
in this version it is using WaveUI.default but that would not stay this way.

Thanks for your help @antoniandre
There is no error on the code but it still haven't appeared on my screen.

Hi @antoniandre,
Sorry to disturb you.
Is there any problems with wave-ui I can not use it. My server has used your wave-ui component but it seems not working in every W-component for 5 hours.

Thank you for work on this @antoniandre . Amazing job!
I used notifications for v2.48 like this:
import WaveUI from 'wave-ui'
export const setup_info_notify = (text = '') => {
  const wave = new WaveUI()
  wave.notify({
    message: 'Hello',
    info: true,
  })
}

After upgrade to v3.0.4 this does not work anymore.
In console it says: runtime-core.esm-bundler.js:218 Uncaught TypeError: wave.notify is not a function
I tried to fix it and found the other way described above with using useWaveUI.
But when I use this
import { useWaveUI } from 'wave-ui'
const waveui = useWaveUI()
export const setup_info_notify = (text = '') => {
  waveui.notify('test!')
}

console says : The requested module '/node_modules/.vite/deps/wave-ui.js?v=218e8fdf' does not provide an export named 'useWaveUI'
So I lost ability to use notifications with composition API, vite and vue 3.
Could you advise me a new way of using it ?
Thank you in advance!

Hi @nastefan, @fxxhhhhhhh,
Indeed, in version 3.0 I have removed the useWaveUI method in favor of inject('$waveui').
https://antoniandre.github.io/wave-ui/options-presets-and-waveui#the-waveui-helper
So now if you want to use $waveui in the composition API, you can do this:
import { inject } from 'vue'

const $waveui = inject('$waveui')
$waveui.notify('Hello!', 'info', 0)

Here is a StackBlitz showcasing the $waveui.notify() with Wave UI 3, Vue 3, and Vite:
https://stackblitz.com/edit/waveui-3-ldocdb?file=src%2FApp.vue
(Also try the rating to see a notification)
Hope this makes sense, let me know if we can close this issue. :)

By the way, since you raised this point, I have updated the migration page to add this note.
https://antoniandre.github.io/wave-ui/migration-from-v2-to-v3
Any feedback on Wave UI 3.0 and/or documentation is appreciated in order to complete it and make it as intuitive as possible. Just open an issue for any comment/suggestion/feedback :)

Hi @antoniandre , thank you for the fast reply!
Indeed, it works as you made in StackBlitz in my project too.
But I have some of my composition functions (such as notifications) in a separate js file which I use then for many components.
I am using it in the way showcasted in StackBlitz (it is yours one , slightly changed), please have a look:
https://stackblitz.com/edit/waveui-3-za1wir?file=src/composition/useNotifications.js
In such way it says , "notify is not a function".  And rating to see a notification not working.
Do you have some hint why it is not working from a separate file?
I guess it is because of inject, but can not find a solution by myself.

Hi @nastefan,
I don't think it is the best strategy to use $waveui in an external file without providing it. I would suggest that the use of $waveui, Wave UI being a UI toolkit that is directly associated to the template and DOM, should stay in a template or in the component that the template uses.
Also this code example is probably simplified, but as it is there is no benefit from calling a custom notify function from another file that would just call $waveui.notify.
That being said, you can still make it work if that is what you want or need for some reasons.
The complexity is that Vue does not let you use the inject function outside of the app context, from an external file, which I also understand. It will raise a warning.
But here are 2 ways to bypass the limitations:

provide $waveui as a parameter of your show_info function, or create a class around it that is storing $waveui from its constructor.
like shown in this StackBlitz, you could create your own useWaveUI function in main.js, and use it from useNotifications.js. In the main.js, you have access to the app context where you can pull the $waveui object. make sure you use this function after the created hook for anything related with DOM.

Let me know if you have made it work the way you wanted :)

now is
<script setup >
import {inject} from "vue";
const $waveui = inject('$waveui')


feat: webgl fly to should fly to bounding sphere rather than extent

FlyTo in 3D was still using the 2D FlyToExtent, which does not take altitude into account and could potentially fly the camera too far in to see the feature.
Test:

Make some places with and without altitude
Right click each one and select "Go To" in 2D and 3D

In 3D, tilt the camera before and verify that it keeps the general orientation after flying to the feature(s)

Place the features in a folder and select "Go To" on the folder in both 2D and 3D

Failing for pixel differences in a Cypress test (smoke-tests/load-state-file-arcgis.spec.js). May or may not be related.

Failing for pixel differences in a Cypress test (smoke-tests/load-state-file-arcgis.spec.js). May or may not be related.

We are currently operating under the assumption that any failure in those tests is unrelated to what we are working on.


Labels for Wheelchairs and Strollers in Sensor Dataset

Hi, I'm currently trying to access the Sensor dataset and was looking for images that have Wheelchairs and Strollers in them. I modified the file in the tutorial (av2-api/blob/main/tutorials/generate_sensor_dataset_visualizations.py) for this. However, I'm not able to find any images with those labels. Can you please tell me specific sequence ID's that have wheelchairs and strollers and the other rare classes?

Thanks for the response and the code, I can now see that these annotations exist.
I have been trying to modify the visualisation code provided in the api (https://github.com/argoai/av2-api/blob/main/tutorials/generate_sensor_dataset_visualizations.py) to convert the cuboids into boxes, clearly there's some bug in my code. I'll open another issue if necessary. Thanks for the help, I'm closing this issue.


Configurable token.dat path

Would it be possible to provide a path via flag for the token.dat?
This would help us add eth2stats client in our deployments.

sure, will prioritize it
seeing how docker creates folders when given a volume that does not exist on the host, would it be ok to have a customizable config so you can specify -v /local/config/folder:/config ?
would you then also need to change the /config part?
p.s. excuse the current poor documentation, super WIP

btw @prestonvanloon , for now you can also just not mount it, if the key is lost on pod/container recreation, a new entry with the same name will appear on the portal, the old one will appear offline and will be cleaned up after a few hours

I don't mind mounting a config volume, but the token path is not in the config path.
https://github.com/Alethio/eth2stats-client/blob/ee16e1e4dca4c4275e47a2905c8ca11e40763621/core/token.go#L11

oh yeah, made the change here https://github.com/Alethio/eth2stats-client/pull/3/files#diff-2c824df4dc0776b6848cf5e02e9d5f07R13
as soon as it's reviewed i ll ping you

hey @prestonvanloon this was merged.
can you try with
docker run -d --name eth2stats --restart always --network="host" \
    alethio/eth2stats-client:latest \
    run --v \
    -v /path/to/your/persistant/data/folder:/data \
    --eth2stats.node-name="YourNode" \
    --data-folder="/data" \
    --eth2stats.addr="grpc.sapphire.eth2stats.net:443" --eth2stats.tls=true \
    --beacon.type="prysm" --beacon.addr="localhost:4000"


CiliumNetworkPolicy validation

This patch adds validation for CiliumNetworkPolicy with CEL
Fixes: #23152

Adding @christarazi and @giorio94 as extra reviewers due to https://github.com/cilium/cilium/issues/23152

Adding @gandro as extra reviewer, who has already reviewed an earlier iteration of this PR.
@romanspb80 Please do not open separate PRs for the same patch as it becomes difficult to follow the comments history.

@romanspb80 Could you rebase on main again? CI is failing due to #26883 not being part of you branch. Thanks.


Direction Finder JS Extension

Is your feature request related to a problem? Please describe.
Users often find it difficult to find directions to visit some places, specially in remote areas. We know, the accuracy of Google Maps varies with the strength of network connection, and in remote areas, it's difficult to have a strong network connection, which many-a-times makes the user lose direction and get lost.
Describe the solution you'd like
I'd like to develop a Direction finder JS extension, which would help the users to get accurate directions of a particular place, even in areas with low/weak network connectivity. Also, the users will be able to choose their mode of travel, i.e., Driving, Walking, Cycling, etc.
Additional context
The UI should be clean and kind of same to that of Google Maps, so that it'll be easier for the users to use it, and also, it should provide accurate directions of any given place.
What problem is this feature trying to solve?
The feature is aimed at providing the users an extension to find directions from and to any place any wish to travel.
How do we know when the feature is complete?
The feature will be completed when the users will be able to find directions by entering the From and To places in the extension.

please assign me this issue

Hey @S-i-y-a-g I'm working on this issue already.
Please note @Sulagna-Dutta-Roy.
Thank you!


(iOS) Background player not having any affect on audio

Configuration
System:
OS: macOS 10.14.6
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 1.64 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.4.0 - ~/.nvm/versions/node/v12.4.0/bin/node
npm: 6.9.0 - ~/.nvm/versions/node/v12.4.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
IDEs:
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.5 => 0.60.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-track-player version: ^2.0.0-rc13
Issue
On iOS 12.4 I notice that while the audio continues playing in the background, none of the background player controls have any affect on the audio other than volume. Pausing and playing are maintaining state independently of the audio in my app.

I Have this problem too ...

Same issue

I have this issue on the latest version of iOS as well

Same issue, were you able to solve it?

react-native-track-player version: dev
not working on iOS 13 too

react-native-track-player version: dev
not working on iOS 13 too

I can confirm that iOS 13 its not possible to play any track at all.

@R3DST0RM could you give #820 a try?

react-native-track-player version: dev
not working on iOS 13 too

I can confirm that iOS 13 its not possible to play any track at all.

@R3DST0RM Can you give #820 a try if you are workin on dev branch.

I will test it tomorrow and report here

Dear all!
Dont specify ^2.0.0-rc13 (version with ^) because NPM will resolve this version by ASCI sort order and will install 2.0.0-rc9, there is a fix for this issue in 2.0.0-rc13
Specify 2.0.0-rc13, reinstall and check package-lock.json (what version is resolved)!

I'm having the same issue. I've swapped to 2.0.0-rc13, but only the time on lock-screen stops, not the actual audio. Not sure if I've failed to declare something, or if I've done something wrong... I did registerPlaybackService right after app registry as well.
Service.js
`module.exports = async function () {
TrackPlayer.addEventListener('remote-play', () => {
console.log("hit background play")
TrackPlayer.play();
});
TrackPlayer.addEventListener("remote-pause", (event) => {
console.log("#DEBUG remote pause #", event);
TrackPlayer.pause();
});
TrackPlayer.addEventListener('remote-next', () => {
console.log("hit background skip")
TrackPlayer.skipToNext();
});
};`
Component playing music:
await TrackPlayer.setupPlayer();         TrackPlayer.updateOptions({           capabilities: [             TrackPlayer.CAPABILITY_PLAY,             TrackPlayer.CAPABILITY_PAUSE,             TrackPlayer.CAPABILITY_SKIP_TO_NEXT           ],           compactCapabilities: [             TrackPlayer.CAPABILITY_PLAY,             TrackPlayer.CAPABILITY_PAUSE,             TrackPlayer.CAPABILITY_SKIP_TO_NEXT           ],           notificationCapabilities: [             TrackPlayer.CAPABILITY_PLAY,             TrackPlayer.CAPABILITY_PAUSE,             TrackPlayer.CAPABILITY_SKIP_TO_NEXT           ]         });

https://github.com/react-native-kit/react-native-track-player/commit/d3400a475d8be146aa25696b5f014dd538e2dd86 should resolve this. Will get this into v2 soon.


[WIP DO NOT MERGE] PWM high level API

This defines the PWM high level API.

This looks pretty good. Is there more work that you want to get in before we merge this?

I believe, according to the feedback I had both on the developers mailing list and slack, for now there is nothing to add.


use new feature syntax for optional deps

As of rust 1.60, we can now manage weak dependency features enabling us to simplify the feature configurations.
context: https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html#new-syntax-for-cargo-features

@adlerjohn needs unblocked ci


Option to disable cluster telemetry after installed

Should be possible to disable it pre-installation and post-installation.

As a user I want to be able to toggle the collection of analytics data from the command line post install so I can control what data is collected from my installation.
You might also include issue #537 to turn off cluster and dashboard analytics at the same time.

What would be the recommended command to toggle this setting. Do we have a pattern for toggling setting yet?


add phone number validation function with tests #309

 New feature, or refactor of existing code: master/develop branch

Q
A

Documentation
no

Bugfix
no

BC Break
no

New Feature
yes

RFC
no

QA
no

Description
added phone number validator -> feature #309
the phone number validator can validate a phone number with county code like below:
+39(country code) 79435680(phone number)
these formats are valid for phone number:
3979435680
+3979435680
+39 79435680
(39) 79435680
+(39)79435680
+(39)<PHONE_NUMBER>
...

Hi there!
Any updates on this PR?


Support default values

It would be good if the users could set default values in case a value for that configuration is not found.
Something like:
const defaultConfig = {
  "verbose": true
}

const config = cosmiconfig.search({ default: defaultConfig })

I'm not sure this needs to be a feature of Cosmiconfig. Is there something challenging about applying the default values once you've loaded the config object?

Closing because I still do not understand the difficulty that Cosmiconfig would be solving by expanding its interface in this way.

Closing because I still do not understand the difficulty that Cosmiconfig would be solving by expanding its interface in this way.


_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
spotless
0m 55s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  4s
Maven dependency ordering for patch

-0 :warning:
shellcheck
0m  2s
The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
spotless
0m 58s
patch has no errors when running spotless:check.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  1s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

-1 :x:
spotless
1m  9s
branch has 1 errors when running spotless:check, run spotless:apply to fix.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  8s
Maven dependency ordering for patch

+1 :green_heart:
shellcheck
0m  2s
There were no new shellcheck issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
spotless
1m  4s
patch has 1 errors when running spotless:check, run spotless:apply to fix.

_ Other Tests _

+0 :ok:
asflicense
0m  0s
ASF License check generated no output?

4m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5781/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5781

Optional Tests
dupname asflicense spotless shellcheck shelldocs

uname
Linux c6ba6e52bedf 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 298c550c80

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5781/2/artifact/yetus-general-check/output/branch-spotless.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5781/2/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
46 (vs. ulimit of 30000)

modules
C:  U:

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5781/2/console

versions
git=2.34.1 maven=3.8.6 shellcheck=0.8.0

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Ability to read from a regex-based topic pattern in kafka-indexing-service extension

Kafka inherently allows pattern based topic subscription. It would be great if we can use it to allow reading them into a single datasource using a single task.

+1 vote

+1

+1


GH-1497: Add test for colon in destination

Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/1497
Fix was in Spring Integration.

The fix was back ported to Spring Integration 5.0.9 which will be in the next boot 2.0.x release.
However, the user will need to add /META-INF/spring.integration.properties containing spring.integration.jmx.quote.names=true.
I don't think it's necessary to backport this test case.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@60b6f02). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1501   +/-   ##
=========================================
  Coverage          ?   62.37%
  Complexity        ?      915
=========================================
  Files             ?      139
  Lines             ?     4223
  Branches          ?      607
=========================================
  Hits              ?     2634
  Misses            ?     1278
  Partials          ?      311

Continue to review full report at Codecov.

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


[Feature] - Add Chain Agnostic Blockchain Reference

Add Chain Agnostic Blockchain Reference

Define a CAIP-2 blockchain reference for Sui.

Motivation
To be able to reference SUI for an integration I am looking at completing for Ceramic Network there is a need to have a blockchain reference in Chain Agnostic. This will be the discussion point for the CAIP that I will be submitting shortly.

Hey team, here is a draft. I'm not sure how far the discussions are regarding a reference framework or if there is any information available publicly. Any insight?

This PR and conversation have been moved to the namespace repository https://github.com/ChainAgnostic/namespaces/pull/43

wondering what support for this does the sui repo need? does signature needs to commit to this namespace or this is for other usages?
the rfc looks fine to me otherwise to give identifier for network names.

Thanks for querying @joyqvq. Nothing is needed in the Sui repo. This was created to provide a place for discussions(as specified in the PR request criteria from Chain Agnostic).
What's required is documentation and/or verification that the namespaces for the sui network are what is specified in the CAIP. While looking in the repo and discord I could see no standard to what sui networks are referred as.
For reference the CAIP has the following sui references:
# Sui mainnet
sui:mainnet
# Sui testnet
sui:testnet
# sui devnet
sui:devnet

Other blockchain CAIPs may provide more context and can be found here

Thanks for the insight @bumblefudge. Thats some good information to keep in mind and makes a lot of sense. I'm not sure if that works for all networks though considering Devnet is dynamic and will change regularly(well,it has been in these early stages). Still waiting on some input from the team but it looks like there has been the appoach of naming via 'testnet' and 'devnet' here.

See also:
https://github.com/ChainAgnostic/namespaces/issues/41

Sorry for not contributing to this thread earlier. I've been working on a number of things related to this topic, let me share a bit about what we're thinking.
Until recently sui didn't really have a concept of a "genesis block", as of a week or so ago this has changed and the output of genesis is now checkpoint 0, or the genesis block as in other systems. This gives us the opportunity to use the hash of checkpoint 0 to be used as an unambiguous chain identifier.
We do use the terminology 'mainnet', 'testnet', 'devnet', etc as more human usable labels for various networks, but going forward they should be treated as tags or references that point to the unambiguous chain id (i.e. the hash of the genesis block), e.g. devnet -> 0x123456....

Thanks, that makes CAIP-authoring (and interop!) a lot simpler!

Whoever takes the pen on finishing up the CASA docs, feel free to ping me on the CASA Discord if I miss the GH notif.

@0xzoz @bmwill
I'll also add that since this thread, other contributors to the CASA docs pointed out that it was confusing to know where to start and what the expectations were from just the template, so I wrote this little doc to guide people through it:
https://github.com/ChainAgnostic/namespaces/blob/main/CONTRIBUTING.md
Feel free to ping me anywhere or open an issue or PR if you think the contributing.md file needs more detail or guidance :D


upgrade the version to align with light-4j for release

Also, add it to the light-bot.

This has been done.


Add a |textlayerrendered| event

Tentative patch, implementing https://github.com/mozilla/pdf.js/pull/5511#issuecomment-68437309.

/botio-windows preview

/botio-windows preview

Thank you


Automated cherry pick of #2511: schedtags: support scope

Cherry pick of #2511 on release/2.12.
#2511: schedtags: support scope

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@f14b5dd). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #2521   +/-   ##
==============================================
  Coverage                ?   7.04%
==============================================
  Files                   ?     457
  Lines                   ?   72021
  Branches                ?       0
==============================================
  Hits                    ?    5073
  Misses                  ?   66528
  Partials                ?     420

Flag
Coverage Δ

#aFlag
7.04% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/policy/resources.go
0% <ø> (ø)

pkg/cloudcommon/db/scoperesource.go
0% <0%> (ø)

pkg/compute/models/schedtags.go
3.9% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm

/approve


Add IP version selection

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
This PR introduces the ability to force a monitor to use IPv4 or IPv6. The existing behavior is left as is if automatic is set (which is the default in the PR). I.e. end-users would need to specifically select IPv4 or IPv6.
This addresses (at least in part) the following issues:
https://github.com/louislam/uptime-kuma/issues/3542
https://github.com/louislam/uptime-kuma/issues/1242
https://github.com/louislam/uptime-kuma/issues/1025
The option is currently only available for the following monitors: ping, tcp, dns.
I looked into adding it for http monitors, but it is not possible without modifying axios, see:
https://github.com/axios/axios/issues/5785
https://github.com/axios/axios/issues/590
Type of change
Please delete any options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
User interface (UI)
New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Could you add Resolves #ISSUE-NUMBER to the issues this PR resolves?

Could you add Resolves #ISSUE-NUMBER to the issues this PR resolves?

I've already listed this in the description:
This addresses (at least in part) the following issues:
https://github.com/louislam/uptime-kuma/issues/3542
https://github.com/louislam/uptime-kuma/issues/1242
https://github.com/louislam/uptime-kuma/issues/1025

Could you add Resolves #ISSUE-NUMBER to the issues this PR resolves?

I've already listed this in the description: This addresses (at least in part) the following issues: #3542 #1242 #1025

He says add it like this Resolves #ISSUE

Could you add Resolves #ISSUE-NUMBER to the issues this PR resolves?

See https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue why this exact wording is important ^^

Could you add Resolves #ISSUE-NUMBER to the issues this PR resolves?

See https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue why this exact wording is important ^^

As I described in the description, this PR supports ping, tcp, and dns. Which means it resolves the problem for these monitors. Notably, I can't fix http which requires a change to axios. Therefore while things are improved for these issues, they are not resolved if you are using an http monitor.

#3542 and #1025 can be considered fixed since they specifically mention the Ping and TCP Port monitor types.

#3542 and #1025 can be considered fixed since they specifically mention the Ping and TCP Port monitor types.

Yes, I agree it Resolves #1025
Without digging into #3542 it's hard to know exactly what their issue is. This PR will add the option they're asking for to force IPv4. Do we consider that resolved? Even if their issue is something else. They have not given detail on their monitor, so it's unclear what is generating the error.

Just have a quick look of code changes, haven't checkout yet.

We don't provide new features for 1.23.X. You have to rebase to master branch.

Have to use knex migration now since we will support MariaDB in upcoming version: https://github.com/louislam/uptime-kuma/tree/master/db/knex_migrations

I saw lines like this this.hostname = address. Is that the original hostname is being overwritten by the resolved IP address? If yes, this approach is not ok.

For DNS Monitor, this option could be ambiguous, since users could wrongly think it is A record vs AAAA record.

Thanks for the comments. I'm happy to make adjustments. I have a few questions.

Just have a quick look of code changes, haven't checkout yet.
* We don't provide new features for 1.23.X. You have to rebase to `master` branch.

I have merged with master already, but happy to rebase. Do you want me to rebase to master, or is the merge ok?

* Have to use knex migration now since we will support MariaDB in upcoming version: https://github.com/louislam/uptime-kuma/tree/master/db/knex_migrations

I'll need to look into what this means.

* I saw lines like this `this.hostname = address`. Is that the original `hostname` is being overwritten by the resolved IP address? If yes, this approach is not ok.

I need to understand a bit more in order to resolve this. Would it be acceptable, to define a new variable in monitor.js, and then pass this new variable into the various monitors in place of the hostname? Or is there something else I need to be considering?

* For DNS Monitor, this option could be ambiguous, since users could wrongly think it is A record vs AAAA record.

This is mainly a UI comment. putting the option far down under advanced settings I think addresses this, but I'm open to ideas. Do we need a short description in the UI?

Maybe we should rename the variable to ipByHostname or similar to prevent confusion, since it's definitely not a hostname anymore.

Maybe we should rename the variable to ipByHostname or similar to prevent confusion, since it's definitely not a hostname anymore.

Happy to change the variable name. It stays as hostname to retain the existing behaviour if IPv4 or IPv6 is not selected. Would HostnameOrIp be more appropriate?

Ah I see how it works now, I'm okay with this.
I'm also slightly concerned that you're seeing the value to null on error. Would continuing to execute the monitor with the null value give weird results? Should we revert to the original hostname, or throw an error to mark the heartbeat as DOWN?

Ah I see how it works now, I'm okay with this.
I'm also slightly concerned that you're setting the value to null on error. Would continuing to execute the monitor with the null value give weird results? Should we revert to the original hostname, or throw an error to mark the heartbeat as DOWN?

This is intended to generate an error in the monitor. We don't want to retain the original value, otherwise the monitor might succeed (e.g. it might be set to IPv6 and have no AAAA record, and then pass with IPv4 - this would have the IPv6 monitor showing up). It might be better to throw an error and mark the monitor down straight away. I'll look into that...

@chakflying updated to throw instead of setting to null. This is definitely an improvement. Thanks.

Could you add Resolves #1242 to the discription? This way it will be closed if merged

Could you add Resolves #1242 to the description? This way it will be closed if merged

@CommanderStorm see more earlier comment below:

As I described in the description, this PR supports ping, tcp, and dns. Which means it resolves the problem for these monitors. Notably, I can't fix http which requires a change to axios. Therefore while things are improved for these issues, they are not resolved if you are using an http monitor.

#1242 is only partially resolved as it does not add the option for http monitors.

Any more comments or are we good to merge?

currently have great use for it, would be nice if the feature would come soon 😊👍

This is the most important feature request I'm missing.

What a huge update! expect!

Can we get this PR merged?


show team view type when login user is the team manager

@harapan1231 What is your use case here? Goji does not handle permissions/user types.

@elithrar so sorry, i made a mistake. i all close the issues. but i don't know how to delete them.


build(darwin): bump libs

fix iOS HDR (#372)
fix HLS MP4 seek (#395)
fix VP9 macOS Intel freezes
fix image based subtitles
fix subtitles in m3u8 (#394)
add AV1 support (#429)

As there are a lot of changes, particularly patches, there's a risk of introducing bugs, so I'm going to keep this PR open for a few days so that everyone can test it.

HLS MP4 seek 😢

HLS MP4 seek 😢


shaka player not auto hide control bar in fullscreen mode on Android device

Chrome Version: 57.0.2970.0
OS: Android
This is not observed on other OS, only on Android. It not repro on HTML5  elements on Android.
What steps will reproduce the problem?
(1) navigate to http://shaka-player-demo.appspot.com/demo/
(2) load any video
(3) switch to fullscreen mode
What is the expected result?
after a some seconds, control bar hide away
What happens instead?
control bar stays, not hide away

Thanks for filing!
I did some preliminary investigation.  It appears that we may be missing some touch event in the UI somehow when we enter fullscreen mode.  Only happens on Android because it depends on touch events.

The problem is that phones do not have a mouse, but browsers simulate them.  The browser will still fire mouse events (e.g. mousemove) and it will still use the CSS :hover pseudo-class.  When you click the fullscreen button, the controls will get the :hover styles; however, the style doesn't get removed until you "click" somewhere else, even if you drag elsewhere.
So if we are getting touch events, we should override the :hover styles and hide the controls.

This appears to be happening again.


Spiral Matrix in C++

Information about Algorithm
It is a question of 2D Array.
-->It is a Medium Level Question on Leetcode
Have you read the Contributing.md and Code of conduct

[x] Yes
[ ] No

Other context
This is a competitive platform problem i.e. Hackerrank,Codechef,GeeksforGeeks,Leetcode,Codeforce

please assign this to me

hey please assign this to me

hey can you describe the problem more in detail

@Vishesh3569 I have already worked on this

may i help you sir.


Inject dll into cmd.exe process and call "dec" function to execute my ".enc" payload.

Hello lawrenceamer, hope you are well.
I have a question, how can I call the export function "dec" and execute it when I injected the dll into "cmd.exe" process, or what is the technique, the reflective injector you are used to do that.
because when I injected the dll into the cmd.exe process it is just injected and didn't execute "dec" function to run the ".enc" payload.

I didn't understand your question, but if you wanna call the specific DLL export function
rundll32 mortar.dll,dec


Services api

[x] #364
[x] #366
[x] #367

@lkuchenb
Post, put and get work as intended, but I have problems with adding the new site_id Prefix DMS- for the services table.

@lkuchenb
Post, put and get work as intended, but I have problems with adding the new site_id Prefix DMS- for the services table.

DMS- is already used for submissions. I added DMP- (process/program) in this PR, maybe we should merge this first?
https://github.com/ghga-de/datameta/pull/388/files

Ah now I see that you've done similar changes in this PR. You didn't add the prefix lengths though, I think, may that be the error?

Ah now I see that you've done similar changes in this PR. You didn't add the prefix lengths though, I think, may that be the error?

Added the prefix lengths, but that did not change the outcome...


sync to live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/windows-iotcore-docs, working directory: W:\prnj-s, target branch: live, target branch commit: 55b9cef9cd4994e0b2dc01526ff77108e0106ef6, source branch: master, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Resources.md
:white_check_mark:Succeeded

windows-iotcore/release-notes/CurrentCommercial.md
:white_check_mark:Succeeded

windows-iotcore/release-notes/commercial/October2018Update.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


CMake: generate and install a Package Configuration file

This pull request is now managed with CodeReviewHub. Refresh.

Current coverage is 80.34%

Merging #362 into master will not affect coverage as of f0059f3

@@            master    #362   diff @@
======================================
  Files          211     211
  Stmts         7169    7169
  Branches         0       0
  Methods          0       0
======================================
  Hit           5760    5760
  Partial          0       0
  Missed        1409    1409

Review entire Coverage Diff as of f0059f3

Powered by Codecov. Updated on successful CI builds.

:+1:

:+1:

:+1:


add dependabot

Signed-off-by: Jan Willies<EMAIL_ADDRESS>Description of your changes
Add dependabot for dependency management
I have:

[x] Read and followed Crossplane's [contribution process].
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
This configuration is used in the provider-kubernetes project

LGTM. Thanks @janwillies


added relevant COI mock community info and rep seqs

Hi mockrobiota folk,
I've added the fasta file for the mock COI dataset I've used in a few bat guano related projects. Though I don't have a publication to link these data to at the moment, @nbokulich is on the forthcoming paper that describes their use. Reads are dumped as BioSamples via NCBI and I've provided a link in the README.md file for users to access.
Please let me know what other information you'd like me to add.
Cheers

Thanks @devonorourke !
It looks like the tests failed; could you please fix those and then I can review once tests path? The error suggests that the dataset metadata file's header line is space delimited not tab delimited.

Sorry; I fixed the dataset-metadata.tsv file so that it was tab-delimited.
Should be okay now


Display pkg fn

we face some problem to find links in laptop version of sui wallet

we face some problem to find links in laptop version of sui wallet


Basic use case with sections

Hi,
Any pointers on how to get a basic sections use case going?  I'm trying to create a recylcerview pulling based on static data with 10 categories and about 30 items.  I'm following the examples in the dev branch example app, but any help would be appreciated.
Regards,
Ivan

Hello @zosocanuck,
You said that data is static, that means it doesn't change if some events occurs while the RV is shown? and 30 items each section?
You can follow the wiki page for headers and sections, and choose the use case 1, which is the most simple to use: You can create ISectionable items by setting the same IHeader for same section; Add the items to the Adapter list; Call setDisplayHeadersAtStartup().
PS. I've just committed some improvements in dev branch.

Correct, I've created a product class which could mimic
SimpleItem extends AbstractExampleItem<SimpleItem.ParentViewHolder>
		implements ISectionable<SimpleItem.ParentViewHolder, HeaderItem>, IFilterable, Serializable {

I have a ProductFragment which now sets an adapter of MyProductViewAdapter
public class MyProductRecyclerViewAdapter extends RecyclerView.Adapter<MyProductRecyclerViewAdapter.ViewHolder> {
So I would then change MyProductRecyclerViewAdapter to extend FlexibleAdapter?

You can also extend AbstractSectionableItem for the Product item. It should be simpler for you, because already implement the common methods for the header.
Regarding, the Adapter, you extend to FlexibleAdapter, correct.
You will see that you will have to give a parameter to the signature (the most common type of all items): Header type and Sectionable type both extends AbstractFlexibleItem, so you should use this signature extends FlexibleAdapter<AbstractFlexibleItem> (as in my ExampleAdapter) and implement the constructor properly.
In the end, your Fragment/Activity should implement the listeners your use case foresee.
Regarding the creation and binding the ViewHolders, my example shows how to use the METHOD A or the METHOD B (always in ExampleAdapter).

@zosocanuck, do you still need support on this issue?

No this can be closed.  Slowly learning by trial and error :)


The type 'Query' [@83:1] has declared a field with a non unique name 'customersByEmail'

Describe the bug
The schema compiles without errors using amplify api gql-compile but gives the following error when deploying:
The type 'Query' [@83:1] has declared a field with a non unique name 'customersByEmail'
The customer type:
type Customer
  @model
  @key(
    name: "customersByEmail"
    fields: ["email"]
    queryField: "customersByEmail"
  )
  @auth(
    rules: [
      {
        allow: groups
        groups: ["Admins"]
        operations: [read, create, update, delete]
      }
      { allow: owner, ownerField: "owner", operations: [create, update, read] }
      { allow: public, provider: apiKey, operations: [create] }
    ]
  ) {
  id: ID!
  email: String!
  [...]
}

The Query schema:
enum ModelSortDirection {
  ASC
  DESC
}

input ModelStringFilterInput {
  ne: String
  eq: String
  le: String
  lt: String
  ge: String
  gt: String
  contains: String
  notContains: String
  between: [String]
  beginsWith: String
}

input ModelIDFilterInput {
  ne: ID
  eq: ID
  le: ID
  lt: ID
  ge: ID
  gt: ID
  contains: ID
  notContains: ID
  between: [ID]
  beginsWith: ID
}

type ModelCustomerConnection {
  items: [Customer]
  nextToken: String
}

input ModelCustomerFilterInput {
  id: ModelIDFilterInput
  firstName: ModelStringFilterInput
  lastName: ModelStringFilterInput
  email: ModelStringFilterInput
  zipCode: ModelStringFilterInput
  owner: ModelStringFilterInput
  and: [ModelCustomerFilterInput]
  or: [ModelCustomerFilterInput]
  not: ModelCustomerFilterInput
}

type Query {
  customersByEmail(
    email: String
    sortDirection: ModelSortDirection
    filter: ModelCustomerFilterInput
    limit: Int
    nextToken: String
  ): ModelCustomerConnection @aws_api_key @aws_cognito_user_pools
}

I am attempting to override what is generated so that @aws_api_key (public access) is available to this query.
To Reproduce
Steps to reproduce the behavior:

write the above in schema
run gql-compile
push change in repo to console
See error

Expected behavior
Successful deployment

Hello @aireater , sorry that you are facing this issue. We are currently investigating this issue. Do you have a sample repo that we could test with?

I don’t have a sample repo to test. Are you not able to replicate the issue with the code I included?

Cannot reproduce anymore.

I get the same error. Could it be that the name and queryField has the same name?
using 4.34.0
I had:
@key(name: "byClaimCode", fields: ["claimCode"])
changed it to
@key(name: "byClaimCode", fields: ["claimCode"], queryField:"byClaimCode")
And then i got that same error.

The reason is because I didn't include the list query... once I remove this line it worked: ✅
queries: { get: "getXX" }

duplicated fiield in the schema


pickPosition broken when point cloud tileset added to scene

This works in 1.47 but is broken in master.  @lilleyse @ggetz
pickPosition randomly returns undefined if this point cloud is added to the scene.  I set show: false for the point cloud in this example because chappes grinds performance to a hault, but the issue happens either way.  It does not happen when there is no tileset in the scene.
var viewer = new Cesium.Viewer('cesiumContainer');

var position;

var moveHandler = new Cesium.ScreenSpaceEventHandler(viewer.scene.canvas);
moveHandler.setInputAction(function(movement) {
    if (position) {
        var p = viewer.scene.pickPosition(movement.endPosition);
        if(Cesium.defined(p)) {
            position = p;
        }
    }
}, Cesium.ScreenSpaceEventType.MOUSE_MOVE);

function getPosition(time, result) {
	return position;
}

var tileset = new Cesium.Cesium3DTileset({ url: Cesium.IonResource.fromAssetId(3838), show: false});
tileset.readyPromise.then(function() {
    position = tileset.boundingSphere.center.clone();
    viewer.entities.add({
        position:new Cesium.CallbackProperty(getPosition,false),
        billboard:{
            image:"../images/Cesium_Logo_overlay.png"
        }
    });

});
viewer.scene.primitives.add(tileset);
viewer.zoomTo(tileset);

@lilleyse we want to fix this before the release goes out.  What's the plan?

I'm hoping to look into this sometime this week.

Just a reminder that the release is this Wednesday.  We should really try and get all showstopper issues addressed by the end of today.

This might be a situation where we have to pick which bug is most tolerable:

Don't render the depth plane before 3D Tiles: tileset may show on opposite side of globe like this
Render the depth plane before 3D Tiles

Don't apply an offset to the depth plane: get classification artifacts.
Apply offset to the depth plane: picking the depth plane produces bad results - this issue

https://github.com/AnalyticalGraphicsInc/cesium/pull/6779 is easy to revert - I just want to know what people think about https://github.com/AnalyticalGraphicsInc/cesium/issues/6814#issuecomment-409059691.
Classification bug:

@lilleyse I don't understand why we have to choose one or the other if both worked in 1.36

1.36 was right before classification primitives were added. Going back to the 1.36 behavior results in the artifact above.

In that situation the depth plane is rendered after 3D Tiles to get around those 2 other bugs, but still before the opaque/translucent pass that all other primitives use.


Return GatewayResponse instead raising an error

Currently we have around 10.2k reported events in sentry due to unable finishing payments. For now instead of raising a PaymentError we will return a GatewayResponse with proper success information (True/False).
Error raises because we have a lot of situations when we have transactions to confirm  (status ACTION_TO_CONFIRM) but actually refused. In these situations we try to process the payment by checking the additional data. The problem is because we don't have additional data to check because we receive a checkoutComplete mutation only with chekoutId value.
After change if we try to create the same mutation we receive following response instead of another entry in sentry:
{
  "data": {
    "checkoutComplete": {
      "errors": [
        {
          "code": "PAYMENT_ERROR",
          "message": "Unable to finish the payment. Payment (<GRAPHQL_PAYMENT_ID>) does not have the additional data."
        }
      ]
    }
  }
}

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Codecov Report

Merging #8330 (94b284c) into 3.0 (082ed86) will decrease coverage by 0.00%.
The diff coverage is 90.16%.

:exclamation: Current head 94b284c differs from pull request most recent head 4a16968. Consider uploading reports for the commit 4a16968 to get more accurate results

@@            Coverage Diff             @@
##              3.0    #8330      +/-   ##
==========================================
- Coverage   93.04%   93.03%   -0.01%
==========================================
  Files         473      475       +2
  Lines       35809    36065     +256
  Branches     3784     3816      +32
==========================================
+ Hits        33318    33553     +235
- Misses       1714     1726      +12
- Partials      777      786       +9

Impacted Files
Coverage Δ

saleor/demo/settings.py
0.00% <0.00%> (ø)

saleor/graphql/checkout/mutations.py
96.97% <ø> (ø)

saleor/order/utils.py
92.75% <ø> (ø)

saleor/payment/gateways/braintree/__init__.py
95.03% <ø> (ø)

saleor/webhook/payloads.py
95.72% <ø> (ø)

saleor/core/app.py
80.00% <33.33%> (-20.00%)
:arrow_down:

saleor/plugins/webhook/tasks.py
86.84% <57.89%> (-5.62%)
:arrow_down:

saleor/plugins/webhook/plugin.py
68.86% <60.00%> (-0.68%)
:arrow_down:

saleor/checkout/complete_checkout.py
88.70% <66.66%> (-1.22%)
:arrow_down:

saleor/graphql/core/connection.py
82.12% <69.23%> (-2.22%)
:arrow_down:

... and 60 more

Continue to review full report at Codecov.

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


feat: replenish auth client interface

关联的Issues (Related Issues)

close https://github.com/filecoin-project/venus/issues/5541
改动 (Proposed Changes)

附注 (Additional Info)

自查清单 (Checklist)
在你认为本 PR 满足被审阅的标准之前，需要确保 / Before you mark the PR ready for review, please make sure that:

[x] 符合Venus项目管理规范中关于PR的相关标准 / The PR follows the PR standards set out in the Venus project management guidelines
[x] 具有清晰明确的commit message / All commits have a clear commit message.
[x] 包含相关的的测试用例或者不需要新增测试用例 / This PR has tests for new functionality or change in behaviour or not need to add new tests.
[x] 包含相关的的指南以及文档或者不需要新增文档 / This PR has updated usage guidelines and documentation or not need
[ ] 通过必要的检查项 / All checks are green

Codecov Report

Merging #123 (f404396) into master (73734ff) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #123   +/-   ##
=======================================
  Coverage   45.42%   45.42%
=======================================
  Files          35       35
  Lines        3813     3813
=======================================
  Hits         1732     1732
  Misses       1868     1868
  Partials      213      213

Flag
Coverage Δ

unittests
45.42% <ø> (ø)

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

Impacted Files
Coverage Δ

jwtclient/auth_client.go
63.45% <ø> (ø)


Python: Loops- pass

Description :
What is pass in python?
Note :

Changes should be made inside the Python/ directory & Python branch.
Issue only for GWOC'21 contributors.
Issue will be assigned on a first come first serve basis, 1 Issue  ==  1 PR.
In the PR, keep this issue's title as your PR's title.

Must Follow : Contributing Guidelines & Code of Conduct before start Contributing.

I would like to work on this please documentation
Peddi sai lohith
Python batch 4

I would like to work on this issue via documentation. Thank you!!

I would like to work on this!!

Hi I'd like to contribute through documentation on this topic
Harmandeep - python - batch 4

I would like to contribute on this.

I would like to contribute on this issue via documentation
Python Batch 6

@adityabisoi
Sir, I would like to contribute to this issue.
Name: Priyanshi Naredi
Type: Documentation
Batch: 18

I would like to work on this issue via documentation.

@adityabisoi
Sir, I would like to contribute to this issue.
Name: Arushi Rautela
Type: Video
Batch: 6

@kumarankm Is the mentor of this issue. Please reach out to him in case of queries.

/assign video

@adityabisoi please review my PR #562

/assign Audio


Enforcing IDE indent policy in the pom.

I think we're all using NetBeans on this project. If it's cool with both of you I'd like to enforce an indent policy so that we can stop seeing tab<->spaces diffs.

Fine with me.

Please leave IDE specific configuration out of the source code. Especially the pom. Either share a configuration file amongst ourselves, add it to the project and gitignore it or set it at the IDE level for each person working on the project.

Ivan, you assert what we should do without providing justification for why we should do it. Why? In general I don't want most IDE-specific configuration checked into source because it references resources that are individual to developers' workstations. I believe this case is exceptional because we are all using the same IDE, and we gain clarity in code review by enforcing workstation-invariant IDE configuration. The solutions you propose permit each developer to (forget to) have any indentation policy they want, and forces the rest of the team to waste time looking at the consequent messy diffs.

Sharing a configuration file amongst ourselves, add it to the project and gitignore it

That will fall out of sync. Devs will lose the file. New devs won't have the file. Space<->tabs diffs will ensue. This could be somewhat remedied by following the example of exampleContext.xml and context.xml. To be precise, we would check an example-nb-configuration.xml into source and tell new devs to copy it to nb-configuration.xml on clone, and tell existing devs to copy it whenever it is updated. This still suffers from the problem of individual devs being able to override the policy by modifying the indentation settings in their IDE's GUIs. Changes are written to nb-configuration.xml. The developer doesn't have to face the music of his/her noncompliance because the file is .gitignored.

set it at the IDE level for each person working on the project

This is essentially the same as the above, but with more opportunity for human error in clicking the right buttons in the GUI instead of reading them in from a file. This approach will fall out of sync even faster. Devs delete and re-clone repos, losing the nb-config file in the process. Since there is no file checked into the repo enforcing or describing an indentation policy, devs have no convenient means to get on the same page as the other devs on their team. Devs will erroneously apply settings from one project to another. Space<->tabs diffs will ensue.

I'd like to keep this open source project agnostic of things like IDE configuration. I see things like that  as a pollution to the code base.
We also can't guarantee that any future developers will be using NetBeans which renders this configuration moot.
Perhaps we can make use of a tooling-agnostic solution like https://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html
Thoughts?

I'm going to close this pull request without merging.


Reloading page in Safari causes new processes to spawn

Client: Safari 12.1 on macOS 10.14.4 via HTTPS with self-signed cert
Host: code-server 1.939-vsc1.33.1 on Ubuntu 18.04.2
When the page is reloaded - or closed and reopened - 2 new code-server processes will spawn on the server. This happens repeatedly, eventually consuming the majority of CPU and RAM on the host.
This doesn't appear to happen when using Chromium  71.0.3578.98 from the same client.

Very interesting. Do the logs show that the client is disconnecting from safari? Maybe we aren't catching a strange connection close...

That does seem to be the issue. When reloading in Chromium, the WebSocket closed message appears consistently in the logs. When reloading in Safari, no closed message appears, but a new WebSocket opened message does.


Fix FindClangTools.cmake

A long-standing pet peeve of mine is that FindClangTools.cmake isn't particularly portable. This can lead to clang tools not being found on certain configurations. This PR aims to fix that.
From #1067.

Will this potentially result in it finding a tool binary from a different version of LLVM if someone has multiple versions installed?

Yes. Since we've all been using CLion with its built-in clang-tidy and clang-format binaries without issue, I don't think that that should pose a problem. It is certainly an improvement over not working at all.

Yes. That's mostly the point of this PR: currently, we don't let people run clang-format or clang-tidy at all unless they have LLVM 8. This seems overly burdensome

That's what we want. It's impossible for people to pass CI if their tools don't match the same version. We've seen differences from one version to the next, even with the same checks. If someone wants to use a newer version on CLion then that's up to them, but the wiki has instructions on how to override that as well.

Understood. I'll close the PR, then.


Implement include-pattern

http://microformats.org/wiki/include-pattern

At the suggestion of @tantek I am not planning to implement this for 3.0.0 unless there is a call for it.  It never seemed to get much use.

Affirming @dissolve's comment. Additional conversation in the microformats IRC channel.
https://chat.indieweb.org/microformats/2017-05-13#t1494634396747000
17:13 [shaners] Does anyone use the `include-pattern` on their personal sites?
17:13 tantek hah we were just discussing that.
17:13 tantek AFAIK, it's usage has either fallen off, or never got traction with mf2 use-cases
17:14 [shaners] that’s been my anecdotal impression too
17:14 tantek that being said, one of its biggest use-cases, hResume, now h-resume, also hasn't gotten a lot of uptake
17:14 tantek so there is the reasonable possibility that if h-resume takes off, then so will include pattern once again
17:14 tantek HOWEVER, if no one implements include pattern in mf2 parsers, then perhaps that will present an opportunity to solve the h-resume use-cases differently (without depending on include pattern)
17:15 [shaners] +1
17:15 [shaners] Do the other mf2 parsers support include-pattern?
17:15 tantek so I'm willing to take a wait and see what "the market" does approach, and then re-evaluate the situ with that new information
17:15 tantek *maybe* microformats-shiv (the Node parser) because Glenn Jones is so thorough
17:16 [shaners] of course
17:16 [shaners] he really is

Closing this issue at wontfix for now. If something changes in the future, we can re-open it.


Filter option in search pane

The filter button option should be removed.

Easy to confuse with an 'enter' button
Default to type = pathways (Related to #7 ).

Fixed in commit 4fe14cf5a927d9fd005a058ec875fa70a01c1a65. I changed the filter button from a filter button to a Search button, which does the same thing as pressing enter.


Fix ci.yml

This is the reason why https://github.com/amphp/amp/pull/360 seems to be "hanging". It's because your CI configuration is kinda wrong - starting checks on both PRs and all branches means it's triggered twice. Which works on your own PRs (you just see double the checks) but breaks for cross-fork PRs. I think it expects the push checks to happen for the branch but they don't because it's on another fork.
I'm sadly not an expert on this matter but I saw it several times in the past already. Basically no cross-fork PR can ever get a success with this setup.
The common setup I see around is this:
on:
  pull_request:
  push:
    branches:
      - "master"

Basically run checks only on PRs and master. In your case I think it would be master, v3, and v3-revolt - basically all branches that are expected to be merged into / used as base branches for PRs.

This issue is caused by the branch protection rules rather than the workflow setup.


Use friendly branching name in push PR

since we merged dd38743f5cc6e422ab6a4aeca4245c83b0e26d32 we don't have to use
the full ref main for branch
related infra commit, https://github.com/openshift-pipelines/tekton-asa-code-infra/commit/41a4fa2939e9d2d1801ac39ade63ca447248a80f
Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>

/retest


docs(zh-cn): Reviewed 06_transformer-models-decoders.srt

#390

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Google Embedding

Is your feature request related to a problem? Please describe.
No, however, i thought to check if there's any chunks procedure already create for Google Gemini model embedding-001

Nope no usage of the Gemini models currently

How do they do the tokenization? If it is via the hugging face library then yes it would work

@loginatcode I will close this for now since I haven't heard back. Looking at the Google docs, it seems like they have some custom way of getting the number of tokens. You could do this in Rust by doing a custom impl of ChunkSizer, or in Python by using the from_callback method on either of the Splitters.
Hopefully that helps, and feel free to respond if this doesn't answer your question.


fix 'http headers' param in test-validation

The param is actually called 'HTTP HEADERS' and not 'HOSTHEADER'.
see: https://mmonit.com/monit/documentation/monit.html
Syntax:

 PROTO(COL) HTTP
     [REQUEST "string"]
     [STATUS operator number]
     [CHECKSUM checksum]
     [HTTP HEADERS list of headers]
     [CONTENT {= | != } STRING]

Ouch. This changed in monit 5.9 - see changelog https://mmonit.com/monit/changes/
We need to identify the monit version in use, and generate the config in concordance.

Or, at least in this case, accept both params and add a comment indicating when HOSTHEADER was deprecated and HTTP HEADERS started being in force.

thx for the feedback. i'll fix.

I've added both Params and also provided a sample config for hiera in README.md

Merged. Thanks!


Fix MPI compilation

Fixes #14558  introduced by 2ce0b9149741105795083c4bae8fb0b85cb9659d

Can one of the admins verify this patch?

Jenkins, test this please


refactor: clean up test file structure

This PR cleans up the test file structure to match /src.

Now this is confusing. Everything passes locally. I am not sure why the unit tests are failing in CI 🤔
Any ideas @oxy @TeffenEllis @code-asher ?


Please add cookies

Please add support for cookies

@Yiming828 after build() you are getting list of successful responses. All the responses are Response object. You can access cookies by res.cookies
For example, get the responses link this,
>>> response = fgreuests.build(urls, method='POST')
>>> print(response)
[<Response [405]>, <Response [200]>, <Response [200]>, <Response [200]>, None]

Now, you want to access the cookies of the first element of the response. You can do the following:
print(response[0].cookies)


Query with Where clause and In Operator returns wrong count

Query with Where clause and in operator returns wrong count. The issue does not present in shc:1.0.0-1.6-s_2.10 but the latest 1.1.1-1.6-s_2.10 has the issue. Below is the repro
Hbase Table and repro data:
hbase(main):005:0> create 'SHC','colfam1'
0 row(s) in 5.8380 seconds
=> Hbase::Table - SHC
hbase(main):006:0>  put 'SHC','ro1','colfam1:col1','val1'
0 row(s) in 0.6730 seconds
hbase(main):021:0> put 'SHC','ro1','colfam1:col2','val2'
0 row(s) in 0.0230 seconds
hbase(main):022:0> put 'SHC','ro2','colfam1:col1','val1'
0 row(s) in 0.0220 seconds
hbase(main):024:0>  put 'SHC','ro2','colfam1:col2','val2'
0 row(s) in 0.0210 seconds
hbase(main):026:0>  put 'SHC','ro3','colfam1:col1','xxx'
0 row(s) in 0.0550 seconds
hbase(main):029:0> put 'SHC','ro3','colfam1:col2','xxx'
0 row(s) in 0.0250 seconds
hbase(main):030:0>scan 'SHC'
ROW COLUMN+CELL
ro1 column=colfam1:col1, timestamp=1496832633772, value=val1
ro1 column=colfam1:col2, timestamp=1496832640358, value=val2
ro2 column=colfam1:col1, timestamp=1496832653773, value=val1
ro2 column=colfam1:col2, timestamp=1496832663550, value=val2
ro3 column=colfam1:col1, timestamp=1496832677218, value=xxx
ro3 column=colfam1:col2, timestamp=1496832689356, value=xxx
3 row(s) in 0.0780 seconds
hbase(main):032:0> exit
./spark-shell --packages com.hortonworks:shc-core:1.1.1-1.6-s_2.10 --repositories http://repo.hortonworks.com/content/groups/public/
import org.apache.spark.sql.execution.datasources.hbase
import org.apache.spark.sql.execution.datasources.hbase._
var cat = """{"table":{"namespace":"default", "name":"SHC","tableCoder":"PrimitiveType"},"rowkey":"key","columns":{"key":{"cf":"rowkey", "col":"key", "type":"string"},"id":{"cf":"colfam1","col":"col1","type":"string"}}}"""
val hbdf = sqlContext.read.options(Map(HBaseTableCatalog.tableCatalog -> cat)).format("org.apache.spark.sql.execution.datasources.hbase").load()
hbdf.registerTempTable("htb")
sql("select count(1) from htb").show
3
sql("select count(1) from htb where id in ('val1','xxx')").show
6
The above is suppose to return 3 but it returned 6.

Thanks @PrabhuJoseph.
I just reproduced this issue.
(1) I ran spark-shell with com.hortonworks:shc-core:1.1.1-1.6-s_2.10:
[ambari-qa@c6401 ~]$ spark-shell --packages com.hortonworks:shc-core:1.1.1-1.6-s_2.10 --repositories http://repo.hortonworks.com/content/groups/public/

Some commands and results:
scala> hbdf.show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> hbdf.registerTempTable("htb")

scala> sql("select * from htb").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> sql("select * from htb where id in ('val1','xxx')").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> sql("select * from htb where (id == 'val1' or id == 'xxx')").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

(2)
I ran spark-shell with com.hortonworks:shc:1.0.0-1.6-s_2.10:
[ambari-qa@c6401 ~]$ spark-shell --packages com.hortonworks:shc:1.0.0-1.6-s_2.10 --repositories http://repo.hortonworks.com/content/groups/public/

Some commands and results:
scala> hbdf.show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> hbdf.registerTempTable("htb")

scala> sql("select * from htb").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> sql("select * from htb where id in ('val1','xxx')").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

scala> sql("select * from htb where (id == 'val1' or id == 'xxx')").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

By comparing with (1) and (2), we can find that Spark has read data from HBase table SHC into Spark DataFrame hbdf correctly. If you use where (id == 'val1' or id == 'xxx') instead of where id in ('val1','xxx'), the results will be correct. So I think this issue may come from Spark itself or from the implementation of unhandledFilters() in SHC.  I'll debug more and update the root cause soon.
Let's know if you have any update. Thanks.
P.S.
In pom file, for com.hortonworks:shc-core:1.1.1-1.6-s_2.10, spark version is 1.6.3; for shc:1.0.0-1.6-s_2.10, spark version is 1.6.1.

It seems this issue was not from unhandledFilters() in SHC. After removing all the implementation of unhandledFilters() from SHC, the number of records returned from the following operation is still 6:
scala> sql("select * from htb where id in ('val1','xxx')").show
+---+----+
|key|  id|
+---+----+
|ro1|val1|
|ro2|val1|
|ro3| xxx|
|ro1|val1|
|ro2|val1|
|ro3| xxx|
+---+----+

Will debug more to confirm if this issue is from Spark itself.

So i just ran into this with the "IN" operator, and even though  i switched to  syntax like "where (id == 'val1' or id == 'xxx')"  the count is still wrong... when you use "show" the result is fine but the count is wrong.  Very odd.

I encounter the same bug.
df.show() returns 4 rows while df.count() is 9.


Use zlib::Flush::sync instead of zlib::Flush::full, for stream compre…

…ssion
https://github.com/boostorg/beast/issues/2313

I've noticed that this failed, due to lower code coverage. But its a little bit confusing, it shows that the code coverage dropped in this file(include/boost/beast/websocket/impl/read.hpp). Which was not modified by me, and also that file doesn't use the deflate() method that was changed.

This has passed all tests. Thank you for your valuable contribution.
I would welcome a suggestion on a test I could implement to prove that this is a fix/improvement.
R

The method that I've changed is this, I tried to find it's related test file, but I only found this, which is empty.
I saw that deflate() is used in this file, when write_some_op::operator() is called  or when write_some is called, so I think the test might be done here somehow.
The test that I was thinking about if we were to only test the deflate() method:

start with Hello string
call deflate(), the resulted string will be 7 bytes or will have this content: 0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00
call deflate() with the same string, and the result will be 5 bytes or will have this content: 0xf2 0x00 0x11 0x00 0x00

Which means that compressing the same string, results has two different outputs, the second time the size is smaller.
A better test would be to test this in the write_some method, because there we can also check that the client_no_context_takeover or server_no_context_takeover do actually work. So there would be two tests:
Test 1: Test where the sliding window is not used between writes

start with Hello string, role(server or client), server_no_context_takeover or client_no_context_takeover set to true(based on the role)
call write_some with that string, the resulted string will be 7 bytes or will have this content: 0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00
call write_some  with the same string, and the result will be 7 bytes or will have this content: 0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00

This is because server_no_context_takeover or client_no_context_takeover were set to true, so when this is called, it resets the compression stream, here.
Test 2: Test where the sliding window is used between writes

start with Hello string, role(server or client), server_no_context_takeover or client_no_context_takeover set to false(based on the role)
call write_some with that string, the resulted string will be 7 bytes or will have this content: 0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00
call write_some  with the same string, and the result will be 5 bytes or will have this content: 0xf2 0x00 0x11 0x00 0x00

This is because server_no_context_takeover or client_no_context_takeover were set to false, so when this is called, it won't reset the compression stream, here.
Hope this helps a little.

The coverage report is a tiny bit flaky, don't worry too much about it


How to use Kafka in wherehows

I want to integrate kafka into wherehows, and I have read the source relative.
But I am confused about what is the message producer (kafka is message middleware: producer and consumer, what does produce the message of some topic; the trigger is?), I have found that the consumer and processor in source code.
Hope anyone can help me

We are experimenting a new ETL pipeline using kafka, more specifically the MetadataChangeEvent. The intention is letting the source platform (or out own ETL job) to send metadata snapshots via this event to kafka system, and WhereHows will run the consumer to get kafka messages and write to DB.
We will have a more detailed documentation once we finalize the Event schema and the consumer.

Dear issue owner,
Thanks for your interest in WhereHows. We have recently announced DataHub which is the rebranding of WhereHows. LinkedIn improved the architecture of WhereHows and rebranded WhereHows into DataHub and replaced its metadata infrastructure in this direction. DataHub is a more advanced and improved metadata management product compared to WhereHows.
Unfortunately, we have to stop supporting WhereHows to better focus on DataHub and offer more help to DataHub users. Therefore, we will drop all issues related to WhereHows and will not accept any contribution for it. Active development for DataHub has already started on datahub branch and will continue to live in there until it's finally merged to master and project is renamed to DataHub.
Please check the datahub branch to get familar with DataHub.
Best,
DataHub team


Invidious: init

Motivation for this change
Packages invidious, an alternative frontend for YouTube. With this module, running invidious is as simple as this!
{
  services.invidious.enable = true;
}

By default it runs on http://localhost:3000

[x] Depends on https://github.com/NixOS/nixpkgs/pull/67510
[x] Depends on https://github.com/NixOS/nixpkgs/pull/67805

There are still some things to do before this is ready (marked as TODO in the code), but it's very much usable in its current state.

Well damn, the hash changed again:
hash mismatch in fixed-output derivation '/nix/store/idrw7vk3j8dvyxh2yjdnnmq6ildbyvq4-invidious':
  wanted: sha256:1z3s9qq6bzzgwjyijffy46cby2f8n03461a0ykpwsjhlyd9ls8bf
  got:    sha256:1y062ngy0wi6aa4bnz68c6jniy6c6bmz6lcvh40gz7c85rwqm23g

@jonringer Do you happen to have the previous path still? Would love if you could upload it so we can check the difference:
nix-store --export /nix/store/j02fmn53mbpgmw4ff1m430i62sspy80d-invidious > exported

Status? Has the nondeterminism been tamed yet?

At least for now the hash seems to still be correct.
Regarding the PR overall: I'm kind of stuck thinking about how to do a configurable database the best. Because what I really want is to run the database on one machine and the service on another. Reason is that invidious the service doesn't work well on servers because the IP there is easily blocked, so I want to run that always on the local machine. The data however should be on a single server, so it can be used by all service instances to serve the same data, such that I don't have to sync my subscriptions manually.
The current module however only supports a local database, which I did because then you don't need a database password (uses unix user authentication).
But now the thing is: When I enable the service with a local database on a machine, it shouldn't need a password. However in order for other machines running the service to access the database, they do need a password. So should I require a database password with a local database just in case other machines want to use it? Maybe I need an allowDatabaseFromOutside option. Also maybe I need a onlyDatabase option for when I only want to run the database on a machine and not the service.
Here's a mockup of what might work:
# Invidious options
{
  options = {
    # Turn this on to have a zero configuration local invidious working
    enabled = mkEnableOption "..";

    # Enable only the service
    enableService = mkEnableOption "..";

    # Enable only the database
    database.enable = mkEnableOption "..";

    # When password is not set only allow passwordless local unix user authentication
		database.password = mkOption {};
  };

  config = mkMerge [
    (mkIf cfg.enabled {
      enableService = mkDefault true;
      database.enable = mkDefault true;
    })
    (mkIf cfg.database.enable {
      assertions = [{
        # Require a password when the database won't used locally
        assertion = !cfg.enableService -> cfg.database.password != null;
      }];
    })
    (mkIf cfg.enableService {
      # ...
    })
  ];
}

@aanderse Maybe you have some opinions on this too?

I would go for the allowDatabaseFromOutside approach, it should be easy enough to implement and doesn't get in the way of users that simply want to run the service locally.
I still wonder if you could use something like munge: the database could continue using unix users as authentication but it would not be limited to local users. A shared secret between the two machines is needed but it would be optional.

Ah I didn't update my comment: Initially I thought about allowDatabaseFromOutside but then I thought that just password != null is a simpler version of that. Though I guess allowDatabaseFromOutside could also open the postgres port in the firewall, and it's also easier to discover when you need it. Yeah maybe the mockup above plus that option is the way to go.
munge sounds interesting, though I'd rather not tie this module to it :)

@Infinisil is there any issue with allowing authentication from either a password file or local socket authentication? If not, I would suggest a very small wiki document explaining such an unusual problem and the solution, with a snippet that can be pasted into configuration.nix, might be better than complicating the module with all sorts of code. Maybe an explanation stating under the scenario you described simply using passwordFile is the better option, deployed over multiple nodes.
If I have missed something simple I'm sorry, it has been a while and the conversation we had around this PR is a bit foggy in my mind.

Note: This is kind of blocked on https://github.com/omarroth/invidious/issues/923, I have no idea how to solve that issue. I could downgrade to version 0.19.1 which works, but that version doesn't play all versions because it doesn't have QUIC support, and 0.20.1 does have QUIC support but it doesn't run successfully, caused by the implementation of QUIC support..

I updated this PR to use the latest invidious version (they no longer provide releases and encourage users to use the latest development version). In the meantime the dependencies were simplified and it no longer segfaults.
I also removed the manual migrations, because it should now automatically do that when check_tables is enabled. That in turn makes it possible to avoid using fetchgit by also manually providing the branch, commit and version.
@Infinisil are you still interested in this?

Nice! I am still interested. I'm really quite busy recently though, so I'm not sure when I have time to update/test this. It might be better if you opened a new PR @sbruder with your updated commits

Awesome, above PR is merged!


Create snap

Internal Jira card: PEK-1308
This adds snapcraft.yaml and related files for the first iteration of the snap. See the README for more details on the snap design and usage. If you'd like to test locally you can install the snap with:
sudo snap install openvino-ai-plugins-gimp --edge

I've tested on my personal machine and on a Meteor Lake machine in the Locker equipped with a NPU and iGPU. I've also tested the integration of the snap with the GIMP snap running version 2.99.16. I'll open and link a related PR for that work shortly.
One important detail is that the size of the snap is quite large (half a gigabyte or so) primarily due to a PyTorch dependency. I expect this will make automated testing on testflinger instances challenging, as the connection to the Snap Store is often very slow.

Related draft PR in the GIMP snap repo: https://github.com/snapcrafters/gimp/pull/304

Looks good to me


Add .blue domain name for authenticating-proxy

https://trello.com/c/USH1B9K1/243-investigate-drying-up-deployment-healthchecks-out-of-smokey
Follow up to: 1.
This will become the target of a .govuk-internal CNAME 2 and will
allow us to request /healthcheck/ready on the app directly.

Planned and works on Integration ✅.
Will require recreating the node launch config, but I think that's benign. [Console log].


CPP/taskcpp/ArrayDynamicEmpty.cpp

Complete the task and attach a screenshot of your code and output. You may take the input yourself according to the task.

Hi @ela2003 , can you please assign this to me?


[SPARK 49109][SQL] Rename leftover BinaryLcase to Lcase

What changes were proposed in this pull request?
Renaming of all leftover binaryLcase to Lcase.
Why are the changes needed?
The code should follow proper naming.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No need for additional testing, it is a variable naming change.
Was this patch authored or co-authored using generative AI tooling?
No.

@cloud-fan Could you merge this renaming?

thanks, merging to master!