Exposing Leader to upper layer

SM needs to return leader in both response of some API call as well as PGStat report.
This helps client(of SM)  to know up-to-date leader and send requests to leader.

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

Comparison is base (6abaabb) 72.56% compared to head (7bc6b84) 75.53%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
+ Coverage   72.56%   75.53%   +2.96%
==========================================
  Files          21       20       -1
  Lines         831      801      -30
  Branches       95       90       -5
==========================================
+ Hits          603      605       +2
+ Misses        168      135      -33
- Partials       60       61       +1

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


Dates should be "Jump to date" buttons

Users sometimes want to jump to an earlier date in their message view, and there is currently no easy way to do that.
As discussed on CZO, we should make clicking on a date in the message header bar or on the date separator line open a date selector. When the user chooses a date, their view should jump to the start of the selected date. The narrow should remain the same.
This is a significant project; please post on the CZO thread above if you are serious about picking it up and are looking for technical guidance.
Open questions:

Should the search bar be updated when a date is selected (e.g., with date:2022-12-14)? If so, we would want to implement this feature so that it can be accessed via the search bar as well (issue: #10385).

@zulipbot claim

@alya Is message header bar this one (Dec 15,2022 on screenshot)?

@alya Is message header bar this one (Dec 15,2022 on screenshot)?

Yes.

Is default date picker ok?

@lapaz17 I recommend raising such questions in the #frontend stream in the Zulip development community. Thanks!

@zulipbot claim

@lapaz17 We noticed that you have not made any updates to this issue or linked PRs for 10 days. Please comment here if you are still actively working on it. Otherwise, we'd appreciate a quick @zulipbot abandon comment so that someone else can claim this issue and continue from where you left off.
If we don't hear back, you will be automatically unassigned in 4 days. Thanks!

Still working on it.

@zulipbot claim

hello @alya I am new to open source contribution . is this good for beginner ??

No, note the "difficult" label.

ok , thanks @alya

@alya can you please some good first issue which is not claimed by other ?

@zulipbot claim

@zulipbot claim


React-Datepicker used inside Formik form and initialized to Date() returns timestamp on selection

Describe the bug
I have a Day-based React-Datepicker used inside a Formik form, which may or may not be relevant (I followed this small Formik wrapper). When the React-Datepicker is initialized to a form value that has a timestamp, such as new Date(), then any day selection returns the current timestamp. On the other hand, when it's initialized to something like NULL, any day selection returns 00:00:00. I need zero-time 00:00:00 returned in both of these cases.
To Reproduce
CodeSandBoxIO Demo:
https://codesandbox.io/s/proud-dust-gb25u
In this demo:

Datepicker 1 in Formik form initialized to new Date(). Note that any date selection includes the current timestamp in the value.
Datepicker 2 in Formik form initialized to NULL. Note that any date selection includes the 00:00:00 timestamp.

Expected behavior
Even if the DatePicker is initialized to a form value of new Date(), it should still return 00:00:00 on any Day selection. Regardless of how it is initialized, the value set by a day-based React-DatePicker such as in this example should always be 00:00:00 (no time, just the date).

This is strange indeed, it's not caused by Formik, I've modified your sandbox and added some datepickers that use state instead on formik and the same happens here also: https://codesandbox.io/s/affectionate-engelbart-sl61c


fix(sec): upgrade org.postgresql:postgresql to 42.4.1

What happened？
There are 1 security vulnerabilities found in org.postgresql:postgresql 42.2.14

CVE-2022-31197

What did I do？
Upgrade org.postgresql:postgresql from 42.2.14 to 42.4.1 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

[X] #1586


Need to specify particular params for mock call

When I have updated from 2.3 to 2.9 I found out that these constructions don't work anymore:
const testServiceMock = mock<TestService>(TestService);
when(testServiceMock.hello(anyString)).thenReturn('a')

const testService = new TestService();
testService.hello(); // mock won't work cause I specified that it should work only when 1 argument is passed
testService.bye(); // mock won't work cause i haven't specified it at all

Ability to use anything() for not provided parameters was great(and totally in js way), why did you took it away?(

It didn't go anywhere, I don't think:
https://github.com/NagRock/ts-mockito/blob/master/src/matcher/type/AnythingMatcher.ts
May have been since updated.

you didn't get me right)
matcher is still the same, the way number of method arguments is processed has changed, previously(in 2.3) if you write
when(testServiceMock.hello(anything())).thenReturn('a')
you got matched for method calls:
testService.hello();
testService.hello(123);

and since 2.9 only for
testService.hello(123);

Ah my bad. I'm unable to test this at the moment but I think
when(testServiceMock.hello).thenReturn('a')

may be a quick fix for now. Let me know if that works.

yes, i have already moved all our tests on this flow as soon as discovered it
but I think that possibility to use anything() as no parameter at all is very helpful and should be returned back)


Implement encoder and decoder

Fixes #2
Next: Hybrid signature support (#3)
Possibly review: interop testing (#32)
TWIMC: The failing interop tests will be OK as and when https://github.com/openssl/openssl/pull/16770 merges

@bhess NP if you don't have time to review. I'll merge anyway only when the upstream PR is through; as that is pending OTC review that may take some time. fyi, time permitting on my side I'll proceed with hybrid (sig) support (based on this branch as I already added quite a few hooks for that).

Sounds good to me @baentsch. At the moment I'm quite busy, but I was anyway interested to have a closer look at the OSSL3 encoders and the oqs-provider code. Hope to be able to do so in 1-2 weeks.


sh: next: not found

When trying to Deploy with $now i run in to following and i don't know how to solve it, logs don't give me any other information.

sh: next: not found
Synced 3 files (651.94kB) [10s]
Initializing…
Building
▲ npm install
✓ Using "package-lock.json"
⧗ Installing 42 main dependencies…
✓ Installed 1648 modules [2m]
▲ npm run build

<EMAIL_ADDRESS>build /home/nowuser/src
next build
sh: next: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

Package.json
{
  "name": "**",
  "version": "0.1.0",
  "description": "Web app",
  "author": "Mathias<EMAIL_ADDRESS>  "license": "ISC",
  "repository": "",
  "main": "index.js",
  "dependencies": {
    "axios": "^0.16.2",
    "babel-plugin-wrap-in-js": "^1.1.1",
    "body-parser": "^1.17.2",
    "cookie": "https://registry.npmjs.org/cookie/-/cookie-0.3.1.tgz",
    "dotenv": "^4.0.0",
    "express": "^4.15.4",
    "express-session": "^1.15.5",
    "firebase": "^4.2.0",
    "firebase-admin": "^5.1.0",
    "firebaseui": "^2.3.0",
    "isomorphic-unfetch": "^2.0.0",
    "js-cookie": "^2.1.4",
    "lusca": "^1.5.0",
    "next": "^3.0.3",
    "next-redux-wrapper": "^1.3.2",
    "node-sass": "^4.5.3",
    "nodemailer": "^4.0.1",
    "now-logs": "0.0.7",
    "orm": "^3.2.4",
    "raw-loader": "^0.5.1",
    "react": "^15.6.1",
    "react-dom": "^15.6.1",
    "react-jplayer": "^5.0.4",
    "react-redux": "^5.0.6",
    "redux": "^3.7.2",
    "redux-thunk": "^2.2.0",
    "sass-loader": "^6.0.6",
    "session-file-store": "^1.1.2",
    "sqlite3": "^3.1.9",
    "styled-jsx": "^1.0.10",
    "uuid": "^3.1.0",
    "webpack": "^2.5.1"
  },
  "devDependencies": {
    "babel-eslint": "^7.2.3",
    "eslint": "^4.4.1",
    "eslint-config-airbnb": "^15.1.0",
    "eslint-config-xo": "^0.18.2",
    "eslint-config-xo-react": "^0.13.0",
    "eslint-config-xo-space": "^0.16.0",
    "eslint-plugin-jsx-a11y": "5.1.1",
    "eslint-plugin-react": "^7.2.0",
    "sass-lint": "^1.10.2",
    "xo": "^0.18.2"
  },
  "scripts": {
    "dev": "node server.js",
    "build": "next build",
    "start": "NODE_ENV=production node server.js"
  },
  "engines": {
    "node": "8.x.x"
  }
}

try removing
"main": "index.js",

I am getting a similar problem but I do not have the main key. I imagine its something to do with the fact that we are both using node server.js file rather than running next therefore we need to change the build script but that is just a theory and I dont know how to do that

I found a solution, hopefully it works for you also:
your trace error has "Using "package-lock.json". is this file up to date? I use yarn so i deleted package-lock.json and now it works

I had the same error "sh: next: not found"
Had to update node from v6 to v8. Hope it helps!


[zh-cn] Updated service-topology.md

Signed-off-by: Gao Qian<EMAIL_ADDRESS>

/lgtm
/approve


Add metadata discovery & resolution paths to escrow contracts

Closes:  #112 cc: @bjartek
Related: #99

ℹ Cadence CI seems to be failing on CLI install because there was a recent release of Flow CLI which isn't yet available. I'll run CI again after some time to confirm passing tests.

Description

Enhances error messages in escrow contracts & scripts
Adds the ability to discover supported metadata views from NFTs in locked in escrow
Adds supporting scripts for new and existing escrow functionality

For contributor use:

[x] Targeted PR against main branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Would it be possible to have a method here to get do the two following things?
https://github.com/onflow/flow-nft/blob/0ce4125dcb5c351c64706edd5b210d1e22691ef5/contracts/NonFungibleToken.cdc#L123
and to get the views and resolve them for subnfts aswell?
Maybe that is another issue. Granted not very many people have subnfts that are bridge but it would still be nice to have if that ever happends.

Codecov Report
Attention: Patch coverage is 50.00000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 86.59%. Comparing base (f7c98ea) to head (05062f6).

Files with missing lines
Patch %
Lines

...adence/contracts/bridge/FlowEVMBridgeNFTEscrow.cdc
33.33%
4 Missing :warning:

...ence/contracts/bridge/FlowEVMBridgeTokenEscrow.cdc
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #113      +/-   ##
==========================================
+ Coverage   86.33%   86.59%   +0.26%
==========================================
  Files          17       17
  Lines         922      925       +3
==========================================
+ Hits          796      801       +5
+ Misses        126      124       -2

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

@bjartek updated based on recent convos (thanks for sharing!) and created #115 to add support for sub-NFTs

Merging in preparation for mainnet migration test today, but feel free to review and request changes after the fact @joshuahannan


Releasing model outputs

Hi Jialu,
Great paper!
I was wondering if you would consider sharing the model outputs (predicted paths) for RxR val-unseen and R2R val-unseen? This would be useful to dig into the performance in more detail. Sharing the outputs of your agent saves some time and avoids randomness compared to re-training the agent from scratch.
Cheers,
Peter

Hi Peter,
Thanks for your interest in EnvEdit! You can access the model outputs from this link. These outputs are from the models we use to submit to R2R and RxR leaderboard. Please let me know if you need pre-trained model/model outputs of other models.
Best,
Jialu

Thanks Jialu, this is super helpful!


(MAINT) Disable 'add_el_extras' for Beaker

Prior to this commit, we install and enable
an EPEL repo config during puppet acceptance
testing. However, we don't currently appear
to install any packages from EPEL during
testing.
To reduce potential occurrence of transient
failures in CI (due to issues with repo metadata,
etc), this commit sets 'add_el_extras' to
'false' so that Beaker doesn't set up the EPEL
repos on an SUT.

Closing this to retarget against stable.

CLA signed by all contributors.


tabletserver: fix shutdown race conditions

Fix race condition in ServiceManager.
Change rowcache invalidator to check shutdown state before
trying to restart binlog streamer.

LGTM


Dashboard Layout - Uncontrollable

Having issues with this media node; whenever i add it to a dashboard tab it completely messes up the dashboard layout. I've tried deleting all the spacers, then redoing the layout and deploying, doesnt resolve the issues. Remove the media node from an active tab and everything goes back to its right place.
Anyone else discovered this too?

Greetings,
Would you mind sharing your flow so we could reproduce your problem?
Thank you

Howdy, the flow is rather simple, purely trying to get 2 different images to display depending on what payload the node receives.
[{"id":"96eee48d.97d058","type":"ui_media","z":"8fd95987.d99e18","group":"","name":"Hi-Low Indicator FAN","width":4,"height":3,"order":53,"category":"FAN","file":"FanON.gif","layout":"adjust","showcontrols":true,"loop":true,"onstart":false,"scope":"local","tooltip":"","x":1063,"y":3470,"wires":[[]]},{"id":"808bb9e8.25a368","type":"change","z":"8fd95987.d99e18","name":"","rules":[{"t":"change","p":"payload","pt":"msg","from":"ON","fromt":"str","to":"FAN/FanON.gif","tot":"str"},{"t":"change","p":"payload","pt":"msg","from":"OFF","fromt":"str","to":"FAN/FanOFF.png","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":702.9999999999999,"y":3483.999999999999,"wires":[["96eee48d.97d058"]]}].

The media node just seems to not be bound to the 'layout', despite being able to specifically locate it wherever you'd like, when you deploy it just seems to go wherever it wants and also messes up the layout of all the other dashboard nodes. Remove media node from that tab and everything goes back how it was again.

Has anyone else discovered the same or similar issue?

Greetings
I'll take a look.
Thank you for your report.

Any update on this @steuck13 ?

Greetings,
Sorry, it's on my to-do list. I'll take a look at it when things calm down a bit.

This is due to #12.
Somewhere around https://github.com/netsmarttech/node-red-contrib-ui-media/blob/master/ui_media.js#L640
just add
    order: config.order,

Hi Dave, taking a look at it right now.
I'm traveling right now, as soon as I have a stable connection I'll publish a new version with this and other fixes

Hi,
Just published 1.2.0 that should solve this and the configuration panel issues as mentioned in #12. As a bonus, I've improved the help section, it should now reflect a bit better the accepted messages and their behavior.
Let me know if you have any other issue
(P.S.: I really hope that that warning about the order property not being set is not because solely of this node)

no - we look for it on any node so that is easy to report to developers. (It wasn't just you.. :-)


Empty bookmark subfolders should have an "(empty)" entry

When a bookmark folder is empty it should be clear to the user. Chrome shows a (empty) item in the folder popup in a muted colour. We should do the same.
On the old master release branch this was already implemented but after the big refactor it now needs to be implemented again.

Fixed in #1149


Stop Gradient When Screen is Off

The gradient should stop animating when the screen is off to save battery. Currently, the gradient animation continues with the screen off and drains battery.

With v0.0.5, it should stop the animation in onScreenStateChanged when screenState == SCREEN_STATE_OFF

Wow, thank you so much! This is an amazing library and SOOO beautiful :rose:
I must apologize for the tone in my issues reports. I made them as TODO items to remind me to fix those issues. I did not mean to be so abrupt!
This library is so wonderful. Thank you for sharing it!

Thanks 😉

You rock! The AnimatedGradientTextView no longer uses CPU when the screen is off. Amazing work!


Can it be installed on Ubuntu server 24.04 ?

Hello, how can it be installed on ubuntu server 24.04?

Next version can be installed on Ubuntu:
https://github.com/seydx/camera.ui/issues/448

hope it'll come soon :)


Set denexcep to 0 when in numer

To test, make a measure pass the logic in numer and denexcep and make sure the denexcep Actual result is set zero


Update azure-services-in-fedramp-auditscope.md

Hi Roger, please review the changes regarding Azure Commercial cert status. I am going to submit the Azure Government Changes in a separate request. thanks

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

@bernie-msft GitHub shows author as 'davib', but this alias is not showing in GH org (or GAL), so I cannot assign to this person for review. Also, article History shows your alias as contributor or author. Please advise, thank you.

Hey Chris. Essentially I authored the article but wanted to let compliance team own going forward. I recommend @Roger<EMAIL_ADDRESS>be listed as the author.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Chris Bain<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 11:46 AM
To: MicrosoftDocs/azure-docs
Cc: Bernarldo Ellis; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Update azure-services-in-fedramp-auditscope.md (#33552)
@bernie-msfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbernie-msft&data=02|01|Bernarldo.Ellis%40microsoft.com|d10c3cdbdeea40c55d5e08d6f4cd50a2|72f988bf86f141af91ab2d7cd011db47|1|0|636965559988242267&sdata=D2nFD3OdtCXeJNEgG5MIqiAnBoOiYoADpgLKpnQudhU%3D&reserved=0 GitHub shows author as 'davib', but this alias is not showing in GH org (or GAL), so I cannot assign to this person for review. Also, article History shows your alias as contributor or author. Please advise, thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F33552%3Femail_source%3Dnotifications%26email_token%3DAHR4BCQJ4T2KXB6KXWMIIWLP3JIF3A5CNFSM4HZETZDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCJPNY%23issuecomment-503617463&data=02|01|Bernarldo.Ellis%40microsoft.com|d10c3cdbdeea40c55d5e08d6f4cd50a2|72f988bf86f141af91ab2d7cd011db47|1|0|636965559988252265&sdata=UbrI5wxlg5BLaI7Su83F9fuqDrjlDYsO4%2B9CamkD6Rw%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHR4BCWFVBV5CQP2G4AX6NLP3JIF3ANCNFSM4HZETZDA&data=02|01|Bernarldo.Ellis%40microsoft.com|d10c3cdbdeea40c55d5e08d6f4cd50a2|72f988bf86f141af91ab2d7cd011db47|1|0|636965559988262265&sdata=Ngxj0nreDpjxCFDXkuX6PsnyNK2TZsV6OXS8AzIKdsw%3D&reserved=0.

@bernie-msft  Thanks. I'm unable to find Roger Chiou's GH alias as well, so I can't assign him as author. He will need to join Microsoft GitHub orgs: https://repos.opensource.microsoft.com/ and then review this PR.

Ok, can you make me the author for now?
From: Chris Bain<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 12:21 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Bernarldo Ellis<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update azure-services-in-fedramp-auditscope.md (#33552)
@bernie-msfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbernie-msft&data=02|01|Bernarldo.Ellis%40microsoft.com|bc5511550091465be25408d6f4d21240|72f988bf86f141af91ab2d7cd011db47|1|0|636965580427500383&sdata=hMVwb6J98EKtqinbaWXy1YIn5O6w4XaDnr9qE5kxuUs%3D&reserved=0 Thanks. I'm unable to find Roger Chiou's GH alias as well, so I can't assign him as author. He will need to join Microsoft GitHub orgs: https://repos.opensource.microsoft.com/https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepos.opensource.microsoft.com%2F&data=02|01|Bernarldo.Ellis%40microsoft.com|bc5511550091465be25408d6f4d21240|72f988bf86f141af91ab2d7cd011db47|1|0|636965580427510367&sdata=072Swqbp0os3HuyDS1mMGZXIc%2B2gGF%2FoBcq2OHZBKuo%3D&reserved=0 and then review this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F33552%3Femail_source%3Dnotifications%26email_token%3DAHR4BCTEPNMKMNCIZJZBIRLP3JMFPA5CNFSM4HZETZDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCMW6Y%23issuecomment-503630715&data=02|01|Bernarldo.Ellis%40microsoft.com|bc5511550091465be25408d6f4d21240|72f988bf86f141af91ab2d7cd011db47|1|0|636965580427510367&sdata=LMUvtCycGt0ghJlO9oaIyjqkln102JoZNnCd3A3i2ks%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHR4BCUOQBSUSN2AONKE22TP3JMFPANCNFSM4HZETZDA&data=02|01|Bernarldo.Ellis%40microsoft.com|bc5511550091465be25408d6f4d21240|72f988bf86f141af91ab2d7cd011db47|1|0|636965580427520363&sdata=pXNU%2Bll%2FL5ZkfotatvfejLj%2F1EJxeFy8z1ICPtLzdc8%3D&reserved=0.

@bernie-msft
With your #sign-off approval as the original author, I can merge this PR.
Note that the metadata author value must be a GitHub user name, and can only contain one name. We don’t assign or update metadata in articles. You, or someone in your team, will need to create a PR in the private repo to change the metadata author value.

@chbain
Thanks for the information and we'll work to get the author metadata updated.
#sign-off

@bernie-msft: I'm sorry - only the author of this article, @davib, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


[BUG] Semiautos have incorrect accuracy

Semiautos currently have 1.1 spread, when their acf2 default was  0.1.
For reference, HMGs are 1.3, and autocannons are 0.12. They are currently less useful than a shotgun.
Semiautos are meant to be limited magazine, high rate of fire, accurate weapons for lighter vehicles.

Addressed in b7c4fa5ebe4093235ae013f34e2abbec82efc61d


@prefresh/vite not working for non-root component

In the default vite template for preact, created with
npx create-vite-app preact-hmr --template preact, editing the default app.jsx works as expected and is reflected on the page instantly. Any new component created and used within app.jsx doesn't cause anything to change in the page when that new component is changed itself.
Posted in Vite. But thought maybe it might be directly related to this instead.
https://github.com/vitejs/vite/issues/388#issue-637305182

I just tested it in vite 0.16.2 and it seems to work, I'll explore their changelog to see what changed.

Thanks. I can confirm it works in vite 0.16.2 for me as well.

What version are you using for @prefresh/vite?

I was using vite 0.20.8 with @prefresh/vite 0.8.3 when I encountered the issue.

All right, I'll publish 0.9.0 tonight 👍

0.9.1 has been published and should fix the default exports and normal non-root one! Thanks for reporting this issue, also PR'ed the upgrade to the template.


async push notification receipts + library support (pipefy)

Hello!
I was reading the Expo SDK 29 release notes today and saw all the changes around Push Notifications, the node-sdk has been updated by the expo team, and they said this:

Is the Pipefy takeover old news or did it just happen? As far as I can tell no Pipefy members have contributed to this repository and no notes about them taking it over have been made. Will we be seeing push notification read receipt support added in the near future by the Pipefy team?
Our team might be able to contribute to this feature, but we don't want to duplicate effort with the Pipefy team.

Bump ?

Check out #29 @audiolion


How to generate bindings without running test?

https://github.com/Aleph-Alpha/ts-rs/blob/147e1522763596ad17508d62e57c1062c575948e/README.md?plain=1#L39
I know I can generate bindings with cargo test. But I want a way to only generate bindings without running tests.
Can you guide me to achieve this please?
Thank you.

Hey @yujong-lee,
you can omit the #[ts(export)] attribute, and call TS::export on your type yourself.
This is documented here

@NyxCode  Sorry that I ask you again that is already documented. Thanks for your response.


Fix codecov report

Currently, there are two codecov reports, one called codecov/patch and codecov/project. The first one is constantly failing, while the second one is passing.
This inconsistency should be fixed.

I am not sure it is really an inconsistency. Does not the first test (codecov/patch) check the percentage of tested lines only within the lines that have been modified while the second (codecov/project) checks the percentage of tested lines among all lines in the whole ppafm package? If so, they are really two different tests, which can be expected to give different results. Namely, if you make only a small change, the status of the codecov/project test is unlikely to change, if it passes before, it probably will after a small change too, if it did not pass before, it will probably keep failing (definitely so unless you added some new tests to cover the change and likely even if you did). So I don't think it is literally a bug to be fixed if codecov/patch fails while codecov/project passes, but applying the codecov/patch may be a too strict criterion at this stage. Should we deactivate it?

should be disabled now. Please reopen in case of problems


Update one-outlook.md

Added guidance for using the olk.exe --devtools command to open browser developer tools, given the absence of the right-click context menu and no support for CTRL+SHIFT+I and F12 to open it in the new Outlook.

Thank you for testing this and correcting our docs, @elegault! I made minor changes to comply with our style guide. I'll also be updating Develop Outlook add-ins for the new Outlook on Windows (preview) in a separate PR to include your guidance on the right-click context menu and keyboard shortcut for dev tools.

 I should have made the same change in the other article - I was thinking about it!

Thank you for testing this and correcting our docs, @elegault! I made minor changes to comply with our style guide. I'll also be updating Develop Outlook add-ins for the new Outlook on Windows (preview) in a separate PR to include your guidance on the right-click context menu and keyboard shortcut for dev tools.

 I should have made the same change in the other article - I was thinking about it!

No problem! We appreciate all your contributions to the Office Add-ins space.
Also, apologies for the GitHub spam. My suggested changes didn't render properly.


Date reason list rendering

Improve the rendering of the list date reason list by changing it to be rendered as a table so the text better align correctly, and the reason can not go in to the date section on small screens.

Sorry this was not part of any of your issues but got sidetracked when trying to look in to one of you issues.

Nice! I always get a bit carried away with flexbox, it's not always the answer lol :) thanks for the contribution!


Updated DE/ES/FR/PT/PT_BR translation strings

This pull request includes a

[ ] Bug fix
[ ] New feature
[x] Translation

The following changes were made

Updated translation strings for German, Spanish, French, Portuguese and Brazilian Portuguese

I don't see any reason to close this

@kevin-brown?


Linux support

Can you try to have Linux support?

I can try, but I'm quite busy lately so I might not get around to it. I'll let you know if I do.

I can try, but I'm quite busy lately so I might not get around to it. I'll let you know if I do.

Thanks!


Universal/Server/Node regression

It seems there's a regression in Universal/Server/Node support caused by isTablet() referencing navigator:
https://github.com/KoderLabs/ngx-device-detector/blob/0f453d29a93ec2d866cd7801db121e751134f0fd/src/device-detector.service.ts#L135-L136

@intellix the issue has been fixed in 1.3.17 and released. Please review and close the task if the issue is solved.

Hi @AhsanAyaz - after installation of 1.3.17, I have still an error.
Here is the stacktrace:
ERROR ReferenceError: navigator is not defined
at DeviceDetectorService.isTablet (/srv/functions/node_modules/ngx-device-detector/bundles/ngx-device-detector.umd.js:592:13)
at DeviceDetectorService.isMobile (/srv/functions/node_modules/ngx-device-detector/bundles/ngx-device-detector.umd.js:575:22)
Are you able to look at this issue again?
Row 592 of the ngx-device-detector.umd.js is:
if (navigator &&
!!this.reTree.test(this.userAgent, TABLETS_RE['iPad']) ||
(navigator.platform === 'MacIntel' && navigator.maxTouchPoints > 1)) {
return true;
}

Error still exist:
ERROR ReferenceError: navigator is not defined

@vucko , the issue has been fixed in 1.3.19
I've also added SSR to the demo to be sure. Tested as well. Please close the issue if it all seems good for you as well.

Thanks @AhsanAyaz - issue fixed for us with the release 1.3.19 !

Awesome. Closing the issue!


Question: Make generated relationship fields public?

Hello. I have a table Sales, which has a foreign key for Products table like so:
@Entity
@Table(name = "sales")
public abstract class AbstractSale {
    @Key
    public String sale_id;
    @ManyToOne
    public Product product;
    public int quantity;
    public float price;
}

Is there any way to generate a field int product_id in the corresponding class Sale which contains the key for the class Product, and if so how do I ensure that the generated field is public. We want to be able to serialize the model into json easily. Thanks in advance.

Any reason you can't declare the field yourself through something like this?
@ManyToOne
@ForeignKey(referencedColumn = "_id", references = Product.class)
@Column(name = "product_id", nullable = false)
public int productId;

Is there a way to have both the field public int product_id and public Product product? I've tried declaring both of them in my class but its throwing this error:
Error:(130, 55) error: variable PRODUCT_ID is already defined in class Test

Hi you should define either ProductId as an int key or a Produce reference as a @ManyToOne, you can't have both since it would lead to inconsistent state.
When you use
@ManyToOne
    public Product product;

the id is in the Product object itself so there is no need for a field and requery doesn't generate one in that case.


Support downloading the language server through proxy settings

Environment data

VS Code version: 1.26.0
Extension version (available under the Extensions sidebar): 2018.7.1
OS and version: windows 7
Python version (& distribution if applicable, e.g. Anaconda): 3.6.6 (miniconda)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: XXX

Actual behavior
Language server and linting does not work
Expected  behavior
Language server and linting should work
Steps to reproduce:
Behind company proxy (I believe this is causing the issue)
Logs
Starting Microsoft Python language server.
Downloading https://pvsc.blob.core.windows.net/python-language-server/Python-Language-Server-win-x<IP_ADDRESS>04.3.nupkg... failed.
Error: tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:d:\buildagent\workspace\318698\vendor\node\deps\openssl\openssl\ssl\s23_clnt.c:827:

Do you need a way to set proxy settings to make this work? I would assume we are already using the proxy settings of your OS so it's a question of whether being able to set more specific settings would have somehow alleviated this failure.

I would assume we are already using the proxy settings of your OS

Unfortunately no.
Solution: All we need to do is get the proxy from the config as follows:
proxy = workspace.getConfiguration('http').get('proxy', '');
And pass that into the request.
I missed this when reviewing the code, I've used this in the past in other extensions :(
Note, VSC have an issue that would automate this process for us.
Support downloading of additional resources when installing an extension

@brettcannon
Changed to P0 and added to current milestone, as this has the potential to affect a number of other users.
At a minimum it'll be P0 before we switch to the language server.
Please feel free to change the labels.

Yes, it's a P0 for September, but it's a P1 for August.

Flagging this as a good first issue since Don basically said what to do. 😁

I've picked up this task, and after reading into the issue a bit I see this information on the subject here:
https://code.visualstudio.com/docs/setup/network
Proxy support for extensions being what it is today, plus @DonJayamanne's suggestion above, means that we will support the proxy but not any further authentication. Instead, we will wait for VSCode support for downloading extra assets during extension installation via Microsoft/vscode#53855.


Keyboard Manager - Process-specific Key Remap

Description of the new feature / enhancement
Please carry the Remap a Shortcut feature's ability to select an individual process to override to Remap a Key.
Both of those Keyboard Manager customizations would only affect individual processes, instead of global enforcement.
Scenario when this would be used?
On my primary browser, I have 8 tabs which are frequently accessed and pinned. Each of these pinned tabs could then be accessed simply by pressing F1 through F12 keys — when these function keys are otherwise unused.
Ex:
I want to remap the chrome process to always use the F1 key to translate to Ctrl (Left) + 1.
This brings up a pinned/static ChatGPT tab that is always in the 1st tab position.
For those that desire this functionality, this remap could be used for any/all tabs.
This is usage case would only apply to static tabs, because users would remember function key correlations to their frequent tabs.
Quickly scrolling threw these tabs now becomes easier as users can simply pan through the function keys. Users can also utilize a browser extension or add-on that displays the tab numbers.
Supporting information
Previously using AutoHotkey for this exact solution, I'd rather use PowerToys' GUI over scripting

/dup #6756


Expose indentation suppressor from SmartIndenter

Separated from #4609.
shouldIndentChildNode function already have indentation suppressing feature, but currently auto-formatter disables it to get delta value and implements another suppressor in computeIndentation function.
This PR split the suppressor from shouldIndentChildNode and expose it as a separate function so that formatter can use it without implementing its own one.
The function will help suppress indentation of:

ImportClause node in ImportDeclaration node. (#4609)
JsxClosingElement node. (#4398)
false branch in ternary operator. (#5905 which already includes this PR)

Note: shouldInheritParentIndentation and its internal nodeWillIndentChild receives TextRangeWithKind to check more conditions other than syntax kind.

Ping @vladima

sorry for the delay. Can you add the @internal annotation in your next PR.


mobilePayload?

can you post an example of what the mobilePayload looks like? I have tried to get the mobilePayload using HTTPCatcher and have never seen it.

When the mobile app checks for a valid sesion or requests an MFA token the body (json) contains an element called 'mobilePayload'. The structure is in the format of a the other tokens used by Arlo. It's a pain to re-engineer outside of intercepting the https payloads because of Cloudflare so using Postman is not an option.


[0.62.0-rc.2] console.warn while enabling Logbox causes App crash in iOS

Description:
Using console.warn while having Logbox on with unstable_enableLogBox causes iOS to crash.
console.log, or console.error does not cause this problem.
It's working fine on Android.
React Native version:
Run `react-native info` in your terminal and copy the results here.

npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.2
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
    Memory: 75.79 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.13.1 - /var/folders/fd/m5mq98bs7k78g706wfysdngc0000gn/T/fnm-shell-2082864/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.12.1 - /var/folders/fd/m5mq98bs7k78g706wfysdngc0000gn/T/fnm-shell-2082864/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 26, 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.11.0 => 16.11.0
    react-native: 0.62.0-rc.2 => 0.62.0-rc.2

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Issues without reproduction steps or code are likely to stall.

npx react-native init RNTest --version 0.62.0-rc.2
add require('react-native').unstable_enableLogBox(); in index.js in root.
add console.warn('Test Warning') inside App.js` before return.
react-native ios

Expected Results

iOS to not crash

Snack, code example, screenshot, or link to a repository:
Repo with minimal code for repro:
https://github.com/Naturalclar/RNTest

Hey @Naturalclar, thanks for filing and for proving the repro repo.
The root cause here is that the FLEXNetworkObserver that Flipper DevTools use to inspect network requests does not work with the base64 encoded image data that LogBox uses for the close icon. If you disable the images in LogBox, there's no crash:

Here's the crash:

We're actually already switched these base64 images over to resource files on master, so we can cherry pick that to 0.62 to fix!

Cherry-picked to 0.62 and confirmed that this is fixed:


Version management around external parameters

As Artemis changes in scope to take more of the heavy lifting from the HCR it will be important to make sure that the correct versions of parameters are being sent to Artemis. As of https://github.com/DiamondLightSource/python-artemis/pull/522 we have a PARAMETER_VERSION number but:

This should ideally be automated so that changes in parameters will automatically change the version e.g. make it a hash of the schema
GDA needs to check this in some way

@DominicOram 18 months late but... sort of. Versioned plan parameters might be an idea, as might "interface definitions" or similar standardisation so you could plug any plan following interface X into a GUI say. This is the first concrete use case I've seen though, might be worth converting to a blueapi ticket?


(maint) Add Azure Pipelines container builds

Test FAILed

Test FAILed

Test PASSed

Test PASSed

CLA signed by all contributors.

Test FAILed

Test FAILed

Test FAILed

Test PASSed

Test PASSed

Test PASSed

Test PASSed

Test FAILed

Test PASSed

Test PASSed


Scenario Injection

  1 package bbc.weatherwatchers
  2
  3 import scala.concurrent.duration._
  4
  5 import io.gatling.core.Predef._
  6 import io.gatling.http.Predef._
  7 import io.github.clickscript.Predef._
  8
  9 object WeatherWatchers2 {
 10
 11   val httpProtocol = http
 12     .baseURL("http://www.stage.bbc.co.uk")
 13     .acceptEncodingHeader("gzip, deflate")
 14
 15   scenario("ViewReport")
 16     .exec(
 17       clickStep("Go To Homepage")
 18         .goTo("/weatherwatchers"))
 19
 20   setUp(ViewReport.inject(
 21     atOnceUsers(2)
 22   ).protocols(httpProtocol))
 23 }

Not sure, how I inject the scenario. I was thinking that the "ViewReport"(15) string would be converted to a value. But ViewReport (20) is not found.

I am now thinking, you'd run it something like this
class WeatherWatchers2 extends Simulation {

  val httpProtocol = http
    .baseURL("http://www.stage.bbc.co.uk")
    .acceptEncodingHeader("gzip, deflate")

  setUp(ViewReport.viewReport.inject(
    atOnceUsers(2)
  ).protocols(httpProtocol))

}

object ViewReport {

  val viewReport = scenario("ViewReport")
    .exec(
      clickStep("Go To Homepage")
        .goTo("/weatherwatchers"))

}

I think you're about right with the second version - the version in WeatherWatchers2 should work (although I haven't tested it). Under the hood, it's just a wrapper around Gatling's standard http capabilities, so you inject a Scenario in the same way.

Good man.


Do you support percentage loading progress ?

Hi Team,
I really like this simple and pretty template. Could you support percentage for the loading bar ?
I think it would be the best free template if have loading percentage progress.
Hope to hear from you soon ?
Thank you for your sharing.
Duc Hoang

It already has a percentage loading bar.

Hi Greggman,
I mean How can I get the loaded percentage and put the percentage text (60% or 70%) to the page ?
Thank you.


List All Product Categories returns image.src: false

API => GET:  products/categories?per_page=20
returns the below listed data which does not include category image src, refer attachment;
`image: {
alt: false,
name: "Hello world!",
src: false, ...
}

`

This library is now deprecated, you should try https://github.com/woocommerce/woocommerce-rest-api-js-lib


[VS Code] fix cluster explorer's right-click menu

Coverage increased (+0.01%) to 52.947% when pulling 78bb71fdb2684366f725b0d0febdae9336239f93 on qinsu/vscode/fix4 into f8e88efef81091fc895cc81a3e76aeb052226c15 on vscode-dev.

Coverage increased (+0.01%) to 52.947% when pulling 78bb71fdb2684366f725b0d0febdae9336239f93 on qinsu/vscode/fix4 into f8e88efef81091fc895cc81a3e76aeb052226c15 on vscode-dev.


Documention needed for 446 PCs – Lickport stage, High-speed videography

To setup 446 PCs, installation instruction wiki has to be updated to include:
1A. New lickport-stage Harp devices that are replacing Newscale stages.
@Poofjunior @bruno-f-cruz
1B. Is the foraging main branch already compatible with the new lickport-stage? I guess ForagingSetting.json is also getting obsolete?
@alexpiet @XX-Yin
2A.High-speed videography setup, including cable connections and Settings_boxN.csv config.
@ZhixiaoSu
2B. Is the foraging main branch already utilizing the AIND-FLIR node, with which we don't have to setup/hardcode camera settings using SpinView?
@alexpiet @XX-Yin @bruno-f-cruz
__
It would be great if you could update the wiki at your earliest convenience so we (@yonibrowning @hagikent ) can finish setting up 446 PCs, thanks!

Will do later today!
On Sat, May 4, 2024 at 16:04 Kenta M. Hagihara @.***>
wrote:

Assigned #425
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/425
to @ZhixiaoSu https://github.com/ZhixiaoSu.
—
Reply to this email directly, view it on GitHub
https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/425#event-12705435122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI4EJ7YRB6ILSMBK2M46P6TZAVSQHAVCNFSM6AAAAABHHFXPXCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSG4YDKNBTGUYTEMQ
.
You are receiving this because you were assigned.Message ID:
<AllenNeuralDynamics/dynamic-foraging-task/issue/425/issue_event/12705435122
@github.com>

Hey. No idea about the state of any of those points. I am happy to help if you need. Feel free to schedule a meeting to go over it.

To setup 446 PCs, installation instruction wiki has to be updated to include:

I've updated the information I know

1A. New lickport-stage Harp devices that are replacing Newscale stages. 1B. Is the foraging main branch already compatible with the new lickport-stage? I guess ForagingSetting.json is also getting obsolete?

The new lick spout stages are not yet compatible, but in progress.

2A.High-speed videography setup, including cable connections and Settings_boxN.csv config. 2B. Is the foraging main branch already utilizing the AIND-FLIR node, with which we don't have to setup/hardcode camera settings using SpinView?

The main branch is compatible with the high speed cameras. I have included the information I know in the wiki. @XX-Yin Can you (1) document how to find the COM ports for the AIND lick detectors? (2) Document how to find the serial number for the high speed cameras?

(1) I just unplugged and plugged in the Harp USB cable to find the COM port. One trick is that the COM port you just plugged in always appears at the end of the list (can be visualized from the behavior node in the bonsai; shown below).

(2) The serial number of the camera can be viewed from the SpinView software.

Thanks @XX-Yin Can you add that to the wiki instructions?

Thanks @XX-Yin Can you add that to the wiki instructions?

@alexpiet Updated

@hagikent How is the documentation going for 446? Is this issue resolved?

@alexpiet
I have no idea on Lickport stage, and documentation for it.
Documentation for High-speed videography was set up by @ZhixiaoSu and it worked for me. @yonibrowning had some troubles but it was utilized to update the doc; I think it's now good.

I will handle the lick port stage documentation when its ready


Fix yet more memory leaks from constructor exceptions

two more whack-a-moles

Good, errm, catch ;) The throw/rethrow pattern here kind of suggests that maybe the underlying pointers want to be smart pointers so they clean themselves up in the throw.


[Feature Templates] Fix Tenant Model jinja file

Pull Request summary:
Fixes tenant model and bump patch version.

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/380


Unknown Strat runner - Gekko doesn't know what strat runner this is...

Action Taken:
Start a new live Gekko
Expected Result:
A new live Gekko would start
Actual Result:
"Gekko doesn't know what strat runner this is..."
Setup:
Installed in Ubuntu (not in Docker)
Poloniex
USDT
BTC
Paper Trader (this all works for just Market Watch)
MACD
1 Hour
10 Hour history
Paper Trader:
`fee = 0.25
slippage = 0.05
riskFreeReturn = 2
[simulationBalance]
asset = 1
currency = 100`
Output looks normal:
'Gekko<PHONE_NUMBER>36416 started
--> POST /api/startGekko 200 3ms 542b'

@askmike That's in the report above.  If it helps, here's a little more info:
Gekko version: v0.4.10
Nodejs version: v8.1.3
I haven't found any other logs, but here's the console output from some of before, up to, and including the problem.
  Once we figure this out, I'll go back and do it all again and submit a PR if one is needed.

I stopped gekko and restarted it and then started a new paper trader gekko with no error or warning.

Strange, so the message "Gekko doesn't know what strat runner this is..." should only happen after it crashes, in which case there should be some logs about why it crashed. Let me know how it goes!

On a side note, the initial install complained when I tried to run it and I had to manually install a couple more node modules. Once we figure this out, I'll go back and do it all again and submit a PR if one is needed.

Great, thanks! Are you running the stable branch or the dev branch?

Stable.  I'll let you know if anything else happens with it.

👍  for now I'll assume this was a one off issue, so I'll close this. But feel free to reopen once it happens again.

Same issue here, with both docker and native installs on windows 10.
Gekko doesn't know what gekko this is..., or sometimes it just shows the loading bar and nothing happens. Crashes if I refresh the page. Requests look as the original poster's: -  --> POST /api/startGekko 200 14ms 1.23kb

I think this has something to do with the websocket connection.
@xtrinch are you using firefox or chrome?

Tried both, same result.

Are you running gekko on your own system? Is there any webserver between
gekko and the browser (such as nginx, Apache)
On Fri, 17 Aug 2018, 17:58 Mojca Rojko<EMAIL_ADDRESS>wrote:

Tried both, same result.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/823#issuecomment-413818062, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD1cS6QErqfprOAH8DJseBWs3zAEHks5uRpOtgaJpZM4OMUxo
.

I'm running gekko on my own system and as I mentioned, I also tried with docker but the result was the same. There is no webserver between gekko and the browser.

As long as your browser does not connect to Apache (to load the gekko UI)
there should indeed be no difference.
All: I will create a test branch with a ton of websocket debugging asap.
On Fri, 17 Aug 2018, 18:23 Mario Dantas<EMAIL_ADDRESS>wrote:

When I stop Apache server the Gekko behaviour is exactly the same
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/823#issuecomment-413823684, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD6oQgc053rdxgeezdIBtIestb8fqks5uRpmWgaJpZM4OMUxo
.

@askmike Tracked the error down to https://github.com/askmike/gekko/blob/bc745a2afcebe39695ed9496b7f445d0df6ca4ec/web/server.js#L28
If I replace this with wss.clients.forEach(function(client) {... everything starts working as expected.
Something to do with lodash then perhaps?

Woa nice find! Anyone mind opening a PR? Else I'll do it when behind laptop.
On Fri, 17 Aug 2018, 20:59 Kgadi Kenneth Mphele<EMAIL_ADDRESS>wrote:

I had the same issue as @xtrinch https://github.com/xtrinch for the
past few days . I impemented @xtrinch https://github.com/xtrinch
solution to replace _.each with wss.clients.forEach(function(client) an
hour ago and it worked.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/823#issuecomment-413857294, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD1b6pw3-azdAGkNgEdhKep_u3YIPks5uRr4cgaJpZM4OMUxo
.

@askmike got it ! gladly.


Added sticky scrollbar and intersection API

There are two scenarios for handling the sticky top horizontal scrollbar issue:
For pages with a single table (recordset page), make the top scrollbar sticky.
For pages with multiple tables (record page), keep the top scrollbar sticky until the bottom scrollbar becomes visible.
Resolves #2448

Overall the changes look good and the feature behaves how I expect. I'll let Aref review and merge this PR when he gets a chance.


Changes for major version 2.X.X

[X] Implement 1.X deprecations
[ ] Add github mirror support
[ ] Add custom source host support
[ ] Use github mirror by default
[ ] Add old-game directory warning for builds

Codecov Report
Patch coverage: 76.92% and project coverage change: +0.92 :tada:

Comparison is base (0c4a279) 84.41% compared to head (dc5d033) 85.34%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #21      +/-   ##
===========================================
+ Coverage    84.41%   85.34%   +0.92%
===========================================
  Files            8        8
  Lines          353      348       -5
  Branches        49       46       -3
===========================================
- Hits           298      297       -1
+ Misses          12       11       -1
+ Partials        43       40       -3

Flag
Coverage Δ

macos-latest
?

ubuntu-latest
?

windows-latest
85.34% <76.92%> (+0.92%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/model/parameters.ts
81.81% <ø> (ø)

src/adapter/parameters.ts
82.60% <57.14%> (+0.91%)
:arrow_up:

src/setup-renpy.ts
90.38% <100.00%> (+4.93%)
:arrow_up:

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

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


Fix homebrew release automation

It was creating invalid PRs as the local state of the taps it based the changes on were outdated

posthumous 👍


Make Netty SO_BACKLOG configurable

For https://github.com/apache/incubator-doris/issues/1637

Besides this, thrift server also have a default backlog(50).
It's better if you can modify it together.

OK, Update.


[WIP] Extended ghost version utility

no issue

differentiate between

original package.json version (can contain prerelease postfixes or custom once)
full package.json version X.X.X
safe package.json version X.X (major+minor)
allowPre: parses the full version including the suffix for prereleases
build: allows build, falls back to full if not available

exporter allows to export the version including pre-release suffix

version mismatch middleware uses the full version

e.g. 1.9.0-pre can be used with admin client 1.8.0
this does not work on master, which should work

public configuration endpoint uses full version and allows to expose the information if it's a pre-release

refs https://github.com/TryGhost/Ghost-Release/issues/24

[x] evaluate this idea https://github.com/TryGhost/Ghost-Release/issues/24#issuecomment-349249934

[ ] remove allowPre and modify version mismatch middleware to compare without pre-release

exporter uses the original version - no matter what, export the original

Hmm will reconsider this before merging. I think having a custom suffix inside the exporter is maybe too visible.

I've added another TODO to the PR description. Back to WIP.

Okay i have updated the PR.
There is another ghostVersion.build available - if not available, it falls back to full.

The order should be: First merge and release+rollout this.
Then we are able to continue with https://github.com/TryGhost/Ghost-Release.

I've added another todo, which have discussed internally. See PR todo's on top.

@ErisDS Updated PR and PR head.


fix ipv6 depreference for Linux #9

I think it is not recommended to use that right? See: https://github.com/maple3142/cf-warp/issues/9#issuecomment-605695009
Also, don't change formatting such as indentation, quotes...
Besides, I think inject untrusted variable(config.interface.addresses.v6) into command is not really safe.