refactor std.format to eliminate redundant dependencies if the format string doesn't ask for it

hsteoh reported this on 2014-10-03T14:18:24Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=13568
CC List

andrei (@andralex)
greensunny12
naptimeentertainment
nick (@ntrel)

Description
Currently, std.format.formattedWrite (along with the convenience wrappers around it, namely writef, writefln, std.string.format, etc.), take a runtime format string as argument, although most use cases involve format strings that are already known at compile-time. This limits what we can statically do with these string, e.g., statically check that the right number of arguments are being passed for that format, that the right types are being passed, etc., instead of deferring until runtime to detect any problems.

Ideally, we should extend formattedWrite() to accept compile-time strings so that if the format is already statically known, we can perform compile-time checks on it.

hsteoh commented on 2014-11-21T03:39:56Z
Another major advantage of compile-time format strings is that we can avoid format() pulling in half of Phobos on the off-chance that some obscure runtime format string might actually need that code to format something. By analysing the format string at compile-time, we can make it so that only the necessary bits of code are imported, thus greatly clearing up the big hairball that is Phobos module interdependencies currently.

github-bugzilla commented on 2017-04-03T15:50:06Z
Commit pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/95b2b139e9438e8ff7383946be4aa0de3a85159a
Merge pull request #5296 from ntrel/ct-stdio-format

github-bugzilla commented on 2017-03-22T22:10:40Z
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/3aa8011a043a9bcfd52d43255f3c0a8885e143e9
Issue 13568: Add CT-checked format string overloads to std.stdio

* Add overloads for readf, writef, writefln.
* Separate fmt argument from args for writef[ln] to improve docs.

https://github.com/dlang/phobos/commit/722683b65186a46a6f9977e15810ee766b257879
Merge pull request #5296 from ntrel/ct-stdio-format

Issue 13568: Add CT-checked format string overloads to std.stdio
merged-on-behalf-of: H. S. Teoh<EMAIL_ADDRESS>

github-bugzilla commented on 2017-04-02T21:30:39Z
Commit pushed to stable at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/95b2b139e9438e8ff7383946be4aa0de3a85159a
Merge pull request #5296 from ntrel/ct-stdio-format

Issue 13568: Add CT-checked format string overloads to std.stdio
merged-on-behalf-of: H. S. Teoh<EMAIL_ADDRESS>

hsteoh commented on 2017-09-01T21:34:48Z
This is not completely fixed yet.  Part II is to refactor std.format to eliminate redundant dependencies if the format string doesn't ask for it.  E.g., if the format string is only "%s" the resulting code should not pull in dependencies on floating-point formatting code.

github-bugzilla commented on 2017-03-22T12:22:35Z
Commit pushed to stable at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/4a1733e7e2e1a1b20a9e2ae2aa28fdc098dc5f7e
Merge pull request #5288 from ntrel/ct-format

hsteoh commented on 2017-03-17T20:45:11Z
Partial implementation: https://github.com/dlang/phobos/pull/5288

github-bugzilla commented on 2017-03-19T00:06:39Z
Commit pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/4a1733e7e2e1a1b20a9e2ae2aa28fdc098dc5f7e
Merge pull request #5288 from ntrel/ct-format

Issue 13568: Add CT-checked format string overloads to std.format
merged-on-behalf-of: Andrei Alexandrescu<EMAIL_ADDRESS>

github-bugzilla commented on 2017-06-17T11:34:08Z
Commits pushed to stable at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/3aa8011a043a9bcfd52d43255f3c0a8885e143e9
Issue 13568: Add CT-checked format string overloads to std.stdio

https://github.com/dlang/phobos/commit/722683b65186a46a6f9977e15810ee766b257879
Merge pull request #5296 from ntrel/ct-stdio-format

github-bugzilla commented on 2017-08-07T12:26:30Z
Commits pushed to newCTFE at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/4a1733e7e2e1a1b20a9e2ae2aa28fdc098dc5f7e
Merge pull request #5288 from ntrel/ct-format

https://github.com/dlang/phobos/commit/3aa8011a043a9bcfd52d43255f3c0a8885e143e9
Issue 13568: Add CT-checked format string overloads to std.stdio

https://github.com/dlang/phobos/commit/722683b65186a46a6f9977e15810ee766b257879
Merge pull request #5296 from ntrel/ct-stdio-format

https://github.com/dlang/phobos/commit/95b2b139e9438e8ff7383946be4aa0de3a85159a
Merge pull request #5296 from ntrel/ct-stdio-format

greensunny12 commented on 2018-03-30T01:05:29Z
> This is not completely fixed yet.  Part II is to refactor std.format to eliminate redundant dependencies if the format string doesn't ask for it

This should have been a separate issue (bugzilla even allows meta issues that depend on other issues), but I renamed this for now.

b2.temp commented on 2017-09-27T22:59:39Z
There's https://issues.dlang.org/show_bug.cgi?id=17381 that could be handled the day std.format will be refact.

The strategy used to check statically the specifier (call format() and look if there's been an exception) makes it impossible to fix.

github-bugzilla commented on 2018-01-05T13:27:54Z
Commits pushed to dmd-cxx at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/4a1733e7e2e1a1b20a9e2ae2aa28fdc098dc5f7e
Merge pull request #5288 from ntrel/ct-format

https://github.com/dlang/phobos/commit/3aa8011a043a9bcfd52d43255f3c0a8885e143e9
Issue 13568: Add CT-checked format string overloads to std.stdio

https://github.com/dlang/phobos/commit/722683b65186a46a6f9977e15810ee766b257879
Merge pull request #5296 from ntrel/ct-stdio-format

https://github.com/dlang/phobos/commit/95b2b139e9438e8ff7383946be4aa0de3a85159a
Merge pull request #5296 from ntrel/ct-stdio-format


Migrate to Bone.io

Need to move the project to a proper framework at some point because the client side code is getting really messy. Already made a bit of an attempt at Angular but the communication is done in AJAX. Bone.io is built on Socket.io which is already being used extensively.

How about using ReactJS or MarkoJS? Angular is slow!


feat(chat):chat overlay sign in

Description:

Add a set of overlay options to allow sign in from the chat overlay (with or without particular auth provider);
Make a small refactoring to have ChatOverlayOptions in one place;

Checklist:

[X ] the pull request name complies with Conventional Commits
[ X] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[ ] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[X ] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "feat(chat):chat overlay sign in". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore

/deploy-review


Travis job TEST_OTHER_MODULES is flaky: job exceeded the maximum log length

TEST_OTHER_MODULES=!presto-tests,!presto-raptor-legacy,!presto-accumulo,!presto-cassandra,!presto-hive,!presto-kudu,!presto-docs,!presto-server,!presto-server-rpm,!presto-main,!presto-orc,!presto-parquet,!presto-mongodb,!presto-redis,!presto-sqlserver,!presto-postgresql,!presto-mysql,!presto-phoenix failed eg in https://travis-ci.com/prestosql/presto/builds/127101090 with
...
2019-09-11T21:22:44.797-0500 WARNING A provider io.prestosql.server.TaskExecutorResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.prestosql.server.TaskExecutorResource will be ignored.
2019-09-11T21:22:44.799-0500 WARNING A provider io.prestosql.server.ClusterStatsResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.prestosql.server.ClusterStatsResource will be ignored.

The job exceeded the maximum log length, and has been terminated.

After https://github.com/prestosql/presto/pull/1525, TEST_OTHER_MODULES takes ~38 minutes and runs tests fewer modules.


[Improvement][service]   move remote clients to dolphinscheduler-remote module

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
The remote clients AlertClientService, LogClientService, RegistryClient should be moved from the dolphinscheduler-service module to the dolphinscheduler-remote module.
They mainly depend on the remote module instead of the service model.
The package name after moving to dolphinscheduler-remote：
org.apache.dolphinscheduler.remote.client.alert.AlertClientService
org.apache.dolphinscheduler.remote.client.log.RegistryClient
org.apache.dolphinscheduler.remote.client.registry.RegistryClient

This will involve refactoring the api、service、master、worker and etc. modules
We can copy the remote clients to the remote first, migrate gradually, and finally delete the remote clients in the service.
The purpose is to remove the worker server's dependency on the service module (that is, the database)
Use case

more reasonable dependencies
prepare to remove the worker server's dependency on the service module

Related issues
#9283
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I tried it.it is too difficult, too many dependencies are nested.
The better way is to move to dolphinscheduler-server, keep the package structure the same so that the impact is minimal.


Batch_size error

Hi,
I am getting this error "TypeError: Campaign.recommend() got an unexpected keyword argument 'batch_size'". I am attaching snapshot for your reference. Could you please help me to sort this error out because till yesterday it was working fine.

Hello @CatSci, thanks for your question!
Could you maybe specify how you used and installed the package? That is, did you install via pip, did you install the latest version directly from the repository and which python version are you using?

Also, some other user experienced this as well, and it turned out that the reason was in fact a de-sync between the installed version of the package itself and the executed files. So you might also want to have a look here #121 and see if this happens to be related to your issue.

Thanks, I am using campaign.from_json() and then using campaign.recommend(). I will keep you updated.

Hi @CatSci the keyword batch_size of recommend was just recently introduced as renaming of the old keyword batch_quantity, please verify that you have a version > 0.7.2 installed since this deprecation happened there. Can you confirm which baybe version exactly is installed?
Also, since the old keyword was batch_quantity and our recommend function still has a batch_quantity keyword (for deprecation reasons) I would prob also try and rename the keyword batch_quantity to something else in your scripts to be absolutely 100% safe

Thanks, I will check the version and other recommendations from your side.

I am sorry I didn't close this earlier. Your suggestions helped to fix the issue. Thank you so much of helping me out

No problem and happy that we could help 😄


Update version of postcss-load-config

Describe the bug
In an issue originally identified in the TailwindCSS repository, I've been able to work through the upstream dependencies and found that vite relies on postcss-load-config to load it's configuration files.
https://github.com/tailwindlabs/tailwindcss/issues/13927
I originally thought that this was an issue with postcss-load-config, however I later realised that support for .mts files has already been integrated into it. The issue is that vite is using a very old version of postcss-load-config.
https://github.com/postcss/postcss-load-config/issues/265
What build tool (or framework if it abstracts the build tool) are you using?
vue 3.4.31, typescript 5.5.2, vue-tsc 2.0.24, vite 5.3.2, tailwindcss 3.4.4
Reproduction
https://github.com/jscarle/ReproTailwindCSS
Steps to reproduce
No response
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700KF
    Memory: 48.57 GB / 63.84 GB
  Binaries:
    Node: 22.3.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.65)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @vitejs/plugin-vue: ^5.0.5 => 5.0.5
    vite: ^5.3.2 => 5.3.2

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I wasn't able to reproduce. At least, I can say we cannot update postcss-load-config until v6 as it's a breaking change: #15869

Closing as a duplicate of #15869


329 - Return ok and status properties on fetchAsync helper

Issue Number
Epic: #336
Closing #329
Purpose/Implementation Notes
Included the ok and status properties in return object.
Next Steps:
Refactor the following patterns in hooks:

errors handling for resource fetching
the state for resources (set on success)

Types of changes

New feature (non-breaking change which adds functionality)

Functional tests
List out the functional tests you've completed to verify your changes work locally.
Checklist

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

This PR is part of Epic #336 and requires further refactoring of the codebase using this updated fetchAsync helper. Merging will be postponed until the refactoring is complete to avoid breaking dev. A new issue for the refactoring will be filed.

Minor change: I've reverted the renaming of result back in 829a10c72f4a6cccb45147182c5a4f1c40e2480c to prevent breaking dev on merge. Thank you!


Improve MAVEN build Performance

According to Maven parallel test, we can run tests in parallel.
=====================
If there are any inappropriate modifications in this PR, please give me a reply and I will change them.

Thanks for the PR, but currently the project doesn't need to run tests in parallel.
Closing the PR.


Create a Frontend with SAP Fiori Elements and Annotations

Tutorial URL: https://developers.sap.com/tutorials/cap-cloudsdk-6-fiori-frontend.html
step 1: the "At the root URL" point to this:
https://developers.sap.com/tutorials/http_localhost_4004.html

instead of : http://localhost:4004/

I assume DJ fixed already -- can you check if this is still an issue?

Fixed already. Still pending the fix in the tutorial rendering (to sort the cause rather than this symptom, but that's not to track here.


[HOLD for payment 2023-12-21] [$500]  [Wave 6: Categories] - Unexpected error when requesting money with a very long category in workspace chat

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

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/30264
Action Performed:
Precondition:
The following long category is set up on OldDot.
Meals: Level 2 nesting and a category name that could span two lines: Level 3 nesting and a category name that could span two lines: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Go to workspace chat > + Request money > Manual.
Create a money request with no category.
Note that the request is successful.
Repeat Step 2 with a very long category name from the precondition.

Expected Result:
The request is successful.
Actual Result:
The request is not successful. It shows an unexpected error message.
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/a02cdb5f-5a93-4c53-a8b1-2aa27c20eee2

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~018cfdce1c85555976
Upwork Job ID:<PHONE_NUMBER>334507520
Last Price Increase: 2023-11-01
Automatic offers:

Ollyws | Reviewer | 27576838

I was able to reproduce this and I confirm that the RequestMoney call fails with the following error:

Which means that the long category created on OldDot turns out to be exceeding maximum size when the NewDot's RequestMoney is called with that category. I think this is a BE related issue.

Hey there shouldn't be any proper handling for requesting money with category. We can use if and AND condition to solve this issue. Let me know if you need a help.
Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01149c9659573bccce

Hey @NisargDeveloper if you'd like to work on this, can you please post a proposal per the instructions in https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md?

hey! @stephanieelliott I tried to reproduce it. I thinking I'm missing step. May I know how can I setup Old Dot?.

@NisargDeveloper can you clarify which step you are getting hung up on? Perhapd @kbecciv can help clarify

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue.

Hey I cannot see the Create Policy on the left side? Please see the attached ss.

Assigning @rezkiy37 as they worked on these features and will handle this update too

So, guys, looks like we have a collision regarding the maximum length of name for a category.
We can add a category up to 256 symbols on the OD, 257 symbols are too long. However, when we create a money request on ND, the backend does not accept a category with 256 symbols name.

https://github.com/Expensify/App/assets/57314631/bfe18c07-d07e-4f78-ae66-c1582fdac8f1
Based on this, looks like we need to unify backend restrictions for name's length.
cc @mountiny

Sounds like we can then just lower the length allowed in new dot right?

@mountiny, can we decide what's exactly the maximum length for names? After, we can add a FE validation for the input.

can we decide what's exactly the maximum length for names? After, we can add a FE validation for the input.

Maximum for categories? Is there any in OldDot? If yes, lets use that one and add FE validation for it.

What? I don't understand. One hour ago I could set a category with 256 symbols.

Ah, OD restricts 255 for one category. I mean for example there is "Parent: Child" and "Parent" OR "Child" shouldn't be longer than 255, but together they could be longer 🤯 😅

there was inconsistency with how we handle these in the backend and I have created a PR which shoul update that however weirdly enough the correct request param size is smaller than what we had there in a first place :D
Lets see if this will help but could you also share whats the payload of the category when you are editing this?

@mountiny, that's a screenshoot how the app sends a request to update a category.

Melvin, we are waiting on backend changes to verify that the bug has been fixed.

Seems like the passed data is fine, lets see how this works after the deploy

Melvin, no "overdue" 😅

@rezkiy37 coul dyou test this out? the backend change has been deployed
The overdue now only reacts and counts to @Ollyws

@mountiny, I've tested on the staging and production. Unfortunately, the bug is still here. I reset cache, no luck.
https://github.com/Expensify/App/assets/57314631/a60eeb81-622f-4ffc-b699-4c825e8c9cff

@mountiny, just a friendly reminder about - https://github.com/Expensify/App/issues/30683#issuecomment-1812556566.

Posted in Slack to get some volunteers to fix this one, we will have to do some debugging

Waiting on some volunteers to fix this on the backend side.

Re-pinging for volunteers on this today

I can work on this

Meals: Level 2 nesting and a category name that could span two lines: Level 3 nesting and a category name that could span two lines: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

I don't really understand these instructions, in Old dot, when I add a new category, I just see one input:

Is this saying I should add 2 categories:

Meals
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua
?

Every time you add a colon it makes it a sub-category. This:

Becomes this on OldDot:

This on NewDot:

Every time you add a colon it makes it a sub-category. This:

🤯 that is new to me, thanks for explaining!

Melvin, waiting on some news from the backend side by @aldo-expensify.

No update.

Sorry, I haven't been able to check again on this, I'll try to come back as soon as possible!

I noticed that this is also broken for OldDot. I'm asking in slack to confirm the path we want to take to fix this: https://expensify.slack.com/archives/C02MW39LT9N/p1701396084292819

We can't increase the category max length beyond 255, so we are going with the solution of improving the error feedback.
Working on improving the error returned by the backend, it feels a bit junky the experience because the modal closes and then an error appears in the chat. I think a better and less confusing UX is to have the limit as a form validation that won't allow you to submit the expense.

I put up a draft PR. The solution looks like this:
https://github.com/Expensify/App/assets/87341702/ef51e164-6c43-4e0b-a0f6-3cab99663d8f
Please let me know if you think that is fine to finish the PR (description/videos).

isn't there a way to align the limitation on the backend side?

I'm guessing you are referring to rejecting in the backend (and frontend) a user creating a category longer than 255 because they won't be able to use it anyway.
I think both things can be done independently: the validation proposed above and disallow creating long categories.
The problem with implementing the second part is that categories can be added manually and also automatically from integrations with external services. The part of the integrations can get complicated if we want to provide some feedback about why some categories didn't load. Also, we would have to think about what would we do with long categories that are already in the database.
Considering the complexity of that second part, and that this is an edge case (someone very very very rarely will add such long category), I don't think it is worth it to try the second part and we should only do the proposed front end validation when using the category.

Made PR ready for review: https://github.com/Expensify/App/pull/32394

Got you, makes sense.

This issue didn't update but the PR was pushed to prod on 12/14. Adjusting title to remember to issue payment after 7 day hold.

Summarizing payment on this issue:

Contributor:  no payment, @rezkiy37 with Callstack
Contributor+:  $500, to pay via Upwork - @Ollyws I've extended the offer to you on Upwork, can you please accept?

Upwork job is here: https://www.upwork.com/jobs/~018cfdce1c85555976

All paid, thank you!


A buggy implementation of the TileIterator.

Since we do not differentiate between GlobalTile and SharedTile, a TileIterator should be able to work with both types. However, the current implementation is tightly coupled with SharedTile, which is a bug as shown below
https://github.com/TiledTensor/TiledCUDA/blob/cb7a3361f70fb1edce2c9f858705629bc8a0f305/include/types/tile_iterator.hpp#L73

Add a template parameter to represent different Tile types?

A possible solution could be to have GlobalTile and SharedTile inherit from a common base class. Currently, since GlobalTile and SharedTile exhibit no differences in behavior, the computation results are correct.
I will carefully consider a suitable solution in next modifications.


build(deps): bump github.com/linxGnu/grocksdb from 1.8.10 to 1.8.11

This PR bumps RocksDB in the Dockerfile and should permit the merge of #119
Itr's also been updated to contain #119 for simplicity's sake, and so that we can see the results in CI.

Thanks @faddat ❤


Indentation error on ethereum/utils.py", line 30

    def __call__(self, *args):
        if args not in self.memo:
            self.memo[args] = self.fn(*args)   # <---------- THIS LINE
        return self.memo[args]

A mix of tab and space is used causing
TabError: inconsistent use of tabs and spaces in indentation

Very bad on the developer front allow such bugs to creep into production code.
:(


Notebook 2

In the output of cell 2, the trajectories and distributions seem exchanged

Maybe it's easier to understand if you use two panels for trajectory and histogram, put time on the horizontal axis and x/y on the vertical axis, and put them in this grid
x traj              x dist
y traj              y dist


Parsing bug in some expressions

Example:
// Error
let v = [0.5];
(v[0].sin()).cos()

EXCEPTION: Function not found: sin (i64)

It also produces an analogous exception when using other float functions instead of sin and cos.
// Error
let v = [0.5];
(v[0].atan(1.0)).log(2.0)

EXCEPTION: Function not found: atan (i64, f64)

However, using a float instead of an array of floats, removing the unnecessary brackets, or removing the second float function doesn't result in the exception.
// Ok
let v = 0.5;
(v.sin()).cos()

// Ok
let v = [0.5];
v[0].sin().cos()

// Ok
let v = [0.5];
(v[0].sin())

Tested in:

Rhai Playground
With Rhai 1.13.0 crate in x86_64-unknown-linux-gnu debug and release builds

Hhhmmm... that seems to be a bug with parsing.
Removing the parentheses work correctly... so this ia a parsing problem.

Looks like extra brackets can also produce other types errors where they shouldn't.
On debug builds the maximum expression nesting depth in functions should be 16, but:
let engine = Engine::new();
let mut scope = Scope::new();
let script = r#"fn foo() {
    let v = 0.5;
    if -((-(((v)).tan())).sin()) != 93.29292920983892 {
        return 4;
    } else {
        return 1;
    }
}"#;
let ast = engine.compile(script).unwrap();
let bar = engine.call_fn::<i64>(&mut scope, &ast, "foo", ()).unwrap();
println!("{bar}");

ParseError(ExprTooDeep, 3:15)

Removing either minus sign fixes it tho:
    if -((-(((v)).tan())).sin()) != 93.29292920983892 {
       ^  ^

Looks like extra brackets can also produce other types errors where they shouldn't.

Probably.  It is an error in the parser so the expression is constructed incorrectly.  It may affect other places.
But it is unlikely to affect max expression depth.  Remember, each level of parentheses is a level, and the unary minus operator is itself a level.  You may have just hit the limit.

The fix has landed in #714


Attach updates

Some more attachment love

Codecov Report

Merging #3437 (1f7077f) into development (fa0b768) will decrease coverage by 0.01%.
The diff coverage is 7.78%.

@@                Coverage Diff                @@
##             development    #3437      +/-   ##
=================================================
- Coverage          32.23%   32.22%   -0.02%
- Complexity         12196    12202       +6
=================================================
  Files                263      263
  Lines              52570    52594      +24
=================================================
+ Hits               16946    16948       +2
- Misses             35624    35646      +22

Impacted Files
Coverage Δ
Complexity Δ

sources/ElkArte/Controller/Attachment.php
12.07% <0.00%> (+0.17%)
106.00 <0.00> (-2.00)
:arrow_up:

sources/ElkArte/Graphics/Image.php
43.52% <ø> (ø)
37.00 <0.00> (ø)

sources/ElkArte/Graphics/Manipulators/Imagick.php
1.38% <0.00%> (+0.05%)
51.00 <0.00> (ø)

sources/ElkArte/TemporaryAttachmentsList.php
14.16% <0.00%> (-0.88%)
60.00 <3.00> (+3.00)
:arrow_down:

sources/subs/Attachments.subs.php
13.18% <0.00%> (-0.33%)
0.00 <0.00> (ø)

sources/subs/Messages.subs.php
32.08% <0.00%> (ø)
0.00 <0.00> (ø)

sources/ElkArte/AttachmentsDirectory.php
7.73% <5.52%> (-0.27%)
158.00 <78.00> (+4.00)
:arrow_down:

sources/subs/ManageAttachments.subs.php
8.19% <16.66%> (ø)
0.00 <0.00> (ø)

...Arte/Graphics/Manipulators/AbstractManipulator.php
66.66% <100.00%> (+19.99%)
11.00 <2.00> (+2.00)

sources/ElkArte/Graphics/Manipulators/Gd2.php
55.62% <100.00%> (-1.53%)
65.00 <0.00> (-1.00)

... and 1 more

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 e3517dc...1f7077f. Read the comment docs.

Codecov Report

Merging #3437 (1f7077f) into development (fa0b768) will decrease coverage by 0.01%.
The diff coverage is 7.78%.

@@                Coverage Diff                @@
##             development    #3437      +/-   ##
=================================================
- Coverage          32.23%   32.22%   -0.02%
- Complexity         12196    12202       +6
=================================================
  Files                263      263
  Lines              52570    52594      +24
=================================================
+ Hits               16946    16948       +2
- Misses             35624    35646      +22

Impacted Files
Coverage Δ
Complexity Δ

sources/ElkArte/Controller/Attachment.php
12.07% <0.00%> (+0.17%)
106.00 <0.00> (-2.00)
:arrow_up:

sources/ElkArte/Graphics/Image.php
43.52% <ø> (ø)
37.00 <0.00> (ø)

sources/ElkArte/Graphics/Manipulators/Imagick.php
1.38% <0.00%> (+0.05%)
51.00 <0.00> (ø)

sources/ElkArte/TemporaryAttachmentsList.php
14.16% <0.00%> (-0.88%)
60.00 <3.00> (+3.00)
:arrow_down:

sources/subs/Attachments.subs.php
13.18% <0.00%> (-0.33%)
0.00 <0.00> (ø)

sources/subs/Messages.subs.php
32.08% <0.00%> (ø)
0.00 <0.00> (ø)

sources/ElkArte/AttachmentsDirectory.php
7.73% <5.52%> (-0.27%)
158.00 <78.00> (+4.00)
:arrow_down:

sources/subs/ManageAttachments.subs.php
8.19% <16.66%> (ø)
0.00 <0.00> (ø)

...Arte/Graphics/Manipulators/AbstractManipulator.php
66.66% <100.00%> (+19.99%)
11.00 <2.00> (+2.00)

sources/ElkArte/Graphics/Manipulators/Gd2.php
55.62% <100.00%> (-1.53%)
65.00 <0.00> (-1.00)

... and 1 more

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 e3517dc...1f7077f. Read the comment docs.


Add an Eq instance for LineCap

I am working on purescript-contrib/purescript-drawing#8, and OutlineStyle has a derived Eq instance. This instance breaks when I try to add a field of type LineCap to it. So, I just added a derived instance, since I see no reason why LineCap shouldn't be Eq.

Thanks!


Returning a JS object in a function work incorrectly

From: https://github.com/orientechnologies/orientdb-studio/issues/209
returning a javascript object from a server side function does not work properly (or displays output improperly). See image attached, it breaks the properties of the object into their own object.

fixed a long time ago. Cannot be reproduced in 2.1


Generic Error message from MSIX upload

Type of issue
Missing information
Feedback
To actually see any error messages, you have to manually refresh the page.
The error system is very generic, with no real actionable information.
Here is an example from submitting a .msix that passes the latest Windows App Cert tests:

You must upload at least one package. If you are using market groups, then each market group must have at least one package.
You must provide a package that supports each selected device family (or uncheck the box for unsupported device families). Note that targeting the Xbox device family requires a neutral or x64 package.
The package *.msix is taking a long time to process. If this isn’t completed soon, try refreshing the page, or remove the package and then upload it again. If you continue to see this issue, contact support.
You must fix all package validation errors before submitting.

Clearly there is a deeper root cause that is not being tested for or exposed here.
Page URL
https://learn.microsoft.com/en-gb/windows/apps/publish/publish-your-app/msix/upload-app-packages
Content source URL
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/publish/publish-your-app/msix/upload-app-packages.md
Author
@GrantMeStrength
Document Id
3d76171e-6819-3c62-0225-c01f8633395c

Alright, so I figured out that it doesn't do well with special characters. I as trying to make it so I could drop a shortcut to a special folder on my computer anywhere I wanted, and at first I thought it just couldn't do shortcuts (maybe something to do with a path in a path or something. but I got it to work. And here's the result:
When the folder was named "Impala", it worked great. But if I changed the folder name to "❇Impala❇", it broke it. Furthermore, I think it's an issue not only with the direct folder name, but with any special characters in the delivery path; because when I had it named "Impala" and tried to create it with the template folder on my "C" drive and and the destination on my "D" drive, it wouldn't work, but then it did when I was just going from "C" to "C" (template folder to a folder on my desktop. The thing with that is, I name my files and folders all kinds of wacky names. I use emojis as kind of a coding system for my files. So I name active projects like "⚡Project⚡" and a dead project like "☠Project☠" and finished projects like "🏆Project🏆"
Considering that it worked and worked and worked, and as soon as I added a "❇" it broke, I'm assuming that even when it WAS just named "Impala" on my earlier attempts, it's because it was traveling from "%USERPROFILE%\AppData\Local\Microsoft\PowerToys\NewPlus\Templates" TO "D:\📄Projects📄\Test"
But then suddenly worked traveling to "%USERPROFILE%\Desktop\New folder\Impala" Until of course I changed it to "%USERPROFILE%\Desktop\New folder\Impala❇" at which point it immediately broke again.


[Please Comment]: Serenity as mBaaS solution

Dear @volkanceylan,
I would like to see possibility of utilizing Serenity as Mobile Back-end since it creates API out of the Box
If we could add token authentication, social logins for the API it could become Mobile Backend Service just like Azure Mobile Services,
Although It Need some customization in regards to Offline Sync and Push Notification, Api calls logging per IP, Per User
Just thought, please comment / feedback about Idea

Hi Samdubey,
We are already using Serenity as mobile backend and have no problems. For other nice-to-have features, it could be, there are some plans, but not prioritized and i don't have a timeline.
Serenity will probably have a paid mobile version, though not decided yet.

Thanks for your views


Cannot use with parcel

When I try to start my server with npm and parcel I get the following error in the console:
ol-contextmenu.umd.cjs:8 Uncaught TypeError: Class extends value #<Object> is not a constructor or null
To reproduce:
Put the files I uploaded here mwe.zip in a folder,
then run:
npm install
npm run start
When accessing the website the error prints to the console.
I think the import 'ol-contextmenu/dist/ol-contextmenu.css' line should be import 'ol-contextmenu/ol-contextmenu.css' but that also fails with:
@parcel/core: Failed to resolve 'ol-contextmenu/ol-contextmenu.css' from  './main.js'

Parcel doesn't support  the package.exports attribute. Try including the file extensions and the entire path:
import ContextMenu from 'ol-contextmenu/dist/ol-contextmenu.js';
import 'ol-contextmenu/dist/ol-contextmenu.css';

Thanks! Providing the full path works nicely.


More Middlewares with Configurability

It's really great to have a web framework that's simple & fast.
I think we can push "fast" forward by implementing more Middlewares like Etag, Logging, Jwt Auth, GraphQL & more... with more configuration options.
Also It's good to have some more examples. Thanks.

Feel free to open a PR.

Great. I will let you know. Also what do you think about a simple docs website for fast. we can build it with Lume or Fresh. what do you think?

Also what do you think about a simple docs website for fast. we can build it with Lume or Fresh. what do you think?

For now let's start with JSDoc annotations. However it would be good to have a dedicated site in the near future.

Ok, Great. I will let you know.

Write tests for any new middleware.

See #5 - this was delayed a bit but I am working on some documentation.

I am working on a web framework that uses fast under the hood. So it would be good to write the documentation site with that when it's ready.

I think we should add some more middleware's like

Now we have an Etag & CORS Middlewares, we should work on bringing other types of middlewares like Static Web Sites Serving Middleware, and more...

We have a static file serving middleware however it lacks configuration options.

I will create a PR when I have finished tests for it. just take a look at it in here:
https://github.com/Abiti-936/fast/blob/static-middleware/middleware/static-server.ts

My original goal with fast was to keep the codebase small. I no longer think bundling middleware is aligned with this goal. Feel free to create your own repo for fast middleware.


Fix 'API is returning peers without access_hash' assertion error

Error happens when executing  cargo run --example dialogs or  cargo run --example downloader -- CHAT due to a users with min: true being returned

It also happens for messages.rs (see above) and regarding chat.rs I assumed it can happen too since it deals with users from a chat. I can try to reproduce tomorrow

Alright, if it happens with messages (I missed that) and dialogs it's probably safe to assume it happens elsewhere. Thanks!


Fix bug whereby epiweekly files had the extension twice

e.g. epiweekly_data.csv.csv
This could break the pipeline

Closing because I failed to branch off main


Update PUT URL to include p_guid

master PUT/POSTs to path: /rd/reminders/tasks, which - at least in my account - is 404ing with any set of arguments, including an unmodified Reminder. In a graphical browser, I can see that all PUTs and POSTs that I can generate (completing, creating, editing) go to /pd/reminders/#{p_guid} with no delimiters, like:
/rd/reminders/1234b0e462ac58bbb43b00cb340816f42aad99f5d247d0aacf780d3620978e8f

My suspicion is that all of the Reminder-specific URLs should change to this, but I added it as a new method to be safe since:

I don't know all intended uses of put_reminder/post_reminder, and
My captures from a browser were far from exhaustive

I can say that calling this method/URL with a reminder that has completed_date set does complete the reminder and that as of today, that's what iCloud itself does in at least Chrome.

@adammck any thoughts on this, other than that the tests need to be passing to merge? If you're interested in a co-maintainer, please let me know; I have a vested interest in making sure at least certain parts work. And regardless, thanks!

Sorry that I missed this one. It looks like the CI failure is unrelated to this PR, so I'll go ahead and merge, and fix the build separately. I've been neglecting this repo for a while now, so I'd be very grateful, actually, if you'd be willing to help maintain it. Could you send me an email to discuss that? Your address isn't in your profile (which is probably wise). Thanks for the fix!


Needs to address remote access to a home computer

This article is linked from a Windows 10 Settings dialog box, where it says, "Why allow connections only with Network Level Access?".  So it should include an explanation that this option should not be checked for a computer on home network, if the person wants to connect remotely from a location outside of their home (and off their home network).

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

ID: 71cfbf1a-c5b7-df0f-8194-6ebc03afcc7d
Version Independent ID: f36b567f-aa48-2c8f-4908-b1fe18cd2842
Content: Remote Desktop - Allow access to your PC
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/remote-desktop-allow-access.md
Service: unspecified
GitHub Login: @lizap
Microsoft Alias: elizapo

i love PC

Hi, the article's been updated to be more clear, using the specific example you called out. Thanks for your help!

Am I missing something here? I have connected to my computers at home for years over the Internet having the NLA option enabled (because it's the default) without any issues except maybe the fact that I needed to setup a Remote Desktop Gateway to connect from corporate networks blocking RDP connections


Accessing Library from Objective c project

I would like to access this library from my objective c project. Is there a way to do that? pls hep me :)

If you add the library a bridging header should automatically be generated. I believe #import "ARCL-Swift.h" should work. I'm not sure if @objc tags need to be added though

@thanks I will try this when I integrate this library to my current objective c project.

@NyeinEiEiTun  have you interegate this library in objective c project ?


Support Azure OpenAI API

Hi, any chance you guys make a support to use azure api?

Hi @wangxing7714436 , this is a good idea. I'll look into it.


Update screenshot to address that feature is in GA state, not in a preview

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/media/generation-2/gen1-gen2-select.png
Please, update to avoid confusion!

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

ID: 9145de07-94e5-05bc-d00b-e05723db9163
Version Independent ID: c5d9a3c6-6fc2-837a-8291-2f4b82550d85
Content: Azure support for generation 2 VMs
Content Source: articles/virtual-machines/windows/generation-2.md
Service: virtual-machines-windows
GitHub Login: @laurenhughes
Microsoft Alias: lahugh

@SychevIgor Thanks for pointing this out. I am assigning this to content author for updating the document with updated screenshot.


CAMEL-20152: camel-jetty - Allow to configure the multipart

Fixes https://issues.apache.org/jira/browse/CAMEL-20152
Motivation
In the case of multipart, the content is kept in memory which can lead to an OOME, it is due to the fact that the fileSizeThreshold is set to 0 by default which should mean that the content is stored on disk according to the Jetty Javadoc but it is not what the Jetty code expects.
Modifications:

Proposes new properties to be able to configure the multipart
Add a unit test to ensure that the file content is stored to disk

Due to https://github.com/jetty/jetty.project/issues/10936

Is Camel using Jetty 12 with the ee10 environment?
These changes seem to be for Jetty 11, which is for Servlet 5.0.
This API spec behavior, where fileSizeThreshold value of 0 is documented, first shows up on Servlet 6.0.
That language is not present in the API spec on Servlet 5.0. - https://github.com/jakartaee/servlet/blob/5.0.0-RELEASE/api/src/main/java/jakarta/servlet/annotation/MultipartConfig.java#L65-L70
Jetty 12 on the ee10 environment already supports this spec behavior.

Yes its Jetty 11 in the source, however we are also working on upgrading to Jetty 12 for the upcoming Camel 4.3 release. But older Camel releases are using Jetty 11 and 9.

Note, Jetty 9 is now at End of Community Support.

https://github.com/jetty/jetty.project/issues/7958

Please note that even if it is mentioned only in EE 10, it is actually a clarification see https://github.com/jakartaee/servlet/issues/111, for example, in Glassfish, it is how it has been implemented even in very old versions that is why I proposed it in version 11 but I can understand your point of view.

And IMHO, it makes more sense to consider that a threshold set to 0 is immediately reached instead of never being reached like it was set to Integer.MAX_VALUE which is somehow the current behavior in any version of Jetty


Location submissions often come in twice

Or three times.

Clicking the "living hell" out of the submit button does this. Super easy to repeat. I'll fix it.

https://github.com/scottwainstock/pbm-ios/commit/270b44b6fba5fde042092c6a7c7037d018f85a7b

So the button grays out? Seems cool.

This seems to have worked great. No more dupes!


Updated the navbar of the cart page and the footer of the cart page #637 and #638

Updated the navbar of the cart page
Added footer to the cart page
Added styling to footer to make it better

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
Closes #637 and #638
Description
[Please include a brief description of the changes or features added]
Type of PR

[X] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]
This PR resolves 2 issues.. #637 and #638
@arghadipmanna101 Please label PR as it resolves 2 issues.. Please consider it while labelling.. Assign me this PR

There have some conflict issue check it once and then make a new PR. ok

@arghadipmanna101 I have resolved the conflicts.. please merge this PR and label it under GSSoC


Get rid of "static"

As of now, most injectors (if not every injector) that offers "Manual map" injection method, while injecting the library will crash the target process.
The most obvious reason is the static keyword used in few places (for example Hooks::Present method, szWatermark variable, or all original hooked methods).
Looks like the "Manual map" injection method causes the static variables not to be initialized properly, and leads into crash.

Kind of a good solutions seems to be replacing them all with some kind of global variables container, that will be instantiated once cheat is injected, and before hooks are created, and released after hooks are restored.

thats because whatever mapper ur using isnt calling all tls callbacks and thus will leave them uninitialized. a proper mapper wont have this problem.


feat(styles): add custom theme for primeng

 Quality Gate failed
Failed conditions  D Reliability Rating on New Code (required ≥ A)  9 New Code Smells (required ≤ 0)
See analysis details on SonarCloud
 Catch issues before they fail your Quality Gate with our IDE extension  SonarLint

9 issues come from primeng base theme, should we correct them or exclude the folder from sonar analysis?
The 18 others are to style icons targeting the component tag selector, we probably have to mark them as false positive.

 Quality Gate failed
Failed conditions  D Reliability Rating on New Code (required ≥ A)  9 New Code Smells (required ≤ 0)
See analysis details on SonarCloud
 Catch issues before they fail your Quality Gate with our IDE extension  SonarLint

9 issues come from primeng base theme, should we correct them or exclude the folder from sonar analysis?
The 18 others are to style icons targeting the component tag selector, we probably have to mark them as false positive.

As they are in the repo, I would have said correct them, but we also don't want that those files derive too much from the original as it's hard to see changes when upgrading.

 Quality Gate failed
Failed conditions  D Reliability Rating on New Code (required ≥ A)  9 New Code Smells (required ≤ 0)
See analysis details on SonarCloud
 Catch issues before they fail your Quality Gate with our IDE extension  SonarLint

9 issues come from primeng base theme, should we correct them or exclude the folder from sonar analysis?
The 18 others are to style icons targeting the component tag selector, we probably have to mark them as false positive.

As they are in the repo, I would have said correct them, but we also don't want that those files derive too much from the original as it's hard to see changes when upgrading.

I just configured Sonar to ignore /icon$/ selectors and fixed the other issues.


Something went wrong with the "Slider" component example

Hey,
I have noticed that something went wrong with the slider example in your's website -
http://semantic-ui.com/modules/slider.html
It doesn't work and there is a JS error via the console.
please check it out :)

OMG, I am so glad this even exists.  Would love to see it working.

Just confirming because we really need this, is this officially supported?

Duplicate, please see:
#3519, #4295, #5295, #4863, #3495


Update text?

@terrajobst ... Maybe scan the front page and give it a quick update?

@MattWhilden is there still anything to do? I think @richlander already did that.

Looks great. Thanks!


Setup initial structure of repository

Tried Java 17 but that won't build, therefore staying with Java 11 for the moment.

Need to fix git client settings, will create a new pull request.


SFML 2.3.2

If I set setPlayingOffset() over more than 50% of .flac file, music restarts playing.
For example: music.setPlayingOffset(sf::seconds(200); (music duration is equal 300 seconds). This causes playing music from the beginning.
If I open .ogg file, everything works well- I can set every value which is less than music.getDuration();
What is the problem?

Please open a thread on the forums and include a complete and minimal example. Be sure to include an audio file that shows the problem and information about your copy of SFML. We try to keep the tracker for confirmed issues/features.

As @zsbzsb said and as it's stated in the contribution guidelines, it would be great if you could open a thread on the official forum about this issue.


gaby: record actions

Keep a record of all actions performed (in a DB).

@jba The feature is already in prod. Can we close this?


Pass command line arguments to process when starting.

Is there a way to pass command line arguments to the process I'm starting using grunt-forever?

I stumbled across the same issue, am going to have to use grunt-forever-multi instead i think until this feature arrives

+1


Scroll snap

Could be nice to snap so that each project in project list view appears right after the logo, so that the item is viewed as intended
Could use https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-snap-type
Maybe same could be applied to project detail view

Moved to https://github.com/davidlj95/chrislb/discussions/320


Icingabeat v.6.3.3 does not send the hostname for the check, instead send own hostname

After installing icingabeat (6.3.3) on a complete new machine, with minimal changes to the icingabeat.yml and outputting to a completely new elasticsearch index (5.5), accessing an icinga2     (2.9.1), icingabeat will log checkresults with the name of the host running icingabeat as host.name:

My icingabeat.yml (with comments, hostnames and credentials redacted):
icingabeat:
  host: "XXXX"
  port: 5665
  user: "XXXX"
  password: "****"
  ssl.verify: false
  eventstream.types:
    - CheckResult
    - StateChange
    - Notification
    - AcknowledgementSet
    - AcknowledgementCleared
    - CommentAdded
    - CommentRemoved
    - DowntimeAdded
    - DowntimeRemoved
    - DowntimeStarted
    - DowntimeTriggered

  eventstream.filter: ""
  eventstream.retry_interval: 10s
  statuspoller.interval: 30s
setup.dashboards.enabled: false
setup.kibana:
output.elasticsearch:
  hosts: ["XXXX:9200"]
  protocol: "https"
  username: "XXXX"
  password: "*****"

Representative checkresult (in json):
{
  "_index": "icingabeat-6.3.3-2018.09.12",
  "_type": "doc",
  "_id": "AWXO07xNOFh-eQsJ_2M4",
  "_version": 1,
  "_score": null,
  "_source": {
    "@timestamp": "2018-09-12T17:27:45.615Z",
    "check_result": {
      "active": true,
      "type": "CheckResult",
      "execution_end": "2018-09-12T17:25:24.348Z",
      "check_source": "icinga2-sat...",
      "state": 0,
      "vars_before": {
        "reachable": true,
        "state": 0,
        "state_type": 1,
        "attempt": 1
      },
      "exit_status": 0,
      "output": "OK",
      "schedule_end": "2018-09-12T17:25:24.348Z",
      "ttl": 0,
      "schedule_start": "2018-09-12T17:25:23.970Z",
      "execution_start": "2018-09-12T17:25:23.970Z",
      "vars_after": {
        "reachable": true,
        "state": 0,
        "state_type": 1,
        "attempt": 1
      },
      "command": [
        "/usr/lib/nagios/custom_plugins/check_multi",
       "..."
      ]
    },
    "beat": {
      "version": "6.3.3",
      "name": "icingabeat-stg-01",
      "hostname": "icingabeat-stg-01"
    },
    "host": {
      "name": "icingabeat-stg-01"
    },
    "service": "$SERVICENAME",
    "timestamp": "2018-09-12T17:25:24.352Z",
    "type": "icingabeat.event.checkresult"
  },
  "fields": {
    "check_result.execution_end": [
<PHONE_NUMBER>348
    ],
    "check_result.schedule_end": [
<PHONE_NUMBER>348
    ],
    "@timestamp": [
<PHONE_NUMBER>615
    ],
    "check_result.execution_start": [
<PHONE_NUMBER>970
    ],
    "check_result.schedule_start": [
<PHONE_NUMBER>970
    ],
    "timestamp": [
<PHONE_NUMBER>352
    ]
  },
  "sort": [
<PHONE_NUMBER>615
  ]
}

Expected Behavior
Somewhere in the document should the hostname for the checkresult (notification, ...) be analog to the service.
Current Behavior
All hostnames will be the icingabeat hostname
Steps to Reproduce (for bugs)

install icingabeat as documented
configure icingabeat with access to icinga & elasticsearch
let icingabeat create the elasticsearch template icingabeat setup
restart icingabeat
create index patterns in kibana (and ignore error while importing kibana dashboards)
check resulting documents in Kibana

Context
We can not use icingabeat 6.3.3 as there is no way to know to which of our hosts the messages are related to.
Your Environment

Beat version (icingabeat -version): icingabeat version 6.3.3 (amd64), libbeat 6.3.3
Icinga 2 version (icinga2 --version): r2.9.1-1
Elasticsearch version (curl -XGET 'localhost:9200'): 5.5.0
Logstash version, if used (bin/logstash -V): 5.6.7 (not configured to be used)
Kibana version, if used (curl -XGET http://localhost:5601/status -I):  5.5.0
Operating System and version: Debian GNU/Linux 9.5 (stretch)

I can confirm this issue. We had to downgrade to 6.1.1 as a workaround.

on my end downgrade makes elastic reject the fields from 6.1.1

Aparently this seems to be connected to the upgrade to libbeat 6.3:

As a solution for https://github.com/elastic/beats/issues/7050, we're adding a host.name field to
all events. This is duplicate information from beat.name,
but is used to avoid the mapping conflict and to slowly
introduce the "host as an object" approach.

https://github.com/elastic/beats/pull/7051

Same issue as in #26


Error: add site dependencies: load resources: loading translations

What happened?
Hello!
I've just downloaded Congo Hugo theme and, as I'm a Windows user, followed the manual installation steps to use it.
The problem is whenever I type hugo server to see my site running, I receive the following error message:
Error: add site dependencies: load resources: loading translations: "C:\Users\Daniel\Hugo\sites\mywebsite\themes\congo\i18n\bn.yaml:1:1": failed to load translations: unable to parse translation #0 because invalid plural category input_placeholder map[id:search translation:map[close_button_title:বন্ধ করুন (Esc) input_placeholder:খুঁজুন open_button_title:খুঁজুন (/)]]
Important: I have created a blank site to try Congo, by entering hugo new site mywebsite, so no other files or folders resided at that location beforehand. It is, therefore, quite odd to have this message shown.
Can someone please advise me?
Thanks in advance.
Theme version
V2.1.0
Hugo version
v0.91.2
What browsers are you seeing the problem on?
Chrome
Relevant Hugo log output
Error: add site dependencies: load resources: loading translations: "C:\Users\Daniel\Hugo\sites\mywebsite\themes\congo\i18n\bn.yaml:1:1": failed to load translations: unable to parse translation #0 because invalid plural category input_placeholder map[id:search translation:map[close_button_title:বন্ধ করুন (Esc) input_placeholder:খুঁজুন open_button_title:খুঁজুন (/)]]

My mistake. Found out I had two hugo binaries locally installed in different path locations. One of them was pretty outdated.
Removing it and installing latest Hugo release solved the problem.


No OnixLabs packages exist on www.nuget.org

You say that there are two packages:

OnixLabs.Security.Cryptography
OnixLabs.Core

But none of them exist on nuget.org

@jesuslpm I don't publish to nuget.org. Instead the packages are published to GitHub's nuget package management repository: https://github.com/orgs/onix-labs/packages?repo_name=onixlabs-dotnet

@MrMatthewLayton I know this issue was closed awhile back but I wanted to provide some feedback on why this choice is problematic. Publishing these artifacts on GitHub Packages severely limits the scope of adoption as an authentication token is required to access packages even if they are on a public repository.
I had plans to replace the dependency that my library cuid.net has on BouncyCastle.Cryptography with OnixLabs.Security.Cryptography but cannot because of this limitation as I cannot guarantee the consumers of my library have access to GitHub.com either directly or on their CI/CD pipelines.

@xaevik Thanks for that feedback, that's useful to know. Let me see what I can do about publishing to nuget.org. Last time I tried I was tied in knots just trying to authenticate my nuget account, and they seem to have horrific support for that.
Out of interest, which components of the cryptography library were you interested in using?

@MrMatthewLayton you can reference https://github.com/visus-io/cuid.net/blob/main/.github/workflows/release.yaml as a guide if you'd like as it takes care of packing and publishing on NuGet.

@xaevik Thanks. I'll see what I can do over the weekend.

@xaevik Just to keep you in the loop, I haven't forgotten about this. I've set up a new account for nuget.org, so I will aim to build and release the packages asap, time permitting.

@jesuslpm @xaevik Both packages have now been released to nuget.org!

OnixLabs.Core
OnixLabs.Security.Cryptography

Apologies for the holdup. I never really expected that I would get much interested in them. I will likely release version 6.0.0 next year, and it will likely target .NET 8.0

@MrMatthewLayton phenomenal, I will conduct testing with them against cuid.net later this week as that would very much lower the size of the transient dependencies and allow greater portability.
I am not sure how much of the loop you've been in with regards to SHA-3 support in .NET but it is making it (partially) into .NET 8 (and subsequently 9). You can review dotnet/runtime#20342 and dotnet/runtime#84132 for additional details but the gist of it is that they will expose an IsSupported boolean property for all SHA-3 algorithm types to let you know if the underlying platform supports it. The scope of the underlying OS support is still basically limited though:

Windows 11 Build 25324 or higher (FIPS-202 compliant)
GNU/Linux with OpenSSL >= 1.1

Apple Crypto does not support SHA-3 still and the dotnet team chose not to depend on OpenSSL for that platform as its not fully native but at least it's now a step in the right direction.

@MrMatthewLayton
Great news, thank you very much.

@xaevik

I am not sure how much of the loop you've been in with regards to SHA-3 support in .NET but it is making it (partially) into .NET 8 (and subsequently 9)...

Yes, I think this is the moment we've all been waiting for. When I first encountered SHA-3, it was the Keccak version which is what Ethereum uses (or at least, did at the time. Perhaps they've updated to use FIPS-202 now). There is a SHA-3 nuget package, but IIRC (I haven't looked at it for a LONG time) it was based on BouncyCastle and implemented the Keccak team variant.
My implementation is the FIPS-202 standard. My plan, once SHA-3 makes its way into .NET is to refactor my implementation, such that it will first check if its implemented by the OS/Platform and use that. If not, it will fall back to using the managed version that I've implemented.

@MrMatthewLayton the implementation worked beautifully, and a new release is out for consumption. Thanks again for making this available on nuget.

@xaevik Amazing work! Thank you for letting me know. I think this is the first time one of my open-source projects has been used in the wild :)


Class missing in stubs

Package installed with composer: abraham/twitteroauth
(I need the stubs as I'm doing something like you do with the WP stubs which do not use composer, so I need stubs)
generate-stubs --force --functions --classes --interfaces --traits --out="a.php" --no-interaction twitter
(package is installed in twitter folder)
It generates the stubs (10 classes), but stubs for class TwitterOAuth extends Config are missing.
But e.g. class TwitterOAuthException extends \Exception and all other classes are there (total 11 classes, but only 10 have stubs created).
Is this a bug or is there something I'm doing wrong?

Hello @kkmuffme!
Try to generate from that specific file.
It is very easy to debug this project.

If I run it for that file only, there are no errors either (but no stubs generated) it even says "OK":
PHP Stubs Generator
===================

 [OK] Stubs written to /some/path/a.php

 ----------- --------- ------------ -------- ----------- ---------
  functions   classes   interfaces   traits   constants   globals
 ----------- --------- ------------ -------- ----------- ---------
  0           0         0            0        0           0
 ----------- --------- ------------ -------- ----------- ---------

and the output file contains only:
<?php

Try debugging in this try/catch block
https://github.com/php-stubs/generator/blob/53c2cbb0ab3049d73d4490d47c9f2f9028580ef8/src/StubsGenerator.php#L133
Please see #4

I'm also experiencing the same issue. When manually trying to generate the stubs from the command line I get the correct number of stubs recognized, but when I check the file, it's empty.

When I don't specify out parameter I don't get anything out.
No error is thrown.
I var dumped the visitor in the StubsGenerator.php, and I can see the correct class and traits mentioned, the $unparsed variable is empty, which is ok.
Not sure why nothing is getting parsed out.

My PHP parsing is not strong, so I'll wait for a fix, but when you'll have something feel free to ping me to test it 👍🏼

$ vendor/bin/generate-stubs --functions --classes --interfaces --traits src/Helpers/ | wc -l
909

Would a new config switch for that behaviour (include "existing" things) be useful? Maybe such issues can than be avoided

I'm sorry, Martin! This is a highly dangerous ⚡ fork for php-stub organization stubs only.
Without php-stubs this would be https://github.com/GiacoCorsiglia/php-stubs-generator


Failed to delete actual stack-scoped volume.

Steps to reproduce:

create a service using rancher cli

version: '2'
services:
  coo:
    image: ubuntu
    stdin_open: true
    scale: 2
    volumes:
    - daishan-re:/mydata
volumes:
  daishan-re:
    driver: rancher-ebs
    driver_opts:
      size: 1

Delete the whole stack. This cause cattle to delete container and volume at the same time.
The log in rancher-agent:

5/2/2017 10:41:18 PMtime="2017-05-03T05:41:18Z" level=info msg="Received event: Name: storage.volume.remove, Event Id: d92410f6-69e4-4156-9e1c-bd3377d25776, Resource Id: 1vspm2437"
5/2/2017 10:41:18 PMtime="2017-05-03T05:41:18Z" level=info msg="Received event: Name: compute.instance.deactivate, Event Id: 1af1d497-fe6c-430f-b9f9-015305afc0f4, Resource Id: 1ihm2170"
5/2/2017 10:41:18 PMtime="2017-05-03T05:41:18Z" level=info msg="Received event: Name: compute.instance.deactivate, Event Id: 48f666d1-1e7e-4193-8ff6-256e05821bd5, Resource Id: 1ihm2171"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=warning msg="Failed to remove volume name [compose-tes1t_daishan-re_6215a]. Tried three times and failed. Error msg: [Error response from daemon: Unable to remove volume, volume still in use: remove compose-tes1t_daishan-re_6215a: volume is in use - [bd3e830f2fb78560fe0fe49bbdb284749253a8dde38d98727b1ab936d86c7227, c0028330544eb774bd72bce0ddc3b571b659ef2bd5af4a08107a24c266e0d30d] Error response from daemon: Unable to remove volume, volume still in use: remove compose-tes1t_daishan-re_6215a: volume is in use - [bd3e830f2fb78560fe0fe49bbdb284749253a8dde38d98727b1ab936d86c7227, c0028330544eb774bd72bce0ddc3b571b659ef2bd5af4a08107a24c266e0d30d] Error response from daemon: Unable to remove volume, volume still in use: remove compose-tes1t_daishan-re_6215a: volume is in use - [bd3e830f2fb78560fe0fe49bbdb284749253a8dde38d98727b1ab936d86c7227, c0028330544eb774bd72bce0ddc3b571b659ef2bd5af4a08107a24c266e0d30d]]"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=info msg="rancher id [1vspm2437]: Volume with name [compose-tes1t_daishan-re_6215a] has been removed"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=info msg="Reply: d92410f6-69e4-4156-9e1c-bd3377d25776, storage.volume.remove, 1vspm2437:volumeStoragePoolMap"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=info msg="Received event: Name: storage.volume.remove, Event Id: c80c77de-f833-46c5-9bc4-2b72bdd3f470, Resource Id: 1vspm2437"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=info msg="rancher id [1vspm2437]: Volume with name [compose-tes1t_daishan-re_6215a] has been removed"
5/2/2017 10:41:22 PMtime="2017-05-03T05:41:22Z" level=info msg="Reply: c80c77de-f833-46c5-9bc4-2b72bdd3f470, storage.volume.remove, 1vspm2437:volumeStoragePoolMap"
5/2/2017 10:41:28 PMtime="2017-05-03T05:41:28Z" level=info msg="rancher id [4062]: Container with docker id [bd3e830f2fb78560fe0fe49bbdb284749253a8dde38d98727b1ab936d86c7227] has been deactivated"
5/2/2017 10:41:28 PMtime="2017-05-03T05:41:28Z" level=info msg="Reply: 1af1d497-fe6c-430f-b9f9-015305afc0f4, compute.instance.deactivate, 1ihm2170:instanceHostMap"
5/2/2017 10:41:28 PMtime="2017-05-03T05:41:28Z" level=info msg="rancher id [4063]: Container with docker id [c0028330544eb774bd72bce0ddc3b571b659ef2bd5af4a08107a24c266e0d30d] has been deactivated"
5/2/2017 10:41:28 PMtime="2017-05-03T05:41:28Z" level=info msg="Reply: 48f666d1-1e7e-4193-8ff6-256e05821bd5, compute.instance.deactivate, 1ihm2171:instanceHostMap"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="Received event: Name: storage.volume.remove, Event Id: 535b7b40-be0b-407a-a76a-7bbcc6c1fe08, Resource Id: 1vspm2438"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="rancher id [1vspm2438]: Volume with name [] has been removed"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="Reply: 535b7b40-be0b-407a-a76a-7bbcc6c1fe08, storage.volume.remove, 1vspm2438:volumeStoragePoolMap"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="Received event: Name: storage.volume.remove, Event Id: 79e42c47-01c8-4016-805d-fac7a419fbba, Resource Id: 1vspm2439"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="rancher id [1vspm2439]: Volume with name [] has been removed"
5/2/2017 10:41:29 PMtime="2017-05-03T05:41:29Z" level=info msg="Reply: 79e42c47-01c8-4016-805d-fac7a419fbba, storage.volume.remove, 1vspm2439:volumeStoragePoolMap"

The EBS volume is not deleted in AWS.

Hello , Is there any workaround i can apply to avoid this issue.. I am having same behavior on 1.6.0

NOTE: the fix is for 2.0 only. will need a completely different fix for 1.x

This code was actually in the last release. There was another issue tracking this. So, this doesnt necessarily need validated for end of july

Tested with rancher v1.6.8-rc1 using EBS 0.3.0. Created stack scoped ebs volume as mentioned above. Deleted the stack with services using ebs volume. The stack was successfully deleted in AWS.


docs: update OCR pre-annotations notebook

missing link to store_with_ocr.gif. The file is added in this PR

@PierreLeveau  we can merge


Make flakehell work with flake8 4.0.x

EDIT 2: Although this PR works in most cases, I have since discovered that it breaks the flakehell plugins call. As there was no feedback on this PR from the maintainer since it was raised and no response to this issue, I made a PR in another fork that has a better governance structure. It was merged and released on PyPI and hence that fork (flakeheaven 0.11.0) already has 4.0.x support: https://pypi.org/project/flakeheaven/
EDIT: all tests now pass
Until this PR is merged, you can use it by replacing the flakehell dependency with flakeheaven. For example if you use tox, it could have a section like:
[testenv:lint]
wheel_build_env = py38
deps =
    flakeheaven
    flake8
    flake8-isort
    flake8-black
commands =
    flakeheaven lint src tests

All tests now pass

@sgaynetdinov Are you the maintainer of flakehell? If not, do you happen to know who is looking at merging PRs?

For now, if you wish to use this PR, you can replace the flakehell dependency with git+git://github.com/mcarans/flakehell.git#egg=flakehell. For example if you use tox, it could have a section like:
[testenv:lint]
wheel_build_env = py38
deps =
    git+git://github.com/mcarans/flakehell.git#egg=flakehell
    flake8
    flake8-isort
    flake8-black
commands =
    flakehell lint src tests

For those using pre-commit, you can change your flakehell entry to:
- repo: https://github.com/mcarans/flakehell
  rev: 1b84f4dd6c16232b5c0c6206511427676ab55f5b
  hooks:
    - id: flakehell

@sgaynetdinov is there anything the community can do to speed up the merging of this contribution?

For all who are watching this PR, I raised an issue a while ago entitled "Is this project no longer maintained?" https://github.com/flakehell/flakehell/issues/25 where you can see my attempts to contact the current maintainer to get this PR merged.

Closing as this project has been superceded by FlakeHeaven.


Upgrate to allow Rails 4.2 for Locomotive 3

Getting the following message when attempting to install locomotivecms/engine from master:
Bundler could not find compatible versions for gem "rails":
  In Gemfile:
    locomotive-heroku (~> 0.1.0) ruby depends on
      rails (~> 3.2.13) ruby

    rails (4.2.0)

+1, same issue here.


SQLite Script syntax error

Error when executing the SQL script:
L'exécution s'est terminée avec des erreurs.
Résultat : near "UPDATE": syntax error
À la ligne 314 :
INSERT INTO statistics (state, sum, metadata_id, created_ts, start_ts)
SELECT new_sum, new_sum, sensor_id, ts, ts FROM STATS_NEW WHERE true
ON CONFLICT DO UPDATE

I would need some more information regarding what you are trying to do. This is not much to go on.
The error has something to do with the previous update statement (before line 314).
What version of DBbrowser are you using?

DBBrowser Version 3.12.2
I've tried with those 4 files :

elec_feed_in_tariff_1_high_resolution.csv
elec_feed_out_tariff_1_high_resolution.csv
gas_high_resolution.csv
water_high_resolution.csv

This is the code that I change before execution:
/*                          name                                sensor_id correction cutoff_new_meter cutoff_invalid_value */
INSERT INTO SENSORS VALUES ('sensor_id_gas',                    11,        1.0,    25.0,            1000.0); /* Change */
INSERT INTO SENSORS VALUES ('sensor_id_elec_feed_in_tariff_1',  3,        1.0,    25.0,            1000.0); /* Change */
INSERT INTO SENSORS VALUES ('sensor_id_elec_feed_out_tariff_1', 6,        1.0,    25.0,            1000.0); /* Change */
INSERT INTO SENSORS VALUES ('sensor_id_water',                  2,      1.0,    25.0,            1000.0); /* Change */

Executed the line alone and got the following error:
UNIQUE constraint failed: statistics.metadata_id, statistics.start_ts
Looks like there are duplicate ts inside of STATS_NEW which might be the cause of the error.
Also line 238 of the script, looks like it should be SELECT value, new_sum, sensor_id, ts, ts FROM STATS_NEW WHERE true instead of SELECT new_sum, new_sum, sensor_id, ts, ts FROM STATS_NEW WHERE true

It seems like that you had an earlier failed run and did not revert any changes.
Could you start with the original database and perform the steps again.

new_sum is not the same as value for me. I moved in into my house while the meter already had a couple kWh. The value starts at x kWh while the sum starts at 0.
The temp.new_stats table contains data from HA and the new values. The insert statement fails for me because it already has entries in the statisticstable for common value of ts. I've tried to delete all of the entries from statistics after creating temp.new_stats and before executing the insert statement. I also had to remove the ON CONFLICT DO UPDATE SET sum = excluded.sum part because of the syntax error. Then only it works.
I don't think the data I'm using has anything special in it, I've reduced the values to the bare minimum for testing purpose and I observe the same.

The script copies the existing data from the statistics table for the specified sensor into the STATS_NEW table. After calculating the new sum it copies the new records and updates any existing records in the statistics table. By removing the ÒN CONFLICT the existing records are not updated anymore which results in incorrect values.
I checked your screenshot and saw that you have rows with NULL values for the sensor_id column for the STATS_NEW table. This should not be possible and that is causing the issue further down the road in the script. We have to determine why you have NULL values in the STATS_NEW table.

"""I checked your screenshot and saw that you have rows with NULL values
for the sensor_id column for the STATS_NEW table. This should not be
possible and that is causing the issue further down the road in the script.
We have to determine why you have NULL values in the STATS_NEW table"""
That was the first time around. After dropping the table and trying what I
said last, it worked.
I know removing the ON CONFLICT will not update the existing record,
that's why I preemptively remove them from the db prior to inserting them.
The ON CONFLICT part still gives a syntax error.
On Mon, Jun 3, 2024, 23:14 Patrick Vorgers @.***> wrote:

The script copies the existing data from the statistics table for the
specified sensor into the STATS_NEW table. After calculating the new sum
it copies the new records and updates any existing records in the
statistics table. By removing the ÒN CONFLICT the existing records are
not updated anymore which results in incorrect values.
I checked your screenshot and saw that you have rows with NULL values for
the sensor_id column for the STATS_NEW table. This should not be possible
and that is causing the issue further down the road in the script. We have
to determine why you have NULL values in the STATS_NEW table.
—
Reply to this email directly, view it on GitHub
https://github.com/patrickvorgers/Home-Assistant-Import-Energy-Data/issues/33#issuecomment-2146134931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOMVQVM2O5RASXGVFZRW5Y3ZFTMCDAVCNFSM6AAAAABIVEZBKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGEZTIOJTGE
.
You are receiving this because you authored the thread.Message ID:
<patrickvorgers/Home-Assistant-Import-Energy-Data/issues/33/2146134931@
github.com>

Okay good to read that you found a workaround.
I updated the script to make it more robust, handling invalid data (null values, duplicate timestamps). This may resolve your issue.
For now I will close the issue.

The ON CONFLICT DO part is still giving me a syntax error. Any way you could try to repro with a SQLite db?

@sudomax did you manage to test the above?

Still the same error. I'm not comfortable sharing the database, feel free to close the issue. Thank you


Remove migrated intg tests develop

https://github.com/MinaProtocol/mina/pull/12379

!ci-build-me

some merge stuff got the dev world branch all messy, closing this and starting afresh


Config My Dns

Hey,
I can't configure my DNS access, do you have any idea how to do it?
I added in my config: verif.mayeda.ga (the domain) and in my dns access the ip address of the hosting of my bot to the domain is it good?
Thanks in advance !

This would be the correct DNS.

Closing this, reopen if you need more help.

I'm sorry, but when I configure my dns, it returns 404 with the url verif.mayeda.ga/verif/. Could you help me

It will return 404 until you get sent a link when you join the server.

my url verif.mayeda.ga works but once the code is added it returns 404 :/

you should make a tuto for people who do not use it in localhost

its should be verify btw

yes, I did everything right but adapted to my bot (which does not change anything because in localhost it works)
What you need to know is that my bot is hosted at home for now (I'm buying a vps tomorrow) and my site is on a plesk access.
In my config.js I put my domain mayeda.ga so in the embed it says https://mayeda.ga/verify/ but when I click on it the site sends me back my 404 page. When I change my url to localhost/verify/code it works. So I think that the server and the site must be hosted on the same machine for your code to work, or I'm wrong.
But if you would have a solution because I'm really not very good for anything related to the website

Correct, the site and bot must be on the same server. Only one machine is needed.


New version: Expectations v1.4.0

Registering package: Expectations
Repository: https://github.com/QuantEcon/Expectations.jl
Created by: @arnavs
Version: v1.4.0
Commit: e43d3596e89223de31fad8858f43167157560712
Reviewed by: @arnavs
Reference: https://github.com/QuantEcon/Expectations.jl/commit/e43d3596e89223de31fad8858f43167157560712#commitcomment-37440224

This should be closed.


Artifact Name Using teamcity build Number

Hi @oledid
I tried to change the build number using teamcity-build-number-cli,It is working fine.But when i try to export the Artifact using the %build.number%.I am not getting the same number as in Build number for the build.
For example.
My artifact path:
%project_path%\dist*.crx=>sourecplugin-%build.number%.crx
Expected:
sourceplugin-<IP_ADDRESS>.crx
46 is build counter value
Actual:
sourceplugin-0.3.0.{build_number}.crx

Hi
You can probably work something out using %build.counter% instead of %build.number% in the artifacts path. Or combine them.

Hi @oledid
Thank s for the response.
I have tried out the suggestions you have give.
When I am using %build.counter% I am getting sourceplugin.46.crx
When I am using %build.counter% I am getting sourceplugin-0.3.0.{build_number}.crx
When I am combined  both of them I am getting sourceplugin-0.3.0.{build_number}.46.crx
Actual output I am expecting
sourceplugin-<IP_ADDRESS>.crx


[CosmosDB-preview] Update restorable table API

Consuming new Python package that uses 2022-05-15-preview swagger.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

CosmosDB


add "why become an ambassador" section

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please chose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

thanks @andronovhopf !


wasmtime: backport to release-22.05

Description of changes
Backports wasmtime 0.39.1 (mainly https://github.com/NixOS/nixpkgs/pull/187702 and the rest of commits). It also backports the fact that this package is not broken, but a false positive in the way the Hydra infrastructure is set up.
These backports do not contain any breaking change.
More information in the commit d97b6efa79a219b6fcdbb90e7f9f514f9c175579.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

/cc @nomeata

changelog: https://github.com/bytecodealliance/wasmtime/blob/main/RELEASES.md
does

Some methods on the Config structure now return &mut Self instead of Result<&mut Self> since the validation is deferred until Engine::new: profiler, cranelift_flag_enable, cranelift_flag_set, max_wasm_stack, async_stack_size, and strategy. https://github.com/bytecodealliance/wasmtime/pull/4252 https://github.com/bytecodealliance/wasmtime/pull/4262

constitute a breaking change?

The manual requires you to use git cherry-pick -x in backports.

Missed that, first time backporting. Done.

constitute a breaking change?

We briefly discussed this on the chat; given rust is vendored in nixpkgs this should not constitute an issue. Being completely strict it would be a breaking change, but I think it does not apply strictly given rust dependencies are vendored.

@GrahamcOfBorg build wasmtime


Implement Sample HIU

As a developer, I would like to have a sample hiu which would demonstrate how to use wrapper apis exposed for an HIU.

This has been taken care of.


Add a section about setting up Available locales in the readme

Hello @MittchoBaroco,
I don't think this section is needed, seems to be the Rails way to doing it, and already handled in official Rails guide. Why you think this section is needed and has a place in our README ?
But if this section can help you configuring Komponent, I am agree to let it. I let @spone check at it to have a second thought about adding it into readme.

Well for the story, I didn't know that yesterday because I rarely use internationalization, so I generate my two first components without the whitelisted locales.
So yes it's just a shortcut, but I guess it can save time for some users.


Change data structure order to mirror beacon state property order

I'm not sure what the logic behind the sorting of the Misc dependencies data structures is but this PR changes the order to be more inline with the order they're used in Beacon State.
I'm always confused on the order whenever I check the spec so hopefully this makes it a tad more consistent.
If something like this is not needed feel free to let me know :)

Due to the way we build the spec, the datastructures need to be sorted topologically (any dependencies coming earlier). That's why we have this crappy "Misc" category.

I think Carl fixed this in #1061. :)


Scaling can trigger endless cleanup loop

What happened?
After a scaling operation cluster went into a bad state of an endless loop of triggering cleanups, cleanup is triggered but is reported back as failed in EP, due to this error the API call DatacenterScalingUp state is not reset causing another multiple round of cleanups.
{"level":"error","ts":1632913707.7406483,"logger":"reconciliation_handler","msg":"unable to perform request to Node Management Endpoint","requestNamespace":"prod","requestName":"xxxx-dc1","loopID":"64424726-be90-45af-98a8-2b018e71de1b","namespace":"prod","datacenterName":"xxxxx-dc1","clusterName":"xxxx-dse","error":"Post \"http://x.x.x.x:8080/api/v0/ops/keyspace/cleanup\": context deadline exceeded","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/datastax/cass-operator/operator/pkg/httphelper.callNodeMgmtEndpoint\n\t/cass-operator/operator/pkg/httphelper/client.go:349\ngithub.com/datastax/cass-operator/operator/pkg/httphelper.(*NodeMgmtClient).CallKeyspaceCleanupEndpoint\n\t/cass-operator/operator/pkg/httphelper/client.go:237\ngithub.com/datastax/cass-operator/operator/pkg/reconciliation.(*ReconciliationContext).cleanupAfterScaling\n\t/cass-operator/operator/pkg/reconciliation/reconcile_racks.go:2090\ngithub.com/datastax/cass-operator/operator/pkg/reconciliation.(*ReconciliationContext).CheckClearActionConditions\n\t/cass-operator/operator/pkg/reconciliation/reconcile_racks.go:2135\ngithub.com/datastax/cass-operator/operator/pkg/reconciliation.(*ReconciliationContext).ReconcileAllRacks\n\t/cass-operator/operator/pkg/reconciliation/reconcile_racks.go:2353\ngithub.com/datastax/cass-operator/operator/pkg/reconciliation.(*ReconciliationContext).calculateReconciliationActions\n\t/cass-operator/operator/pkg/reconciliation/handler.go:166\ngithub.com/datastax/cass-operator/operator/pkg/reconciliation.(*ReconcileCassandraDatacenter).Reconcile\n\t/cass-operator/operator/pkg/reconciliation/handler.go:269\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.17.4/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.17.4/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io/apimachinery@v0.17.4/pkg/util/wait/wait.go:88"}

Did you expect to see something different?
There should be a way to stop cleanups. It is understood that somehow the cleanup is wrongly reported as failing. However, there needs to be a way to get out of that loop.
How to reproduce it (as minimally and precisely as possible):
Environment

Cass Operator version:
Insert image tag or Git SHA here

* Kubernetes version information:
kubectl version
* Kubernetes cluster kind:

insert how you created your cluster: kops, bootkube, etc.

Manifests:

insert manifests relevant to the issue

Cass Operator Logs:

insert Cass Operator logs relevant to the issue here

Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-940
┆Priority: Medium

After the discussion in the meeting, here is my proposed approach:

operator will spawn cleanupAfterScaling() to a goroutine and mark this part of the operation as done. The cleanupAfterScaling() will eject logging and potentially events to indicate if the cleanup has failed / succeeded. There will be no retries and the timeout for that operation is removed (but context is created to allow canceling).
The above approach works with older images of DSE/Cassandra also, without requiring changes to the management-api / Cassandra code.
We should look into fixing the issue in Cassandra by making the process async (such as queueing it to the compaction queue instead of canceling all compactions and waiting for completion in a sync matter)
We will also fix a bug in the cleanupAfterScaling() which stops the processing if first node succeeds as the operation should be ran on all of the nodes (serial).

There will be no retries and the timeout for that operation is removed (but context is created to allow canceling).

If the timeout is removed, do we fall back to HTTP defaults?

We will also fix a bug in the cleanupAfterScaling() which stops the processing if first node succeeds as the operation should be ran on all of the nodes (serial)

It should be run on all nodes except the one that was added.

The above approach works with older images of DSE/Cassandra also, without requiring changes to the management-api / Cassandra code.

That is a plus but I think we should also look at making it async on the management-api side since getting changes pushed through in Cassandra is more involved and will take a lot longer.
The other reason I would like to see the change on the management-api side is because I think it would be a bit more resilient.
Doing it on the operator side means that if the operator pod goes down then the operation is aborted. That shouldn't be the case. The operation should able to continue to run so long as the Cassandra pod is up IMO.

That would work as long as management-api can keep track of those jobs. Otherwise at cass-operator we're unable to track which pods have executed, which haven't and when should we reissue the cleanup command.
Also, we need to detect when management-api supports this new feature as there are Cassandra pods with non-functional and functional versions.

I think this is a pretty nuanced approach and threads the needle.

yes, cleanup needs to be fixed to be less aggressive to shutting down existing work. However, this is also risky as we could get long-running compactions that block all compaction on the node for hours. We cannot count on this getting widely better since it is tricky to make cleanup less mean without creating new issues. Therefore, I would not expect a resolution on this front any time soon.
no cleanup on added nodes: yes! Nice optimization.
upgraded management-API great, with lots of baked images out there, as @burmanm noted, we would need to support two code paths for this. I think this is maybe ok, but part of me does wonder if auto cleanup is worth it or not. I get there is a long-term goal to remove all the hard parts of Cassandra out via the operator, but I also sort of wonder if this should be an explicit command to the operator itself? Some CRD for creating a cleanup job? This way the end-users still do not have to manage running cleanup on the cluster, but they can control when it happens.

no cleanup on added nodes: yes! Nice optimization.

This is not being removed. The cleanup will still be called in the ScalingUp process.

Cassandra out via the operator, but I also sort of wonder if this should be an explicit command to the operator itself? Some CRD for creating a cleanup job?

There is already a job that the user triggers, that's the scalingUp. If the cluster can't handle scale up process at that point of time, it should not be issued (and instead done during the maintenance window they might have).

So if we and N nodes then it will be called on 1st...N-1th?

Well, it will be called on every node, but the operation on that new node is noop.

I think for 4.0 there's a better way. The Virtual Tables provide a view system.sstable_tasks which allows to fetch the status of compactions and cleanups. Modifying the management api to make the task go to background would allow us to check on the next reconcile if the pod has finished the cleanup task (by querying the virtual table) and if it has, move on to the next one. Fixing 4.0 itself to make this always async is of course another thing, but that's a slower approach to get this working.
For older deployments (and 3.11), the approach as done in PR #191 should be still used as a workaround.


Add walltime metrics on add primitive

closed #72
😕 Maybe we should handle it this way

thank you for your contribution!
this pr adds the walltime metrics for the add primitive, we still need add the walltime metrics for the sampling phase, which locates in the llama2.rs file, so the #72 issue is still better to be kept open :)

ok, I will continue work on it


Crashes in promql.ParseMetricSelector()

After fuzzing ParseMetricSelector() for a few hundred iterations (see https://github.com/prometheus/prometheus/issues/667#issuecomment-125750642), it is found to crash on inputs .٩, G.٩ and .٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩.
The first two lead to errors in the lexer and the latter hangs the parser (i.e. it takes more than 10s to complete; the limit looks to be imposed by go-fuzz).
See

Whoa, pasing .٩ into the Prometheus expression text area in the browser and then hitting the left-arrow button moves the cursor all the way to the left of the input field and then freezes my Chrome tab. Seems like Prometheus isn't the only piece of software disliking that character combination...

Hah. So this symbol is an Arabic 9, which is categorized as a digit by unicode.IsDigit().
http://play.golang.org/p/TsuLx8f2pO
Same for the other "digits" in the Arabic Unicode block: https://en.wikipedia.org/wiki/Arabic_(Unicode_block)
This probably throws off our parser because we use unicode.IsDigit() in multiple places in the lexer in the expectation that it would only match [0-9].
Filed https://github.com/prometheus/prometheus/pull/942 to fix this.
I definitely learned something new today.

@msiebuhr Btw., were you inspired by this Fuzz-athon? https://groups.google.com/forum/#!topic/golang-nuts/4PmyYvcnpIs


Adding feature: IRIS Recognition

feature request link: https://github.com/akshitagupta15june/Face-X/issues/422

can you make changes in folder name its like you have made two same name folders

create in a single folder

create in a single folder

@akshitagupta15june It is merged now, so I guess making a single file now is not possible.
If you can, please do the needful.

can you please give me the direct link of my pull request which i can add to my resume. I can not find it.