Fix perfdash after moving performance data to separate files

FYI @Random-Liu @dchen1107 - I want to wait for main repo changes to go in first, so that I can actually test this one. But this in theory should be enough.

This change is

It's done and working. @wojtek-t PTAL

/lgtm


JAX numpy mishandles certain 32-bit floating point operations as compared with numpy

**Might be related to https://github.com/google/jax/issues/8068 ? **
import numpy as np
import jax.numpy as jnp

(1 / 256 ** np.arange(1, 5)).astype(np.float32)
# output:
# array([3.9062500e-03, 1.5258789e-05, 5.9604645e-08, 2.3283064e-10], dtype=float32)

(1 / 256 ** jnp.arange(1, 5)).astype(jnp.float32)
# output:
# DeviceArray([3.9062500e-03, 1.5258789e-05, 5.9604645e-08,           inf],            dtype=float32)

The "inf" part seems like a bug. I can represent the numbers correctly individually, as in
jnp.float32(1/256**4)
# output: DeviceArray(2.3283064e-10, dtype=float32)

It just breaks for this particular version of that same computation...

This is integer overflow. If 64-bit types aren't enabled, you get:
In [3]: 256 ** jnp.arange(1, 5)
Out[3]: DeviceArray([     256,    65536, 16777216,        0], dtype=int32)

Try setting JAX_ENABLE_X64=1 to enable 64-bit types. Alternatively, perform the exponentiation on floats:
In [6]: (1 / 256. ** jnp.arange(1, 5)).astype(jnp.float32)
Out[6]: DeviceArray([3.9062500e-03, 1.5258789e-05, 5.9604645e-08, 2.3283064e-10],            dtype=float32)

Closing because I don't think this is a bug in JAX. We're already working on enabling x64 mode by default, and I think catching integer overflow would be a big project and not something we would want to enable by default even if we could do it.

Sorry for the noise, in that case, and thanks for the quick assistance!


Maximum Sum Increasing Subsequence in C | GSSoC'21 | Dynamic Programming

💥 Proposal
Maximum Sum Increasing Subsequence in C
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Add rule importer to backfill

This PR implements a solution for issue #11 to add the ability to retroactively evaluate new rules so that there is historical data for new rules. For details see design doc here.
This PR includes the following code changes:

creates a rule importer. The rule importer parses recording rule files and creates tsdb blocks of recording rules from historical prometheus data.
creates a promtool subcommand  promtool tsdb create-blocks-from rules to execute backfilling data for a new rule
the output of the subcommand is a directory that contains blocks with the series created from evaluating the recording rules on old data

Things not in the PR that must be added:

add documentation in the "storage" page (ref)
add stale markers

Things not in this PR, but might be nice to add at a later date:

long running service to backfill any amount of data
backfill alerting rules
ability to move the output blocks to a prometheus data dir and perform validation before doing so

Example usage:
$ promtool tsdb create-blocks-from rules --start=1606382352 --end=1606389552 \
    --output-dir <path/to/dir/to/write/data> \
    --url <prometheus api addr and port> \
    rules1.yml,rules2.yml

Let us know if it's ready to review! (:

Sorry for the slow rely to comments (had some life stuff to take care of).  I'm back at it now and aiming to have this PR ready for review in a week. Will ping you all when its ready.

@bwplotka and @brian-brazil I made some changes per your comments, not sure if I'm handling the alignment correctly and the queryRange API right. I would appreciate another review when you all have a free moment. Thanks so much for the help!

Did you forget to push?

Can we just hardcode 2 hr blocks for now and make it a flag another day if needed?

It should be a flag from the start I think, so you can pass in a smaller value if you've an expensive query.

I will add a flag, I will push a change in a bit.

I have not looked at the implementation yet, but wanted to say that as with the normal backfill, we need to align the block boundaries of new blocks being created with existing blocks to avoid formation of a single huge block (vertical compaction merges all overlapping block into one).

Ups, misclick I did not plan to put green mark yet ;p But very close!

I collected a few thoughts about the command structure here, roughly continuing where we just ended the sync meeting.

This was close to being merged, are you around @JessicaGreben to merge this in? (:

Its not quite ready. Needs a little more testing, but almost there. I have been busy with other things, but I can get back on it this week.

Thank you! Did you notice that the tests are failing?

oops let me fix those failing tests

As per message from @roidelapluie, merging this now.

Wow, heroic year-long effort.  Well done!

Hello @JessicaGreben, when I discovered about this feature in the Medium article you wrote, I had to find this PR, to thank you. You are reducing my pain with Prometheus rules. Thanks again.


fix: scale-up new node bug

Describe what this PR does / why we need it
Does this pull request fix one issue?

Fixes #1998
Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 18.34% // Head: 18.34% // No change to project coverage :thumbsup:

Coverage data is based on head (f4c554f) compared to base (866a48f).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2038   +/-   ##
=======================================
  Coverage   18.34%   18.34%
=======================================
  Files         101      101
  Lines        9222     9222
=======================================
  Hits         1692     1692
  Misses       7299     7299
  Partials      231      231

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

confirm this PR can fix #1998?


@Environment(\.dismiss) no longer works when using 0.3.5

Hi there!
Sorry, don't currently have a shareable reproduction case, but the change made in 0.3.5 seems to have broken the SwiftUI native @Environment(\.dismiss) action. The view that's presented by a TCARouter does not actually dismiss correctly. In my TCA state, nothing changes either when I press a button that calls the Environment's dismiss in a view.
I'm using TCACoordinators, but the issue doesn't appear to be specifically with TCACoordinators – if I pin my app to FlowStacks 0.3.4, everything works great. If I pin to 0.3.5, it breaks and @Environment(\.dismiss) stops working.
The issue affects both iOS 16 and iOS 17 – I've tried it on both iOS 16.4 and iOS 17.0.1/17.2 sims, and the issue persists. Given the only other non-iOS 17 change that exists is wrapping a screenView in a ZStack, I wonder if that's the particular issue I'm encountering. I'm just wondering if the screenView needs the whole @Environment propagating to it perhaps? I dunno, I'll give that a try and PR if it fixes things!
I'll try and get a reproduction case up soon as well, but I thought I'd better report the issue sooner!

Thanks for finding this @rhysm94! I did a quick test and it seems that wrapping screenView in a ZStack is indeed the culprit. Here's the context for that change - it seems the 'unintended consequences' I feared have come to roost! Given that the reason for adding the ZStack was a lot more niche than the use of @Environment(\.dismiss), and can be worked around in user code, I think removing the ZStack would be the best course of action, but I'll have a play and see if I can find a way to keep both fixes.

Sorry I didn’t quite get round to producing a repro. case for you this evening, but glad it hopefully wasn’t too difficult to find.
Shame it’s not possible to propagate a dismiss action through the environment, as I imagine that would be a fix, but \.dismiss is only  KeyPath, not a WritableKeyPath 😭

I've removed the ZStack wrapper in version 0.3.8. Thanks @rhysm94!

I've removed the ZStack wrapper in version 0.3.8. Thanks @rhysm94!

Fab, thank you! Much appreciated 😄


Use the nonmissingtype function

Codecov Report

Merging #52 (7ed34b0) into master (23cafca) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   94.42%   94.42%
=======================================
  Files           6        6
  Lines         269      269
=======================================
  Hits          254      254
  Misses         15       15

Files Changed
Coverage Δ

src/abstractgeotable.jl
99.00% <100.00%> (ø)


Added ability for callbacks to poll promises for fulfillment value

This will allow a callback native to libgit2 to actually have a promise value be returned in the callback eventually. We'll be able to not pause the JS thread while we wait for authentication or any other callback that is triggered from the V8 side.

I still don't understand, why not to use the Bluebird-lib?

This PR is superseded by https://github.com/nodegit/nodegit/pull/854


Can't use traffic mirroring capabilities of Kmesh

What happened:
Can't use traffic mirroring capabilities of Kmesh:
Completed the task of transferring all traffic to v1:

Failed to the task of traffic mirroring:

What you expected to happen:
Traffic from v1 should be mirrored to v2
How to reproduce it (as minimally and precisely as possible):

https://istio.io/latest/docs/tasks/traffic-management/mirroring/#before-you-begin
As we worked in ambient mode, I deploied a waypoint pod for 'httpbin' service. Refer to https://kmesh.net/en/docs/userguide/install_waypoint/
When I refered to https://istio.io/latest/docs/tasks/traffic-management/mirroring/#creating-a-default-routing-policy, error happened as: error: error parsing STDIN: error converting YAML to JSON: yaml: line 6: did not find expected key. So I post my yaml here.

kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1
kind: VirtualService
metadata:
  name: httpbin
spec:
  hosts:
    - httpbin
  http:
    - route:
        - destination:
            host: httpbin
            subset: v1
          weight: 100
---
apiVersion: networking.istio.io/v1
kind: DestinationRule
metadata:
  name: httpbin
spec:
  host: httpbin
  subsets:
    - name: v1
      labels:
        version: v1
    - name: v2
      labels:
        version: v2
EOF

kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1
kind: VirtualService
metadata:
  name: httpbin
spec:
  hosts:
    - httpbin
  http:
    - route:
        - destination:
            host: httpbin
            subset: v1
          weight: 100
      mirror:
        host: httpbin
        subset: v2
      mirrorPercentage:
        value: 100.0
EOF

Then test refer to the istio website

kubectl exec deploy/sleep -c sleep -- curl -sS http://httpbin:8000/headers
kubectl logs deploy/httpbin-v1 -c httpbin
kubectl logs deploy/httpbin-v2 -c httpbin

Anything else we need to know?:
Environment:

Kmesh version:
Others:

The mirror-related config has indeed issued, because it already contains requestMirrorPolicies field:
    {
        "name": "inbound-vip|8000|http|httpbin.test.svc.cluster.local",
        "virtualHosts": [
            {
                "name": "inbound|http|8000",
                "domains": [
                    "*"
                ],
                "routes": [
                    {
                        "match": {
                            "prefix": "/"
                        },
                        "route": {
                            "cluster": "inbound-vip|8000|http/v1|httpbin.test.svc.cluster.local",
                            "timeout": "0s",
                            "retryPolicy": {
                                "retryOn": "connect-failure,refused-stream,unavailable,cancelled,retriable-status-codes",
                                "numRetries": 2,
                                "retryHostPredicate": [
                                    {
                                        "name": "envoy.retry_host_predicates.previous_hosts",
                                        "typedConfig": {
                                            "@type": "type.googleapis.com/envoy.extensions.retry.host.previous_hosts.v3.PreviousHostsPredicate"
                                        }
                                    }
                                ],
                                "hostSelectionRetryMaxAttempts": "5",
                                "retriableStatusCodes": [
                                    503
                                ]
                            },
                            "requestMirrorPolicies": [
                                {
                                    "cluster": "outbound|8000|v2|httpbin.test.svc.cluster.local",
                                    "runtimeFraction": {
                                        "defaultValue": {
                                            "numerator": 100
                                        }
                                    },
                                    "traceSampled": false
                                }
                            ],
                            "maxGrpcTimeout": "0s"
                        },

But an error was reported during the access:
kubectl exec -n deploy/sleep -c sleep -- curl -sS http://httpbin:8000/headers
curl: (7) Failed to connect to httpbin port 8000 after 1 ms: Could not connect to server
command terminated with exit code 7

In addition, Under ambient mirror related config is also issued, but will not take effect as well.
Further research is needed.


ref(scheduler): generate secrets manifest for create and update secrets

Move to the same model as Pod building. Also moves update secret to generate a whole new object to overwrite the previous one instead of just updating the data element
Unifies the base64 encoding and how labels are applied
This may help fix #862

[Current coverage][cc-pull] is 86.81%

Merging [#863][cc-pull] into [master][cc-base-branch] will increase coverage by 0.10%

@@             master       #863   diff @@
==========================================
  Files            30         30
  Lines          2746       2745     -1
  Methods           0          0
  Messages          0          0
  Branches        453        453
==========================================
+ Hits           2381       2383     +2
+ Misses          239        238     -1
+ Partials        126        124     -2

Powered by Codecov. Last updated by [0fa78f0...d5b8396][cc-compare]
[cc-base-branch]: https://codecov.io/gh/deis/controller/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/deis/controller/compare/0fa78f0baa8aacb5836b9825817e45e579704ce4...d5b83966d409551012f0051a7df76a02425d0ea2?src=pr
[cc-pull]: https://codecov.io/gh/deis/controller/pull/863?src=pr


Improve empty result messages

This PR replaces the WARNING: nothing to output message in the cases we can output something more useful.
For example (using the test bench outputs)
cargo benchcmp bench_output_4.txt bench_output_5.txt --threshold 2 --improvements
yields
All (2/2) improvements are within a 2% threshold
Changes

Add 0/$n benchmarks improved message
Add 0/$n benchmarks regressed message
Add All ($n) benchmarks are within a $t% threshold message
Add All ($r/$n) regressions are within a $t% threshold message
Add All ($i/$n) improvements are within a $t% threshold message
Update dependencies

@BurntSushi let me know if you can take a look at this, I'll otherwise close this PR in a few days.

@alexheretic Thanks for the ping and the PR! This seems fine to me.


Fix vesting logic

Previously, the vesting_balance was used to deduce if a vest was finished. This is problematic since it will be clamped at free_balance and thus is free_balance happens to be temporarily zero then (e.g. because the vesting schedule is placed on an account before the funds are transferred as in claims.rs) then the schedule will be insta-dropped.
This checks with the underlying vesting schedule, ignoring the free balance and will only drop if the schedule is actually over.

Isn't the implementation of vesting_balance still invalid?
Shouldn't it return what currently is stored in the lock for vesting?

No, vesting balance is correct.
In general the amount locked for vesting (unvested) will be at least the free_balance, and as such the amount of funds that will eventually vest (vesting_balance) is equal to unvested. However, in the case that unvested is greater, then the amount of funds that will eventually vest is not that but free_balance. In general then it's the minimum of the two.


MTG-8 use latest version of shared pipeline

What does this PR do?
Bump the pipeline dependency (cf dd-source#21171 )

Codecov Report

Merging #1201 (1301b7f) into develop (e707d40) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1201      +/-   ##
===========================================
+ Coverage    82.31%   82.33%   +0.03%
===========================================
  Files          353      353
  Lines        11795    11790       -5
  Branches      2007     2005       -2
===========================================
- Hits          9708     9707       -1
+ Misses        1475     1474       -1
+ Partials       612      609       -3

Impacted Files
Coverage Δ

...rsistence/file/batch/PlainBatchFileReaderWriter.kt
86.27% <0.00%> (-2.94%)
:arrow_down:

...d/v2/core/internal/storage/FileEventBatchWriter.kt
95.24% <0.00%> (-2.38%)
:arrow_down:

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
86.70% <0.00%> (-0.49%)
:arrow_down:

.../kotlin/com/datadog/android/v2/core/DatadogCore.kt
89.86% <0.00%> (-0.46%)
:arrow_down:

...n/com/datadog/android/v2/core/SdkInternalLogger.kt
80.77% <0.00%> (ø)

...ndroid/telemetry/internal/TelemetryEventHandler.kt
72.27% <0.00%> (ø)

.../android/rum/internal/domain/scope/RumViewScope.kt
95.42% <0.00%> (+0.18%)
:arrow_up:

...android/log/internal/domain/DatadogLogGenerator.kt
97.32% <0.00%> (+1.34%)
:arrow_up:

...in/com/datadog/android/log/internal/LogsFeature.kt
91.94% <0.00%> (+3.23%)
:arrow_up:

...droid/rum/tracking/FragmentViewTrackingStrategy.kt
78.85% <0.00%> (+3.85%)
:arrow_up:

... and 2 more


Clue scroll kc chat command

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
I would like to show off my clue kc in chat. For all tiers but especially per clue tier. Just like with bosses. Otherwise I got to 1150 medium clues for nothing.''
For example, a chat command;
!Kc easy clue
!Kc medium clue
etc...
Describe alternatives you've considered
Additional context

!clues (easy/medium/hard/elite/master/all) already does this.


getCompletedData changes

Description
Resolves #1169
Blocked by #1155
Previously; getCompletedData did not fill missing x values for categorical data (e.g. color). This led to visible oddities for stacked charts
Checklist

[x] I have added a changeset

@ItsMeBrianD chart testing section looks good!

🚢


HttpClient.Timeout usage.

Having an issue setting a timeout value for the HttpClient Class.  myHttpClient.Timeout(60); Compiles, but then throws a run time exception.   Also, could someone clarify the type of the parameter to the method.  The documentation indicates seconds, but code assist types the parameter as duration.

Thanks for the feedback. We're working on improving the documentation for these classes, these will be available with one of the next refreshes of the docs.


[TypeScript SDK] New version bug, Could not serialize argument of type U64 at 7 into u64

Methods that worked before now don't work

it's due to the sui version update,
so you need to trans u64 to hex string
plz check:
https://github.com/MystenLabs/sui/releases/tag/devnet-0.20.0
https://docs.sui.io/build/sui-json

it's due to the sui version update, so you need to trans u64 to hex string
plz check: https://github.com/MystenLabs/sui/releases/tag/devnet-0.20.0 https://docs.sui.io/build/sui-json

Thank you for your reply, I have solved the problem.


Add missing file...

Add missing file that seems to be being required by Anura.
Cheers and regards,

I discovered mint tictactoe is working OK now. Bisecting http://github.com/anura-engine/anura it seems its rev 1127b8e5cd26cd165d4896a77e1e209832f7aeda (https://github.com/anura-engine/anura/commit/1127b8e5cd26cd165d4896a77e1e209832f7aeda) fixed the underlying issue.


add pf-net

Submit pf-net as the final project of 百度顶会论文复现营

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


Opening TPBs

When trying to open a TPB, it loads a Mummy one for some reason.

I'm a little late responding... could you tell me what TPB?

Trade Paper Back, though I haven't used the app in a few years now.


Prefix vars to prevent conflict with other roles

Great callout with this PR - will definitely merge. Do you think the prefix be more specific to this role, e.g. artis3n_tailscale_?

CI errors are due to https://github.com/artis3n/ansible-role-tailscale/issues/279 , will re-run in a bit.

I think just using tailscale as prefix is fine. The only conflict that I came across until now is in https://github.com/dev-sec/ansible-collection-hardening/blob/154f862ccd839ee72f771895d4ee0f956327a686/roles/os_hardening/tasks/yum.yml#L16

Sounds good to me. While these vars shouldn't be modified by end users, renaming them technically breaks backwards compatibility so I'll hold off on merging until I'm ready to create the next major version bump.
Want to get https://github.com/artis3n/ansible-role-tailscale/issues/276 done in the next few days, then I'll merge both and we'll push out a new release.


OData v4 is not working for Northwind

OData v4 is not working for Northwind
https://services.odata.org/v4/northwind/northwind

Same for odata v2 https://services.odata.org/v2/northwind/northwind.svc/Products.
Message: Login failed for user 'odataNorthwind'. Reason: Azure Active Directory only authentication is enabled. Please contact your system administrator.

Same issue for the following service: https://services.odata.org/V4/(S(readwrite))/OData/OData.svc/
Looks like the same error message.
Would be helpful is someone have a look to this.


Add init process for zombie fighting

This adds a small C binary for fighting zombies.  It is mounted under
/dev/init and is prepended to the args specified by the user.  You
enable it via a daemon flag, dockerd --reaper, as it is disable by
default for backwards compat.
You can test this by running a process like this as the pid 1 in a
container and see the extra zombie that appears in the container as it
is running.
int main(int argc, char ** argv) {
	pid_t pid = fork();
	if (pid == 0) {
		pid = fork();
		if (pid == 0) {
			exit(0);
		}
		sleep(3);
		exit(0);
	}
	printf("got pid %d and exited\n", pid);
	sleep(20);
}

We probably also need a per container flag to disable the reaper when it it turned on via the daemon for those containers that want to run as pid1.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

# dockerd -s overlay -D --reaper 2>/daemon.log &
# docker run busybox /nosuchfile
error: No such file or directory
# echo $?
1

# dockerd -s overlay -D 2>/daemon.log &
# docker run busybox /nosuchfile
docker: Error response from daemon: oci runtime error: exec: "/nosuchfile": stat /nosuchfile: no such file or directory.
# echo $?
127

We should add an option to run integration-cli with both modes. I'm sure we have a test for this case.

Looks like this will resolve #3793

Ok, so as far as flags go, @tonistiigi and I talked about this some.  We are not totally sold on what the flag name should be but we have a good idea on how it should work.
On the daemon we will have a bool --init flag.  This will be false by default, and if set to true, will run the custom docker init in every container.
On run, we will also have a --init flag that is a nullable bool.  If it is not set, we use the daemon default.  If it is set to true, we use the docker init for the container, if it is --init=false we will not use the init.  This allows us to have bot a daemon wide option and the ability to enable/disable per container, without changing anything for users that don't have this set.
If anyone has a better idea for a flag name let me know.

Updated this to use --init for now on both the daemon and run.  You can try out all the various combinations.

Moving this to code review: I think there no big controversy on the design :+1: I agree with everything in that comment https://github.com/docker/docker/pull/26061#issuecomment-243883226.

Small questions regarding tests, otherwise LGTM :+1:

found a typo, but LGTM otherwise.

:heart_eyes: any way we'll be able to turn this on by default at the image metadata level at some point? (since the author of a particular software image is likely to be able to tell whether or not a particular bit of software is going to be making zombies and thus need reaping)
I've got several images that use either tini or dumb-init for this purpose currently that I'd love to replace with some metadata telling Docker that each image needs this new /dev/init behavior. :heart:

@tianon yes, we will add a dockerfile instruction

fixed the typos , merge'n

congrats!

Curious why a new implementation of a docker init system was chosen over other implementations which have tests, many more users, and likely fewer bugs such as:

https://github.com/Yelp/dumb-init/
https://github.com/krallin/tini

+1, thanks for working on it @crosbymichael! That's awesome!

is the /dev abuse really a good idea?
i recall discussion about /run because vendors abused /dev for their early boot dirty work:
https://lists.fedoraproject.org/pipermail/devel/2011-March/150031.html
perhaps just use file named docker-init (or .docker-init) in root filesystem or /lib or /sbin?

That's a nice improvement to get docker handle this PID1 issue. But I'm concerned this moves the responsibility to run with --init option into end users hands. For sample, the jenkins docker image uses tiny for same purpose, but end user don't have to even know what a zombie process is.
I suggest one could use some metadata in image to let runtime know such init process is required, for sample by adding to Dockerfile: LABEL io.docker.init='true'

I suggest one could use some metadata in image to let runtime know such init process is required, for sample by adding to Dockerfile: LABEL io.docker.init='true'

In cases where a zombie reaper is required (in most cases, it should not even be needed), it should be added by the image author. I think this PR should be seen as a "last effort" if the image is not under control of the user.

Did the Dockerfile instruction to enable this by default at the image level
we discussed make it in to 1.13? :innocent:


Is User and Group only identities capable for MFA?

What about Service Principals? Is it capable for MFA?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a586047b-a3f3-9cc7-5408-e06f81c1ff99
Version Independent ID: 5a6f9e74-2859-6f44-1ec4-9fada1441df5
Content: Azure Multi-Factor Authentication overview
Content Source: articles/active-directory/authentication/concept-mfa-howitworks.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@CharmanderJieniJieni Thanks for your comment. We will review your issue and  get back to you shortly.

@CharmanderJieniJieni, MFA's doesnt qualify for Service Principals, since Service principals cannot perform interactive auth processes. Service Principals are mostly used by apps to perform silent logins where no human interventions are needed and MFA doesnt need a human interaction.
Hope this helps.
Closing the thread for now. Do let us know in case any more queries around this.


[SEI-6004] [BUG] - Local Javascript Sei Wallet Connect can't connect to LocalSei running on own machine.

Seid version
name: sei
server_name: <appd>
version: 3.0.9
commit: 6baf4dda89d5c5200883d86813cbfa6796fe09ef
build_tags: netgo,ledger
go: go version go1.21.0 darwin/arm64
build_deps:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>=><EMAIL_ADDRESS>
Chain ID
Local Chain: sei-chain
Describe the bug
So, Keplr Wallet does allow you to specify your own set endpoints/chain name: see here, but it has to be pushed from the page's javascript.
There are two things blocking this:

SeiWalletConnector, does not have this setup to pass the local chain id to Keplr. There is a devnet setup in Keplr, but you can't use that for local-dev because the chain-ids must match (or the SeiWalletConnector has to instantiate the new chain). You can see this is a bug (despite the second issue) because with testnet, you must first pre-register the testnet in Keplr.
Sei is not setup for CORS to work:

To Reproduce
Steps to reproduce the behavior:

Download the front-end tutorial.
Change the wallets, and add in keplr to the possible wallet connections.
Run the local sei node.
Update the front-end application to change the endpoints to the local chain.
Try to connect to Keplr from the site [will fail due to CORS]
You can change the front-end to connect to the testnet, and you will see Keplr fail again (because you have to pre-add the testnet). You shouldn't have to do that, it should recommend to add the testnet.

From SyncLinear.com | SEI-6004

The issue with CORS is still here. All the requests from a locally running frontend application fail due to the cors error coming from http://<IP_ADDRESS>:26657/


beforeLink hook does not work as expected

Hey there 👋,
The beforeLink  hook doc says it should be able to prevent linking depending of what it returns.
Even if I return false, true, or whatever in my hook, the each will ignore the result of the callback and LinkUserFromExternalService  will continue its execution and allow linking.
See that block
I workarounded this problem by manually removing the connection in the onLink hook, but that's not very clean :(

Hi @uuuJ
Can you please check that #101 fixes the issue for you?

Hi 👋,
I tried the same things as @uuuJ and return false in the Accounts.beforeLink seems to cancel the link but I'm facing another problem :
When I return false I have the following meteor error : "A login handler should return a result or undefined".
So I tried to return undefined but same result.
I would like to know if I miss something or there is a problem with the code ? Thanks 🙏


Linux corrupted install

Hi, so I messed with this til late, and am now on the phone.  Essentially the references to  3rd/bee*/ inside Linux.ninja were one directory too deep.  I manually fixed this with a nasty find/replace, renaming everything ../3rd/bee* to jump up a directory.  This mainly affected/corrected the '.cpp' files.  It now built, correcting the same error seen here:
https://www.reddit.com/r/neovim/comments/m3m5ya/neovim_as_a_lua_ide_autocomplete_diagnostics_and/
However the next issue was the luamake rebuild command was also at the wrong directory depth.  I pulled it one level higher and again, now it now ran.  However in the end this didn't yield a functional install, and it wiped my '.config/neovim' folder (which was no issue, but clearly the directory depth for cleanup was mismatched after moving luamake rebuild)
I didn't find the correct original references to the $PWD or $PATH that were wrong.
To clarify, I do have the 0.5 nvim LSP which is working great for me.  However I was hoping to get the love2d language references which aren't supported in that version.
Anyway hope this helps

I do not understand you.
Are you trying to say that there is an error in the compilation process provided by this wiki https://github.com/sumneko/lua-language-server/wiki/Build-and-Run-(Standalone) ?

Yes that's it :)
But I believe the linux.ninja file contains incorrect working directory reference and the luamake rebuild as well.  The build guide won't give a functional install for Linux

I can't reproduce it.


Bug: dedupe handleVoteUpdateByRepo function

Describe the bug
Any part of the website that can be used to vote requires posthog and as such the handleVoteUpdateByRepo function should be deduplicated and moved to the lib folder.
Steps to reproduce
Duplicated code exists in:

[ ] PostList.tsx
[ ] PostGrid.tsx
[ ] HotRepositories.tsx

Affected services
hot.opensauced.pizza
Platforms
No response
Browsers
No response
Environment
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

.take

having errors related to line breaks after pulling updates from the main repo...

Can any propose a fix to this? would appreciate

having errors related to line breaks after pulling updates from the main repo...

Can any one propose a fix to this? would appreciate

npm run format should fix the issur - it's complaining about line endings (which are windows atm). When commiting, git sets them to LF (unix).
This should be a better way to fix it: https://stackoverflow.com/questions/2517190/how-do-i-force-git-to-use-lf-instead-of-crlf-under-windows

having errors related to line breaks after pulling updates from the main repo...

Can any one propose a fix to this? would appreciate

npm run format should fix the issur - it's complaining about line endings (which are windows atm). When commiting, git sets them to LF (unix).
This should be a better way to fix it: https://stackoverflow.com/questions/2517190/how-do-i-force-git-to-use-lf-instead-of-crlf-under-windows

Thanks @0-vortex, you the boss :)


Issue #20: personalizing script with user location and contact name (WIP)

This is "working" but we have not gotten the Script component under test and would like to do that before completing the issue.

It looks like the script test file is empty - so Jest is complaining about there being no tests in what is supposed to be a test file.
If you want to add tests here, try copying one of the snapshot tests from Call.test.tsx and replacing it with the script component, snapshot makes sense for this type of test.

Re: the funky test result we discussed in slack, here was the proposed solution for the moment:
Use a similar method to export const ContactOfficesTranslatable = translate()(ContactOffices); that appears in ContactOffices.tsx.
Requiring full instances of the i18n-react for each test isn't ideal but I'm not quite certain how to work around the issue at the moment. We can refactor at a future time.

Thanks @nickoneill, I committed this so that @lnathanson can finish up the tests. 😄

Perfect, thanks!

Hi all - I'm going to merge this in and add a snapshot test to verify that this component doesn't change unexpectedly. If you have other plans for more concrete tests of functionality, please send a new PR!
Thanks for your help on this!


Add support for SCHED_{CLS,ACT} progs

It should have examples explaining how to attach it to a qdisc. Since the PR does not have functions to hook the bpf programs to a qdisc, I guess you can do it manually by pinning the programs on bpffs and calling tc? Did they add parameters for that in the tc CLI?

I guess you can do it manually by pinning the programs on bpffs and calling tc? Did they add parameters for that in the tc CLI?

object-pinned is supported. I will ll try to put together a small example.

I guess you can do it manually by pinning the programs on bpffs and calling tc? Did they add parameters for that in the tc CLI?

object-pinned is supported. I will ll try to put together a small example.

I have updated the commit message (d16f63bd8810465ee11c8f8c46131b5215e1d106) with a tc example.
I have also added 4f9e9bc784957dcbd68d1d4859c376acff00b445 as an alternative way to pin an object.


terraform_0_14: 0.14.6 -> 0.14.7

Motivation for this change
Things done

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

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

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

Result of nixpkgs-review pr 113478 at 75527979 run on x86_64-linux 1

1 package built:

terraform_0_14

4 suggestions:

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:143:9:
    |
143 |         ./provider-path.patch
    |         ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:144:9:
    |
144 |         (fetchpatch {
    |         ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:155:17:
    |
155 |     patches = [ ./provider-path.patch ];
    |                 ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:163:17:
    |
163 |     patches = [ ./provider-path.patch ];
    |                 ^

@GrahamcOfBorg build terraform.full


VEGA-2330 Add module to disable button after click #minor

Existing methods were not suitable, for the following reasons:

The data-prevent-double-click module in govuk design system does not change the appearance of the button after clicking.
Our app-loading-button module expects a message element to exist (which is populates). It also blocks the form submit.

Change to a submit input (that's what it is), and add a function which will not block the submit of the form.
Checklist

[ ] I have updated the end-to-end tests to work with my changes
[ ] I have added styling for Dark Mode
[ ] I have checked that my UI changes meet accessibility standards

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

Comparison is base (e2dc6c6) 76.45% compared to head (41670ca) 76.45%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #478   +/-   ##
=======================================
  Coverage   76.45%   76.45%
=======================================
  Files         104      104
  Lines        3334     3334
=======================================
  Hits         2549     2549
  Misses        482      482
  Partials      303      303

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

QA passed by Katie Gibbs 2024-02-28 12:10


[examples] Given by each projects

[ ] Load and Save asymetric
[ ] A field changes, an other field need to be updated
[ ] Blur validation
[ ] List field (with mass edition)
[ ] Two blocs (intricated) using the same store node (difficult to sync)
[ ] Validation custom on the block level
[ ] Validation custom on the field level + domain validation
[ ] A component state change is triggered and the state is reread from the store (all what was typed) by the user disapeared
[ ] Initial states of the page (vs read from the stores)
[ ] Useless load
[ ] Page without edition mode but who needs a displayFor must use the formBehaviour => More separation is needed.
[ ] wizard example
[ ] Easier to access buttons

Projects: [CHA, CRF, ATL, STI, AGA]

@Bernardstanislas Hope you will find time to do this (please focus on all the examples with middleware and add as manny comment / doc as you can)
Thanks!


Remove unused key handling functions

When the keyring length was changed and ipsec keys were introduced in later RCs of 1.12 release previous version of key rotation handling was left around to handle transition from older to newer RC. For the 1.12 release the cluster has to be initialized afresh. Removing the unused functions and adding a check for number of keys.
Signed-off-by: Santhosh Manohar<EMAIL_ADDRESS>

@sanimej There is a CI failure related to your change.

@mrjana Fixed it. PTAL.

LGTM


SAKIII-4517 - Collections don't have an icon in the dashboard, just show...

https://jira.sakaiproject.org/browse/SAKIII-4517

merged via squash


Don't implement WebSocket Protocol from scratch

There is no need to maintain code that implements the websocket protocol. Just wrap the TcpClient stream with a factory method from the System library System.Net.Sockets.WebSocket.CreateFromStream(client.GetStream(), true, null, TimeSpan.FromSeconds(n)) and you get all the functionality for free.

you still need the negotiation step, but saves you from having to read and write data frames


Moved go and java model generation into gen package

From the ardielle-tools repo, to encourage reuse. Bumped version to
1.5.1.

The regression was introduced by b919d345f28a6a119110ec3a245c24ec25c100c5, where a generated file was hand-edited.

The go formatting (and go vet) were not run on those new files. This is fixed now.
The lack of warning was only on the generated xxx_schema.go file generation, that is also fixed.
The whole bootstrap could be made clearer, but I think it is more than just go generate. Part of this PR is to move model generation into this library package, from the tooling package. I find that keeping them in sync for bootstrapping is a pain when in separate repos. But that fix would be for another time. All of the codegen stuff needs a cleanup, if anybody has time to contribute :-)


How to influence on the displayed project name?

Hi!
Is it possible to influence on the project name that is displayed in the GUI?

It becomes quite confusing if there many projects...
Thanks
Enno

@larshp do you think that's something we should implement?

yea probably, just dont make it too complicated

maybe a simple additional file for additional information

project name displayed in abapGit
here might be some more information about what the project does and what it is for.

?
I haven't seen any "github standards" for this.

I would imagine this being a local setting

imho, just add ty_repo_xml-local_name or display_name and split the logic a bit. From the top of my head: add field to online repo dialog, maybe add rename command (or maybe leave for DB util)

@tricktresor can you try the latest build?

Works great! Thanks a lot!


zbus-proxies: initial commit and add login1

This crate will become the new home of zbus proxies for third party services. The intention is to then use the login1 proxy in the update agent, and remove zbus_systemd, since the maintainer has repeatedly stated that our changes won't be upstreamed. For something so trivial, we are better off rewriting it ourselves, and consolidating all of this in one spot.
We might also want other third party services like wpa_supplicant to live in here in the future.
The PR adds .xml files retrieved via busctl introspect, as well as a cli tool to convert from the xml files to the zbus code. It then includes the generated results after tweaking them manually and documenting the tweaks.

I'm closing this PR. zbus-xmlgen doesn't generate all of the additional proxy structs for systemd1. It seems to only generate the main toplevel manager. I'm also dissatisfies that I have to include zbus-xmlgen as a binary via nix instead of using it as a library.
Given that zbus_systemd is fine to use as long as we only use the async interfaces, I've decided that forking it as @oldgalileo originally did, or simply vendoring the proxy interface ourselves when we can't use async, is fine.


evolved steps towards devicetree-based device definitions and dependency representations

This supersedes #26388 which is similar but was a trial for whether the handles could be identified solely from devictree.  They can't (#26575), so this shows current status of an approach that post-processes the prebuilt ELF file and will generate correct and complete dependency data.
The solution here extends the DEVICE_INIT() macro infrastructure to take the declaration names and other information from a devicetree node.  For devices defined in this way dependency information from the devicetree and from external sources are stored in an array referenced from the driver structure.  This array uses the ordinals from the devicetree, and is placed in a linker section that will be discarded in the final link.
A new script gen_handles.py reads the prebuilt binary and uses the device handle array data to associate each device with the devicetree node associated with it.  The dependency graph of the whole devicetree is then reduced to a dependency graph involving only devices present in the application.  Ordinals for these devices are assigned based on their offset in the Zephyr device section, and new handle values are generated that replace the ones used in the pre-build link.
Issues to be addressed:

Dependency information is available only when the drivers use devicetree nodes to define the device structure.  All drivers will have to be updated to do this.
Many devices will not have any recorded dependencies.  Each of those currently costs 2 bytes for the device-specific handle array that holds the empty sequence.  Those can be replaced by aliases to a common empty sequence array.
Although non-device handles can be added there is currently no mechanism to define them for reference from other devices and init functions.

The tooling-supplied ordinal is not used in the application.  The rework would enable:
struct device *dev = &DEVICE_DT_GET(nodeid);

as a mechanism to access the device structure, if the underlying names were made global.

Good work. I recently did something like this for a bare metal module loader at $DAYJOB and took the same approach, reducing the problem to a topological sort.

Still not ready for real review, but this is basically functional now.  @mbolivar-nordic please look; the commits I've adopted cover the current need for devicetree API for ordinals.  That the original devicetree ordinals are ephemeral (replaced by the index of the device in the device array) suggests that exposing generic API to access them in C is probably not useful.  So we're much closer now to closing on #26062.
@galak if you feel it worthwhile we could discuss this in dev-review tomorrow.  It's going to be blocked until the changes to support defining devices with devicetree nodes go in, which probably conflict with #24873 or other work @tbursztyka is doing, so I don't think there's a great rush.

Definitely could use deterministic device intialization  right about now.

@mbolivar-nordic please look; the commits I've adopted cover the current need for devicetree API for ordinals.

I haven't forgotten this and will get to it as soon as I can.

Currently this draft PR has the following content:

#27443 which extends the on-off service in support of...

d1dfee381d sys: onoff: use updated API terminology
0c59be0d73 sys: onoff: support clients using synchronous transitions

#27360 which adds regulator devices which provide another source of meaningful dependency in devicetree.

bbb521e6bb devicetree: add infrastructure for regulator devices
ae865fb766 drivers: regulator: add GPIO-controlled regulator driver
d61f8e2a80 devicetree: i2c-device: add power-supply property
9e98876ac4 boards: thingy52_nrf52832: add nodes for on-board voltage regulators

Pieces from #26062 by @mbolivar-nordic providing devicetree macro support to get dependency information from devicetree

f2665de9a6 devicetree: add first round of dependency ordinal info
051e9b0339 doc: document devicetree.h dependency ordinal APIs

Additional commits the complement or extend what's provided in #26062

971e3efb59 DNM: add FOR_EACH_NONEMPTY_TERM
a1cdb117b9 REWORK edtlib: add support for finding node from dependency ordinal
2e8b323222 sys: util: add identity macro
2cfae1b56d devicetree: add a name for an invalid node identifier

Commits that rework the device initialization macros so that devices can be defined using devicetree node data.  These will conflict with other device restructuring work in progress

6183da35ec device: provide API that uses the devicetree node as identifier
a5f68084cf device: redefine devicetree device definition using a more generic API

Partial conversion of existing drivers to use the new DEVICE_DT_ macros to define devices, so that they can participate in dependency relationships

9fe52be8c4 WIP drivers/clock: update to DT device API
5cc9201dc3 WIP drivers/flash: update to DT device API
b7d41103ac WIP drivers/gpio: update to DT device API
c7d2a833db WIP drivers/i2c: update to DT device API
f25765733b WIP drivers/regulator: update to DT device API
7e1dcdd9ab WIP drivers/sensor: update to DT device API
0c61635c83 WIP drivers/serial: update to DT device API
f5094ce578 WIP drivers/spi: update to DT device API

Extending the device structure to represent dependency information using handles and information from the devicetree nodes

050caf68b8 WIP device: inject device dependency information from devicetree nodes
f9f003bf9b WIP timer: demonstrate way of associating handles with system devices

Translating the devicetree ordinals to handles that directly correspond to device objects

280f859f56 REWORK scripts/gen_handles: add post-processing to fix up handle references

Hacked examples that display the dependency information
85df75d05b DNM hello: playground for device dependencies
3a4a47c717 DNM samples: spi_flash: hack for testing

Dependency information for arbitrary programs can be obtained using the gen_handles script, e.g.:
python3 scripts/gen_handles.py -v -o g.c \
  -k samples/sensor/ccs811/build/zephyr/zephyr_prebuilt.elf

That sample, when built for thingy52_nrf52832, has the deepest dependency set currently available.


Alerts notification 846c0e

Could we please verify the alerts notification is working ok?
The alert 846c0e for measles/rubella has been investigated but this is no longer reflecting in the alerts tab (it was previously)?
Is this an issue with the start_date? But please note the start_date for the tablet is 30 May 2016.

This is now resolved.


bugfix/report-rendered-when-on-dom

problem statement
.rendered yields true when the view is not rendered
solution

detect if the el is attached to the document body

unfortunately, disable caching as event based solutions are apparently out-of-the-question. 1, 2

add supporting test

i have not tested this in production code yet.  will be making some widgets shortly.  until then, tests passing, ready for review

@cdaringe my understanding was that rendered yields true when the render function was called i.e. this.el is true and not necessarily if it is attached to the document. They seem to be two different things …

hey @ferdinandsalis, see http://requirebin.com/?gist=34edb359882bce0c85ae.  i think that this example demonstrates that a test against this.el is insufficient.  view conventions somewhat supports your point, but the waters become muddied when your own el is provided.  you'll see that a View reports rendered without render ever being called.
you are correct--this modified test may counter separation of concerns--i just couldnt' think of an instance where someone would call render and not put something on the DOM.  we could feasibly flip some bits in render and remove?

@fyockm, would like your input too

to me, rendered sounds like either the render method has been called and subviews have been registered and attached to el or that and the el has been attached to the DOM.
If render is ever called without attaching el to the DOM, i would advise to have a property rendered aswell as a property attached.
Deriving rendered only from the presence of an el is misleading to me. Please change! :+1:

I agree with @gonsfx's last statement that we should probably separate attached vs. rendered because they are distinct, and there are things one can do with an unattached but rendered el that are legitimate.
I'd rather we go that route than making rendered mean both created and attached.

thanks everyone for your input!  sounds like we're all in agreement then.  I will rework to match group consensus.

Sorry for my late response. I'll pile on with @gonsfx and @aaronmccall that separating rendered and attached makes sense. Seems you've already accepted that path, but wanted to throw in my 2¢.

for now I just patched render, and didn't fiddle with attach.  ready for review number 2!  gracias.

So now when people override render (the most common method overridden afaik) they will have to also set rendered to true?

as it is written, yes.  to get the desired behavior and not force overriders to have to manage rendered in render, the only solution coming to mind is a custom setter that wraps the user provided render function with &-View internal actions (i.e. flipping the rendered bit).  im not sure if that will produce undesirable side-effects or not, but am willing to try it.  other implementation suggestions welcomed too.
in other views, rendered is managed manually, e.g. form-view.  however, form-view doesn't extend &-view, and in that case, it's certainly not advertised as being a public attr!

Closing until review & discussion happen on #119


Build issues again musl libc

The project fails  to compile on musl-based systems.
Details:

GCC 13.2.0
musl 1.2.5

Failure:
$ make
==== Building vxt (release_native) ====
==== Building adlib (release_native) ====
==== Building arstech_isa (release_native) ====
==== Building bios (release_native) ====
==== Building cga (release_native) ====
==== Building ch36x_isa (release_native) ====
ch36x_lib.c
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_get_chiptype':
modules/ch36x_isa/ch36x/ch36x_lib.c:78:21: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635352' to '-2147331944' [-Werror=overflow]
   78 |     ret = ioctl(fd, CH36x_GET_CHIPTYPE, &ct);
      |                     ^~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_get_version':
modules/ch36x_isa/ch36x/ch36x_lib.c:92:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635353' to '-2147331943' [-Werror=overflow]
   92 |     return ioctl(fd, CH36x_GET_VERSION, (unsigned long)version);
      |                      ^~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_get_ioaddr':
modules/ch36x_isa/ch36x/ch36x_lib.c:104:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635328' to '-2147331968' [-Werror=overflow]
  104 |     return ioctl(fd, CH36x_GET_IO_BASE_ADDR, (unsigned long)ioaddr);
      |                      ^~~~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_get_memaddr':
modules/ch36x_isa/ch36x/ch36x_lib.c:117:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635329' to '-2147331967' [-Werror=overflow]
  117 |     return ioctl(fd, CH36x_GET_MEM_BASE_ADDR, (unsigned long)memaddr);
      |                      ^~~~~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_config_byte':
modules/ch36x_isa/ch36x/ch36x_lib.c:138:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635330' to '-2147331966' [-Werror=overflow]
  138 |     return ioctl(fd, CH36x_READ_CONFIG_BYTE, (unsigned long)&ch36x_read_config_t);
      |                      ^~~~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_config_word':
modules/ch36x_isa/ch36x/ch36x_lib.c:159:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635331' to '-2147331965' [-Werror=overflow]
  159 |     return ioctl(fd, CH36x_READ_CONFIG_WORD, (unsigned long)&ch36x_read_config_t);
      |                      ^~~~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_config_dword':
modules/ch36x_isa/ch36x/ch36x_lib.c:180:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635332' to '-2147331964' [-Werror=overflow]
  180 |     return ioctl(fd, CH36x_READ_CONFIG_DWORD, (unsigned long)&ch36x_read_config_t);
      |                      ^~~~~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_io_byte':
modules/ch36x_isa/ch36x/ch36x_lib.c:267:21: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635336' to '-2147331960' [-Werror=overflow]
  267 |     ret = ioctl(fd, CH36x_READ_IO_BYTE, (unsigned long)&ch36x_read_io_t);
      |                     ^~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_io_word':
modules/ch36x_isa/ch36x/ch36x_lib.c:290:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635337' to '-2147331959' [-Werror=overflow]
  290 |     return ioctl(fd, CH36x_READ_IO_WORD, (unsigned long)&ch36x_read_io_t);
      |                      ^~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_io_dword':
modules/ch36x_isa/ch36x/ch36x_lib.c:311:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635338' to '-2147331958' [-Werror=overflow]
  311 |     return ioctl(fd, CH36x_READ_IO_DWORD, (unsigned long)&ch36x_read_io_t);
      |                      ^~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_mem_byte':
modules/ch36x_isa/ch36x/ch36x_lib.c:398:21: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635342' to '-2147331954' [-Werror=overflow]
  398 |     ret = ioctl(fd, CH36x_READ_MEM_BYTE, (unsigned long)&ch36x_read_mem_t);
      |                     ^~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_mem_word':
modules/ch36x_isa/ch36x/ch36x_lib.c:421:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635343' to '-2147331953' [-Werror=overflow]
  421 |     return ioctl(fd, CH36x_READ_MEM_WORD, (unsigned long)&ch36x_read_mem_t);
      |                      ^~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_mem_dword':
modules/ch36x_isa/ch36x/ch36x_lib.c:442:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635344' to '-2147331952' [-Werror=overflow]
  442 |     return ioctl(fd, CH36x_READ_MEM_DWORD, (unsigned long)&ch36x_read_mem_t);
      |                      ^~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_read_mem_block':
modules/ch36x_isa/ch36x/ch36x_lib.c:532:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '2147635348' to '-2147331948' [-Werror=overflow]
  532 |     return ioctl(fd, CH36x_READ_MEM_BLOCK, (unsigned long)&ch36x_read_mem_t);
      |                      ^~~~~~~~~~~~~~~~~~~~
modules/ch36x_isa/ch36x/ch36x_lib.c: In function 'ch36x_stream_spi':
modules/ch36x_isa/ch36x/ch36x_lib.c:640:22: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '3221377179' to '-1073590117' [-Werror=overflow]
  640 |     return ioctl(fd, CH36x_STREAM_SPI, (unsigned long)&ch36x_stream_spi_t);
      |                      ^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [ch36x_isa.make:169: obj/native/release/ch36x_isa/ch36x_lib.o] Error 1
make: *** [Makefile:172: ch36x_isa] Error 2

Perhaps an explicit cast is in order.

Nevermind, the bug is in the libc.


Implement Efficient Lockfile for Better Version Control and Faster Startup

vim-plug would benefit from a lockfile system for the following reasons:

Reproducible environments across machines
Prevention of unexpected plugin updates
Easier rollbacks to known-good states

The current snapshot feature, while useful, has limitations:

Slow startup times due to executing multiple git commands on each Vim launch
Doesn't prevent automatic updates during normal plugin operations

A lockfile approach would:

Store plugin commit hashes in a simple, fast-to-read format
Be checked during updates to determine if changes are needed
Only update plugins when explicitly requested or when the lockfile changes
Significantly reduce startup overhead compared to the current snapshot system

This feature would enhance vim-plug's utility for users prioritizing stability, reproducibility, and performance in their Vim/Neovim setups.

Type:

[ ] Bug
[ ] Enhancement
[x] Feature Request
[ ] Question

OS:

[x] All/Other

Vim:

[x] Terminal Vim
[x] GVim
[x] Neovim

note: I know https://github.com/junegunn/vim-plug/issues/954 was opened previously, this is effectively restarting that convo.


Code Signing Issue with Alamofire

Hi, I have integrated the latest framework of Alamofire in my app. But now I am getting this error when I try to run my app on my iPhone. I searched a lot over the Internet but I didn't find the solution! Please help! Thanks!
-------   Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)! 17467AD3C396A302B30E4278587814C64080AE93: no identity found ----------
@mattt Please see!

This is not a support forum. Please open a question on StackOverflow and tag Alamofire. Also, please add more information about your project such as whether it is iOS or Mac OS X, deployment target, how you added Alamofire to your project, etc.

Thanks, @cnoon.


Update googleAPI.py

make global variable BUCKET_NAME
, which you can change your project bucket name easily(google-cloud-storage)
(for developer)

readme.md
how to use google stt api


update config page with WAL logging syntax

See https://github.com/influxdb/influxdb.com/issues/550.
Apparently in 0.9.5 the syntax is different than 0.9.6, although I can't explain why from looking at the code.

@gunnaraasen can you figure out why we have a mismatch here? I can't find any record of wal-enable-logging in the repo, but that's absolutely what my 0.9.5 config shows:
[data]
  dir = "/Users/sean/.influxdb/data"
  max-wal-size = 104857600
  wal-flush-interval = "10m0s"
  wal-partition-flush-delay = "2s"
  wal-dir = "/Users/sean/.influxdb/wal"
  wal-enable-logging = true
  wal-ready-series-size = 30720
  wal-compaction-threshold = 0.5
  wal-max-series-size = 1048576
  wal-flush-cold-interval = "5m0s"
  wal-partition-size-threshold = 20971520

I think he might be confused; it's always been wal-enable-logging in the config file.

@jademcgough I just looked at a config file on @jackzampolin's 0.9.6 box and it was wal-logging-enabled. Not sure what's the truth yet.

If you look at source code:
tsdb/config.go:90:	WALLoggingEnabled         bool          toml:"wal-logging-enabled"

oh, I'm completely wrong: https://github.com/influxdb/influxdb/commit/6592dcc69948190c19b8ec73a6c37a8bae9d486d

Looks like the config option was changed to wal-enable-logging back in 0.9.4 via https://github.com/influxdb/influxdb/commit/6592dcc69948190c19b8ec73a6c37a8bae9d486d and the sample config had wal-enable-logging up until this commit https://github.com/influxdb/influxdb/commit/4281da6688261f4675e21da850839a941268e56a.
On <IP_ADDRESS> and <IP_ADDRESS>, the generated config is wal-logging-enabled.
I'm updating the config page now. There's some other stuff on there which needs to be updated as well.


Skip SELinux operations on downburst VMs

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1593/
Tests passed for this pull request.

http://pulpito.ceph.com/zack-2015-07-01_09:15:11-teuthology-master---basic-vps/


proot: 5.3.1 -> 5.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/proot-me/proot/releases.
meta.description for proot is: User-space implementation of chroot, mount --bind and binfmt_misc
meta.homepage for proot is: https://proot-me.github.io
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.4.0 in filename of file in /nix/store/r88ysnpfyqjbns8la9m4pgfsaqn2l0x7-proot-5.4.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
canon-cups-ufr2
proot

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r88ysnpfyqjbns8la9m4pgfsaqn2l0x7-proot-5.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A proot https://github.com/r-ryantm/nixpkgs/archive/1e5a2916ada1e179f49c76a2ef0b30f28f1945a4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r88ysnpfyqjbns8la9m4pgfsaqn2l0x7-proot-5.4.0
ls -la /nix/store/r88ysnpfyqjbns8la9m4pgfsaqn2l0x7-proot-5.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

canon-cups-ufr2
proot

Maintainer pings
cc @wavewave @makefu @veprbl @dtzWill for testing.

thanks!


[Event Hub] Small improvements & refactorings

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@jsquire I noticed GetPooledProducer might call TransportProducerFactory multiple times because GetOrAdd might call the value factory multiple times. Maybe it is not a problem I just made me suspicious because the transport producer is a resource that needs to be closed if I understand the code correctly.

Please also see https://github.com/Azure/azure-sdk-for-net/pull/29952#issuecomment-1187588797

Ah I think these comments
// A race condition at this point may end with CloseAsync called on
            // the returned PoolItem if it had expired. The probability is very low and
            // possible exceptions should be handled by the invoking methods.

// If TryRemove returned false the PoolItem would not be closed deterministically
                // and the ExpirationTimer callback would eventually remove it from the
                // Pool leaving to the Garbage Collector the responsibility of closing
                // the TransportProducer and the AMQP link.

explains things

I have another design related question. I wonder if it would make sense to add the necessary state and references to PooledProducer and then make the DisposeAsync method do the cleaning. With that the pooled producer could have a reference to the PooledItem and piggy back the identifier and what is needed for the cleanup. While this class is a bit sneaky how it reaches into the parent state it would get rid of the unnecessary closure.

I have another design related question. I wonder if it would make sense to add the necessary state and references to PooledProducer and then make the DisposeAsync method do the cleaning. With that the pooled producer could have a reference to the PooledItem and piggy back the identifier and what is needed for the cleanup. While this class is a bit sneaky how it reaches into the parent state it would get rid of the unnecessary closure.

I generally have a strong preference to keep object graphs flowing in a single direction, but this is an internal construct of very tightly coupled types, so I'm not totally opposed in this specific instance.  I do know that we originally ran into a lot of issues with concurrent use and non-deterministic clean-up that we had to guard against.   (the two comments that you highlighted call some out)
Do you think we'd be opening up additional corner cases to guard against?

I guess this is good to go then

I guess this is good to go then

Much appreciated!


Ollie: Watch fastwaytracking.com

Ollie requests the watch of the watch_keyword fastwaytracking\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

fastwaytracking\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Host Override doesn't work with ip port

Describe the bug
I am trying to do a host override in Unbound DNS on OPNsense. I have done other redirects but with out port numbers and they work fine. When I try to create a host redirect with an ip address and port number, like <IP_ADDRESS>:5959, I get "please specify a valid network segment or address (IPv4/IPv6)" in red.
To reproduce
Steps to reproduce the behavior:

Add an ip address WITH port on Edit Host Override dialog screen.

Hi there,
I am not familiar with the OPNsense interface but if they pass values as-is to Unbound you could try Unbound's ip@port notation, since Unbound does support specifying custom ports.
If that doesn't work I cannot help you further and it would be best to open an issue with OPNsense instead.
Actually opening an issue to document the expected notation in the interface (if that is not already there) would be an appreciated move!


Feature: Set status of ESB itineraries

With the  item, it would be good if you could optionally specify if the itinerary should be set to a status of "Published".  Currently all itineraries are set to a status of "Deployed".
This work item was migrated from CodePlex
CodePlex work item ID: '8040'
Vote count: '1'

[tfabraham@3/22/2011]
Actually, it just follows whatever you configured in the Itinerary Designer.  If you look at the Properties in the designer on the main design surface, you'll find the status.  Just switch it to Deployed and export to XML.  Please confirm if that takes care of it for you.  Thanks!

[charliemott@3/23/2011]
Hi Tom,
In Visual Studio, while the Database Itinerary Exporter give you the ability to set a status property, the XML Itinerary Exporter does not.
When uploading an interary xml file using the EsbImportUtil utility (see: See: http://msdn.microsoft.com/en-us/library/ee384245(v=bts.10).aspx), you set the status using the /c: paramerter.
So the command line can be:
EsbImportUtil /f:myitinerary.xml /c:published
EsbImportUtil  /f:myitinerary.xml /c:deployed
Charlie

[tfabraham@3/23/2011]
Got it, I misinterpreted the original request in relation to the current behavior.  I could add a Status metadata item to the EsbItineraries element.

[UnknownUser@10/20/2011]

[UnknownUser@2/21/2013]


Issue with the registration on the Login page.

Describe the bug
Currently, on clicking 'Register' button without entering any details, the page simply refreshes.
Name, Email and Password need to be a required field.
Expected behavior
It should display a message saying 'Please fill this field.'
Screenshots
screen-capture.webm(video)

Are you contributing under any open-source program ?
This is under GSSOC'24.

Please assign it to me.

Please assign this to me

Please assign this to me, I'll try best to fix it

Hey! I can resolve this issue in less time! Can you assign me?

Hello I am Debarun Chakrabortty and am contributing under GSSoC'24 , I would request you to assign this issue to me. Thankyou

I want to work on this part of project please assign it to me under GSSOC-24

#343 Issue with the registration on the Login page
I want to contribute to the above issue ,can you please assign me this work because I can do it fast and efficient.

Hi,
I am contributing under GSSOC'24.I am having experience on developing web development projects and I can handle this issue. Could please assign it to me.

@avanimathur You are assigned . you can start working on this issue


update docs to advice exponent js users

I spend some days trying to figure out how to use this lib with Exponent js. I was having compatibility errors and then managed to get it to work on android by changing the gms version.

This info is also relevant when using airbnb's react-native-maps package. Having both installed crashes the app unless you alter the required google package version, as per the example repo:

Module react-native-maps v0.8.2 requires Google Play Services library version 9.4.0, we need to change node_modules/react-native-mauron85-background-geolocation/android/lib/build.gradle
dependencies {
...
compile 'com.google.android.gms:play-services-location:9.4.0'
...
}

I've some instructions regarding rn-maps in https://github.com/mauron85/react-native-background-geolocation-example.
But agree that is might be valuable instruction also here in plugin repo.
Only one thing. Can you also add mention about react-native-maps (like you said here)? I will merge it then.

Done!

Since I originally commented here I saw a different approach that may be better.
See info here:
https://github.com/transistorsoft/react-native-background-geolocation/issues/229
Basically if you edit your app/build.gradle and force your own version, you can avoid having to update the build.gradle of the package, which would be annoying in the future (have to be careful with upgrades, etc)

merged, thank you


⚠ Anthelion has degraded performance

In 119977d, Anthelion ($ATH) experienced degraded performance:

HTTP code: 200
Response time: 2388 ms

Resolved: Anthelion performance has improved in 61bdc81 after 411 days, 15 hours, 39 minutes.


New org: Nonlinear Fund

http://www.nonlinearfund.org/about.html
"Our board of advisors currently includes: Jonas Vollmer, Spencer Greenberg, Alex Zhu, Robert Miles, and David Moss. " https://forum.effectivealtruism.org/posts/fX8JsabQyRSd7zWiD/introducing-the-nonlinear-fund-ai-safety-research-incubation

I added 5 positions. Ready for review.

Sorry for not getting around to reviewing this. But I noticed they added more positions recently https://www.nonlinear.org/about.html

More positions added


[WIP] - Monitor 2.0

Codecov Report

Merging #69 (1b1f781) into master (0f05069) will decrease coverage by 0.93%.
The diff coverage is 4.28%.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
- Coverage   56.91%   55.98%   -0.94%
==========================================
  Files         106      106
  Lines        9858    10022     +164
==========================================
  Hits         5611     5611
- Misses       3877     4041     +164
  Partials      370      370

Flag
Coverage Δ

unittests
55.98% <4.28%> (-0.94%)
:arrow_down:

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

Impacted Files
Coverage Δ

action_blockheader.go
0.00% <0.00%> (ø)

chainstate/client_options.go
90.51% <ø> (ø)

chainstate/monitor.go
0.00% <0.00%> (ø)

chainstate/monitor_client.go
0.00% <0.00%> (ø)

model_blockheaders.go
1.65% <0.00%> (-0.21%)
:arrow_down:

monitor_event_handler.go
0.00% <0.00%> (ø)

chainstate/processor.go
27.94% <24.32%> (-5.40%)
:arrow_down:

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 0f05069...1b1f781. Read the comment docs.


Doesn't work with<EMAIL_ADDRESS>

In<EMAIL_ADDRESS>the file structure of node_modules was flattened. However, this addon does not currently take that into effect and appears to just blindly expect the ember-cli-windows tool to be at a very specific path.
As such, this Ember CLI addon does not currently work with<EMAIL_ADDRESS>> ember windows
version: 1.13.12
module.js:339
    throw err;
    ^

Error: Cannot find module 'C:\Users\gre63396\Development\win-ember\node_modules\
ember-cli-windows-addon\node_modules\ember-cli-windows\bin\ember-cli-windows'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

[object Object]

That's because the ember-cli-windows module is now a sibling to the ember-cli-windows-addon module (directory-wise), e.g. running from the same directory as before:
> node_modules\.bin\ember-cli-windows
ember-cli-windows v2.0.0
Configure Windows for Ember-Cli Performace
If you continue, this tool will automate the configuration of Windows Defender a
nd Windows Search
Confirm: Do you want to proceed? (Y/N):  Y
Finished Search Configuration.
Finished Defender Configuration.

Dang, that's a really good point - and kind of embarrassing, given that I've been pushing npm@3 like crazy. I'll fix that.

Thanks, looking forward to it.  :+1:


Fix a typo in github workflows

There is a typo in variable name, at the moment, it runs
conda install python= numpy=>1.20 scipy...
As a consequence, python 3.8 is also installed in 3.7 build so the tests are not really done in 3.7.

@kbuc Thanks, I switched from appveyor to using github actions, since it supports more OSes in a uniform way.

@newville There is a typo in github actions, which makes tests in "build 3.7" actually run python 3.8.8
Just ignore the commit about appveyor in this PR, it's because of merging branches.
I'm talking about commit 3699e95.

@kbuc Thanks -- I was just checking that out too and making the two Actions tests more uniform.   Then I'll go investigate why Python 3.9 wasn't passing...


Investigate feasibility of testing Windows playbooks under Vagrant

How easily can Windows systems be created and run via Vagrant? Can we automate the playbook testing on "clean" OS installs as we can now do on Linux (https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/842)?

Written a vagrantfile that can boot a Windows 10 VM, however when using vagrant ssh it boots into a linux shell script. cmd can then be run from there.

Created a vagrantfile that can boot a windows VM, and have a list of reliable steps towards running the playbook remotely. A readme.md file will need to be created, or an existing one altered to give steps on how to do this.
Overview of the steps taken:

vagrant up on Vagrantfile.WindowsS12
On windows vagrant machine:

wget https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 -OutFile .\ConfigureRemotingForAnsible.ps1
.\ConfigureRemotingForAnsible.ps1 -EnableCredSSP
ipConfig to find the ip-address for the VM

(if on Mac host) export OBJC_DISABLE_INITIALISE_FORK_SAFETY=yes
On Host machine:

change hosts.txt in ../ansible/playbooks/AdoptOpenJDK_Windows_Playbook/ to include the Windows VM ip address.
add in ../AdoptOpenJDK_Windows_Playbook/group_vars/all/adoptopenjdk_variables.yml, the line ansible_winrm_transport=CredSSP
From ../ansible run sudo ansible-playbook -i playbooks/AdoptOpenJDK_Windows_Playbook/hosts.win -u vagrant playbooks/AdoptOpenJDK_Windows_Playbook/main.yml

.. and the playbook should run.


Any update for DAVIS 2017?

Yes, I'll release a new version in the upcoming days.
Federico
On Tue, May 16, 2017 at 1:25 PM, bhack<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fperazzi/davis/issues/6, or mute the thread
https://github.com/notifications/unsubscribe-auth/ARh0Gw-9OzFar7_eakjSJ5MJ53ahQdNQks5r6YeQgaJpZM4NcWYu
.

There you go: https://github.com/fperazzi/davis-2017

Thanks

No problem, I didn't have time to thoroughly test the code, if you have problem, just open an issue in the repo. Thanks!


Translations update from Foundry Hub - Weblate

Translations update from Foundry Hub - Weblate for Hey, Wait!/main.
Current translation status:

I think its bugged? Closing for now


[Radio button] Selected disable state is off

Detailed description
When a radio button is selected & disabled the inner circle to indicate it's selected doesn't appear to be correct.
Here is what I'm seeing...

Here is what I expect to see...

What browser are you working in?
Appears to be in all browsers

What version of the Carbon Design System are you using?
I'm seeing it on latest 9.88.3

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
Digital Design

Steps to reproduce the issue

Please create a reduced test case in CodeSandbox
https://codesandbox.io/s/r0wk6rwwwm

@shixiedesign here is that issue I brought up to you the other day.


Exclude files in search always active - on/off button has no effect

Issue Type: Bug
The 'Use Exclude Settings and Ignore Files' button in search does not have any effect - 'files to exclude' (please also use capital letter for 'files' -> 'Files') is always active (e.g.: .venv, *.log, *.json).
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

Not the same issue as suggested by 'vscodebot' ;-)

That button does not toggle off the text input, whatever is in there is always applied. Is that what you are talking about?

It doesn't do that, it toggles of the exclude settings and using the gitignore file. The text input is still applied


Notify after being sure we got back online after disconnection.

Notify if we are connected to internet but DNS is not working.

Seems to work ok.


Dynamicly change title

What is the proper way to change title dynamicly on client-side?
I want to use
<Helmet title={this.getTitle.bind(this)}/>

But console brings me warnings about proptypes.
So, I can do a PR with
title: _react2["default"].PropTypes.oneOfType([   _react2["default"].PropTypes.string,
_react2["default"].PropTypes.func]),

in Helmet.js 339 string

Since it's inside the component's render function, you can just call the function. It'll get updated as much as possible.

@DGizmo - To dynamically set the title, you can call your function earlier in the render function and save to a variable.  Or you can set a variable in your state.
I don't think we want to allow functions as props for the title.


GEOMETRY error when trying Tegola with a geopackage

I get an error saying "Error: could not register providers: unsupported geometry type: GEOMETRY" when trying to tegola_windows_amd64_cgo version 0.8.1 on a geopackage file. The gpkg file contains only one table that lists as a LineString25D when opened in QGis (works perfectly) geometry column is geom, srid is 3857.
This is my config-file:
[webserver] port = ":8082"

[cache] type = "file" basepath = "C:\Tegola\cache"

[[providers]] name = "gsd" type = "gpkg" filepath = "C:\Tegola\data\gsd.gpkg"

    [[providers.layers]] name = "gsdvol" tablename = "vol"

[[maps]] name = "roads"

    [[maps.layers]] provider_layer = "gsd.gsdvol" min_zoom = 11 max_zoom = 19

Is this a bug or am I just configuring it wrong?

@kartogishenko anyway I can get access to the geopackage to recreate it? I would suspect what's going on here is that the GEOMETRY type is too generic and tegola wants to know if it's a polygon, line string, point, etc.

Sure, here it comes. Doubblechecked there is only one kind of geometry in the fil.
geopackage.zip

@kartogishenko i got it working. A few things:

tegola does not have support for the generic "geometry" type. This is because MVT does not have support for it (also called a geometry collection). A layer must have a single geometry type, not a heterogenous mixture. In the case of this geopackage, the vol layer has a type of LINESTRING
The geopackage appears to have a non standard structure (missing fid) so the auto generated SQL from tegola does not work out of the box. I was able to export your geopackage using QGIS, setting the geometry type to LINESTRING and everything works fine (screen shot below). I have also attached the new geopackage for your review.
Where did you obtain this geopackage file? I'm interested in knowing what's creating this structure in case it shows up again.
This issue also brings to attention that tegola needs to support the geometry_type override for geopackage like we do for PostGIS. This is a different issue.

New Geopackage: gsd-2.gpkg.zip

For convenience the URL in the screen shot is: http://localhost:8082/#11.64/55.6392/13.7449

Hi, thank you for looking in to it. The Geopackage was created using FME Desktop 2018.1 and the software might have som issues when exporting to geopackage, according to its support forum. When comparing your rework of my geopackage with the original one I notice that mine has the geometrytype LineString25D and yours has LineString. This I cannot correct in FME, unfortunately. I do get it to work using the same method as you did when creating the geopackage from QGis so I just have to use that method for now. Thank you!

@kartogishenko I have not used FME myself so I don't have any insight into some of the data conversion nuances.

When comparing your rework of my geopackage with the original one I notice that mine has the geometrytype LineString25D and yours has LineString.

This sounds like a bug in FME as LineString25D is not a valid Geometry Type according to the Geopackage spec. Maybe let them know?
Glad you have a work around. Please close the issue unless you have any other questions.


Gateway tries to read from stream after closure on resumes

Resumes currently log something like this:
2022-01-08T12:06:22.516997Z DEBUG twilight_gateway::shard::processor::r#impl: got request to reconnect
2022-01-08T12:06:22.517015Z DEBUG twilight_gateway::shard::processor::r#impl: resuming shard [91, 240]
2022-01-08T12:06:22.638171Z  WARN twilight_gateway::shard::processor::socket_forwarder: socket errored: IO error: unexpected end of file
2022-01-08T12:06:22.638190Z DEBUG twilight_gateway::shard::processor::socket_forwarder: Leaving loop
2022-01-08T12:06:22.724225Z DEBUG twilight_gateway::shard::processor::r#impl: Shook hands with remote
2022-01-08T12:06:22.724254Z DEBUG twilight_gateway::shard::processor::socket_forwarder: starting driving loop
2022-01-08T12:06:22.724293Z DEBUG twilight_gateway::shard::processor::r#impl: got hello with interval 41250
2022-01-08T12:06:22.724298Z DEBUG twilight_gateway::shard::processor::r#impl: resuming with sequence 4284, session id 219740e6a206b8844428c86927b60cb8

This indicates that twilight knows it was requested to reconnect, but still attempts to read from the closed TCP stream. This should not happen, for two reasons:

It results in a lot of verbose logging the more shards are created
Dropping the log level might suppress "real" I/O related issues

I assume this happens because the socket forwarder isn't stopped in time (https://github.com/twilight-rs/twilight/blob/main/gateway/src/shard/processor/socket_forwarder.rs#L84).

Assigning to self as this will likely be fixed as a result of my gateway refactor.

Fixed in next, Twilight 0.14

Actually the issue is due to a bug in tokio-rustls (see snapview/tungstenite-rs#316 for some more research into the issue). The rewrite merely sidesteps this issue by disconnecting the WebSocket connection prior to what the WebSocket protocol demands. Note that Discord somewhat says that this is okay (https://discord.com/developers/docs/topics/gateway#initiating-a-disconnect):

If you simply close the TCP connection or use a different close code, the session will remain active and timeout after a few minutes. This can be useful when you're Resuming the previous session.

Yes. There's a hack in the gateway that works around this but I think this should be opened until the root issue is fixed (as a reminder).

Fix available in 0.15.0 and 0.14.2 🎉


cloud LLM via API key

hi. adding support for cloud LLMs via API (chatGPT, Claude, Gemini, Grok) would be easy?
PS: thanks for the cool extension!

It is ready for Openai cloud. Just change api url and token key.

successfully tested with openai gpt4mini,
grok also worked (even tho i also have no access in my region. somehow i still got an API key, but i forgot how exactly i requested it :D ):

google gemini failed... seems it needs oauth token:

let me try try.
https://console.groq.com/docs/quickstart
i check this api request page didnt see oauth setting.

good morning. just to clarify: groq worked fine.
it was gemini that didn't work. maybe it's my google settings idk. but i think groq models are better than gemini anyway. there is llama-3.2-90b-chat-preview new as of yesterday

Okie. So is goohle api call will fail right? Ill check accroding
`
curl \ -H 'Content-Type: application/json' \ -d '{"contents":[{"parts":[{"text":"Explain how AI works"}]}]}' \ -X POST 'https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash-latest:generateContent?key=YOUR_API_KEY'
It seems like different format with openai lmstudio ollama, ill try call gemuni later.
`

dear @tazztone its not ur promblem about oauth issue, that is google has different from OpenAI request process. so i just rewrited. Now, it support google gemini-text and gemini-vision now.
BTW gemini-vision is really good, i just try and it can detect snow white correctly

well gemini seems a bit overly censored:
:D

but anyway i tried to setup groq again....
did you maybe break groq support with your update?:
**WARNING:[auto-llm]:[][AutoLLM][getReq][Json]{'model': 'llama-3.1-70b-versatile', 'messages': [{'role': 'system', 'content': 'You are a text prompt enhancer for AI Image generation.\n'}, {'role': 'user', 'content': 'beautiful otherwordly place'}], 'max_tokens': 150, 'temperature': 0.5, 'top_p': 0.9, 'top_k': 8, 'stream': False}
WARNING:[auto-llm]:[][AutoLLM][getReq][Header]{'Content-Type': 'application/json', 'Authorization': 'Bearer APIKEY'}
WARNING:[auto-llm]:[Auto-LLM][][]Req URL=> https://api.groq.com/openai/v1/chat/completions
WARNING:[auto-llm]:[Auto-LLM][][]Server Ans=> {"error":{"message":"property 'top_k' is unsupported, did you mean 'top_p'?","type":"invalid_request_error"}}

WARNING:[auto-llm]:[Auto-LLM][][]Missing LLM Server?'choices'**

groq is amazing and deserves a preset as well :D


Rework tagging to be consistent with the live container view and Autodiscovery

What does this PR do?
Sister PR for https://github.com/DataDog/datadog-agent/pull/2675 , using the tagger for container tagging.

New tags from the tagger: task_version, task_family, cluster_name, ecs_container_name, task_arn, container_id, container_name
Compatibility layer is added to keep the aliased ecs_task_family, ecs_task_version, ecs_cluster, docker_name
label_whitelist option is removed, users should migrate to the agent's docker_labels_as_tags that works with fargate task labels

Motivation
Consistent tagging
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[x] Feature or bugfix has tests
[x] Git history is clean
[x] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2601 into master will decrease coverage by 9.19%.
The diff coverage is 88%.

@@            Coverage Diff             @@
##           master    #2601      +/-   ##
==========================================
- Coverage   83.84%   74.64%    -9.2%
==========================================
  Files         639        4     -635
  Lines       36373      213   -36160
  Branches     4421       34    -4387
==========================================
- Hits        30496      159   -30337
+ Misses       4560       42    -4518
+ Partials     1317       12    -1305


Migration does not work on Android.

I have an issue. I have cashed data with pre load views. If login and pass are cashed we don't need to show user all info screens. If i log in on Android device then kill app from app list running and then open app, database return empty data and user need to pass all process again. if i comment Migration it works. On iOS there is not such problem. Does anybody have his?

I'm sorry but i'm not sure I understand your problem, let me try to rephrase it:
If you use migrations, then the database will be empty after restarting the app?
Could you share some code, e.g. the migrations you are trying to run and maybe the class with the @Database annotation? Without those it will be really hard to try and reproduce your problem, let alone fix it.

As there were no answers for two months, I will be closing this issue. If you are still having problems with this, please share some more code with us and reopen the issue!


Hiding virtual list during momentum scroll causes the virtual list to be blanked out when returning to it

Describe the bug
Hiding virtual list during momentum scroll causes the virtual list to be blanked out when returning to it.
To Reproduce

Start momentum scrolling a view
Tap a button to toggle to hide the view (setting display: none)
Tap the button again to reveal the view
Observe the virtual list is not rendered. Observe if you try to swipe the virtual list, the items reappear.

Expected behavior
Items should be rendered when virtual list becomes visible again.
Platform:

OS: iOS
Browser: Safari
Version of react: 18
Version of this package: 0.15.3

Additional context
Here is a video demonstrating this problem. I am tapping the bottom tab bar. When I tap to go to Inbox, the virtual list stays mounted with display: none set to a parent element. Tapping back to Posts removes display: none.
https://github.com/inokawa/virtua/assets/2166114/bb7d4b65-24cc-4d76-b890-26e79a438d44

I have to do some investigation but visibility: hidden instead of display: none may resolve the issue.
display: none will change sizes of all children to 0 but visibility: hidden is not. Size detection is key of this virtual list so that may cause strange behavior.

I think it was fixed in 0.15.4!

I think it was fixed in 0.15.4!

Can confirm! Thanks so much!


Fix MetadataReportConfig being valid when pre config

What is the purpose of the change
Fixes https://github.com/apache/dubbo/issues/11096
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #11110 (dcafcbb) into 3.1 (9713ad6) will increase coverage by 0.05%.
The diff coverage is 67.92%.

@@             Coverage Diff              @@
##                3.1   #11110      +/-   ##
============================================
+ Coverage     64.51%   64.56%   +0.05%
  Complexity       14       14
============================================
  Files          1420     1420
  Lines         59072    59108      +36
  Branches       8673     8683      +10
============================================
+ Hits          38108    38162      +54
+ Misses        16920    16893      -27
- Partials       4044     4053       +9

Impacted Files
Coverage Δ

...org/apache/dubbo/config/context/ConfigManager.java
85.26% <ø> (ø)

...ache/dubbo/config/utils/ConfigValidationUtils.java
77.74% <20.00%> (-0.67%)
:arrow_down:

...ubbo/config/deploy/DefaultApplicationDeployer.java
71.12% <72.91%> (-1.35%)
:arrow_down:

...che/dubbo/config/utils/DefaultConfigValidator.java
86.36% <0.00%> (-9.10%)
:arrow_down:

.../dubbo/remoting/transport/netty4/NettyChannel.java
69.81% <0.00%> (-1.89%)
:arrow_down:

...e/dubbo/remoting/transport/netty4/NettyClient.java
67.77% <0.00%> (-1.12%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
86.20% <0.00%> (-0.87%)
:arrow_down:

...bo/registry/client/migration/MigrationInvoker.java
60.72% <0.00%> (-0.81%)
:arrow_down:

...ubbo/registry/client/AbstractServiceDiscovery.java
78.35% <0.00%> (-0.75%)
:arrow_down:

.../dubbo/registry/integration/RegistryDirectory.java
45.93% <0.00%> (-0.71%)
:arrow_down:

... and 21 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Integration test cases: https://github.com/apache/dubbo-samples/pull/620