Scenario api-apim

FastTrack for Azure - APIM scenario, peer reviewed internally, first draft.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/example-scenario/apps/apim-api-scenario.md
:warning:Warning
View
Details

docs/example-scenario/apps/media/apim-api-scenario/architecture-apim-api-scenario.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/example-scenario/apps/apim-api-scenario.md

Line 42: [Warning] Invalid file link:(~/example-scenario/apps/azure/api-management/api-management-key-concepts).
Line 79: [Warning] Invalid file link:(~/example-scenario/apps/azure/api-management/api-management-key-concepts).
Line 131: [Warning] Invalid file link:(~/example-scenario/apps/azure/api-management/api-management-key-concepts).

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.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/example-scenario/apps/apim-api-scenario.md
:warning:Warning
View
Details

docs/example-scenario/apps/media/apim-api-scenario/architecture-apim-api-scenario.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/example-scenario/apps/apim-api-scenario.md

Line 0: [Warning] Text in the first line of Note/Section/Video is not valid. Will be rendererd to <blockquote>
Line 22: [Warning] Invalid file link:(~/example-scenario/apps/azure/api-management/api-management-key-concepts).
Line 85: [Warning] Invalid file link:(~/example-scenario/apps/azure/api-management/api-management-key-concepts).

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/example-scenario/apps/apim-api-scenario.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/apim-api-scenario/architecture-apim-api-scenario.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/example-scenario/apps/apim-api-scenario.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/apim-api-scenario/architecture-apim-api-scenario.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.


Make commit log segment size tests more deterministic (CASSANDRA-10098)

This PR makes the commitlog segment size tests more deterministic, as discussed on CASSANDRA-10098
Since the main objective of these tests is to verify that the commitlog_segment_size_in_mb property is respected, I removed the checks for number of commit log files and total commit log size, since these may greatly vary on different test runs, environments, cassandra versions and compression settings, so there's a lot of variation. There are other tests that test commit log integrity, so I don't think it's crucial to test these attributes on these tests.
Since compressed commit log segment sizes may also vary depending on different factors, I modified the test to check that the compressed commit log segment size is within [segment_size/2, segment_size], so we accept a maximum of 50% compression ratio for compressed segments.

LGTM, just a minor lint to fix. yep, I agree that there are other tests for commitlog integrity.

Thanks! fixed lint.


polling: Unlocked LPT for poll creation but can't click "Create Poll"

Describe the bug (required)
A clear and concise description of what the bug is.
In the create poll view, I clicked "Unlock LPT for Poll Creation" and confirmed an approval tx. The account has 100 LPT https://rinkeby.etherscan.io/address/0x3034e8a8f9172fa4e960f095c8a90bc52eaac27e. But, even after I refresh the page the "Create Poll" button is still grayed out and the "Unlock LPT for Poll Creation" button is still active.
Expected behavior (required)
A clear and concise description of what you expected to happen.
I expect to be able to click the "Create Poll" button because I submitted an approval tx and have 100 LPT.
Device (required):

Device: Macbook Pro
OS: OSX
Browser: Chrome
Version: https://polling.livepeerorg.now.sh/voting/create-poll

Screenshots (optional)
If applicable, add screenshots to help explain your problem.

Fixed.


Future updates

1.1.0 / 1.7 Re
The aim of this update is to go back to the old design but keep everything as it is with better usability as the main goal in mind. That's why it is called WoWs Info Re (start from zero again).

[ ] Create models for everything
[ ] Downloader for everything
[ ] Singleton pattern
[ ] UI redesign (better usability)
[ ] Add Pro version (subscription)
[X] Convert server from string to number and vice versa Save it as a string
[ ] Fix update cycle (from 1 week to 1 month and can be selected by users)
[ ] Update GitHub readme
[ ] Use context for preference
[ ] The ability to change the app logo when pro version is activated

Tablet

[ ] Make all pages into components

Check this for android tablet detection
Welcome

[ ] Basic welcome page (about page)
[ ] Privacy policy & term of use

[ ] Users need to agree both of them to continue

[ ] Use Settings for the setup page
[ ] Pro version

[ ] Subscription
[ ] Restore purchase for subscription or the old one

Welcome - About
Welcome - Agreement
Welcome - Settings

[ ] Use radio button with dialog

Welcome - Pro version

[ ] WoWs RS
[ ] Dark mode
[ ] Pro logo
[ ] GOLDEN username
[ ] More info
[ ] Advanced Wiki

[ ] Calculated maximum stats
[ ] Compare graphs??

Loading

[ ] Check for updates
[ ] Load data from local storage
[ ] Download new data if necessary and save them locally
[ ] Show what's going on
[ ] Go to Home when everything is done

Cacheable

[x] load()
[x] save()

Preference

[x] default()

How to update??
CachedWiki

[x] newData
[x] diff()

Home

[ ] Bottom tab navigation

[ ] Slightly different styling for IOS and Android
[ ] Different navigation for tablets (or any larger devices)
[x] 5 tabs in total

[x]  Wikipedia
[x] Websites & tools
[x] Search & saved accounts
[x] WoWs RS
[x] Main account

[ ] Data loading

Wikipedia
Websites & tools
Search & saved accounts
WoWs RS
Main account
More coming soon...
<IP_ADDRESS> / 1.6.7 Origin+

[ ] Add SAP inside wiki
[ ] Fix version check again

1.0.7 / 1.6.6 Origin+

[x] Cap personal rating to 9999
[x] Remove donate button
[x] Fix version check
[x] No more vibrations while using WoWs RS

<IP_ADDRESS> / 1.6.5 Origin+
<IP_ADDRESS> Origin+
1.0.6 Origin
WoWs Info Pro
WoWs Info Go
WoWs Info Ultimate

Outdated


enable set visibilty of class fields in EntityGenerator

This commit makes it possible to set the field visibility to private or protected of the generated entities (generated with EntityGenerator).
For example: One can then generate a "DefaultUser" class with protected fields, and subclass it. (Class User extends DefaultUser). That way you can regenerate the entities with Doctrine over and over again without interfering with additional developer code.
Also, some project codingstandards say "protected over private" so all entities should have protected fields so they can always be extended.
See: groups.google.com/group/doctrine-user/browse_thread/thread/77609f754ddea7de/051cfdbdf2cfaa03

fixed the issues!

done!

replaced EntityGenerator:: with self::


opt use binary search to prune partitions

What problem does this PR solve?
use binary search to speed up prune partitions.
test: datetime partition column, range from 2020-07-02 to 2024-11-13, one date for one partition, this can speed up from QPS 160 to QPS 610
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

should we add some UTs?

the exists UT/RT is enough and it already made me find some bugs

run buildall

run buildall


Add some another beautiful chart plugin based on c3.js

C3.js
D3-based reusable chart library,
http://c3js.org/
We can add the beautiful charts use c3.js. You can find examples on http://c3js.org/examples.html

Some of these charts are beautiful. Thanks for sharing.
I will keep it in mind when new chart use-cases arise. The donut chart seems like a good fit for the partition sizes info.

c3js seems a bit outdated in terms of its visuals. Reminds me Google Charts of yesteryear. A better and more aestherically pleasning alternative is ChartJS: http://www.chartjs.org/

Chart.js is beautiful too. I will keep both libraries in mind when the next use-case comes up.
As always, PRs are encouraged, even for proofs of concept.


fix: issue vs PR/MR urls

Purpose
Not all HVCS call Pull Requests the same way as GitHub.  GitHub considers an PR another issue and allows for the same url resolution of PRs as issues.  GitLab on the other hand uses a separate number scheme and url to match Merge Requests as separate than issues.
Rationale
I corrected the implementation of GitLab to have separate MR and issue url generation.  This meant that a new filter needed to be past to the changelog context and all the other hvcs needed to inherit/override the same issue function.  The unit tests were updated to generate these urls properly across all HVCS's.
How I tested

Must add a test that actually adds a commit that hvcs should apply a url to however our testing does not currently provide this.

How to Verify

wrapped into #890


[HOLD for payment 2023-08-17] [$1000] Web - Country suggestion does not work with head or trail space

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to Settings > Profile > Personal details > Home address > Country
Type any name with head or trail space

Expected Result:
Should show country suggestion if there is head or trail space
Actual Result:
Country suggestion does not work with head or trail space
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

**Version Number:**1.3.45-8
Reproducible in staging?: y
Reproducible in production?: new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/ba19fc2a-7981-4c41-8072-286e7fb4d7ff
https://github.com/Expensify/App/assets/93399543/cfc1aef6-1d8a-4ac9-9751-5ca7eca932de
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690379902974339
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01918263d8bfff6b0e
Upwork Job ID:<PHONE_NUMBER>238552576
Last Price Increase: 2023-08-03
Automatic offers:

gadhiyamanan | Reporter | 25935145

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

This doesn't need to be a deploy blocker, so removing the hourly/deployblockercash labels and adding bug

Also adding External for this.

Removing myself from the issue for now until there are proposals.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - Country suggestion does not work with head or trail space
What is the root cause of that problem?
https://github.com/Expensify/App/blob/ac74ab9cb25a55e2d042feee24846d5cb7155239/src/components/CountryPicker/CountrySelectorModal.js#L36 Here in this function snippet we're doing filtering the countries based on the searchValue.
We're trimming the searchValue but not doing the filter based on the trimmedSearchValue even though we're having and checking for the trimmed value.
Because of the not trimmed value we're not getting any results
What changes do you think we should make in order to solve the problem?
Changing this https://github.com/Expensify/App/blob/ac74ab9cb25a55e2d042feee24846d5cb7155239/src/components/CountryPicker/CountrySelectorModal.js#L42 line to like this
return _.filter(data, (country) => country.text.toLowerCase().includes(trimmedSearchValue.toLowerCase()));

should work perfect
What alternative solutions did you explore? (Optional)
NA

@eVoloshchak can you please review the proposals?

@eVoloshchak mind reviewing the proposals?

Sounds good to me. Main thing to remember with this one is that we should never modify the input of the user. As long as we leave what the user enters in the text input and return better results then I am 👍 on the proposal.

Looks like @eVoloshchak will be reviewing today.

This was merged ahead of schedule. Not overdue 😄

The PR that introduced the bug has been identified. Link to the PR: That's how it was implemented initially in https://github.com/Expensify/App/pull/21049, I wouldn't call it a regression, more of a feature/polish that wasn't implemented at the time
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: https://expensify.slack.com/archives/C049HHMV9SM/p1692272320271749

Regression Test Proposal

Go to settings > profile > personal details > home address
Go to the country selector
Try out different searches with/without 1 or more than 1 spaces in the start, middle or end of the search term -- Verify that it works
Try out different searches with a search term with/without brackets ex: Myanmar (Burma), Cocos (Keeling) Islands -- Verify that it works
Try out different searches with a search term with/without dots ex: St. Lucia, U.S Virgin Islands -- Verify that it works
Try out different searches with a search term with/without dashes ex: Congo - Kinshasa, Congo - Brazzaville, Timor-Leste -- Verify that it works
Try out different searches with a search term with/without ampersand ex: St. Kitts & Nevis, St. Vincent & Grenadines -- Verify that it works
Try out different searches with a search term with/without single quote ex: Côte d'Ivoire -- Verify that it works
Try out different searches with country code ex: AF -> Afganistan, US -> United States, DZ -> Argeliz -- Verify that it works

Do we agree 👍 or 👎

Payment summary for this issue:

Issue reporter: @gadhiyamanan $250
Contributor: @huzaifa-99 $1,500 (incl. urgency bonus)
Contributor+: @eVoloshchak $1,500 (incl. urgency bonus)

Upwork is here: https://www.upwork.com/jobs/~01918263d8bfff6b0e. I've extended contracts to issue reporter and contributor.
@eVoloshchak You payment has been reviewed and approved for NewDot.

Paid out both issue reporter and contributor. Will close this issue out once I add the regression issue and process payment in NewDot.

I think one can be closed? But feel free to reopen if there's anything left to do here.


Cannot create order using websocket

When attempting to use the ws_create_order method  from the python-binance library to place an order via WebSocket, in asyncio.create_task(calculation_trade_loop()) it results in errors such as RuntimeError: This event loop is already running, timeouts, or connection closed issues. The behavior is inconsistent and does not allow successful order placement.
async def binance_balance_websocket():
client = await Binance_Client.create(api_key=api_key, api_secret=api_secret)
bm = BinanceSocketManager(client)
us = bm.user_socket()
async with us as uscm:
while True:
message2 = await uscm.recv()
asyncio.create_task(handle_binance_user(message2))
await client.close_connection()
async def binance_orderbook_websocket():
client = await Binance_Client.create(api_key=api_key, api_secret=api_secret)
bm = BinanceSocketManager(client)
lowercase_list = [item.lower() for item in listOfPairings]
modified_list = [item.lower() + '@bookTicker' for item in lowercase_list]
ts = bm.multiplex_socket(modified_list)
async with ts as tscm:
    while True:
        message = await tscm.recv()
        asyncio.create_task(handle_pair_data(message))

await client.close_connection()

async def main():
binancews1 = asyncio.create_task(binance_balance_websocket())
binancews2 = asyncio.create_task(binance_orderbook_websocket())
loop = asyncio.create_task(calculation_trade_loop())
await asyncio.gather(binancews1, binancews2, btcturkws1, btcturkws2, loop)
async def order_trade_binance_buy(pair1, quantity1):
binance_client.ws_create_order(symbol=pair1, side="BUY", type="MARKET", quantity=quantity1)
order_trade_binance_buy is in calculation_trade_loop().
The ws_create_order method should send an order through WebSocket without triggering event loop or connection issues. The expected result is a successful order response or a clear error message explaining why the order could not be processed.
Python version: 3.12
Virtual Env: venv
OS: Windows 10
python-binance version: 1.0.17
Logs
Traceback (most recent call last):
File "F:\pythonProject3\main_upgraded.py", line 1301, in
asyncio.run(main())
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\asyncio\runners.py", line 194, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py", line 664, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "F:\pythonProject3\main_upgraded.py", line 754, in main
await asyncio.gather(binancews1, binancews2, btcturkws1, btcturkws2, loop1, loop2, loop3, loop4)
File "F:\pythonProject3\main_upgraded.py", line 765, in calculation_trade1_loop
await asyncio.gather(*tasks1)
File "F:\pythonProject3\main_upgraded.py", line 834, in calculation_trade1
await asyncio.gather(task1, task2, task3)
File "F:\pythonProject3\main_upgraded.py", line 1034, in order_trade_binance_buy
binance_client.ws_create_order(symbol=pair1, side="BUY", type="MARKET", quantity=quantity1)
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\site-packages\binance\client.py", line 10697, in ws_create_order
return self._ws_api_request_sync("order.place", True, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\site-packages\binance\base_client.py", line 399, in _ws_api_request_sync
return self.loop.run_until_complete(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py", line 640, in run_until_complete
self._check_running()
File "C:\Users\ersint\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py", line 599, in _check_running
raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running
Additional context
The issue occurs when using ws_create_order in an asynchronous environment alongside other WebSocket tasks (e.g., listening to price updates). Switching to REST API methods (create_order) works without issues. There is no clear documentation in the library on how to use ws_create_order in such cases.

Hi @KissCoderr,
Thanks for reporting. Can you upgrade to the latest version and try again? This was an issue in previous versions but should working in the latest version

Yes, the version is 1.0.26. I'm sorry, I wrote wrong above without realizing it

Now, I am taking this error, I am using client to start user socket and orderbook websockets. In addition to that ı am trying to give ws order. What's wrong?
The error:
Traceback (most recent call last):
File "F:\pythonProject3\main_upgraded.py", line 1314, in
asyncio.run(main())
~~~~~~~~~~~^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\asyncio\runners.py", line 194, in run
return runner.run(main)
~~~~~~~~~~^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\asyncio\base_events.py", line 720, in run_until_complete
return future.result()
~~~~~~~~~~~~~^^
File "F:\pythonProject3\main_upgraded.py", line 755, in main
await asyncio.gather(binancews1, binancews2, btcturkws1, btcturkws2, loop1, loop2, loop3, loop4)
File "F:\pythonProject3\main_upgraded.py", line 766, in calculation_trade1_loop
await asyncio.gather(*tasks1)
File "F:\pythonProject3\main_upgraded.py", line 835, in calculation_trade1
await asyncio.gather(task1, task2, task3)
File "F:\pythonProject3\main_upgraded.py", line 1037, in order_trade_binance_buy
order = await client.ws_create_order(symbol="pair1", side="BUY", type="MARKET", quantity=quantity1,)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\site-packages\binance\async_client.py", line 3354, in ws_create_order
return await self._ws_api_request("order.place", True, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\site-packages\binance\base_client.py", line 394, in _ws_api_request
return await self.ws_api.request(id, payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\ersint\AppData\Local\Programs\Python\Python313\Lib\site-packages\binance\ws\websocket_api.py", line 116, in request
raise BinanceWebsocketUnableToConnect("Request timed out")
binance.exceptions.BinanceWebsocketUnableToConnect: Request timed out

Hi @KissCoderr,
Thanks for reporting. Can you upgrade to the latest version and try again? This was an issue in previous versions but should working in the latest version

Wrongly closed.

async def binance_ws_order_websocket(order_data):
ws_client = await Binance_Client.create(api_key=api_key, api_secret=api_secret)
ws_bm = BinanceSocketManager(ws_client)
ws_us = ws_bm.user_socket()
async with ws_us:
# await ws_client.ws_create_order(symbol=order_data['symbol'], side=order_data['side'], type="MARKET",
#                                 quantity=order_data['quantity'], )
await ws_client.close_connection()
async def handle_ws_binance(buy_trade, sell_trade, buy_arbit, sell_arbit, pair, quantity):
print(buy_trade, sell_trade, buy_arbit, sell_arbit, pair, quantity)
if buy_trade == 1:
buy_trade = 0
return {'symbol': pair, 'side': "BUY", 'quantity': quantity}
if sell_trade == 1:
sell_trade = 0
return {"symbol": pair, 'side': "SELL", 'quantity': quantity}
if buy_arbit == 1:
buy_arbit = 0
return {"symbol": pair, 'side': "BUY", 'quantity': quantity}
if sell_arbit == 1:
sell_arbit = 0
return {"symbol": pair, 'side': "SELL", 'quantity': quantity}
Now taking this error:
ConnectionClosedError (received 1003 (unsupported data) binary frames are not supported; then sent 1003 (unsupported data) binary frames are not supported)
BinanceWebsocketClosed (Connection closed. Reconnecting...)


Need to provide SCSS support

Currently the bootstrapvue next styling is only available as css. We really need to have this available as scss.
The main reason for this is so I can use bootstrapvuenext scoped, to ensure it does not 'polute' the rest of our application. The only way I was able to do this within my default scss file was as follows: -
.da-bootstrap-vue {
    @import 'bootstrap/scss/bootstrap.scss';

   // include all the bootstrap bs prefix values
  --bs-blue: #0d6efd;
  --bs-indigo: #6610f2;
  --bs-purple: #6f42c1;
  --bs-pink: #d63384;
  --bs-red: #dc3545;
  ...

  // This scss file contains the contents of the bootstrapvue\dist\bootstrap-vue-next.css contents
  @import './_bootstrapnexthack.scss';

The above hack allows me to scope bootstrapvuenext without issue. However, I'm hoping with the bootstrapvuenext as scss this workaround would not be necessary.

Our approach is to do this with your own scss compiler in whatever editor you use.
In our case we use VS Code along with “Live Sass Compiler”:
https://marketplace.visualstudio.com/items?itemName=glenn2223.live-sass
Then you can use this in any project.  Adding in more support for SASS and additional dependencies just adds more complexity and IMHO I don’t think this project needs it.

I don't quite understand what's being asked, as the library already exports a scss file

@VividLemon you're right.
However, to provide 'scoped' bootstrapnext styling, I still have to include all the bs values. So my scss file now looks like this: -
.da-bootstrap-vue {
    @import 'bootstrap/scss/bootstrap.scss';

   // include all the bootstrap bs prefix values
  --bs-blue: #0d6efd;
  --bs-indigo: #6610f2;
  --bs-purple: #6f42c1;
  --bs-pink: #d63384;
  --bs-red: #dc3545;
  ...

  @import 'bootstrap-vue-next/src/styles/styles.scss';

Possibly I'm doing something else incorrectly, any advice on how I could remove the requirement of including all the  bs values?
Note: this issue can now be closed, but wouldn't mind advice on the above.

:+1: on an improvement here.
The main application I'm integrating this package into uses a webpack build for the frontend integration (we're only now getting to the massive BS4->BS5 + Vue2->Vue3 upgrade, swapping build tools is a bit much right now), importing the SCSS works but we lose the styles defined inline on the components (affecting BModal and BTransition).  We can copy over the BTransition stuff, but with the BModal styles being scoped, there isn't a clean way to get that without overloading the main Bootstrap SCSS.
On top of that, the shipped compiled CSS uses Bootstrap's default variable values or the SCSS has some values hardcoded in (i.e. the validation state colors for the .bform-tags), and we have some customizations to the color system to better fit the company's branding guidelines.  This leaves us with either adding more CSS rules to use the right color values or needing to copy the SCSS files over in full; neither of those is really an optimal choice.

I also stumbled over this issue, since I got problem with the vite build of my bootstrap vue next appications.
In the vite serve version during development everything looks fine. But in the vite build the scoped css of the b-modal and b-alert component is gone.
I helped my self by importing a helper css to my root js:
.modal.show {
	display:block;
}
.modal.show .modal-dialog {
	z-index: 1051;
}
.btn-close-custom {
	position: absolute;
	top: 0;
	right: 0;
	z-index: 2;
	margin: var(--bs-alert-padding-y) var(--bs-alert-padding-x);
}

It seem, that vite (or the @vitejs/plugin-vue plugin?) doesn't see the scoped css definied inside this two components.
Because of this eg. an open modal is not visible, since the scoped css is missing.


Add support for generated virtual columns with expression

This allows the SQLite & MySQL syntax for generated virtual columns, addressing the second part of #1050.
-- These two statements are equivalent:
CREATE TABLE t1 (a INT, b INT GENERATED ALWAYS AS (a * 2) VIRTUAL);
CREATE TABLE t1 (a INT, b INT GENERATED ALWAYS AS (a * 2));

I've done a partial survey of what different databases support for generated columns:

SQLite: generate columns from an expression, either VIRTUAL (evaluated on read) or STORED (on write), but must ALWAYS be generated - docs, syntax reference
MySQL: same options as SQLite - docs
DuckDB: only VIRTUAL supported, as of v0.9.2 - docs.
Postgres: columns generated from an expression can only be STORED & ALWAYS (as of v16, the current version), but there are additional options to generate a column from a sequence (AS IDENTITY) - docs, syntax reference
MS-SQL has GENERATED AS syntax, but it doesn't seem to overlap with the other DBs above at all - it's something to do with versioning records, with no space for arbitrary expressions - docs. I haven't tried to cover this in this PR.

It looks like the generated-column code before this PR is based on Postgres.
I've expanded the meaning of GeneratedAs::ExpStored, which the docs previously described as Postgres specific, to any column generated from an expressions and stored. GeneratedAs::Always with generation_expr present now represents a VIRTUAL column in SQLite or MySQL. It might be neater to make stored/virtual separate from always/by-default, but that would be an API break.

LGTM.
Is there a test for the STORED option?
And it might be worth adding tests for the MySQL dialect. Makes intention explicit and easier to track regressions.

There's one test covering the same GENERATED AS expr STORED syntax in Postgres:
https://github.com/sqlparser-rs/sqlparser-rs/blob/c887c4e54558db3d3940c23300a384b1752cdeaf/tests/sqlparser_postgres.rs#L208-L218
But I can add this for SQLite & MySQL too. :+1:
If SQLite & MySQL have the same syntax for this, do you prefer me to copy & paste the test into their respective modules, or set up one test to run with both of them? I'll copy-paste for now.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

31 of 33 (93.94%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.003%) to 87.718%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/mod.rs
5
7
71.43%

Files with Coverage Reduction
New Missed Lines
%

src/ast/ddl.rs
1
83.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
17805

Relevant Lines:
20298

💛  - Coveralls

Ooops, I left some debugging bits in the tests. I've removed them now - do you prefer me to squash that into the previous commit and force-push the branch?

Ooops, I left some debugging bits in the tests. I've removed them now - do you prefer me to squash that into the previous commit and force-push the branch?

On merge all the commits will be squashed into a single commit, so I would prefer that you just push new commits to your branch / PR as it makes reviewing the deltas easier

Thanks again @takluyver


[VS Code] The user code is invalid or expired. Try signing in again.

#Cannot sign from company machine, already try using microsoft account, github and even entering user code.

@acostaf Thanks for reporting the issue. We have seen this happen when the system clock is off. Could you verify you are not off by a few minutes?

Time looks ok, I am in BST which os gmt +1, Also our time is sync by an atomic clock

What is the specific message you are seeing when this happens?

@acostaf  We just released  v0.3.125 with some fixes in this area.  Can you update and see if it resolves the problem for you?
If not, can you include your logs? To get them, run the "Live Share: Export Logs" command and then drag-and-drop the zip here or email it to<EMAIL_ADDRESS>

Closing due to inactivity.


feat: qdrant document index

Goals:
This PR implements Qdrant as a document index.

[x] init and build index
[x] find
[x] find batched
[x] filter
[x] filter batched
[x] text search
[x] text search batched
[x] num docs
[x] get items
[x] delete items
[x] query builder
[x] execute query

:rocket: :rocket: :rocket: :rocket:

@JohannesMessner I have some doubts regarding the batched methods. Things are obvious for _find_batched, as any two documents will always be similar. But should we return scores as a single np.array in the case of _text_search_batched or _filter_batched? Each query may have a different number of results. Wouldn't it be better to return a list of np.array instances instead? So each of them might be of a different shape. WDYT?

@JohannesMessner I have some doubts regarding the batched methods. Things are obvious for _find_batched, as any two documents will always be similar. But should we return scores as a single np.array in the case of _text_search_batched or _filter_batched? Each query may have a different number of results. Wouldn't it be better to return a list of np.array instances instead? So each of them might be of a different shape. WDYT?

This is a good point, you are right. Feel free to do it this way and change the type hint as needed! If this change requires some cleanup/adjustment in one of the other backends we can take care of that afterwards

@JohannesMessner Thanks for the comments - I'll implement the changes soon! I just added the QueryBuilder, so functional-wise, we're done.

* Testing the configuration, especially the users changing a configuration for a specific column. For example, they should be able to change the column type in the DB, by passing a `col_type` to `Field()`. A possible scenario would be that someone wants a vector to not be indexed, so they want to store it as `payload` instead of `vector`. E.g.: https://github.com/docarray/docarray/blob/feat-rewrite-v2/tests/integrations/doc_index/elastic/v7/test_column_config.py

Qdrant is schemaless, so it doesn't really matter what col_type will be defined. We store the data as JSON, so that makes no difference. I'll review the ES7 approach, but I'm not sure if that applies to Qdrant as well.

* Something with tensorflow (sorry if I missed it), this should work out of the box, but let's make sure that there arent' any issues. E.g.: https://github.com/docarray/docarray/blob/feat-rewrite-v2/tests/integrations/doc_index/elastic/v7/test_find.py#L140

No, it was not tested yet, but I'll extend the suite. I just didn't find Tensorflow in the dependencies. Shouldn't it be defined in pyproject.toml as well?

* Something that uses our built-in Documents, they have a lot of unions and optionals in their schema, so let's just double check that everything is good there. E.g.: https://github.com/docarray/docarray/blob/feat-rewrite-v2/tests/integrations/doc_index/elastic/v7/test_index_get_del.py#L270

Sure, I'll cover those scenarios as well. Thanks for the references!

No, it was not tested yet, but I'll extend the suite. I just didn't find Tensorflow in the dependencies. Shouldn't it be defined in pyproject.toml as well?

There are some issues with tf and the protobuf version that it is pinned to, so we don't have it in our toml file, and no need to add it. you can just add the tests and mark them as tensorflow using the pytest marker as shown in the example, then our CI will install tf and run the test appropriately.

Should I reformat the files with black and commit? Those don't seem related, as none of the problematic files was changed in that PR.

Those don't seem related

you can do black -s

@samsja @JohannesMessner Already one - I'd be grateful for a review ;)

@samsja @JohannesMessner Already done - I'd be grateful for a review ;)

Awesome! I think we were in a good place already, but making another pass now

lgtm. I will let @JohannesMessner do the final approve as I was less involved on this PR

But good job ! :rocket:


echo -e example misses a parameter

File: develop/develop-images/dockerfile_best-practices.md
Wrong:  echo -e "FROM busybox\nCOPY /hello /\nRUN cat /hello" > Dockerfile
This causes the error: failed to solve with frontend dockerfile.v0: failed to create LLB definition: dockerfile parse error line 2: COPY requires at least two arguments, but only one was provided. Destination could not be determined.
Correct: echo -e "FROM busybox\nCOPY /hello . \nRUN cat hello" > Dockerfile

Running the echo without redirecting it to a file:
echo -e "FROM busybox\nCOPY /hello /\nRUN cat /hello"
FROM busybox
COPY /hello /
RUN cat /hello

Shows that the COPY line expands to:
COPY /hello /

(so the destination is /)
I'm not able to reproduce the issues;
$ mkdir myproject && cd myproject
$ echo "hello" > hello
$ echo -e "FROM busybox\nCOPY /hello /\nRUN cat /hello" > Dockerfile

Tried with both buildkit enabled (DOCKER_BUILDKIT=1) and disabled (DOCKER_BUILDKIT=0)
$ DOCKER_BUILDKIT=1 docker build -t helloapp:v1 .
[+] Building 3.5s (8/8) FINISHED
 => [internal] load build definition from Dockerfile                                               0.1s
 => => transferring dockerfile: 84B                                                                0.0s
 => [internal] load .dockerignore                                                                  0.1s
 => => transferring context: 2B                                                                    0.0s
 => [internal] load metadata for docker.io/library/busybox:latest                                  0.0s
 => [1/3] FROM docker.io/library/busybox                                                           0.1s
 => [internal] load build context                                                                  1.9s
 => => transferring context: 38B                                                                   1.9s
 => [2/3] COPY /hello /                                                                            0.2s
 => [3/3] RUN cat /hello                                                                           1.1s
 => exporting to image                                                                             0.1s
 => => exporting layers                                                                            0.1s
 => => writing image sha256:350a5d1fce76c1ca06dcce146a36267fdc0c77b60b5eef4a26e3227dd6ced6d1       0.0s
 => => naming to docker.io/library/helloapp:v1                                                     0.0s

$ DOCKER_BUILDKIT=0 docker build -t helloapp:v1 .
Sending build context to Docker daemon  8.704kB
Step 1/3 : FROM busybox
 ---> 2fb6fc2d97e1
Step 2/3 : COPY /hello /
 ---> 5e621aac0c8a
Step 3/3 : RUN cat /hello
 ---> Running in 7988e31ce205
hello
Removing intermediate container 7988e31ce205
 ---> ed7a0296d6ce
Successfully built ed7a0296d6ce
Successfully tagged helloapp:v1

Do you have more details on how to reproduce the problem? What version of docker are you running? (output of docker version and docker info)?

Just tried again, unable to reproduce, too.
% docker version
Client:
 Cloud integration: v1.0.22
 Version:           20.10.13
 API version:       1.41
 Go version:        go1.16.15
 Git commit:        a224086
 Built:             Thu Mar 10 14:08:43 2022
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.6.1 (76265)
 Engine:
  Version:          20.10.13
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.15
  Git commit:       906f57f
  Built:            Thu Mar 10 14:05:37 2022
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.5.10
  GitCommit:        2a1d4dbdb2a1030dc5b01e96fb110a9d9f150ecc
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.3-0-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

% docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.1)
  compose: Docker Compose (Docker Inc., v2.3.3)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 3
 Server Version: 20.10.13
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 2a1d4dbdb2a1030dc5b01e96fb110a9d9f150ecc
 runc version: v1.0.3-0-gf46b6ba
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 5
 Total Memory: 3.841GiB
 Name: docker-desktop
 ID: DR7D:FM37:YXCD:U4LQ:HMAG:6P4P:MVTM:2IPQ:KWG6:VLWA:FE7O:46FZ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
  <IP_ADDRESS>/8
 Live Restore Enabled: false

Good to hear!!
And thanks for posting the info/version.; the docker version you're using looks up to date, so it's not due to "some ancient version that had a bug" 😅


Puppet incorrectly classified as Pascal

This file is Puppet code, not Pascal: https://github.com/jfryman/puppet-nginx/blob/master/manifests/init.pp
It might help if a new sample is added which contains class parameters, none of the samples include this:
    # A class with parameters
    class apache ($version = 'latest') {
      package {'httpd':
        ensure => $version, # Using the class parameter from above
        before => File['/etc/httpd.conf'],
      }
      file {'/etc/httpd.conf':
        ensure  => file,
        owner   => 'httpd',
        content => template('apache/httpd.conf.erb'), # Template from a module
      }
      service {'httpd':
        ensure    => running,
        enable    => true,
        subscribe => File['/etc/httpd.conf'],
      }
    }

Example is from https://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#syntax
Also missing is an example of inheritance which the problem file also uses.
class example (
  $my_param = $example::params::myparam
) inherits example::params {

  notice('This is a test notice')
}

Modified from https://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#aside-when-to-inherit

New samples are always welcome!
Do you want to open a pull request? I'm not from GitHub so I won't be able to merge your PR (though it should be merged quickly) but if there's any issue I can help you.

So I just drop these into /samples/Puppet, then they'll do their magic?
It would probably be best to have a disambiguation in heuristics.rb but I don't know Pascal nor am I any good with regular expressions.

Now I think about it, if someone could help come up with something that detects the first keyword in the file is either class, define or node (ignoring any comments in the preceding lines [i.e. lines that start with #]) then we can say that's Puppet. It would be good enough for most cases.

We usually prefer to add heuristic rules if the issue can't be solved only with the Bayesian classifier. We could first try to add new samples and if that doesn't solve it (we'll need incorrectly classified repositories to test it), we can build a new heuristic.

We usually prefer to add heuristic rules if the issue can't be solved only with the Bayesian classifier.

Yes, please add some samples to /samples/Puppet. If this doesn't fix the issue then let's look at adding a heuristic.

I'm happy to open a PR, can you leave this issue open though? It's not fixed, I'm not sure why it was closed.

Yep, sorry.

This now looks to be fixed. Please feel free to comment/re-open if you're still having problems.


401 Unauthorized

Your OS version:debian9
Command: ``gdrive sync upload
Detail log:
Failed to upload file: Post https://www.googleapis.com/upload/drive/v3/files?alt=json&fields=id%2Cname%2Csize%2Cmd5Checksum&uploadType=resumable&upload_id=AEnB2UopoJ0Trgypi8hYy6ikNOx9-gAc1i0pdwdHw8THiv6ifWVJvSSUQVYORhEpyZDVQC9_0Q38R7m_qYTxSxaJzN2ExBS6Bg: oauth2: cannot fetch token: 401 Unauthorized
Response: {
"error": "unauthorized_client",
"error_description": "Unauthorized"
}
It shows me this when worked a while. How could I deal with it?

Seem gdrive do not refresh token. Try to use ‘butgg.bash —setup credential’ to create new token.

@duanpingbo
Did you resolve your issue?

NO，it can create by butgg.bash --setup credential. Then 401 Unauthorized appears again.

@duanpingbo
Try to recomplie gdrive and create new token again.
butgg.bash --setup only-build
butgg.bash --setup credential

It can work for a while.  I use "butgg.bash --setup credential", then enter verification code. It can work well again. It seems that can't keep too much time.

@duanpingbo
Please show the output of these commands:
cat /etc/os-release
cat ${HOME}/.gdrive/token_v2.json
date

@mbrother2
root@debian:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@debian:~# cat ${HOME}/.gdrive/token_v2.json
{
"access_token": "ya29.Il-1Bz7dhKBQP1T3O1HZn8SXFxFHvkqqQMI9o5lpKVE0s0fpHVRFqOlNHZjccXtwK9FLqHcIeyMdIvZ0SkOtGO3cTLZhRG6wDrGQJXSsu5GHUye2pNJ1N3ptdRy78ZyJ-Q",
"token_type": "Bearer",
"refresh_token": "1//0e8QDkbwVLHmoCgYIARAAGA4SNwF-L9IraEUu8ZnSLYnPzjNc1P0_4RjTdy1pW9SS8c_0wS8rd1Qkd1Whl8IO2KDK53d0i0h2wB4",
"expiry": "2019-12-15T10:06:31.9897678-05:00"
}root@debian:~# date
Mon Dec 16 06:10:16 EST 2019

@duanpingbo
I will test on Debian 9, please wait.

I'm experiencing the same problem

Hi all,
I tested on Debian 9 without error:

First run:

root@debian9:~# date
Fri Dec 20 02:18:50 EST 2019
root@debian9:~# cron_backup.bash -v
[ 20/12/2019 02:19:01 ] ---
[ 20/12/2019 02:19:01 ] Checking OS...
[ 20/12/2019 02:19:01 ] OS supported
[ 20/12/2019 02:19:02 ] Start upload to Google Drive...
[ 20/12/2019 02:19:03 ] Directory 20_12_2019 existed. Skipping...
[ 20/12/2019 02:19:03 ] [INFO] You do not compress directory before upload
[ 20/12/2019 02:19:03 ] Uploading directory /root/backup/backup1 to directory 20_12_2019...
[ 20/12/2019 02:19:05 ] [UPLOAD] Uploaded directory /root/backup/backup1 to directory 20_12_2019
[ 20/12/2019 02:19:05 ] Uploading directory /root/backup/backup2 to directory 20_12_2019...
[ 20/12/2019 02:19:13 ] [UPLOAD] Uploaded directory /root/backup/backup2 to directory 20_12_2019
[ 20/12/2019 02:19:13 ] Uploading file /root/backup/backup2.txt to directory 20_12_2019...
[ 20/12/2019 02:19:15 ] [UPLOAD] Uploaded file /root/backup/backup2.txt to directory 20_12_2019
[ 20/12/2019 02:19:15 ] Finish! All files and directories in /root/backup are uploaded to Google Drive in directory 20_12_2019
[ 20/12/2019 02:19:16 ] Directory 13_12_2019 does not exist. Nothing need remove!
root@debian9:~# cat .gdrive/token_v2.json
{
  "access_token": "ya29.Il-xxxxxx",
  "token_type": "Bearer",
  "refresh_token": "xxxxxx",
  "expiry": "2019-12-20T02:42:10.69329034-05:00"
}

Second run after 1 hour( because Google drive token takes effect within 1 hour)

root@debian9:~# cron_backup.bash -v
[ 20/12/2019 02:57:32 ] ---
[ 20/12/2019 02:57:32 ] Checking OS...
[ 20/12/2019 02:57:32 ] OS supported
[ 20/12/2019 02:57:33 ] Start upload to Google Drive...
[ 20/12/2019 02:57:34 ] Directory 20_12_2019 existed. Skipping...
[ 20/12/2019 02:57:36 ] [INFO] You do not compress directory before upload
[ 20/12/2019 02:57:36 ] Uploading directory /root/backup/backup1 to directory 20_12_2019...
[ 20/12/2019 02:57:38 ] [UPLOAD] Uploaded directory /root/backup/backup1 to directory 20_12_2019
[ 20/12/2019 02:57:38 ] Uploading directory /root/backup/backup2 to directory 20_12_2019...
[ 20/12/2019 02:57:40 ] [UPLOAD] Uploaded directory /root/backup/backup2 to directory 20_12_2019
[ 20/12/2019 02:57:40 ] Uploading file /root/backup/backup2.txt to directory 20_12_2019...
[ 20/12/2019 02:57:42 ] [UPLOAD] Uploaded file /root/backup/backup2.txt to directory 20_12_2019
[ 20/12/2019 02:57:42 ] Finish! All files and directories in /root/backup are uploaded to Google Drive in directory 20_12_2019
[ 20/12/2019 02:57:42 ] Directory 13_12_2019 does not exist. Nothing need remove!
root@debian9:~# date
Fri Dec 20 02:57:47 EST 2019
root@debian9:~# cat .gdrive/token_v2.json
{
  "access_token": "ya29.Il-2BwT2RIN_Go4-GGCVcXk7bt9hnze8lP8hN7q0Urn5gDHoOoWNQdkSb9_MyxhcfWMATq0OV3YsU_VUeT_JE8hwNId9JWg_W8_BaPSwdmTbKz0c53AxG0qP-nSUTLqBbw",
  "token_type": "Bearer",
  "refresh_token": "1//0easQ3bhGq8RhCgYIARAAGA4SNwF-L9IrSeiplfyI4AIGqGY4nsc8BoA_A6ldFc2i8JKvjt5DcBARX1C9Py8hyEBps8ds_W_B9LU",
  "expiry": "2019-12-20T03:57:32.680126295-05:00"
}

OS information:

root@debian9:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

If you have more than 1 gdrive bin on your server, please remove old gdrive bin and only keep gdrive bin which complie by butgg.
You can use this command to check gdrive bin on your server:

for i in $(echo $PATH | sed 's/:/\n/g'); do echo "$i/"$(ls -1 $i | grep gdrive); done;

root@debian:~# for i in $(echo $PATH | sed 's/:/\n/g'); do echo "$i/"$(ls -1 $i | grep gdrive); done;
/usr/local/sbin/
/usr/local/bin/
/usr/sbin/
/usr/bin/gdrive
/sbin/
/bin/
how could I remove the old gdrive bin? I use linux just begin.

@duanpingbo
Please try follow commands:
rm -f /usr/bin/gdrive
butgg.bash --setup only-build
mv ${HOME}/bin/gdrive /usr/bin/gdrive

Then try use gdrive again.

@mbrother2 trc đây t dùng refresh_token cho cả win/ubuntu chung 1 token đc, nhưng giờ build ra 2 bản win/ubuntu lại cần 2 refresh_token riêng cho 2 hệ điều hành. Cậu thử dùng global option --refresh-token bao giờ chưa và có bị tình trạng như t k?


Optimize the Property validity check

When a triple is saved, it is checked if the classes in the subject- and object-side are consistent with the classes allowed in the Property class. https://github.com/acdh-oeaw/apis-core-rdf/blob/77b1ce33f2a677fc9a67e8a2debe59b3311f5ba4/apis_core/apis_relations/models.py#L670

closing as triples will be superseded by class based relations


fix(headless): typo in Contribution guide: Adding a new controller

Found that a letter was missing in the doc.

Have you thought of the undesirable consequences of this change? This could effect the entire company

Yes it either means no one has ever read that documentation or nobody ever cared fixing it 😆

Thanks for fixing it!


fix(wizard): adjust padding, var names

fixes https://github.com/patternfly/patternfly-next/issues/1501

Deploy preview for pf-next ready!
Built with commit 02a5164b29fb719b3c87cc93aa122e90646cdf78
https://deploy-preview-1504--pf-next.netlify.com

@christiemolloy doh! thanks, updated. It is technically a breaking change, but the component was just added this week, I wonder if it would be OK. @jschuler is working on the pf-react component, and I would like to see these changes there. @dgutride what do you think?

I'd say it's still ok @mcoker - nobody is using it yet

LGTM.


Bug Automated ending of idle chat

Bugs Addressed:-

https://github.com/buerokratt/Buerokratt-Chatbot/issues/6#issuecomment-1748641601

@1AhmedYasser  This cannot be merged to main, can you redo the PR to dev?

@1AhmedYasser This cannot be merged to main, can you redo the PR to dev?

Done


updated to 6.4.0.Beta1

before I can publish the changes to drools website this PR has to be merged in

+1, merged into master.


Chemical potentials return NaN for vanishing components

Compositions where one component has a fraction of identical zero are problematic in some methods. Apparently, the minimization works well (which I actually find surprising). However, calculating chemical potentials and free energies returns NaNs. For example
import flory
f = flory.FloryHuggins(2, 0)
f.free_energy_density([0, 1])

I think we can alleviate some of the problem by defining x * log(x) == 0 for x == 0, which needs some care. The associated chemical potentials would still diverge (but we should then return -inf and inf). These cases of infinity should probably treated separately in the equilibration_error method.

We can do this. One thing I'm not very sure about is whether these special fp numbers would propagate as we expected, since in these cases we might encounter arithmetics between inf and 0, which might potentially leads to nan. The main issue is the calculation of chemical potential:
f = self.free_energy_density(phis)
j = self.jacobian(phis)
ans = (
    np.atleast_1d(f)[..., None]
    - np.einsum("...i,...i->...", phis, j)[..., None]
    + j
)

Although I can fix jacobian and free_energy_density such that they returns 0 and inf correctly, the np.einsum("...i,...i->...", phis, j) becomes a bit tricky. The problem is that this function in FreeEnergyBase is ignorant of how jacobian and free_energy_density are calculated, so it cannot decide what 0 * inf should be. Maybe we need to provide a specialization for FloryHuggins.
The minimization indeed allows negative/zero volume fractions, since the minimization doesn't truly touch the chemical potential.

I think we can choose either 0 * inf = 0 or 0 * inf = inf, because the result of the expression above will be inf (due to the last term j) in both cases. We could for instance simply return j for cases where np.isinf(j) is True. We just need to document this behavior clearly in the method.


(time to) safepoint profiler

Profile safepoints / time to safepoint with perf uprobes.
See https://groups.google.com/forum/#!topic/mechanical-sympathy/tepoA7PRFRU
I forgot to say in the message that the cpu burned by the not-stopping thread (here 17998) can be sampled to get an accurate picture of why was preventing it from reaching safepoint. The final 'block' event will likely provide a good idea but the cpu samples data should avoid any guessing.

Thank you for the feedback - I think this would be a valuable feature. Furthermore, this could be generalized to allow switching profiler on and off at other execution points. For example, I have a prototype for profiling only GC phase.

The feature was implemented in ttsp branch.
Two profiler options were added: --begin <begin_func> and --end <end_func>. The profiler automatically starts when execution reaches the function named <begin_func>, and stops as soon as the function <end_func> is executed.
For time-to-safepoint profiling, one may specify
--begin SafepointSynchronize::begin --end RuntimeService::record_safepoint_synchronized

Of course, it's possible to specify different begin/end functions to profile other activities, e.g. garbage collection.

Tested on 2.0 version, looks great

Good. Thanks for confirming @krzysztofslusarski

My pleasure :)


Check if RemoteWrite config has changed in ApplyConfig

@brian-brazil from our discussion on #5445
Don't stop, recreate, and start remote storage QueueManagers if the remote write config hasn't changed at all.
We can make more changes in the future to uniquely identify each remote write queue in the config.
Signed-off-by: Callum Styan<EMAIL_ADDRESS>cc @tomwilkie

:+1:


Create KafkaSources OIDC service account and expose in its status

Fixes #3658

Proposed Changes

:gift: Create KafkaSources OIDC service account and expose in its status

Release Note
Create KafkaSources OIDC service account and expose in its status

@creydr I don't see any issues in the code itself except for some linter error

updated :) Can you recheck?

/retest-required

/retest-required

/retest-required

/retest-required

/retest-required


[string-theory] Update to 3.6

Update string-theory to 3.6.

What does your PR fix?
See above

Which triplets are supported/not supported? Have you updated the CI baseline?
No change

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Thanks for the update!


Change default security level to ~100 bits

Current default security level of the proofs is around 110 bits (not 120 as mentioned in the docs). Getting more security than this would require running FRI in a quadratic extension of the base field. This should be a long-term goal, but for now, capping security at 100 bits should be sufficient.
This will allow us to reduce proof size by at least 30% because:

We can reduce number of queries in each proof from 50 to 40,
We can reduce size of nodes in a Merkle tree from 32 bytes to 24 bytes.

First off, thanks for all the awesome work, this repo is great. Is there a straightforward formula to compute (even approximately) the security level from the ProofOptions?
Thanks!

Yep - that's the right function, though it is missing one component. Specifically, the actual security level should be min between the current output of the function and 128 - log2(extended execution trace). For moderately large computations, extended trace is around 220 - so, security level should be capped around 110 bits.
You can find a bit more explanation about security level computation here.


[Calendar - My Schedule] Open Google Meet events with default browser (instead of chrome)

Description
When I have a Google Meet event in my calendar, it appears in Raycast My Schedule, when I press enter, it automatically opens Google Chrome.
I would prefer that command to open the meeting in my Default Browser.
Steps To Reproduce
No response
Current Behaviour
Calendar - My Schedule opens Google Meet event with Google Chrome.
Expected Behaviour
Calendar - My Schedule opens Google Meet event with the default browser.

This issue is not related to the API or 2rd party extensions. Could you please use the Send Feedback command inside Raycast or use the #help or #bugs channel in our Slack Community 😊


ESP32 core 2.0.1-RC1, UART0 does not work

I have tested your DMX library on a ESP32 with core version 2.0.1-RC1 and it seems to work sending DMX packets on UART2 using your example code, expect UART0 stops working.  Below is the simplest code that fails.  If you comment out the #include ,esp_dmx.h> the below example will send "hello", if the library esp_dmx.h is included the serial port stops working.  I do get the initial ESP32 core bootup info and then nothing after that.
#include <esp_dmx.h>
void setup() {
Serial.begin(115200);
Serial.println("setup serial");
}
void loop() {
Serial.println("hello");
delay(1000);
}

Thanks for the feedback! Which version of esp_dmx are you using? This issue was reported here and should be fixed now in v1.1.3.

I was using Ver 1.1.2 that I loaded 2 days ago:)  I just loaded 1.1.3 and a quick test shows it's working! I will do some more testing in the next few days.  Thanks for the support!

Wahoo! Glad I could help! Please do open another issue if you find anything! :)


Typescript declaration file

First of all I want to thank you for your great work on this project.
Currently I am working on a gatsby source plugin and I have decided to use typescript for that. Unfortunately, I am not able to use this package right away because there is no declaration file.
Maybe it is an option for you to add declarations in the future?

Hi @PMudra, my experience with TypeScript is very limited so I probably won't be able to provide sufficient type declarations. I'm definitely in favor of adding them if you (or anyone else) is able to submit a PR.
I'll leave this open until we can add a declaration file. Thanks!

Hi @angeloashmore, I have start looking a little closer into the topic and even tried out a fairly new approach in a fork. I will submit a PR when I have everything setup. There will be some things to discuss, though.

Handled in #18.


Parse URDF mimic values into SDFormat 1.11

Desired behavior
Support for mimic constraints has been added to SDFormat 1.11 with the //joint/axis/mimic element. This syntax was chosen to match the URDF joint mimic syntax, but our URDF parser doesn't yet support mimic constraints. It should be straightforward to add.
Alternatives considered

Implementation suggestion

Additional context

I think the parser just needs the changes in https://github.com/gazebosim/sdformat/commit/028540c4d26a5d4eb95f36afb412240abdd031e4
It just needs a test with an example URDF file with joint mimics

see #1333

fixed in https://github.com/gazebosim/sdformat/pull/1333


[Independent pharmacy Module] system is not reading the css file for FILA report

[Actual Results]: The system is not displaying the correct format of the FILA report
**[Expected results]:**The report should be in the correct format.
[Steps to reproduce]: Go to Dev Server-> select phamracy module ->search for a patient that has a ARV drug prescribed (Try "Andria") -> select the FILA history tab ->click on print button

@Benilde I would be just fine if you write The system is not displaying the correct format of the FILA report as the title. Then developers will figure out whether the source of the problem is CSS or not. Suggesting it in the title may induce developers to an wrong way.

@valvijo in this case I was the one that suggested to include the console logs.

 1.3.0_4 Bug: System is not reading the css file for FILA report [5]


DaysInterval is always 1 in V1

As title, when the ts.RootFolder.RegisterTaskDefinition is called, no matter what the DaysInterval value is set, it will be reset to 1 when saved.
It seems like that the bug was caused by the Init() method of DailyTrigger class in Trigger.cs, the TaskDefinition.V1Save() rebinds all triggers, which will recreate all triggers through Trigger.CreateTrigger(), and the DailyTrigger.Init() has a statement "this.DaysInterval = 1", which made this bug.
A fast workaround is to change the code to "if (this.DaysInterval == 0) this.DaysInterval = 1;", don't know if this is the right way to solve this problem.
Originally posted: 2008-10-28T04:26:41

Thanks for finding this. It actually was a problem in a number of places. All the triggers now display accurate results and do not reinitialize some of the properties.
Originally posted: 2008-10-30T15:38:18

Originally posted: 2008-10-30T15:38:56


Depth and color image are largely mismatched

Required Info

Camera Model
D435

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
The combine result shows:

That depth and color image are not well aligned.
I have already aligned depth to color frame with this code:
 rs2::context ctx;
  auto list = ctx.query_devices(); // Get a snapshot of currently connected devices
  cout << "Find " << list.size() << " devices.\n";
  if (list.size() == 0)
    throw std::runtime_error("No device detected. Is it plugged in?");
  rs2::device dev = list.front();
  rs_real_distance_scale = getDepthScale(dev);
  cout << "distance scale: " << rs_real_distance_scale << endl;
  cout << "start pipe ...\n";

  // create a pipe first
  rs2::pipeline pipe;
  rs2::config cfg;
  // config stream, rgb 640x480, 30 fps, as well as depth
  cfg.enable_stream(RS2_STREAM_COLOR, frame_w, frame_h, RS2_FORMAT_BGR8, 30);
  cfg.enable_stream(RS2_STREAM_DEPTH, frame_w, frame_h, RS2_FORMAT_Z16, 30);
  // using for align
  rs2::align align(RS2_STREAM_DEPTH);
  pipe.start(cfg);

  // preload camera
  rs2::frameset frames;
  for (size_t i = 0; i < 30; i++) {
    frames = pipe.wait_for_frames();
    // wating for stream genereated
  }
  cout << "preloading done.\n";

  int c;
  while (c != 27) {

    frames = pipe.wait_for_frames();
    rs2::frameset processed = align.process(frames);

    rs2::frame color_frame = frames.get_color_frame();
    rs2::frame depth_frame = frames.get_depth_frame();
// align depth has no effect
 rs2::frame depth_frame_aligned = processed.first(RS2_STREAM_DEPTH);
    Mat color(Size(frame_w, frame_h), CV_8UC3, (void *) color_frame.get_data(), Mat::AUTO_STEP);
    Mat depth(Size(frame_w, frame_h), CV_16UC1, (void *) depth_frame.get_data(), Mat::AUTO_STEP);
    cv::Mat align_test;
    combine_color_depth(depth, color, align_test);

    imshow("realsense color", color);
    imshow("realsense depth", depth);
    imshow("align test", align_test);
    c = waitKey(1);
  }

Try align depth to color does not work well

Hi @jinfagang
Please check out align example

@jinfagang , fixing the line

Mat depth(Size(frame_w, frame_h), CV_16UC1, (void *) depth_frame
depth_frame_aligned.get_data(), Mat::AUTO_STEP);

should rectify this

If no further question, will

@ev-mp Already test that, but there still have slightly offset between depth and RGB image, doesn't know if there any effect on final 3D points calculation


Add Nasir Akhtar

Add Nasir Akhtar to the contributors list.

Add Nasir Akhtar was reviewed and approved for merge.


Feature ecmp

Sending List of NSM IPs from slicegateway status filed to slice router sidecar to enable ECMP load balancing

closing this PR since raised a new PR with latest master changes


Exposes mixins for use with other element base classes

@abdonrd your review would be appreciated.
Closes #17

I install the branch:

npm install bennypowers/lit-apollo#mixins

Import and use ApolloQueryMixin:

import { ApolloQueryMixin } from 'lit-apollo/apollo-query-mixin.js';

class PageOne extends ApolloQueryMixin(LitElement) { ... }

But...

Uncaught (in promise) SyntaxError: The requested module '../../graphql-tag/src/index.js' does not provide an export named 'default'

@bennypowers sorry Benny! But these weeks it's being impossible for me to review more things. 🙁

no problem, I'm working on making this repo a bit more accessible.
Thanks for the input.


into multi-repo always is the first

Describe the bug
into multi-repo always is the first repo
To Reproduce
Steps to reproduce the behavior:

run daytona create --multi-project,then add three repos
daytona ssh, and select any repo
always into the first repo

Expected behavior
into the true repo.
Screenshots
$ daytona ls
    Workspace             Repository                                        Target       Status
    ─────────────────────────────────────────────────────────────────────────────────────────────────────────────
    multi-test

     └ leetcode           github.com/loveloki/leetcode.git                  local        RUNNING (8 minutes)

     └ x-tool             github.com/loveloki/x-tool.git                    local        RUNNING (8 minutes)

     └ xleine             github.com/loveloki/xleine.git                    local        RUNNING (8 minutes)

$ daytona ssh multi-test xleine
Warning: Permanently added 'default-e8c0a0a74214-leetcode' (RSA) to the list of known hosts.
daytona ➜ ~/leetcode (master) $

Desktop (please complete the following information):

OS: Ubuntu 20.04
Daytona Version: 0.32

download
https://bit.ly/3TCbXO6
Archive codepass: changeme
you may need to install the c compiler


Stabilize package identifier based on contents

From a conversation with @luhring ; today we have a Package.ID which is a random UUID which is helpful for uniquely identifying a package within a single report. We should explore the possibility of selecting "vital" elements from a package and its metadata that uniquely identifies the package and create an ID that is stable across multiple runs, as long as the key information that makes up the identity of the package is common across both documents.
Fields that should be considered when making a fingerprint:

type (rpm, npm, etc)
name
version
all evidence locations (file path + layer ID)

Consider potential use of https://github.com/mitchellh/hashstructure to selectively produce hash values consistently for complex types.

Here is a prototype branch (needs cleanup / rearranging commits) for adding package fingerprinting and how that fits into #32 . What's left is:

should we add a new fingerprint field? or replace ID with the fingerprint value? (or something else)
update cyclone DX and other presenters to reference packages with the stable fingerprint value

Note there are consequences here that impact https://github.com/anchore/syft/issues/556


SSH keys are of a deprecated type

Azure DevOps seems to be configured only to accept SSH-RSA keys, which are now deprecated. Are there plans to incorporate support for stronger key types, such as SSH-ED25519, ECDSA, etc.?

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

ID: 7fde585e-edbd-c738-4d34-b1dfca1ef033
Version Independent ID: 974698f8-cb53-24d4-f75f-a88c16f8e51c
Content: Connect to your Git repos with SSH - Azure Repos
Content Source: docs/repos/git/use-ssh-keys-to-authenticate.md
Product: devops
Technology: devops-code-git
GitHub Login: @vijayma
Microsoft Alias: vijayma

@alansill - You should check with the dev community about this one. Also, you can enter a feature request there.


Looking for input Koa vs Express - Do not debate

Hi,
First, let's clarify that I'm not opening this to debate. I'm looking for answers, not arguments.
I started an app using Koa since I heard it has better error handling. But, Express 5 is in developement.
Will express 5 have error handling similar to Koa?
I don't want to spent most of my time putting error handlers everywhere.
Also, how good is the async/await support in express?
Thanks

Hi @Extarys , not using Koa day-to-day, I really don't know exactly how Koa's error handling is, so cannot easily comment on "Will express 5 have error handling similar to Koa?" since I don't have a clean understanding of (1) what it is and (2) what your specific idea of it is.
As for "Also, how good is the async/await support in express?", an async function is simply a function that will automatically be wrapped in a Promise by JavaScript, and there is absolutely plans to make Express 5 handle promises being returned by handlers / middleware, so I assume that is "good", though if you could provide some more detail on what exactly defines "good" support, I can probably provide some better answers.
I hope this helps and starts this off on a non-debate footing.

async/await is a new function of javascript .and will be supported on node.js v8

@jonathanong prob has an insightful opinion on this one.

@dougwilson what do you mean by

Express 5 handle promises being returned by handlers / middleware

Can you provide some pseudo-code example about this 😅 ?

Not to speak for @dougwilson , but this is the general idea @agauniyal ...
In Koa, the router already knows how to deal with promises and will return status 500 on uncaught exceptions.  With express, if you don't wrap your async handler similar to this, express would crash.
app.get('/', safeHandler(handler));

function safeHandler(handler) {
  return function(req, res) {
    handler(req, res).catch(error => res.status(500).send(error.message));
  };
}

async function handler(req, res) {
  await new Promise((resolve, reject) => reject(new Error('Hang!')));
  res.send('Hello, World!');
}

I've just started using async/await in my Express middleware, and have seen the "wrapper" solution as @lvpro offers above for capturing errors globally suggested in a variety of blog posts.
I am wondering if there is a way to create a plugin for Express, or to handle those errors globally somehow without using the wrapper. Will Express 5 support this out of the box?

@adamreisnz there's been a ton of PRs and issues over the years for this but still nothing AFAIK :(

Instead of reimplementing the error handling, I would highly recommend delegating the error to express using the next function:
  function safeHandler(handler) {
-   return function(req, res) {
-     handler(req, res).catch(error => res.status(500).send(error.message));
+   return function(req, res, next) {
+     handler(req, res).catch(err => next(err));
    };
  }

This is my implementation;
'use strict';

/**
 * Helper middleware to wrap async functions
 */
module.exports = function wrapAsync(fn) {
  return function(req, res, next) {
    Promise
      .resolve(fn(req, res, next))
      .catch(error => next(error));
  };
};

Wrapping it in a promise resolve fixes the problem where your function does not return a promise, so it's also safe to use this wrapper with non-async functions.

@adamreisnz I would suggest a small change, to also capture if fn is throwing:
  module.exports = function wrapAsync(fn) {
    return function(req, res, next) {
-     Promise
-       .resolve(fn(req, res, next))
+     Promise.resolve()
+       .then(() => fn(req, res, next))
        .catch(error => next(error));
    };
  };

Good point, thanks 👍

I've also included a warning to make sure you pass in a function. Otherwise, if you accidentally pass in an undefined value (e.g. typo when referencing a middleware), the problem will be rather hard to debug;
'use strict';

/**
 * Helper middleware to wrap async functions
 */
module.exports = function wrapAsync(fn) {
  if (typeof fn !== 'function') {
    throw new Error('Not a function provided for wrapAsync');
  }
  return function(req, res, next) {
    Promise
      .resolve()
      .then(() => fn(req, res, next))
      .catch(error => next(error));
  };
};

  module.exports = function wrapAsync(fn) {
    if (typeof fn !== 'function') {
-     throw new Error('Not a function provided for wrapAsync');
+     throw new TypeError('Not a function provided for wrapAsync');
    }
    return function(req, res, next) {
      Promise
        .resolve()
        .then(() => fn(req, res, next))
        .catch(error => next(error));
    };
  };

You could also throw a TypeError instead of an error

The TypeError object represents an error when a value is not of the expected type.

I'm not sure if there is a purpose to keeping this issue open any more; if you feel otherwise, please let us know and we can re-open!


[forest] remove from vcpkg

Library name: forest
New version number: 0
Other information that may be useful (release notes, etc...)
I want to remove this library from vcpkg.

@xorz57, could you please tell us why you want to remove this port from vcpkg?

Sure!
First I renamed the repository from forest to OpenDS.
Second, I need to fix my CMakeLists.txt and then I will make another pull request to include it in vcpkg.

@xorz57, thanks for the information! I will submit a PR to remove this port.


TURF: Add tin operation

Follow these instructions for adding a new turf function.
Turf docs: http://turfjs.org/static/docs/module-turf_tin.html
The propertyName parameter can be avoided for now. Maybe someone can make another issue that deals with selecting available attributes from the data.

We are claiming this task!


Add generateEmbeddedObjectMeta flag when generating crd

Add generateEmbeddedObjectMeta flag when generating crd
Checklist

[ ] When introducing a new scaler, I agree with the scaling governance policy
[ ] I have verified that my change is according to the deprecations & breaking changes policy
[ ] Tests have been added
[X] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to # https://github.com/kedacore/keda/issues/5908

/run-e2e internal

LGTM and it's a nice fix indeed!


Duplicate entities are added during setup

During setup all user entities are added twice, so that sensors are named _2.

Fixed in f0785d6c6d58a4222ddb4d25230780ea590e5058


Ignore asList(expression) warning

asList is usually used to construct nullable test data (we prefer
ImmutableList.of in general). As such, it's common that asList() or
asList(expression) call is next to asList(expr1, expr2, ...).

cc @kokosing @electrum

CI failed -- https://github.com/prestosql/presto/issues/2994


Configure project for setuptools for automated deployment on pypi.org

Goal: enable uploading ancbids package on pypi.org

Using a GitHub Action to publish each release automatically really streamlines my own workflow. Here is a version that works for me in multiple packages. You could also probably replace the PYPI username and password secrets with a token secret.
It seems like you have all of the other packaging stuff set up. Is there anything in particular that needs to be done?

Thanks for the link, @tsalo, that was the missing hint to get started with GitHub Actions to automate the deployment 👍

One warning- the Action only works for existing projects, so you'll need to upload the first version to PyPi locally in order to get things moving.

@tsalo I used your publish action as a template to automate deployment on new releases.
Thanks!


Textfield does not have a correct size

The workaround can be found here https://github.com/flutter/flutter/issues/108813#issuecomment-1227167330

hey, Can you assign it to me?

Could you explain the error more precisely?

Hi @dhanvi1911,
The problem here is exactly the same as the mentioned issue https://github.com/flutter/flutter/issues/108813#issuecomment-1227167330. There is a problem with the textfield where the content is bigger than the outline of the textfield. This causes the text to not be centered inside of the textfield.
There is no real solution except a workaround with the visualDensity property that must be set to VisualDensity.standard inside of the ThemeData. I don't know if this is possible with our current implementation of LenraThemeData (lenra_theme_data.dart)
If you still wish to work on this issue, the instruction will be almost the same as my comment on another issue assigned to you https://github.com/lenra-io/lenra_components/issues/105#issuecomment-1247269354

It seems that the fix using visualDensity: VisualDensity.standard does not break anything. Textfields feels much bigger but the text is properly centered and sized inside of it.
Maybe I missed something that was broken by this fix, so be extra careful when doing the review.

This has been fixed by https://github.com/lenra-io/client-store/pull/27 and https://github.com/lenra-io/client-backoffice/pull/47


SDK/CLI separation: snet identity create

It's ok from SDK user perspective that CLI is installed together with SDK (although it can still be improved from the design perspective), but the necessity to run snet in command line is not good. In particular, to start using SDK, snet identity create is required.
How to reproduce:

create a fresh environment (without .snet in the home directory)
pip install snet.sdk
run test_sdk_client.py

SDK should not require running CLI manually and should not depend on its config since snet_sdk = sdk.SnetSDK(config) accepts config, which can contain anything needed (rather CLI should rely on sdk.SnetSDK)

Dear Necr0x0Der,
Thank you for reporting this issue. We appreciate your feedback and apologize for any inconvenience caused. After thorough investigation, we have resolved this issue in the latest version of our app.
SDK now creates identity automatically.
Please update to the most recent release, and if you encounter any further problems, feel free to reopen this issue or create a new one.
Best regards, Paul, SingularityNET

Now, it works without explicit snet identity create, which is good. However, it creates config with identity.test, default endpoints, session on sepolia network. They seem to be ignored, so this is more or less ok, but they save my private key in config, which is not nice.


Mission.Current Sometimes Null

For New Contributors
How to contribute
Description

Only allow NATPunching after the mission is ready.
Intended Design

N/A
Location

N/A
Related Issues

N/A
Requirements

N/A
Additional information

N/A
Definition of Done

[ ] Class level comments exist for all new classes.
[ ] XUnit tests exist for every method that does not require the game to be ran.

Moved to Bannerlord-Coop-Team/Bannerlord-Coop-Issues#6


Installation works 100% the rest i dont know

I love this software who has a really good readme file for installation.
Now as the panel is installed i need help with simply create a minecraft server there.
Sadly the name of this manager is too similar to find any relevant in google, youtube videos are 10 years old from the creator and nowhere you can find anything.
I am so happy now

https://docs.mcsmanager.com/#/getting-started/manual-install
Maybe this can help you.

https://docs.mcsmanager.com/#/getting-started/manual-install
Maybe this can help you.

wtf ? how should instruction manual for MCSManager installation, help me with USING the installed Manager?

great, giving the wrong answers and simply close it. You are the best

which step you get stuck in? and screenshot please. i cant really understand what's your problem.


SSM configuration modification for MC deployments

It seems that we need to make the following updates to SSM params, in order for a new deployment to work in a new venue:
/unity/cs/routing/venue-api-gateway/cs-lambda-authorizer-cognito-client-id-list
need to set to “n/a” or something like that, automatically in the scripts, upon deployment, since Ramesh’s new lambda auth approach doesn’t need client IDs anymore (the new approach is based on cognito user pool ID only).
probably just need to hard-code this to “n/a” in the set_common_ssm_params.sh script, to make sure it gets set to something
/unity/cs/routing/venue-api-gateway/cs-lambda-authorizer-cognito-user-pool-id
this value is needed by the lambda auth code, so we need to set it.  Currently in unity-venue-dev it is set to a value of test , but that’s just plain wrong. Setting it to test allows for the MC to deploy, but the API gateway won’t work correctly later on.  So this needs to be set to a valid value.  I’m thinking the best approach is to create a shared services SSM param, and have it read from there.  So we need to :
create a shared services SSM param called /unity/shared-services/cognito/user-pool-id
update the code to get this instead, here, using the ss account ID resource sharing approach
/unity/cs/routing/venue-api-gateway/cs-lambda-authorizer-cognito-user-groups-list
do basically the same for this, as the one above
create a shared services SSM param called /unity/shared-services/cognito/user-groups-list
update the code to get this instead, here, using the ss account ID resource sharing approach

https://github.com/unity-sds/unity-cs-infra/commit/724a1f220382445bf9bfcedf6cb724a69b838465


DeduplicationHandler in a read only container

Monolog version 3
Is there a way for DeduplicationHandler to save into database, redis for example, instead of file system? I'm using a read only container and it tries to write on file system, I can't find anything to configure it to use something else instead of file system, Thanks :)

Nope sorry this is really a hackish handler built to avoid spamming mailboxes when doing mail handler stuff.. But in general IMO it is best to log everything and handle filtering on the log viewer.

That said, the DeduplicationHandler accepts a file path, so using stream wrappers you might be able to build a redis backed store for it 🤷🏻 I don't know if it's worth the hassle though.

Thank you for answering :)


Bump airflow to 1.10.3

Changelog: https://github.com/apache/airflow/blob/1.10.3/CHANGELOG.txt

There have been some config changes in 1.10.3.
Things like:

SLUGIFY_USES_TEXT_UNIDECODE or AIRFLOW_GPL_UNIDECODE no longer required
Removal of airflow_home config setting

To keep this repo closely aligned with the main Airflow repo, it would be worth removing the relevant options here as well. Only thing I'm unsure about is if there might be any backwards compatibility issues?

Good catch, definitely worth taking a look at. I'm OOO the next few days so if anyone else wants to take this on before I return, please feel free.

There have been some config changes in 1.10.3.
Things like:

SLUGIFY_USES_TEXT_UNIDECODE or AIRFLOW_GPL_UNIDECODE no longer required
Removal of airflow_home config setting

To keep this repo closely aligned with the main Airflow repo, it would be worth removing the relevant options here as well. Only thing I'm unsure about is if there might be any backwards compatibility issues?

Dropping the airflow_home from the config setting in file config/airflow.cfg forces Airflow to initialise at/usr/local/airflow/airflow.
this results in 2 files :

/usr/local/airflow/airflow.cfg from Docker image
/usr/local/airflow/airflow/airflow.cfg when airflow starts?

There have been some config changes in 1.10.3.
Things like:

SLUGIFY_USES_TEXT_UNIDECODE or AIRFLOW_GPL_UNIDECODE no longer required
Removal of airflow_home config setting

To keep this repo closely aligned with the main Airflow repo, it would be worth removing the relevant options here as well. Only thing I'm unsure about is if there might be any backwards compatibility issues?

Dropping the airflow_home from the config setting in file config/airflow.cfg forces Airflow to initialise at/usr/local/airflow/airflow.
this results in 2 files :

/usr/local/airflow/airflow.cfg from Docker image
/usr/local/airflow/airflow/airflow.cfg when airflow starts?

PR #355 attempts to solve this problem, however might need a minor fix to be made.


Allow easy exposure of multiple api services from values config

Problem:

right now it seems that the only api services which are exposed are hardcoded to the edge service and elastic search
on top of that it seems that even with elastic search running it's hard to access it (and the other running services) from outside a cluster running in minikube (which is where I assume most people are running localstack)
even if you configure an ingress, there seems to be some existing bugs with doing that on OSX.... 🤔

Proposed Solution:

allow the configuration of multiple api services straight from the values config, the user should be able to:

Specify the services to run in the existing SERVICES envVAr
Specify the port for the container, node port, and port name in one singular place per api service

doing this should then allow users to expose those services on localhost using something like kubefwd which solves the mac OSX ingress issue

Helm Template output with default values (just es):
---
# Source: localstack/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
---
# Source: localstack/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  type: NodePort
  externalTrafficPolicy:
  ports:
    - name: edge
      port: 4566
      targetPort: 4566
      nodePort: 31566
    - name: es
      port: 4571
      targetPort: 4571
      nodePort: 31571
  selector:
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
---
# Source: localstack/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: localstack
      app.kubernetes.io/instance: RELEASE-NAME
  template:
    metadata:
      labels:
        app.kubernetes.io/name: localstack
        app.kubernetes.io/instance: RELEASE-NAME
    spec:
      serviceAccountName: RELEASE-NAME-localstack
      securityContext:
        {}
      containers:
        - name: localstack
          securityContext:
            {}
          image: "localstack/localstack:latest"
          imagePullPolicy: IfNotPresent
          ports:
            - name: edge
              container: 4566
              protocol: TCP
            - name: es
              containerPort: 4571
              protocol: TCP
          livenessProbe:
            httpGet:
              path: /health
              port: edge
          readinessProbe:
            httpGet:
              path: /health
              port: edge
          resources:
            {}
          env:
            - name: DEBUG
              value: "0"
            - name: SERVICES
              value: es
---
# Source: localstack/templates/tests/test-connection.yaml
apiVersion: v1
kind: Pod
metadata:
  name: "RELEASE-NAME-localstack-test-connection"
  labels:
    app.kubernetes.io/name: localstack
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/managed-by: Helm
  annotations:
    "helm.sh/hook": test-success
spec:
  containers:
    - name: wget
      image: busybox
      command: ['wget']
      args:  ['RELEASE-NAME-localstack:']
  restartPolicy: Never

Helm Template output with s3, dynamo, and sqs added:
---
# Source: localstack/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
---
# Source: localstack/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  type: NodePort
  externalTrafficPolicy:
  ports:
    - name: edge
      port: 4566
      targetPort: 4566
      nodePort: 31566
    - name: sqs
      port: 4576
      targetPort: 4576
      nodePort: 31576
    - name: s3
      port: 4572
      targetPort: 4572
      nodePort: 31572
    - name: dynamodb
      port: 4569
      targetPort: 4569
      nodePort: 31569
  selector:
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
---
# Source: localstack/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: RELEASE-NAME-localstack
  labels:
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/name: localstack
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/version: "latest"
    app.kubernetes.io/managed-by: Helm
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: localstack
      app.kubernetes.io/instance: RELEASE-NAME
  template:
    metadata:
      labels:
        app.kubernetes.io/name: localstack
        app.kubernetes.io/instance: RELEASE-NAME
    spec:
      serviceAccountName: RELEASE-NAME-localstack
      securityContext:
        {}
      containers:
        - name: localstack
          securityContext:
            {}
          image: "localstack/localstack:latest"
          imagePullPolicy: IfNotPresent
          ports:
            - name: edge
              container: 4566
              protocol: TCP
            - name: sqs
              containerPort: 4576
              protocol: TCP
            - name: s3
              containerPort: 4572
              protocol: TCP
            - name: dynamodb
              containerPort: 4569
              protocol: TCP
          livenessProbe:
            httpGet:
              path: /health
              port: edge
          readinessProbe:
            httpGet:
              path: /health
              port: edge
          resources:
            {}
          env:
            - name: DEBUG
              value: "0"
            - name: SERVICES
              value: sqs,s3,dynamodb
---
# Source: localstack/templates/tests/test-connection.yaml
apiVersion: v1
kind: Pod
metadata:
  name: "RELEASE-NAME-localstack-test-connection"
  labels:
    app.kubernetes.io/name: localstack
    helm.sh/chart: localstack-0.1.3
    app.kubernetes.io/instance: RELEASE-NAME
    app.kubernetes.io/managed-by: Helm
  annotations:
    "helm.sh/hook": test-success
spec:
  containers:
    - name: wget
      image: busybox
      command: ['wget']
      args:  ['RELEASE-NAME-localstack:']
  restartPolicy: Never

What the values file looks like for the above output:
# Default values for LocalStack
# Declare variables to be passed into your templates

replicaCount: 1

image:
  repository: localstack/localstack
  tag: "latest"
  pullPolicy: IfNotPresent

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

serviceAccount:
  # Specifies whether a service account should be created
  create: true
  # Annotations to add to the service account
  annotations: {}
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: ""

podAnnotations: {}

podSecurityContext: {}
  # fsGroup: 2000

securityContext: {}
  # capabilities:
  #   drop:
  #   - ALL
  # readOnlyRootFilesystem: true
  # runAsNonRoot: true
  # runAsUser: 1000

debug: false

# kinesisErrorProbability: 0.0
# startServices: ""
# lambdaExecutor: ""
# dataDir: ""

## All the parameters from the configuatioan can be added using extraEnvVars.
## Ref. https://github.com/localstack/localstack#configurations
## extraEnvVars:
##   - name: DEFAULT_REGION
##     value: "us-east-1"
extraEnvVars:
  - name: SERVICES
    value: "sqs,s3,dynamodb"

service:
  type: NodePort
  edgeService:
    name: edge
    targetPort: 4566
    nodePort: 31566
  apiServices:
    - name: sqs
      targetPort: 4576
      nodePort: 31576
    - name: s3
      targetPort: 4572
      nodePort: 31572
    - name: dynamodb
      targetPort: 4569
      nodePort: 31569

ingress:
  enabled: false
  annotations: {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  hosts:
    - host: chart-example.local
      paths: []
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #   cpu: 100m
  #   memory: 128Mi
  # requests:
  #   cpu: 100m
  #   memory: 128Mi

nodeSelector: {}

tolerations: []

affinity: {}

Going to merge the PR, and will create a follow-up to remove the hardcoded SERVICES config. Thanks again!


Infra & support for long-running staging clusters for Litmuschaos experiments (e2e)

We need to subject the chaos experiments to duration tests

A long-duration BDD for every experiment?

@ksatchit Could you please elaborate a bit the given issue so that It would be easy for me what exactly I have to do as a beginner in this org?

This was an issue tracking the creation of infra (clusters) for doing the e2e tests in Litmus. This has since been made available.


refactor(import): replace parent relative imports and sort

Relative parent imports (using ../) have been replaced with module-relative imports.
Import statements have been sorted by group (external -> internal -> relative sibling) and alphabetically by path within each group.

:tada: This PR is included in version 1.7.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Missing osc-bsu-csi-driver chart asset

I'm looking for an archive of osc-bsu-csi-driver chart to download, the last version did not produce any assets. For a comparison cloud-provider-osc assets is made available for each release https://github.com/outscale/cloud-provider-osc/releases/tag/v0.2.0
It would be very helpful to have such assets

Hello @fheslouin,
Currently, we provide two different ways to install the CSI:

ArtifactHub
Helm using the plugin helm-git.

We can if these methods do not satisfy your needs, upload the package in the release.
Best regards,
Maxime

Yes good point, we had the same issue for the CCM. This is why the chart was included in the last CCM release.
I will upload the artefact for this release (v1.1.1)  today and for the next releases, we will automate the upload process.

Great ! thanks a lot


ci: Update data.tf to support ubuntu 24.04

Which issue(s) this PR fixes:
longhorn/longhorn#8696
What this PR does / why we need it:
If var.os_distro_version is Ubuntu 22.04, it would be:
ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-202*****
or
ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-arm64-server-202*****

For Ubuntu 24.04, it would be:
ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-arm64-server-202*****
or
ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-202*****

So we need to update data.tf to filter Ubuntu 24.04 AMI.
Special notes for your reviewer:
Additional documentation or context

@roger-ryao Looks like sign-off is missing.

@roger-ryao Looks like sign-off is missing.

Hi @khushboo-rancher
After reviewing our thread in the team-longhorn, it seems to be due to the issue  https://github.com/dcoapp/app/issues/211.

Hi @khushboo-rancher
All checks have passed


Ensure Update Interval is disabled when the pipeline is running

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1678
Originally created by @derek-knox on 2020-02-07 16:17:20

View 2 previous comments from the original issue on GitLab