[improve] Replacing characters with http constants

hi, It is recommended that constants that are only used in the collector module be placed in the collector module instead of the common module.

hi, It is recommended that constants that are only used in the collector module be placed in the collector module instead of the common module.

Meaning in CollectorConstants? 🤔

hi, It is recommended that constants that are only used in the collector module be placed in the collector module instead of the common module.

Meaning in CollectorConstants? 🤔

move the collector relate constant files into collector module

Okay.i will do it
tomsun28 @.***>于2024年8月11日 周日15:59写道：

hi, It is recommended that constants that are only used in the collector
module be placed in the collector module instead of the common module.
Meaning in CollectorConstants? 🤔
move the collector relate constant files into collector module
—
Reply to this email directly, view it on GitHub
https://github.com/apache/hertzbeat/pull/2500#issuecomment-2282662666,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASS2GCPOMJG2NQADLNE27B3ZQ4KUPAVCNFSM6AAAAABMJWJN7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGY3DENRWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

ptal again, tks @tomsun28


[WIP] New feature: DeploymentTargetRules

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

Explain the details for making this change. What existing problem does the pull request solve?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

released in #2829


[Bug] UnboundLocalError: local variable 'archive' referenced before assignment

Hi,
since few days we have a problem with one of our charts on one of our grafana (4.3.2-1) dashboards. We use graphite datasource. The problem appears only in one particular chart, sicne few days, similar charts with other parameters are not impacted.
Here some print screen about the issue.

The server have been rebooted (by our hoster) few days ago. I don't know if it's related but maybe it's a useful information. I search for corrupted whisper files, in case of, but didn't find them.
Have you an idea of where I can search to fix the problem?
Thanks.

Hello @scraly ,
What's version of your Graphite?

Good question. I use graphite with Grafana so do you know where I can find this version?
Thw.

In my graphite repository I've got webapp/graphite-web-0.9.13-py2.7.egg-info repository.
I don't know if it's the version used by last version of Grafana.

Try to ask '/version/' on Graphite URL.
E.g.
0.9.12

Grafana is not 'using' Graphite, it's separate dashboard. Somebody installed Graphite on your system and connect Grafana to it, but that's completely separate projects.

You can find Graphite url in Datasources list in Grafana.

When I access to the graphite url I am redirected to the graphite web interface.

So, the graphite version we use is: 0.9.12

I would say that's broken whisper file.  Please check the size of your whisper files, do you see some really small files, less than 1KB? Maybe disk with whisper file was full some time ago? (it's effectively corrupt whisper files)

Hi,
I search for whisper files smaller than 676k (the size of correct files) and I found 0 files ... :-(
We don't have full disk space issue but our sevrer have been rebooted by our hoster, maybe it's the root cause but how to fix the problem?
Have you some ideas ?
Thanks.

Unfortunately, not. According to code it's really looks like broken wsp files, though

Yeah, the whisper file must not have any archive entries in the header.


Add testing for CloudQuery and AWS Source upgrades

CloudQuery has a rapid release cycle and each of its plugins even more so (they are being developed independently).
Being able to quickly and continuously assess whether upcoming versions break our custom queries running on top of CQ source plugins is critical to ensure that we always have a full view of our LZ and that we are aligned with our desired security measures.

fixed in #453


Add task for Istio CA health check.

@wattli @ldemailly PTAL. Thanks!

@ldemailly I think this PR is ready to be merged :)

feel free to merge it and we can continue the discussion on why not use the open port for health check elsewhere
my last comment:

afaik we are allowing grpc calls from the mesh and vms, without mtls so not sure I get your point with the benefits/requirements of not use the open port for health checks

Sure. Could you merge it for me? I don't have write access to this repo.
The design doc is here:
https://docs.google.com/document/d/1ig1ieuaPYr-EB7gByt4BgCQAXudnmZrqXV294K_oU1M/edit#
Please feel free to comment.


Documentation: Document BGP timers & neighbor update behavior

Adds documentation for the BGP timer parameters (added in https://github.com/cilium/cilium/pull/25408) & BGP neighbor update behavior (updated in https://github.com/cilium/cilium/pull/25827).

Doc change only, documentation workflow and Netlify preview passed. This is ready to merge.


pretrainedmodels problem

when i run the features preporation code:
python prepro_feats.py --output_dir data/feats/resnet152 --model resnet152 --n_frame_steps 40  --gpu 1,2,3
i got the problem:
No module named pretrainedmodels,.
where could i get it?

https://github.com/Cadene/pretrained-models.pytorch


sqlite json1 extension

Hi, I'm using peewee and a sqlite database with the json1 extension.  On both a normal windows install as well as on my linux machine, sqlite out of the box has the json1 extension enabled.
When I however check on the python executable in the docker image it does not have this extension enabled and thus the build exe does not work correctly.  Do you have any idea how I can do this in wine ?

I've in the meanwhile figured out that it isn't an issue with wine, but just with pyinstaller itself that also occurs without docker. Sorry for the inconvenience.


Document .babelrc option for transformation

Ref: https://github.com/babel/babel/blob/4e82edb6d0c9e7a8ba2c51d6baf3e170824ed285/packages/babel-core/src/transformation/file/options/config.js#L142
Fixes #620.

Thanks


Side navigation submenu animation with simpler transition

Changes

@mayank99 following your suggestion using only transformX and based on https://web.dev/building-a-sidenav-component/#transforms. Also made another PR because this change effectively undo 95% of the other PR so might as well.
The z-index: -1 is needed here because otherwise the submenu will slide on top of side navigation bar during transition
So far so good, only one issue: the parent/wrapper doesn't resize (to only the size of side navigation) when submenu is transited out of view.
Things I have tried include:

add flex-shrink: 1 to submenu
add justify-content: end and justify-items: end to wrapper (also tried align-self: end too)
testing different values for block-size and width submenu

Do you know what else could work?
Testing

Docs

only one issue: the parent/wrapper doesn't resize (to only the size of side navigation) when submenu is transited out of view.

ah yeah, it won't work with this technique, so let's abandon this and move forward with the grid technique from #1439


Add Solidity tests JS benchmark

Adds a JS benchmark command to execute certain forge-std tests to benchmark the EDR Solidity tests implementation against forge. The benchmark can be executed with pnpm i && pnpm soltests from the crates/tools/js/benchmark directory. There is no difference in execution time on my machine between forge test and pnpm soltests.
Baseline:
git clone https://github.com/NomicFoundation/forge-std.git
cd forge-std
git checkout js-benchmark-config
foundryup --commit 0a5b22f07
forge test --no-match-contract 'StdChainsTest|StdCheatsTest|MockERC721Test|MockERC20Test|StdCheatsForkTest|StdJsonTest|StdUtilsForkTest|StdTomlTest'

The ignored forge-std tests use fork mode or depend on Foundry project format.

There seem to be issues in CI that I'm not seeing on other PRs. Could a setting have affected the deserialisation logic?

There seem to be issues in CI that I'm not seeing on other PRs. Could a setting have affected the deserialisation logic?

Thanks, it was a problem in the base branch after merging main into it. It should be fixed now.


Search Fibonacci algorithm in python

Hi I want to contribute in issue related to #37. Please kindly review it. I only wrote it in python.

Thank you for contribution
Give star :star: to this repository


how to track ?

in the implementation i didnt see how to start tracker. How should i try this tracker on video ?

@cezeribursa here: https://github.com/megvii-research/video_analyst#sot-video-demo

@cezeribursa here: https://github.com/megvii-research/video_analyst#sot-video-demo

Hello, is it okay to just fill in the missing directories? I did this, but the run was unsuccessful

not only the missing directories, but also the files in it @HoungJee


Hammer custom title on plates

It would be handy to have a reserved area of the plate where an arbitrary text entered by the user can be engraved.
Even a small number characters would be useful.

We'll implement this on our side by using the titles passed to us from the coordinator software.
For Sparrow, that's https://github.com/sparrowwallet/sparrow/issues/911.
For Nunchuk, that's https://github.com/nunchuk-io/nunchuk-android/issues/22

It would be great to be able to set the title independently of the coordinator or offer the possibility to override it in the seedhammer interface. It's a quite useful feature, especially to avoid mix ups when you have multiple sets of plates for different accounts

It would be great to be able to set the title independently of the coordinator or offer the possibility to override it in the seedhammer interface.

We want to keep the UI/UX as simple as possible. And with such a small screen and only 3 buttons it quickly becomes cluttered.
More importantly we wan't to be "the printer", not the configurator (for now at least). Titles of cosigners/keys is not just easier to do in eg. Sparrow (with access to full QWERTY) but also the right place to do so. The descriptor should exactly describe your setup - in essence nothing unknown to the descriptor should be entered in a later process.

It's a quite useful feature, especially to avoid mix ups when you have multiple sets of plates for different accounts

We can't see how this is not obtained through the descriptors?

It would be great to be able to set the title independently of the coordinator or offer the possibility to override it in the seedhammer interface.

We want to keep the UI/UX as simple as possible. And with such a small screen and only 3 buttons it quickly becomes cluttered.
More importantly we wan't to be "the printer", not the configurator (for now at least). Titles of cosigners/keys is not just easier to do in eg. Sparrow (with access to full QWERTY) but also the right place to do so. The descriptor should exactly describe your setup - in essence nothing unknown to the descriptor should be entered in a later process.

Alright, makes sense!

It's a quite useful feature, especially to avoid mix ups when you have multiple sets of plates for different accounts

We can't see how this is not obtained through the descriptors?

Basically you have 3 account which are each a 2 of 3, you end up with 9 plates and want to restore your 3 wallets, which pairs (of descriptor parts) do you scan ?

Basically you have 3 account which are each a 2 of 3, you end up with 9 plates and want to restore your 3 wallets, which pairs (of descriptor parts) do you scan ?

Assuming we have implemented this feature:
Those that identifies themself as being part of the same setup.
Eg scan these two:
1/3 “Satoshi’s stash”
3/3 “ Satoshi’s stash”
and these two:
1/3 “Alice’s stash”
2/3 “Alice’s stash”
…
However it isn’t a real world problem. If you ever want to collect the quorum of a setup (in order to restore) you probably never would gather more than one multisig wallet at a time (would be a honeypot of dimensions).
And if you take the risk anyways then just scan all plates from a to z until a wallet reveals. As soon as the first workable wallet is identified you can see the mfp’s in the coordinator software and remove those plates from the pot of plates at hand (mfp always hammered on each plate).

Backup titles have been implemented in v1.2.0 for supported wallets.

We'll implement this on our side by using the titles passed to us from the coordinator software.
For Sparrow, that's sparrowwallet/sparrow#911.

This was just keystore (co-signer) labels and is not used for titles. We brought up the issue of adding wallet titles to the Sparrow/Blockchain Commons format, but since the format is not deprecated, titles are unlikely to be implemented for Sparrow exports. Use the BlueWallet export option as a workaround.


[TEAL] Extra documentation

This issue is for documenting TEAL behavior which is insufficiently explained in the official docs. The proper place for this is the wiki, but this implies a larger refactoring of it, which we will do in-between audits. My recommendation is that we tag items with source and timestamp where possible.

When creating an application, the creator can opt-in straight away
@nwatson22 has discovered the fact that when an ApplicationCall transaction with ApplicationID == 0 is submitted (app creation), the creator account can specify OnCompletion == OptIn and become opted-in upon acceptance of the creation transaction.
This behavior is not documented in Algrorand Developer Documentation, but that's what go-algorand does.

Not only that, I believe it can be instantly deleted.
On Fri, Sep 30, 2022, 4:43 AM Georgy Lukyanov @.***>
wrote:

When creating an application, the creator can opt-in straight away
@nwatson22 https://github.com/nwatson22 has discovered the fact that
when an ApplicationCall transaction with ApplicationID == 0 is submitted
(app creation), the creator account can specify OnCompletion == OptIn and
become opted-in upon acceptance of the creation transaction.
This behavior is not documented in Algrorand Developer Documentation, but
that's what go-algorand does.
—
Reply to this email directly, view it on GitHub
https://github.com/runtimeverification/avm-semantics/issues/12#issuecomment-1263287912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADL7TZVNR7J3V3H6NTIGQDWA2R2LANCNFSM5P6CGLVQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Date missing milliseconds if they are exactly 0 which causes server error

Environment details

OS: Gentoo Linux
PHP version: 7.4.5
Package name and version: google-api-php-client v2.4.1

Steps to reproduce
Two days ago I got the following error from an API call that usually works totally flawlessly:
"error": {
   "errors": [
     {
      "domain": "global",
      "reason": "invalid",
      "message": "Invalid value for: Invalid format: \"2020-05-02T09:13:32Z\" is malformed at \"Z\""
     }
   ],
   "code": 400,
   "message": "Invalid value for: Invalid format: \"2020-05-02T09:13:32Z\" is malformed at \"Z\""
  }
}

Stack trace:
#0 /vendor/google/apiclient/src/Google/Http/REST.php(94): Google_Http_REST::decodeHttpResponse()
#1 /vendor/google/apiclient/src/Google/Task/Runner.php(176): Google_Http_REST::doExecute()
#2 /vendor/google/apiclient/src/Google/Http/REST.php(58): Google_Task_Runner->run()
#3 /vendor/google/apiclient/src/Google/Client.php(842): Google_Http_REST::execute()
#4 /vendor/google/apiclient/src/Google/Service/Resource.php(232): Google_Client->execute()
#5 /vendor/google/apiclient-services/src/Google/Service/YouTube/Resource/Videos.php(313): Google_Service_Resource->call()
#6 Video.php(545): Google_Service_YouTube_Resource_Videos->update()
…

The error seems to indicate that the microseconds are missing.
My code itself does not format any dates when using the YouTube API. Could it be that google-api-php-client omits the milliseconds when formatting ISO 8601 dates if they are exactly 0? This is very unlikely to happen but seems to have happend here.
I've been trying to find out where google-api-php-client formats dates but have been unable to find such places.

The API client does not transform dates. It accepts them in any format and leaves it up to the user and the upstream API to control for errors. If you've only seen the error once, it's possible there was just a transient error in the API.
If you continue to see the error, share the code that triggers it and we'll take a look.

I've dug a little deeper. The issue happens more or less reliably since about one week when you try to update a video immediately after it has been uploaded. To update a video, you have to have to first fetch it (using listVideos). If you do this immediately after uploading, the YouTube API sometimes returns a publishedAt date without milliseconds (i.e. 2020-05-07T08:48:22Z instead of 2020-05-07T08:48:22.000Z). Such a publishedAt value is then refused by the YouTube API when updating the video.
So this is not an issue in google-api-php-client but a YouTube API server issue. I'm not sure where to report that. A possible client-side workaround is:
if (preg_match('/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}Z$/', $snippet->publishedAt))
{
	$snippet->publishedAt = str_replace('Z', '.000Z', $snippet->publishedAt);
}```

Nice find! That does seem like a problem they should know about. You can report it in the public issue tracker.
Since we seem to have discovered that this isn't a bug in the client library, I'm going to close it out.
I haven't tested this, but you could probably also do something like this:
if (!DateTime::createFromFormat(DateTime::RFC3339, $snippet->publishedAt)) {
	$snippet->publishedAt = str_replace('Z', '.000Z', $snippet->publishedAt);
}


Version 5.2.1 shows jazz_fingers as application name

Version 5.2.0:
$ rails console
2.7.1 (my_app_name)[1] »

Version 5.2.1:
$ rails console
2.7.1 (jazz_fingers)[1] »

Which version of Rails are you using?

Sorry, forgot to mention in the issue. I'm using Rails <IP_ADDRESS>.

Ah, I can see it now. https://github.com/plribeiro3000/jazz_fingers/commit/57c97fa206e3e5eca0397ac844cd6e9487002f3b tries to fix a deprecation warning, but removed the return statement. Now jazz_fingers is always returned.
Should we return a default like this instead of maybe throwing an exception or displaying a warning? In which cases would this not return a value?

Ouch. Good catch.
Could you open a PR?

I guess just adding return would be enough.
If we can get the application name let use it otherwise use the default which is the gem name.


reference relationship diagram

Is your feature request related to a problem? Please describe.
views and materialized views often refers to layers of tables and other views and materialized views. making changes on one table can have ripple effects on views and materialized views that refers to it. and to change a view or a materialized view, you need to adjust multiple of table/view/materialized views it refers to. This intricate relationship often burdens users, as they may forget some dependent entities (table/views/materialized views) when making changes on one entity.
Describe the solution you'd like
So, other than entity relationship diagram (ER diagram), I propose another diagram called reference relationship diagram, which shows clearly how each entity refers to each other. When you open an entity, you can see what entities it refers to and what entities refers it.
it would look like this, where green represents table, yellow view and red materialized view. so when I want to get rid of a record in metadata.mv_complete_field_info, I know the source may come from several root tables. basically it's the visualization of current dependencies tab, but not only with one layer of dependencies, but all layers of dependencies.

Thanks for the request. It sounds interesting


Pull out initTagField from core.js into includes/initTagField.ts

Is your proposal related to a problem?
initTagField should move from core.js to a new file client/src/includes/initTagField.ts
Wagtail's JavaScript core.js is quite large and many items can be pulled out to shared utils or includes to help make the code more maintainable and supported with base unit tests.
Pulling some basic functions out lets us put these into TypeScript (type safety) but also document and unit test them better.
Describe the solution you'd like
The function initTagField should be moved from
https://github.com/wagtail/wagtail/blob/aaea8710c21ba4d5368d3825781bc54e1869c561/client/src/entrypoints/admin/core.js#L32-L50
To a new file client/src/includes/initTagField.ts (note: TypeScript ts not JavaScript js)
From there it can be imported and triggered the same way (added to a global back in core.js)
Requirements

[ ] Move the function to the the new TypeScript file and set up correct types - https://www.typescriptlang.org/
[ ] Add a JSDOC description to the function
[ ] Add a basic set unit test (just one is fine) for this function in a new client/src/includes/initTagField.test.js file using Jest
[ ] Ensure the util is imported in core.js correctly and the window variables window.initTagField works, take as screenshot of a tag field working after your change fo rthe PR

Additional context

This has been created as part of the Outreachy program to help new contributors that are interested in the Stimulus project.
Look at client/src/includes/breadcrumbs.test.js for an example of mocking some HTML to then trigger some behaviour on that HTML
Note that this will be a bit tricky as tagit is a jquery plugin and is a global, so TypeScript may not like this, you will need to look at other TypeScript files or search online for how to ensure that TypeScript will allow this global. See client/src/utils/text.ts for an example of declaring a global for Typescript.
Testing jquery unit tests will require you to set up window.$ - see client/src/entrypoints/admin/telepath/widgets.test.js as an example, you may also need to mock (Jest mocks) the tagit function.
Important: The unit test does not need to test the full functionality of the tagit plugin, only that it was called.

Thank you @lb-
I would work on this.

Can I work with .JS file because currently there are some complications with .ts file.

I am working on it
On Fri, 4 Nov 2022, 12:09 Anisha Singh, @.***> wrote:

Can I work with .JS file because currently there are some complications
with .ts file.
—
Reply to this email directly, view it on GitHub
https://github.com/wagtail/wagtail/issues/9496#issuecomment-1303276567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATR5T4IVPDVBVUXZDVXT4BLWGTVFHANCNFSM6AAAAAARO6FLX4
.
You are receiving this because you were assigned.Message ID:
@.***>

Hey @lb- I have come up with a PR https://github.com/wagtail/wagtail/pull/9614 which is fixing 2 issues at once.
Issue 1:
https://github.com/wagtail/wagtail/issues/9496
Issue 2:
https://github.com/wagtail/wagtail/issues/9493

@AnishaSingh0118 thanks but as per the previous comments and already linked PR it hopefully was quite clear that @xomcodes is actively working on this issue.
I appreciate your enthusiasm but stepping in over someone who is trying to learn is not ideal.
For now, can you close the PR that covers both issues and I suggest that @xomcodes you take a look at the PR for any inspiration.

@AnishaSingh0118 thanks but as per the previous comments and already linked PR it hopefully was quite clear that @xomcodes is actively working on this issue.
I appreciate your enthusiasm but stepping in over someone who is trying to learn is not ideal.
For now, can you close the PR that covers both issues and I suggest that @xomcodes you take a look at the PR for any inspiration.

Ok, sure I am just trying from my end to help as much I can by constantly working and understanding the issues and coming up with a approach and get feedback. I am sorry if I came in way of someone else I have read somewhere "no need to ask if you have resolved the issue you could provide the efforts". So I got confused now 😅


Zero width character highlighting for the file explorer

The editor already does a fantastic job of highlighting those nasty zero-width characters. Can the same be applied to file names in the file explorer too? I think the problem is self explanatory.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


add a hatdataserver.py for API access to the HAT data server

This will be a module that encapsulates all the annoying bits of authentication and API keys and allows access to:

the HAT footprint service
the HAT light curve catalog
the HAT object info service
the HAT xmatch service

Pointers to credentials and user options, etc. will be in a hatdataserver.conf file. The actual credentials will be in a .hatcreds file.
We may want to break this out into a separate package later.

Finally fixed now that we actually have a working HAT data server!
See 16155cd5de27d2e730a6f259203489905f449db7 to d2a88381b98a30491cf6726c92f949be67a5f950.


adds a new "Box and Whisker Diagram"

Hi @Thodajeha, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@Thodajeha please use separate fork for your development. And we are waiting for you submission to the Power BI visuals gallery.


Update fields of optional image watcher config

What this PR does / why we need it:
The three changes are included:

Rename repos to gitRepos (some people can confuse and mistake it for container repository)
Make checkInterval global (most cases need only global settings. Let's add a field for each repo when really needed)
Add some validations

The current structure is:
apiVersion: pipecd.dev/v1beta1
kind: Piped
spec:
  imageWatcher:
    repos:
      - repoId: foo
        checkInterval: 10m
        commitMessage: Update image
        includes:
          - imagewatcher-dev.yaml
          - imagewatcher-stg.yaml

From now:
apiVersion: pipecd.dev/v1beta1
kind: Piped
spec:
  imageWatcher:
    checkInterval: 10m
    gitRepos:
      - repoId: foo
        commitMessage: Update image
        includes:
          - imagewatcher-dev.yaml
          - imagewatcher-stg.yaml

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/lgtm

/approve