fs_watcher：对write的系统调用，进一步探测，更改挂载点的执行函数

Pull Request Template
Description/描述
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
此 pr 解决了什么问题
Fixes # (issue)
Type of change /PR 类型
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?/ 测试方式
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist/检查列表

[ ] My code follows the style guidelines of this project /代码规范检查
[ ] I have performed a self-review of my own code / 自己已经检查代码
[ ] I have commented my code, particularly in hard-to-understand areas / 有代码注释，尤其是关键代码
[ ] I have made corresponding changes to the documentation /变更内容同步到了文档中
[ ] My changes generate no new warnings / 变更没有新产生告警
[ ] I have added tests that prove my fix is effective or that my feature works /对修改代码添加了测试用例
[ ] New and existing unit tests pass locally with my changes / 对单元测试也同步更新了

@13186379707 review 一下

运行截图提供下。


Rename Castor Otu batch loader

Renames the Castor batch loader for Otus to Identifiers to have a more generic name. The batch loader reads in a csv file with 2 columns of "name" and "uri". An Otu gets created with the name of the value in the "name" column and gets a Global::Uri identifier with the value of the "uri" column.

Coverage increased (+0.06%) to 66.155% when pulling 1e95d7429f1db159cd852bb24146a2d6109f1543 on Merfoo:rename-otu-interpreter into 9b83a8551968bd87211b00eb9042421f9c35e411 on SpeciesFileGroup:development.


how to Ping/Keep-alive a ListenKey (USER_STREAM)

Ping/Keep-alive a ListenKey (USER_STREAM)
my code
async def spot_user(client):
    bm = BinanceSocketManager(client)
    logger.info("Binance futures Socket Manager started..")
    async with bm.futures_socket() as stream:
        while True:
            print(True)
            res = await stream.recv()
            if res is not None:
                logger.info(f"futures Socket Message Received: {res['e']}")

                print(json.dumps(res,indent=2))
            else:
                logger.error(f"futures Socket Message Received: {res}")

async def main():
    client = await AsyncClient.create(api_key=api_key,api_secret=api_secret)
    await spot_user(client)

if __name__ == "__main__":

    loop = asyncio.get_event_loop()
    loop.run_until_complete(main())

error " listenKeyExpired "
In binance api docs
Keepalive a user data stream to prevent a time out. User data streams will close after 60 minutes. It's recommended to send a ping about every 30 minutes.
how to send a ping about every 30 minutes?
please share full code(include my code too) for this.
please help me for this.

i test it and "listenKeyExpired" goen but while testing this error thrown
listen key same: keepalive
listen key same: keepalive
05/09/2021 06:14:58 PM India Standard Time - __main__ - INFO - futures Socket Message Received: ACCOUNT_UPDATE
{
  "e": "ACCOUNT_UPDATE",
  "T":<PHONE_NUMBER>803,
  "E":<PHONE_NUMBER>808,
  "a": {
    "B": [
      {
        "a": "USDT",
        "wb": "0.04258721",
        "cw": "0.04258721",
        "bc": "0.04258721"
      }
    ],
    "P": [],
    "m": "DEPOSIT"
  }
}
listen key same: keepalive
listen key same: keepalive
listen key same: keepalive
05/09/2021 06:15:21 PM India Standard Time - __main__ - INFO - futures Socket Message Received: ACCOUNT_UPDATE
{
  "e": "ACCOUNT_UPDATE",
  "T":<PHONE_NUMBER>779,
  "E":<PHONE_NUMBER>783,
  "a": {
    "B": [
      {
        "a": "USDT",
        "wb": "0",
        "cw": "0",
        "bc": "-0.04258721"
      }
    ],
    "P": [],
    "m": "WITHDRAW"
  }
}
listen key same: keepalive
listen key same: keepalive
listen key same: keepalive
05/09/2021 06:15:40 PM India Standard Time - asyncio - ERROR - Task exception was never retrieved
future: <Task finished name='Task-2084' coro=<KeepAliveWebsocket._keepalive_socket() done, defined at C:\Users\******\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\streams.py:216> exception=BinanceAPIException(<ClientResponse(https://fapi.binance.com/fapi/v1/listenKey?listenKey=V0ZlgbP********************************Hj9d5TiyAJypBmWVBY8g) [502 Bad Gateway]>
<CIMultiDictProxy('Content-Type': 'text/html', 'Content-Length': '1033', 'Connection': 'keep-alive', 'Server': 'CloudFront', 'Date': 'Sun, 09 May 2021 12:45:41 GMT', 'X-Cache': 'Error from cloudfront', 'Via': '1.1 1c8c957c4a5bf12***********0ec6570.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'BOM50-C1', 'X-Amz-Cf-Id': 'W1Bz6uYbDwVd9***********TvP7_Fm7STWg1g-3ZIuSESeA==')>
, 502, '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">\n<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n\n
502 ERROR
\n
The request could not be satisfied.
\n
\nCloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.\nWe can\'t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n
\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n
\n
\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: E_c3s1IcddQEb6Z*********************m3h07xkbA==\n
\n<ADDRESS>\n</ADDRESS>\n')>
Traceback (most recent call last):
  File "C:\Users\*******\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\streams.py", line 230, in _keepalive_socket
    await self._client.futures_stream_keepalive(self._path)
  File "C:\Users\*******\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\client.py", line 7362, in futures_stream_keepalive
    return await self._request_futures_api('put', 'listenKey', signed=False, data=params)
  File "C:\Users\*******\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\client.py", line 6471, in _request_futures_api
    return await self._request(method, uri, signed, True, **kwargs)
  File "C:\Users\*******\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\client.py", line 6449, in _request
    return await self._handle_response(response)
  File "C:\Users\*****\AppData\Local\Programs\Python\Python39\lib\site-packages\binance\client.py", line 6457, in _handle_response
    raise BinanceAPIException(response, response.status, await response.text())
binance.exceptions.BinanceAPIException: APIError(code=0): Invalid JSON error message from Binance: <bound method ClientResponse.text of <ClientResponse(https://fapi.binance.com/fapi/v1/listenKey?listenKey=V0ZlgbPufLPMccMF***********************************AJypBmWVBY8g) [502 Bad Gateway]>
<CIMultiDictProxy('Content-Type': 'text/html', 'Content-Length': '1033', 'Connection': 'keep-alive', 'Server': 'CloudFront', 'Date': 'Sun, 09 May 2021 12:45:41 GMT', 'X-Cache': 'Error from cloudfront', 'Via': '1.1 1c8c95********************************570.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'BOM50-C1', 'X-Amz-Cf-Id': 'W1Bz6uYbDw*********************************Fm7STWg1g-3ZIuSESeA==')>
>
05/09/2021 06:16:24 PM India Standard Time - __main__ - ERROR - futures Socket Message Received: None
listen key same: keepalive
listen key same: keepalive
listen key same: keepalive

i don't know above error is related to your repo or not.
if not related to your repo then close this issue.
Thanks


Fix the public scope of the buildEither(component:) components of RouterBuilder

Resolves #10

Codecov Report

Merging #12 (3d33b9b) into main (ca4988f) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   93.12%   93.12%
=======================================
  Files           8        8
  Lines         407      407
=======================================
  Hits          379      379
  Misses         28       28

Impacted Files
Coverage Δ

Sources/APIRouter/RouterBuilder.swift
88.37% <100.00%> (ø)

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


Upgrading from 2 -> 3 - seems helper functions are missing

Description
Last night trying to upgrade from 2 -> 3: Getting lots of errors around helper functions. Specifically, functions like isActiveNavigation are missing - and I can't see them anywhere in the repo.
Steps to reproduce
Upgrade Twill CMS from 2 -> 3
Expected result
Helper functions should be available.
Actual result
Helper functions are missing.
Versions
 3.0.2
 9.52.7
 8.1.15
 MySQL

Hi @kirkbushell please share at least one of the error message/stack so we can help you.
Are you using helpers like isActiveNavigation in your own code?
My first thought is that you published Twill blade layouts in the past, so you need to update them (or just delete them from your codebase if you aren't modifying them).

@ifox yeah, that's exactly what it was - I simply had to re-publish the views :)
Cheers!


readtimeout of zero will not send the request

The following code will not send a request:
endpoint = 'some.server.com'
data = {'foo':123}
requests.post(self._endpoint , json=data,
                          verify=False, timeout=(5, 0.00))

I would expect the library to send the request but not wait for the server to respond. This would correspond to a fire and forget type of request particularly useful for logging of non critical information

What does "will not send the request" mean? On my system, the request is sent, but a ReadTimeoutError is raised, which feels like exactly the expected behaviour. What are you seeing that makes you believe that's not happening for you?
Please note, however, that setting a timeout of exactly zero is a bad idea: see #2699 for more. We plan to forbid doing that entirely in future: instead, you should choose a small floating point value.

So "will not send the request" means that the request isn't sent to my server when the timeout is set to zero. I also get the ReadTimeoutError but no sending occurs.  My request is sent if i raise the read timeout from 0 to 0.01. Based on #2699 that it would be a bad idea for the library but its not bad from a usage perspective. In other words setting a read timeout seems to me to be a valid use case even if the underlying socket implementation has a bug in it.

@trcarden Our intention is that we will forbid it: it's simply not a sensible thing to pass to this library. Generally speaking, the better logic for a 'fire-and-forget' request is to set stream=True and simply close the request afterwards. This will ensure that the server really did receive the request, but won't block on reading any of the response body.

but won't block on reading any of the response body.

It will block on reading the headers though fwiw

Ok, I am trying to be practical here. I don't want to wait on the response coming back from the server but i do want to obligate the system to send the request. I could use UDP sockets but that requires a new server and a bunch more overhead. I completely understand TCP/IP and HTTP aren't really built for this but i think i can get 90%+ of what i need just setting a small value on the read-timeout. I did read in a couple places that setting a timeout of zero doesn't "obligate" the system to send the message (might only make it to buffers without getting transmitted) depending on the local implementation so i see why my problem might have been occurring.
@sigmavirus24 thank you for the note on the headers. Emulating a "best effort" protocol on top of TCPI/IP and HTTP with a upper bound on total wait time (caveats on limitations acknowledged) seems to work better with low read-timeout settings than enabling streaming responses. Eventually I think we will enable a UDP server.


Provision File storage

Description

ROKS provisioned via DA has only block storage.
We have a requirement that requires File storage.
Good to have File storage installation as part of (post) steps in ROKS provision process

New or affected modules
Not sure

By submitting this issue, you agree to follow our Code of Conduct

Opened the request at https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone/issues/729 . The file storageclass are added by the file storage addon. https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-apps

I was able to resolve this file storage issue by enabing the file storage add-on by following steps here --> https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-install
I used ibmc-vpc-file-dp2 storage class for rwx operations needed for db2 and pipeline run was successful in all tasks. @vburckhardt @padmankosalaram

@NatarajBTI your going to wan't to ensure that the override json you add to the repo that your docs will reference includes the config to provision the file storage addon

override_FileStorage.json
This issue is now resolved by adding the below entry in override.json file. Attached override.json file used above.
"addons": { "vpc-file-csi-driver": "1.2" }


Bended arrows

Create bended arrows
Add └   like characters on the bend

─────────────────────┐
                     │
                     │
                     │
                     │
                     │
                     │
                     │
                     │
                     ▼

What changes to Arrow tool?
When to bend? How to trigger it?
How many bends?

Maybe add a new tool - bended arrow. This way mouseDown and drag behavior of arrow can remain.


yocto for coin3d

There are recipes for coin3d.

What does this issue mean? Is it meant as question or does it mean: "Please provide a yocto build recipe for coin3d" or do you have knowledge of a build recipe you'ld like to share with us? Please clarify.

Please provide a yocto build recipe for coin3d

What is yocto?

Yocto is a build system for embedded devices. I have a lot of experience in writing recipes for RDK, a reference design kit for Linux from Comcast for interactive set-top box devices. The thing about Yocto is that you usually target a hardware vendor BSP and stack. There are generic yocto recipes for open-source projects that can be used for most Linux platforms.
I think the initial Yocto recipe for coin3d will be straight-forward with OpenGL dependencies. However, the windowing toolkit (i.e. Quarter, SoQt, etc.) will be take more work for the target platform. Are you thinking of Quarter/SoQt for embedded devices? Or are you thinking of a new toolkit that can be used for non-Qt platforms?


demo/milk/index.html not working

Latest Firefox over Windows 10. The Remember the milk demo does not correctly validate email or user entries. All entries return an error result.

While this is considered "content", there is no Issues area for the content repo and I wouldn't know the solution to offer a PR.

That file can be found here - https://github.com/jquery-validation/jquery-validation/blob/master/demo/milk/index.html. PR welcome.

Ahh, so this does belong here. Thanks.
As I said, I'm not qualified to offer a solution to this specific issue so I hope we can leave this open for someone who can look at it.

Update all versions of jQuery, mockjax, and validate.
'''

'''
In head tag of milk.html, works fine.

Latest pre-built version 1.19.5 / 2022-07-01 download works fine.
If you using from source, you need to build the distribution (dist) folder using grunt.

The real problem is that https://jqueryvalidation.org/files/ needs to be rebuilt from latest.
https://jqueryvalidation.org/files/lib/jquery.js is showing jQuery 1.11.1
Latest download prebuilt shows jQuery 3.1.1.
^^^ this is the problem, not the milk demo.


gorebuild will fail on Windows or other OSes where os.PathSeparator is not '/'.

I don't see a mention in the README that gorebuild is not supposed to be supported on Windows, yet it has an issue that would prevent it from working there.
Many places in the code assume that os.PathSeparator is /, but that isn't true on Windows and potentially other OSes.
ioutil.ReadDir(build.Default.GOPATH + "/bin")

build.Default.GOPATH+"/bin/"+f.Name()

return strings.TrimPrefix(dir, build.Default.GOPATH+"/src/")

The correct fix for this is to use filepath package to manipulate system filepaths, rather than concatenating strings. E.g.:
ioutil.ReadDir(filepath.Join(build.Default.GOPATH, "bin"))

filepath.Join(build.Default.GOPATH, "bin", f.Name())

This is true, although the more fundamental issue for Windows users is presumably that the code in dwarf.go currently inspects ELF and Mach-O executables only.


Add HTTP redirect option

Follow up to https://github.com/macadmins/installapplications/issues/76
Introduces --follow-redirects argument option to InstallApplications.
If this flag is passed, InstallApplications will follow redirects from the web server to the remote URL. By default, InstallApplications will not follow redirects. Thus, existing implementations should be unaffected by this feature addition.
I made an update to the README for this change. Let me know if anything else is needed.

LGTM!


[mpeg2d] fix for 'invalid temporal_reference count' commit

Issue: 1614
Test: see issue

"Issue: 1614" is done anyway ways. See https://github.com/Intel-Media-SDK/MediaSDK/pull/1450 as example


Making request crashes when no fair or location is set

seems to happen when offline when distance cannot be calculated


Calling the Cavalry does not change hand rank

According to report, Calling the cavalry does not change hand rank. Need to reproduce or get more info.

Calling the Cavalry card is going to be changed and implementation reworked, so this is not relevant anymore.


tests for points seem overly strict.

Currently there are a bunch of tests in points_test.go that appear to be designed for errors raised on minor problems with the input to ParseText. I notice however that it doesn't appear that ParseText implements the checks which the test expects.
I suppose that it makes sense to write the test first and then implement the expected behavior, however... in this case I think that the additional sanitization of input is unneeded. For instance "foo..bar" splits to fields like ["foo","","bar"] which, when building the path with filepath.join ends up collapsing out the empty path element. Similarly a leading "." ends up causing an empty path element between the storage directory and the whisper file name which similarly is collapsed.
The additional step of sanitization of these metric names would seem to be a wasted effort, even metric names like "foo.bar.." lead to only marginally confusing whisper file names like "foo/bar/.wsp" which arguably are valid and should be allowed.

I need this validations for scan bugs in carbon clients (metric senders). You're right - I will make strict mode is optional


support ComponentArrays

Implements #253.
Please let me know if I shoudl change something.

Some CI tests failed but I think it has nothing to do with this commit. Unfortuantlay it  says only This check failed when clicking on details...
Locally the tests pass.

Thanks for the PR.
The proposed way to support ComponentArrays looks great to me.
But the current implementation changes the interface, which is not desirable.
Please check my comments on addressing this.
Also, can you add a test with the use case of ComponentArrays so that we know this PR works as expected?
The example you have in https://github.com/TuringLang/AdvancedHMC.jl/issues/253 should be good enough.
You should be able to add packages only for testing purposes in the [extras] section in the Project.toml file.

Thanks for your review @xukai92! Your suggestion made a lot of sense.

Great! The changes look good to me.
It's quite neat to have ComponentArray offically supported in AHMC.
Thanks for the PR again!


Automated cherry pick of #1626: metadata permission

Cherry pick of #1626 on release/2.10.0.
#1626: metadata permission

Codecov Report

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

@@               Coverage Diff                @@
##             release/2.10.0   #1628   +/-   ##
================================================
  Coverage                  ?   7.72%
================================================
  Files                     ?     409
  Lines                     ?   62368
  Branches                  ?       0
================================================
  Hits                      ?    4818
  Misses                    ?   57142
  Partials                  ?     408

Flag
Coverage Δ

#aFlag
7.72% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/metadata.go
11.86% <ø> (ø)

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

Continue to review full report at Codecov.

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

/lgtm
/approve


Customer relationship

It would be useful to be able to link entities to customers the way you can already do with products.

I'm using this module output in a slighty different way, but I believe it can be useful to others. After adapting the output code, users on our website are creating entities on the front-end (only registered customers can do so) and we need to link these entities with the corresponding user that created them. "Linking entities to customes" would be a very useful feature. Also "Creating entities from the front end".
In any case, thanks for this great contribution.
Kind regards.


[Pose Model] The predicted xyz coordinate of the same image is not deterministic

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Linux, Mac
Mobile device if the issue happens on mobile device
No response
Browser and version if the issue happens on browser
No response
Programming Language and version
Python
MediaPipe version
0.10.0
Bazel version
No response
Solution
Pose
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
# I initiate the model like this
mp_model = mp_pose.Pose()

# And I use the mediapipe for inferencing the image to get the pose, say I only inference for just the landmark of nose
keypoints = mp_model.process(img.copy())
print(keypoints.pose_landmarks.landmark[mp_pose.PoseLandmark.NOSE])

>> x: 0.5427083373069763
 y: 0.2361130267381668
 z: -0.4000009596347809
 visibility: 0.9999982714653015

# Now, I try doing inference from the same image and model again
keypoints = mp_model.process(img.copy())
print(keypoints.pose_landmarks.landmark[mp_pose.PoseLandmark.NOSE])

>>  x: 0.5427098274230957
 y: 0.23612599074840546
 z: -0.4002065360546112
 visibility: 0.9999982118606567

You can see the output of this 2 images are slightly different.

Describe the expected behaviour
xyz coordinates is deterministic, and no random (temperature=0)

Standalone code/steps you may have used to try to get what you need
https://colab.research.google.com/drive/10f5lONDqOBHPNvT7BH1_8bDIR0L94-Pc?usp=sharing

Other info / Complete Logs
No response

I change this to this, The default argument static_image_mode=False
mp_model = mp_pose.Pose()
mp_model = mp_pose.Pose(static_image_mode=True)
Now it's deterministic


Multi-sign problem

1.bebtc-test is my  account to do some tests,active key ower list is 8 person,it should be only the man in the   list can approve a transaction,but we fond anyone can approve a transaction,it not safe.
2.bebtc-test account has no QBITS,but can approve a QBITS transaction.

Anyone can add an approval. It will just be ignored if it is not in the set of required approvals. The users that approve dont nees to have any funds except for the fee to pay for the approval ..


E2E Testing: PRs merged after a regression all get marked as regression as well

With the current architecture of the e2e tests there is a problem where:

A new release is created, this will be the baseline for the e2e performance regression testing
PR1 is merged which introduces a performance regression
PR2 is merged with no performance regression
PR3 is merged with no performance regression

however, all PRs will be compared against the same baseline. Thus not only PR1 gets marked as deploy blocker for having introduced a performance regression, but also PR2 and PR3.
This creates confusion and additional spam in slack:

As discussed here, the proposed solution is to create for each merge commit to make a new baseline build from the previous merge commit and compare it against that one.

cc @kirillzyusko can you comment here so it can be assigned to you? Thanks!

cc @AndrewGable does this sound good to you?

Yes sounds great!

@kirillzyusko, are you going to take this one on? Can you comment here if so? thanks

Yeah, feel free to assign this to me 🙌

not overdue

I think we discussed this internally with Hanno, but I'll post here as well.
We think that we should postpone this PR, because current e2e tests are not very stable (i. e. sometimes they pass, sometimes not) and having such unstable pipeline with assembling builds for each new commit may lead to uncaught regressions, i. e.:
A <- first commit in chain, e2e passed no regression has been detected
|
|
B <- commit that introduces a regression and e2e tests fails
|
|
C <- e2e tests pass again, but we compare with a build that introduced a regression and this regression was unnoticed

So I think we need to have a good e2e pipeline first and only then go ahead with this PR 👀

Sounds good, are you or someone else actively working on fixing the pipeline?

Sounds good, are you or someone else actively working on fixing the pipeline?

@mountiny current e2e pipeline slightly unstable, but we need to have gather logs/videos for all latest failures to detect what needs to be fixed first.
From what I saw - we have several major problems:

sometimes tests fail after 2-3 mins - looks like a job can not be started properly;
sometimes tests fail after 9-10 minutes - it means that something is wrong with first test;
sometimes third test fails;

I think we need to gather kind of analytics on what is the most frequent failure, gather logs for this failure and try to fix it. How does it sound for you?
I can prepare analytic based on latest failures (and attach links for all of them) but I need someone to help me to get logs + videos. Would you be able to help me? 👀

Provided some more logs in DM and also created an issue to give you and some other people from Margelo access to the device farm

@kirillzyusko how is this looking

@mountiny I prepared two PRs:

https://github.com/Expensify/App/pull/49649 (should fix a problem with failure after 8-10 minutes);
https://github.com/Expensify/App/pull/49925 (should fix random build failures).

The remaining problem will be AWS scheduling - my assumption is that we'll need to add retry mechanism to that step (I think we can try to use https://github.com/marketplace/actions/retry-action).
But overall with these 2 fixes tests should become pretty stable (we should have 1-2 failures per week, which I think is kind of acceptable).

Bumped the PRs

How is this looking? Can @chrispader help here? I read he has some spare cycles

@mountiny I will work on it 👀 Just will finish react-native-app-logs and will switch back to e2e tests stuff!

This was a follow up to improve the E2E test suite, I dont think we need a checklist in this case as Margelo keeps slowly improving the suite. No external review was done so no payment required either


Add choice widget

Added a Choice Button widget. I've tested the itemsFromPv and enabled/disabled functionality, as well as writing to PV and these all seem to work. I modelled this off the Phoebus version of the widget

Great, thanks Becky! I'll resolve those conflicts when I merge it in


Recursive type with List incorrectly thinks there is a type mismatch

 Environment data

Language Server version: 2022.2.0
OS and version: darwin arm64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: null
python.analysis.typeCheckingMode: off

In the example below, VS Code and Pylance flag a problem when there isn't one:
from typing import Iterable, List, Union

RecursiveType = Union[
    int,
    List["RecursiveType"],
]

def foo(x: RecursiveType) -> None:
    pass

z = [1, 2]
foo(z)   # <- z is underlined, but should not be

It says:
Argument of type "list[int]" cannot be assigned to parameter "x" of type "RecursiveType" in function "foo"
  Type "list[int]" cannot be assigned to type "RecursiveType"
    "list[int]" is incompatible with "int"
    TypeVar "_T@list" is invariant
      Type "int" cannot be assigned to type "RecursiveType"
        "int" is incompatible with "List[RecursiveType]"Pylance[reportGeneralTypeIssues]

If I explicitly specify the type for z, however, Pylance thinks it's OK:
z: RecursiveType = [1, 2]
foo(z)   # OK

If I use Iterable instead of List, Pylance also thinks it's OK:
RecursiveType2 = Union[
    int,
    Iterable["RecursiveType2"],
]

def bar(x: RecursiveType2) -> None:
    pass

z = [1, 2]
bar(z)  # OK

Pyright is correct to report an error in this case. The type parameter for List is invariant, so List[int] is not compatible with List[RecursiveType].
You can fix this in a couple of ways:
Switch to a Sequence, where the type parameter is covariant.
RecursiveType = Union[int, Sequence["RecursiveType"]]

Provide a type annotation for z to specify that [1, 2] should be inferred as RecursiveType rather than List[int].
z: RecursiveType = [1, 2]

Ah, after reading up on covariant types, it does make sense to me now.
Sequence isn't exactly right for my use case, since lists, tuples, and ranges (and a few others) count as Sequences, but I only want my functions to accept lists or tuples. But I suppose Sequence is close enough for practical purposes.


error on start AMAVIS & DOVECOT

Hi;
hopefully It's a mistake from my side and I don't see it but since few hours now I try to start your mailserver and I always result with something similar
EVEN IF :

I run docker-compose as root
I spefify the VMAILUID=1024 & VMAILGID=1024

basicly AMAVIS & DOVECOT are unable to start
those logs are from mailserver
> 2017-05-30 10:29:03,927 INFO exited: amavisd (exit status 255; not expected)
> 2017-05-30 10:29:04,932 INFO spawned: 'amavisd' with pid 1355
> Tue May 30 10:29:05 2017 grossd status summary (begin, end, trust, match, greylist, block):<PHONE_NUMBER>,<PHONE_NUMBER>, 0, 0, 0, 0
> Tue May 30 10:29:05 2017 grossd processing average delay (begin, end, trust[ms], match[ms], greylist[ms], block[ms]):<PHONE_NUMBER>,<PHONE_NUMBER>, 0.000, 0.000, 0.000, 0.000
> Tue May 30 10:29:05 2017 grossd processing max delay (begin, end, trust[ms], match[ms], greylist[ms], block[ms]):<PHONE_NUMBER>,<PHONE_NUMBER>, 0.000, 0.000, 0.000, 0.000
> 2017-05-30 10:29:06,082 INFO success: amavisd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
> 2017-05-30 10:29:06,101 INFO exited: amavisd (exit status 255; not expected)
> 2017-05-30 10:29:07,106 INFO spawned: 'amavisd' with pid 1362
> 2017-05-30 10:29:08,109 INFO success: amavisd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
> 2017-05-30 10:29:08,322 INFO exited: amavisd (exit status 255; not expected)
> 2017-05-30 10:29:09,327 INFO spawned: 'amavisd' with pid 1369
> 2017-05-30 10:29:10,331 INFO success: amavisd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
> 2017-05-30 10:29:10,488 INFO exited: amavisd (exit status 255; not expected)
> 201 [...] Ad vitam æternam

> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> /usr/local/bin/startup: line 160: echo: write error: Operation not supported
> /usr/local/bin/startup: line 168: echo: write error: Operation not supported
> mv: cannot move '/etc/cron.d/spamassassin' to '/etc/cron.d/spamassassin.tpl': Operation not supported
> Error: spamassassin.tpl
> mv: cannot move '/etc/postfix/virtual' to '/etc/postfix/virtual.tpl': Operation not supported
> Error: virtual.tpl
> mv: cannot move '/etc/postfix/header_checks' to '/etc/postfix/header_checks.tpl': Operation not supported
> Error: header_checks.tpl
> mv: cannot move '/etc/postfix/sql/sender-login-maps.cf' to '/etc/postfix/sql/sender-login-maps.cf.tpl': Operation not supported
> Error: sender-login-maps.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-mailbox-domains.cf' to '/etc/postfix/sql/virtual-mailbox-domains.cf.tpl': Operation not supported
> Error: virtual-mailbox-domains.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-mailbox-maps.cf' to '/etc/postfix/sql/virtual-mailbox-maps.cf.tpl': Operation not supported
> Error: virtual-mailbox-maps.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-alias-domain-mailbox-maps.cf' to '/etc/postfix/sql/virtual-alias-domain-mailbox-maps.cf.tpl': Operation not supported
> Error: virtual-alias-domain-mailbox-maps.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-alias-maps.cf' to '/etc/postfix/sql/virtual-alias-maps.cf.tpl': Operation not supported
> Error: virtual-alias-maps.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-alias-domain-maps.cf' to '/etc/postfix/sql/virtual-alias-domain-maps.cf.tpl': Operation not supported
> Error: virtual-alias-domain-maps.cf.tpl
> mv: cannot move '/etc/postfix/sql/virtual-alias-domain-catchall-maps.cf' to '/etc/postfix/sql/virtual-alias-domain-catchall-maps.cf.tpl': Operation not supported
> Error: virtual-alias-domain-catchall-maps.cf.tpl
> mv: cannot move '/etc/postfixadmin/fetchmail.conf' to '/etc/postfixadmin/fetchmail.conf.tpl': Operation not supported
> Error: fetchmail.conf.tpl
> mv: cannot move '/etc/dovecot/dovecot-sql.conf.ext' to '/etc/dovecot/dovecot-sql.conf.ext.tpl': Operation not supported
> Error: dovecot-sql.conf.ext.tpl
> mv: cannot move '/etc/dovecot/dovecot-dict-sql.conf.ext' to '/etc/dovecot/dovecot-dict-sql.conf.ext.tpl': Operation not supported
> Error: dovecot-dict-sql.conf.ext.tpl
> mv: cannot move '/etc/dovecot/conf.d/10-mail.conf' to '/etc/dovecot/conf.d/10-mail.conf.tpl': Operation not supported
> Error: 10-mail.conf.tpl
> mv: cannot move '/etc/dovecot/conf.d/10-ssl.conf' to '/etc/dovecot/conf.d/10-ssl.conf.tpl': Operation not supported
> Error: 10-ssl.conf.tpl
> mv: cannot move '/etc/dovecot/conf.d/15-lda.conf' to '/etc/dovecot/conf.d/15-lda.conf.tpl': Operation not supported
> Error: 15-lda.conf.tpl
> mv: cannot move '/etc/dovecot/conf.d/20-lmtp.conf' to '/etc/dovecot/conf.d/20-lmtp.conf.tpl': Operation not supported
> Error: 20-lmtp.conf.tpl
> mv: cannot move '/etc/opendkim/opendkim.conf' to '/etc/opendkim/opendkim.conf.tpl': Operation not supported
> Error: opendkim.conf.tpl
> mv: cannot move '/etc/opendmarc/opendmarc.conf' to '/etc/opendmarc/opendmarc.conf.tpl': Operation not supported
> Error: opendmarc.conf.tpl
> mv: cannot move '/etc/amavis/conf.d/05-node_id' to '/etc/amavis/conf.d/05-node_id.tpl': Operation not supported
> Error: 05-node_id.tpl
> mv: cannot move '/etc/amavis/conf.d/20-debian_defaults' to '/etc/amavis/conf.d/20-debian_defaults.tpl': Operation not supported
> Error: 20-debian_defaults.tpl
> mv: cannot move '/etc/amavis/conf.d/50-user' to '/etc/amavis/conf.d/50-user.tpl': Operation not supported
> Error: 50-user.tpl
> mv: cannot move '/etc/cron.d/fetchmail' to '/etc/cron.d/fetchmail.tpl': Operation not supported
> Error: fetchmail.tpl
> mv: cannot move '/etc/mailname' to '/etc/mailname.tpl': Operation not supported
> Error: mailname.tpl
> mv: cannot move '/usr/local/bin/quota-warning' to '/usr/local/bin/quota-warning.tpl': Operation not supported
> Error: quota-warning.tpl
> useradd: failed to reset the faillog entry of UID 1024: Operation not supported
> useradd: failed to reset the lastlog entry of UID 1024: Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-auth.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-mail.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-ssl.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/15-lda.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/15-mailboxes.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/20-imap.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/20-lmtp.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/20-pop3.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/90-quota.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/90-sieve.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-sql.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-director.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-logging.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/10-tcpwrapper.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/20-managesieve.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/90-acl.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/90-plugin.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/90-sieve-extprograms.conf': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-checkpassword.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-deny.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-dict.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-master.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-passwdfile.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-static.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-system.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/conf.d/auth-vpopmail.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/dovecot-dict-sql.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/dovecot-sql.conf.ext': Operation not supported
> chmod: changing permissions of '/etc/dovecot/README': Operation not supported
> chmod: changing permissions of '/etc/dovecot/dovecot-dict-auth.conf.ext': Operation not supported
> chmod: changing permissions of '/usr/local/bin/amavisd': Operation not supported
> chmod: changing permissions of '/usr/local/bin/clamav': Operation not supported
> chmod: changing permissions of '/usr/local/bin/envtpl': Operation not supported
> chmod: changing permissions of '/usr/local/bin/fetchmail.pl': Operation not supported
> chmod: changing permissions of '/usr/local/bin/gross': Operation not supported
> chmod: changing permissions of '/usr/local/bin/postfix': Operation not supported
> chmod: changing permissions of '/usr/local/bin/postgrey': Operation not supported
> chmod: changing permissions of '/usr/local/bin/quota-warning': Operation not supported
> chmod: changing permissions of '/usr/local/bin/startup': Operation not supported
> doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-mail.conf line 12: Invalid number {{ VMAILUID }}: Not a valid number
> Unlinking stale socket /dev/shm/supervisor.sock
>

Post the result of this command docker info please.

Containers: 19
Running: 19
Paused: 0
Stopped: 0
Images: 15
Server Version: 17.05.0-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: xfs
Dirs: 117
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.10.8-docker-1
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.857GiB
Name: bast.otg.space
ID: OPTK:RYDL:6RAX:7UBG:S4DW:OJC4:OKRX:ZYDM:FZXU:NDF7:RRHD:BHPE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false

I think it's a host level problem, maybe try to reboot your server.  Have you updated your kernel recently ? Maybe some changes are in pending state.

thank for your try;
I try another host and keep you in touch ;)

It works well on my Debian host
Sorry for this !! :)


Support for SQL_BLOB ODBC SQL type -98

Please first make sure you have looked at:

Documentation: https://github.com/mkleehammer/pyodbc/wiki
Other issues

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: 3.11.6
pyodbc: 5.0.1
OS: Linux
DB: Db2
driver: IBM Db2 ODBC

Issue
Howdy :wave:,
Do you have any plans to support the ODBC type SQL_BLOB? I'm currently getting the error message from Db2 results.
'ODBC SQL type -98 is not yet supported.  column-index=5  type=-98', 'HY106'

An example query to replicate the issue is:
SELECT * FROM SYSIBM.SYSTABLES

If not, I can try and poke around the IBM Db2 python driver to see if I can adapt that code to pyodbc.
Cheers

You can add an output converter function to handle DB-specific types: https://github.com/mkleehammer/pyodbc/wiki/Using-an-Output-Converter-function

Beautiful. Thank you for pointer @v-chojas


[Fastlane] Display error upon bundler failure to run

In a fresh react-native v0.43 project I get the following error when running fastlane-setup
? Please confirm the project name gen
? Commit keystore files? No
identical fastlane/Appfile
identical fastlane/Fastfile
identical environment/index.js
identical Gemfile
identical android/app/src/main/res/values/strings.xml
 conflict .gitignore
? Overwrite .gitignore? overwrite this and all others
    force .gitignore
    force android/app/build.gradle
    force ios/gen.xcodeproj/project.pbxproj
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: spawn bundle ENOENT
    at exports._errnoException (util.js:1033:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Which OS and Node version are you using?
Do you have more data regarding the stasktrace?

I'm on MACos Sierra (v 10.12.4) and using node v7.7.2.
I created a repo with my code but it's really nothing more than a fresh react-native project with this library added.
I tried get some more data out of the stacktrace using node --inspect but it didn't give my any more information.

Okay I need to read the docs better, turns out I was just missing Bundler. After installing the setup worked without any problems.

Nice! Is there any way we could have made it clearer that you need to have bundler installed? Do you think we need to make it clear in the terminal?
Anyway, I'm opening a new issue to add error description when the generator fails to run a terminal command.

For me I read the requirements in the readme and saw ruby and thought, "check I got that" and didn't bother to read the rest. Maybe add a separate check for bundler with the install command gem install bundler to the requirements?
Other than that an error description or a check to see if bundler is installed would also be very helpful of course.

#100

#100

Doubly fixed in latest version ;)


[Task]: Extract ExampleCache.isSelectorOpened

What needs to happen?
ExampleCache is the class to store examples as they are fetched from the network.
For historical reasons, it also contains the state of the example dropdown in isSelectorOpened flag.
It should be extracted to somewhere else and to be unified with other dropdowns.
Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.remove-labels 'awaiting triage'


Problem: historical data loss after node restart

Problem: historical data loss after node restart
Expected result: it is hoped that the data after the time when the node is first built can be retained, and the previous data will not be lost even if it is restarted
How to configure nodes to achieve this purpose？
The following is our current node setup configuration, but there is this problem at present

rippled.cfg

[server]
port_rpc_admin_local
port_peer
port_ws_admin_local

[port_rpc_admin_local]
port = 5005
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = http

[port_peer]
port = 51235
ip = <IP_ADDRESS>
#ip = ::
protocol = peer

[port_ws_admin_local]
port = 6006
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = ws

[node_size]
medium

[node_db]
type=NuDB
path=/var/lib/rippled/db/nudb
online_delete=81920000
advisory_delete=0

[database_path]
/var/lib/rippled/db

[debug_logfile]
/var/log/rippled/debug.log

[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org

[validators_file]
validators.txt

[rpc_startup]
{ "command": "log_level", "severity": "warning" }

[ssl_verify]
1

rippled does not instantly know what data is available on startup. It basically has to backfill in the same way it would if the data was not there, except that it is much faster, because it's available locally. Additionally, it will first work to retrieve any ledgers that were missed while the node was down before it finds those ledgers locally. With an online_delete value that large, it will take a significant amount of time to do that work, but it will eventually get there.
tl;dr Give your node more time to "discover" that it has those ledgers after all.

@ximinez Thank you very much for being able to answer my question.
I don't understand it very well. When I start rippled for the first time, I can get the data after the height "70144088", but after restarting it once, I can only access the data after the height "72378219". is this normal?
Shouldn't the data after the "70144088" height be written to the hard disk from the first boot? Why can't the block be accessed after restarting?

How are you trying to access the ledger? There are some ways of requesting the info which will go directly to the database, and others which require rippled to have processed back to the ledger.
 Immediately after starting, I ran the same commands:
$ rippled -q json ledger '{"ledger_index": 73469653, "transactions": true }'
{
   "result" : {
      "error" : "noNetwork",
      "error_code" : 17,
      "error_message" : "InsufficientNetworkMode",
      "request" : {
         "api_version" : 1,
         "command" : "ledger",
         "ledger_index" : 73469653,
         "method" : "ledger",
         "transactions" : true
      },
      "status" : "error"
   }
}
$ rippled -q json ledger '{"ledger_hash": "9DE6ECF7529B4DDB517A6D69D8994CE9B15C9DB1434E0203626180814A7E6873", "transactions": true }'
{
   "result" : {
      "ledger" : {
         "accepted" : true,
         "account_hash" : "1D43AFDF9A15FBC0BD589240F0487E89425ABA81E700B9505EF73FDFCC1FA552",
         "close_flags" : 0,
         "close_time" : 712945901,
         "close_time_human" : "2022-Aug-04 16:31:41.000000000 UTC",
         "close_time_resolution" : 10,
         "closed" : true,
         "hash" : "9DE6ECF7529B4DDB517A6D69D8994CE9B15C9DB1434E0203626180814A7E6873",
         "ledger_hash" : "9DE6ECF7529B4DDB517A6D69D8994CE9B15C9DB1434E0203626180814A7E6873",
         "ledger_index" : "73469653",
         "parent_close_time" : 712945900,
         "parent_hash" : "F1698F1D6B6049B91F7FA9E2923C2DE9B92553373BF3D9630322A2DCAAF3B792",
         "seqNum" : "73469653",
         "totalCoins" : "99989365827414354",
         "total_coins" : "99989365827414354",
         "transaction_hash" : "95C1BBCC30D58D089225BDC09A3CA1EC159C42DAE3620870C03D0F443CF5DAEE",
         "transactions" : [
            "0810CDF6AFE619DDFED1F272349C580B04D78446375AF587FD6169697DFFBE4B",
            "165E9838B3F93F7B8ABA5E9AD4A0916025262E54990CEC44169E9A5D14D2A284",
            "18A48FB68E35AF1AC6F6AD59DA8FDB2563538A8A724F02A1FAC655B91460C31A",
            "21D7B7DC1799F01BA9E7A7D205E2DCCB3FCDC3F8D2F43782900050919F87BBB0",
            "2E731D77A36CD7245680B4694C4C982FF5983000B0331A5A0731B65BD59B17B9",
            "48D834AE692F0F9B80E282E3933BD00BE9FFE9425D58D5087DB65AEABC39877B",
            "540237183D2FBB34AD42E7298975F135C639D619AAA78FAC7B4A560EFD77F2D4",
            "55C90CC7B321BD0855A2E431BAF4D03FBC5AC88E073BB35B5265898F4E5BAA28",
            "5D98D0CB6FAB57D5C954B7F8309F4849D6F03ED49C20D18DD71A564326DB0D2B",
            "6ADE854F15B5D3A9F981FBC42FD1C1F361585D48B69E2CA9A634B97945CB9480",
            "6BFDFF169479B135C14A07DD8DA7E59DA93FEB4637BDD54E6A147575BE64D389",
            "6FC2565E80200F5F1D700CF6787326FA5F0F02C4D9C82D33829F92E559D92E24",
            "7789B664C8BAC4BD952FD6CE22264F7AEB3DA5317D24BBDE0B27A652A5D2CE2F",
            "79E120DCACE148F38DA161F2B8B6F02CD27F51D8052B301B768EACDE29B10220",
            "813B00A348EADE502C86B0FB60E4AD66671997518CDCF0118594A31BDD0B89F2",
            "855DE537DA4D28950563544D2F94019B1BDE0EFD3F49B3A075F01456A386B372",
            "870F603273F8E7BEC54624C72124CD4931C4383807BC8810723F6E65BF76F55C",
            "8DEE15F70662D59779FBA88D790F417D465323452A2E9AB483CF9E6ECBB6BD3A",
            "9B4EB7C06F7D9D7B261DD1685EA9AD97ED6228B93EFEE1368D927C17FDF8CCF2",
            "A67AB4F51EA2086F048A3299CF519DEBD08A1CC35969AD34D572EDF78D9664A8",
            "ABF81A03F2BCBC680A8204A9E6C8367EAB5C4831475E2081FFA656D57EADAC61",
            "B6DFAE6B40BDBC10D9805C4CC5867D804C8AA997B96445E16834D31017E3BFB6",
            "C6BC6D6FB2F77F03F178200D483FD20CE1A7FDE87E97629040CA953782AC002D",
            "D2FCDC13529A8586B0313F78E6499DCA5D946236007811139170DF7AED866870",
            "D8131A724817F4FDE969B52A924B44E984D94B0E2433A7AFBE056203F1BE8F41",
            "DBBF033763C839A026A1C7D6AAEFD88DDA72D7DD5617D40D2B5CACEDD2212156",
            "DE1A53940910DD8D69DEA1B1713E872A1CC16E02883187CA083FB3750474AA23",
            "E3750EE40504D7BF7FDDB9CEE16C9688590D2EE6F8FA01CC7A712C06F799727D",
            "EAA2DAED39BA5E506F99F5B446ECEF721684BA48E0783FFBD1A3EE748F8AC0CE",
            "F021CC33512D68ABD8AAE0A4C1AF1BEAE0D0637B11B32FC76691BD346CF34D4C",
            "F0FF32B7A58AF5AE394B893AB07280997138A4C7C1D298C114D7B9FADF2CB988",
            "F7689F4868E97B0B775AFF3939F7EBE0D5CFD950649829EF4C2019115381A603"
         ]
      },
      "ledger_hash" : "9DE6ECF7529B4DDB517A6D69D8994CE9B15C9DB1434E0203626180814A7E6873",
      "ledger_index" : 73469653,
      "status" : "success",
      "validated" : false
   }
}
$ rippled -q tx EAA2DAED39BA5E506F99F5B446ECEF721684BA48E0783FFBD1A3EE748F8AC0CE
{
   "result" : {
      "error" : "noNetwork",
      "error_code" : 17,
      "error_message" : "Not synced to the network.",
      "request" : {
         "api_version" : 1,
         "command" : "tx",
         "transaction" : "EAA2DAED39BA5E506F99F5B446ECEF721684BA48E0783FFBD1A3EE748F8AC0CE"
      },
      "status" : "error"
   }
}

As you can see, looking for the ledger by index doesn't work because the node isn't synced, but looking up by hash finds the ledger on disk, but doesn't yet know that it's validated ("validated" : false).
Unfortunately, my node keeps very little history, so once it synced, it very quickly finished loading all those old ledgers, but you can repeat the experiment on your node, since I'm not entirely sure what the behavior will be.

@ximinez Hi,ximinez
First of all, I will describe what I understand about what you said above to avoid misunderstanding.

That is to say, when the node is just started, it can only query the most recent block. Over time, the node will check forward the computation blocks. When the node verification is completed, the block from a long time ago can be queried .

Below is my method of querying blocks through nodes. As shown in the figure

question:

Our node was restarted two days ago, and data after the height "70144088" can be queried before the restart. After restarting, you can query the data after the height "72378219". Two days later, which is now, I still can only query the data after the height "72378219". There is no sign of forward synchronization, is it because we have not configured it correctly?
We found another case, when we removed these two configurations (online_delete=81920000 AND advisory_delete=0), after restarting the node, the node will indeed verify and synchronize the previous blocks. But when we add these two configurations, the node will not verify and synchronize previous blocks. I wonder if this is normal? And if we remove these two configs, will the node keep checking sync blocks forward until the height is "0" or will it only sync forward to the height "70144088" (the height when the node was first built)?

I'm not sure why your node is not processing those older ledgers to be aware of them, but I'd bet they're still there.

The hash of ledger 70144088 is<PHONE_NUMBER>AC630A5B14161A214002CEA89434E2C1EFBF001F0D90F55F2F3C36, so try something like curl [...] '{"method", "ledger", "params": [{"ledger_hash": "0566043611AC630A5B14161A214002CEA89434E2C1EFBF001F0D90F55F2F3C36"}]'.
The hash of ledger 72378218 is D6E0E6378F93CAAC396D44C1ABB52F0DF3B287B284B237F702B4B2996720CE80 so try something like curl [...] '{"method", "ledger", "params": [{"ledger_hash": "D6E0E6378F93CAAC396D44C1ABB52F0DF3B287B284B237F702B4B2996720CE80"}]'.
I expect that it will return unvalidated data for both ledgers, which indicates the data is on disk, but rippled is not looking back for it. That could be for several reasons, which I'm not going to go in to right now, because I think most of them can be worked around by increasing your [ledger_history] value to be at least large enough to reach back to the ledgers you're trying to access - that would be on the order of 3500000. One significant exception is if your node does not have sufficient resources or connectivity to stay in sync with the network and backfill ledgers. Rippled will always prioritize staying up to date over finding or acquiring historical data.

More generally, though, your online_delete setting is 81,920,000, which is more than the total number of historical ledgers: 73,494,876. The way that online delete works is that nothing will be deleted until you have at least double the number of ledgers as the setting. That will probably mean you're covered for the next decade plus. You're effectively running a full history node, and it may make more sense to configure it explicitly to do that. Instructions are at: https://xrpl.org/configure-full-history.html

Hi ximinez 。
According to your statement, I tried to request, but I can't get the block data.

This means that there is no previous data after the node is restarted.  This is strange, but we do not intend to dwell on this issue.  Prepare to rebuild the new node.
We suspect that there is a problem with the directory mounted on the "docker container", which causes data loss after restart. I hope you can tell me where the data directory of the node is? Thank you.
The following is our current node building method. If there is any problem, please help me correct it， I'm very grateful. (we hope that the node can have data since the construction, but we don't need previous data.)
docker-compose.yml
version: "3"

networks:
  xrp-mainnet-01:
    ipam:
      driver: default
      config:
        - subnet: <IP_ADDRESS>/24

services:
  xrp-mainnet-01:
    container_name: wallet-xrp-mainnet-01
    hostname: wallet-xrp-mainnet-01
    image: image-wallet-xrp-daemon
    command: "/opt/ripple/bin/rippled --conf /etc/opt/ripple/rippled.cfg"
    ports:
      - "61076:5005"
    build:
      context: ./daemon
    environment:
    - TZ=Asia/Shanghai
    volumes:
      - /data/xrp-mainnet-01:/var/lib/rippled/
    networks:
      - xrp-mainnet-01
    tty: true
    mem_limit: 64g
    restart: always

Dockerfile
FROM ubuntu:20.04

RUN cd /root \
        && apt-get update && apt-get -y install apt-transport-https ca-certificates wget gnupg \
    && wget -q -O - "https://repos.ripple.com/repos/api/gpg/key/public" | apt-key add - \
    && echo "deb https://repos.ripple.com/repos/rippled-deb bionic stable" | tee -a /etc/apt/sources.list.d/ripple.list \
    && apt -y update \
    && apt -y install rippled \
    && apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

COPY rippled.cfg /etc/opt/ripple/rippled.cfg

rippled.cfg
[server]
port_rpc_admin_local
port_peer
port_ws_admin_local

[port_rpc_admin_local]
port = 5005
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = http

[port_peer]
port = 51235
ip = <IP_ADDRESS>
#ip = ::
protocol = peer

[port_ws_admin_local]
port = 6006
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = ws

[node_size]
medium

[node_db]
type=NuDB
path=/var/lib/rippled/db/nudb
online_delete=20480000
advisory_delete=0

[database_path]
/var/lib/rippled/db

[debug_logfile]
/var/log/rippled/debug.log

[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org

[validators_file]
validators.txt

[rpc_startup]
{ "command": "log_level", "severity": "warning" }

[ssl_verify]
1

I'm not a Docker expert, and I can't really comment on anything related to that. You're data is stored based on the location you specify in the ripple.cfg file, in this case:
[node_db]
path=/var/lib/rippled/db/nudb

[database_path]
/var/lib/rippled/db

[debug_logfile]
/var/log/rippled/debug.log

Probably relative to the Docker container.

OK, thank you very much.


Headless mode

The reliance on VSCode or IntelliJ is little problematic. In my latest scenario, I actually generate the XRM files but I still need to have vscode open for the src-gen to be updated
Ideally, I would not even commit that dir and generate from sources on the fly (such as on CI)
Maybe this feature would be the tipping point moving us towards Langium?

Re https://github.com/eclipse-langium/langium/discussions/212


Ejected theme folder breaking vscode TS intellisense

"react": "16.8.6",
"react-native": "0.60.4",
"native-base": "^2.13.4",
No Expo
After ejecting the theme as mentioned in this link https://docs.nativebase.io/Customize.html#theaming-nb-headref
Following code is breaking VSCode Typescript intellisense.
import getTheme from '../../theme/components';

const theme = getTheme();

@saggiyogesh
I also faced the same issue. Vscode intellisense just stopped working and I know the culprit is native base as itwas the last plugin i added. It  was very very frustrating.
The solution I found is that, you need to exclude the ejected native base folder 'native-base-theme' from VSCode intellisense by adding it in jsconfig.json file. Also close all the files and restart VSCode.
Example:
{     "compilerOptions": {         "target": "ES6",         "module": "commonjs",         "baseUrl": ".",         "paths": {         }     },     "exclude": [         "node_modules",         "native-base-theme"     ] }
You can find the method here in the  official documentation
Happy Coding

@aneesh2693 Tried already what you've mentioned. I'm developing in TS.
What happens after opening the file which is importing the theme/components, TS IntelliSense and every other VScode smart features stop working.

@saggiyogesh Unfortunately I was facing this issue again. So the best I did right now is that define the style provider in the project's main index.js file and forget about it. Just don't open that file. My VScode and CPU is stable now.
Try this thing.

@aneesh2693
Did this https://github.com/GeekyAnts/NativeBase/issues/2849#issuecomment-520047638
So now no more calculations by calling getTheme, as json file will get cached in require cache.

Any word on an official fix coming for this?
Having to do a separate file with theme vars that I can never open or my IDE blows up is a pretty bad solution.

Got the same problem with IntelliJ Webstorm: the typescript compiler (run through 'yarn tic') won't return and it seems it's stuck in a loop.
Excluding the native-base-theme directory and not importing/referencing it from a compiled file makes it work again, but is not ideal...

Hello @saggiyogesh  .vscode/settings.json
and add this setting
"typescript.disableAutomaticTypeAcquisition": true
Your issue will be fixed
Cheers
Happy Coding
You are the boss!

Cool, But now moved to other options like react-native-elements due to its small size.

A quick fix for me was to just change the StyleProvider snippet to:
<StyleProvider style={getTheme(material as any)}>
Hope that helps.

Hi @saggiyogesh , please provide more information regarding the issue like, steps to reproduce and its outcome.


Add handler for opn function call

Hi there,
Thanks for your work on this project, it's been really great to get up and going with a really neat looking set of docs!
Came across an unhandled exception when running the app inside docker for the first time, I was running npm start which includes the -l flag for arapaho, which won't work in the container I'm running.
docs             | > node arapaho -l
docs             |
docs             | Arapaho server listening at http://:::4567
docs             | Launching...
docs             | (node:112) UnhandledPromiseRejectionWarning: Error: Exited with code 3
docs             |     at ChildProcess.<anonymous> (/app/nankai/shins/node_modules/opn/index.js:84:13)
docs             |     at Object.onceWrapper (events.js:300:26)
docs             |     at ChildProcess.emit (events.js:210:5)
docs             |     at maybeClose (internal/child_process.js:1021:16)
docs             |     at Socket.<anonymous> (internal/child_process.js:430:11)
docs             |     at Socket.emit (events.js:210:5)
docs             |     at Pipe.<anonymous> (net.js:659:12)
docs             | (node:112) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
docs             | (node:112) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It looks like the convention across the app is try/catch, however that didn't work with the opn function call, so I used the .catch syntax instead.

Thanks for the detailed description and PR!


Support FP8 params updating for NVIDIA Hopper GPUs

In this PR, we support configuring FP8 GEMMs and updating the FP8 params. This PR depends on the praxis PR, which introduces the FP8 GEMMs to the praxis layers. Users can simply set the USE_FP8 = True to turn on the FP8 layers (i.e. the QKV projection, attention output projection, and feedforward layers) in the transformer layer.
cc. @pjannaty @reedwm

cc @lew

Closing as this is resubmitted in another PRs.


Cannot deserialize any file router JSON

Describe the bug
Latest alpha cannot deserialize views from JSON. This has been introduced by https://github.com/vaadin/hilla/pull/2315.
At https://github.com/vaadin/hilla/blob/a7be7e3b5c8dcf2a4a8a94473690b20e1b70c162/packages/java/endpoint/src/main/java/com/vaadin/hilla/route/ClientRouteRegistry.java#L162, it tries to parse a list of routes, but the root node is single route object, not an array. Thus, it throws:
com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `java.util.ArrayList<com.vaadin.hilla.route.records.ClientViewConfig>` from Object value (token `JsonToken.START_OBJECT`)

Expected-behavior
No response
Reproduction
Start any project, mine has an index, a layout, and two other views, which gives this JSON:
{
    "route": "",
    "params": {},
    "title": "Main Layout",
    "children": [
        {
            "route": "",
            "menu": {
                "order": 0,
                "icon": "line-awesome/svg/globe-solid.svg"
            },
            "params": {},
            "title": "Hello World"
        },
        {
            "route": "about",
            "menu": {
                "order": 1,
                "icon": "line-awesome/svg/file.svg"
            },
            "loginRequired": true,
            "params": {},
            "title": "About"
        },
        {
            "route": "login",
            "menu": {
                "exclude": true
            },
            "params": {},
            "title": "Login"
        }
    ]
}

System Info
Vaadin 24.4.0.alpha25

Caused (again) by an old package version


ID-2129: Support contextual image names

We have image names that include a "namespace", like event-statistikk/stat-ingester and event-statistikk/brukeradmin-backend.
The image name contains a slash that is interpreted as a directory-separator in the anchore/sbom-action when specified as the artifact-name: https://github.com/felleslosninger/brukeradmin-backend/actions/runs/3297077884/jobs/5437472307#step:11:198

I see, but maybe we then need an input param for name or filter out slashes, preferably the last since my long term hope is to publish this to a SBOM server so we easily can search for applications containing a given dependacy/vunerability. Then we need to include the name of the application or repo in the name as well. E.g. replace slash with underscore or something would then be good.

https://digdir.atlassian.net/browse/ID-2149 created.


Play random songs from YouTube

Fixes #11, YouTube auto generated Lists as autocomplete option added

User will get a list of YouTube generated playlists when using the /play command without entering anything


Schema validation error when creating composite custom action

What happened?
When creating a composite custom action, if I set runs.using to composite then trying to set runs.steps[*]. I have a schema validation error saying that runs.main or  runs.image should be set. Which is not true regarding Github documentation
How can we reproduce the issue?
Steps to reproduce the behavior:

Create an action.yaml file in .github/actions folder
Fill the name, description properties
create a runs property with runs.using set to 'composite'
Try to create a steps property

Relevant log output

Schema validation: One of the following property sets is required: property 'main' or property 'image'

Operating System

macos Sonoma 14.5

Plugin Version

3.2.1

IDE Name and Version

Webstorm 2024.1.5

Expected behavior
I could be able to not set runs.main or  runs.image
Screenshots

In fact, there was some error in my steps property. It's working fine after fixing them. No longer an issue


Category
DEV
Inspiration
Linux
Description
I would like to have the Linux logo (Tux) chilling around inside the repository.
Are there any possible issues with the idea
No response
TODO's

[X] The component hasn't been suggested / isn't already implemented yet.
[X] The title is clear and descriptive.
[X] The component is properly described.
[X] The Component has good tags.

Code of Conduct

[X] I agree to follow the Code of Conduct

Feedback on Process
No response

Could u give me an example or describe it clearly. I want to help u

@hectorDB01 What is not clear or where can I help you?
An exampel would be this: link


Slightly improve copy around personal access token in the options

Closes https://github.com/sindresorhus/refined-github/issues/2679
Closes https://github.com/sindresorhus/refined-github/issues/2693
Please review and suggest further copy or explanation you think it's needed here.

For the forms I create, I always assume all fields are required and put an (optional) remark behind the ones that are optional.

Indeed, but I can't come up with anything better than the current wording: "Not required but ..."
Perhaps:
Personal token (optional)
[Some features]() may not work without it. [Generate one]().

I like that last one ✔🤝


Task - Browse Nomenclature - redirect to valid autocomplete option

When I use the autocomplete search
   then I want to be redirected automatically to the valid version of the name I selected
   so I should be able to click a check box below the search that enables this functionality

[ ] Add input
[ ] Add attributes to JSON response if not there (valid_id)
[ ] Add client side handling to swap in the alternate id when applicable.

[ ] We've decided to make this a global preference as well -
[ ] global preference will set the default of the switches value, which can then be over-ridden in a param, switch will snap back to global preference value after the request


Future plans with this backend

Hello, I would have preferred to contact you directly @vasilcovsky but I couldn't find a way to do so. What are the future plans in supporting this backend? I've found multiple issues and missing functionality with it which I fixed locally. I see that this repo did not have much changes in the past, so I'd like to first figure out if it makes sense to create PR's against this repo or directly go with a fork?

Hi Alexander,
I don't have any plans for this backend but feel free to send PR.
Thanks,

Please see https://github.com/vasilcovsky/errbot-backend-botframework/pull/8, which contains the mentioned changes


Installation instructions not working

Issue 1:
sudo docker build -t buddycloud-stack
Errors out with:
docker: "build" requires 1 argument.
See 'docker build --help'.
Removing the -t works
Issue 2 :
sudo docker run   -i   --dns <IP_ADDRESS>   -v /srv/buddycloud-stack/logs:/var/log/buddycloud   -v /srv/buddycloud-stack/prosody:/var/lib/prosody   -v /srv/buddycloud-stack/postgresql:/var/lib/postgresql   -v /srv/buddycloud-stack/buddycloud-media-server:/var/lib/buddycloud-media-server   -P -p 80:80 -p 443:443 -p 5269:5269   -t buddycloud-stack
Fails with:
WARNING: Localhost DNS setting (--dns=<IP_ADDRESS>) may fail in containers.
Unable to find image 'buddycloud-stack:latest' locally

Hi Christopher - I'm about to update the install instructions to point people at the buddycloud-vm.  The docker approach is nice... but comes with a lot of caveats. Kinda a container format with rudimentary orchestration and... well it's a long story but I'm going to remove them in the next few days. If you can give me a day or so, I should be able to wrap up my work on https://github.com/buddycloud/buddycloud-vm and https://github.com/buddycloud/saltstack and then release that as an option.

I got the docker container buddycloud/complete-stack from the docker
site to run just fine, however after signing up for an account on the
local server the page stalled at:
What is supposed to happen after this?
On 08/28/2015 01:13 AM, Simon Tennant wrote:

Hi Christopher - I'm about to update the install instructions to point
people at the buddycloud-vm. The docker approach is nice... but comes
with a lot of caveats. Kinda a container format with rudimentary
orchestration and... well it's a long story but I'm going to remove
them in the next few days. If you can give me a day or so, I should be
able to wrap up my work on https://github.com/buddycloud/buddycloud-vm
and https://github.com/buddycloud/saltstack and then release that as
an option.
—
Reply to this email directly or view it on GitHub
https://github.com/buddycloud/dockerfiles/issues/6#issuecomment-135667946.

I'm not seeing the error message in your comment - can you repost please?


Remove redundant default value

It’s done in index.js.

I don't think it's redundant. If a library were using create-react-context but the top level project was using React > 16, then this line would allow the built-in React.createContext to be used and fall back to createReactContext.

Isn't that what this line does? (i.e. you're doing it twice)
https://github.com/jamiebuilds/create-react-context/blob/master/src/index.js#L5

@donavon aha! You are correct there. Sorry I missed that. Your change has my vote.... but I'm just an outsider and my vote doesn't count here.

Could we make a release for this? We are kind relied on the pure implementation.


Build docker image fails

When I tried to build the application using docker file I've got this error:
21.82 ><EMAIL_ADDRESS>build
21.82 > vite build
21.82
21.92 vite v4.5.3 building for production...
21.94 transforming...
21.98 ✓ 5 modules transformed.
21.98 ✓ built in 59ms
21.98 [vite]: Rollup failed to resolve import "@shopify/polaris" from "/app/frontend/utils/i18nUtils.js".
21.98 This is most likely unintended because it can break your application at runtime.
21.98 If you do want to externalize this module explicitly add it to
21.98 `build.rollupOptions.external`
21.99 error during build:
21.99 Error: [vite]: Rollup failed to resolve import "@shopify/polaris" from "/app/frontend/utils/i18nUtils.js".
21.99 This is most likely unintended because it can break your application at runtime.
21.99 If you do want to externalize this module explicitly add it to
21.99 `build.rollupOptions.external`
21.99     at viteWarn (file:///app/frontend/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:48216:27)
21.99     at onwarn (file:///app/frontend/node_modules/@vitejs/plugin-react/dist/index.mjs:250:9)
21.99     at onRollupWarning (file:///app/frontend/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:48245:9)
21.99     at onwarn (file:///app/frontend/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:47976:13)
21.99     at file:///app/frontend/node_modules/rollup/dist/es/shared/node-entry.js:24276:13
21.99     at Object.logger [as onLog] (file:///app/frontend/node_modules/rollup/dist/es/shared/node-entry.js:25950:9)
21.99     at ModuleLoader.handleInvalidResolvedId (file:///app/frontend/node_modules/rollup/dist/es/shared/node-entry.js:24862:26)
21.99     at file:///app/frontend/node_modules/rollup/dist/es/shared/node-entry.js:24822:26
------
Dockerfile:9
--------------------
   7 |     COPY web .
   8 |     RUN npm install
   9 | >>> RUN cd frontend && npm install && npm run build
  10 |     CMD ["npm", "run", "serve"]
  11 |

@shopify/shopify-app-express version:
Node version: v22.2.0
Operating system: MacOs

My docker file:
FROM node:18-alpine

ARG SHOPIFY_API_KEY
ENV SHOPIFY_API_KEY=$SHOPIFY_API_KEY
EXPOSE 8081
WORKDIR /app
COPY web .
RUN npm install
RUN cd frontend && npm install && npm run build
CMD ["npm", "run", "serve"]

The error you're encountering is related to Vite and Rollup failing to resolve the @shopify/polaris module during the build process. Here are a few steps you can take to troubleshoot and resolve this issue:
1- Check Dependency Installation: Ensure that @shopify/polaris is correctly listed in your package.json dependencies and is installed. You can do this by running:
in path web/frontend
npm install @shopify/polaris

2- Import Path: Verify that the import path in i18nUtils.js is correct. It should look something like this:
import {
  DEFAULT_LOCALE as DEFAULT_POLARIS_LOCALE,
  SUPPORTED_LOCALES as SUPPORTED_POLARIS_LOCALES,
} from "@shopify/polaris";

3- Externalize the Module: If you want to externalize the module as suggested by the error message, you can modify your Vite configuration. Add @shopify/polaris to the build.rollupOptions.external in your vite.config.js:
in your web/frontend/vite.config.js
// vite.config.js
export default {
  // ...
  build: {
    rollupOptions: {
      external: ['@shopify/polaris']
    }
  }
  // ...
};

By following these steps, you should be able to resolve the issue with the Vite build process in your Docker environment.

Hi there 👋
I was not able to reproduce this on my side. Could you provide a minimal repository for reproduction if you would like me to investigate further?


Add TemporaryMk1-3Pod IVA FIX for 1.4 from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of RocketInMyPocket, to add TemporaryMk1-3Pod IVA FIX for 1.4 to CKAN.
Mod details:
name = /mod/1729/TemporaryMk1-3Pod%20IVA%20FIX%20for%201.4
author = RocketInMyPocket
abstract = Fixes the broken IVA/Kerbal portrait windows on the new Mk1-3 Command Pod temporarily (It will be fixed by Squad in the 1.4.1 patch) by using the prior version of the Mk1-2 IVA. Requires Module Manager.
license = MIT
Homepage =
description = Fixes the broken IVA/Kerbal portrait windows on the new Mk1-3 Command Pod temporarily (It will be fixed by Squad in the 1.4.1 patch) by using the prior version of the Mk1-2 IVA. Requires Module Manager.
Please direct questions about this pull request to RocketInMyPocket.

No longer needed, 1.4.1 is out with the IVA.


try out arch's binutils

You are correct that we only need the linker. I have switched to arch's binutils which is what I use locally. I'm most hopeful that this build is usable by others too.
The other dependencies need to go together in a big change (after japaric/cortex-m-rtfm#87 is released). I see you're already moving -hal forwards?

I have successfully built a dfu using llvm-tools-preview and cargo-binutils, after upgrading to japaric/cortex-m-rtfm#87. I think that path is more worthwhile to follow than figuring out which arm-gcc works for other users.

Indeed. We're trying to get rid of all the (unstable) loose ends. So japaric came up with a way to provide pre-compiled assembler primitives which can be linked in directly with the available llvm linker.


quality issues on customized models

Hi @wyhuai ,
Happy new year of the rabbit.
I like your work very much. Recently, I tried it for medical image super-resolution and denoising but suffered from quality issues.
I trained a DDPM on my dataset and verified that it can generate very good images.

Then, I applied the DDNM for denoising and SR.
Original image:
128x128

Reconstructed image

The results still have large noise and obvious block effects. I have tried different sigma_y but it didn't improve the quality.
I modified the code https://github.com/wyhuai/DDNM/blob/main/hq_demo/main.py as follows
Any comments are highly appreciated. BTW, the question is not urgent. Enjoy your holidays first:)
"""
This is an DDNM implementation based on RePaint.
This implementation support arbitrary in/out image size.
At present, we only implemented SR and noisy SR tasks.
"""

import os
import argparse
import torch as th
import torch.nn.functional as F
import time
import conf_mgt
from utils import yamlread
from guided_diffusion import dist_util
import torchvision.transforms as transforms
from PIL import Image

# Workaround
try:
    import ctypes
    libgcc_s = ctypes.CDLL('libgcc_s.so.1')
except:
    pass

from guided_diffusion.script_util import (
    NUM_CLASSES,
    model_and_diffusion_defaults,
    classifier_defaults,
    add_dict_to_argparser,
    create_model_and_diffusion,
    create_classifier,
    select_args,
    args_to_dict,
)  # noqa: E402

def read_model_and_diffusion(args, model_path):
    """Reads the latest model from the given directory."""

    model, diffusion = create_model_and_diffusion(
        **args_to_dict(args, model_and_diffusion_defaults().keys()), conf=conf,
    )
    model.load_state_dict(dist_util.load_state_dict(model_path, map_location="cuda"))

    # if args.use_fp16:
    #     model.convert_to_fp16()
    model.eval()
    return model, diffusion

# def main(conf: conf_mgt.Default_Conf, args):

# if __name__ == "__main__":
parser = argparse.ArgumentParser()
parser.add_argument('--config', type=str, required=False, default="/home/jma/Documents/I2I/DDNM/hq_demo/confs/ct256.yml")
parser.add_argument('--deg', type=str, required=False, default="sr_averagepooling")
parser.add_argument('--sigma_y', type=float, required=False, default=1.5)
parser.add_argument('-i', "--save_path", type=str, required=False, default="demo15")

"""
SR scales should be divisible by 256, e.g., 2, 4, 8, 16 ...
"""
parser.add_argument('--scale', type=int, required=False, default=4)

"""
resize y to the same shape with the desired result
"""
parser.add_argument('--resize_y', default=True, action='store_true')
parser.add_argument('--path_y', type=str, required=False, default="data/datasets/ct128.png")
"""
no classifier guidance
"""
parser.add_argument('--class', type=int, required=False, default=323)
args = vars(parser.parse_args())

conf_arg = conf_mgt.conf_base.Default_Conf()
conf_arg.update(yamlread(args.get('config')))

def create_argparser():
    defaults = dict(
        image_size=256,
        batch_size=1,
        num_channels=64,
        num_res_blocks=3,
        num_heads=1,
        diffusion_steps=1000,
        noise_schedule='linear',
        lr=1e-4,
        clip_denoised=False,
        num_samples=1, # 10000
        use_ddim=True,
        # timestep_respacing='ddim250',
        model_path="",
    )
    ori = model_and_diffusion_defaults()
    # defaults.update(model_and_diffusion_defaults())
    ori.update(defaults)
    parser = argparse.ArgumentParser()
    add_dict_to_argparser(parser, ori)
    return parser

model_args = create_argparser().parse_args()

conf = conf_arg

print("Start", conf['name'])
print(f"{conf=}")
print(f"{args=}")

os.chdir('/home/jma/Documents/I2I/DDNM/hq_demo')
ct_model_path = './data/pretrained/ct256.pt'
device = dist_util.dev(conf.get('device'))
model, diffusion = read_model_and_diffusion(model_args, ct_model_path)
model.to(device)
if conf.use_fp16:
    model.convert_to_fp16()
model.eval()

show_progress = conf.show_progress

cond_fn = None

def model_fn(x, t, y=None, gt=None, **kwargs):
    assert y is not None
    return model(x, t, y if conf.class_cond else None, gt=gt)

print("sampling...")
all_images = []

dset = 'eval'

eval_name = conf.get_default_eval_name()

dl = conf.get_dataloader(dset=dset, dsName=eval_name)

for batch in iter(dl):

    for k in batch.keys():
        if isinstance(batch[k], th.Tensor):
            batch[k] = batch[k].to(device)

    model_kwargs = {}

    gt = Image.open(args.get("path_y")).convert('RGB')
    data_transform=transforms.Compose([
                        transforms.ToTensor(),
                        transforms.Normalize([0.5, 0.5, 0.5], [0.5, 0.5, 0.5])
                    ])
    #print("gt.size:",gt.size)
    gt = data_transform(gt).unsqueeze(0).to("cuda")
    model_kwargs["gt"] = gt
    model_kwargs['scale'] = args.get('scale')
    model_kwargs['deg'] = args.get('deg')
    model_kwargs['resize_y'] = args.get('resize_y')
    model_kwargs['sigma_y'] = args.get('sigma_y')
    model_kwargs['save_path'] = args.get('save_path')

    gt_keep_mask = batch.get('gt_keep_mask')
    if gt_keep_mask is not None:
        model_kwargs['gt_keep_mask'] = gt_keep_mask

    batch_size = model_kwargs["gt"].shape[0]

    if conf.cond_y is not None:
        classes = th.ones(batch_size, dtype=th.long, device=device)
        model_kwargs["y"] = classes * conf.cond_y
    else:
        classes = th.randint(
            low=0, high=NUM_CLASSES, size=(batch_size,), device=device
        )
        model_kwargs["y"] = classes

    classes = th.ones(batch_size, dtype=th.long, device=device)
    model_kwargs["y"] = classes * args.get("class")

    sample_fn = (
        diffusion.p_sample_loop if not conf.use_ddim else diffusion.ddim_sample_loop
    )

    result = sample_fn(
        model_fn,
        (batch_size, 3, conf.image_size, conf.image_size),
        clip_denoised=conf.clip_denoised,
        model_kwargs=model_kwargs,
        cond_fn=cond_fn,
        device=device,
        progress=show_progress,
        return_all=True,
        conf=conf
    )

print("sampling complete")

Thanks for your attention and greeting!
Your generative model is of size 256x256. In this test, your input is size 128x128, and you want to get a 512x512 result. However, your generative model may be trained on aligned full brain images of size 256x256. Hence it can not handle partial brain patches of size 256x256. To solve this out-of-domain problem, you may need to train a model with random cropped brain images. Due to the same problem, models trained on standard FFHQ or CelebA-HQ datasets (they contain aligned human faces) are also improper for solving arbitrary sizes.
Besides, the 128x128 image you present seems to be aliased. It is better to use downsamplers with anti-aliasing, e.g., bicubic or average-pooling.

Hi @wyhuai ,
Thanks for your quick reply. I really appreciate your great help.
I have some follow-up questions

what's the correct way for downsampling?

The original image size is 256x256 and I obtain the downsampled size by img128v1 = img[::2,::2,:]; img64v1[::4,::4,:].
img64v1

img128v1

To address the aliased issue, I used skimage.transform.rescale function.
https://scikit-image.org/docs/stable/api/skimage.transform.html#skimage.transform.rescale
img64v2 = transform.rescale(b_slice, 0.25, order=3, anti_aliasing=True)
img128v1 = transform.rescale(b_slice, 0.5, order=3, anti_aliasing=True)

img64v2

img128v2

It seems that the aliasing issue was addressed by gaussian smoothing. In this way, I cannot verify whether the noise is removed by the model because it is already removed by gaussian smoothing.
BTW, the noise is inherent in the image because of the imaging technique rather than hand-crafted. This is why it is important to be kept in the input image.

How to make the model work on img64v1 and img128v1?

For img64v1, the task is 64x64 to 256x256 and set scale=4
For img64v1, the task is 128x128 to 256x256 and set scale=2

In this way, it doesn't have the OOD issue.
Here are the restoration results
64->256

128->256

I'm also attaching the restoration results for img64v2 and img128v2
64->256

128->256

The results are much better but they are not what I want because the noise is already removed in the input image.

How to only denoise the image?

The input image is 256x256 and I set scale=1; sigma_y=1.5 but it seems that the model doesn't work
Input:

Output:

For Q1&Q2:
Note that the operator A you used for generating the input image and the A used in DDNM should be the same. This is critical, and you may refer to Section 2.2 and Section 3.1 in our paper to understand why.
If you use --deg "sr_averagepooling" --scale 4,  then A = torch.nn.AdaptiveAvgPool2d((256//scale,256//scale)) in DDNM. However, the operator in img64v1= img[::4,::4,:] is more like a mask operation rather than the defined A. So I suggest you use  img64v1 = A(img).
For Q3:
The denoising function in hq_demo is not carefully checked, and this problem may be a bug 😂.

Hi @JunMa11,
Thank you for your attention to our work. I want to make some additions to @wyhuai's reply.
Let us note the original image as $\mathbf{x}_{ori}=\mathbf{x}_{gt}+\mathbf{n}$, where $\mathbf{x}_{gt}$ means the clean ground truth and $\mathbf{n}$ means the imaging noise. If you want to solve a task combined with super-resolution and denoising, you create a low-resolution measurement as $\mathbf{y}=\mathbf{A}\mathbf{x}_{ori}=\mathbf{A}(\mathbf{x}_{gt}+\mathbf{n})=\mathbf{A}\mathbf{x}_{gt}+\mathbf{An}$, where $\mathbf{A}$ means some down sampler.
For Q1, we do not think the down sampler denoises the original image completely, that is, $\mathbf{An}\neq \mathbf{0}$. And even if we think that the noise has mainly been removed, we do not get a high-quality image but a low-resolution image $\mathbf{A}\mathbf{x}_{gt}$, which means that our restoration work is not really finished.
For Q2, in our code, we produce the degraded measurements and restore them using the same degradation operator $\mathbf{A}$. However, from your statements, I guess the degradation operator $\mathbf{A}$ used in your experiments is your own defined operator, and the degradation operator used in restoration is the one provided in our code, which may cause the two operators are not the same, and DDNM does not work.
For Q3, I suggest trying different values of sigma_y. In experience, too small sigma_y will lead to noise that is not completely removed, and too large sigma_y will lead to blurred results. You can try to increase the value of sigma_y to see the effect.

Hi @wyhuai and @vvictoryuki ,
Thanks for your detailed explanations very much. The Q1 and Q2 have been well addressed.
For Q3, I have tested different sigma_y but the results are the same.
Input

sigma_y = 1.5

sigma_y = 15

sigma_y = 150

This issue only appears in the hq code.
The original code does not have this issue. Thanks again for the awesome work.


Handle negative value of Version.Build when Version.TryParse succeeds…

… for a version string with only 2 fields (e.g. 1.0)
Customer scenario
Package property page fails to load due to an Argument exception when the Version property in the project file has less than 3 fields (e.g. 1.0)
Bugs this fixes:
Fixes VSO #382040
Workarounds, if any
Ensure the version field has at least 3 fields.
Risk
Low risk, we are just defaulting to 0 for non-existent fields.
Performance impact
None
Is this a regression from a previous update?
No, package property page was added very recently.
Root cause analysis:
Version.TryParse succeeds for version string with 2 fields, but the parsed version has a negative value for unspecified fields. Subsequently, we try to new up a Version with the individual fields, and this throws an ArgumentException.
How was the bug found?
Vsfeedback

@srivatsn @natidea @MattGertz for shiproom bar check.


Bring dialog policy up-to-date.

The dialog policy article was written a while ago. This removes the
“proposed” adjective (because it is published and no longer proposed),
and updates the list of changes to be up-to-date.

PTAL.


[KYUUBI #2553] Kyuubi Spark TPC-DS Connector - Add tiny scale

Why are the changes needed?
Current available scales: 0, 1, 10, 100, 300, 1000, 3000, 10000, 30000, 100000.
Event scale 1G is a little bit large for demo on laptop, we can introduce a scale 0.01 and name the database as tiny for demo purpose.
At the same time, it can also shorten the test time of UT.
close #2553
How was this patch tested?

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

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

./build/mvn test -Pspark-3.2 -Dtest=none -DwildcardSuites=org.apache.kyuubi.spark.connector.tpcds.TPCDSCatalogSuite,org.apache.kyuubi.spark.connector.tpcds.TPCDSQuerySuite,org.apache.kyuubi.spark.connector.tpcds.TPCDSTableSuite -pl 'extensions/spark/kyuubi-spark-connector-tpcds' -am

Current

Tiny

Codecov Report

Merging #2773 (fb62f32) into master (d49377e) will decrease coverage by 0.03%.
The diff coverage is 60.86%.

@@             Coverage Diff              @@
##             master    #2773      +/-   ##
============================================
- Coverage     62.12%   62.08%   -0.04%
- Complexity      425      426       +1
============================================
  Files           464      464
  Lines         20810    20825      +15
  Branches       2807     2816       +9
============================================
+ Hits          12928    12930       +2
- Misses         6620     6625       +5
- Partials       1262     1270       +8

Impacted Files
Coverage Δ

...i/spark/connector/tpcds/TPCDSStatisticsUtils.scala
34.73% <22.22%> (-2.05%)
:arrow_down:

.../kyuubi/spark/connector/tpcds/TPCDSBatchScan.scala
83.05% <75.00%> (+0.29%)
:arrow_up:

...he/kyuubi/spark/connector/tpcds/TPCDSCatalog.scala
45.71% <80.00%> (+1.96%)
:arrow_up:

...yuubi/spark/connector/tpcds/TPCDSSchemaUtils.scala
99.36% <100.00%> (+<0.01%)
:arrow_up:

...ache/kyuubi/spark/connector/tpcds/TPCDSTable.scala
70.27% <100.00%> (ø)

...rg/apache/kyuubi/engine/trino/TrinoSqlEngine.scala
52.63% <0.00%> (-7.02%)
:arrow_down:

.../org/apache/kyuubi/engine/jdbc/JdbcSQLEngine.scala
51.51% <0.00%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

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

Close in favor #2774


Bass annotations patch

Change delimiter to commas in new annotations. Add test for new annotations.

Coverage remained the same at 79.583% when pulling 8b7f66361a3f0b56eec3ca046a491680cac39489 on bass-annotations-patch into 482ab3e0b970640811e756cb6869a5159065629d on master.

Coverage remained the same at 79.583% when pulling 8b7f66361a3f0b56eec3ca046a491680cac39489 on bass-annotations-patch into 482ab3e0b970640811e756cb6869a5159065629d on master.


Class Diagramss

Complete it please!

Error: Missing Admin Privileges set for the class diagram.

The same issue has been already created and and one of our developer is working on it.  Thanks  @Raja108N
Regards,
Sudip


什么时候出4.6兄台 持支持支

The Redis adapter is currently being improved, and there is still much work to be done. Please be patient and wait for further support.

thanks


[WIP] housekeeping(esbuild): bump to v0.13.1

Fixes https://github.com/evanw/esbuild/pull/1621

We'll update esbuild in due time. Thanks for pointing out that specific issue and fix though!


double-beep: Watch bankstatementpdfedit.com

double-beep requests the watch of the watch_keyword bankstatementpdfedit\.com. See the MS search here and the Stack Exchange search here.

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

Approved by Makyen in Charcoal HQ


for antlr grammar development specification

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 6675

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.242%

Totals

Change from base Build 6672:
0.0%

Covered Lines:
10563

Relevant Lines:
14422

💛  - Coveralls


If string to output containst multiple words only the first is displayed

Given a string like "this is a great tool",
{%=o.Title%} will display:
This
and ignore the rest!

Thanks for your report @umbundu.
Unfortunately I cannot reproduce this issue, e.g. it works as expected on the demo.
I'm closing this tentatively, but feel free to provide additional comments with information on how to reproduce your result (e.g. an online demo).

Sebastian,
How are you? just to thank you for a prompt reply! I do apologize for
opening a ticket without proper testing on my part! I am all set.
Stay safe,
Everardo
On Tue, Apr 28, 2020 at 2:57 PM Sebastian Tschan<EMAIL_ADDRESS>wrote:

Thanks for your report @umbundu https://github.com/umbundu.
Unfortunately I cannot reproduce this issue, e.g. it works as expected on
the demo https://blueimp.github.io/JavaScript-Templates/.
I'm closing this tentatively, but feel free to provide additional comments
with information on how to reproduce your result (e.g. an online demo).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/blueimp/JavaScript-Templates/issues/48#issuecomment-620793892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMBWNFDPDXMF65EFJUS7ETRO4RKDANCNFSM4MSCMWZQ
.

I'm well, thanks for your kind reply Everardo ☺


Netgen file format

Hi,
I've implemented read/write support for the native format of the Netgen meshing software (.vol, .vol.gz).
Some features ( like domain names / cell_sets ) are still missing (need some example data sets before working on that).
Best,
Matthias

Looks pretty good! The test failures are unrelated, let me look into that. You can take care of the lint errors in the meantime.

Thanks for the fast and detailed review. I think all comments are addressed in the latest version.
Some problems with older Netgen files (and tokens I didn't test before) are now also resolved.
Concerning the "geomtype": I check now for known/allowed values but decided to only issue a warning if it doesn't match (new values might be added). The geomtype defines the format of additional geometry information after the "endmesh" token (this section is not parsed at all here).

Lint still fails, otherwise good to go.

Merged. Thanks for the great PR!

Published in v4.4.4.

Published in v4.4.4.

Thanks for merging and the fast response (inkluding a new version)!
There might be some future PR with new features in the future ( or an updated link to a new netgen format documentation :smiley:  )
Best,
Matthias