[AMORO-3202] Upgrade Paimon Version to 0.9.0

Why are the changes needed?

Close #3202.
Brief change log

Upgrade Paimon to 0.9.0

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)

cc @huyuanfeng2018

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

Project coverage is 22.46%. Comparing base (8207efc) to head (57cb145).
Report is 23 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (8207efc) and HEAD (57cb145). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (8207efc)
HEAD (57cb145)

core
2
0

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3207      +/-   ##
============================================
- Coverage     29.43%   22.46%   -6.97%
+ Complexity     3685     2281    -1404
============================================
  Files           568      379     -189
  Lines         47267    38036    -9231
  Branches       6196     5442     -754
============================================
- Hits          13912     8544    -5368
+ Misses        32372    28754    -3618
+ Partials        983      738     -245

Flag
Coverage Δ

core
?

trino
22.46% <ø> (?)

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

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


Centering after animation

Hi. Firstly thx for the excellent plugin. I would like to center my screen after every animation. Based on the docs, I figured this would do the trick:
require('neoscroll').setup({
	post_hook = function(info) vim.cmd [[ normal zz ]] end
})

but it doesn't seem to work. I also tried exe "normal zz" instead ☁

i also tried the same thing with no luck 😢

this is working for me:
require("neoscroll").setup({
	post_hook = function(info)
		vim.cmd("normal! zz")
	end,
})

I have a feeling that there's a way to use neoscroll.zz here, although obviously infinite recursion is a concern there xD

Spent a few hours on this -- I'd recommend tweaking the specific numbers / easing function:
local neoscroll = require("neoscroll")

local easing = "sine"
local zz_time_ms = 100
local jump_time_ms = 200

neoscroll.setup({
	post_hook = function(info)
		if info ~= "center" then
			return
		end

		-- The `defer_fn` is a bit of a hack.
		-- We use it so that `neoscroll.init.scroll` will be false when we call `neoscroll.zz`
		-- As long as we don't input another neoscroll mapping in the timeout,
		-- we should be able to center the cursor.
		local defer_time_ms = 10
		vim.defer_fn(function()
			neoscroll.zz(zz_time_ms, easing)
		end, defer_time_ms)
	end,
})

local mappings = {}

mappings["<C-u>"] = { "scroll", { "-vim.wo.scroll", "true", jump_time_ms, easing, "'center'" } }
mappings["<C-d>"] = { "scroll", { "vim.wo.scroll", "true", jump_time_ms, easing, "'center'" } }

require("neoscroll.config").set_mappings(mappings)

@zdog234 Thank you for creating this hack, it works with your config, but the scroll speed is too fast for my eyes. I've tried to tweak the number but the following happens:
https://user-images.githubusercontent.com/57322459/209611462-e6077f34-0131-4862-9aad-bd59ea51ad1d.mp4
Basically it'd start to center with zz before the scrolling is done. It only happens when I scroll at the top of the file, not when the cursor is already centered. I tried tweaking but to no avail. Then I found cinnamon.nvim and with its built-in centered = true I no longer have the above weird issue. Thanks guys!


Can it prompt for the common files?

Could it prompt a formatted message for the files which type is Git Commit Message?

This file is created by the extension - vscode-conventional-commits.
The file uses the conventionalCommits.showEditor option to open the commit message in a separate tab.
And the file seems not at the current workspace. Could it use the configuration of the current workspace?

Thanks for the report. This is interesting.
It looks like that extension uses a custom filesystem provider for that editor, and the file's URI uses a custom scheme. Since we don't recognize the custom schema we treat it like a file on the filesystem and ask commitlint to load a configuration for that path (which it won't, because the path isn't really on the filesystem). There is already special case handling for untitled files; I think doing the same for non-file schemes would make sense anyway and address this issue.
Another option could just be to try to use a config for the workspace whenever we fail to load any valid rules, under the assumption that it's probably due to lack of a valid configuration. I don't think there's a way to tell whether a config was found from @commitlint/load, you just get the resulting configuration. I'm a little unsure whether this change would make sense, since even though I can't think of a good reason to have a configuration without any rules, it might be more confusing to impose a different set of rules instead.
Handling non-file schemes is a simple change. I'll push something up.


[Runtime] Validate scribble data when metadata allocation scribbling is enabled.

Instead of scribbling each allocation as it's parceled out, scribble the entire chunk up-front. Then, when handing out an allocation, check to make sure it still has the right scribbled data in it.

This catches the overflow fixed by https://github.com/apple/swift/pull/34822.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 4f8a64b56fc24b805fa91be1c45008f7df3d8a00

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - e2d109528f1667cd3ba296c5288cb9a336462dea

@swift-ci please test os x platform

Build failed
Swift Test OS X Platform
Git Sha - e2d109528f1667cd3ba296c5288cb9a336462dea

@swift-ci please test os x platform

Build failed
Swift Test OS X Platform
Git Sha - d94cbe909846a16a03ab9052a2100eaf738f2f21

@swift-ci please test os x platform

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - b47607c34e2efbab3b69b39499305ba70eae54d5

@swift-ci please test os x platform

Build failed
Swift Test OS X Platform
Git Sha - b47607c34e2efbab3b69b39499305ba70eae54d5

@swift-ci please test windows platform


Added missing lang attributes to html element in docs.

Trac ticket number
N / A
Branch description
Provide a concise overview of the issue or rationale behind the proposed changes.
Checklist

[ ] This PR targets the main branch.
[ ] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[ ] I have checked the "Has patch" ticket flag in the Trac system.
[ ] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

Thank you for this @JohananOppongAmoateng :star:
I think there are two more places we might want to add this in:
--- a/docs/topics/http/views.txt
+++ b/docs/topics/http/views.txt
@@ -23,7 +23,7 @@ Here's a view that returns the current date and time, as an HTML document::

     def current_datetime(request):
         now = datetime.datetime.now()
-        html = "It is now %s." % now
+        html = 'It is now %s.' % now
         return HttpResponse(html)

 Let's step through this code one line at a time:
@@ -225,7 +225,7 @@ Here's an example of an async view::

     async def current_datetime(request):
         now = datetime.datetime.now()
-        html = "It is now %s." % now
+        html = 'It is now %s.' % now
         return HttpResponse(html)

 You can read more about Django's async support, and how to best use async

Can you confirm whether these should be left out and if not, add these in?

Let me add it

I think this looks good - @thibaudcolas can you confirm you're happy?

Hello 👋 @thibaudcolas  asking out of curiosity is there changes that needs to be done or it okay.


simplified replies in a file-based extendable system

the randomization function is way better mate

I haven't tested it though so we'll have to see for any bugs


FAQ update - #vac_booster_jj - issue 2182

implements text https://github.com/corona-warn-app/cwa-website/issues/2182

Internal Tracking ID: EXPOSUREAPP-11017

@MikeMcC399 Good morning! Thanks for reviewing!


unable to decode v3.0 protocol - timestamp incompatibility

Now that Dart SDK 1.13 dev builds are shipping, we are seeing v3.0 protocol where as Dart SDK 1.12 stable is v2.x. When the current client is run with 1.13, the following exception occurs. Apparently
timestamps in v2.x were int while in v3.0 they are double as the exception below shows.
Observatory listening on http://<IP_ADDRESS>:53778
Using sdk at /Users/danrubel/work/eclipse3/dart-sdk.
dart process started
Observatory listening on http://<IP_ADDRESS>:7581

socket connected
--> {"id":"1","method":"streamListen","params":{"streamId":"Isolate"}}
--> {"id":"2","method":"streamListen","params":{"streamId":"Debug"}}
--> {"id":"3","method":"streamListen","params":{"streamId":"Stdout"}}
--> {"id":"4","method":"getVM","params":{}}
<-- {"jsonrpc":"2.0","id":"1","result":{"type":"Success"}}
<-- {"jsonrpc":"2.0","id":"2","result":{"type":"Success"}}
<-- {"jsonrpc":"2.0","id":"3","result":{"type":"Success"}}
unable to decode message: {"jsonrpc":"2.0", "result":{"type":"VM","architectureBits":32,"targetCPU":"ia32","hostCPU":"Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz","version":"1.13.0-edge.7b322c246c4bd3670294485c70dad0ab87adb7de (Wed Sep 16 07:21:34 2015) on \"macos_ia32\"","pid":"24537","_assertsEnabled":false,"_typeChecksEnabled":false,"startTime":1442638868575.000000,"isolates":[{"type":"@Isolate","fixedId":true,"id":"isolates\/535398960","name":"sample_main.dart$main","number":"535398960"}]},"id":"4"}, type 'double' is not a subtype of type 'int' of 'value'.
#0      VM.startTime= (package:vm_service_lib/vm_service_lib.dart:1779:7)
#1      VM.VM.fromJson (package:vm_service_lib/vm_service_lib.dart:1758:5)
#2      VM.parse (package:vm_service_lib/vm_service_lib.dart:1749:36)
#3      createObject (package:vm_service_lib/vm_service_lib.dart:291:34)
#4      VmService._processMessage (package:vm_service_lib/vm_service_lib.dart:269:32)
#5      _RootZone.runUnaryGuarded (dart:async/zone.dart:1103)
#6      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:341)
#7      _DelayedData.perform (dart:async/stream_impl.dart:595)
#8      _StreamImplEvents.handleNext (dart:async/stream_impl.dart:711)
#9      _PendingEvents.schedule.<anonymous closure> (dart:async/stream_impl.dart:671)
#10     _microtaskLoop (dart:async/schedule_microtask.dart:43)
#11     _microtaskLoopEntry (dart:async/schedule_microtask.dart:52)
#12     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
#13     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)

<-- {"jsonrpc":"2.0", "result":{"type":"VM","architectureBits":32,"targetCPU":"ia32","hostCPU":"Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz","version":"1.13.0-edge.7b322c246c4bd3670294485c70dad0ab87adb7de (Wed Sep 16 07:21:34 2015) on \"macos_ia32\"","pid":"24537","_assertsEnabled":false,"_typeChecksEnabled":false,"startTime":1442638868575.000000,"isolates":[{"type":"@Isolate","fixedId":true,"id":"isolates\/535398960","name":"sample_main.dart$main","number":"535398960"}]},"id":"4"}

@danrubel, I think this is done as well?

Yes, this is fixed in latest 1.13 build.


pipenv basic tutorial should link to valid values of python_version

Reading the basic usage tutorial through for the first time mentions python_version, but doesn't link to what the acceptable values are for that option.
Concretely, since my project uses PyPy, I put pypy in there, which appears to "work" in the sense that the virtualenv was created using PyPy when then running pipenv install, but I had to guess whether that was actually a thing.

PyPy isn't actually a valid python version that can be enforced afaik.  But this is a good point, I probably implemented a bunch of this and I actually have no idea what is valid here.

To be clear -- is the python_version here just referring to the PEP 508 thing called python_version?

Yeah OK, from looking at what module parses that value, which is literally called pep508parser, I guess that's a "yes" :)

That is correct!


Config detail request

could u provide the all config detail for reproducing the paper results? For example, the model with pretrained and without pretrained version. By the way, must i use the audio with resample rate 32k?

The paper config is indeed the default config used in ex_audioset.py.
Train an ImageNet pre-trained model on AudioSet with the paper config:
python ex_audioset.py --cuda --train --pretrained_name=mn10_im_pytorch

Train a model on AudioSet with the paper config from scratch:
python ex_audioset.py --cuda --train

Technically it is possible to use audio with a different sampling rate. The code in this repo allows to use 16k and 8k. However, I can't make statements about the expected performance, as I only trained models with 32k sampling rate.


Including the word Features in your project namespace breaks conventions

I created a new ASP.NET Core 2.1 MVC project and named the project ASPNETCoreMVC.Features.Web.
I added <PackageReference Include="OdeToCode.AddFeatureFolders" Version="2.0.1" /> to my .csproj.
When I run the app it says
An unhandled exception occurred while processing the request.
InvalidOperationException: The view 'Index' was not found. The following locations were searched:
Features\Web\Features\Home\Index.cshtml
Features\Shared\Index.cshtml
\Features\Index\Home.cshtml

In this case I'd need to change FeatureFolderOptions.FeatureFolderName to something other than Features because
@namespace.Split('.')
	 .SkipWhile(s => s != _folderName)
	.Aggregate("", Path.Combine);

is going to stop too early and create the wrong folder path.
Here is an ugly solution
.AddFeatureFolders(new FeatureFolderOptions
{
    FeatureFolderName = "Features",
    DeriveFeatureFolderName = model =>
    {
        string assemblyNamespacePrefix = $"{typeof(Startup).Namespace}.";
        string @namespace = model
                .ControllerType
                .Namespace
                .Remove(0, assemblyNamespacePrefix.Length);

        string result = @namespace.Split('.')
                                .SkipWhile(s => s != "Features")
                                .Aggregate("", Path.Combine);

        return result;
    }
});

But maybe the best thing to do is add a disclaimer to the README.md that your feature folder name cannot be in the project namespace?

Yes, I think the best change would be in the documentation.

I can PR this.


Extract out coin-selection and primitive libraries.

Issue number
ADP-2386
Summary
This PR extracts out the following libraries:

cardano-wallet-coin-selection
cardano-wallet-primitive

Details

The cardano-wallet-coin-selection library:

contains modules that relate to coin selection algorithms.
can eventually be imported by our balance-transaction library.

The cardano-wallet-primitive library:

contains just the subset of Primitive modules on which both cardano-wallet and cardano-wallet-coin-selection currently depend.
does not contain all modules from the Primitive hierarchy, as this hierarchy has a very large transitive dependency footprint.

Testing

cardano-wallet-coin-selection

tested by hydra here (log)

cardano-wallet-primitive

tested by hydra here (log)

Direction
We intend to steadily reduce the size of the cardano-wallet-primitive library and eventually eliminate it, by revising cardano-wallet-coin-selection (and balance-transaction) so that it does not depend on these types.

bors try

bors r+

It looks like the failure above is indeed reproducible on master (i.e., not caused by this PR):

I'm going to merge this PR manually, since:

We already have one successful bors try (https://github.com/input-output-hk/cardano-wallet/pull/3591#issuecomment-1319509062)
The last run of bors r+ (https://github.com/input-output-hk/cardano-wallet/pull/3591#issuecomment-1319932086) failed with one error, but that error is reproducible on master. (https://github.com/input-output-hk/cardano-wallet/pull/3591#issuecomment-1319947127)
I have confirmed that all tests pass on my local machine.


Error in creating, updating, deleting scopes in the Petstore API

Create API from swagger petstore url: http://petstore.swagger.io/v2/swagger.json
Try to modifiy scopes: it gives no errors but there is no changes

Hi @stefanonegri ,
I hope this is in APIM 3.0.0 ?

Hi @stefanonegri ,
Thank you for reporting this issue, I was able to reproduce this in APIM 3.0.0 latest pack.
Steps to reproduce:

Create swagger pet store API from the http://petstore.swagger.io/v2/swagger.json URL
Goto scopes page
Add a new scope

Request payload contains the newly added scope, but the response doesn't contain it

curl 'https://localhost:9443/api/am/publisher/v1.0/apis/60de014b-0f67-4338-8718-ffb76a4f3242' -X PUT -H 'Connection: keep-alive' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache' -H 'authorization: Bearer 59760fff-fd37-3621' -H 'Origin: https://knnect.lk' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36' -H 'Content-Type: application/json' -H 'Accept: */*' -H 'Sec-Fetch-Site: same-origin' -H 'Sec-Fetch-Mode: cors' -H 'Referer: https://knnect.lk/testapp/apis/60de014b-0f67-4338-8718-ffb76a4f3242/scopes/create' -H 'Accept-Encoding: gzip, deflate, br' -H 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' -H 'Cookie: AM_ACC_TOKEN_DEFAULT_P2=-a630-046309cc9a1d; opbs=153ee638-e606-432c-aa9e-ca981cbd6235' --data-binary '{"id":"60de014b-0f67-4338-8718-ffb76a4f3242","name":"SwaggerPetstore","description":null,"context":"/v2","version":"1.0.3","provider":"admin","lifeCycleStatus":"PUBLISHED","wsdlInfo":null,"responseCachingEnabled":false,"cacheTimeout":300,"destinationStatsEnabled":null,"hasThumbnail":null,"isDefaultVersion":false,"enableSchemaValidation":true,"type":"HTTP","transport":["http","https"],"tags":[],"policies":["Gold"],"apiThrottlingPolicy":"Unlimited","authorizationHeader":"Authorization","securityScheme":["oauth2","oauth_basic_auth_api_key_mandatory"],"maxTps":null,"visibility":"PUBLIC","visibleRoles":[],"visibleTenants":[],"endpointSecurity":null,"gatewayEnvironments":["Production and Sandbox"],"labels":[],"mediationPolicies":[],"subscriptionAvailability":"ALL_TENANTS","subscriptionAvailableTenants":[],"additionalProperties":{},"monetization":null,"accessControl":"NONE","accessControlRoles":[],"businessInformation":{"businessOwner":null,"businessOwnerEmail":null,"technicalOwner":null,"technicalOwnerEmail":null},"corsConfiguration":{"corsConfigurationEnabled":false,"accessControlAllowOrigins":["*"],"accessControlAllowCredentials":false,"accessControlAllowHeaders":["authorization","Access-Control-Allow-Origin","Content-Type","SOAPAction"],"accessControlAllowMethods":["GET","PUT","POST","DELETE","PATCH","OPTIONS"]},"workflowStatus":null,"createdTime":"2019-10-28 12:36:09.805","lastUpdatedTime":"2019-11-07 08:48:36.244","endpointConfig":{"endpoint_type":"http","sandbox_endpoints":{"url":"http://localhost:8000/apis"},"production_endpoints":{"url":"http://localhost:8000/apis"}},"endpointImplementationType":"ENDPOINT","scopes":[{"name":"read:pets","description":"read your pets","bindings":{"type":null,"values":[]}},{"name":"write:pets","description":"modify pets in your account","bindings":{"type":null,"values":[]}},{"name":"sample_scope","description":"sample","bindings":{"type":"role","values":["admin"]}}],"operations":[{"id":"","target":"/user/createWithList","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/{petId}/uploadImage","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/findByStatus","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/{username}","verb":"DELETE","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/{petId}","verb":"DELETE","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/store/order/{orderId}","verb":"DELETE","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/store/order","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/createWithArray","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/{username}","verb":"PUT","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/login","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/store/inventory","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/{petId}","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/store/order/{orderId}","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/{username}","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/{petId}","verb":"POST","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet","verb":"PUT","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/user/logout","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]},{"id":"","target":"/pet/findByTags","verb":"GET","authType":"Application & Application User","throttlingPolicy":"Unlimited","scopes":[],"usedProductIds":[]}],"threatProtectionPolicies":null}' --compressed --insecure

This issue occurs when there is more than one security definition with type "oauth2" in the swagger definition and their order matters.
When adding a new scope to the pet store API, the "default" security definition gets added to the swagger as the last element in the security definition list as follows. Note that all new scopes will be added to the "default" security definition.
"securityDefinitions": {
  "api_key": {
   "type": "apiKey",
   "name": "api_key",
   "in": "header"
  },
 "petstore_auth": {
   "type": "oauth2",
   "authorizationUrl": "https://petstore.swagger.io/oauth/authorize",
   "flow": "implicit",
   "scopes": {
    "read:pets": "read your pets",
    "write:pets": "modify pets in your account"
   }
  "default": {
   "type": "oauth2",
   "authorizationUrl": "https://test.com",
   "flow": "implicit",
   "scopes": {
    "read:pets": "read your pets",
    "newscope": "this is a new scope",
    "write:pets": "modify pets in your account"
   },
   "x-scopes-bindings": {
    "write:pets": "",
    "newscope": "",
    "read:pets": ""
   }
  },
  }

When retrieving the scopes of the API, we get the first matching Oauth2 type security definition from the list in the swagger as the OAuth2SecuritySchemeKey [1]. In the pet store API, the security definition returned is "petstore_auth". Hence only the originally existing scopes are always shown in the UI and the changes don't get affected.
Changing the order of "default" and "petstore_auth" as follows, solves the issue.
"securityDefinitions": {
  "api_key": {
   "type": "apiKey",
   "name": "api_key",
   "in": "header"
  },
  "default": {
   "type": "oauth2",
   "authorizationUrl": "https://test.com",
   "flow": "implicit",
   "scopes": {
    "read:pets": "read your pets",
    "newscope": "this is a new scope",
    "write:pets": "modify pets in your account"
   },
   "x-scopes-bindings": {
    "write:pets": "",
    "newscope": "",
    "read:pets": ""
   }
 "petstore_auth": {
   "type": "oauth2",
   "authorizationUrl": "https://petstore.swagger.io/oauth/authorize",
   "flow": "implicit",
   "scopes": {
    "read:pets": "read your pets",
    "write:pets": "modify pets in your account"
   }
  },
  }

Therefore when adding the "default" security definition, we should add it as the first element in the list.
@ruks Is this feasible?
[1] https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/definitions/OAS2Parser.java#L751-L762


Unable to deploy cluster if subnets are specified

Hi,
I'm trying to deploy HA cluster using kube-aws, but as soon as I add subnets definition as shown in documentation, deployment fails with the following error. Without subnets everything works great.
kube-aws up --s3-uri s3://<bucket>
Creating AWS resources. Please wait. It may take a few minutes.
Error: Error creating cluster: Stack creation failed: CREATE_FAILED : The following resource(s) failed to create: [Controlplane].

Printing the most recent failed stack events:
CREATE_FAILED AWS::CloudFormation::Stack production The following resource(s) failed to create: [Controlplane].
CREATE_FAILED AWS::CloudFormation::Stack Controlplane Embedded stack arn:aws:cloudformation:eu-central-1:<EDITED-STACK-ID> was not successfully created: The following resource(s) failed to create: [InternetGateway, IAMRoleEtcd, VPC, Etcd2EIP, Etcd1EIP, NatGatewayManagedPrivateSubnet1EIP, NatGatewayManagedPrivateSubnet2EIP, NatGatewayManagedPrivateSubnet3EIP, Etcd0EIP].

here is my cluster.yaml
clusterName: cluster
releaseChannel: stable
apiEndpoints:
- name: default
  dnsName: cluster.<domain>
  loadBalancer:
    createRecordSet: true
    subnets:
    - name: ManagedPublicSubnet1
    - name: ManagedPublicSubnet2
    - name: ManagedPublicSubnet3

    hostedZone:
      id: "EDITED"

region: eu-central-1
kmsKeyArn: "EDITED"

controller:
  instanceType: t2.medium

  autoScalingGroup:
    minSize: 3
    maxSize: 3

  subnets:
    - name: ManagedPublicSubnet1
    - name: ManagedPublicSubnet2
    - name: ManagedPublicSubnet3

worker:
  nodePools:
  - name: nodepool1
    instanceType: t2.medium
    waitSignal:
      enabled: true
      maxBatchSize: 1

    autoScalingGroup:
      minSize: 1
      maxSize: 5
      rollingUpdateMinInstancesInService: 2
    autoscaling:
      clusterAutoscaler:
        enabled: true
    clusterAutoscalerSupport:
      enabled: true

    nodeDrainer:
      enabled: true
    subnets:
      - name: ManagedPublicSubnet1

  - name: nodepool2
    instanceType: t2.medium
    waitSignal:
      enabled: true
      maxBatchSize: 1

    autoScalingGroup:
      minSize: 1
      maxSize: 5
      rollingUpdateMinInstancesInService: 2
    autoscaling:
      clusterAutoscaler:
        enabled: true
    clusterAutoscalerSupport:
      enabled: true

    nodeDrainer:
      enabled: true

    subnets:
      - name: ManagedPublicSubnet2

etcd:
  count: 3
  instanceType: t2.medium

  rootVolume:
    size: 30
    type: gp2
    iops: 0

  dataVolume:
    size: 30
    type: gp2
    iops: 0
    encrypted: true
    ephemeral: false

  version: 3.2.1
  snapshot:
    automated: true

  disasterRecovery:
    automated: true

  subnets:
    - name: ManagedPrivateSubnet1
    - name: ManagedPrivateSubnet2
    - name: ManagedPrivateSubnet3

vpcCIDR: "<IP_ADDRESS>/16"

subnets:
  - name: ManagedPublicSubnet1
    availabilityZone: eu-central-1a
    instanceCIDR: "<IP_ADDRESS>/24"
  - name: ManagedPublicSubnet2
    availabilityZone: eu-central-1b
    instanceCIDR: "<IP_ADDRESS>/24"
  - name: ManagedPublicSubnet3
    availabilityZone: eu-central-1c
    instanceCIDR: "<IP_ADDRESS>/24"

  - name: ManagedPrivateSubnet1
    private: true
    availabilityZone: eu-central-1a
    instanceCIDR: "<IP_ADDRESS>/24"

  - name: ManagedPrivateSubnet2
    private: true
    availabilityZone: eu-central-1b
    instanceCIDR: "<IP_ADDRESS>/24"

  - name: ManagedPrivateSubnet3
    private: true
    availabilityZone: eu-central-1c
    instanceCIDR: "<IP_ADDRESS>/24"

@lwolf are you sure you are not trying to change subnets for an existing cluster?

Hi @lwolf what are the errors shown in AWS console - Cloudformation events

@camilb thanks. My bad, I was looking only to the latest event. The problem is
The maximum number of addresses has been reached

@lwolf you can use
memberIdentityProvider: eni

to stop Etcd cluster using EIP and start using separately created ENI

@redbaron Thanks, good to know.
It's marked as EXPERIMENTAL. How stable is it in 0.9.7?

works for me since the beginning :)

Increased EIP limit for now :)
Thanks for the quick help


Add menu entry for "recently opened files"

Is your feature request related to a problem? Please describe.
Use-case: We create our process models with the program „Camunda Modeler“. Oftentimes, we work on several projects at the same time, which are located in different folders on the computer.
As of now, it’s a bit cumbersome to open the process models in the Modeler because it does not have the menu entry for “open recently opened files”. Sure, it’s possible to open the models via the IDE. But there are cases where we work mostly on the models and hence primarily with the Modeler.
Describe the solution you'd like
Add a menue entry to the file menue which allows to view and open "recently opened files".
Describe alternatives you've considered
n/a
Additional context
SUPPORT-8641

Moving to backlog since requirement seems clear to me.

There are already solutions available for this request.
(1) Recent files as part of the "plus" button, see prototype v14:

(2) Recent files listed on the welcome tab, see prototype v14:

Solution (1) is preferred since it is always accessible and not part of just one specific view. In addition, such a list should also be part of the app menu.

Good catch, we overlooked this one.

Closed via https://github.com/camunda/camunda-modeler/issues/3917.


Beautify Project

Add theming
Add titles / subtitles to each page
Add Readme
Add helper text to anything that might need explaining
Create nice "Home" page

Essentially the content of the Readme, but abbreviated

Closing #2 In favor of this issue


Need ability to modify ObjectMapper created by JacksonJsonPayloadConverter

Is your feature request related to a problem? Please describe.
When building a Temporal app using Scala, we need to add jackson-scala-module so it knows how to handle Scala types.  However, we need access to the ObjectMapper to do this.
This isn't useful for just Scala; for example, we also have a few other org-specific Jackson modules that we use to make using Twilio-internal JVM types easier with Jackson.
Describe the solution you'd like
Two options come to mind:

A new constructor for JacksonJsonPayloadConverter that allows us to pass our own ObjectMapper.
A getObjectMapper() method that returns the ObjectMapper that's already been created, which allows us to augment its configuration.

Describe alternatives you've considered
Right now I'm using fragile bits of reflection to fetch the private ObjectMapper field to make modifications to it.  Obviously, that's not sustainable.
Additional context
n/a

Same issue with Kotlin data classes.
To save time for anybody until the issue is resolved, the reflection based workaround for Kotlin is as follows:
val jacksonJsonPayloadConverter = JacksonJsonPayloadConverter()
val privateMapperField = JacksonJsonPayloadConverter::class.java.getDeclaredField("mapper");
privateMapperField.isAccessible = true
privateMapperField.set(
    jacksonJsonPayloadConverter,
    ObjectMapper().registerKotlinModule().findAndRegisterModules()
)

val defaultDataConverter =
        DefaultDataConverter(NullPayloadConverter(), ByteArrayPayloadConverter(), jacksonJsonPayloadConverter)
val workflowClientOptions = WorkflowClientOptions.newBuilder()
        .setDataConverter(defaultDataConverter)
        .build()

val client = WorkflowClient.newInstance(service, workflowClientOptions)

Public constructor that takes ObjectMapper added to JacksonJsonPayloadConverter by https://github.com/temporalio/java-sdk/pull/150


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=415217470
https://github.com/Azure/azure-cli-extensions/commit/3af42722afb8d650392212fec3ccccaaf991d41b

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

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


Implement SSR

 Issue by arunoda
Monday Aug 15, 2016 at 08:11 GMT
Originally opened as https://github.com/storybooks/getstorybook.io/issues/13

Implement the SSR support.
Initially we could use something like prerender.io for the simplicity.

Hey I finished this when we ported to Gatsby. Closing! 👍


consider enhancing MCMC sampling for parameters on constrained domains

e.g., for non-negative parameters, think about:

sampling on log scale
reflecting proposals back across zero (I forget the name of this)

We've had both of these in place for a long time.


Feats with charges don't send a chat message when deactivated.

Feats with charges set create a chat message when activated, but not when deactivated. The feat is properly deactivated, with modifiers being turned off, but nothing to chat.
To reproduce, add a feat with an activation cost and max charges. Activate and deactivate the feat.

Fixed for the next release, thanks for the report. :)


tinylog has no module-info

Required filename-based automodules detected: [tinylog-1.3.6.jar]. Please don't publish this project to a public artifact repository!

Can be fixed by updating to tinylog 2.x


changes in license header

tested locally after the changes with mvn clean install -Dfull -TC1 -- build was successful

master: aecfa178f30bde1c27c5de5df9f72b8bf58328ae


Update RST spec to include a nextSibling pointer

*and possibly a parent pointer.
Currently, the RST spec only allows one form of traversal: from root to leaf. This isn't ideal, since we occasionally need to check some predicate for either a sibling node. I suggest we add a nextSibling pointer, so we can traverse siblings as a singly linked list (prevSibling could be included but I haven't found it super useful yet)
I did some work with a similar tree format and found that it wasn't too hard to add these pointers.
As an example of an existing pain point, think about adjacent sibling selectors. Currently, we need to find the parent of the node (if we don't already have a reference to it that means we need a reference to the root node and have to traverse the ~whole tree in the worst case) and iterate through the children.
With a nextSibling pointer we could just do a constant-time operation by running the predicate against node.nextSibling. It also makes general sibling selectors easier.
I'm not sure if a parent pointer would be useful yet, but it could be 🤔

If we agree that this is an acceptable change to the RST spec I can include the changes to the adapters and spec alongside the work I'm doing integrating a CSS parser with the RST traversal stuff.

Would adding a parent pointer preclude the need for sibling iterators? It might be less complex then enforcing the idea of a finite and non-repeating list of ordered siblings.

In what situations could an RST represent a set of child nodes that aren't finite, unique and ordered?   I think even if an element was repeated it would be represented by a unique node, but I'm not sure.
Having just a parent pointer would be a find compromise though. It would still require a linear search for sibling selectors but that's probably not too costly in most cases.

All three seem reasonable fwiw (nextSibling, prevSibling, parent) but it'd be nice to minimize the API surface :-)

While working on https://github.com/airbnb/enzyme/pull/1086 I found that the only time I needed to get the parent was to get a sibling, and I never had to match a previous sibling since CSS selectors only match following siblings.
So I think we could get away with just nextSibling unless there are other APIs that would benefit from prevSibling or parent?

If we have next, I think we need prev. I'm less concerned about parent tho, since theoretically you got to a node from the parent.

Without a parent link how do you implement https://github.com/airbnb/enzyme/blob/master/docs/api/ShallowWrapper/parent.md ? By starting from the root and following children until you get to the current node?

@nfcampos that's exactly how it does it: https://github.com/airbnb/enzyme/blob/master/packages/enzyme/src/RSTTraversal.js#L74-L76
I was only thinking about it in the context of the selector API, but a parent pointer would definitely be helpful here. Since it's an internal API used only by adapters, maybe it's OK to increase the API surface and add all three? prevSibling is the least useful, but it does make sense to include it if we have nextSibling (which is really useful).

Sounds like there's use cases for all three then.
@lelandrichardson, thoughts?

@aweary i worry about adding these types of things when JS doesn't have weak references. I think it also makes actually building an RST much more complicated. Since this is just traversal stuff, It'd be nice if any logic around prev/next sibling etc was contained inside enzyme. If we wanted to transform an RST into a structure that had these pointers, that might make sense... but i also am not sure i'm convinced that this is a good idea.


cannot link directly with dylib/framework

Description
I created a new npm project and install npm install --save @eyevinn/srt. It asked me to install cmake which i did. Everything gets built when ./configure ran until this error shows up.

Macbook PRO
macOS Catalina 10.15.3
NodeJS v10.20.1
cmake version 3.18.1

Scanning dependencies of target srt_shared
[ 80%] Building C object CMakeFiles/srt_shared.dir/cmake_object_lib_support.c.o
[ 82%] Linking CXX shared library libsrt.dylib

/Users/johndavedecano/Projects/node-srt/node_modules/@eyevinn/srt/deps/srt/srtcore/fec.cpp:976:20: warning: unused function 'CellMark' [-Wunused-function]
static inline char CellMark(const std::deque<bool>& cells, int index)
                   ^
1 warning generated.
ld: cannot link directly with dylib/framework, your binary is not an allowed client of /usr/lib/libcrypto.dylib for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libsrt.1.4.1.dylib] Error 1
make[1]: *** [CMakeFiles/srt_shared.dir/all] Error 2
make: *** [all] Error 2

npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

Thanks, I haven't seen this issue myself before. Will need to investigate.

Same Issue here running Catalina 10.15.5. The Issue seems to be Apple not allowing to link to the system supplied Openssl library.
Resolved it by following this Issue/Guide on Stackoverflow.
https://stackoverflow.com/questions/59006602/dyld-library-not-loaded-usr-local-opt-openssl-lib-libssl-1-0-0-dylib

Thank you, I will write a note that it requires a newer version of openssl. Which version of openssl did you get it to work with. This one?
brew switch openssl 1.0.2q

You can also fix this issue with:
export LDFLAGS="-L/usr/local/opt/openssl/lib"
export CPPFLAGS="-I/usr/local/opt/openssl/include"
export PKG_CONFIG_PATH="/usr/local/opt/openssl/lib/pkgconfig"

See what I wrote on: https://github.com/Eyevinn/node-srt/pull/14

^
In case you want to actually keep your up-to-date OpenSSL install from brew (or whereever), which is actually I think from a security point of view a much better idea ... :)
Moreover, I think there is a breaking change between 1.0 and 1.1 (it doesn't make sense in terms of sem-ver, but basically some function that was de-facto public was made officially private, but that broke some apps using it afair - there is a way to fix that app-side obviously with a different now public functionality provided in 1.1).


[FLINK-16916][serialization] Fix the logic of NullableSerializer#copy

What is the purpose of the change
Fix the wrong logic of NullableSerializer#copy,
currently, the logic is such as below:
public void copy(DataInputView source, DataOutputView target) throws IOException {
   boolean isNull = source.readBoolean();
   target.writeBoolean(isNull);
   if (isNull) {
      target.write(padding);
   }
   else {
      originalSerializer.copy(source, target);
   }
}

we forgot to skip paddings.length bytes when if the padding's length is not 0.
We can correct the logic such as below
public void copy(DataInputView source, DataOutputView target) throws IOException {
   boolean isNull = deserializeNull(source); // this will skip the padding values.
   target.writeBoolean(isNull);
   if (isNull) {
      target.write(padding);
   }
   else {
      originalSerializer.copy(source, target);
   }
}

Verifying this change
Harden the test of NullalbeSerialierTest#testSerializedCopyAsSequence by update the test data.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (yes)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @aljoscha

Good fix! I will wait for Travis or Azure and then merge.

@flinkbot run azure

@flinkbot run travis

@flinkbot run azure

@flinkbot run travis

Thanks for the fix! 🍵

@aljoscha thanks for the review and merging.


user12986714: Watch nass?\W*+cleaners?(?!.com)

user12986714 requests the watch of the watch_keyword nass?\W*+cleaners?(?!\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

nass?\W*+cleaners?(?!\.com) has been seen in 2 true positives, 0 false positives, and 0 NAAs.

See chat


Pull request intake form (PR template)

Creating template for pull request.
Issue #, if available: ~None~
Description of changes:
Creating template for pull request. It will add pull request intake form for Security plugin.  Idea behind creating this template is for asking community members to provide as much details as possible about changes.
Please suggest any additional/missing questions for this template.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Is it possible to make the label madatory? Labeling will category the PRs and help release note drafter position the PRs in proper sections in release notes.

It will be good to add category such as enhancement, new functionality, bug fix, refactoring and project maintenance to the template and require certain items only for specific categories. Another option is to use labels, but it is easier to forget to apply label.

Is it possible to make the label madatory? Labeling will categorize the PRs and help release note drafter position the PRs in proper sections in release notes automatically.

Added Category field for same.  Not sure if there is a way to make some field mandatory.

It will be good to add category such as enhancement, new functionality, bug fix, refactoring and project maintenance to the template and require certain items only for specific categories. Another option is to use labels, but it is easier to forget to apply label.

Added category field.


Remove digiwf-schema-registry

Remove digiwf-schema-registry
Todo

Delete package

Hey team! Please add your planning poker estimate with Zenhub @dominikhorn93 @lehju @StephanStrehlerCGI @lmoesle

Please add your planning poker estimate with Zenhub @darenegade


gh-pages forcing HTTP

It would be nice if the gh-pages URL's for this project didn't redirect to sindresorhus.com (forcing HTTP), so that apps could use the script from gh-pages directly.
I.e. currently https://sindresorhus.github.io/screenfull.js/dist/screenfull.min.js redirects to http://sindresorhus.com/screenfull.js/dist/screenfull.min.js, causing browser to throw cross-scheme exception.
Thanks for considering and for the useful tool.

That's intentional. You absolutely shouldn't directly link that. GitHub has hotlink limits. Rather use the referenced CDN link if you want to directly link to the script ;)


CORS error on viewing images

OPTIONS http://localhost:8080/api/fileOps 403
Access to XMLHttpRequest at 'http://localhost:8080/api/fileOps' from origin 'http://localhost:3000
Getting the following error when clicking on Explore Public Images and My Gallery.
Must have something to do with ALLOW_CORS_ORIGINS setup

Hi Aravind,
We have fixed this issue. It would be great if you review it and revert.

Will do.
Also, it'd be great if all commit messages followed this format:
"#<issue_number>:   <usual_commit_message>"
Advantage of this is that the commit gets automatically referenced to the issue and can be viewed in the respective Issue's page

Thank you, Aravind. Will keep this in mind.

Hi Aravind, Please read the wiki again and then review.
We have changed the download microservice to explore microservice

Works for me! Great!


[fix](disk balance) Change disk rebalance unpick time to configurable…

run buildall

https://github.com/apache/doris/pull/28949


rocksdb: use new pipelined-write to replace multibatch-write

What is changed and how it works?

Issue Number: Close https://github.com/tikv/tikv/issues/12059
What's Changed:

I refactor the pipelined-write referring the solution of cockroachdb. See the design details in https://github.com/cockroachdb/pebble/blob/master/docs/rocksdb.md#commit-pipeline
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Integration test
Manual test (add detailed scripts or steps below)

Side effects

Breaking backward compatibility

Release note
* The configure rocksdb.enable-multibatch-write will be discarded.  And if user set both rocksdb.enable-pipelined-write and rocksdb.enable-unordered-write false, TiKV will enable the new pipeline write. Otherwise, TiKV will use either original pipelined-write or unordered-write.

/test

/merge

/test


apps/hubble: fix docker-compose.yml warning

"version is obsolelte"
Docker has made this line obsolete, no need to nention docker compose version
Motivation
Describe why this issue should be fixed and link to any relevant design docs, issues or other relevant items.
Change Summary
Describe the changes being made in 1-2 concise sentences.
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[ ] PR title adheres to the conventional commits standard
[ ] PR has a changeset
[ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[ ] PR includes documentation if necessary.
[ ] All commits have been signed

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

PR-Codex overview
This PR updates the docker-compose.yml file for the hubble service to use version 3.9 and the latest image farcasterxyz/hubble:latest.
Detailed summary

Updated docker-compose.yml to version 3.9
Changed hubble service image to farcasterxyz/hubble:latest

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Thanks!


[BUGFIX] Update operator to work with Checkpoints

As of Great Expectations v0.13.8, we use SimpleCheckpoints instead of the former ValidationOperators. This PR updates the airflow-provider-great-expectations to reflect this change.

Thanks for the review, @spbail!

After adding logic to handle either config v2.0 or v3.0, I realized that LegacyCheckpoint can already handle both, so I've kept that logic as is.
I've removed the comments/prints.
The data_context.run_checkpoint() method appears to be experimental, and it looks like it might not be possible to use that here given I'm not working with a saved checkpoint, but rather instantiating a LegacyCheckpoint and running it immediately. I do think it would make sense to use that when we have update this to work with the v3 Batch Request API. Is that a correct assessment?
I have tested this with the v2.0 config, and the v3.0 config, both with the v2 Batch Kwargs API. When the v3 Batch Request API solidifies, we will need to update this and re-test. This will fail on versions of GE that don't have class-based checkpoints implemented (<0.13.8)


feat(plugins): allow plugins to export a name for use in reporting

@sjelin one more for you!

LGTM

Thanks! Merged.


Can't read the properties something of 'usePageContext()'

Sometimes using rakkasjs hooks like usePageContext and useLocation throws error showing cant read the properties something of null

also sometimes i get random error showing TypeError: Invalid URL

TypeError: Cannot read properties of null (reading 'useLocation')
This was what I got

It's because of this bug: https://github.com/vitejs/vite/issues/3301 It probably kicks in when editing the entry-client file. Vite has some problems when doing HMR with React context. I'll see what I can do but it's a long standing issue :/

hey, I think this one was solved by the beta update of vite-plugin-react
<EMAIL_ADDRESS>

hey, I think this one was solved by the beta update of vite-plugin-react<EMAIL_ADDRESS>
Awesome, I'll try it soon. I think Vite 4 is just around the corner anyway. I'll try to coincide Rakkas 0.7 with it.

hey, I think this one was solved by the beta update of vite-plugin-react<EMAIL_ADDRESS>
Awesome, I'll try it soon. I think Vite 4 is just around the corner anyway. I'll try to coincide Rakkas 0.7 with it.

very excited to see rakkas v0.7 🥳

this is still not fixed

You're right. I'll look into it more thoroughly.

I've been failing to replicate this for sometime. Do you have a repro somewhere? Also, are you on a monorepo setup? I think it might be relevant.

I think it's now fixed. BTW is fast refresh disabled by default on rakkasv7? last time i had to manually enable fast refresh. After enabling fast refresh, i was not getting any context related issues. I'd inform you after using it more. For now closing this issue

is fast refresh disabled by default on rakkasv7?

Erm, no? That's weird. How did you enable it?

Oh i used react field on rakkas' vite plugin 😃


[Defect] Chaos Bolt on-use macro does not apply damage.

The macro works as intended such that it changes the damage type and then applies damage to a target. However, when the macro completes there is an error response in the log:
TypeError: rollTerms is undefined
    createDamageList https://bradfordly-coi-vol-one.forge-vtt.com/modules/midi-qol/src/module/utils.js:87
    DamageOnlyWorkflow https://bradfordly-coi-vol-one.forge-vtt.com/modules/midi-qol/src/module/workflow.js:2583
    anonymous https://assets.forge-vtt.com/bazaar/modules/advanced-macros/v1.14.1/Macros.js line 169 > Function:42
Macros.js:212:13
    executeMacro https://assets.forge-vtt.com/bazaar/modules/advanced-macros/v1.14.1/Macros.js:212

The called dependencies seem to implicate an issue with some embedded macro functionality with the Midi QOL module.

Updated title of issue: the macro since last being worked on now no longer applies any damage after a damage type is selected from the rolled damage. It is being assumed that the "chaos bounce" affect is also malfunctioning.


[headers] : update the User-Agent

This is more of a question than a issue. Should we update the user agent for every new release?
User agent option

I think we can close this issue now @davidjpeacock


Limit reaction avatars to 2 when there are too many

See it here: https://github.com/babel/babel/pull/3646
CSS-only change. Can send PR
GitHub

Refined GitHub

Suggested

:+1:

👍 PR welcome :)

Can you leave all the reactions on this post so I can test it out with a non-locked thread?


Draw chart of : Floating point Value

Hi @shaishavgandhi05
is it possible to draw a chart of floating point value as per your library it only support Integer value, if it's possible then how? please guide me.
Thanks. (_)

One way would be to round your floats to the nearest Integer, but keep the labels as floats. Alternatively, if you're trying to plot very minute floating point differences (7.4, 7.5, 7.8, 7.9) you could also multiply by 10, plot it, but keep the labels as the original value. Let me know if that works

Hi @shaishavgandhi05
I think this is not a right way to display, because a floating point value multiply by 10 and after round up that value it may causes a large difference of value that is affected on chart.
so that's not work, if u any other solution then please tell me.
thanks.

Could you post the same dataset you're referring to?

Floating value support added in v1.0.3


add future package as dependency

resolves #12

Interesting. The only change was including future as a dependency in requirements.txt and setup.py, but Travis log shows 10 tests have failed...

Coverage decreased (-0.3%) to 97.82% when pulling ac6b5ad988cb62443727ae70fcbcc7a3b47592ac on gboeing:master into 4504333d959ff59126ca6172f8f068fa55a08bfa on timothyb0912:master.

Everything seems to be working now. The failing tests seem to have something to do with the behavior of scipy sparse matrices performing a dot product with 2D numpy arrays or numpy matrices. I don't really know what exactly changed, but it was a bit of a pain to track down and fix.
In any case, thanks for taking care of this dependency issue!


update communication channels

 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.

/run-all-tests

/cherrypick release-2.4

/cherrypick release-2.5


KaraxInstance null in kajax callback

The redraw that's ultimately called in the line below receives a null KaraxInstance for some reason under Nimib.
https://github.com/karaxnim/karax/blob/master/karax/kajax.nim#L75
I've tried this with Nim 2.0.8 and Nim 2.2.0. It doesn't seem to be an issue with Karax because the ajax example in their repo works fine.

Thanks for letting us know 😄
I don't think I ever tried Kajax when developing the Karax support in nimib so it might never have worked. I'll have a look during the week 👍

Do you have a reproducible example by any chance?

Give this a try:
import nimib

nbInit

nbKaraxCode:
    import karax/kajax

    proc handleRatesResponse(httpStatus: int, response: cstring) =
        echo response

    proc requestData() =
        let url = "https://jsonplaceholder.typicode.com/todos/1".cstring
        let headers = @[("Accept".cstring, "application/json".cstring)]
        ajaxGet(url, headers,
            cont=proc(httpStatus: int, response: cstring) = handleRatesResponse(httpStatus, response)
        )

    requestData()
    karaxHtml:
        text "Hello, World"

nbSave

It seems like it's just trying to lift the global kxi KaraxInstance from the parent scope as a parameter default, but maybe there is something weird going on there because of the macros.

Thanks, yes you are right:
proc ajaxGet*(url: cstring; headers: openarray[(cstring, cstring)];
          cont: proc (httpStatus: int, response: cstring);
          doRedraw: bool = true,
          kxi: KaraxInstance = kxi) =
  ajax("GET", url, headers, nil, cont, doRedraw, kxi)

What we do to allow multiple Karax apps to run at the same time is that we pass a custom kxiname for each one like this:
nim js -d:danger -d:kxiname=nimib_kxi_1 file.nim

So it will not find it in this case because it explicitly is looking for kxi and not our custom nimib_kxi_1

Huh, but it seems Karax should handle that correctly :O https://github.com/karaxnim/karax/blob/2536062b7c2ffc031c70b9b92216b771a1206f98/karax/karax.nim#L60

Aha! Moving the Kajax logic below the karaxHtml seems to work!
I think it has to do with Karax not being initialized before the setRenderer which is called at the end of karaxHtml

Hmm, how so? I get a compile error from the requestData under karaxHtml because it's trying to treat it as a VNode in the buildHtml macro I think.

Ahh, I was a bit unclear. I meant this:
import nimib

nbInit

nbKaraxCode:
    import karax/kajax

    proc handleRatesResponse(httpStatus: int, response: cstring) =
        echo response

    proc requestData() =
        let url = "https://jsonplaceholder.typicode.com/todos/1".cstring
        let headers = @[("Accept".cstring, "application/json".cstring)]
        ajaxGet(url, headers,
            cont=proc(httpStatus: int, response: cstring) = handleRatesResponse(httpStatus, response)
        )

    karaxHtml:
        text "Hello, World"

    requestData()

nbSave

"After" karaxHtml would have been a better word than "under".

Oh, duh! :) Reading the code, apparently there's also a postRender hook that seems to work for me as well!

Yep it runs every time Karax renders the page (for example when updating a variable used in the karaxHtml. So I'm not sure how useful it is for this case.

If you want to fetch data periodically the example I showed in the NimConf video could be useful: https://github.com/nimib-land/nimconf24/blob/7a8a2b264f5b718f4fa8029da4a999aba8347431/nimib_intro.nim#L43-L54

If you want to fetch data periodically the example I showed in the NimConf video could be useful: https://github.com/nimib-land/nimconf24/blob/7a8a2b264f5b718f4fa8029da4a999aba8347431/nimib_intro.nim#L43-L54

That's useful, thanks!
I was just trying to initialize some data, so your first solution seems to be working fine. I appreciate the help! : )


Review Substrate Connect

Edits to the Substrate Connect article based on Pierre's feedback. Please review.

(note I changed the target branch to main per convention now, you can change in editing the title of the PR and a dropdown shows up)

Some more consistency suggestions:

"light client(s)" are a technology, it is a shortening of "light blockchain client" because the client only verifies the block headers. It is  not a product or brand so should not be hyphenated or capitalised outside of usual grammatical rules.
"Substrate Connect" is the product app developers interact with and is not hyphenated. It should be capitalised if it's converted to "English" from it's npm name. I try to always refer to it using its npm name @substrate/connect but that can be awkward in headings / links etc


Add basic gman util functions

Looking for some eyes.
Let me know!

Updated PR to reflect changes in https://github.com/AFCYBER-DREAM/piedpiper-gman/pull/5


Change memory usage by minus cache memory

Fixes #10824
Calculate the real usage_memory by "used - buffers cached".
Using cgroup file is  "memory.usage_in_bytes - memory.stat.cache"
Signed-off-by: Sun Jianbo<EMAIL_ADDRESS>

@wonderflow +1 to what @avagin said,  I think we should add cache to the output then consume that on the client to clarify the results.

OK I'll add it.


Netsparker JSON Parser

Adding support for a new parser for Netsparker.  This will parse a JSON report from Netsparker.  This was tested on the latest DefectDojo code and all tests passed.
Please submit your pull requests to the 'dev' branch.
When submitting a pull request, please make sure you have completed the following checklist:

[ ] Your code is flake8 compliant (Dojo's code isn't currently flake8 compliant, but we're trying to correct that)
[ ] If this is a new feature and not a bug fix, you've included the proper documentation under the /docs folder

Closing to add to dev branch.


Index_failed metric

Hi,
Activating the -es.indices(shards) flag I see that no metric related to index_failed is extracted. Should any development needs to be done in the code to have this?

Hi @ionutancuta,
the json field is not exposed as a metric, so this needs to be implemented if you like to have such a metric. The value is unmarshaled from the json, you can find it in https://github.com/justwatchcom/elasticsearch_exporter/blob/master/collector/indices_response.go#L65. Exporting it should be straight forward. Ping me if you need help

fix by #281


Remove the CDIO Pillars page

This page is now just information about the structure of CDIO, rather than specific guidance relevant to the building or operating of services.
The information on the Cyber team is likely useful, but is better placed somewhere else. For now, any references to contacting the Cyber team have been replaced with a link to their Slack channel. This is also somewhat related to #695 which is more of a product page than guidance.

@gabrielcurrie I'd be interested in your thoughts about this. There's a reasonable amount of Cyber-related content in the GDS Way now, but a fair amount of it is not guidance about how to do a thing, but more information about the services that Cyber offers, or the structure of the team. It feels like there should be a better place for that information than here.

Hi @timblair I agree with this, and we are in the process of developing an internally-facing Google Site to host this kind of information about the team. Happy to remove from the GDS Way.


sys/linux: use GICD/GICR register offsets in SYZOS_API_MEMWRITE

In addition to random offsets passed to SYZOS_API_MEMWRITE, use VGICv3 distributor/redistributor base and offsets of the corresponding registers.

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

@dvyukov PTAL


Extension complains about project.json files in node_modules

Environment data
dotnet --info output:
.NET Command Line Tools (2.1.4)

Product Information:
 Version:            2.1.4
 Commit SHA-1 hash:  5e8add2190

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16299
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.4\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

VS Code version: 1.19.3
C# Extension version: 1.13.1
Steps to reproduce

Use Yarn or npm to install the edge or edge-js package
Open the root folder (i.e. the folder containing node_modules) in VS Code

Expected  behavior

No warnings

Actual behavior

Warnings about project.json and requests to restore dependencies

Related to agracio/edge-js#20

Thanks for reporting! OmniSharp should just leave node_modules out when searching for projects.


Bot to present the consent form

Resolves #18
This adds a new field on the ConsentForm table that allows experiment admins to tell users to respond with "1" in order to give consent.

On the Experiment create/edit form there's also a new field:

We don't allow experiemts to be created/updated when this is enabled and the seed message is missing, since the bot needs to respond with a seed message when the user gave consent.

I'll merge this on Monday when I'm back. Don't want to accidentally let this go into prod and causing issues that someone else has to fix


Failed to install addin 'Cake.Powershell'

I was using Cake.Powershell version 0.3.5 with Cake 0.19.5, now when using 0.4.0 with same Cake version I get this error:
Could not find any assemblies compatible with .NETFramework,Version=v4.5.
Error: Failed to install addin 'Cake.Powershell'.

Unless configured, the Cake preprocessor will always download the latest version of any #addin or #tool.
With packages updating to support Cake 0.22.0
A workaround for now is pin the version of the tools e.g. #addin "nuget:?package=Cake.Powershell&version=0.3.5"
To avoid random breakages for your build script, I would recommend pinning the version of all dependencies.

Thanks @dennisroche 👍
I've added a description to the ReadMe and to the Troubleshooting page to explain Cakes changes.
I'm also going to leave this issue open for a couple of weeks as I've closed 3 identical issues in the last day and I suspect there will be more to come 😢

Thanks @dennisroche ! And also thanks @SharpeRAD for leaving this issue open making it easier for me to find it :)

Closing this now as I think its been long enough that people should be aware of the changes to Cake.


Is it possible to specify video chunk size when recording ?

The use case for this would start recording a stream and instead of saving a large video save small chunks of the video, specified by time e.g. 3s,5s, etc

Hello,
No, currently record video only support one single file.
I think that one way to solve this for your case is use a library to do it after finish record the video. Maybe you can do it with a wrapper of ffmpeg

You can create timer and just stop and record again.

You can create timer and just stop and record again.

It is an option if lose frames while you start again is not important

I explored the option but the chunk size i am looking for (3 to 6s ) is very frequent which would cause multiple frame loss

If we could save the video files in small chunks, without losing frames or audio, we could upload them to a server to use directly for HLS. Then I would no longer need to have an RTSP server or RTMP server to make the video available through a browser. I think that would be really nice.

I solved the problem by modifying the library to use 2 media muxer instances, This allowed me to stop and release 1 muxer while the other records and achieve 2-second chunks,but there were still some issues with MPEG writer so in the end had to move to a different solution.


Issue command bug fixes

The ability to send commands to chaosbot via issue comments is now available. However there were a few major bugs with the first version.
This PR..

[x] Runs commands from oldest to newest
[x] Has slightly more error handling
[x] Better validation of commands. /vote for :beers: will no longer be run.
[x] Stop overwriting command comment. Bot would overwrite comment with command saying "Command has been run". This now updates on the bot status reply instead.
[x]  Don't show negative time remaining

I'll approve after lints are fixed.

/vote for :beers: will no longer be run.

😭

Nice job at @rudehn :beers:
Much needed improvements!

@PlasmaPower Meritocracy?

@rudehn The title of this PR is inaccurate. This is unacceptable. Remove [Needs Review] this instant!!! :rage:

🎉 That did work!


feat(Pagination): remove is prefix in props

Closes #3492
Description
Removing all is prefix from is*
Is this a breaking change (Yes/No):
No

No changeset.

I determined that it was unnecessary because there were no changesets in the already merged PRs. @108yen

https://github.com/yamada-ui/yamada-ui/pull/3418
https://github.com/yamada-ui/yamada-ui/pull/3420

@kaehehehe
The change will not be published without changeset.

@kaehehehe The change will not be published without changeset.

This PR was approved even though it doesn't have a changeset. Why is it that only my PR requires a changeset?

@kaehehehe
I think the previous PR is wrong.


H36M_HRNET_2D_EDGES show wrong results?

H36M_HRNET_2D_EDGES https://github.com/cure-lab/SmoothNet/blob/3eb7a85534da868e54ff866622ff4c7976733fa9/lib/visualize/visualize_skeleton.py#L796
should be [5, 6, 0],please check again

Hi @codylcs ! Thank you for pointing out the typo error. We have already revised it to [5,6,0].


Add generic sorting (ORDER BY) on non-clustering columns using SAI

High Level Design
Add support for ORDER BY via SAI. The PR essentially makes the ANN vector ordering logic more generic by adding a few abstractions. This PR adds support for ordering all existing BA and CA indexes without writing any new index files. AA indexes cannot be sorted because the primary key map is based on partitions, not primary keys.
New Abstractions

PrimaryKeyWithSortKey - this is a primary key that has some metadata that can be used for sorting. The two implementations at the moment are a float used for vector similarity score and a ByteComparable object used from numeric and text indexes.
RowWithSourceTable and CellWithSourceTable - this abstraction gives us a way to validate the source of a given cell. That source is then used to confirm whether an index's ranking of the data is valid.

Notable design details

ORDER BY on SAI requires CL=1.
Updates on same memtable: unlike the VectorMemtableIndex, the TrieMemoryIndex does not override MemtableIndex#update. Instead, an update is handled as an insertion. That presents two problems. First, the memtable has both values, and second, the resulting sstable index has both values. This PR addresses that edge case by comparing the index's view of the value to memtable/sstable's live view of the value for the row. If implement MemtableIndex#update, we can remove the PrimaryKeyWithSortKey#isIndexDataEqualToLiveData guard.
The RowWithSourceTable and CellWithSourceTable are used by vector ordering to prevent re-calculating the score in the TopKProcessor. Once we solve the update problem for numeric and text indexes, we will do the same for those indexes.
In order for the "source table" logic to work, we must acquire a single view of the sstables and memtables and their associated indexes. Otherwise, we risk classifying a valid row as "updated". In the StorageAttachedIndexSearcher, we get this view and hold it for the duration of the query. Because hyrbid queries do not need to have the source table validated, they are not included in the view logic, which simplifies determining which indexes need to be locked.
Hybrid queries are only weakly index based. Because we do not have an easy way to map from PrimaryKey to value in our numeric and text indexes, the quickest solution to implement was to read the value from the sstable and then sort in the index.
@pkolaczk updated the cost based query planner for kd tree and trie based ordering. They might need tweaking in subsequent testing.

Unsupported data types
Currently, there are 3 types that are not sortable via SAI:

InetAddressType because we need to add decoding logic based on SAI's TypeUtil.encode method, and because SAI sorts InetAddress objects differently that Cassandra's InetAddressType comparator sorts them
DecimalType because SAI truncates the value to 24 bytes
IntegerType because SAI truncates to 20 bytes

The first one could be fixed based in the current paradigm, and the last two will likely require a change to the index format. Technically, we could optionally pull out all of the values that have more than 20 or 24 bytes, but I think that isn't worth the effort.
Dependencies
The following PRs originally had the following dependencies merged to vsearch and then into this branch:

#1090
#1079 (aka #1100)

Update: order by on date types does work. I missed the nuance that the byte comparable representation sorts on unsigned ints, so centering on 0 is only for signed integers. By updating the DateDataSet's comparator, the order by assertions pass tests now.

cqlsh:test> select * from test order by a;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Use of ANN OF in an ORDER BY clause requires a LIMIT that is not greater than 1000. LIMIT was NO LIMIT"

The error message needs to be updated, because there is no ANN OF now.

I squashed it and rebased: #1150

@eolivelli @pkolaczk - I think this PR is very close (I know we want it merged as soon as possible), but I reviewed some of the TODOs left in the code, and I think it might be worth either another pass before merging or shortly after merging. All of the tests are passing, which is a great sign, but the TODOs are some open questions I had when writing the PR and I still don't seem to have answers yet.

I found a bug:
ERROR [ReadStage-1] 2024-07-26 16:37:15,253 AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread Thread[ReadStage-1,5,main]
java.lang.NullPointerException: null
	at org.apache.cassandra.utils.bytecomparable.ByteComparable.compare(ByteComparable.java:138)
	at org.apache.cassandra.index.sai.utils.PrimaryKeyWithByteComparable.compareTo(PrimaryKeyWithByteComparable.java:66)
	at org.apache.cassandra.index.sai.utils.PrimaryKeyWithByteComparable.compareTo(PrimaryKeyWithByteComparable.java:33)
	at java.base/java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
	at java.base/java.util.PriorityQueue.siftUpUsingComparator(PriorityQueue.java:675)
	at java.base/java.util.PriorityQueue.siftUp(PriorityQueue.java:652)
	at java.base/java.util.PriorityQueue.offer(PriorityQueue.java:345)
	at java.base/java.util.PriorityQueue.add(PriorityQueue.java:326)
	at org.apache.cassandra.index.sai.utils.MergePrimaryWithSortKeyIterator.computeNext(MergePrimaryWithSortKeyIterator.java:76)
	at org.apache.cassandra.index.sai.utils.MergePrimaryWithSortKeyIterator.computeNext(MergePrimaryWithSortKeyIterator.java:38)
	at org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
	at com.google.common.collect.Iterators$PeekingImpl.hasNext(Iterators.java:1126)
	at org.apache.cassandra.index.sai.utils.MergePrimaryWithSortKeyIterator.computeNext(MergePrimaryWithSortKeyIterator.java:75)
	at org.apache.cassandra.index.sai.utils.MergePrimaryWithSortKeyIterator.computeNext(MergePrimaryWithSortKeyIterator.java:38)
	at org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
	at org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ScoreOrderedResultRetriever.nextSelectedKeyInRange(StorageAttachedIndexSearcher.java:536)
	at org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ScoreOrderedResultRetriever.nextRowIterator(StorageAttachedIndexSearcher.java:504)
	at org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ScoreOrderedResultRetriever.computeNext(StorageAttachedIndexSearcher.java:486)
	at org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ScoreOrderedResultRetriever.computeNext(StorageAttachedIndexSearcher.java:447)
	at org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
	at org.apache.cassandra.index.sai.plan.TopKProcessor.filterInternal(TopKProcessor.java:222)
	at org.apache.cassandra.index.sai.plan.TopKProcessor.filter(TopKProcessor.java:157)
	at org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:139)
	at org.apache.cassandra.db.ReadCommand.searchStorage(ReadCommand.java:512)
	at org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:410)
	at org.apache.cassandra.db.ReadCommandVerbHandler.doVerb(ReadCommandVerbHandler.java:58)
	at org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:79)
	at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:98)
	at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:46)
	at org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:436)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:165)
	at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:137)
	at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:829)

Reproduction
Load data with latte order.rn workload mentioned here (https://docs.google.com/document/d/11qqu9D1DM8kYTFP3aFhaxFkd4zRnBI6Yh-QPrlnBzfw/edit?usp=sharing)
Do not flush after loading.
Issue the query:
SELECT * FROM orderby WHERE a >= 0.1 AND a < 0.2 ORDER BY a LIMIT 10

@pkolaczk - nice catch. I introduced that bug while resolving merge conflicts.

Retested it and now it works fine.

This is overall great new feature!
I'm conditionally approving this, provided the following issues are fixed:
* `SELECT * FROM tab WHERE a > const ORDER BY a` queries currently don't work because of huge performance cost; neither for on-disk or in-memory indexes. Either let's fix it or at least disable it?

* Don't forget to merge the PR for lazy memory index range scans as that PR solves the first performance issues I mentioned in the doc.

Merging this PR with the understanding that we will follow up with individual PRs to address these issues.


Scroll To / Anchor scroll

Hi,
First of all, great project, thank you!
If I want to add anchorScroll or scrollTo functionality to the vs-repeat structure,
what will be the best way to do it?
What do you recommend?
Thank you

This is a great project indeed!
I was trying to set scroll thumb manually to a specific position using .scrollTop, but without success.

I think I found way: if you know approx position in pixels, then
$timer(() => {     containerElement.animate({ scrollTop: pos }, 0); })
will do the trick. Make sure that there is no latch option set to true in vs-options.

@varvarvar Where would you put that code statement?

@Shaggy13spe , I would put it there in code where I can calculate position which I wanted to set a scroll bar at.

See https://github.com/kamilkp/angular-vs-repeat/issues/144


CSS Floating Labels are broken

This doesn't work: http://docs.appgyver.com/supersonic/guides/ui/components/#forms-floating-labels

:+1:


fix(fcm): Add MessagingDeviceGroupResponse as sendToDevice return type

While working on refactoring FCM I realized that there is a slight discrepancy between sendToDevice's source and typing file with respect to the return type. Not sure if this is the best approach to address it.
Source
https://github.com/firebase/firebase-admin-node/blob/f3d9da5d727e84c9c8dcf0e9484608e0c2b615c4/src/messaging/messaging.ts#L378-L382
Typing
https://github.com/firebase/firebase-admin-node/blob/f3d9da5d727e84c9c8dcf0e9484608e0c2b615c4/src/messaging.d.ts#L1228-L1232
I figured that since there is a reason for having the MessagingDeviceGroupResponse return type, as mentioned below, that the typings might require a change.
https://github.com/firebase/firebase-admin-node/blob/f3d9da5d727e84c9c8dcf0e9484608e0c2b615c4/src/messaging/messaging.ts#L412-L421
Feedback appreciated!

Actually this is a breaking change as can be noted by the integration tests failing; it might be better to hold off on changes there until a major update. Similar differences also exist for sendToDeviceGroup.

Closing this for now because I do not see any immediate action


Sample on Falling Edge?

The datasheet states that the data change on the falling edge of the SCK, but the logic analyzer suggests doing otherwise.

The original code, which sampled on the falling edge, throws away the least-significant bit when sampling on the rising edge--even with PIO synchronizers disabled on the SPI POCI pin. Sampling on the falling edge fixes this issue.

Fixed in: https://github.com/AllenNeuralDynamics/rp2040.pio-ads7049/commit/56bdb0a5b9c2a4941439181e97c78a5d7a6c1fe3


champion cards with curated content rather than from a feed

Allow champion cards to accept curated content.
Test URLs:

Before: https://main--theplayers--hlxsites.hlx.live/past-champions
After: https://champion-cards-curated--theplayers--hlxsites.hlx.live/past-champions
After: https://champion-cards-curated--theplayers--hlxsites.hlx.page/drafts/fkakatie/sentry-past-champions
After: https://champion-cards-curated--theplayers--hlxsites.hlx.page/drafts/fkakatie/wgc-past-champions

and... the more i think about it, the "champions" variant/type isn't doing anything except making the card feed two columns instead of three. it originated as "champions" because that is currently the only place it appears, but would it make more sense then to change it from champions to "two-col" or "col-2"?

Think this is good now. Players version had one issue with the wrapper missing for the bubble when the data came form the feed, but was an easy fix. Also adjusted to use two-cols rather than champions per your comment.
Maybe take one more look when you get a chance, but otherwise think this is good to merge.


Explore race conditions with multiple trackers installed on page

We have at least two users that experience same problem with trackers installed by 3rd side.

In both cases 3rd side is http://keywee.co.
It looks like a race condition and therefore not easily reproducible

Although it looks impossible in current version of tracker, we may want to explore version installed by keywee (2.4.3?)
More info: http://discourse.snowplowanalytics.com/t/strange-js-error-with-javascript-tracker-with-multiple-sp-js-load/1080

If the problem is in 2.4.3, then won't this be difficult for us to tackle in a new release from us?

It would, indeed. But we also need to discover a problem to make sure this is in 2.4 and there's still may be a chance we can protect newer trackers.

Makes sense, thanks!

One possible culprit in pre-2.6.0 could be this https://github.com/snowplow/snowplow-javascript-tracker/commit/1e59f802aa065c7ae014394b2684d4fd11b42033. But it cannot explain why this happens when different namespaces are used.

If page has two script tags (user's with 2.7.0 and keywee's with 2.4.3), both attaching scripts with sp.js and pushing namespaces (user_snowplow and keywee_snowplow) to GlobalSnowplowNamespace, is it possible for keywee's 2.4.3 to be loaded first and pop user_snowplow namespace?
If that is possible it can explain absence of trackSelfDescribingEvent in discourse thread above, but cannot explain keywee's tracker sending events to user's collector.

@dmpacheco came up with a way to make this bug appear, from his email:

While doing the QA 2.8.0 RC I have come across a strange behavior with the Javascript tracker.
Having two different versions of the javascript tracker and one tracker instance referencing only one of them can cause the browser to randomly load either version.
We have created a simple html document to demonstrate our set-up. (attached to the email).
In the file, we included version 2.7.2 and 2.8.0 and called them T272 and T280 respectively.  We created a tracker instance that would only load T272.
When testing in Chrome with disable cache both version of the tracker could be loaded when reloading the page multiple times as seen below.

Analytics_test_JS.html.txt

Bringing forwards...

Seems that some users are able to resolve this by updating keywee, so likely problem does not manifest itself with newer trackers.


insert a struct without using params

I have a struct that contains lot of params so this example to insert wouldn't be lot of repetation.
 conn.execute(
        "INSERT INTO person (name, time_created, data)
                  VALUES (?1, ?2, ?3)",
        params![me.name, me.time_created, me.data],
    )?;

Is there a way to do something like this?
struct ObjectWithLotOfParams {
    param1: String;
    param2: u8;
    .....
    param50: String
}

let obj = ObjectwithLotOfParams {....};
conn.insert_into("table1", &obj);

No, you're looking something more ORM-shaped like https://github.com/diesel-rs/diesel, which can do these sorts of things for you.

thanks. closing for now.


Device type interfaces

Change all the built in devices to interfaces and provide the Arke Industries implementations in another assembly.

Done


Document cleanCache in README

The cleanCache command should be documented in README, see https://github.com/serverless/serverless-python-requirements/issues/437#issuecomment-1155659925
This doesn't fix issue #437 -- but it makes the workaround more visible.
Move commands from inline code markdown to code blocks to make them more visible.

(I think there's a bug where the python version should be included in the hash in the cache, but I'm not familiar enough with the caching mechanism to be sure.)

@dschep  are you still a good person to ask for PR review? #165 added the cleanCache command but it's not listed in the README documentation yet.

Nope. From the commit history it looks like you want @pgrzesik

Thanks @dschep for the ping, I'm trying to keep the lights on whenever I have a little bit of free time, which is not easy lately 😅


"Event Details" page

[ ] Event details

[ ] If accessed by owner: Button to register to event.
[ ] If accessed by everyone else: Edit button to go to an event edit page (We should be able to reuse the "Create Event" page for this.

~We must differentiate between public and private events.~
Update: we decided that all events should be public.


feat/allowing multiple tags for operation meta

Closes #82
Old PR: #83

Sure thing, made the change and currently, a test is failing. Will try and fix it and commit it.
Will tag after.

@jlalmes Houston we have a problem. Things get weird with the nullish coalescing operator.

To escape the ternary tree, will have to introduce if statements as a utility or something to that effect to resolve the Tags.

This seems to work 👉 tags ?? (tag ? [tag] : undefined)

@jlalmes we originally had tags: string[] instead of tag: string, right?
Just wondering what was the reason to remove it and now reverting it.

@dodas It was me seeking a "better" DX, because it's very rare that I ever add more than one tag to an endpoint. I suppose having both is a good solution for the time-being.

@jlalmes Squash and Merge? or is there a release pipeline/strategy for this?

@SeanCassiere squash please! I will manually release after you've merged 👍

Release under<EMAIL_ADDRESS>thanks for your hard work @SeanCassiere 🚀

Thanks a bunch for all your help. Was my second contribution to OSS and y'all made it great.


No error returned if I put invalid info after 'rio stack/volume/config' commands

Steps:

rio stack garbage

Results:  returns info for rio stack.  should return some sort of error or help for rio stack

No longer valid


etcdmain: only get initial cluster setting if the member is not initi…

fix https://github.com/coreos/etcd/issues/5444
@raoofm can you give this a try?

@xiang90 lgtm
backporting to v2?

@raoofm Is there a reason that prevents you from upgrading to etcd 3.0? We will probably keep back-porting bug fixes to 2.3 branch until 3.0 is stable. But once we feel 3.0 is stable, we wont back port any.

@heyitsanthony rebased. ptal.

lgtm

Is there a reason that prevents you from upgrading to etcd 3.0?

@xiang90 Nope, just waiting for v3 to stabilize as we are running in prod. Need to evaluate and plan the migration which seems a lot as a number of clients (java based) needs to be changed to support v3.
Oh wait, so as I read the v2-migration guide, I think there is no need to migrate the clients unless I want the clients to use v3 features. So even after upgrading, both v2 and v3 should be available and the clients should work as is. Right?
So upgrade of clients (read only) is not directly linked to upgrade of etcd from v2 to v3, and the write ones might need some planning (with/without downtime and migration mode) Right?

So even after upgrading, both v2 and v3 should be available and the clients should work as is. Right?

Yes

So upgrade of clients (read only) is not directly linked to upgrade of etcd from v2 to v3, and the write ones might need some planning (with/without downtime and migration mode) Right?

You can still write to v2 after migration.

:clap: great, thanks much @xiang90


[Storage] Download Tokens does not support lowercase object metadata

Forwarding an issue from nodejs-storage: https://github.com/googleapis/nodejs-storage/issues/1341
from: @leoalopes:
Basically, what I'm trying to do is to have my server send a signed URL to the client and have the client upload the file and generate a Firebase download URL that gives public access to the upload file. The problem is that I cant send my download token as metadata to uploaded file, because it has to be camel case. I read somewhere in the docs that I could send the metadata as a JSON file too, but I couldn't make it work (it didn't gave me an error, just didn't set the metadata).
Environment details

OS: Ubuntu 20.04
Node.js version: v12.16.3
npm version: 6.14.4
@google-cloud/storage version: 5.5.0

Steps to reproduce

Generate a signed URL with the code below

const [url] = await storage.bucket(bucket_name).file(file).getSignedUrl({
    version: 'v4',
    action: 'resumable',
    expires: Date.now() + 24 * 60 * 60 * 1000,
    extensionHeaders: {
        'x-goog-meta-firebaseStorageDownloadTokens': 'a883673-4957-4120-8f52-f383ddddbfb1',
    }
})

Upload a file using this signed URL and sending the x-goog-meta-firebaseStorageDownloadTokens. My code looks something like this:

const chunkSize = 1024 * 1024

async uploadFile(file) {
    let sessionUri = await axios.post(signedUrl, null, {
        headers: {
            'x-goog-resumable': 'start',
            'x-goog-meta-firebaseStorageDownloadTokens': 'a883673-4957-4120-8f52-f383ddddbfb1',
            'content-type': 'image/jpeg'
        }
    }).then(response => {
        return response.headers.location
    })

    const slice = file.mozSlice ? file.mozSlice :
        file.webkitSlice ? file.webkitSlice :
        file.slice ? file.slice : () => {}

    let chunkStart = 0
    while(chunkStart < file.size) {
        let chunkEnd = chunkStart + chunkSize
        if (chunkEnd > file.size) {
            chunkEnd = file.size
        }

        let currentChunk = slice.bind(file)(chunkStart, chunkEnd)
        console.log(chunkStart, chunkEnd, currentChunk)

        await new Promise((resolve, reject) => {
            axios.put(sessionUri, currentChunk, {
                headers: {
                    'Content-Type': file.type,
                    'Content-Lenght': chunkSize,
                    'Content-Range': `bytes ${chunkStart}-${chunkEnd - 1}/${file.size}`
                }
            }).then(response => {
                console.log('[RESPONSE]', response)
                resolve()
            }).catch(error => {
                // RESPONSE WITH 308 ARE TREATED LIKE ERRORS BY AXIOS
                console.log('[ERROR]', error)
                resolve()
            })
        })

        chunkStart = chunkEnd
    }

    console.log('FILE UPLOADED')
}

So, the problem is that, the metadata firebaseStorageDownloadTokens, sent on the headers, become all lower case, which I understand is the way it is supposed to work, but that makes me unable to upload a file and retrieve a firebase download URL, because the file doesn't contain any firebase download token.
This is how it is:

And this is how I need it:

For firebase to read that as an access token it needs to be camel case and I don't know how I could accomplish that without asking for my server to change the metadata after the client uploads a file using the generated signed URL.

I don't know much about the Storage SDK that is used by Firebase Admin. Assigning to the Admin team for triage.

Good find, per https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata#settable-fields;-field-values the keys should be case insensitive, let me file an internal bug

Thanks for raising this. Just pushed a fix to our server code that should start rolling out next week.

Closing this based on the last comment. Please comment here if the issue still exists.


The code compiles, gives me all the right outputs for the given inputs, but the website doesn't register any of them as valid,

Challenge  Bonfire: Steamroller  http://www.freecodecamp.com/challenges/bonfire-steamroller?solution=var B     %3B FUNCTION steamroller arr  { FUNCTION steamrolle array  { %2F%2F I m a steamroller%2C baby %2F%2Fvar A     %3B %2F%2F return %3B if Array.isArray array   { for var i   0%3B i   array.length%3Bi%2B  { steamrolle array i  %3B } } else B.push array %3B } steamrolle arr %3B return B%3B } steamroller  1%2C {}%2C  3%2C   4     %3B   has an issue. User Agent is%3A code>Mozilla%2F5.0  Windows NT 10.0%3B WOW64%3B rv%3A41.0  Gecko%2F20100101 Firefox%2F41.0 %2Fcode>. Please describe how to reproduce this issue%2C and include links to screenshots if possible. My code%3A    javascript var B =   %3B FUNCTION steamroller arr  { FUNCTION steamrolle array  { %2F%2F I m a steamroller%2C baby %2F%2Fvar A =   %3B %2F%2F return %3B if Array.isArray array   { for var i = 0%3B i   array.length%3Bi+  { steamrolle array i  %3B } } else B.push array %3B } steamrolle arr %3B return B%3B } steamroller  1%2C {}%2C  3%2C   4     %3B

The link included with your bug has very broken code. Please copy and paste the code you are trying to run that you think should work.

Closing as not an issue with FCC.
Thanks and happy coding!


Mention of name with space character (with two or more words)

what happens
When I try to tag a name that has two or more words (i.e. has at least one space character in name), Coracle name auto-suggest exits.

Known issue, but yeah, worth fixing.

Known issue, but yeah, worth fixing.

Apologize if duplicate - could not find in the issues list

Apologize if duplicate - could not find in the issues list

Nope, helpful to have it cataloged

I believe this issue has been fixed and can be closed. When I try and tag the person mentioned about now:

It shows up fine in the suggestions and can be clicked to tag that person.

Of course, the search string breaks when you add a space, but I think this makes since. Also, this is the same behavior I get when I use Amethyst.

Agreed, and nostr-editor has the ability to potentially change this behavior.


Reduce the retained memory when defining the relation readers

Fixes: https://github.com/rom-rb/rom/issues/694

@DangerDawson seems like repository specs are now failing :/ looks like "Optimise the repository relations reader" is the culprit.

It looks as though it is something to do with the way I am caching the build_relation_readers in the class attribute.
I will try and carve sometime out over the weekend to understand what is going on, bit it feels like state leaking between the specs as the specs that fail pass when they are ran individually

On 2 Aug 2024, at 15:21, Peter Solnica @.***> wrote:
@DangerDawson https://github.com/DangerDawson seems like repository specs are now failing :/ looks like "Optimise the repository relations reader" is the culprit.
—
Reply to this email directly, view it on GitHub https://github.com/rom-rb/rom/pull/695#issuecomment-2265503513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAARNDCV2NZNIY2BGUKHUPTZPOIU7AVCNFSM6AAAAABLF6C6LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGUYDGNJRGM.
You are receiving this because you were mentioned.

Yeah that's what I suspected. We can have an after callback that clears the cache in RSpec.

This is probably not the most elegant way, maybe using dry configurable and having a callback reset the class attributes back to their defaults would be nicer. But I wanted provide a fix ASAP in order to get the branch green again:
https://github.com/rom-rb/rom/pull/696


Contact Delete returns false?

So the Contact delete works great now but why is it that it returns false on success, shouldn't it return true?

Could be a brain fart. Will check logic Monday.  Thanks for confirming.

I get lots if those ;-)
On Sat, Aug 13, 2022, 4:10 PM Bruce Wells @.***> wrote:

Could be a brain fart. Will check logic Monday. Thanks for confirming.
—
Reply to this email directly, view it on GitHub
https://github.com/phpfui/ConstantContact/issues/11#issuecomment-1214244113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGE33VYZOBGQ335TUJJXK4TVZATN5ANCNFSM56OY4A2Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Turns out Constant Contact returns various 200 status codes for a successful delete. I was only checking for one.  Grab the latest version.  Should work now.


CB-14037 Change Light Duty Shape

In conjunction with Micro Duty, Light Duty is splitting it's services into 2 nodes, master and gateway for 7.2.12+.
Master contains Hbase, Kafka, HDFS, HMS, and Solr.  Gateway contains Atlas, Knox, Ranger, CM, and Zookeeper.
See detailed description in the commit message.

This is up for discussion and review.  I need to work with QA and the other suites of tests before committing this to make sure nothing breaks.

Can one of the admins verify this patch?

do we still need this?


Proactive Asset Dirtying

This PR determines all known dirty assets pro-actively. This is used to ensure that PlanManagers that are presented with offers first, does not accidentally schedule an asset that's actively being worked upon by another PlanManager that is presented offers later.

Addressed both comments!


Fix connection_pool.ex when connections takes too long

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: